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.
that's what i've heard as well since the problem doesn't persist with dpx transcoding; unfortunately editing in fcp with dpx's is about as efficient as proxies, so why even bother?
 
2 Separate issues:

1. Rocket Cine X has suddenly stopped allowing exports. Of any kind. Just weird. Used it for Build 21 Rec 42 for 2 shoots the past two weekends, worked fine to prores 4444 on 2 separate film shoots. now we cant export a simple camera test at all.

Restarted
Hard Shutdown (unplugged cables for 5 minutes)
Reinstalled all RED software
Repaired permissions.

Problem persists.

FWIW- We can playback footy to our Dreamcolor, but when you mouse over export buttons they turn yellow, but no longer click. They do nothing like they were disabled?

Wrote Deanan yesterday, waiting for answer. Anyone have any thoughts?

2. (A build 21 or Rocket issue?) Our camera (we shot with 3 the other day) all on Build 21 Rec 42... but ours imports with no meta data (or se to 0) and the clips are all black. EASY FIX... just select clip in Rocket-X and then click "Defaults"... and the clip appears.
but a pain in the arse and scared the hell out of us as we thought we lost a day's shooting.

Is it our camera settings.? a known bug? 31 pages here. Cant find our specific issues.

thanks!
 
Tim Whitcomb said:
(A build 21 or Rocket issue?) Our camera (we shot with 3 the other day) all on Build 21 Rec 42... but ours imports with no meta data (or se to 0) and the clips are all black. EASY FIX... just select clip in Rocket-X and then click "Defaults"... and the clip appears.
but a pain in the arse and scared the hell out of us as we thought we lost a day's shooting.

Is it our camera settings.? a known bug? 31 pages here. Cant find our specific issues.

thanks!
Click to expand...

we had the same problem on a shoot last year; it was a camera setting that got bumped; try resetting camera and everything falls back in fine.
 
So i saw that other people were getting similar render errors as we are but no-one ever really helped them with any kind of knowledge why this may be happening or any workaround besides shutting down for a minute or two; that really isn't helping, it might fix 2 out of 5 clips; for $5k this card isn't really living up to the hype
 
I actually agree with Thom. It's just another video card to my ext. monitor which I don't need. I have a Kona 3 for that. I could invest the money somewhere else and buy the RR when it actually does something in my workflow.

Also, getting that "it's almost ready" or "next week" comments don't really help.
 
I have the latest Nehalem Mac Pro and I had to do tons of rendering for Olympic bid presentation job. Especially with Snow Leopard running, I never had issues going down to x4 speed. Since I'm pretty much on Snow Leopard, I can't use the metaSAN at this moment, so I'm reading from and rendering to local ATTO RAID and don't have issues.
I don't use Kona, though. I have Blackmagic or MXO2 Rack running with my system.
 
Colin Hubick said:
The issue with a 2gb cap on network renders is said to be an Apple problem.
Click to expand...

There are plenty of Mac OS X apps (in fact, nearly all), than can successfully write files larger than 2GB to a server volume. After Effects, Final Cut, even shareware programs like JES deinterlacer all handle it fine.

As I understand it, RED is using an older API that has the 2GB limitation, apparently they are using this API due to bugs in the modern API. Deanan said they would look into switching to the newer one someday, but it can't be soon enough for me.
 
I ran into the rendering trash issue last night when I set the rendering target as internal HD. As soon as I change the target to be RAID configured with ATTO R380, it was fine.
 
Jeremy Neish said:
There are plenty of Mac OS X apps (in fact, nearly all), than can successfully write files larger than 2GB to a server volume. After Effects, Final Cut, even shareware programs like JES deinterlacer all handle it fine.

As I understand it, RED is using an older API that has the 2GB limitation, apparently they are using this API due to bugs in the modern API. Deanan said they would look into switching to the newer one someday, but it can't be soon enough for me.
Click to expand...


I can confirm that I run into the 2 gig limit when I render to a Network Drive over afp, but do not run into this problem when going to Xsan over Fiber.
 
hello Deanan

sorry to Hi-jack Mike curtis's same questions but now i am wondering if these are comming soon...as i gotten used to the great tools in Red alert im jonseing for them.

-Chroma Denoise - not functional at all yet - greyed out?
-Debayer Detail - greyed out, not usable?
-OLPF Compensation - greyed out, not usable?

DRX - greyed out, not usable?
 
didnt read all posts....

a progression bar when rendering clips would be nice.... per clip or over all....
 
Rainer Fritz said:
didnt read all posts....

a progression bar when rendering clips would be nice.... per clip or over all....
Click to expand...

Rainer,

There is already a % read out while clips are rendering, which in my mind gives you the same info as a progression bar. Click on the Batch Tab on the lower left while exports are going.
 
kk thanks

resample filter option is also empty.....

debayer detail would be great to have and resample filter, because the pictures are sometimes too soft...

do you get proper audio export ?

thx
rainer
 
a bigger histogram would be also nice....

i am getting audio at playback but nothing in the exported files....
 
full debayer seems to run not smooth, half high is ok here......

setting individual caches would be great....
 
I just installed the new redcine - X and rocket -X and it tells me i need new firmware and driver, but they weren't in the download? do other people have this or am i just being dumb?
 
:emote_headwall:PROBLEM WITH NEW REDROCKET INSTALLER (V1.0.10) !!

Just installed new Redrocket driver on my Macpro Nehalem 8Core running Snow Leopard.
Asked to restart/shutdown after install....Getting a kernel panic and now the computer won't start! (Posting from my laptop).
HELP !!!! Hope this doesn't mean a system re-install.
:-(
 
Status
Not open for further replies.
Back
Top