Miraizon Prores
Mizamook
24 Feb 2017 07:09
Daniel, I agree, but also disagree. I don't really want yet another machine in my house, and I prefer not to have to fly files back and forth between machines if at all possible. I shut down my larger desktop power hog when not using, so it doesn't "network" well ...
In fact, I would prefer not to have to do an intermediate render/transcode at all, so that's why I was hoping that other company would get back to me. So far ... not. I'm not impressed.
Here's the thing: I was making very nice PRHQ files using Footage Studio (where I can fly the final renders back into my original AE project and compare, even after two renders in between, and found very little, if any changes whatsoever, viewed at 400%) It seemed, that AE and the various agencies considered my output files "real" ProRes" ... and I was happy with the outcome ...
Then today, I was doing a favor cloning job for a friend, and wanted to make sure the final render I am gonna give them back was fine, and I noticed that the saturation was UP, the contrast was UP, and the highlights were blown.
Huh?
Oh ... I see in AE it now says "Miraizon ProRes" in the file info pane. I had reinstalled Miraizon several days ago, and it has INFECTED my machine!!!
I uninstalled it, then tried again. Nope. .. same difference. I don't want to see ANY difference, and this shift is HUGE (no magnification necessary), so I cleaned registry, rebooted machine again, re-imported, etc, Nope ...
Checked the uncompressed AVI render against the original ... pixel identical at 400% ... it's not that.
Transferred the AVI to my laptop ... used Acrovid Footage Studio, reimported to the desktop machine... all is well .. project is done.
But my desktop machine still thinks Miraizon is installed. Has messed up my Footage Studio, or, perhaps, has messed up the way AE interprets the PR files .. not sure yet how to figure this out .. working on it .. .although if it was interpretation issue, the file I made on the other machine would not now be IDENTICAL to the original (except for the cloning)
I am hoping updating Footage Studio will fix issue. Fingers crossed. Luckily I have not done too much work on this machine since I installed Mirazon back on ... but I will be checking those files just in case.
What a piece of ...
In fact, I would prefer not to have to do an intermediate render/transcode at all, so that's why I was hoping that other company would get back to me. So far ... not. I'm not impressed.
Here's the thing: I was making very nice PRHQ files using Footage Studio (where I can fly the final renders back into my original AE project and compare, even after two renders in between, and found very little, if any changes whatsoever, viewed at 400%) It seemed, that AE and the various agencies considered my output files "real" ProRes" ... and I was happy with the outcome ...
Then today, I was doing a favor cloning job for a friend, and wanted to make sure the final render I am gonna give them back was fine, and I noticed that the saturation was UP, the contrast was UP, and the highlights were blown.
Huh?
Oh ... I see in AE it now says "Miraizon ProRes" in the file info pane. I had reinstalled Miraizon several days ago, and it has INFECTED my machine!!!
I uninstalled it, then tried again. Nope. .. same difference. I don't want to see ANY difference, and this shift is HUGE (no magnification necessary), so I cleaned registry, rebooted machine again, re-imported, etc, Nope ...
Checked the uncompressed AVI render against the original ... pixel identical at 400% ... it's not that.
Transferred the AVI to my laptop ... used Acrovid Footage Studio, reimported to the desktop machine... all is well .. project is done.
But my desktop machine still thinks Miraizon is installed. Has messed up my Footage Studio, or, perhaps, has messed up the way AE interprets the PR files .. not sure yet how to figure this out .. working on it .. .although if it was interpretation issue, the file I made on the other machine would not now be IDENTICAL to the original (except for the cloning)
I am hoping updating Footage Studio will fix issue. Fingers crossed. Luckily I have not done too much work on this machine since I installed Mirazon back on ... but I will be checking those files just in case.
What a piece of ...