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.
Are Mac Pro people really forgoing optimum RAID speeds (by switching down to 4x PCI) and/or downsizing their Graphic Cards, also to 4X -- just for Rocket! This seems like a huge amount of house cleaning - unless you have a single Rocket dedicated system with no 8x RAID and/or slow graphics. Still waiting word on Kona/Rocket together... Are they getting along? Plus, I'm little confused as to how people are currently using Rocket with out the breakout box - are they running straight to their primary monitor - and if so, I don't understand why a graphics card is still needed. Mayday.
 
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.

Jeff,

Do you see faster rendering to uncompressed format than ProRes?
 
  • Thread starter
  • Moderator
  • #26
Jeff,

About what speed are you currently getting to ProRes formats? I know it should improve with optimization, but just trying to figure out where it's at right now.

I'm only writing to an internal RAID-0 at the moment (2x1TB HDDs striped) until I can get a better RAID on this new system. So I'm hesitant to really put any stock in the numbers I'm getting. But it seems fast. I can do 2K DPX from a 4K full debayer close to real-time, 2K ProRes is slower, maybe 18fps... I will try to hook up a faster RAID so I can get some better numbers and I want to see where the bottleneck is at. Either way, the Rocket makes it way faster than before.

Are Mac Pro people really forgoing optimum RAID speeds (by switching down to 4x PCI) and/or downsizing their Graphic Cards, also to 4X -- just for Rocket!

Some compromises do need to be made in certain situations. However, either of the two x4 PCIe 2.0 slots will give up to 2GB/s throughput. I don't know of too many conventional RAID systems that will pull that off. I have my nVidia GTX285 in slot-1, RED Rocket in slot-2, ATTO SAS/eSATA HBA in slot-3 and slot-4 is currently empty as I'm trying to decide what else I'm doing with this new system. I need to add a good external RAID, but I'm trying to hold out for one of the new PCIe-2.0 ATTO R6xx RAID cards, but they're a couple months over-due. Also waiting for the enterprise class 2TB HDDs to hit the market as well, but I may just have to suck it up and buy something here in the next couple weeks. I should be able t replace the current ATTO card in the system and support the RAID, plus handle my LTO-4 and occasional eSATA needs in one slot. I'm considering a Kona LHi for the other empty slot, but also holding off to see just how much RED Rocket is going to factor into acceleration and monitoring within FCS3 and Adobe CS4.
 
Regarding the Mac Pro again... Any idea as to whether a Quadro FX 4800 would fit in slot-1 with a Rocket in slot-2 ---?
 
  • Thread starter
  • Moderator
  • #29
The Quadro FX 4800 isa double-width card, just like the nVidia GTX285 and ATI 4870 that many of us here are using. The RED Rocket will still fit just fine in slot-2, however the video card does cover the blank option slot. Which means that if you need the SDI connections to the RED Rocket card, you will have to run them out of a different slot or out somewhere else...
 
Hi, sorry if this has been asked before, but has anyone got the KONA3 and the RRocket to play nice in a 2009 macpro nehalem? If so what slots are you using and in what configuration? Just got my rocket and am planning an install on monday along with the new FCP studio update!


thanks!
 
  • Thread starter
  • Moderator
  • #31
Haven't done it myself yet as I don't have access to a Kona card right now, but the Rocket and Kona3 both prefer slot-2. I would first try it with the Kona3 in slot-3 and the Rocket in slot-2. If the Kona doesn't play nice, then swap them.
 
AJA's site says that slot 2 or 3 should work fine with the Kona 3 card. Unfortunately, I have a Kona LHe and it is NOT working well when moved from slot 2 to slot 3.
 
So we've go the Rocket up and running and things look really promising. As has been stated before, this is really going to change the industry.

Couple of requests on ROCKETCINE-X.

First, with the inability to save a project and with ROCKETCINE-X not writing RSX files, every time the program crashes, it loses everything. I know that it must be in the plan to have some sort of way to restore project or clip setting, I just wonder if it will be through a saved project or if it will be through RSX files? And I'd love to see whatever it is implemented soon.

Second, while I can save Looks, I haven't been able to restore any yet.

Third, I couldn't figure out how to select multiple clips to export to a batch. Just had to do it one at a time.

I have a personal preference for waveforms over histograms, but put this on the long term list or on the REDCINE-X list.

Performance to render to ProResHQ with the latest build is about 16fps on our system (4KHD 24P to 1080P ProRes). I'm very happy and look forward to more optimization to come!

Looking forward to playing around with it more tomorrow.

Thanks for all the hard work and such a great tool!

-Russ
 
So we've go the Rocket up and running and things look really promising. As has been stated before, this is really going to change the industry.

Couple of requests on ROCKETCINE-X.

First, with the inability to save a project and with ROCKETCINE-X not writing RSX files, every time the program crashes, it loses everything. I know that it must be in the plan to have some sort of way to restore project or clip setting, I just wonder if it will be through a saved project or if it will be through RSX files? And I'd love to see whatever it is implemented soon.

Second, while I can save Looks, I haven't been able to restore any yet.

Third, I couldn't figure out how to select multiple clips to export to a batch. Just had to do it one at a time.

I have a personal preference for waveforms over histograms, but put this on the long term list or on the REDCINE-X list.

Performance to render to ProResHQ with the latest build is about 16fps on our system (4KHD 24P to 1080P ProRes). I'm very happy and look forward to more optimization to come!

Looking forward to playing around with it more tomorrow.

Thanks for all the hard work and such a great tool!

-Russ

a. Saving looks with each clip will come first and then saving a project.

b. Not sure what you mean about saving look and restoring.

c. multi-select is also coming soon on the clip list.

d. waveform is on the longer list (i personally prefer histogram+parade ) :)

e. the latest build boosted qt performance from about 10-12 fps up to 16-17fps. We're anxious to get that up to full speed asap.
 
a. Saving looks with each clip will come first and then saving a project.

b. Not sure what you mean about saving look and restoring.

c. multi-select is also coming soon on the clip list.

d. waveform is on the longer list (i personally prefer histogram+parade ) :)

e. the latest build boosted qt performance from about 10-12 fps up to 16-17fps. We're anxious to get that up to full speed asap.

As expected, you guys have a solid plan of features that you're adding. I'll play around with Looks again tomorrow and see if I can get it to work (creating a look on one clip, then applying it to another).

With how promising ROCKETCINE-X is, it's getting me very excited to see REDCINE-X and also to see how the SDK is going to be implemented in other apps.

-Russ
 
Russ, you have to save a "look" setting and then doubleclick it and the look should automatically be added to the clip.

Works for me.
 
Russ, you have to save a "look" setting and then doubleclick it and the look should automatically be added to the clip.

Works for me.

I gave that a shot and somehow I ended up causing the program to quit showing any of the color adjustments on any of the clips.... then it crashed.

I'll load up some fresh clips tomorrow and give it another stab.

Thanks,

-Russ
 
I gave that a shot and somehow I ended up causing the program to quit showing any of the color adjustments on any of the clips.... then it crashed.

I'll load up some fresh clips tomorrow and give it another stab.

Thanks,

-Russ

Please email me the crash log if it crashes (deanan - a t - red) again or look in your home directory / library/logs/crashreporter for any old crash logs.


Russ, you have to save a "look" setting and then doubleclick it and the look should automatically be added to the clip.

Single click is all you should need.
 
Thanks. I'll send you the crash logs.

Just tested using Looks and they aren't loading on any of the shots. Currently there isn't a preference file to keep Looks and Presets right? So they need to be created each time the program opens?

-Russ
 
Thanks. I'll send you the crash logs.

Just tested using Looks and they aren't loading on any of the shots. Currently there isn't a preference file to keep Looks and Presets right? So they need to be created each time the program opens?

-Russ

The looks get saved in a prefs file. Maybe there are permission issues in your folders?
 
Status
Not open for further replies.
Back
Top