YV12 codec problem?

[chazz spacey]

Why sony vegas can't open this video? Can it be because YV12 codec?

http://youtu.be/-KuGdr_RRGg

[LigH.de]

Yes, might be. YV12 is a very basic color format, yet, Microsoft YUV converter does not handle it because it is planar. You have to assign a codec which will actively convert it. There are several excamples of VfW codecs providing such a conversion in addition, e.g. Xvid or ffdshow's VfW codec. Unfortunately, as convenient as the user interface of ffdshow's VFW Codec Configuration may be, it does not reliably register VfW codec associations after it has been installed, so you may have to use RegEdit to fix that...

[chazz spacey]

actually i need uncompressed video. how to get uncompressed video without codec? it has to be no codec when it is uncompressed right? when i select yuv color depth there is yv12 codec shows in mediainfo but when i select 24 bit rgb(888) there is no codec shows.

[jagabo]

The codec in an AVI file is identified by a fourcc -- a four letter code that indicates what codec is used. Even if the video is uncompressed it needs to have a fourcc to tell the program that opens it what uncompressed format the data is in. Try using installing ffdshow and enabling the YV12 fourcc decoder. Or install some other YV12 decoder.

[Cornucopia]

IOW, It may not need to be De-Compressed, but it still needs to be De-Coded. That needs SOME codec.

Scott

[chazz spacey]

why when i set ffdhsow encoder to uncompressed it saves video at RGB 24 bit? and in sony vegas uncompressed format is RGB 24 bit too? the file sizes are same.
uncompressed video must be RGB always?

[poisondeathray]

why when i set ffdhsow encoder to uncompressed it saves video at RGB 24 bit? and in sony vegas uncompressed format is RGB 24 bit too? the file sizes are same.
uncompressed video must be RGB always?

No, you can have uncompressed YUV 4:2:0 as well

IYUV and I420 are should be accepted by vegas natively . The difference between YV12 and those two, is is the U, V plane order is swapped

[poisondeathray]

Do you want to do some tests? Don't install anything, and try importing these into vegas . It's hard for me to do "clean out of the box" tests because all my computers have a bunch of codecs and junk installed

They are just 3 clips, 3 frames each, 640x360, YUV 4:2:0 uncompressed, but different fourcc's - I420, IYUV, YV12

Vegas should import I420, IYUV natively (at least I think it should), and it should decode it with studio RGB levels. The YV12, if you have a YV12 decoder installed should get computerRGB treatment

[hello_hello]

You can specify an output type for ffdshow's encoder configuration. For uncompressed output, it probably defaults to RGB, but you can change it. After selecting "uncompressed" click on "generic" and you'll see the output option.

I've never used Vegas, but you could try disabling all the output types in ffdshow's decoder configuration aside from YV12 (and maybe NV12). It's under "Output" in the ffdshow VFW configuration (and also the ffdshow DirectShow configuration). When ffdshow is decoding you should be able to hover the cursor over the ffdshow icon and the tooltip will tell you the input and output video type.

I'm not exactly sure how it works, but I'm pretty sure programs can tell ffdshow their preference for video type and ffdshow will convert it to that format if it can. If you disable the RGB output options that may solve the problem. Changing the "primary output colour space" setting to YV12 might also fix it without needing to disable the RGB output options.

[chazz spacey]

Do you want to do some tests? Don't install anything, and try importing these into vegas . It's hard for me to do "clean out of the box" tests because all my computers have a bunch of codecs and junk installed

They are just 3 clips, 3 frames each, 640x360, YUV 4:2:0 uncompressed, but different fourcc's - I420, IYUV, YV12

Vegas should import I420, IYUV natively (at least I think it should), and it should decode it with studio RGB levels. The YV12, if you have a YV12 decoder installed should get computerRGB treatment

only yv12.avi can't be opened:



and i installed "helix yuv codec suite 1.3", didn't work.

[chazz spacey]

You can specify an output type for ffdshow's encoder configuration. For uncompressed output, it probably defaults to RGB, but you can change it. After selecting "uncompressed" click on "generic" and you'll see the output option.

I've never used Vegas, but you could try disabling all the output types in ffdshow's decoder configuration aside from YV12 (and maybe NV12). It's under "Output" in the ffdshow VFW configuration (and also the ffdshow DirectShow configuration). When ffdshow is decoding you should be able to hover the cursor over the ffdshow icon and the tooltip will tell you the input and output video type.

I'm not exactly sure how it works, but I'm pretty sure programs can tell ffdshow their preference for video type and ffdshow will convert it to that format if it can. If you disable the RGB output options that may solve the problem. Changing the "primary output colour space" setting to YV12 might also fix it without needing to disable the RGB output options.


[Attachment 29022 - Click to enlarge]

didn't work. i want YV12 because RGB file size is insanely big.

[_Al_]

Get utvideo video codec, then you can choose, YUV420 or YUV 422, BT.601 or BT 709, even RGB or RGBA. It is lossless codec, so size is not that insane and Vegas loads that video.

[hello_hello]

What didn't work, saving the video as an uncompressed AVI in YV12 format or setting the ffdshow decoder to only output RGB? What program are you using to save the video as an uncompressed AVI? I can definitely open an AVI with VirtualDub, set the compressor as the ffdshow video codec and then configure ffdshow to output the correct type. It might help if you describe your process in a little more detail.

If Vegas can open AVIs, there's probably a way to avoid the large file problem with the help of Avisynth. I don't know if you use it but one method would be to create a basic Avisynth script for opening the original video. Once you create the script you can open it with MakeAVIS. It usually comes along for the ride when you install ffdshow, although I don't think there's a start menu shortcut for it. You need to navigate to the folder where ffdshow is installed and run it manually or create your own shortcut. MakeAVIS will "wrap" the AVISynth script into an AVI. You should be able to open the AVI with any program capable of opening one and AVISynth will frame serve uncompressed video. Doing it that way tends to be a bit slower when it comes to navigating but the AVI in question will only be a few MBs in size and you don't need to spend time converting to an uncompressed format. MakeAVIS can also add the audio to the AVI it creates in the form of uncompressed LPCM, or alternatively you can open the AVI with VirtualDub, add audio such as MP3 or AC3 or DTS and save it while using Direct Stream Copy for the audio and video. You'll end up with an AVI the size of the audio stream plus a few more MBs. That way you can import the AVI and edit the video and audio together as you normally would. You can even open the AVI with VirtualDub and edit, and if you use DirectStream copy for the audio and video when saving you'll still only have an AVI the size of the audio stream plus a few MBs.

By default, I don't think AVISynth files are enabled in ffdshow's decoder configuration (under codecs). You'll probably need to enable that for it to work.

Rather than use MakeAVIS, I use the AVISynth Wrapper Codec. It works in much the same way as MakeAVIS except it installs a right click Explorer option "wrap into AVI". Right click on an AVISynth script, select "wrap into AVI" and it'll create one for you. VirtualDub can open it, add the audio and save that as a new AVI. I've attached it as it's hard to find these days.

Or there's the Avisynth Virtual File System.

If you want to give any of that a shot and you're not familiar with AVIsynth someone will be able to help you to create a basic script for opening video once the type of source file is known. That's all the script needs to do, although you can add filtering to it before wrapping it into an AVI if you want to.

[poisondeathray]

Do you want to do some tests? Don't install anything, and try importing these into vegas . It's hard for me to do "clean out of the box" tests because all my computers have a bunch of codecs and junk installed

They are just 3 clips, 3 frames each, 640x360, YUV 4:2:0 uncompressed, but different fourcc's - I420, IYUV, YV12

Vegas should import I420, IYUV natively (at least I think it should), and it should decode it with studio RGB levels. The YV12, if you have a YV12 decoder installed should get computerRGB treatment

only yv12.avi can't be opened:

Thanks for doing the test

Can you explain why you "need" uncompressed YV12 in the first place ?

There are pros/cons to using frameserving vs. lossless codecs vs. uncompressed

[chazz spacey]

What didn't work, saving the video as an uncompressed AVI in YV12 format or setting the ffdshow decoder to only output RGB? What program are you using to save the video as an uncompressed AVI? I can definitely open an AVI with VirtualDub, set the compressor as the ffdshow video codec and then configure ffdshow to output the correct type. It might help if you describe your pr...

of course i used virtualdub. i did how you showed. uncompressed AVI in YV12 with ffdshow couldn't open in sony vegas.
uum, if i understand right i already created untitled.avs and opened it with virtualdub. the source file is mkv. so i used DirectShow filters(don't understand what it actually is) as it is mkv. and you mean remuxing i guess. But since i hardcode subtitles it needs encoding. i am satisfied with utvideo video codec.

[chazz spacey]

Get utvideo video codec, then you can choose, YUV420 or YUV 422, BT.601 or BT 709, even RGB or RGBA. It is lossless codec, so size is not that insane and Vegas loads that video.

Thank you so much. it is really fast. and sony can handle it. i didn't notice that lossless codecs are so fast. and i think the file size is really matters to speed. cuz uncompressed video at YUV420 file size was 3 times huge than lossles ut codec at YUV420.
by the way UtVideo RGB VCM codec gives error in virtualdub: unable to initialize video compression.

[chazz spacey]

Do you want to do some tests? Don't install anything, and try importing these into vegas . It's hard for me to do "clean out of the box" tests because all my computers have a bunch of codecs and junk installed

They are just 3 clips, 3 frames each, 640x360, YUV 4:2:0 uncompressed, but different fourcc's - I420, IYUV, YV12

Vegas should import I420, IYUV natively (at least I think it should), and it should decode it with studio RGB levels. The YV12, if you have a YV12 decoder installed should get computerRGB treatment

only yv12.avi can't be opened:

Thanks for doing the test

Can you explain why you "need" uncompressed YV12 in the first place ?

There are pros/cons to using frameserving vs. lossless codecs vs. uncompressed

i use virtualdub for hardcode subtitles beacuse sony can't add subtitles. it needs plugin which costs $99.95 and called Vegasaur. so i wanted to save video without quality loss then to edit it in sony vegas. so i just saved them uncompressed without playing with lossless codecs. and i thought they will be slow. but after ut codec it is ok.

[poisondeathray]

Can you explain why you "need" uncompressed YV12 in the first place ?

There are pros/cons to using frameserving vs. lossless codecs vs. uncompressed

i use virtualdub for hardcode subtitles beacuse sony can't add subtitles. it needs plugin which costs $99.95 and called Vegasaur. so i wanted to save video without quality loss then to edit it in sony vegas. so i just saved them uncompressed without playing with lossless codecs. and i thought they will be slow. but after ut codec it is ok.

Yes, UT is awesome

Why don't you hardcode with avisynth ? Or are you editing in vegas with hardsubs in place ?

Another method is render out the subs as a transparent overlay RGBA using avisynth, then import that into vegas. That's even faster, much lower filesize

[chazz spacey]

Why don't you hardcode with avisynth ?

Using subtitle filter for virtualdub is faster than messing around with script.
and i hate scripts!

Or are you editing in vegas with hardsubs in place ?

What you mean?

Another method is render out the subs as a transparent overlay RGBA using avisynth, then import that into vegas. That's even faster, much lower filesize

Wow. That is a very good idea. I must try it.

[poisondeathray]

Or are you editing in vegas with hardsubs in place ?

What you mean?

I mean - Is the reason for using vegas to edit the video, that already has hardsubs on it ? Why are you using vegas ? What are you doing with the subs ? It's difficult to edit the video and keep the timing, unless the subs are hardcoded - Is that what you are doing ? Unless you export the edited video then retime the subs in another program.

Another method is render out the subs as a transparent overlay RGBA using avisynth, then import that into vegas. That's even faster, much lower filesize

Wow. That is a very good idea. I must try it.

Basically you use masksub() , but it requires avisynth and a 2 line script . Encoding will be faster, filesize will be much smaller because a transparent overlay with subs only will compress very well compared to "normal" content

See this
https://forum.videohelp.com/threads/364265-Importing-SRT-subtitles-into-Premiere-Pro-CC...00#post2319000

[hello_hello]

of course i used virtualdub. i did how you showed. uncompressed AVI in YV12 with ffdshow couldn't open in sony vegas.

So "didn't work" meant Vegas couldn't open it, not that ffdshow was outputting RGB when YV12 was selected etc? I wasn't clear on exactly where the problem was.... whether you'd managed to get ffdshow to output uncompressed YUV.

uum, if i understand right i already created untitled.avs and opened it with virtualdub. the source file is mkv. so i used DirectShow filters(don't understand what it actually is) as it is mkv. and you mean remuxing i guess. But since i hardcode subtitles it needs encoding. i am satisfied with utvideo video codec.

So many ways do do things....
If you open the MKV directly with Virtualdub and the ffmpeg input plugin, and you choose "fast recompress" for the video, the output will be uncompressed but should be the same format as the source. ie YV12 in, YV12 out. The same should apply to opening an Avisynth script, as long as the decoder doesn't convert to another format.
It did just occur to me the "normal" and "full" VirtualDub compression modes output RGB by default. I don't know why, or whether you're aware of it, but the output format can be set under the Video/Color Depth menu. Could VirtualDub be doing the converting to RGB? If it is, and you can force the UT Video Codec to compress it as YV12 it might be converting it too.

That's omething else to maybe keep in mind..... I've never used the Ut Video Codec myself, but generally lossless codecs that can compress different types of video can also convert from one format to another. Sometimes you can limit the input and output formats but it's very possible a codec can compress lossless YV12 video and output RGB because that's what a program says it prefers. I'm not saying that's what's happening or it's something you necessarily need to worry about too much, but it's something to keep in mind.

DirectShowSource tends to be a "last resort" decoding method, although if you're just re-encoding a video from start to finish it's usually fine. The main problem is it's not frame accurate so you can't rely on it for accurate seeking/editing while decoding/encoding. One of the most commonly used Avisynth decoding methods for video in MKVs would be FFMS2. You'd open an MKV with FFMS2 instead of DirectShowSource something like this:

LoadPlugin("C:\Program Files\ffms2.dll")
FFVideoSource("E:\video.mkv", threads=1)

That opens just the video. FFAudioSource will open the audio or FFmpegSource2 will open both (you'd just use FFmpegSource2 and wouldn't need FFVideoSource or FFAudioSource). The first time you open an MKV that way FFMS2 will index it which can take anywhere from a few seconds to a few minutes depending on the file size and hard drive speed. Once the index file is created the video will open normally and you should be able to navigate frame accurately.

You can probably add the subtitles to the AVISynth script, wrap the script into an AVI, open the AVI with Vegas and the subtitles should be included with the video as though they're already hard-coded, and you should be able to edit in Vegas normally. There's definitely times when creating a lossless intermediate file is a good idea, or a necessity, but if the sort of thing you're doing at the moment is the sort of thing you'll be doing regularly, frameserving with AVISynth can save a fair bit of time.
There's a utility called AVISynthesizer that can help to automate opening video with Avisynth. It lets you create script templates and adds a shortcut to the Windows SendTo menu. Right click on a video file and select SendTo/Avisynthesizer and it'll open a menu displaying your script templates. Pick one and it creates the script for you. Then if need be I can right click on the script, select "wrap into AVI" and I'm ready to frameserve.

Here's a few examples of basic Avisynthesizer script templates if you're interested in playing with it at some stage (they're templates I use).

Just opening via DirectShow:

#ASYNTHER DirectShowSource
[DirectShowSource("%f")]

DirectShow without audio, frame rate converted to 25fps:

#ASYNTHER 25fps - DirectShowSource - No Audio
[DirectShowSource("%f", audio=false, fps=25, convertfps=true)]

FFMS2, video only, single threaded mode:

#ASYNTHER FFMS2 - Video Only
LoadPlugin("C:\Program Files\ffms2\ffms2.dll")
[FFVideoSource("%f", threads=1)]

If I'm opening video with Avisynth I tend to try to do everything with Avisynth myself. Sometimes for one reason or another you can't, but when it's possible, I do.
An Avisynth based encoder GUI such as MeGUI might be worth a bit of time getting to know. It'll open files, index them for you and create a script for encoding which you can easily edit if need be. MeGUI also has an AVS Cutter under the tools menu which opens a script and lets you add multiple start and end points for encoding using a preview, much like VirtualDub's editing. It can add straight edits or basic fades etc to a script and add the subtitles for encoding. I generally don't leave AviSynth-land unless there's a necessity. A script created by MeGUI including subtitles and edits might look something like this:

LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
FFVideoSource("E:\video.mkv", threads=1)

Spline36Resize(1280,720)

LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\VSFilter.dll")
TextSub("D:\test.srt", 1)

__film = last
__t0 = __film.trim(0, 6513)
__t1 = __film.trim(7215, 9436)
__t2 = __film.trim(9481, 12547)
FadeOut0(__t0, 10, fps=AudioRate(__film)) ++ FadeIO0(__t1, 10, fps=AudioRate(__film)) ++ FadeIn0(__t2, 10, fps=AudioRate(__film))

[chazz spacey]

I mean - Is the reason for using vegas to edit the video, that already has hardsubs on it ? Why are you using vegas ? What are you doing with the subs ? It's difficult to edit the video and keep the timing, unless the subs are hardcoded - Is that what you are doing ? Unless you export the edited video then retime the subs in another program.

nevermind

Basically you use masksub() , but it requires avisynth and a 2 line script . Encoding will be faster, filesize will be much smaller because a transparent overlay with subs only will compress very well compared to "normal" content

See this
https://forum.videohelp.com/threads/364265-Importing-SRT-subtitles-into-Premiere-Pro-CC...00#post2319000

Thank you. i'll try. when you said overlay subtitles some memory flashes happened and then i remembered that video.
https://www.youtube.com/watch?v=pelPO-xNO7U
cuz i was stucked with this problem too. but didn't use it. maybe this time i'll use this software(Subtitle Workshop).

[chazz spacey]

Thank you very much hello_hello for such a guide.
and yes:

So "didn't work" meant Vegas couldn't open it, not that ffdshow was outputting RGB when YV12 was selected

[poisondeathray]

when you said overlay subtitles some memory flashes happened and then i remembered that video.
https://www.youtube.com/watch?v=pelPO-xNO7U
cuz i was stucked with this problem too. but didn't use it. maybe this time i'll use this software(Subtitle Workshop).

Ok, you 're complaining about vegasaur's price? Lemony is used in that video. Lemony is nice but more expensive and doesn't integrate directly with vegas. Moreover, it doesn't support ASS subs. So if you had ASS fancy subs, fonts, styles, animation and effects, it wouldn't work. The free avisynth method supports ASS

[chazz spacey]

when you said overlay subtitles some memory flashes happened and then i remembered that video.
https://www.youtube.com/watch?v=pelPO-xNO7U
cuz i was stucked with this problem too. but didn't use it. maybe this time i'll use this software(Subtitle Workshop).

Ok, you 're complaining about vegasaur's price? Lemony is used in that video. Lemony is nice but more expensive and doesn't integrate directly with vegas. Moreover, it doesn't support ASS subs. So if you had ASS fancy subs, fonts, styles, animation and effects, it wouldn't work. The free avisynth method supports ASS

oh sorry i watched the video here and there. i didn't know that there is 2 software.