RELEASED: REDCINE-X (Build 256) & REDline (Build 256) - BETA

[David Ibbitson]

Feature Request: It would be helpful if the Batch Monitor would display progress for creation of QT wrappers the way it does transcodes.

It's in for the next release. Additionally, the creation of QT wrappers will be able to run simultaneously with other exports.

 

[Rob Lohman]

Can anyone confirm or deny that Redcine-X works with ALL camera builds, even builds going way back to 17, 15, etc... or is it just for builds 30 and beyond?

I am seeing some odd transcodes using the same settings between Redcine and Redcine-X... the colorspaces do not look the same. Using CAMRGB/REDLOG.

Yes, it works with all footage.

It will look different because it uses new and improved color science

 

[Andrew Hunter]

Hey,

I'm trying to figure out if this is user error or in fact a bug. When I try any export to quicktime anything that has a crop applied to it I get only black frames.

For clarity, my encoder settings are:

Quicktime
ProRes 422 Proxy
FPS: 23.98
Gamma: Automatic

This doesn't happen when using jpegs for example, I get what I would expect a 1920x1080 picture with the 2.4:1 image matted inside.

Thoughts?

EDIT: If I select No Crop in the framing presets, the quicktime export works as expected.

 

[Brandon Kraemer]

When exporting to sub-folders for each clip, from a timeline imported from a LUA script, It only creates a folder for every .R3D clip, but not for every edit event. In other words I might have 10 .R3D files, but 30 edits that use some clips multiple times, from different portions of the raw. I want to have a sub folder for each clip instead of having a folder that has multiple clips in it and a suffix on the end of the file name that denotes it's another version of that same clip.

 

[Jean Déraps]

It was fixed.

If you're seeing it please send steps to recreate it to redcinex@red.com.

I'm definitely still getting it on build 256. I emailed the above address, but didn't really know what to answer...there are no steps to recreate it. When I use the eyedropper, it either works properly (which is seldom the case!) or assigns an erroneous color temperature value of 1700K. That's it. Any suggestions as to what is happening?

 

[Deanan]

I'm definitely still getting it on build 256. I emailed the above address, but didn't really know what to answer...there are no steps to recreate it. When I use the eyedropper, it either works properly (which is seldom the case!) or assigns an erroneous color temperature value of 1700K. That's it. Any suggestions as to what is happening?

Can you turn on verbose logging and then make it happen and send the logs?

 

[David Battistella]

I'm definitely still getting it on build 256. I emailed the above address, but didn't really know what to answer...there are no steps to recreate it. When I use the eyedropper, it either works properly (which is seldom the case!) or assigns an erroneous color temperature value of 1700K. That's it. Any suggestions as to what is happening?

I have noticed that the only time you get the 1700K error with the eydropper is if you are trying to affect any clip AFTER the FIRST clip in the timeline. it NEVER happens to the first clip in the timeline just any clip thereafter.


David

 

[Andrae Palmer]

Can a field be added to the batch text file to report when the job was started? Also the duration of the total batched files.

 

[Oliver Koeppel]

Thanks to Matt at Red for responding...
Problem solved.
I had two pref files there at /users/username/Library/Preferences/com.red.RedCineX.plist-

RedCineX.plist
and
REDCINEX.plist

Had to drag both to the trash.

Thanks again.

Does anybody knows how to find the same in windows 7? Where could I find the user prefs?

 

[Mark B.]

Here's another bug... after splitting a clip in the timeline, the right-side of the clip is moved to the end of the time line. This can be seen if you have two clips, and then split the first one.