Welcome to our community

Be a part of something great, join today!

  • 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.

Jeff Kilgroe

Well-known member
Joined
Jan 3, 2007
Messages
17,055
Reaction score
42
Points
48
Location
Colorado
EDIT : Please direct all questions to the appropriate REDCINE-X forum area. ROCKETCINE is deprecated and no longer supported. This thread has been closed (mostly because it was attracting spam bots).
 
Last edited:
  • Thread starter
  • Moderator
  • #2
I thought I would start off with an issue I encountered last night. ROCKETCINE-X would quit unexpectedly every time I rendered out a ProRes clip. Other codecs were fine, but ProRes (422, HQ, 4444) would crash the app.

Jarred and Deanan were awesome and answered my email last night at midnight..

Turns out it was a problematic ProRes QT component on my end, I have it working now after removing the ProRes component, reinstalling and repairing permissions.
 
I've received fantastic help from the guys on my Rocket thus far. I got an email from Sean at about 11:30 the other night after I submitted a bug report!

Do we want to treat this as an appropriate place to report bugs for RED to read? Or [RED], would you guys prefer that we contact you directly with bug reports?
 
Great idea Jeff!

Here's my list so far. Everything has been reported to Red, who have been amazing!

Running a worst case scenario here, 1st gen quad Mac Pro 2.66 with 6GB of RAM, 10.5.7. Pretty much a base system.

Rocket Cine X build440

IMPORTANT - anyone using a 1st gen Mac Pro needs to use the Expansion Slot Utility and play with the settings. Otherwise the card's performance will be hampered. When I first installed I couldn't play at full frame rate. Deanon helped me greatly to fine tune this.


*BASIC USE*
Results are pretty good. I can play 4k at full resolution on the Mac monitor, downsized of course, but using every pixel. DVI/SDI not implemented yet.

Transcoding is impressive. 4k full debayer to SD in real time. 4k full debayer to HD 3x real time. Without RR it's about 25x real time for SD and don't even try HD.



*Rocket Cine X*
Love the app. Can't wait for more features to come online.

*TRANSCODING - *
- Batch list doesn't display proper %. Starts at random places, like 4321% or 52% and jumps around. When complete it jumps to 100%


- QUICKTIME presets don't remain. I have to re-enter them each time I open CineX


- QUICKTIME presets can't be edited. If I want to alter it I have to erase the preset and create a new one

- PRESET drop box cut off

*VIEWING/GRADING-*
- 1/8 and 1/16 don't play, only stills. Have to use 1/4 or higher for playback

- METADATA not coming in properly, particularly with Color Space and Gamma

- PLAYBACK doesn't happen from cursor point. Usually starts 1000 frames+ after. Frustrating when I want to check in/out points etc.

*GENERAL*
Got a couple of crashes and errors, but nothing unexpected from ALPHA
 
I thought I would start off with an issue I encountered last night. ROCKETCINE-X would quit unexpectedly every time I rendered out a ProRes clip. Other codecs were fine, but ProRes (422, HQ, 4444) would crash the app.

Jarred and Deanan were awesome and answered my email last night at midnight..

Turns out it was a problematic ProRes QT component on my end, I have it working now after removing the ProRes component, reinstalling and repairing permissions.

I've been having the same problem as well with quicktime exports. I submitted a support ticket this afternoon. However, I'm also not getting real-time playback of any 4k 16x9 clips when set to "full". It plays for a few seconds then starts dropping frames. Anyone else had this issue?
 
Jeff

UPDATE EDIT

You can view the ProRes Porxy,LT and 4:4:4:4 on a system not running FCS 2009 moving the ProRes component will work like in the past .
You can then encode to it as well from FCP 6 and Compressor.
As of yet RocketCineX doesnt work for exporting to it (yet).

So anything exporting QT will in essence use it FFMPEG,MPEG Streamclip, Adobe etc but I have not tested all of them yet.
 
I've been having the same problem as well with quicktime exports. I submitted a support ticket this afternoon. However, I'm also not getting real-time playback of any 4k 16x9 clips when set to "full". It plays for a few seconds then starts dropping frames. Anyone else had this issue?

Send support your system profile so we can try to figure out could be the issue.
For full 4k playback the bottleneck is getting data to the graphics card as the card has no problem maintaining realtime. As we get more info about system configs out there, we'll be able to better optimize things. We're everything being used from the latest mac with a nvidia 285 all the down to the oldest intel macpro with the oldest ati card in it.
 
can we paste looks across multiple clips? i want a whole rdm folder to get the same look. do i have to punch it in manually for the time being? i tried red rushes>create wrappers> open in rocket cine and they all look like default metadata still

creating looks and pasting coming very soon...
 
Hi Deanan - can we get start/stop clip playback capability in the space bar? That would save a lot of keystroke and shifting between the process of identifying the clip and playing it back. I was running through a thick folder of clips yesterday, and enabling space bar playback would have made the process much faster, that way I could keep the cursor scrolling through the clips.

Or is there already a secret keyboard command that I am not aware of with this functionality...?

Thanks for the awesome app -
 
I am currently running a 2 x 2.8 GHz Quad-Core Intel Xeon Mac Pro
16 GB 800 MHz DDR2 FB-DIMM
Mac OS X 10.5.6


I have had success exporting these Q.Ts:
- Pro Res & Pro Res HQ 1920x1080 at each Debayer setting
- Pro Res & Pro Res HQ 2k at each debayer setting
- Avid DNX HD at 1920x1080 at each debayer setting
- Avid DNX HD at 2K at each debayer setting

No 4K..?

Are there different versions of Rocket Cine X that people are using? Currently I can not open an "About RocketCineX" option to see the version.

Audio seems to be rendering fine with each of these quicktime files.

The software seems to crash randomly. But more often when I am leaving to go to the finder and attempting to go back into RocketCineX.

Currently the 2K playback is fine, but the 4k drop frames immediately.

Cheers,

Jesse Korosi
 
Mine is arriving tomorrow. There goes my weekend. Thank you for everybody's information, this will get me ready to do a work next week on the footage with very important person.
 
  • Thread starter
  • Moderator
  • #13
I'd also like to second Meryem's request for the spacebar. I keep hitting the thing out of habit.

After I repaired permissions and reinstalled FCS3, all seems to be working well. ProRes 4444 seems to be a really nice codec, but that's for another thread. All my QT and ProRes formats works just fine now without crashing the application.
 
Hello all!
I have had a chance to do some tests with the Rocket Cine X software also.

I am currently running a 2 x 2.8 GHz Quad-Core Intel Xeon with 16 Gigs of Ram. With an ATI Radeon HD 2600 graphics card. Current Q.T version is 7.6 (472)

I also can not play back 4K material without it dropping frames right away.

2k doesnt seem to have an issue with playing back though.

Here are the Quicktimes I have processed successfully:
- Pro Res & Pro Res HQ 2k, 1080 and 720 using each debayer
- Avid DNX HD 2k, 1080 and 720 using each debayer

Each seem to be carrying time code properly and also keeping the Curve Adjustments that I set. (unlike Red Alert to Red Rushes the curve doesn't carry through)

- 4K with which ever codec I have tried continues to crash.

Does anyone know how to clear the Batch field from previously rendered clips?

Cheers,
 
Hi Deanan - can we get start/stop clip playback capability in the space bar? That would save a lot of keystroke and shifting between the process of identifying the clip and playing it back. I was running through a thick folder of clips yesterday, and enabling space bar playback would have made the process much faster, that way I could keep the cursor scrolling through the clips.

Or is there already a secret keyboard command that I am not aware of with this functionality...?

Thanks for the awesome app -

Space bar is there but it seems to be blocked. Will take a look at it today.
 
we need it to auto name the files with their r3d name.. ( we need the auto filename and blanket looks across multiple clips.. typing in the look manually as well as the filename for each individual clip for a reconnect media in fcp is so tedious its almost faster using red rushes and not red rocket (in my particular case this week..
 
we need it to auto name the files with their r3d name.. ( we need the auto filename and blanket looks across multiple clips.. typing in the look manually as well as the filename for each individual clip for a reconnect media in fcp is so tedious its almost faster using red rushes and not RED Rocket™ (in my particular case this week..

auto naming is already in the next build.
copy/paste looks is already in the next build.
multiselect/paste build be in the build after that...

It sounds like you're suggesting (not quite sure though) that it would be better to hold up releasing until we get everything in there.

We'd rather get you something working and so there's something for you to give feedback on how you'd like things to work. The public alpha/beta cycle is a process that we intentionally do so we have a chance to roll in changes before things get baked in.
 
Absolutely. definitely not suggesting you hold up releasing stuff =] My post may have read not how I wanted

reading everyone's suggestions got me worried that things might be implemented in place of what I felt was more important/urgent to be resolved, I am very happy to have some form of RocketCine right now and understand we are all beta testing it pretty much.



auto naming is already in the next build.
copy/paste looks is already in the next build.
multiselect/paste build be in the build after that...

It sounds like you're suggesting (not quite sure though) that it would be better to hold up releasing until we get everything in there.

We'd rather get you something working and so there's something for you to give feedback on how you'd like things to work. The public alpha/beta cycle is a process that we intentionally do so we have a chance to roll in changes before things get baked in.
 
Absolutely. definitely not suggesting you hold up releasing stuff =] My post may have read not how I wanted

reading everyone's suggestions got me worried that things might be implemented in place of what I felt was more important/urgent to be resolved, I am very happy to have some form of RocketCine right now and understand we are all beta testing it pretty much.

Great. Keep the suggestions and feedback coming!
 
Status
Not open for further replies.
Back
Top