[closed] VidBlaster not setting correct video size for camera

[BrandonJones]

I would like to operate VidBlaster at 640x360 for both recording and streaming (eventually). However, I'm running into a problem doing this. Here is what is happening:

I'm using VidBlaster 1.11 and capturing video with an Osprey 450e (via composite). The video is coming in natively at 864x480. VidBlaster functions just fine at the 864x480 resolution and even at 428x240 (which is what I've been running it at and the picture is good and clean). When I change the VidBlaster resolution to 640x360, it down scales the video - producing unacceptable pixilation in the process. I want a good clean picture.

So, I had the idea of resizing the video with the Osprey card. This can easily be done with the software provided with the card. However, after I make the appropriate changes to the settings on the Osprey card and change the resolution in VidBlaster to 640x360, VidBlaster recognizes the resolution for the camera to be 720x480 (not the 640x360 it is being resized to via the card). Even stranger, if I change the VidBlaster resolution back to 428x240, it actually correctly recognizes the camera resolution to be 640x360 – of course, it then down-scales the video to 428x240 creating the unwanted pixilation again.

Any idea what is going on here? Why would VidBlaster detect the correct camera resolution when set to 428x240 and not when set to 640x360 – the actual camera resolution?

Thanks for the help.

Brandon

[Mike]

The card's driver does that. VidBlaster simply asks it to use the set resolution, or something that comes closest.

[Mike]

I think I can work around this problem using new code, but first need to have a better understanding of the problem. Next time you find VidBlaster uses the wrong resolution, make sure you are running v1.12 then and send me the Log.

[BrandonJones]

Thanks Mike, I'll get you more info. How do I get a copy of 1.12? Don't see it in Downloads forum.

[kricher]

I believe ver. 1.12 is still in the testing phase. Mike will release it when he feels it is ready to go.

[lill]

Hi

1.12 is released now...

To get it, go to http://vidblaster.com/forum/index.php?topic=1053.0

[lill]

Hi I would like to reopen this topic...

I have now done some test on my VidBlaster Machine...

Se below of my hardware version of VB is 1.17

I am capturing a PC on 1024x768 on the DVI/VGA in on my Datapath card.

And when I change the resolution in VidBlaster (Below as Output) (Video/Resolution, all other are on auto...)

I get the following when i right click the camera module...

Output Camera module says input is.
640x360 512x256
640x480 640x480
720x406 640x480
768x576 640x480
800x600 640x480
864x480 1024x512
1024x576 1024x512
1024x768 1024x1024
1280x720 1024x512

[Mike]

And?

[lill]

And?


Why dose not VidBlaster stay on the same input... I don't change the input, only the Total Output (as I think it's)
and sometimes VidBlaster "feels" almost the correct...

When I use another "captureing software" beside, it always stays on 1024x768 as the input resolution...

Is it possible to get VidBlaster to nail int the input somehow ?

[Mike]

As I write earlier in this thread, VidBlaster automatically finds the nearest supported resolution. Your findings seem to confirm this, so I do not understand what bug you wish to report?

[weconverse]

I'd like to add my few cents here, although it most likely is not about a "bug". I will investigate more, meanwhile just pointing to the problems I have.

I am currently trying to move my productions from 4:3 (typically 640x480) to 16:9 (desired 864x480). Furthermore I want to produce on a laptop, so USB video grabbers and web cams is what I can use. Been trying the last few days like a madman to make multiple cameras work together, so far little success. The webcams I am using are Logitech Quickcam Pro 9000 and Microsoft Cinema.

I have only found USB two capture devices. The König USBVG5, reported by Vidblaster as "USB 286" or something similar (will check again when I am at the production machine) and a Plextor, reported as "TVBOX". König is automatically detected as 320x240 or 640x480, and the Plextor always as 720x576. The problem starts when I set Vidblasters resolutions to any "wide" format. In some settings König info reports 320x240, in other it just goes black - as do the Plextor.

As I said, I will test more and write down what I get for various combinations of settings and cameras. But generally I do not understand why the USB drivers automatically sets the resolutions they do. And I am fully aware of that this might be issues with drivers, not Vidblaster.

Thanks.

[Mike]

If you continue this, please open a new thread under Hardware. Indeed many webcams have very limited support, often they only support one resolution.

[Johan Lundberg]

I've tried one quite cheap 4-channel CCTV. It shows up and works in Vidblaster BUT, gives a really low resolution. I don't think it understands Vidblasters request regarding what resolution to send and I'm actually getting a higher resolution from the card when i choose a VB resolution of 512x288 instead of when I choose 1024x576. I guess this would be solved if we could force Vidblaster sources to specific resolutions.

Without knowing how Vidblaster communicates with the devices I get the feeling that some of this has to do with the fact that regular video is using non-square pixels where the computer world uses square pixels. For instance, in the video world both PAL 4:3 and PAL 16:9 are 720x576, but with different pixels aspect. Both are non-square, which means the pixels are wider than they are high and the image is stretched to it's correct aspect ratio. In the computer world PAL 4:3 equals to 768x576 and PAL 16:9 to 1024x576, all square pixels. If Vidblaster ask the device to provide 1024x576 the device might think that it can't provide that (when in fact it can), and drops to a very low resolution instead.

As pointed out earlier, I don't know for sure if this is the problem but from all testing I've done with various equipment I wouldn't be surprised.


/Johan

[Mike]

As I suggested earlier I will start rewriting the code so I can make my own best judgement for the resolution. This won't fix bugs in drivers (offering a resolution that it does not support given the input signal), but at least will prevent some from turning up. For the Broadcast edition I will open up manual selection of the resolution, giving you ultimate control.

[Mike]

Okay, here's what I did. I added a popup menu option in the Camera module called Video Resolution (see attached shot) that indicates the resolutions available, and which one is automatically picked. I did not write my own algorithm yet, as I still haven't seen any hard prove that what we have now does not work.

This will be available in v1.19. If anyone sees a wrong auto selection, please send a screen shot like attached and do not forget to mention the global video resolution. Thanks.

[weconverse]

Thanks Mike! Looking forward to try that feature out.

[Johan Lundberg]

Sounds great Mike! :)

[lill]

Lovely

Thanks Mike

[weconverse]

I have had problems using two Logitech 9000's (1 webcam and 1 quickcam) at the same time. Typically one of them sometimes goes black, depending on the resolution set in Vidblaster and what other cameras I use. Today Windows7 downloaded the latest software/driver from Logitech (dated 2010-05-14, version 13.01873.0. At first they seemed to work together nicely, then while trying to add another camera the Quickcam went black. Now I see that Vidblaster has set its frame rate to 15fps, while Vidblaster is set to 25fps 720x406 and all other cameras report 25fps. Both the Logitech cams report 800x450. Selecting screen capture for the two modules having the Logitechs, and then changing back to the Logitech cameras always gives the Webcam 25 fps, and the Quickam 15 fps. It does not matter which order I select them back, or in wich one of two source modules. The Logitech camera I add back first becomes visible, the second is black.

If possible, it could perhaps be useful with the possibility to force a frame rate too?

[Mike]

This will be possible in the next release, see here (http://vidblaster.com/forum/index.php?topic=200.msg6811#msg6811), but by default VidBlaster sets the camera to the same frame rate as the global frame rate. Most webcams ignore this however and adjust frame rate to lighting conditions. Please do not continue this discussion in this topic.

[lill]

Hi

I have problem to set the Video Resolution on and VGA capture unit...

See attached image...

The resolution from the capture device is 1024x768

And the global VB resolution is 768x576 or 1024x768.

I have tried with diffrent settings on all, and in no setting am I able to "hard lock" a resolution in the Camera module/Video Resolution... to 1024x768.

Please help...

[Mike]

You cannot lock the setting as it is fixed to Auto. Please reread this topic. If you think VidBlaster is setting the wrong resolution, send me a readable screen shot.

[lill]

Hi Mike

Will be back with VidBlaster in 1-4 days, burnt my VidBlaster machine...
Will give you and update then...

[lill]

Okey Now I am up and running again...

Yes the camera module only says Auto and I am not possible to change it in any way. Please se attached image.

How to remove the Auto, is it possible or do I missunderstand this ?

[lill]

I really need to be able to force VidBlaster to capture at a specific resolution... can it be made ?

[Mike]

Sure, but please read this topic first: I need to see if there is a problem and what, before I invest time in this. Still waiting for proof (and screen shots).

[lill]

Sure, but please read this topic first: I need to see if there is a problem and what, before I invest time in this. Still waiting for proof (and screen shots).


Hi Mike

Sorry, I have read the thread, and I am sorry, I cant see what you need, and if, from me...

So if I can help in any way, please point it out in a short and easy list... so i really understand it :-)

[Mike]

Your really did read the topic? At least you should have noticed your attached image is missing?

[lill]

Your really did read the topic? At least you should have noticed your attached image is missing?


Aha sorry diden't see that... now it should be attached...

[Mike]

Like last time, this is a reduced size screen shot that is unreadable for me.

[lill]

Like last time, this is a reduced size screen shot that is unreadable for me.

Humm, strange I will send you a mail... the picture seams fine before I post it...

[Mike]

Maybe the forum reduces its size? Just send me the part with the popup menu, that's all I need. Also saves me disk space on the server :)

[Mike]

Got it. So what is the problem here? Seems VidBlaster picks the right resolution. I'm having deja vu now :(

[lill]

Got it. So what is the problem here? Seems VidBlaster picks the right resolution. I'm having deja vu now :(


Or we missunderstand each other...

The capture resolution is 1024x768 and the camera module says in Info 640*480, I want it do be able to force it to be 1024x768...


As my understand the Video Resolution function was a way to force this to happen... even if VidBlaster dot get it automatic...

[Mike]

You cannot force a video device to work in a resolution it does not support. You have set VidBlaster to work in 768*576, so based on supported resolutions by this device it rightfully decides 640*480 fits the best. I have explained all of this already on page 1 of this topic :(

[lill]

But this is no problem when I start camtasia and want to capture this device, so thats why I can't really understand why we cant get it to work in VidBlaster...

[Mike]

I am not familiar with camtasia so do not know how it works, but it may be the same as someone telling them that your card supports HD because VidBlaster supports it. The list of resolutions supported by your device is in the menu. VidBlaster picks the best resolution for your need. Bug closed. Oh, it already was ;)

BTW: if you really feel your device supports this resolution and VidBlaster misses it, feel free to open a bug report for it. I'd like to have some confirmation from the manufacturer though.

[lill]

I am not familiar with camtasia so do not know how it works,

Camtaisa is the most used software's to make screen capture video's and it also have a function that inputs camera if you want.

I also downloaded another software (Debut Video Capture Software Professional I google it) and test it, and it also says 1024x768 as the capture format...


but it may be the same as someone telling them that your card supports HD because VidBlaster supports it. The list of resolutions supported by your device is in the menu. VidBlaster picks the best resolution for your need. Bug closed. Oh, it already was ;)

I don't think VidBlaster picks the best, in this case ;)


A bit more testing between this two programs...

I change the resolution on the machine I am capture from 1280x720
the Debut Video software gets it and says 1280x720 as resolution
VidBlaster still have 640x480 (with the global Resolution 768x576)

When I then change the global resolution in VidBlaster to 1280x720 then
the camera module info say 1024x768... Why not 1280x720 for as I understands it would be the best resolution... as it would be a 1:1...



Sooo is there any why to make it possible to do that VidBlaster gets me a choice so I can pick it for my self... (or don't have the list greyed out...)

If VidBlaster gets that my card support diffrent inputs, then I would want to force it to a input... and if the pictures looks hell, (it should be up to me to understand that and change the resolution to the correct or back to Auto.

[Mike]

Again, 1280*720 is not supported by your video device, as you can see in the list, so VidBlaster picks the next best resolution.

[lill]

Fair enough the Vision SD4+1 don't support 1280x720 as of the manual...
but the other 2 software gets the resolution from somewhere...

And as for supported formats its supports 1024x768 and in the Camera module the greyed out resolution list in VidBlaster tells me that it support's is 1024x1024 or 1024x512 and none of these is supported as from the manual...

Is there any chance that its something in the code or "talk" between VB and the card driver because the greyed out list is change depends on the global resolution ?

When I now have update the driver for the Vision card to a new relase of the driver (4 days ago) the grey out list says 1024x1024 and 1024x768

And when I then change the global resolution is set to 1024x768 the camera module put in the 1024x768 in the grey out list...


I don't know if I am look for a new feature or something like that... but as of know VidBlaster is the software that don't get this cards resolutions...

[Mike]

Daniel, I have opened a new bug report (http://forum.vidblaster.com/showthread.php?t=1344) on your name for this problem as it falls outside current topic.