V-dub will handle the conversion from full-range YUV automatically - there's no need for explicit conversion. Use the FFmpeg input driver () it will preserve Fraps' native YV12, and does a better job of color resampling for sharper color details. All the loss occurs when you convert to YUV and subsample to 4:2:0. It's the same as the dmfs RGB output from vegas - there is no loss at that stage. 8 red, 8 blue, 8 green, + 8 "dummy" alpha. Would it make more sense to send output to VirtualDub through FS in 32b RGB or the final result won't be very different? My main concern primarily is to reduce colorspace conversion as mcuh as possible. My main concern is case with frameserver. Nothing can be done here, fine detail loss quite noticeable even with lossess codes (Lagarith, Huff, x264 lossess mode) but whatever. In case with direct access to file there isn't that much to do, Virtual Dub does conversion to 32b RGB in "full processing" and then later encoder does another conversion into YUV420 again. In order to receive proper colorspace and color compatibility in final AVC1 MP4 video, I either use x264vfw in VirtualDub's full processing mode with the option "Convert to YUV 4:2:0" in the encoder itself (+ specify the matrix), or use "convert format" and "alias format" when it comes to External Filters. Vegas with DebugMode FrameServer, RGB24/32 Direct read from videofiles recorded by FRAPS (FPS1,YUV12, rec 709, full range ()) or DxTory (xtor, YUV24|CompressV3)ΔΆ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |