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.
Don't know if this is mentioned before, and it sounds like conflicting what Deanan is suggesting, but when I keep getting x4 status alert, instead of shutting down and leave it for awhile and power cycle, I restart the Mac instead and it would come back up with x8 lane.

We'll be releasing the new firmware that fixes this early next week.
 
Hey deanan,

any word on when visual burn-in options will be there for exports? And is DNxHD export working yet? Excuse my questions if they have been answered already somewhere. Barely been sleeping lately. Too many red gigs ;)


DNxHD to MXF (zero import time in media composer!) is working.
Auto-Sync to BWF (via timecode) is working.
More scaling options are going in now.
Visual Burn in is also going in.

All of these are targeted for a rocketcine build for next week.
 
Deanan, I asked this before (mostly out of curiosity).

What's the point of continued development of RocketCine-X rather than just putting all efforts into REDCINE-X (which even Jim says will be the app used nearly all the time by users)?

It just seems a waste to time unless there is something I'm missing--that Rocketcine-X does something that can't be done with REDCINE-X. Am I missing something?

Thanks! Both are awesome. I'm playing around with REDCINE-X now and really love the layout you guys came up with.

Kevin
 
You rock kaku

Chris, I'm sure many must feel the same way, but I'm even amazed with these facts that I experienced.

Thanks for your kind words.
 
Deanan, I asked this before (mostly out of curiosity).

What's the point of continued development of RocketCine-X rather than just putting all efforts into REDCINE-X (which even Jim says will be the app used nearly all the time by users)?

It just seems a waste to time unless there is something I'm missing--that Rocketcine-X does something that can't be done with REDCINE-X. Am I missing something?

Thanks! Both are awesome. I'm playing around with REDCINE-X now and really love the layout you guys came up with.

Kevin

Kevin,

At this point, since ROCKETcine-X is simpler application, it provides more solid working condition where REDCINE-X is more capable but less stable, don't provide the output from RED ROCKET in realtime, yet.

In my opinion, ROCKETcine-X will provide earlier adoption of new features of the color science and RED ROCKET development, so the meaning of its presence is there.
 
We'll be releasing the new firmware that fixes this early next week.

Deanan, sorry I know you told me so, but until then, it did help me.

I'm doing some vast converting with ROCKETcine-X right now (it's the dream job I got that I mentioned in the other post).

Changing the topic, I noticed that when you convert clips to PALDV, the gamma seems to change to 1.8. I did the baselight in 2.2 environment, but it came out in 1.8 (in Snow Leopard). I thought I should let you know.
 
Kaku-No offense, but I was hoping to hear RED's answer. It just seems like a LOT of extra work to develop 2 app's simultaneously that are getting closer and closer in what they do.

Unless there is something that RocketCine-X does that REDCINE-X does not...it makes sense to put all efforts into one. I'm not trying to tell them how to do their job, but my main question is as these finalize, what is the difference between them and is there a point to RocketCine-X at all once REDCINE-X is up to speed, has all the same features, supports Rocket and non, etc.

Thanks.

Kevin
 
Deanan, I asked this before (mostly out of curiosity).

What's the point of continued development of RocketCine-X rather than just putting all efforts into REDCINE-X (which even Jim says will be the app used nearly all the time by users)?

It just seems a waste to time unless there is something I'm missing--that Rocketcine-X does something that can't be done with REDCINE-X. Am I missing something?

Thanks! Both are awesome. I'm playing around with REDCINE-X now and really love the layout you guys came up with.

Kevin

They will merge into one app pretty soon.
 
Kevin, I'm sorry if I offended you with my broken English and thoughtless points.
 
Deanan,

About the PALDV gamma thing, it might have happened only on certain clip. Is there any particular parameters that don't apply in rendering?
 
Ah, that is what I was wondering. Thanks, Deanan. I asked this in another thread and got about 25 different opinions on this. :-) I was kind of thinking that they were merging since their feature sets are getting very similar.

Kaku-Your points weren't "thoughtless." I just wanted to hear the facts from the people "in the know." :-)

Thanks.

Kevin
 
Just installed RED Rocket™ today - a couple issues that I don't see discussed here:

I'm trying to record the SDI out - but, of course, it's 1080p with no option for PSF. I don't know of any decks that record P, just PSF. Similarly, the SR deck doesn't like the RGB output - monitors love it, decks don't.

Has this already been discussed? Couldn't find it.

Going to test some rendering now - which will be our main use anyway, but the play-out-to-tape would be / will be awesome (and useable/marketable) once we're actually able to do it.

gh
 
Just installed RED Rocket™™ today - a couple issues that I don't see discussed here:

I'm trying to record the SDI out - but, of course, it's 1080p with no option for PSF. I don't know of any decks that record P, just PSF. Similarly, the SR deck doesn't like the RGB output - monitors love it, decks don't.

Has this already been discussed? Couldn't find it.

Going to test some rendering now - which will be our main use anyway, but the play-out-to-tape would be / will be awesome (and useable/marketable) once we're actually able to do it.

gh

PsF will be added to a release next week.
 
I did some real world rendering of R3D to ProRes4444 tonight. 47 minutes of 4K footage converted to ProRes4444 (without the key channel) too about 100 minutes with Mac Pro Nehalem 2.26 dual QC and x6 drive raid6 with ATTO R380. So not quite real time but 2:1 ratio is pretty impressive.

And with Nehalem Mac Pro, I don't get the x4 alert even once yet.
 
Interesting that you're getting just over 2:1 ratio on the transcode to ProRes4444 w/ a Nehalem machine. I've got a Rocket card installed on a version 2 MacPro (Intel Xeon) -- I'm getting the x4 alert and I'm getting about 2 min 12 sec for a 1 minute clip. Perhaps the transcode times don't increase all that much with a Nehalem box with faster port speed.

I'll be switching over to a Nehalem box tomorrow so I curiously await new results.
 
Hello JD,

x4 speed down issue will be solved soon, but I guess my report is the realistic one considering there's 4k to HD resizing involved.
 
Have you tried using 4K HD footage? Perhaps this is a faster transcode due to easier math on the scaling?
 
Status
Not open for further replies.
Back
Top