![]() |
|
|
#6 |
|
Member
Join Date: Jul 2008
Posts: 48
|
Sorry, I've been overseas for the last several months and have just come back to find RED Rushes no longer supported, which is a bit of a shame. Don't get me wrong, REDCINE-X looks great and has a lot of potential, but I was just really fond of the simple and effective RED Rushes workflow. I'm curious...
I haven't been able to find an post here that says categorically when and why RED Rushes is no longer supported, and what exactly happens if you try and transcode build 30 R3Ds in the older RED Rushes (even if you have the latest version of REDline). I know there is some metadata being lost in translation, but I'm not sure of the specifics. Any ideas? Does REDCINE-X use REDline to handle all the transcoding? I'm presuming it does, as when you download REDCINE-X it comes with REDline. As RED Rushes is just an interface on top of REDline, would it be possible to update RED Rushes to support the new metadata that is currently causing it to output wrong? If RED doesn't want to do it, any chance RED could Open Source RED Rushes so that the community could make the necessary changes? I know most (if not everyone) has given up on RED Rushes and moved along to the bigger and better REDCINE-X, but already I've heard a lot of people saying that REDCINE-X is crashing a fair amount of times, and is not overly stable in a production environment yet - whereas RED Rushes was rock solid. Obviously I need to do some more testing myself, and present the facts here for the developers to see, but my gut feeling says that it would be great to have the option of using the powerful REDCINE-X or the less pretty, but just as practical RED Rushes. Any information or clarification you could provide would be greatly appreciated! Thanks in advance... Best Regards, Chris! |
|
|
|
| Thread Tools | |
| Display Modes | |
|
|