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.
Anders has some good points, and I'm in complete agreement. Especially the selection schemes.

On the other hand, I'm just glad we have some way to do all of those things. I've kind of been viewing RocketCine as a stop gap to more elegant solutions that take advantage of the rocket savvy API when it comes out. However, if we are going to be using RocketCine for a while then once the more serious bugs are worked out and critical features added, I think the UI could certainly use some tweaks.

I'm glad I didn't bring up the Qt thing first. From a user interface standpoint, I detest programs that use Trolltech Qt (not to be confused with QuickTime). I'm looking at you Sorenson Squeeze! They always feel like bad Linux ports rather than Mac programs. And though this is one of the better examples of a Qt App, it still exhibits some of the telltale signs of being a Qt port. Specifically the use of Helvetica on all the buttons rather than the system standard font, the fact that list boxes never quite look or work right or as expected. The UI refreshes poorly, especially when resized. Dialog boxes always put the buttons in the wrong place (The Okay button should be on the bottom right corner of the dialog and cancel just to it's left. Not centered as they are in this app). Mouse overs slightly delayed. I could go on.

Like I said, minor issues until the program is more stable and functional. But it would be nice if they were addressed some day.
 
Robert Horwell said:
Export selected asks me for a different folder for every file.
Click to expand...

When you set up your export you can have it go automatically to a specific folder, ask for every clip, or output to the clips source folder.
 
Hi,

on set today with the rocket! I am not having any of the problems that are mentioned on this board. Only problem is once in a while it will not transcode the first clip in the list to be transcoded. No biggy I just quit out and load just that clip. Trancode. game over. I am using it today to get to 720P prores 23.98 clips for the offline. I am reading and writing to a 7200rpm drive with esata! Crazy fast!!!! have not times anything but at the end of the day client will have 720p proresHQ full debayer. Unheard of till rocket. I think my rocket,kona3, fCStudio3 are running flawlessly because I did a fresh install of all on a new system. Hey it was not fun, but I am having no issues like the others on the board. Just thought I would share my success story here with the card. System drive is 2 10,000 rpm raptors/16ig ram. Have been rendering to a internal 2 drive raid but the read/write to esata drive set up today is still crazy fast!!!!

IMG_7212.jpg
[/IMG][/IMG]

IMG_7210.jpg


IMG_7211.jpg
 
Deanan said:
When you set up your export you can have it go automatically to a specific folder, ask for every clip, or output to the clips source folder.
Click to expand...

ah thanks deanan, just done that and managed to output a few QT's.:thumbup1:
 
External monitor playback speed still not fixed.

External monitor playback speed still not fixed.

Playing back 24fps clips to an external monitor @ 1080p 29.97 still results in the clip playing too fast.

I haven't had a chance to really work with this or check other modes.
 
Howdy,

I noticed that with build 566 of RocketCine-X DPX files no longer have timecode information in the metadata. I have tried several R3D files that with build 491 had the information in the metadata and have used the same export settings, but alas no TC info in 566. Can anyone else out there re-create this?

Regards,
Duck
 
Jeff Kilgroe said:
Playing back 24fps clips to an external monitor @ 1080p 29.97 still results in the clip playing too fast.

I haven't had a chance to really work with this or check other modes.
Click to expand...

Hmm, definitely fixed that but we're checking now because it sounds like it may not have been fully fixed.
 
duckgrossberg said:
Howdy,

I noticed that with build 566 of RocketCine-X DPX files no longer have timecode information in the metadata. I have tried several R3D files that with build 491 had the information in the metadata and have used the same export settings, but alas no TC info in 566. Can anyone else out there re-create this?

Regards,
Duck
Click to expand...

Just checked it and TC looks ok.
What program are you viewing TC in?

(no higgins in sight though)
 
Deanan said:
Just checked it and TC looks ok.
What program are you viewing TC in?

(no higgins in sight though)
Click to expand...

Howdy,

I have viewed the frames via, Pomfort SilverStack, DVS Clipster, and E-Works 2009 (Lustre)

All of them show the key code and time code as the same, it seems like RocketCine-X will apply information to the first frame and duplicate across the entire sequence.

Regards,
Duck
 
duckgrossberg said:
Howdy,

I have viewed the frames via, Pomfort SilverStack, DVS Clipster, and E-Works 2009 (Lustre)

All of them show the key code and time code as the same, it seems like RocketCine-X will apply information to the first frame and duplicate across the entire sequence.

Regards,
Duck
Click to expand...

Looks like it is stuck. Fixing.
 
I'm still getting unable to render errors.

When i select clips and then set in-out points for new clips it de-selects all my selected clips, anyone else get this?
 
Robert Horwell said:
I'm still getting unable to render errors.

When i select clips and then set in-out points for new clips it de-selects all my selected clips, anyone else get this?
Click to expand...

Robert,

I am able to render multiple clips with in and out points selected without having them deselected. I set my in and outs, then check the selection box and click on "export selected" I then get prompted to select the folder for where to render each selection.

If I make a new preset and select the option to use sub folders, it creates the folders for me, but the option to select which folder to use is not available to click on, so it renders the clips in new folders in the folder containing the R3D files. I would like to see the availability to select which folder it writes to in a future build.

Sorry I could not re-create the problem.

Regards,
Duck
 
duckgrossberg said:
Robert,

I am able to render multiple clips with in and out points selected without having them deselected. I set my in and outs, then check the selection box and click on "export selected" I then get prompted to select the folder for where to render each selection.

If I make a new preset and select the option to use sub folders, it creates the folders for me, but the option to select which folder to use is not available to click on, so it renders the clips in new folders in the folder containing the R3D files. I would like to see the availability to select which folder it writes to in a future build.

Sorry I could not re-create the problem.

Regards,
Duck
Click to expand...

Right above "sub-folder per clip", select "Output with Clip Filename to Selected Folder", then click on the "select Output Folder" button.
 
Did something change with Build 566 and ProRes 4444??? I'm finally working with the new build today and any clip I transcode to ProRes 4444 becomes a movie that is all black. ProRes HQ and H.264 are working fine. ProRes 4444 was working with the previous build.
 
Jeff Kilgroe said:
Did something change with Build 566 and ProRes 4444??? I'm finally working with the new build today and any clip I transcode to ProRes 4444 becomes a movie that is all black. ProRes HQ and H.264 are working fine. ProRes 4444 was working with the previous build.
Click to expand...

Try setting the Quicktime option in the setup window to MillionsOfColors instead of MillionsOfColors+ (which adds alpha).
 
Last edited:
Yep, that fixed it. Guess I didn't think to check that. So is this alpha channel "issue" actually an issue that is to be addressed in Rocketcine? Or is it a QT issue or something with the PR4444 codec that hasn't been resolved yet. I know the new codec has alpha support, just curious as to why when the color+ alpha option is selected this happens?

Thanks.
 
Jeff Kilgroe said:
Yep, that fixed it. Guess I didn't think to check that. So is this alpha channel "issue" actually an issue that is to be addressed in Rocketcine? Or is it a QT issue or something with the PR4444 codec that hasn't been resolved yet. I know the new codec has alpha support, just curious as to why when the color+ alpha option is selected this happens?

Thanks.
Click to expand...

None of our apps output alpha channels and rocketcine especially since it would slow things down going through every pixel and adding an alpha.
It's one of the down sides of giving full control to the QT setup dialog box.
 
whats up with audio? i thought red default quicktimes were 4 channel 48khz 24 bit ? in rocketcine when you open the quicktime export dialog it only lets you do 16bit 2 channel. i assume this will be fixed soon but thought i'd mention it..
 
It says that but my Rocket generated QTs come out with 4 channels when recorded. Maybe it's just the QT dialog.
 
Status
Not open for further replies.
Back
Top