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

Random black frames won't go away...

Random black frames won't go away...

Me too:

eric a wahl said:
The black frames are random..
Not in the same place if I export again.
Sometimes not at all.
Click to expand...

I have tried different solutions that usually have solved export problems like these in the past but to no use:

- throwing away everything associated with REDCINE-X 104 and then re-installed REDCINE-X, done this several times
- also re-installing the REDCODE QT 3.9 and RED FCS 3 vers. 20 plugins
- repairing properties using both OS 10.6 disc repair and DiscWarrior
- using most features of Snow Leopard Cache Cleaner (demo)
- exporting to different drives
- tried Snow Leopard both in 32-bit and 64-bit mode

Carl Dieker said:
I am running build 104 on a 2009 MBP 17" w/ Snow Leopard. The material is shot both in 4k 16:9 and 4.5 WS at REDCODE 28. Export settings are 25p 2048x1152, ProRes HQ.
Click to expand...

The funny thing is that I don't have any random black frames in my exports from REDCINE-X 104 when I am booted in 10.5.8 instead of Snow Leopard.

I really would like to use REDCINE-X 104 in Snow Leopard since it has native 2.2 gamma.

I hope that we can figure out this one soon.

Thanks,

Calle

PS: Deanan, I will pm you a Verbose log soon.
 
Last edited:
Got random black frames as well (.tiff export). Redcine-x 104 on windows vista 64.

I also can't save projects. No save dialogue window pops-up :(
 
Same black frames issue here.

I transcoded shots on an unibody 17" Macbook pro with RCX build 104 (4K HD half good debayer and 2K 16/9 full debayer, RC36, 25P, Sound on Channel 1) to 1920x1080 Avid MXF DNxHD36. Just got a call from the director, he's having the black frames too, randomly.
So it's not just QT.
 
save/export Look preset files

save/export Look preset files

is it possible to save - actually export - an individual look preset? I want to send different look files with their R3D files to another computer. In a previous version of RedCineX the look files were saved into: user/library/application support/red/recineX/looks (Mac) but they don't seem to appear there now, or am I missing something.
Thanks for any help
 
Hey Deanan,

I just emailed you the log file. Still get random black frames, even in verbose logging mode.

Best of luck!

Calle
 
After a few different sessions in RCX 104 I've got a few suggestions.

- Better keyboard shortcut functionality (select all rarely works depending on bin, timeline etc.)
- Ability to set presets for curves tool (the ones built in are pretty odd)
- I find it hard to tell clips apart from eachother on the timeline (aside from clicking on them one by one) anything that can be done to cleanup the cluttered look of the timeline would be great.
- Folders for look presets ( I do a new shoot almost 3 times a week and have lots of presets, its frustrating to scroll through them all )
- RSX style grade memory. When you grade in redalert, your grade automatically follows the clip with a history of each time you've opened the clip in red alert. This was great for when color science changes were implemented because footage we re-processed after had a history to it, so small changes could be made to keep the look but improve the color
- Make the adjustments done in the framing tool reflect in the clip browser
- Obviously (like everyone is saying) XML support for final cut etc.
- Better scaling for tools, I can't fit half the tools I need on my 13" macbook pro but worse, even on a 24" 1080p monitor the program feels very cluttered.
- Please remove the textured dirty scratchy look from the program. The 'pro' app grey will do just fine, I've had several co-workers and clients ask why my screen is so dirty, ugly or just simply why the program looks like that. Its ugly and its just not a clean look like after effects or color.
- The Zebra button from red alert would be nice.

I think thats all for now, Love the color science, not totally sold on the interface just yet, and yes I am aware its still a beta.
 
Deanan said:
Not enough details to know if or how it would be flawed.
Click to expand...

Color and RCX seems to develop the RAW files (more or less) identical with identical settings - except for gamma differences.
Redline/clipfinder seems to develop more detail and less noise with the same base settings

Being:
320 asa
-0,4 exposure
redcolor for RCX/Color/redlog for redline/clipfinder

No sharpening or de-noising applied

Looks like to me.
There's some sort of DRX "magic" happening in the highlights in the RCX/Color files.

Will test RedRocket renders tomorrow...


G
 
Gunleik Groven said:
Color and RCX seems to develop the RAW files (more or less) identical with identical settings - except for gamma differences.
Redline/clipfinder seems to develop more detail and less noise with the same base settings

Being:
320 asa
-0,4 exposure
redcolor for RCX/Color/redlog for redline/clipfinder

No sharpening or de-noising applied

Looks like to me.
There's some sort of DRX "magic" happening in the highlights in the RCX/Color files.

Will test RedRocket renders tomorrow...


G
Click to expand...

The main difference is in the color science between the older redline and the new color science in RCX. The new color science goes for more accurate color, easier grading and better skintones. White balance is key with new CS also. The blue channel will like differ because of the way the color space gets transformed but the the overall image is what improvements are targeted for rather than a specific channel.
 
Aaron Hucker said:
After a few different sessions in RCX 104 I've got a few suggestions.

- Ability to set presets for curves tool (the ones built in are pretty odd)
Click to expand...


You can do this now. Adjust the curve ..and then hold down a 'preset button' until the dots on the curve enlarge...preset set!
 
Deanan said:
The main difference is in the color science between the older redline and the new color science in RCX. The new color science goes for more accurate color, easier grading and better skintones. White balance is key with new CS also. The blue channel will like differ because of the way the color space gets transformed but the the overall image is what improvements are targeted for rather than a specific channel.
Click to expand...

I can see very well that the channels behaves differently under new and old CS, and that the WB/K sliders work in a much better way.

I haven't only looked into the blue channel - thus I posted the DPXs for others to peek. But I'll do more tests, and post RAW files with them to try to dig into the things I see that I ponder on...

It seems that some detail is given up for over all better image.
But as long as it is for a greater good....
And that one allows for more noise
NOT that that is a bad trade-off.

Color and RCX now renders identical DPXs with the same settings - except from gamma-shift.
Quite impressed with that.
I wouldn't have thought so...
 
Build 158 stuff

Build 158 stuff

Build 158 Stuff

1) Not sure if this is a bug, but it feels like one - every time I drag a different clip from the browser into the player window, the resolution for the player reverts back to 1/4 res. (Well...strangely...as I write this and play with 158 at the same time, it has suddenly stopped behaving this way...I'll leave this one here in case it's reproducible elsewhere).

2) Not new to 158 - just renewing my request for a finer degree of precision with the controls...exposure, FLUT™, the curve breakpoints, etc. All drastically affect the image with only the slightest movement, and the slider movement is kind of "jerky" making it hard to move the slider precisely, even when adjusting with 1/4 res on a fast computer. Please add a fine-adjustment mode (ie, command-drag or shift-drag a slider to move with slow/fine precision)

3) Expanding upon #2, with emphasis on the curves controls - there is no numeric indicator for the x-axis of the breakpoints. If I want to crush the blacks by moving the "shadows" breakpoint to the right, I have no value to read and refer back to as I experiment with the position. Particularly with curves, as related to #2 above, because the controls don't move easily with fine precision, and because curves points have no readable x-axis value, I can't just type in a value as I might with the other slider controls after eyeballing where I want the breakpoint to be. It's just more imprecise that it needs to be right now. Please add some zeroes to the right of the decimal point, add fine-precision (shift or command-drag) to adjust values, and please add x-axis numerical value readout & entry for the curves breakpoints.

4) Minor UI stuff - if you click in a text value field (ie, Kelvin, Tint, etc - any of them) to edit the value, and then click outside of the text value field, the field is not-deselected. The cursor remains blinking within the text field. If you enter a value and press return or enter, the whole value gets selected, but the field still has the focus for editing. Escape key doesn't get me out of it either. Good UI would be enter/return enters the value and deselects the edit field so it isn't inadvertently changed thereafter. Clicking outside of a text field should also deselect the text field. Tab/shift-tab works as expected.

5) I love the feature where footage at any resolution renders forward from the playhead position for real-time playback with audio in the viewer. However, the rendering seems to be much slower in this build. It it just me?

6) The Preset 1-7 buttons in the curves window - how about command or control-click to store a preset in P1-7 buttons, instead of having to hold the preset button for almost three seconds? It's so slow the way it is now.

7) Another minor UI suggestion - when resizing the image in the player window, ie, from 1/4 to full resolution, then I drag the window to view perhaps the far upper right portion of the image, then when I switch back to 1/4 res, the viewer window turns black. My movie has disappeared! :-) Well, actually, it has just snapped down to the bottom left corner of the viewer, out the visible area, and I have to use the hand to drag it back. (This is when I'm working on a MacBook Pro with the overall viewer window size set to view a 1/4 res image at 100%). When resizing the player resolution downwards (ie, from full to 1/4, etc), it would be nice if Redcine-X re-centered the image in the viewer window.

8) New terminology in the export window debayer settings - "1/2 Premium" and "1/2 Good". Is that essentially the same as "1/2 High" and "1/2 Standard"? If it's the same...well...I prefer the old terminology. For one, it's simply easier to say. Half high. Half standard. It's concise. It feels like well crafted post-production terminology. Actually, it has become deeply ingrained terminology in post-production, ie, "Render the offlines at 1080, half standard". Whereas, "Premium and Good"...kinda subjective, don't you think? Not to mention, the term "half good" doesn't exactly make an editor or director feel warm and fuzzy about the quality of his offline. :001_rolleyes: Perhaps this is intentional, so we'll stop rending those crappy "half good" offlines and buy a RedRocket to blast out the "Half Premiums"? :-) Anyway, I wouldn't go to bat over this one. Just mentioning it in case it the new terms were simply placeholders. :-)

9) Dumb question - why have the framing controls separate from the export controls window? Don't the framing controls only pertain to exporting footage? This occurred to me as I was setting up a new export preset, where it's all arranged very nicely in the export preset dialog. Then I exported a test clip, and realized...oops...I forget about the crop settings I wanted. Well, I did that because they are in a completely separate window which was nowhere near my export window. This new UI is definitely flexible, but in some ways...respectfully...the modular floating window concept has been taken slightly overboard in Redcine-X. I like the way Adobe has developed their UI in cs4, where you have tabbed floating windows, and you can drag and drop any tabs (ie, Image, Framing, Export, etc) from any floating windows into other floating windows and reorganize them in whatever way you like best. I bring this up only because, in the case of my framing controls, I would like them to always be right next to my export controls. Food for thought. I know it's all very subjective with UI. But I want it my way. :tongue_smilie:

10) Redcine-X is the FLUT™shizzle. :-)
 
This is probably mentioned before...but will there be more key commands in the future, particularly for things like marking in/out points, etc?
 
Export Settings dialog:

1) It would very useful if there were some columns in the Export window, next to the preset names, which displayed the parameters for a given preset. ie, Audio, with little check marks for a 1234 in a column beneath, as well as debayer resolution, output res, format, etc. When the Export window is resized horizontally, there would be room to see all that stuff with little lights or checkmarks beneath column titles, if it was displayed there. Would be helpful so I could verify my export preset settings at a glance, and not have to methodically name all my presets with the underlying parameter values, and/or dive into the edit dialog to confirm settings before exporting.

2) The windows that appear to edit a preset (the Export Settings window and Debayer Setting window) are global modal dialogs which look identical to all the other windows in Redcine-X. I work on a laptop with a 2nd display connected and disconnected frequently. Redcine-X's modal dialogs sometimes appear off the edge of the main display, locking up the interface, if the 2nd display has been disconnected since last using the program. Window Reset command works, but this could use some refinement. Modal dialogs should be distinguished from regular windows, and appear directly in front of windows they relate to.

2b) Bug - open Export Settings. Press command-period to cancel and close the window. Works. Open Export Settings, then open Debayer Setting window. Press command-period to close Debayer Setting window. Works. Press command-period again to close Export Settings window. Doesn't work.
 
Build 158

User error resulting in a bug:

1) Export a clip with "Clip filename to selected folder". In my case, I'm test exporting a clip from the viewer.

2) While Clip #1 is exporting, "accidentally" press the export button again in the export settings window, which still has the same preset selected, and which is still referring to the same clip in the viewer.

Result: Clip #2 is added to the batch list. The file in progress (Clip #1) immediately disappears from the designated folder in the Finder the moment the export button was pressed the second time, but meanwhile, the batch list continues to show progress on Clip #1, and then proceeds with Clip #2 as well, but no file exists in the designated folder from the moment the export button was pressed a second time. Neither clip is rendered.

That's a lot of pain and suffering for accidentally double-tapping the "export" button. :mad2: :biggrin5:

Can we have a "Do not overwrite" checkbox in the export settings window? Can Redcine-X prompt before overwriting a file? Is Redcine-X using Redline, or...? I don't see a separate process in Activity Monitor. I ran into this before, where it just blows away existing render files without warning. Wish it didn't do that. :emote_hanged:

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