RGB Color Corrector errors since update 6.0.2

Hey guys,
since i've updated Premiere Pro CS6 to version 6.0.2 yesterday, all projects in which i use the RGB Color Corrector have errors while rendering the work area. Rendering is not possible until i delete the effect. Same problem with new projects.
Are there any solutions? Do you have this problem too?
Patrick

Jim,
thanks for your input, but I have 7.5 hours of video that is ready to go out the door to a customer who is waiting. I don't use creative cloud because at 68 the last thing I want is a new learning curve every few weeks. I have a few years of learning and have been very successful producing video that is very good for my needs. I just want to have the product that I have been using for all this time, to work correctly. If the RBCC problem has been fixed in the CC version, then why is it not available to someone who has clients who depend on their work, but happen to be using the standalone version. I'm sure that the cc version is really good and there will always be new improvements, but for lectures and seminars, CS6.0 is great. I would just like to know who to contact at Adobe to get the fix for this. Someone said somethinhg about going back and using the 6.1 version, which maybe means a reinstall. I don't know when I updated to 6.3, but I'm not sure if it came with the disk upgrade I received late last year.
I was on hold on the Tech phone line for an hour, and gave up. Will try next week. So far, the only people at adobe who have made themselves available to actually help me are the people who sold the program to me.
If there is an update to fix this, why can I not get it. Do you have a number I can call at Adobe?
Sorry for the rant but Adobe leaves me feeling quite alone with a product that I have used, recommended, and had good luck with, util now when I have a problem.
Rick

Similar Messages

Error Compiling when using RGB Color Corrector and Unsharp Mask

If I apply the RGB Color Corrector and and Unsharp mask to a clip within a sequence and try to render the sequence or a small portion of the work area I get the Error Compiling: Unknown error.
This is occurring within a project I have updated to Premiere CS6 from Premiere CS5.
I have tried creating a new sequence and importing the same clip and other clips. Anytime I try to use both the Unsharp Mask and RGB Color Corrector I am unable to render. I have tried this with Mercury Playback both in hardware and software modes with the same result.
Has anyone else seen something like this?

Okay, glad this occurs for others too and I am not experiencing something isolated. The issue here is this shouldn't be happening at all.
Premiere CS5 has no problem with this.
Yeah if I turn off one effect or the other no problem. Unfortunately it doesn't matter the order I place the effects in I get the same error regardless of which is placed first.
Nesting does work. If I create a sequence, apply one or the other to the clip in the sequence then embed the sequence in another sequence and apply the remaining filter to the sequence containing the clip then I can get my color correction and edge definition. But this is a work around.
There seems to a bug here since there were no issues when using RGB Color Corrector and Unsharp Mask simultaneously applied to one clip in CS5. I doubt there will be a fix for this anytime soon so it looks like I will have to use another method for color correcting or apply RGB color correction to clips already embedded in a sequence as I move forward into solely using CS6.
(How this can become an issue is that after applying effects and color correction to several clips within a sequence I like to render that entire sequence. Then this sequence is ebedded in another main sequence and I can add additional effects and transitions and overlays without killing the live playback speed and only have to render smaller amounts of content from additional tracks. It ends up saving a lot of time after the initial length of rendering.)
Thanks for the suggestions.

Premiere Pro stops rendering and gives error message when encounters "RGB Color Corrector"

Premiere Pro (and also Encore) stops rendering and gives error message when it encounters a clip containing the "RGB Color Corrector" in any clip. It will process clips without RGBCC, but will stop when it gets to one with RGBCC activavted. PP will render clips if other effects, such as "Fast Color Corrector", "Color Balance (HLS)", and "Three-Way Color Corrector" are selected. However, these do not have the capabilities that The other color correctors will not do what RGB color corrector does, so I need to have this working to finish a large product that is due to the client. Please help me..... I am not using the Creative Cloud version, and can't find either a download for the new update from 2013, or a phone number to talk to anyone.

Using a Win7 computer with 2.8 quad core processor, 24 gig of ram, Nvidia Quadro 5000 video card. Don't think I have any plugins. I looked at one a while back for cleaning up grainy video, but I am not sure I paid for that. Think I deleted it.
Incidentally, someone named Jim on another part of the forum mentioned that this problem has been fixed in the CC version of the program. I am using the non-CC version because I am 68 years old and only do seminars and documentation video. Don't need so many bells and whistles, and definitely don't need learning curves every few weeks. CS6.0.3 works fine for me. By the way, someone else said that maybe version 6.0.1 might work better and I should revert to that. Not sure if it is the version i have on the disk upgrade to 5.5 that I purchased in December.
As it stands now, I have 7.5 hours of a seminar that is ready to go out the door. If there is an upgrade I can get from Adobe, maybe you can tell me about it. If I have a setting incorrect in the video output format, maybe I can change that. So far it just happens with clips in my video that have RGB color correction.
Rick

CS6 Using RGB Color Corrector effect, Reference Monitor will not update?

When the current tine indicator is on a clip using RGB Color Corrector effect, the Reference window will not update.
And not only doesn't it update the data on the graph, but if you change the type of scope (Display Mode) (e.g. from RGB Parade to Vectorscope), that also doesn't change until you move the CTI to view a clip without the RGB Color Corrector effect on.
Anybody can help me to fix this problem, it is very important to me, many thanks!!!

Take a look here: http://help.adobe.com/en_US/premierepro/cs/using/WSCB566F37-A8BA-4b43-8BD2-B6467AAE930E.ht ml
Here the appropriate quotation from the help:
Gang the Reference Monitor and Program Monitor
You can gang the Reference Monitor and the Program Monitor so that both always monitor the same frame.
Do one of the following:
In the Reference Monitor, click the Gang To Program Monitor button .
In the Reference Monitor’s panel menu, choose Gang To Program Monitor.
In the Program Monitor’s panel menu, choose Gang To Reference Monitor.
Both Monitors show the same frame. Moving the playhead in either the Reference Monitor, the Program Monitor, or the Timeline will move the playheads in the other two to the same frame.
Regards
Axel

How to get RGB color corrector back working with YC waveform monitor

so, as many of you are probably aware, Adobe's latest update killed the RGB color corrector, at least in terms of using it with the YC waveform monitor.
In this thread ( http://forums.adobe.com/message/4825916#4825916 )
someone says-
"Yes it's a Bug since the 6.0.2 Update. I replace the effect in the premiere plugin directory with the same from version 6.0.1 and it's working again"
how can I go about doing this?
I looked on another machine running premiere 6.0.0, but I am not seeing a plugin for RGB color corrector in C:\Program Files\Adobe\Adobe Premiere Pro CS6\Plug-ins\Common
and I don't know what "RGBColorCorrector.cubin" is in C:\Program Files\Adobe\Adobe Premiere Pro CS6\PTX\cubin11
bottom line is that I want the RBG CC back working with the YC waveform monitor again.

also, I saw that initially, but assumed it was only used by after effects, due to the AE in the name, and that windows classifies it as an "adobe after effects effect".

CS6 BUG: Reference window and RGB Color Corrector

An interesting bug in Premiere Pro CS6.
It took me a while to work out what the common factor was, but it now seems to be the RGB Color Corrector effect.
When the current tine indicator is on a clip using this effect, the Reference window will not update.
And not only doesn't it update the data on the graph, but if you change the type of scope (Display Mode) (e.g. from RGB Parade to Vectorscope), that also doesn't change until you move the CTI to view a clip without the RGB Color Corrector effect on.
I have tested this with both Red R3D files as the source and image sequences. Same thing in both cases.
Extra info:
OS is Windows 7-64 bit

If anyone is still having trouble with this issue, here is a link to download the 6.0 version of the RGB Color Corrector plug-in. Just grabbed it from an old install, and replaced the file in the Plugins folder and it worked perfectly.
https://drive.google.com/file/d/0B9ULtCJ4GoxhTndMX0MxdGZfVmc/edit?usp=sharing

Tonal Range Output not working in RGB Color Corrector Effect!

I am using a MacPro:
Processor 2 x 2.93 GHz 6-Core Intel Xeon
Memory 32 GB 1333 MHz DDR3 ECC
Graphics NVIDIA Quadro 4000 2048 MB
Serial Number H01231DQGWR
Software OS X 10.9.5 (13F34)
In RGB Color Corrector Effect I cannot get the Output option of Tonal Range to work!
I have tried it with various files/projects. I have restarted the computer. I have uninstalled Premiere and downloaded again.
Nothing I have tried has made it work.

Neither can I.
Please file a Bug report
On windows its working like expected.

Invalid Color Space error after update Reader to 9.3.3

After updating Adobe Reader to 9.3.3 I run into the Invalid Color Space error when trying to open a PDF file created with CorelDraw 12 in the format PDF/X-1A. This format needed by a printing office to print the file. The strange thing is that Reader opens older PDF files exported from CorelDraw in thsi format normally without the error message.
It happens only with PDF exports made after the Reader update. CorelDraw settings are as previously used.
Exports in other formats, other than PDF/x-1, X-1A and X-3 open normally. How to solve this??

any suggestions?

MXF frame read errors and general render errors since update to CC

Hi there folks,
Being a Creative Cloud member for a while now I share the benefits of immediate updates of CC products. However, I also get to deal with the downsides, it seems.
Since I updated to CC versions of the entire Adobe Collection I experienced unprecedented trouble with After Effects. I'll mention the most pertinent errors:
- I used to render short compositions to uncompressed HD Quicktime, functioning as a master render for future sorts of output for my clients or just to have optimum quality before further conversions. For some reason AE CC has been generating all sorts of video dropouts lately, especially when audio render is set to 'auto'. Furthermore I noticed that the only audio res that I can choose in case of an uncompressed QT render is 8000 Hz. This is new in AE CC, I don't understand the reason for this modification since the previous AE versions never had this limitation.
I must mention the fact that other output formats and codecs also suffer from dropouts, be it less frequently than QT uncompressed.
- Imported MXF files from my customers which I incorporate in AE compositions are also full of dropouts. Every dropout shows up as a single frame (two fields) of red or black. Premiere Pro encounters the same problem and reports the dropouts as frames with a read or decode error. I checked some older MXF files in previous AE projects that have been rendered and delivered perfectly in the past, but these old MXFs now appear to have the same issue. I tested the older and the new MXF on another PC that wasn't updated to CC versions and found no dropouts at all. Something must have changed in the updated codecs that belong to the CC version. All MXFs play fine in VLC player on all systems, so it's not the video source being faulty. Anyone recognize this?
I do get notifications of CC product updates, but is there a way to just update the codecs? Maybe there is a better codec for MXF.
Any help is truy appreciated!

Like often, it's better to wait a little until there's enough people experiencing the same problem. So everyone here: thanks for responding to my post! In the end it seems to have helped, considering the update of Adobe. I am still a little precautious, because some MXFs give no red frames at all (input side I'm talking about) and others still do, but then the strange thing is that scrubbing the MXFs forth and back a bit results in having less red frames to none at all in the end. The red frames now disappear and then re-appear on different points in time of the MXF file, whereas I always found them being bound to specific and unchanging points, especially on the first frame of a scene change for instance.
Anyway, Adobe Media Encoder is not suffering from this problem, so there is a workaround, converting the footage before using it in AE and Premiere. That's good enough for now. But the problem hasn't vanished yet. Another problem that I had with rendering uncompressed HD Quicktime videos that always generated dropouts has all of a sudden magically disappeared. Thanks Adobe. I see progress.

Custom Page Size Printing Error Since Updating to Mavericks

Can anyone help me please...
iMac 10.9.4, with Adobe CS4 suite and Adobe CC Suite installed.
I have recently updated to Mavericks and since the update my custom page sizes no longer print at 100%, custom sizes all get scaled down (i presume to fit sheet) and leave me unable to print jobs out at correct size.
The custom page sizes work for builtin apps such as Preview, but my CS4 suite no longer work correctly. I have also tried using Acrobat CC and that gives me the same issues too.
I have googled the problem but have not found a solution and it seems i am not alone either.
Please help as this is rendering my ability output as useless.
All the best
Andy Barrington
[signature deleted by host]

This problem is from all Adobe CC & CS4 products i use: indesign, illustrator, photoshop, and acrobat.
My main staple work process is using pdf exported from indesign then printed using acrobat.

"Safari can't find server" errors since updating to 6.0.5

Hi,
Anyone else experiencing consistent errors from Safari after the latest update? Once I've updated to the new Safari on my Mac (on Mountain Lion 10.8.4), the errors start to appear on my of the URLs that I'm trying to access. I tried Chrome as well and it's the same issue.
I'm also having Network Connection errors in iTunes when updating apps.

Triple-click the line of text below to select it:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -f -a TextEdit
Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open. Post the contents of that window, if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that.

Spotlight "disappearing"? New since update to 10.4.5

I'm experiencing a major Spotlight error since updating to 10.4.5 through Software Update.
In my menu bar, I have a few items. From left-to-right: an e-mail monitor, a SMART status monitor, my Fast User Switching icon, the clock, then Spotlight. When I pop open the Spotlight menu item, it only stays open for 1 or 2 seconds after I start typing before disappearing, along with my User Switching icon. The menu bar then rebuilds itself.
Furthermore, I cannot open the Spotlight window at all. And, when I try to search in a Finder window, Finder crashes and restarts itself.
Has anyone experienced these problems? If so, is there a fix?
Mac OS X (10.4.5)

Same here. Just started happening today. Have no idea how or why.
Then I reindexed the volume (syst prefs: spotlight: ad and then remove your HD volume to the privacy list)
And now it works again.
S.

Premiere Pro Freezes mac while rendering Fast Color Corrector & Rgb curves

I am having a problem that is impacting our business. We are doing commercials that we are doing color correction of the subject using Fast Color Corrector and RGB curves. When these effects are added to the sequenced video, the performance of the Mac Pro slows down considerably.
Then when we go to render the project so that we can see the effects in real time, the computer freezes completely. The program usually informs us that it must close due to a serious error. I have attempted to restart the computer, clean up permissions etc to solve this problem but to no avail. Why would this happen? Any ideas on how to solve it?
Here are the specs:
Using Premiere Pro CC 7.2.1 (4)
Mac Pro: 3.2 Ghz Quad-Core Intel Xeon
Memory: 24 GB
ATI Radeon HD 5770 (1024 MB)
OS: 10.8.5

Yes. I experimented on my own and got confirms from a couple of sources. Where the problem was is bad suggestions about what settings to use in Premiere Pro.
The first setting you want to check (although Premiere Pro will probably see the card right away is:
File > Project Settings > General - Make sure that Mercury Playback Engine GPU Acceleration is selected. Everyone agrees on this.
Now is where the fun begins. There is a school of thought that says to go here:
Sequence > Sequence Setttings - Under Video Previews, they want you to check off Maximum Render Quality. Once you do this, you must also go to:
Preferences > Memory - and change Optimize Rendering for Performance
DO NOT DO THIS! What I found is that this significantly slows down your system and makes rendering and exporting take over your computer (and I have a lot of ram). Leave your change with the setting Mercury Playback Engine GPU Acceleration and you should be great.
I have found a significant change in running color correction effects, exporting and rendering. You will too.
Let me know how you make out after your setup.
Have a great day!

Ever since updating to new OS, my iphone won't sync to itunes. When I plug in the phone to the PC, it says I need to update itunes to 10.6.3 or later. I did, but still get the same error message.

Ever since updating to new OS, my iphone won't sync to itunes. When I plug in the phone to the PC, dialog box says I need to update itunes to 10.6.3 or later. I did that update, but still get the same error message.
Can anyone offer suggestions?
Thanks!

Since it told me to update, I updated to 10.7.
Then when I plugged in the phone again, it gave the same message that I need to update itunes.

Since updating to Firefox 3.6.15, I can no longer print coupons from SmartSource. The error message is that Java is not detected. The check box is longer showing in the Options/Content of this version of Firefox, so I can not enable it.

# Question
Since updating to Firefox 3.6.15, I can no longer print coupons from SmartSource. The error message is that Java is not detected. The check box is longer showing in the Options/Content of this version of Firefox, so I can not enable it.

Same PC as I used to post the question. When I go to the "plug in check" page, it shows I am up to date and it is not disabled.
Java(TM) Platform SE 6 U24
Next Generation Java Plug-in 1.6.0_24 for Mozilla browsers 1.6.0.24

RGB Color Corrector errors since update 6.0.2

Similar Messages

Maybe you are looking for