View Single Post
Old 4th July 2015, 00:53   #376  |  Link
kolak
Registered User
 
Join Date: Nov 2004
Location: Poland
Posts: 2,843
You are getting closer and more and more confirms that problem is integration between Cinegy and codecs (not tested/optimised).

Vdub has no problems at all with magicyuv or utvideo. If you set correct pixel format in Vdub settings than it will talk to both codecs through YUY2 or even v210. If you see RGB it means that you have wrong (most likeky default) settings. If your source is magicyuv (encoded from v210) and you see black/green picture in Vdub than you have wrong setting in decompression format (magicyuv has no internal conversion between 10 and 8bit). It has to be set to v210.
Both magicyuv and utvideo work very well in Edius NLE if files were encoded as 422 YUV. This is because Edius engine 'likes' YUY2 pixel format. Many software will ask codec to provide RGB, so you end up with conversion.

Magicyuv 25p 4K playback through v210 pixel format directly to madVR renderer in mediaplayer classic was using <20% of 6 cores 3.2 GHz E5 Xeon (HP Z420). SD files play at tiny CPU load on such a machine. Key point is to avoid any pixel format conversion. Ideally in pro solutions you want direct integration through codec SDK, not over WIN system vfw etc.

UYVY and YUY2 are “the same“ and conversion between them is trivial, so even if you see this, it's 100% lossless and fast. There is NO picture quality difference whatsoever, so if you see leess sharp footage than there are some serious problems with decoding chain.

As I said- write to Cinegy, so maybe they can debug and add proper support for magicyuv/utvideo.
If you want to test pure speed of the codec use tool provided by Ignus2 on his website. Most NLEs etc. will give totally inaccurate results.

Last edited by kolak; 4th July 2015 at 01:13.
kolak is offline   Reply With Quote