Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Wim Brul

Pages: [1] 2 3 ... 12
1
Multimedia / Re: Use of webcam
« on: June 02, 2020, 03:52:14 pm »
Hi Lars,

Hi Wim,

does USBAUDIO.SYS also fail to find the microphone on the C-270 ?

I cannot try because I don't have the C270. But the C270 is also a miscellaneous device so usbaudio.sys will also ignore it.   

Quote
For the C-250 and also for the C-270 I can see AUDIO CONTROL and also one or more AUDIO STREAMING interfaces and that's ok.
But there are also association descriptors. Maybe usbaudio.sys fails to properly find the control and streaming descriptors because it gets confused by the association descriptor.

Certainly, USBAUDIO.SYS should not trap if it finds a "record only" USB audio device. I have a USB microphone (only MIC). Let's see what that does to USBAUDIO.SYS.

I must say that I did a dirty hack to accept the webcam and to find the feature_unit  descriptor. I seem to recall that the traps occur while attempting to record.

Quote
I would say that USBAUDIO.SYS (and USBAUD2.SYS) should support everything that has a AUDIO CONTROL and AUDIO STREAMING interface (descriptor). It has to serve all devices of that class, even if there is more to the device than just audio.

The video part would then be handled by a USBVIDEO.SYS driver but you have decided to go a different route via USBCALLS/USBRESMG which is also ok.

2
Multimedia / Re: Use of webcam
« on: June 02, 2020, 12:24:27 pm »
I also tried to have usbaudio.sys recognize the c250 microphone but I gave up on that.

Wim, can you send me the lsusb report for the C250 ? I suspect that there is some feature unit for volume/mute on the USB "data out" (microphone) path that needs to be cranked up (or a multiplexer unit set to the correct input or some such). Currently, USBAUDIO.SYS only controls the feature unit for volume/mute on the USB "data in" (speaker) path.

O.K. I have attached the lsusb reports for both the c250 and c270.
The problem (in fact feature) with usbaudio.sys is that it does not recognize the webcam as an audio device. It is a so-called miscellaneous device.
Once I fixed that. It appears that only the microphone has descriptors and usbaudio.sys expects an audio output interface as well. It ran into traps.

Quote
You can even try to write a REXX script to crank up that feature unit. You sure know how to do that once you find the corresponding feature unit in the descriptor info ...

Yes I do. The question remains should usbaudio.sys support the webcam microphone. I doubt it.

3
Multimedia / Re: Use of webcam
« on: June 02, 2020, 11:35:40 am »
Hi Rémy,

Quote
Under linux, ffmpeg as well ffplay are able to use specified hw input device like webcam but this is currently not implemented under os/2 (code not ported)

Perhaps 2 hardware devices are then being used (one for audio and one for video)? Would that be dll's (like video4linux.dll and alsa.dll)?

Quote
Or uvcscope sending mjpeg (play video + send all mjpeg or only send mjpeg) to ffmpeg or ffplay (both using parm " f mjpeg -i - "  (reading stdin)
e.g.  uvvscope /dxxxx:xxxx:xxxx - | ffplay -f mjpeg -i -     (or   uvvscope /dxxxx:xxxx:xxxx - | ffmpeg -f mjpeg -i - record.avi   

What do you mean by "play video + send all mjpeg or only send mjpeg" ? Would an application without video display (like my weblook.exe) do?

Quote
But audio is missing out of uvcscope...

Yes. To be done of course. But how? I looked into your avxcat.pdf and learned that audio and video are handled as separate inputs.
When both audio and video must be delivered then working with named pipes (one for audio and one for video)  would do I guess.
The webcam can only be accessed by one application, so how would I send both both audio and video through stdout?

Best regards,
Wim.

4
Multimedia / Re: Use of webcam
« on: June 01, 2020, 03:23:13 pm »
I have read some of the ffmpeg documentation and rfc1341(mime).

Section 20.15 mpjpeg - MJPEG encapsulated in multi-part MIME demuxer. 
Suppose the webcam streams mjpg video through "\PIPE\Webcam\Video".
Would the following be correct to play that mjpg video?

"ffplay -f mpjpeg \PIPE\Webcam\Video"
"ffplay -f mpjpeg Strict_mime_boundary 0 \PIPE\Webcam\Video"
"ffplay -f mpjpeg Strict_mime_boundary 1 \PIPE\Webcam\Video"

What are the exact mime headers to be used?

Section 20.16 rawvideo - Raw video demuxer.
Suppose the webcam streams yuyv video through "\PIPE\Webcam\Video".
Would the following be correct to play that yuyv video?

"ffplay -f rawvideo -video_size 640x480 \PIPE\Webcam\Video"
"ffplay -f rawvideo -pixel_format yuv420p -video_size 640x480 -framerate 10 \PIPE\Webcam\Video"

The above assumes that the original mjpg/yuyv video from the webcam will be streamed.
An alternative could be to stream rgb24/mjpg snapshots from the application window?

5
Multimedia / Re: Use of webcam
« on: May 31, 2020, 10:40:06 am »
Quote
  Interface 2: Alt=0 nEP=0 Class=1(Audio) SubClass=1 Protocol=0 StringIx=0
  Interface 3: Alt=0 nEP=0 Class=1(Audio) SubClass=2 Protocol=0 StringIx=0
  Interface 3: Alt=1 nEP=1 Class=1(Audio) SubClass=2 Protocol=0 StringIx=0
  Interface 3: Alt=2 nEP=1 Class=1(Audio) SubClass=2 Protocol=0 StringIx=0
  Interface 3: Alt=3 nEP=1 Class=1(Audio) SubClass=2 Protocol=0 StringIx=0
  Interface 3: Alt=4 nEP=1 Class=1(Audio) SubClass=2 Protocol=0 StringIx=0

The information on audio is rather meager i.e. even endpoint information is missing.
Fortunately I have lsusb reports from both c250 and c270 webcams and the audio descriptors appear to be identical.
The inbuild microphone may deliver 16-bit mono at 16000/ 24000/32000/48000 Hz.

I have experimented in the past to obtain audio from the c250 webcam and it appears to be possible.
The big question is what to do with the audio data once obtained. Should it go to the default audio device?
The truth is that I am not really an application programmer, so I want this to be as simple as it can be.

I also tried to have usbaudio.sys recognize the c250 microphone but I gave up on that.

6
Multimedia / Re: Use of webcam
« on: May 27, 2020, 05:11:57 pm »
In my search, I did find one comment from David A (the USB developer) that's relevant here. He said that he uses a "046D:0804" as part of his QA testing and that it works "just fine". I wouldn't have known what device that was if it weren't the very first one on Wim's "USB Webcam Tests" page: a Logitech C250 Webcam.

So, at this point we know that one program is able to establish an isochronous connection with a common webcam using v12.04/12.05 while another isn't. Until someone files a ticket with AN and/or Wim cares to look into this, that's _all_ we know. IMO, it's way too early to play the blame game.

Too early to file a ticket. Right now I am busy testing isochronous transfers with my Logitech C250 Webcam using the usbecd.sys interface. Will take some time though.

7
Multimedia / Re: Use of webcam
« on: May 25, 2020, 12:53:02 pm »
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.

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.

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!

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

8
Multimedia / Re: Use of webcam
« on: May 24, 2020, 09:55:34 pm »
The program gets this FF14 error when it tries to allocate resources for isochronous transfers.
Like Lars already said: isochronous transfers are not yet supported by the ArcaOS 12.x USB drivers.
Try and use the ArcaOS 11.17 drivers instead. Or use the latest Lars Erdmann USB driver set.

Ok, thanks i'll give it a try

Did you try and use your webcam with the ArcaOS 11.17 drivers? Did it work with these?
Did you try and use your webcam with the Lars Erdmann 10.234 drivers? Did it work with these? 

Hi    Wim,

According Andy's update,  isochronous is supported.
How to make it work please using  AN latest build ?
Thanks

Regards
Rémy

When the answers to my 4 questions above are yes then it is time to use ArcaNoae's Mantis to report the problem.   

9
Multimedia / Re: Use of webcam
« on: May 20, 2020, 05:24:20 pm »
The program gets this FF14 error when it tries to allocate resources for isochronous transfers.
Like Lars already said: isochronous transfers are not yet supported by the ArcaOS 12.x USB drivers.
Try and use the ArcaOS 11.17 drivers instead. Or use the latest Lars Erdmann USB driver set.

10
Multimedia / Re: Use of webcam
« on: May 20, 2020, 02:57:49 pm »
Hi Remy,

Go to https://home.hccnet.nl/w.m.brul/usbvideo/index.html and select your webcam, or equivalent, then select the necessary program.

Not sure about sound as I don't have it on my main computer.

Hi Ivan,

I already was there but nothing works.
My system is SMP  -   USBEHCD.SYS  (ArcaOS latest level)
The  webcam is a 720p 30fps - defined as USBECD.SYS /D:046D:0825:0010

Regards
Rémy

Hi Remy,

The URL given by Ivan points to my "USB Webcam Tests" web page, which is beta test software, not to be used anymore.
So remove the usbecd.sys line you added in config.sys for your webcam and use my "UVC Microscope Viewer" instead.

Regards, Wim.


11
Hardware / Re: Report: ArcaOS on Panasonic Toughbook CF-M34 MK1
« on: May 14, 2020, 07:28:28 pm »
Everything working now.. but this notebook also comes with touch screen ... next task will be to get that working, too.
Have a look at my "Digitizer Support" web page. Support is a 3 step process: Access COM device, Develop REXX script, Send Mouse events.
It seems to me that your Panasonic Toughbook touch screen has been connected to com port 2 using a gunze AHL-71N Touch Panel Controller.
Try and run "comraw 2 9600" to get raw input data at 9600 baud into the 9600.raw file. Touch the screen for actual input. Use Ctrl+C to stop.

12
Unfortunately I wasn't able to get any further than this despite following Lars' advice on installing his driver kit and doing my best to make sure config.sys was up to date. I'm currently backing up my system and once that is complete I may do a fresh reinstall and try following the steps on a clean slate - I'm sincerely hoping that may yield better results than what we've been facing so far.

I have also once again attached a copy of my config file for anyone who is interested.
I looked into your config.txt file and after the "REM [END USB section" line it contains duplicate "BASEDEV=USBD.SYS" etc. statements. Take your time to scrutinize.

13
I have prepared Yoga12-20200422.zip containing two rexx scripts for you to try out:

1. Run ofinger.cmd in a command window to obtain and show raw finger events. Touch the screen with your finger to see if that works.

2. Run ostylus.cmd in a command window to obtain and show raw stylus events. Touch the screen with your stylus to see if that works.

14
Quote
I apologize for not attaching this beforehand, I've uploaded it with this post. From inspecting the file myself I see it is putting out a picture, the UVCVIEW program itself just doesn't display it.
No need to apologize. I am glad it is now available so I may improve my mjpg decoder once I find the time and feel like it.

Quote
And then loops on this:
Code: [Select]
stylus configuration
 stylus configuration
[0000001D]
The program is retrying because usbecd.sys reports an i/o error. Please report which USB driver set you are using. Try and use the Lars Erdmann USB driver set.

15
Quote
Perhaps the mjpg decoding in uvcview.exe is not good enough. Click on "Testshot" to capture raw input data. Captured input data is written to the UVCVIEW.RAW file for later inspection. This could be of help in situations where the WebCam Viewer is working but the displayed picture stays black. Post your results. Try uvcview /u to watch yuyv video.

yuyv appears to fix the camera issue entirely, I'm happy to say the camera is now working perfectly. It's a shame I didn't try the /u flag beforehand as it's clearly there in the documentation

Nice. However, I really would like you to attach UVCVIEW.RAW created from the procedure outlined above (using uvcview without parameter) for me to inspect.

Pages: [1] 2 3 ... 12