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

[chris layhe]

But it would be so nice to have a scope or two as well as the waveform!

But it would be so nice to have a scope or two as well as the waveform!

Great release guys, but is there any chance of getting a scope or two on the output as well as the histogram? It just makes life easier and correcting faster...

Chris

 

[Adi Lima]

REDline 256

REDline 256

I've been using REDline to convert most of R3D files, but after build 252 I got these 3 confusing lines of output like the following:

RedImageExporterToExternal:reProcessing complete and successful.
redexport: export_server_wait: received error message from the client. 0
RedImageExporterToExternal:rocess failed to wait for frame 0
​

But then I realize that the new version of REDline takes -o argument consisting the path to the output file, not just the filename. Not only that, this argument is also a MUST, otherwise the RedExporter will just stop.

 

[Luis Otero]

My "Look presets" are not sorted alphabetically as it was published. Is there any step I need to do to to force them to be in such order?

Thanks!

 

[Kaku Ito]

Now I'm heavily working on converting using RED ROCKET and the REDCINE-X 256 but too many crashes and it hasn't been so stable with all of the builds on REDCINE-X, so I'm getting little tired. ROCKETcine-X was so reliable so I'm going back there for now. But everything looks promising in REDCINE-X, so good luck to the RED team and hope it gets stable soon.

 

[Kaku Ito]

Would I be lacking any of the color science features if I go back to older combination with ROCKETcine-X compatible software/firmware?

 

[Panos Bournias]

Redline

Redline

Where can I find the commands for red line in order to try and use it?
Thanks
Panos

 

[Rob Lohman]

Now I'm heavily working on converting using RED ROCKET and the REDCINE-X 256 but too many crashes and it hasn't been so stable with all of the builds on REDCINE-X, so I'm getting little tired. ROCKETcine-X was so reliable so I'm going back there for now. But everything looks promising in REDCINE-X, so good luck to the RED team and hope it gets stable soon.

It would greatly help us if you can email redcine-x logs and any crash reports your system generates to us: redcinex (at) red.com

From what we can tell it's been very stable, so it would be good to find out why it's crashing for you so we can fix it.

Thanks,

Rob

 

[Kaku Ito]

Okay Rob, I won't give up just for you, because you show so much dedication to help us.

It might be totally just a wild guess, but it might have been the RCX file in the particular R3D footage that was causing the crash. I will do some tests and give you the report when it happens again.

 

[Chris Burg]

Can someone tell me what the REDline install package is all about…
What is it good for and how do I get it installed?

 

[Kaku Ito]

The current version comes with the installer, so just use the installer. REDLINE features can be used with command line, or used in the application that utilizes the REDLINE (like Monkey Extract or Clipfinder rendering).

 

[Chris Burg]

Thanks…

I´m on windows – so no Clipfinder or Monkey Extract

 

[Kaku Ito]

I think REDCINE-X works based on REDLINE that is why they're always released together. And R3D Manager's rendering, too.

 

[Alexander Alexandrov]

i have a question / feature request on the audio sync & filetype.
i'm using sound devices 702T recorder (very common in the industry).
i understand that RCX only allows sync with BWF audio files and not WAV. i tried everything to make the recorder output bwf and with no luck finally emailed S.D. support. Here's the reply i got: "Hi Alexander,
You aren't doing anything wrong. you want to choose "WAV" under "REC: File Type". This will create AES-31 broadcast WAV files. In the past, we used the file extension of ".bwf" for these files, but have since abandoned that practice in favor of the more standard ".wav" file extension. These are still broadcast WAV files with all of the compliant metadata. The only difference is the spelling of the file extension.".

i know i could just rename the extension it seems, but still seems that wav should be the sound standard or at least an option?

and number 2 request is an option to easily change TC in R3D if possible, like one can do in FCP on QT files for easier audio sync by tc for cases when camera TC doesnt match the visual slate TC.

 

[Brandon Kraemer]

Why is this program still way slower than Redcine when transcoding the same shots? We are trying to streamline workflow that covers both MX and pre-MX footage, but the speed of the transcodes with Redcine-X is a killer.

*Also... unless I am missing something, the fact that you can't preview framing controls in the viewer is a feature I miss terribly from redcine. You are flying blind.

The lack of named presets (4k HD, 4k 16:9, 3K 2:1, etc...) in Output Resolution makes that step difficult too if you haven't memorized all the resolutions by their numerical values.

 

[Mark B.]

Rocket or no Rocket? Windows or Mac? Playback on computer monitor, playback through Rocket to external monitor or export?

Regarding the sound sync issue...
No Rocket, Win7 (x64) on i7 processor, playback on single-screen computer monitor, viewing directly in Redcine-x (I have not tested exported footage yet).

 

[Brandon Kraemer]

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.

 

[Brandon Kraemer]

OK, we just got screwed by the timecode issue. We had issues with the camera generated proxies right about the time we updated our codecs to support MX sensor. Seems like non-MX camera proxies do not like the new codec, and this is frustrating, it causes the proxies to continuously look for the data in the .R3D files. A large project took over 30 minutes to open because of this. The solution was to recreate proxies, and this happened with the build(s) that had the time code issue.

So we went to recreate all the proxies again, with build 256, and then relink the files. We tested a few clips and it worked with out causing any issues with edited sequences.

However, when trying to bin up a bunch of clips to create new proxies, Redcine-X crashes. It's also really slow to populate the browser with the clips that correspond to the selected directory. *You have to scroll the window up and down a few times to get it to see all the clips, even if you wait for it to load the clips. Select all (control-a) will not select all the clips in that mag until they are also loaded in the list, which requires scrolling. The beach ball will appear as you scroll to find the clips not showing up.

**It's crashing very frequently just using this browser feature to load clips into the bin.

bk

 

[Brandon Kraemer]

Export Issue

Export Issue

One other thing I've noticed... I am using a LUA script that loads clips onto the timeline for doing select transcoding. I can apply a look preset to all clips in the timeline using that tool, no problem.

But in my export settings, I try the same thing, I set QT movie as my type and as export using clip name to selected folder, then I set a folder location. If I export using that setting Timeline All Clips... it asks me for what file name I want the clips to be, but if I export Timeline Selected Clips, and I select all the clips, it does what I told it to in the settings, export using clip name to the selected folder.

Not sure why it doesn't work with Timeline All Clips, but it behaves unexpectedly.

 

[Mark Pugh]

Redcine Builds 252 and 256 freeze with a Beachball a couple of seconds after opening on my MacBook Pro.

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.

 

[Brandon Kraemer]

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