Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Beta REDCINE-X (Build 221) & REDLINE (Build 194)

Sometimes it seems that the histogram is not uptodate... when i changing a setting eg. curve it shows actual values... often after playback...
 
Does this new REDCine X (221) cancel out RocketCine?
So they are one in the same now? Or are we waiting on RocketCine to be released?
 
roryhinds said:
what are the differences between the two, with regard to Rocket performance?
Click to expand...

REDcinex is faster in some cases but about the same in others.
We're doing some speed testing this week to see where things are.

REDcineX also has alot more bug fixes in it and alot more flexibility/features.
 
I found another bug that creates a mirror drive that shows up in the browser if you accidentally hit export with a preset that has an output path to a drive that is not currently mounted. The drive that is preset in the export sequence pops up in the browser and I can not get rid of it. If I connect that drive and open up rcx the drive has a -1 after the name because there already is the ghost mirror drive always mounted in the rcx browser.
 
Michael Epple said:
I found another bug that creates a mirror drive that shows up in the browser if you accidentally hit export with a preset that has an output path to a drive that is not currently mounted. The drive that is preset in the export sequence pops up in the browser and I can not get rid of it. If I connect that drive and open up rcx the drive has a -1 after the name because there already is the ghost mirror drive always mounted in the rcx browser.
Click to expand...

That's not really a bug. OSX mounts the volume under a normal unix path and the export preset is using a normal unix path. There's no concept of a mounted drive with unix paths so when you go to export and the drive is not there, the path is still relevant and the directories get populated as needed.
 
It shows up in the browser because its in the path. With the drive disconnected, in finder, select Go > Go to folder, then enter "/Volumes/" without quotes. Move the folder with your drive name to somewhere else. Now the browser window will be as you expect it, and the drives wont mount with "-1" appended.
 
Michael Epple said:
Yes, but that drive shows up now in the browser window regardless if it is actually connected or not. You're saying that's not a bug?
Click to expand...

Correct. You can mount drives anywhere but OSX mounts them under /Volumes by default. You can make your own folders there also since it's a regular path.

One option is to detect if the folder is actually the same as a mounted volume or not but we make assumptions that may not work for other people (such as some facilities that link to san volumes manually under /Volumes).
 
Build 221 crashes frequently during renders on Snow Leopard 10.6.3
It's pretty stable on Leopard 10.5.8
 
Chris Bouchard said:
Build 221 crashes frequently during renders on Snow Leopard 10.6.3
It's pretty stable on Leopard 10.5.8
Click to expand...

I've had the same issue, but under both Leopard and Snow Leopard. I'm able to process between 40-60GB of R3D footage before the application quits and needs to be restarted. This happens if I submit it all at once, or in multiple batches over the course of a day.

I've also noticed that the REDCINE-X 221 processes our slow-motion 2K clips in two or three times the time it takes to render a 4.5K clip of the same final duration. Am I the only one noticing this?

I don't know if this is a bug or by design, but a burn in always has two lines, even if both fields in one line are selected as "None".

A couple of features that I would wish for:
- A separate grading viewer than the timeline, i.e. the ability to open and grade a file from the bin, rather than needing to pull it into the timeline first
- Custom field for Burn-Ins
- Ability to simultaneously burn in at the top and bottom of the clip
- A magazine rename tool that would fix a formatting error by renumber in the Roll number in the file structure and each clip's metadata, then regenerate the QT Reference files in each folder. Currently I can do this manually or using NameMangler and Clipfinder (or REDRushes), but I can't rename the roll on the metadata, though this is less important to my since our workflow relies wholly on the file names themselves.
- Copy a look directly from one clip to another without having to save a look preset

Other than that the program is working fine here and really accelerating our on-set workflow. Great job RED team and keep it coming!
 
64-bit?

64-bit?

Deanan,

Is there any plan to move this to 64-bit structure? I think that being able to use more than 4 GB of RAM will help us a lot. I have 16 GB installed, and it is a shame it is not using more...

Also, is it CPU centric, or is it taking advantage of the GPU. I recently installed GTX 285 (Mac) with CUDA activated to take advantage of the PP CS5 Mercury Engine (I love it!!!) and I think it will be great if such power is unleashed...

Regards,
 
sbilodeau said:
- A separate grading viewer than the timeline, i.e. the ability to open and grade a file from the bin, rather than needing to pull it into the timeline first
Click to expand...

Unless I've misunderstood you, this has been possible for some time. Just drag a clip from the bin to the viewer, grade away, happy days :)

This build has been pretty stable for me, except when saving TIFF stills- it seems to crash about every fourth or fifth image. Saves the file OK, but the app freezes.
 
Can anyone help me understand exactly what RedLine is, and what it does for me. Also, I'm wondering if this along with the new Recode QT codec is going to help along programs such as Clipfinder and Red Rushes to have the new RedColor and RedGamma
 
You must log in or register to reply here.
Back
Top