I've successfully installed RedCine 3.12 for XP in the XP virtual machines using VMWare Fusion on both my new MacBook Pro and my new Mac Pro. But RedCine doesn't work.
Here's what happens. The install is successful. When I launch RedCine, I get the splash/launch screen. Then the app opens full screen and all of the graphical user interface is blurred/smeared/distorted. See this screenshot
Has anyone else experienced this? Lucus at Assimilate or Red: any thoughts on how to fix this bug?
FYI, VMWare Fusion XP on Mac is super stable and runs thousands of PC apps without any problem.
In case anyone is wondering why I don't just run RedCine for Mac, there are 2 reasons:
a)I wanted to test outputting to Cineform 444 (4K 12-bit RGB)
b)RedCine for Mac is unacceptably buggy on the over half dozen Macs I've tested it on. Specifically, if I have over 5 clips on the RedCine (for Mac) timeline and render (to ProRes HQ) I get the "frozen frame" bug over 70% of the time. This is unacceptable and wastes countless hours of my time (and editors who work with me).
If anyone has experienced the same problem, I'd love to know. Or even better, if you have a tip or workaround, I would be most grateful! Thanks.
-Dan
Here's what happens. The install is successful. When I launch RedCine, I get the splash/launch screen. Then the app opens full screen and all of the graphical user interface is blurred/smeared/distorted. See this screenshot
Has anyone else experienced this? Lucus at Assimilate or Red: any thoughts on how to fix this bug?
FYI, VMWare Fusion XP on Mac is super stable and runs thousands of PC apps without any problem.
In case anyone is wondering why I don't just run RedCine for Mac, there are 2 reasons:
a)I wanted to test outputting to Cineform 444 (4K 12-bit RGB)
b)RedCine for Mac is unacceptably buggy on the over half dozen Macs I've tested it on. Specifically, if I have over 5 clips on the RedCine (for Mac) timeline and render (to ProRes HQ) I get the "frozen frame" bug over 70% of the time. This is unacceptable and wastes countless hours of my time (and editors who work with me).
If anyone has experienced the same problem, I'd love to know. Or even better, if you have a tip or workaround, I would be most grateful! Thanks.
-Dan