RELEASED: Beta REDCINE-X (Build 194)

[Brent@RED]

We have released the following on www.red.com/support today:

* Beta REDCINE-X, Build 194 for Mac OSX : http://www.red.com/support/release_history/2196541#189

* Beta REDCINE-X, Build 194 for Windows : http://www.red.com/support/release_history/2196541#188

Please see release notes and/or readme files for further details.

ALWAYS READ ALL INSTRUCTIONS CONTAINED IN THE DOWNLOADED INSTALLATION FILES BEFORE PROCEEDING.

WARNING: AS THESE ARE BETA BUILDS, THEY ARE RECOMMENDED FOR PREVIEW AND TESTING PURPOSES ONLY. THEY ARE NOT RECOMMENDED FOR USE ON COMMERCIAL PRODUCTIONS.

If you have any questions or feedback, please contact RED Technical Support at www.red.com/support.

Thanks, BC

[Martin Weiss]

Thanks for all the hard work.

[Colin Hubick]

echo

[Bill Goehring]

REDCINE-X 194 crashes on opening. Version 104 opens and operates fine.

[Jonas Rejman]

its faaaasteeeeeerrrr !!!! :-D thnx

[Andrae Palmer]

Doesn't seem as crash prone as Build 183... testing with RED Rocket on a dual 30" Apple setup. Now can drag the image window around in full 4k playback without worrying about the system crashing.

[Bill Goehring]

I couldn't open 183 either.

Mac OSX 10.6.3
MacPro 2x 2.8 GHz Quad-Core Intel Xeon
Nvidia GeForce 8800 GT

[Deanan]

REDCINE-X 194 crashes on opening. Version 104 opens and operates fine.

Windows or Mac?
Which OS?
Which graphics card?

Big changes between 104 and 194 are we're doing alot more intensive opengl.

Edit: see you reply now.

Are you running the app on a case sensitive filesystem?
Can you send the crash report and logs to redcinex@red.com

[Bill Goehring]

crash report sent to redcinex@red.com

[Bill Goehring]

i'm not sure how to determine if my file system is case sensitive
and not sure how to find the log

[Deanan]

i'm not sure how to determine if my file system is case sensitive
and not sure how to find the log

The logs are in userfolder/library/application support/red/redcinex/logs.

[Bill Goehring]

crash report, logs and system info sent to redcinex@red.com

[Chris Reynolds]

Coming along nicely! One thing I am having problems with is it seems that the default header information in the DPXs is set to 24fps. Is there anyway of changing that?

Cheers, Chris

[Sidney L. Plaut]

.crash sensitive = windows?:)

[Luca Immesi]

It seems it has been improved in speed.

[Elsie N]

.crash sensitive = windows?:)
Not according to post #7

[Julian Krause]

Hi there,

I tested the new erx export briefly today and it appears that it is very slow compared to an ordinary dpx export. Since I have no experience with erx so far, I just wonder whether that is a known issue.

And does anyone know, whether RR is supporting the export to one of these fileformats?

Cheers!

[Nikolay Spasov]

Did the Wave Panel works with Beta REDCINE-X (Build 194) for Windows ?

[Matt Mascheri]

Props to the RED teams for all the updates.

One question though... In RedCine I was able to output jpeg frames, any chance that could be implemented in a future build?

Thanks

Matt

[Andrae Palmer]

Is it possible to collapse the timeline in redcine-x? Sometimes I would like to view all the timeline in one window.

[Deanan]

Hi there,

I tested the new erx export briefly today and it appears that it is very slow compared to an ordinary dpx export. Since I have no experience with erx so far, I just wonder whether that is a known issue.

And does anyone know, whether RR is supporting the export to one of these fileformats?

Cheers!

exr is going to be a bigger file and it also needs to go through an extra pixel conversion so it's going to be slower. We're using the EXR library conversion so we haven't optimized for speed yet.

We're also planning on improving the exr output as it's currently limited to 1.0 at the top end because of limitations in how things are processed. That will change sometime in the next month.

[Deanan]

Did the Wave Panel works with Beta REDCINE-X (Build 194) for Windows ?

Not yet.

[Deanan]

Is it possible to collapse the timeline in redcine-x? Sometimes I would like to view all the timeline in one window.

It can to a degree but we have more work to do on the timeline to improve that and other areas.

[Deanan]

Props to the RED teams for all the updates.

One question though... In RedCine I was able to output jpeg frames, any chance that could be implemented in a future build?

Thanks

Matt

Yes, it's on the todo list.

[Petri Teittinen]

Whoa; b194 did something I haven't seen on any previous versions: a BSOD on Windows 7 64-bit!

I had placed some clips in the bin with the previous version of RC-X, and they were shown properly in the bin with b194. On the first run of b194 double-clicking any of the clips crashed the app. On second run double-clicking a clip caused a BSOD.

Logs attached.

[Julian Krause]

exr is going to be a bigger file and it also needs to go through an extra pixel conversion so it's going to be slower. We're using the EXR library conversion so we haven't optimized for speed yet.

We're also planning on improving the exr output as it's currently limited to 1.0 at the top end because of limitations in how things are processed. That will change sometime in the next month.

Thanks for the explanation :)

[Sean Carley]

I'm finding that the new build locks up when I try to export more than one R3D file in the render queue (trying to export to QuickTime). It works flawlessly when I select and export the clips one at a time. But with more than one selected for render, it just freezes and won't budge past 0% on the first clip. It won't let me abort the export at the point either--it's just seemingly locked up. I can close the program, however.

Log report sent.

[Deanan]

Whoa; b194 did something I haven't seen on any previous versions: a BSOD on Windows 7 64-bit!

I had placed some clips in the bin with the previous version of RC-X, and they were shown properly in the bin with b194. On the first run of b194 double-clicking any of the clips crashed the app. On second run double-clicking a clip caused a BSOD.

Logs attached.

Can you please email redcinex at red . com?
We'd like to figure out what might be triggering this.

[Luis Otero]

On the improvements list, the folowing statement is made: "A lockup when grading or playing back while exporting has been fixed."

Does it mean that the intention was to allow the rendering to continue, even if we try to go back and even touch the timeline? If so, whenever I try to go to the timeline while rendering, automatically the render status changes to "Paused".

Please clarify,

[Deanan]

On the improvements list, the folowing statement is made: "A lockup when grading or playing back while exporting has been fixed."

Does it mean that the intention was to allow the rendering to continue, even if we try to go back and even touch the timeline? If so, whenever I try to go to the timeline while rendering, automatically the render status changes to "Paused".

Please clarify,

The intention has always been to pause rendering while grading so usability is maintained. Otherwise, grading would be grind to a slow crawl if rendering in the background.

[Tom Gleeson]

Build 194 crashes on start up. Log attached but just says
"REDCine-X Build 194 Starting...
Using R3DSDK 3.0"

Build 104 ran with few hassles. Any thoughts on solving the issue?

Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
OS 10.6.3

[Luis Otero]

The intention has always been to pause rendering while grading so usability is maintained. Otherwise, grading would be grind to a slow crawl if rendering in the background.


Understood for grading (I would stop rendering if I am grading since there is no point to render if you are going to make changes anyways), but for just take a look of clips further in the timeline? This is really a nice-to-have feature. FCP partially let you move the timeline, but not to the extent of moving the line position, so it would be nice if you can offer such feature.

On other observations:

1. The system is not consistent on saving the grading parameters; I would say, 25% of the times most of the parameters, specially the LGG wheels, they go to the neutral position, but the grading is maintained. As soon as you dare to touch ANY parameter, every aspect of the grading goes cu-cu big time. I am using the software to do the primary CC for a feature, that has close to 100 scenes with quite a few clips per scene, so this is very prominent for me. I know that we are advised not to use it for commercial projects, but most of us are using it anyways... It is so great and works with the Wave!!! But anyways, what does the indicated statement means?

2. For scenes with 3-5 clips, the system, most times than not, do not show the time reference ruler within the timeline area.

3. The system, most times than not, do not allow me to reposition the line within the timeline by clicking on the desired spot as we were able to use it on the previous build. I need to drag the line, or use the Wave jump buttons, to move it to the desired spot.

4. System crashes very often when rendering is commanded (I already sent you the log).

Now a couple of questions:

1. I have asked before, but never have received any answer: Is it within Red plans to improve Redcine-X so that it can render files at the same quality level than we used to get (or still can get) with Redcine Build 20? Why are they remarkable different? Any technical explanation?

2. I have not tried it with this version, so you do not need to necessarily answer, unless there is a trick that you can provide: Can I still close the project while rendering, then open a new one, ad another render, etc., etc.? If so, is there an advised limit on the number of renders we should put in-que? I think the maximum that I successfully did was four...

3. Somebody once asked Jim if the UI can be modified to have the kind of look that "Aperture" offers. His response was more or less: "What about if we do it better?", or something to that effect. I know that this is considered a "cosmetic" issue, but after using it heavyly, I still feel that there is so much space dedicated to borders and style, that we can use such "real-state" to optimize and facilitate the functions you currently offer (or will add in the future).

Thanks for this great tool!! :emote_happyhappy:

[Kevin Wild]

See the other thread...I think possibly audio channels are being "summed" so that they are combined to both channels.

[Brian Broz]

I assume no Euphonix MC Color compatibility yet?
I know you guys are busy...just deciding whether to order one yet:-)

BBroz

[Deanan]

Build 194 crashes on start up. Log attached but just says
"REDCine-X Build 194 Starting...
Using R3DSDK 3.0"

Build 104 ran with few hassles. Any thoughts on solving the issue?

Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
OS 10.6.3

What graphics card do you have?

[Tom Gleeson]

What graphics card do you have?


The ATI Radeon HD 2600 is installed

[Deanan]

The ATI Radeon HD 2600 is installed

Can you send an email the full crash report to redcinex at red . com?

[Jonathan Cooper]

On the release updates it say this. Changes have been made to the OpenGL usage which should allow some lower end cards to work. Is there a list of cards that it will work with While some of us are saving for a red rocket.