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 :)

new REDCINE-X feedback

Red alert has a way of working with qmaster is there a plan for redcinex to do the same. I can not find any information inside redcinex about qmaster.
 
Jonathan Cooper said:
Red alert has a way of working with qmaster is there a plan for redcinex to do the same. I can not find any information inside redcinex about qmaster.
Click to expand...

Possibly when we release redline but none planned yet.
General feedback has been that very few people have been using qmaster without huge headaches. Another cross platform queue engine might be a better choice.
 
I would really like to get this figured out. Qmaster has been giving us problems as well. After doing a google search for cross platform queue engine I have found nothing useful. Do I need to start a new thread to find out what is working for people? Sorry for the rookie question.
 
Not to hijack the thread - but Jonathan - have you looked in to X Grid with Qmaster? I know Broadway Video has quite a lot of success with it as their render managed farm starring Qmaster
 
Deanan,

Any word on when we're going to be able to use the full CPU for Transcoding?
I'm still getting only 2 of the 8 cores working when I am transcoding through RED CINE X. RED RUSHES let me pick how many clips at a time, and how many cores per clip, I'd love to see that function again. Either that or just force RedcineX to use the full CPU (for us that don't have a rocket card)
 
Aaron Hucker said:
Deanan,

Any word on when we're going to be able to use the full CPU for Transcoding?
I'm still getting only 2 of the 8 cores working when I am transcoding through RED CINE X. RED RUSHES let me pick how many clips at a time, and how many cores per clip, I'd love to see that function again. Either that or just force RedcineX to use the full CPU (for us that don't have a rocket card)
Click to expand...

We're planning on doing an optimization pass after we get through the bulk of the workflow items. (optimization is best done after things don't change much otherwise every time you make a change, you can easily lose the gains you made by optimizing).
 
eric a wahl said:
Has anyone fully resolved the Black Frames issue?, I still get random black frames.
Click to expand...

Unfortunately we're not able to recreate it here after testing through a thousand clips.

We've made some improvements to the exporting mechnism so hopefully that will fix it.
 
Black Frames

Black Frames

Is there a link to the update yet? Sometime soon?

Deanan said:
Unfortunately we're not able to recreate it here after testing through a thousand clips.

We've made some improvements to the exporting mechnism so hopefully that will fix it.
Click to expand...
 
Hi,

these are some problems i ran into the last couple of days testing the workflow with RCX (last build):

-I'd like to do QC off of the CF card directly. But when i'm done i need to unmount the media. Now i have to close RCX, eject the card out of the finder and restart RCX. Is there another way to unmount the card out of the application?

- tangent wave: transport & jog/shuttle doesn't work (did work on last build)
- histogram won't update using the RR output

Another question regarding FLUT™:
in the RCX manual it says:
" Once the preferred ISO is set, the FLUT level allows fine tuning of the ISO level. FLUT control units are in stops, so +1 FLUT Control is the equivalent of brightening the image by one stop or doubling the ISO value."

When i do a test and lift the ISO one unit on the first hand and leave the FLUT as is and lift the FLUT from 0 to 1 and leave the ISO as is on the other hand should it be the same? Because it is not. What would be the benefit using FLUT vs. setting ISO?

Help is greatly appreciated. Thanks.

- Severin
 
Getting a bit of random results on colorspace and gamma vs the settings I have chosen when rendering with RR.

Can this be an RSX issue?

I render from the bin to get separate clips.

Probably a userfault, but which?

(In the meantime, back to rendering with CF...)
 
I was setting in/out points in the player window and exporting several clips today. Unfortunately, sometimes the in/out points I specify don't stick, and the whole clip gets added to the queue. Don't know why that happened several times. There's no way to catch that bug, or user error, except by noticing how long some clips are taking to render. The player window indicates the in/out points are set, but then I jump to the export window and add to the queue, the in/out points are not set.

Related to that, there are some things I really wish would change about the Redcine-X UI:

1) When you set an in/out point, the earlier/later portions of the clip outside the in/out boundaries are no longer accessible in the viewer. I always wondered why it was implemented like this. It seems like it was a workaround for not having timeline scroll/zoom bars in player window. Why not show in/out markers independent of the overall clip length, and leave all the footage accessible to me on the player timeline to move the in/out markers? Perhaps for longer clips this would require a zoom/scroll bar for the timeline. So be it. It is sorely needed.

2) The user specified in point of a clip is displayed nowhere, except in the current frame position field if the playhead is at the top of the clip. Less Information = More I Screw Things Up.

2a) I forgot what the key command is to clear in/out points on a clip in the player window. It's not 'x', option-X, apple-X, control-X. ...help...

3) In/out points and currently rendering frame number are not displayed in the batch monitor window. See Less Information Axiom above.

Thank you Red for all the hard work!

Bryan
 
Feature request:

An undo history for each clip, which I could step forward/backward through, like in Adobe Lightroom, in the Develop room. :-)

Bryan
 
Feature request:
(and more realistic alternative solution to above post)

A key command for adding the currently applied look to the presets.

Default look preset name (specified in prefs) = Project name_ClipName_##

So for example, if I try out three different grade ideas on a clip, and press command-L each time I'm happy, I get:

PROJECTNAME_A001_C001_01
PROJECTNAME_A001_C001_02
PROJECTNAME_A001_C001_03

And then, if the above wasn't too difficult, great - stop there. Later, add ability to sort look presets into bins in the Look Preset window, and let user set default bin for capturing new presets.

Food for thought. :-)

Bryan
 
You must log in or register to reply here.
Back
Top