Build 99...

[Nick Shaw]

I personally do not think it is a good use of the RED developers' time to write a full EDL parser (or FCP XML parser for that matter). It's not as simple as it might at first seem. I think it would be more useful if REDcineX could export and import its time-line (including deBayer settings and LGG) in its own XML format. Then third parties could write parsers to translate that to and from anything required.

 

[Nils Ruinet]

I personally do not think it is a good use of the RED developers' time to write a full EDL parser (or FCP XML parser for that matter). It's not as simple as it might at first seem. I think it would be more useful if REDcineX could export and import its time-line (including deBayer settings and LGG) in its own XML format. Then third parties could write parsers to translate that to and from anything required.

Yes, I think that's what's gonna happen, and that's fine.

Regarding EDL, it depends if you want it to do a full conform (which indeed can quickly get very complicated), or just use it as a pull list to take all your shots (with or without handles) and add them to the timeline, grade them, render them individually to whatever format you want and do your real conform in FCP, Avid, Premiere or whatever.
But I agree, let's leave that to third parties...

 

[Jean-Charles Wolfarth]

The main advantage of being able to use an EDL within Redcine-X would be a storage space saving. If you're editing a commercial or a music video, that's fine without it, but on a indie feature work, it's always nice to save some time and disks' space.

I'm just afraid that this XML stuff will, again, lead other users than FCP ones to think that they chose the wrong platform to deal with r3d files.

But I agree, the Red developpers should take more time to work on other issues like :

- Quicktime export which crashes on Windows, whatever codec you choose (test done with JPEG2000, Sheer, Animation and Sans)
- TIF exports with the option 8 bits/16 bits to save disk space, again
- Batch conversion with different folder for clips in the timeline
- saving of looks and projects

This way, it would be a great alternative to more expensive solutions.

 

[Jochen Schmidt-Hambrock]

Oh whow, for a few seconds I thought build 99 refered to the camera´s build.
Until the thread opened I speculated what could be the reason for that giant leap ....

Phew, what to do with all that adrenalin?

Jochen

 

[Jannard]

Nigel, this has been reported by a ton of people who have downloaded those R3Ds (from Scarletuser). Rest assured that the problem lies within the files (probably corrupt) and not with RC-X, because the files are also randomly garbled (sometimes they're good, sometimes they're not) in the other RED apps, including the original Redcine. A shame too, because Peter M. spent his own time organizing these files specifically for the SU crowd. Bottom line: it's not a Redcine-X problem.

Where are the corrupt files (and which ones) so I can take them down?

Jim

 

[Mike N]

When will the build 99 for Windows be ready ?

 

[Russ Campbell]

Great work team. Good to see that adjusting FLUT controls now shows up on an external monitor connected to RR. One bug that I noticed today. Switching between look presets doesn't show up on the external monitor. No problems seeing the changes on the laptop screen.

 

[Curtis Stanton]

Where are the corrupt files (and which ones) so I can take them down?

Jim

I had the same or a similar problem with build 96: http://www.reduser.net/forum/showthread.php?p=547650#post547650. I downloaded the r3d files from http://www.scarletuser.com/showthread.php?t=559. I tried uninstalling everything and starting over with new downloads of the app and files. I have tried only two r3d files since then: A001_C009_1125R8_001.R3D works fine and A002_C003_07236R_001.R3D still runs for a few frames before turning into noise and crashing RedCine-X.

 

[Nick Shaw]

I'm just afraid that this XML stuff will, again, lead other users than FCP ones to think that they chose the wrong platform to deal with r3d files.

When I say XML I don't mean FCP XML.

I would expect REDcineX to read and write XML with tags specific to its own timeline and parameters.

A translator would be required to translate into this format from FCP XML, EDL, AAF, ALE or whatever. And indeed a translator for a simple EDL would probably be easiest to write.

But other apps could do more sophisticated things in writing XML for REDcineX. For example an app like Clipfinder could maybe allow you to set deBayer parameters and then send a list of clips to REDcineX with those parameters already set