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

These settings crash RedRushes EVERY TIME

Tim Fassnacht

Tim Fassnacht

Well-known member
Joined
Sep 6, 2007
Messages
196
Reaction score
0
Points
0
Hey Red Gurus,

I've tried rendering out Apple ProRes SQ, 1024x576 qt's with a 1024x426 (2:40) crop and burn-in using Camera's look about 15 times now from both my 3.0Ghz MacPro and a MacBook Pro and it crashes EVERY TIME before starting the render. Then, strangely, when I change the burn in window and font colors back to defaults it miraculous renders. WTF? Yellow over Grey burn-in is ugly.

Logs attached. Any ideas appreciated.

Thanks

Tim Fassnacht
Los Angeles, CA
 
It's changing the foreground colour for burn-in that crashes it. Like you said, every time.

The BG colour you can change to your hearts content, as far as I can tell...

I agree, white burn-in text would be much nicer, but let's face it, it's not a huge issue!

HTH,
Dom.
 
I think it might depend on the codec as well. I can change foreground and background when making DNxHD 36 with the latest version of REDrushes and it does not crash. Something to loo into on your end.

I changed foreground, background size and position successfully.

Michael
 
That's interesting Michael - I'll look into it, thanks for the info...

My info from ProRes422 HQ transcodes to 720p, for reference.

Should also add that I can happily change font, size and location with no problems, along with BG colour and opacity - it appears to be only the FG colour change that causes the crash.
 
I'll try 720 - all my tests were as 1080. May be that as well.

Michael
 
Nope - 720p worked fine - changing everything possible.

Michael
 
I have found the same problem in Clipfinder.
After some research, it turns out that some of the swatches in the Apple Color Panel are apparently defined in a different color space than RGB and that it is illegal to extract RGB components from an NSColor object which is not in the RGB color space.
I have been able to fix the problem in my lab version of Clipfinder by inserting the following piece of code
NSColor *c = [[settings objectForKey:BURN_TEXT_COLOR] colorUsingColorSpaceName:NSCalibratedRGBColorSpace];
The corrected version of Clipfinder is available from my website.
As a workaround in REDRushes, the problem can be avoided if you select a gray swatch and then drag the brightness slider to all white (rather than selecting the white swatch).

Cheers,
Hans
 
Martin Weiss said:
Hans-Georg really deserves a technical REDOscar.
Click to expand...
I'll second that - Hans, you're a genius, thanks mate!

And thank you Michael for the testing your end, also very much appreciated information...

I wonder why (maybe this is obvious to those with more nuts'n'bolts know-how than myself) the issue raises it's head with PR422 and not DNxHD? Any ideas?
 
From what I have found I'd assume that the error is independent of the codec setting.
I guess the different test results can be explained by the fact that people have used different approaches for setting the text color (clicking on a color swatch may cause the problem, moving the brightness slider seems to avoid it).

Cheers,
Hans
 
Ah, yes, that would make sense - I'll have to do some testing at my end as well, but Michael - what was your method of changing the text colour?
 
I always did my color selection via the slider which would explain why it worked with DNxHD.

Michael
 
Ladies and Gentlemen, we have a winner!!

Thanks again Hans and Michael for your time and input, all useful stuff. One still has to wonder who's the choice of a horrible yellow text colour as default was?! :wink:
 
Hans-Georg Daun said:
I have found the same problem in Clipfinder.
After some research, it turns out that some of the swatches in the Apple Color Panel are apparently defined in a different color space than RGB and that it is illegal to extract RGB components from an NSColor object which is not in the RGB color space.
I have been able to fix the problem in my lab version of Clipfinder by inserting the following piece of code
NSColor *c = [[settings objectForKey:BURN_TEXT_COLOR] colorUsingColorSpaceName:NSCalibratedRGBColorSpace];
The corrected version of Clipfinder is available from my website.
As a workaround in REDRushes, the problem can be avoided if you select a gray swatch and then drag the brightness slider to all white (rather than selecting the white swatch).

Cheers,
Hans
Click to expand...

Hans-

You continue to impress me. Thanks man.

Best,

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