|
|
| fmagreed2 |
| Posted: Jan 4 2011, 06:36 PM |
 |
|
Newbie
Group: Members
Posts: 6
Member No.: 29527
Joined: 4-January 11
|
I'll start by saying I've tested this in both 1.9.11 and 1.10.0 and they both exhibit the same behavior. I'll try to be as clear as possible. While capturing, these options seem to behave in a strange way. This could actually apply to almost any capture format, but I'm just going to use my own situation as an example.
I have a capture card (BlackMagic) which will only output HDYC, so I go to Video>Set Custom Format and the only option allowed is HDYC.
HDYC is a rare format, though, which means the only codecs available are the ones that came with the card and a modified huffyuv codec, so going to compression gives only these options, as expected.
When filters are involved is the confusing part.
From what I understand, the HDYC stream is fed to the filters, converted for use if needed by the filter, and altered as needed. After the last filter, the video stream (whatever format it happens to be at this point) is converted to RGB24 as long as the option to skip isn't selected.
So the video-stream is now RGB24. This is accepted by many, many encoders. If I go to compression, though, I'm still limited by the input format HDYC. Since the format being sent to the encoder is now RGB24, shouldn't RGB24 compatible codecs now be shown in the compression dialog? Along the same lines, I could opt to skip the 24-bit conversion and set a convert format filter as the last step to get any format I wanted.
It's possible I'm misunderstanding how these features are supposed to be function, in which case consider this a feature request. Since virtualdub can already convert formats for filters, could an option be added to specify output format so we're not limited in our choice of codec?
Thread from which this was inspired:
http://forum.doom9.org/showthread.php?p=1468531 |
|
| phaeron |
| Posted: Jan 12 2011, 05:29 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Yup, this is a bug. As a workaround, choose the format with a different capture mode that can produce RGB, such as the video file test driver, then switch back to the Intensity.
|
|
| fmagreed2 |
| Posted: Jan 15 2011, 01:19 AM |
|
|
Newbie
Group: Members
Posts: 6
Member No.: 29527
Joined: 4-January 11
|
First: Thank you for replying!
I can't test the workaround at the moment (I'm in my dorm and the capture card's at home), so I can't tell you if it works. Will this issue be fixed in 1.10 (just in case the workaround doesn't work, and it just makes life easier)? |
|
| fmagreed2 |
| Posted: Feb 17 2011, 10:35 PM |
|
|
Newbie
Group: Members
Posts: 6
Member No.: 29527
Joined: 4-January 11
|
I've finally had some time to test this. The workaround does not work. Switching back to the intensity also switches back to the black magic codec. |
|
| phaeron |
| Posted: Feb 19 2011, 08:54 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
It does, but the key is that it doesn't switch the codec back -- you select the codec, then you switch back to the Intensity, and it should still use that codec even though it won't show up in the compression dialog anymore.
|
|
