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

ROCKETCINE-X Bugs, Comments, Help...

Status
Not open for further replies.
Working with ROCKET CINE-X build 661 this week -- have discovered what seems to be a bug of sorts involving choice of GAMMA / tone for output. I'm using clips that are default as REDSPACE color space and REDSPACE gamma.

But when I try to output using Camera RGB / 709 GAMMA the rendered media defaults back to REDSPACE gamma even though the interface is showing me the 709 gamma. I was going from 4k 23.98 RC36 down to 2048x1152 DPX. Has anyone else seen this?
 
...hey RED team, what is the latest on the updates to Rocket Cine, and drivers for RED Rocket? Audio through HD-SDI? PsF? Anything new, or revised timelines?

would love to have a dedicated sticky regarding RED Rocket as well!

cheers
Colin
 
Colin Hubick said:
...hey RED team, what is the latest on the updates to Rocket Cine, and drivers for RED Rocket™? Audio through HD-SDI? PsF? Anything new, or revised timelines?

would love to have a dedicated sticky regarding RED Rocket™ as well!

cheers
Colin
Click to expand...

Should have a new release with some big features like mxf in the next few days. (psf also)

Audio on HDSDI is still a bit out as the firmware is still being developed for that.
 
Deanan said:
Should have a new release with some big features like mxf in the next few days. (psf also)

Audio on HDSDI is still a bit out as the firmware is still being developed for that.
Click to expand...

I like big features! EDL? XML? REDLINE support? those would be big features.
 
Is either RocketCine-X or REDCine-X working with build 20, 4k HD yet? We shot some footage today and it would not work. RECCine-X would only see it as black files even in it's preview bin window.

The old Red Alert did open the clips fine.

Is there something I'm missing to allow these to work?

Thanks.

Kevin
 
4kHD no problem with RocketCine-X and RedCine-X, must be something else going on.

I do know that 4.5k isn't working in them yet, but 4kHD is fine, I use it all the time.
 
Jim, Build 20?
 
Reading between the lines, it seems like EDL/XML will come through 3rd party plug-ins, and intentionally won't be developed by RED.

There's a theory that RED may have an agreement with Assimilate not to include these so it doesn't compete with Scratch. No proof of that, just a conspiracy theory! :wink:

Colin Hubick said:
I like big features! EDL? XML? REDLINE support? those would be big features.
Click to expand...
 
Interesting that neither of my app's are seeing the build 20 footage. Maybe it's the Quicktime plugin I need to try?
 
Hey Kevin. That's weird. Have you checked the settings within Rocket Cine? I know Red Alert used to misinterpret meta data sometimes and set the exposure to zero.

I haven't had any trouble at all.

The QuickTime plugin isn't at play here, it's only for viewing proxies. If you open an R3D in Rocket Cine X, it should just be there.

Let me know what you find.

Cheers,

Jim
 
Okay, a little more testing. For some reason, RocketCine-X and REDCine-X both fail to read the files on our RAID Volumes. They won't work in preview mode, nor can we bring them in to play them back. As soon as I moved the folder of new 4k B20 files to the desktop, they worked fine. The odd thing is the app's do see older footage on the RAID just fine.

We have our RAID used within a MetaSAN setup. Deanan-Any known issues with RAID's? Make any sense that it's seeing older ftg, but not new ftg?

At least I could move the ftg and check it out. New RPP's today, so I couldn't wait to play.

Thanks!

Kevin

**EDIT**
Figured out the problem. It's "*" in the name of a folder that for some reason, the RED app's cannot see through. As soon as I brought the file out to the root, outside of the folder with "*" in the title, it worked fine. (My bad. I know I shouldn't have those in folder names...just never changed it from long ago. FCP has no problem with it.) So...problem solved!
 
Kevin Wild said:
Okay, a little more testing. For some reason, RocketCine-X and REDCine-X both fail to read the files on our RAID Volumes. They won't work in preview mode, nor can we bring them in to play them back. As soon as I moved the folder of new 4k B20 files to the desktop, they worked fine. The odd thing is the app's do see older footage on the RAID just fine.

We have our RAID used within a MetaSAN setup. Deanan-Any known issues with RAID's? Make any sense that it's seeing older ftg, but not new ftg?

At least I could move the ftg and check it out. New RPP's today, so I couldn't wait to play.

Thanks!

Kevin
Click to expand...

There are some issues we've heard about with some SANs but completely unexplainable though as we're using bog standard file i/o. It might have to do with permissions through the SAN. We're looking into but haven't replicated it here at the office.
 
Deanan,

I found ROCKETcine-X can load same clips and also load from aliases. Conveniently, the aliases can hold their own RSX aside from the one in the original. Therefore, you can create as many aliases as you can and have different metadata settings for each cuts from a same clip.

Now, upon loading multiple aliases with the same parental R3D, with folder names altered, by using loading folder function in ROCKETcine-X does not let me load multiple aliases. If I load them one by one it will let me load. Is there anything on your side to make this happen? Also, I'm not certain what happens upon rendering.
 
Never mind, I figured it out. You gonna see a surprised workaround that Hans and me created (for the time being anyways).
 
I had a strange issue with the RedRocket on set yesterday. I'm running RocketCine-X on an 8Core Nehalem 12GB Ram w/SnowLeopard.

Transcodes to ProRes 1080 (from 4K 16:9/23.98) were working fine...a few select clips here and there for the director to cut the spot on set. But then I tried to batch a series of 120 Clips (unfortunately reading and writing to the same drive), which took a good 2 hours.
Playback on any clips in RocketCine-X (during batch) would hang / display only a single frame and all 120 ProRes clips were frozen on the first frame of each clip. The drive being used was connected eSATA.
After a restart the transcoded clips seemed unplayable (a 2 minute clip would have only the first frame yet be playing in quicktime-X). A Restart didn't help clip playback...seems they were transcoded that way (not a playback / stuttering issue)
After the forementioned restart transcoding to Prores worked as it should. Unfortunately it was the end of a 15hr day and there was no time to transcode again.
So just a warning that it does pay to check clips as you go (if possible).
Has anyone else experienced transcoded clips hung on the first frame?


BBroz
 
Deanan said:
Should have a new release with some big features like mxf in the next few days. (psf also)

Audio on HDSDI is still a bit out as the firmware is still being developed for that.
Click to expand...

Any chance we will see this new version out today? a few more options like scaling and time code burn would be great...

cheers
Colin
 
Wow ...

Wow ...

First of all, thank you Red for RedRocket (and ROCKETcine-X) ... BRILLIANT ! Popped into Red UK to have a look at one and it's a dangerous thing to 'taste' ... could not leave without one ;-)

I've scanned some of the entries here ... initial comments :

- render (presets) : once saved, cannot edit them ? can only delete or add a new one (no big deal, but could it be possible to double click an existing setting and tweak) ?
- batch tab : invert the order ? ie: latest completed at the top ? ... saves having to scroll to the bottom once the list is bigger than pane height (or provide click on column name to invert sort order)
- Look Setup area (and Default / Metadata / Grade tabs) ... am I correct in assuming that Default = some pre-canned default point settings; Metadada = settings as at capture time; Grade = setting following the grade done withing RocketCine-X for the each clip ?
However, once graded, if I click Defaults or Metada (to compare) I seem to loose the 'Grade' settings ... where am I going wrong ?

Anyway ... please do not shout back at me if these are already covered elsewhere ;-) been like pig-in-s**t for the last few hours playing (and not reading fully this thread) ...

This card is a MUST for any R3D user :emote_happyhappy:

TTFN
 
Status
Not open for further replies.
Back
Top