Welcome to our community

Be a part of something great, join today!

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 :)

NAB13- REDCINE-X Professional Build 18 Alpha

Wrote this in another thread:

Jarred how about a simple, easy feature for Redcine-X...
One-button searching for all R3ds in a given directory folder and sub-folders (eg today's shots) that are varispeed, and placing them automatically in a bin for export.
That way Redcine could quickly mop up the job that the proxy module ( and Meizler) can't handle.
5 second's labor, job done.
 
Jordi Figueras said:
Once this is out of Alpha, will it be available for OSX 10.6 or is it only going to be compatible with 10.7?
Click to expand...

For OpenCL support you really want something newer (Mountain Lion would be my suggestion)
 
Tommaso Alvisi said:
great!!!!
is the ultrastudio mini monitor supported?!?!
SDI only or HDMI too?
thanks!!!
Click to expand...

We believe that should work but we've not had a chance to try it yet
 
I have problem with Export from REDCINE-X via REDLine

In Export preset -> Options -> Use REDLine (software only) I have checked
In Preferences -> Transcode -> Max Simultaneous Export Jobs (REDLine, Snapshots) I have value 2

Export is finishing very quickly without exported files. I'm exporting to ProRes 422

Same configuration is working fine with version 17.26547 on Mac OS X 10.8.3 installed in /Applications/REDCINE-X Professional

Version 18 is installed in /Applications
 
Laco Zamba said:
I have problem with Export from REDCINE-X via REDLine

In Export preset -> Options -> Use REDLine (software only) I have checked
In Preferences -> Transcode -> Max Simultaneous Export Jobs (REDLine, Snapshots) I have value 2

Export is finishing very quickly without exported files. I'm exporting to ProRes 422

Same configuration is working fine with version 17.26547 on Mac OS X 10.8.3 installed in /Applications/REDCINE-X Professional

Version 18 is installed in /Applications
Click to expand...

Thank you! I am able to reproduce the issue here.
 
Tim Sutherland said:
Ok, thanks. I've been running the 2 rockets in the Cubix for quite a while, seems odd that it doesn't work anymore in the alpha when not using the decklink. How it gets cleared up soon, saves a lot of input switching for me on my monitor.

Tim
Click to expand...

Tim,

I've been looking at your issue all morning. I've got a Mac Pro 4,1 running OSX 10.7.5 with a Cubix attached and 2 RED rockets inside. I've tried running SDI Output on both Rockets, on a DeckLink Extreme 3D+ and a DeckLink 4K Extreme and am unable to recreate your issue here.

Could you please turn on verbose logging and send your log files in to redcinex at red dot com? Maybe that will shed some light on things.

Also, what rocket driver and firmware versions are you using? What version of the Blackmagic Desktop Video are you running? It should be in the title in the system preferences page. We built the DeckLink support around version 9.7, so it's possible there's an issue with older versions of Desktop Video.
 
"Added: OpenCL processing for Effects. Requires an OpenCL 1.1 driver and a card with 768MB or more memory onboard."

Well, so much for the most expensive Mac Book Pro ever made.... 512MB!

What about a "passes" mode? Or quad processing? Or is that too old Video Toaster thinking? :)
 
Glen David Miller said:
"Added: OpenCL processing for Effects. Requires an OpenCL 1.1 driver and a card with 768MB or more memory onboard."

Well, so much for the most expensive Mac Book Pro ever made.... 512MB!

What about a "passes" mode? Or quad processing? Or is that too old Video Toaster thinking? :)
Click to expand...

The current generation of Mac Book Pro has 1gb of video ram.

Unfortunately OpenCl is not a magic bullet that makes everything faster, it requires a hefty graphics card to be able to process as fast as your CPU the graphics cards in older laptops are very crippled due to extremely low core counts and memory compared to their desktop counterparts.

On the other hand we do not disable your ability to attempt to use lower end cards currently, we just warn you when you do.

RCX will also continue to run with OpenCl disabled.
 
Grant Limberg said:
Tim,

I've been looking at your issue all morning. I've got a Mac Pro 4,1 running OSX 10.7.5 with a Cubix attached and 2 RED rockets inside. I've tried running SDI Output on both Rockets, on a DeckLink Extreme 3D+ and a DeckLink 4K Extreme and am unable to recreate your issue here.

Could you please turn on verbose logging and send your log files in to redcinex at red dot com? Maybe that will shed some light on things.

Also, what rocket driver and firmware versions are you using? What version of the Blackmagic Desktop Video are you running? It should be in the title in the system preferences page. We built the DeckLink support around version 9.7, so it's possible there's an issue with older versions of Desktop Video.
Click to expand...

I just shipped my cart to the next job but I think I halve it figured out. I didn't want to override my current install so I just ran it off the disk image, which maybe doesn't let the app look back at drivers correctly. So I bet if I drag it to the desktop it might work. I'll test it out on Tuesday when I get to where my cart is and let you know.

Tim
 
This may be a silly question, but is there any reason it would be preferable to monitor RCX through a BlackMagic or AJA card instead of the HD-SDI out of the RedRocket? Or is it simply the advantage of having more HD-SDI outs for multiple monitors; or as a gift to those users without Rockets?
 
Just checked out the second new build on my Mac. Enabling Video Out kept immediately crashing the app until I went into the preferences and changed the output from the Rocket to the Decklink card. Output seemed to work great. Footage, however, was buffering really slow. My 8 bay SAS RAID is reading at 680MB/s and even at 1/8 debayer, footage was buffering to slow to play real time.
 
Christopher Barrett said:
Just checked out the second new build on my Mac. Enabling Video Out kept immediately crashing the app until I went into the preferences and changed the output from the Rocket to the Decklink card. Output seemed to work great. Footage, however, was buffering really slow. My 8 bay SAS RAID is reading at 680MB/s and even at 1/8 debayer, footage was buffering to slow to play real time.
Click to expand...

Christopher, can you send me a system profile and a saved report from this RCX to (redcinex at red dot com). You should be able to get much faster playback than that.
 
All sorted out, Matthew. I went back through the Preferences and the RAM allowance was set to 2GB. I took that up to 30GB. Also, my RRocket was disabled. Re-enabled it and I have Full Debayer, Real Time playback of 5k FF to my Flanders Monitor. Killer!
 
Paul Kalbach said:
This may be a silly question, but is there any reason it would be preferable to monitor RCX through a BlackMagic or AJA card instead of the HD-SDI out of the RedRocket? Or is it simply the advantage of having more HD-SDI outs for multiple monitors; or as a gift to those users without Rockets?
Click to expand...

The main advantage is that with REDRocket, it's not currently possible to send out post-effects such as Alchemy, Film Look, Unsharp Mask through the Rockets SDI output ports. With AJA/Blackmagic cards, all of those effects are piped through to the SDI monitor as well.
 
And if you have one of those cards already then you don't have to keep switching cables when you use different applications for video out ;) Plenty of reasons to use it, but we'll keep supporting Rocket video out, so no worries if you're using that
 
You must log in or register to reply here.
Back
Top