Rick Griffo wrote:In the end, I believe Miraizon is also nothing but ffmpeg no?
I thought so but no - it seems not. As I mentioned above, there's some differences - depending on what applications you're using, the Miraizon codec has different gamma properties/levels to both Apple ProRes and ffmpeg (which in general is pretty darn close to Apple ProRes) - it's easy enough to compare them with some test patterns and gradients.
Since you haven't experienced any issues with v1 either, I decided to give it another shot just to check I wasn't going completely crazy - and sure enough, the moment I installed them, Fusion started importing ProRes and DNxHD in 8-bit rather than 16. Changing the depth in Fusion did nothing and it was obvious from the waveforms that the Miraizon codec was handing 8-bit footage over to Fusion.
Which is something else that bothered me - *all* ProRes/DNxHD decoding (except perhaps Resolve's) is done by the Miraizon codec once you've installed it and frankly, I just don't trust it any more.
I'm glad it's working well for you though - but as I said above, I can't afford to be second-guessing what Miraizon's software is doing and I don't want to have to keep double-checking and running tests to ensure my video isn't getting squashed into 8-bit whilst I'm trying to get work done.
Rick Griffo wrote:As I use PR444 a lot as a render codec, I don't really see a use of ClipToolz and others, as I only can convert already transcoded data :/
Yes - 4444's nice - I encode exr's to it via Snow Leopard which I've got running in a VM - it'd be nice to be able to encode it natively but unfortunately ffmpeg's implementation of 4444 is broken - it can't encode anything above 10-bit YUV and its data-rates are screwed. It's a bit of a pain to use a VM for transcoding that stuff but it's better than nothing
Hope you continue to get good use out of your codecs and I'm still hoping Miraizon get bought out so that someone else picks up development (maybe they'll fix my bugs
)