[Jaeson Koszarsky]

I get these errors on/off too when importing media from shared drives, even though I have full read/write permission.

[Jaeson Koszarsky]

Forgot to mention the random garbage glitches that regularly appear in renders. If I un-render the selected clip and re-render, the problem goes away. It’s usually a small block(s) of garbage isolated to one area of the image. I think it happens more often with the application of a filter to a clip in the timeline.

[Jaeson Koszarsky]

I experience intermittent lock-ups EVERY DAY when exiting RED5 back to Media100 Suite2.1. I just force quit Media100 for the third time today. VERY FRUSTRATING.

Other bugs that have been bugging me lately are related to how RED5 mishandles my pre-comps from old projects. Masks don’t stick as they did in RED4. Drop shadows are a problem too with pre-comps. There’s also a weird aspect ratio glitch with graphic files in old projects.

I like the speed of the new MacPros but there are too many days when I’d go back to using the more stable G5 Media100 & RED4 set-up if I could.

[Jaeson Koszarsky]

I’ve done the validation, removed any fonts that were flagged but things still don’t work correctly. Both of our MacPros exhibit the same problem with fonts.

Can I reinstall the OSX fonts from the install discs without re-installing everything else?

[Jaeson Koszarsky]

Apple ProRes 422
Media100 Suite 2.1
OSX 10.6.7

[Jaeson Koszarsky]

I’m working in NTSC SD 4:3. When the program was in progressive mode, Boris titles rendered txt/gfx as if those elements were single field but the video layer looked ok.

When I first saw it, I thought the Media100 STOP MODE was set to DISPLAY FIRST FIELD or DISPLAY SECOND FIELD, rather than DISPLAY BOTH FIELDS.

Before discovering my error, I tried applying my txt/gfx in the video clip itself, as a title track overlay and as a composition clip overlay. All with the same problem in the Media10 progressive mode. Looks sharp un-rendered but not when rendered. I also when for something less complicated and used a simple text only layer and it exhibited the same problem upon rendering.

I also tried turning the RED “better quality field rendering” option on/off.

After changing the media100 back to Interlaced NTSC SD mode, the problem disappeared.

Jaeson

[Jaeson Koszarsky]

Thanks. I reached the same conclusion with fresher eyes this morning. I usually work in interlaced mode and must have clicked the progressive option accidentally. After switching back to interlaced and re-rendering, everything was sharp again.

Does RED have a problem with progressive output in general or only in conjunction with Media100?

Jaeson

[Jaeson Koszarsky]

When using deflickering, I often use it on its own RED layer/project. I then apply logos/text/other in another non-deflicker layer/project above that. You’re right about deflickering making some things too fuzzy.

It’d be helpful if BorisFX would include an on/off option for deflicker on individual layers within a single project in some future update of RED. Motion Blur can be turned on/off for individual layers.

Resizing the large PSD in PhotoShop often yields better results than rescaling in RED and by reducing that image data that needs processed, you speed up your renders.

You can also apply pre-blurring in PS to regions of the image that are particularly troublesome.

Have you tried the smooth-tone filter? I might give it a go the next time a situation calls for it.

Jaeson

[Jaeson Koszarsky]

Have you tried the deflicker option under edit/project settings?

If you are moving the PSD around, try applying motion-blur.

Do your PSD files need to be as large as they are? I will sometimes scale them down in PhotoShop prior to using them in RED if I know I won’t need that much resolution. It saves some render time and the results are usually better looking.

[Jaeson Koszarsky]

Just in case anyone is wondering about installing QuickTime 7.6 (not 7.7) under OSX 10.6.x, if they only have QuickTimeX, I did this not too long ago.

You’ll need your install disc. Insert the DVD. When the Mac OS X Install DVD window appears, select the Optional Installs folder, then double-click the Optional Installs icon. When you get to the “Custom Install” list, you can pick QuickTime 7.

Once installed, you will find QuickTime 7.6 in the Applications/Utilities folder.

You can plug in your QuickTimePro activation code if you have one.