OS/2, eCS & ArcaOS - Technical > Multimedia

Use of webcam

<< < (5/35) > >>

Wim Brul:

--- Quote from: Lars on May 25, 2020, 11:45:32 am ---One additional note:
Wim can confirm or not but I would believe that uvcview.exe/uvcscope.exe uses USBCALLS/USBRESMG to do its thing.
Therefore,the problem could also be located in those components.
Taken the fact that Rich reported that USB audio works ok with the AN 32-bit stack, I consider these 2 a likely source of the problem.

--- End quote ---

Yes, uvcview.exe/uvcscope.exe are using USBCALLS/USBRESMG to do their thing. The only difference is that uvcscope.exe has a microscope selection parameter.


--- Quote from: Neil Waldhauer on May 25, 2020, 05:33:13 am ---I have a Lenovo Thinkpad T540p with two bootable ArcaOS volumes. One has USB 11.17, and runs websee UVCView.exe perfectly. The second has USB 12.05 and  UVCView terminates with an error: [0000FF14] Obtain thread error!

--- End quote ---

This confirms that the problem is somewhere within the ArcaNoae 12.x USB driver set.

Remy:

--- Quote from: Wim Brul on May 25, 2020, 12:53:02 pm ---
--- Quote from: Lars on May 25, 2020, 11:45:32 am ---One additional note:
Wim can confirm or not but I would believe that uvcview.exe/uvcscope.exe uses USBCALLS/USBRESMG to do its thing.
Therefore,the problem could also be located in those components.
Taken the fact that Rich reported that USB audio works ok with the AN 32-bit stack, I consider these 2 a likely source of the problem.

--- End quote ---

Yes, uvcview.exe/uvcscope.exe are using USBCALLS/USBRESMG to do their thing. The only difference is that uvcscope.exe has a microscope selection parameter.


--- Quote from: Neil Waldhauer on May 25, 2020, 05:33:13 am ---I have a Lenovo Thinkpad T540p with two bootable ArcaOS volumes. One has USB 11.17, and runs websee UVCView.exe perfectly. The second has USB 12.05 and  UVCView terminates with an error: [0000FF14] Obtain thread error!

--- End quote ---

This confirms that the problem is somewhere within the ArcaNoae 12.x USB driver set.

--- End quote ---

This doesn't confirm anything due USBCALLS is specific and must be at same level as other usb drivers.
Changing process or like it works is not a sing of miss function but more like compatibility...
 
What can be done to have uvcscope.exe compatible with new releases ?
(this is something I always have with GUI reequiring me to verify and adapt my "tools" at each update)

Do you have a debug option to trace in/out flow ?

Thanks and Regards
Rémy
   

Remy:

--- Quote from: roberto on May 25, 2020, 10:03:49 am ---I version 12.05 of the usb, I had to remove it because it did not allow me to send forwarding emails from the Thunderbird. For now I continue with 12.04

--- End quote ---

With which thunderbird version !
I have done many test recently with thunderbird 38 and 45 and didn't fall into our case (I have all dlls at latest AN rel level). It may be interresting for me to test similar case (after updating clamav xpi plugin). how did you (step by step)
Regards
Rémy

Lars:

--- Quote from: Remy on May 25, 2020, 01:54:49 pm ---
--- Quote from: Wim Brul on May 25, 2020, 12:53:02 pm ---
--- Quote from: Lars on May 25, 2020, 11:45:32 am ---One additional note:
Wim can confirm or not but I would believe that uvcview.exe/uvcscope.exe uses USBCALLS/USBRESMG to do its thing.
Therefore,the problem could also be located in those components.
Taken the fact that Rich reported that USB audio works ok with the AN 32-bit stack, I consider these 2 a likely source of the problem.

--- End quote ---

Yes, uvcview.exe/uvcscope.exe are using USBCALLS/USBRESMG to do their thing. The only difference is that uvcscope.exe has a microscope selection parameter.


--- Quote from: Neil Waldhauer on May 25, 2020, 05:33:13 am ---I have a Lenovo Thinkpad T540p with two bootable ArcaOS volumes. One has USB 11.17, and runs websee UVCView.exe perfectly. The second has USB 12.05 and  UVCView terminates with an error: [0000FF14] Obtain thread error!

--- End quote ---

This confirms that the problem is somewhere within the ArcaNoae 12.x USB driver set.

--- End quote ---

This doesn't confirm anything due USBCALLS is specific and must be at same level as other usb drivers.
Changing process or like it works is not a sing of miss function but more like compatibility...
 
What can be done to have uvcscope.exe compatible with new releases ?
(this is something I always have with GUI reequiring me to verify and adapt my "tools" at each update)

Do you have a debug option to trace in/out flow ?

Thanks and Regards
Rémy
 

--- End quote ---

It worked with 11.17. It worked and still works with my USB driver stack. It fails with 12.05. Therefore, it confirms EVERYTHING. If AN did change the programming interface to USBCALLS/USBRESMG either accidentally or deliberately or if it is a bug accidentally introduced, then it is up to them to fix it.
There are a whole lot of other applications using USBCALLS/USBRESMG. Do you also expect them to be updated ?

Remy:

--- Quote from: Lars on May 25, 2020, 02:41:57 pm ---
--- Quote from: Remy on May 25, 2020, 01:54:49 pm ---
--- Quote from: Wim Brul on May 25, 2020, 12:53:02 pm ---
--- Quote from: Lars on May 25, 2020, 11:45:32 am ---One additional note:
Wim can confirm or not but I would believe that uvcview.exe/uvcscope.exe uses USBCALLS/USBRESMG to do its thing.
Therefore,the problem could also be located in those components.
Taken the fact that Rich reported that USB audio works ok with the AN 32-bit stack, I consider these 2 a likely source of the problem.

--- End quote ---

Yes, uvcview.exe/uvcscope.exe are using USBCALLS/USBRESMG to do their thing. The only difference is that uvcscope.exe has a microscope selection parameter.


--- Quote from: Neil Waldhauer on May 25, 2020, 05:33:13 am ---I have a Lenovo Thinkpad T540p with two bootable ArcaOS volumes. One has USB 11.17, and runs websee UVCView.exe perfectly. The second has USB 12.05 and  UVCView terminates with an error: [0000FF14] Obtain thread error!

--- End quote ---

This confirms that the problem is somewhere within the ArcaNoae 12.x USB driver set.

--- End quote ---

This doesn't confirm anything due USBCALLS is specific and must be at same level as other usb drivers.
Changing process or like it works is not a sing of miss function but more like compatibility...
 
What can be done to have uvcscope.exe compatible with new releases ?
(this is something I always have with GUI reequiring me to verify and adapt my "tools" at each update)

Do you have a debug option to trace in/out flow ?

Thanks and Regards
Rémy
 

--- End quote ---

It worked with 11.17. It worked and still works with my USB driver stack. It fails with 12.05. Therefore, it confirms EVERYTHING. If AN did change the programming interface to USBCALLS/USBRESMG either accidentally or deliberately or if it is a bug accidentally introduced, then it is up to them to fix it.
There are a whole lot of other applications using USBCALLS/USBRESMG. Do you also expect them to be updated ?

--- End quote ---

Are any RFC about this part of function ?
If no RFC exist, it may be possible, why not ? else it should satisfy rfc.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version