Adobe Community : All Content - All Communities

mp3 audio disappearing on export in 2014.1 (8.1.0)

forums_noreply@adobe.com — Thu, 30 Oct 2014 18:58:19 GMT

I hate to use MP3 audio, but my client provided a bunch of them (around 20) as audio clips in a video I cut that ended up being 45 minutes long.

Everything was fine as I was editing, but two of the clips went silent on my exported movie. Both of the missing audio clips had a Constant Power audio dissolve applied to them at their in-point which was a dissolve from another MP3 clip. All my audio clips have Constant Power fades at the ins and outs (Most of them are from silence (a gap) or to silence.).

The audio just disappeared on export when the fade was applied from a first MP3 clip to a second one, with the audio from the second one disappearing on export.

I worked around this by using the new Render and Replace feature in 8.1 before exporting. So, head's up to anybody else using MP3 audio files in this version of Pr on Mac.

MacPro3,1 10.8.5

New CUDA Driver 6.0.37 for Mac: Safe for Pr CC?

forums_noreply@adobe.com — Wed, 30 Apr 2014 19:23:15 GMT

As some of you learned the hard way, the CUDA driver version 5.5.47 was a no-go for Premiere. Now, the nVidia site has version 6.0.37 available (which I suppose is a Mavericks 10.9.x compatible upgrade. I'm still on 10.8.5).

Has anybody tried it with Pr, and found it to be a benefit over 5.5.28, the last compatible version?

two versions on the same machine

forums_noreply@adobe.com — Sun, 12 Oct 2014 18:36:41 GMT

Because I'm not ready to risk committing to the latest build of Pr (which I'll call "2014.1" or ".1" for the purposes of this post), I'd like to have the option of launching 2014.0 (the previous version) on projects that have been ongoing for weeks or months. This is because once you commit on 2014.1, and if you run into a job-stopper, going backwards is very painful and time-killing.

I want to continue to work on my heavy duty projects in 2014.0, while starting new, lighter and quicker projects in 2014.1 before I commit to it full time.

So... here's what I did. Compress (zip) the 2014.0 application, then run the CC updater. That will update CC 2014.0 to 2014.1, which I renamed "CC 2014.1."

Then, I unzipped the .0 version, and renamed it 2014.0.

I was able to successfully launch both versions and run them simultaneously. Both, seemed to work OK; I didn't do a lot; mostly wanted to see if they would both launch without crashing.

Interestingly, I was able to copy clips from a Sequence in .0 and paste it into a sequence in .1. I could not do the reverse. I suppose that is to be expected; but it's unfortunate, because if that was possible, it would be a way for people to retrograde their Pr Projects.

So, I just wanted to offer this bit of information, and if anybody else would like to try it and post horror or success stories, I'd be interested in reading them, either way.

I need to go back one version to CC 2014 - the one before the October release

forums_noreply@adobe.com — Fri, 10 Oct 2014 23:53:01 GMT

... and it looks like Adobe took it off the Previous Versions in the Cloud installer. I've done months worth of work in CC 2014 on ongoing projects, and I can't go back to the CC version using the Cloud installer.

Adobe, please put the previous installer back on the Cloud PRONTO.

I was able to retrograde the day that the new release came out (After discovering that it wouldn't work with my RED footage), but now it's gone! All that's available is 6.0 and 7.0.

I'm not totally dead, because like an experienced person, I cloned my drive before upgrading. But, it's going to require more hoop jumping and take longer than is really necessary, if only Adobe would make ALL versions accessible to us.

constant crashing (Mac) at early stages

forums_noreply@adobe.com — Mon, 08 Sep 2014 21:37:17 GMT

Encore used to work great. I don't make a lot of DVDs, but somewhere around installing CC or CC2014 of Ae, Pr, AME, etc., Encore crashes on Create New Project and I can't get a thing done with it.

I've re-installed the app several times several times, both from the Cloud and also from my CS6 installer .dmgs.

Installer fails from both unless I'm booted into Safe Mode. That may be a clue to an extension conflict.

I scoured my drive for all Encore prefs and trashed them.

There have been a few times I've gotten to the Import Assets stage, but when I try to create a Timeline... crash.

Somebody please help. I make videos for a living, and have clients waiting for DVDs and Blu-Rays.

Here's PART of my crash log (I do understand that posting complete Crash Logs is uncool here.):

Process: Adobe Encore [731]

Path: /Applications/Adobe Encore CS6/Adobe Encore CS6.app/Contents/MacOS/Adobe Encore

Identifier: com.adobe.Encore

Version: 6.0.1 (6.0.1)

Code Type: X86-64 (Native)

Parent Process: launchd [217]

User ID: 502

Date/Time: 2014-09-08 16:29:52.151 -0500

OS Version: Mac OS X 10.8.5 (12F45)

Report Version: 10

Interval Since Last Report: 54209 sec

Crashes Since Last Report: 17

Per-App Interval Since Last Report: 443 sec

Per-App Crashes Since Last Report: -2

Anonymous UUID: 838B33BE-5D03-1AFE-39C3-BF8A9AB9AF76

Crashed Thread: 44 Dispatch queue: com.apple.root.default-priority

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:

*** error for object 0x145994528: incorrect checksum for freed object - object was probably modified after being freed.

Thread 0:: Dispatch queue: com.apple.main-thread

0 com.apple.CoreGraphics 0x0000000112e7be74 ARGB32blend_color + 394

1 com.apple.CoreGraphics 0x0000000112af3e58 sseCGSColorDeepMaskCopyARGB32 + 1710

2 com.apple.CoreGraphics 0x0000000112ba50d1 CGSColorDeepMaskCopyXRGB8888 + 124

3 com.apple.CoreGraphics 0x0000000112aad628 argb32_mark + 547

4 libRIP.A.dylib 0x000000011f0fecc3 ripl_BltGlyph + 5579

5 libRIP.A.dylib 0x000000011f0fc577 ripc_DrawGlyphs + 2893

6 com.apple.CoreGraphics 0x0000000112e1786c draw_glyphs + 699

7 com.apple.CoreGraphics 0x0000000112ab38e7 CGContextShowGlyphsWithAdvances + 489

8 com.apple.CoreText 0x000000011351c38b CTFontDrawGlyphsWithAdvances + 105

9 com.apple.CoreText 0x000000011351c269 TRun::DrawGlyphs(CGContext*, CFRange) const + 259

10 com.apple.CoreText 0x000000011351bb88 TLine::DrawGlyphs(CGContext*) const + 200

11 com.adobe.dvaui.framework 0x0000000106458b94 dvaui::drawbot::CoreTextStringDisplayInterface::DrawString(dvaui::drawbot::SurfaceInterfa ce*, dvacore::geom::PointT<float> const&) + 556

12 com.adobe.dvaui.framework 0x000000010645b405 dvaui::drawbot::OSSurfaceInterface::DrawStringImpl(dvaui::drawbot::BrushInterface const&, dvaui::drawbot::FontInterface const&, unsigned short const*, dvacore::geom::PointT<float> const&, dvaui::drawbot::TextAlignment) + 113

13 com.adobe.dvaui.framework 0x00000001064527ac dvaui::drawbot::SurfaceInterface::DrawString(dvaui::drawbot::BrushInterface const&, dvaui::drawbot::FontInterface const&, unsigned short const*,

Serious job-killing export bug in latest CC 2014 build 8.0.1 (21) ???

forums_noreply@adobe.com — Mon, 04 Aug 2014 22:51:21 GMT

Exports now take 1000 times longer than before.

I opened an old project that was exporting in 35 seconds, and now am seeing estimates of over four hours.

I exported the project using XML and opened it in Pr CC. Export was 34 seconds.

So, I re-opened CC 2014 and imported the XML, set it to Export, and was now seeing an estimate of 90 minutes.

???

What's the status of new Mac Pros and CC 2014?

forums_noreply@adobe.com — Wed, 13 Aug 2014 17:32:31 GMT

I've read some horror stories on this forum about new MacPros not being much faster with Pr CC or CC 2014. Since Pr accounts for about 80% of my income, I'm not inclined to spend $10K for a system with no net gain in speed, and an increase in problems and downtime.

I realize part of the problems may be with Mavericks and third party drivers; but if the whole system doesn't work well together, it's a no-go, and that many users don't come to the forums if their systems are working great. But, if the outlook is encouraging, I might start planning to upgrade from my trusty ol' MacPro3,1 and Quadro 4000, which running 10.8.5 has been more or less a dream, with a few bumps along the way (most if not all of which have been solved by Mark and Kevin from Adobe here. Thanks, guys!)

Search function in Project tab no longer works in 8.0.1.21 Mac

forums_noreply@adobe.com — Mon, 11 Aug 2014 22:05:47 GMT

I reported another bug in a separate thread.

Is anybody else getting this? It's grayed out.

Re-rendering clips in Ae crashes Pr

forums_noreply@adobe.com — Sun, 10 Aug 2014 06:02:34 GMT

I have clips that I rendered in Ae and imported into Pr and put in a Sequence.

When I re-render a clip in Ae, over-writing the clip, it crashes Pr about three to five seconds into the Ae render.

This is new behavior to the latest Pr (8.0.1 (21)) and Ae (13.0.2.3) CC 2014 builds.

MacPro3,1 - 10.8.5

weird scaling behavior

forums_noreply@adobe.com — Mon, 04 Aug 2014 04:47:38 GMT

Pr CC 2014 Mac. This behavior is new in the 2014 build.

When putting an HD clip in a SD sequence, and scaling it to 34% to get it to scale down to the SD raster, the clip appears to be scaled to 100% when I play the sequence.

If I turn CUDA off (software rendering), function returns to normal.

I updated CUDA driver today, and the issue persists.

rendering improvements, please

forums_noreply@adobe.com — Mon, 28 Apr 2014 14:10:05 GMT

This is intended to be a discussion, not a question.

As awesome as Pr is and will be with the next release, there's always room for improvements. I'm writing this to try to convince you all to join me in requesting more robust rendering in Pr.

Pr does what I call "top down" rendering. It creates a render file that reflects the entire stack of video tracks. While this is an efficient way to render initially, it's not necessarily the best way for all purposes. Avid calls this approach "smart rendering;" it only renders what it needs to play the sequence in real-time. The downside to this approach is that when you make a change to even one frame of a clip of a multi-layer section (even on the top-most layer), the entire section has to be re-rendered all over again.

What I'd like to suggest is the approach Avid uses, which gives the editor a choice of "top down" or "bottom up" rendering.

With bottom up rendering, all effects are rendered with all individual clips. So, for example if you have four video layers, and you make a change to a clip on V4, with "bottom up" rendering, only the top clips have to be re-rendered. Once you've done an intitial "bottom up" render to your sequence (which does take longer than top down), changes to the upper layers when you're fine tuning your sequences go much much faster. So, the time you lose in your initial bottom up render, you make back later in spades as you finesse your work.

As we start to see more 4K and RAW formats coming in to edit, we can expect less real-time performance (especially on older slower machines). So, as with every jump to bigger formats, we usually see a return to some of the banes of our existence, and I expect that constant rendering and re-rendering is going to be a biggie.

Please join me in requesting this feature. Thank you.

VTDecoderXPCService hogging my CPUs

forums_noreply@adobe.com — Tue, 15 Apr 2014 21:20:15 GMT

Just started my first Alexa project after updating to Pr 7.2.2 Mac. Footage is 2K ProRes4444 with no audio in a matching Pr Sequence.

I notice a couple of things. VTDecoderXPCService is running according to my Activity Monitor and taking up about 20-50% of my CPUs when I hit Play in Premiere. I've never noticed this any previous version of Premiere.

For comparison, I opened another project that had a mix of MPEG and ProRes422 footage. VTDecoderXPCService still runs in the Activity Monitor but using only about 6% of the CPUs.

When playing a ProRes4444 clip in QT Player, VTDecoderXPCService is using ZERO of the CPUs. Interesting, no?

If I force quit VTDecoderXPCService, it relaunches itself immediately. Google search tells me that it's a Sandbox service for Quicktime, whatever that means.

Also, my Inactive Ram is taking up all my Free Ram within a few minutes, which usually makes Premiere respond very sluggishly. Shuttling in the timeline varies between acceptable and non-existent.

I thought the RAM leak issue was fixed a few revs ago.

MacPro3,1 - 10.8.5 - Quadro 4000 (older drivers because the latest make Pr inoperable) - very fast RAID5 - Adobe CC latest updates - AJA Kona LHi latest drivers

Premiere CC lies to me.

forums_noreply@adobe.com — Sat, 12 Apr 2014 17:08:29 GMT

When opening various old projects, it tells me this:

"This project was last used with Mercury Playback Engine GPU Accelleration (CUDA) which is either not available or not certified on this system. Mercury Playback Engine Software Only will be used."

That's not true. I've had a qualified CUDA card installed for years. I dismiss the message and proceed to work as usual. Sometimes, I have to throw the CUDA switch in General Preferences, but Pr works fine with my qualified CUDA card once I do so.

It's more of an annoyance than anything. Might be related to the version of GPU or CUDA driver I have installed. But, could also be a bug in Pr.

Anybody else?

MacPro 10.8.5 nVideo Quadro 4000 - not running the latest nVidia drivers, because there have been many reported job-stopping problems.

I'm running 313.01.03f02 & CUDA 5.5.28

Feature Requests for next version of Pr

forums_noreply@adobe.com — Wed, 26 Feb 2014 18:52:42 GMT

I've submitted this list. If you agree, please join me. Copy and paste into the Feature Request page if you like. Add your own requests.

AUDIO:

Ability to save track or clip based audio effect user presets.

Option-drag to copy an audio effect from one insert location to another (to different tracks)

Drag audio effects up or down in the effect stack order, or to another track

Temporary Snap on or off (Reverse Snap Behavior) keyboard modifier.

KEYBOARD / SHORTCUTS:

Ability to map multiple Keyboard Shortcuts to the same function (like Avid: E & R keys, same as I and O)

Ability to print the Keyboard Shortcuts, or save all of them as a text file.

TIMELINE:

More obvious indicator that Timeline Snap is on.

Indicator on Clips in the Timeline that indicate Frame Blend is enabled.

Ripple Sequence and Chapter Markers.

Ripple Audio Track Keyframes.

Solo video layer button on the Timeline track panel.

Constrain clip time movement between tracks by holding shift key, just like all other applications.

FX button/switch, as in After Effects, to turn off all effects on a track (video and audio).

Option-double click a nest to reveal contents of nest in the same master timeline.

SOURCE AND PROGRAM PANES:

Keyboard shortcuts to scale image zoom in Source and Program tabs.

Keyboard shortcuts to increase or decrease playback resolution.

Have the Program monitor remember the Zoom and Resolution level for each Sequence; don't have Zoom scale set universally by the project.

VIDEO EFFECTS:

Make ALL effects Accelerated, YUV, 32-bit. Allow Third Party effects to be accelerated!

Ability to save user/custom transition presets.

In Effects tab, press Tab button to jump to next effect parameter (as in After Effects)

Feathering and invert on Garbage Mattes

A Track Matte function that allows us to pan and scale the clip being matted without affecting the matte size or position. You could do this with a Stencil / Silhouette Alpha / Luma Blend mode as in Ae.

MISC:

When using Clip > Scale to Sequence, DO NOT have the new Scale factor in the Motion tab change the clip's scale to 100%.

Consistent Mouse Wheel behavior across all apps in CS

Scopes update while playing.

Make Export and Title windows return to the previously adjusted size and placement.

Add a command buffer, so that we can execute several commands in a row, and not wait for the app to "release", or for the first event to complete before I can proceed to the next event.

File requests here:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Au CC crashes on launch

forums_noreply@adobe.com — Thu, 20 Jun 2013 16:19:47 GMT

Every time, even after un- and reinstall. Here are the first few lines of the crash report. Au CS6 works beautifully.

Any ideas to get it working appreciated.

10.7.5 MacPro3,1 32G RAM

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 0x00007fff906d5ce2 __pthread_kill + 10

1 libsystem_c.dylib 0x00007fff915807d2 pthread_kill + 95

2 libsystem_c.dylib 0x00007fff91571a7a abort + 143

3 libc++abi.dylib 0x00007fff919fc7bc abort_message + 214

4 libc++abi.dylib 0x00007fff919f9fcf default_terminate() + 28

5 libobjc.A.dylib 0x00007fff908711cd _objc_terminate + 114

6 libc++abi.dylib 0x00007fff919fa001 safe_handler_caller(void (*)()) + 11

7 libc++abi.dylib 0x00007fff919fa05c std::terminate() + 16

8 libc++abi.dylib 0x00007fff919fb152 __cxa_throw + 114

9 com.adobe.auui.framework 0x00000001058980e9 BIB_T_MT::BIBThrowError(BIBError*) + 169

10 com.adobe.auui.framework 0x00000001058c7f2b dvaui::drawbot::AGMTextDoc::GetLineBounds(int) const + 411

11 com.adobe.auui.framework 0x00000001058b01e6 dvaui::drawbot::AGMFontInterface::MeasureMultiLineStringHeight(unsigned short const*, float, int) const + 486

12 com.adobe.dvaui.framework 0x00000001006645ff dvaui::controls::UI_StaticText::GetRecommendedSize_Helper(dvaui::drawbot::Drawbot*, boost::intrusive_ptr<dvaui::ui::Theme>, bool) const + 383

13 com.adobe.dvaui.framework 0x0000000100664825 dvaui::controls::UI_StaticText::UI_GetRecommendedSize(dvaui::drawbot::Drawbot*) const + 53

14 com.adobe.dvaui.framework 0x00000001007c7f98 dvaui::ui::(anonymous namespace)::LayoutNode::operator()(boost::intrusive_ptr<dvaui::ui::UI_Node>) + 536

15 com.adobe.dvaui.framework 0x00000001007c781a dvaui::ui::AutoLayoutSubView(boost::intrusive_ptr<dvaui::ui::UI_SubView>, dvaui::drawbot::Drawbot*) + 1386

16 com.adobe.dvaui.framework 0x0000000100798f05 dvaui::ui::UI_SubViewAdapter::AutoLayout(dvaui::drawbot::Drawbot*, boost::intrusive_ptr<dvaui::ui::UI_Node>, boost::intrusive_ptr<dvaui::ui::UI_Node>) const + 37

17 com.adobe.dvaui.framework 0x00000001007cf788 dvaui::ui::UI_NodeArchive::CreateNode(boost::intrusive_ptr<dvaui::ui::UI_Node>, dvacore::proplist::PropList const&, boost::function<boost::intrusive_ptr<dvaui::ui::UI_Node> ()

Q for those who work with linear footage

forums_noreply@adobe.com — Wed, 22 Jan 2014 23:06:40 GMT

When working with Alexa footage recorded in linear color space, I'm wondering what real-time CUDA effects you all use to get the footage to look good, and play in real-time without rendering.

Normally, the Cineon Converter would be the first plug in the stack, but that requires rendering; it's not an Accellerated Effect. So, I rule it out. (Feature request!)

Currently, I start with the Levels effect to bring the blacks to 0, and the whites to 100. Then, I add 3-Way CC to bring up the chroma. And I might tweak the Gamma at this point (usually downward / negative), and readjust the blacks and whites with the Input Levels sliders in the 3-Way effect to compensate for deviations from my initial 0 and 100 settings.

That's just to get the footage to look "normal" as RGB footage ordinarily does without effects upon import into a Sequence.

What's your method?

sloppy 4K performance

forums_noreply@adobe.com — Sun, 05 Jan 2014 18:27:47 GMT

On this Adobe video: https://www.youtube.com/watch?v=UrxEx8ICqME

the user is getting responsive play and real-time effects with 4K footage on a laptop, using Thunderbolt storage.

I have a different system, still very powerful, and I'm not getting nearly the same response. I'm getting dropped frames unless I dip down to 1/16 resolution (Playback) with 4K XDCam AVC/MP4 footage. My audio is choppy unless I turn off my video track.

My 8 cores are maxing out at 100% as I play the footage at any resolution above 1/8. These are clips in a Sequence that matches the footage with no effects applied. I also get dropped frames in the Source player; not just the Program.

For comparison, I can load the same clips in VLC, and it will play them smoothly, and my 8 cores are running at between 20 and 85 percent at FULL resolution (There is no option to downsample.); the audio is not choppy.

This begs the question of why Pr is adding that extra CPU overhead just to play back un-effected clips? It can't be drawing the timeline. Every player has a timeline to draw.

I feel like taking a giant step back, and considering transcoding to ProRes to get acceptable performance. But, the hitch there is that AME won't accept my MXF clips for transcoding. I appear to be stuck with poor performance in Pr, unless somebody has an idea if I'm doing anything wrong, or if my system is just too archaic for 4K.

Here's my system. It's not puny. My CPU is "mature," but strong.

MacPro3,1 - 8 x 3GHz - 32G RAM - Quadro 4000 for Mac (latest drivers) - 10.8.5 - Pr CC 7.2.1 (4)

RAID5 - 8 SAS drives - ATTO 6G/s - over 2GB/s read speeds (This is not a bottleneck.)

Thanks,

Jim Curtis

"The project appears to be damaged. It cannot be opened."

forums_noreply@adobe.com — Mon, 05 Dec 2011 18:58:14 GMT

This is what I see when I try to open two ongoing projects. I tried importing the old project into a new project. Some times, that works, but on others, I get the same message, except with "opened" replaced by "imported."

Is there way to fix damaged projects? Perhaps in a text editor? Is there a service that can fix them for me?

Even my auto-saved projects are damaged (from Friday, but not Wednesday)

This can cost me a client. I need to open these projects now.

Mac 10.6.8; Pr CS5.5. They won't open on my MacPro3,1 or on my MBP.

I reinstalled PrCS5.5 on the MP. I ran Disk Warror, Repaired Permissions, trashed preferences, cleaned Caches.

Has Save As CS6 Project been removed from CC?

forums_noreply@adobe.com — Fri, 20 Dec 2013 16:06:18 GMT

I thought it was there at first.

I can't find it, nor can I find a mention of it in the reference PDF.

Is XML the only way to retrograde projects?

Pr 7.1 Mac bug in Dynamic Link

forums_noreply@adobe.com — Sat, 16 Nov 2013 17:35:02 GMT

When I drag (Dynamically Link) an Ae CC 12.1.0 Comp that's 23.976 FPS into Pr CC 7.1.0, it comes into Pr interpreted at 29.97.

I can workaround by using Interpret Footage, and change the frame rate of the linked Comp in Pr after importing it.

But, it seems to me that Pr should interpret the frame rate of linked comps correctly and automatically.

I'm calling this is a bug. I have filed a report.

MacPro3,1 - 10.8.5 - CC latest updates

launching bug in 7.1.0?

forums_noreply@adobe.com — Fri, 08 Nov 2013 17:12:07 GMT

A few times I've attempted to open a Pr project by double-clicking a Pr Project icon in the Finder, Pr launches, loads up the previous project - NOT the one I clicked in the Finder, and crashes.

Anybody else?

Mac, obviously.

Feature Requests - audio

forums_noreply@adobe.com — Tue, 15 Oct 2013 15:09:27 GMT

I'm anticipating the upgrade to Pr CC this month. I watched the video, and am thrilled with the upcoming new features. But, I'm still seeing areas for improvement, specifically in the audio domain.

Currently, the only way to dupe settings is to do it manually, parameter by parameter. Slow and counterproductive.

Audio Plug-ins / Inserts:

- Save the settings on plug-ins.

- Copy plug-ins from one track and paste into another (and/or option-drag).

- Move plug-in in the insert positions in the channel strip by dragging (Changing the order of plugs can have big results.).

Audio Hardware Preference:

- Increase the range of buffer options.

Here's why this is important. Now, it tops out at 1024. That's not high enough when using lots of plugs or CPU intensive plugs. If you've ever heard your audio become choppy after inserting plugs, it's usually because they're spiking the CPU or overloading the buffer. 4096 would be a better maximum.

Here's the link for feature requests. I've already filed mine. If you agree with these productivity enhancements, please join me.

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

___

PS. I recently purchased a license to what could be an invaluable post-production plug-in, called Zynaptic Unveil. It's purpose is to remove reverb. How many times have you pros been given some footage with less than ideal audio? If you're like me, it's way too many. Here's the problem: Just one instance of Unveil is all Pr Mac can handle. Unveil plus any other CPU challenging plug is out of the question. Chop City. That's because of the buffer limitation in Pr (Au has the same buffer limitation.). I have to export clips and bring into MOTU Digital Performer, which has a buffer max of 4096, and there I'm able to use several instances of Unveil without choppiness.

I'd like to see Pr get so good at handling audio that taking it to another app is no longer necessary. It's getting close. Very close.

Premiere Pro (CC) has encountered an error. (Mac)

forums_noreply@adobe.com — Sun, 07 Jul 2013 20:52:31 GMT

Darn, this is bad. I'm having flashbacks to Pr CS6.0.0. I keep getting this error, which leads to a crash:

Premiere Pro has encountered an error.

[/siree64/releases/2013.02/PremierePro/

Messanine/Make/Mac/../../Src/Utilities.cpp-780]

Pr CC has been working pretty well on older CS6 projects and new projects started in CC.

For the record, I'm a professional Premiere Pro power user; not a novice.

This recurring problem happens when I just click on audio or video certain clips in a timeline. I exported this project from FCP7 via XML and into Pr CC. All the sync clips are double system; video from a Canon transcoded to ProRes; audio files are .WAV from a Zoom recorder.

{Sidebar: I have an ongoing project in CC I started in CS6 with Canon H264 video, and Zoom audio. I'm not having the same problems.}

I exported this problem project to XML from Pr CC, opened it in Pr CS6, and I don't get the crashes when clicking on clips.

This is a new issue with PrCC, and apparently projects imported via XML.

I did all the usual maintanence: Trashed prefs, previews and Media Cache. Ran Disk Warrior. Problem persists.

Workaround is, once I locate a clip that causes the crash, use In and Out around the clip to lift it, then replace manually. Slow going. LOTS of crashing. Every few minutes. Once the media is replaced, the crashing stops. So, this rules out corrupt media. Besides, I ran Digital Rebellion's Corrupt Clip Finder, and all media on this project passes as not corrupted. I save about every minute now, so as not to lose too much work.

Silver lining: Pr CC launches about ten times faster than Pr CS6, so getting back to work after a crash is faster.

If anybody has a clue on how to stop this, please chime in.

Flickering on H264 exports

forums_noreply@adobe.com — Fri, 27 Sep 2013 17:04:11 GMT

Flickering is occasional flashes of partial black (like a layer over the video at 50% opacity) every so often; random intervals.

I've seen this on several projects now in the last few weeks, with different kinds of source footage, but mostly ProRes442 or 4444.

It doesn't bother me for initial content reviews, but my clients want to see a representation of their spot, and the flickering concerns them, my assurances that the masters won't have it to the contrary.

And some of my deliverables are H264 for the web or company intranets.

Workaround is to export to ProRes and use AME to make H264, which then come out clean with no flicker. But, that's an extra step that's unnecessary and slows me down.

Will report as bug. Wanted to see if anybody else is getting the flickering.

I've had some issues using Dynamic Link to AME from Pr for exports, such as seeing Dynamically Linked Ae clips jumping around the frame, too.

MacPro3,1 32G RAM Quadro 4000; latest drivers Pr CC 701 (105) 10.8.5

Is there a shortcut to close the Titler window?

forums_noreply@adobe.com — Sun, 04 Aug 2013 17:54:04 GMT

I've been meaning to ask this for quite a while:

I'm having difficulty shaking the habit of using Command-W, and I end up closing tabs in the Titler, and not the Titler itself, and then having to reopen the tab I was using last, before going old school with the mouse.

Is there a keyboard alternative to clicking the red Close Window button?

Mac Troubleshooting List

forums_noreply@adobe.com — Thu, 01 Aug 2013 15:07:23 GMT

I make my living with Pr and Ae, and it's vital I keep my system running, and not encounter any job-stopping problems. Here's my checklist of troubleshooting Pr on Mac.

I don't even post my problems here unless I've tried all these fixes first, as these routines haven't failed to get me back in business (so far), unless the problem was a bug. Those can't be fixed by us, but some can be worked around.

1. Trash Preferences (fixes most Pr problems when "it's just not working right"). Hold down Option while launching.

2. Delete media caches and previews. Do this after an application crash or hang.

3. Check for corrupt media in your project. This can cause major performance degradation, freezes and crashes. Remove or transcode problem media to some other format.

4. If Pr is simply sluggish, reboot the computer (Pr has RAM leaks), OR much faster, open the Terminal, and type in "purge" (no quote marks) and hit Return every so often. You can tell you're out of RAM when you open the Activity Monitor > System Memory tab, and there's no Free RAM left. Free RAM defaults to the green color. A lot of blue (Inactive RAM) is caused by Pr. It's RAM that's not accessible. Low RAM causes performance issues, and I'm gobsmacked that Adobe hasn't fixed this problem yet. Purging will turn the blue Inactive RAM into green Free RAM. The longer you work in Pr, the less Free RAM becomes available, and the more sluggish it will become.

5. Run Disk Warrior (esp. if you're getting beach balls, AND every time after a computer (not application) crash or freeze).

6. Re-install the application.

7. If you have an external video (BMD, AJA, etc.) or audio card that requires third-party drivers, remove them and see if the problem vanishes.

8. Re-install graphics drivers (this has fixed display issues for me, such as video not updating in real-time).

A lot of people suggest Repairing Permissions, but this is mostly useless advice. You need to do that if you're getting "directory access denied" or "can't write file" errors. However, it can't hurt. Disk access is vital to caching, previews, and project saving. If you're having permissions issues, the app will either stop working (if it can't cache or write previews), or it won't let you save your project.

Has anybody gotten Zynaptiq Unveil to work in Pr Mac?

forums_noreply@adobe.com — Wed, 24 Jul 2013 15:40:14 GMT

If so, which versions of the plug-and application, please?

This looks in theory to be a boon to documentary editors, as it removes reverb and slapback due to poor audio recordings. That's something that's plagued any editor of any significant experience.

I downloaded the demo, and the plugs don't show up in the Inserts menu in CC. It shows up in CS6, but the GUI is truncated and useless.

It doesn't show up in Au CS6 or CC either.

I'm running OS 10.7.5.

Zynaptiq tech support says they don't have a Mac with Premiere to test it on.

It works on MOTU Digital Performer on Mac. Probably something about the way Adobe apps handle plug-ins is the problem.

Worst case, I could process in DP, or the standalone Unveil app, export, and import into Pr. But, it'd be a lot more convenient to get it to work in Adobe products.

Please confirm: 7.0.1 incompatible with AJA Adobe 10.4.5

forums_noreply@adobe.com — Sun, 14 Jul 2013 19:57:00 GMT

Hopefully somebody can confirm the same issue, or let me know it's working fine for them.

MacPro3,1 10.7.5 Kona LHi Quadro 4000

I have the latest AJA Control Panel and AJA Adobe plug-in installed (10.4.5). This was working great with Pr 7.0.0.

And seemed to be OK with 7.0.1 for a few hours. But, all of a sudden, I lost the ability to watch anything in real-time in Pr, whether or not I had enabled the LHi for external viewing, on several different projects that were working fine before. All I could see was the frame I parked on before hitting play. The audio would play, but not the video.

On a hunch, I uninstalled the AJA software, relaunched Pr 701, and was able to watch my footage and sequences in real-time again.

So... I reinstalled Pr 7.0.0, the AJA software, and I'm back in business with external monitoring and smooth playback.

Too bad, because I liked the new features in Pr 7.0.1.

I've also sent a report to AJA.

Pr CC Mac: third party audio VST plugs issue

forums_noreply@adobe.com — Wed, 17 Jul 2013 21:46:23 GMT

The GUIs are garbled and useless on my VST plugs from WaveArts. But, the AU versions work fine.

Another bug in Pr CC Mac.

Anybody else?

AME CC ignores some Dynamic Linked clips

forums_noreply@adobe.com — Wed, 17 Jul 2013 21:43:35 GMT

That pretty much sums it up. I cut two sequences today. On both of them the GFX were all Ae comps I dragged into Pr. There were full screen, lower thirds, and several that were a vertical third (covered the right third of the frame, while video was running on the left side). Using AME CC to render (from a Pr CC Mac Sequence), the "right thirds" didn't show up either in the renders, or in the compression settings dialog box.

Everything rendered fine when I did it straight from Pr and didn't use the AME app.

Something is wrong with Dynamic Link.

Anybody else?

CC bug (Mac)

forums_noreply@adobe.com — Tue, 18 Jun 2013 20:20:36 GMT

I put one of the Lumetri Looks on ONE clip in my timeline with about 200 clips. That bogged down the playback pretty badly, but that's not the issue. This is:

I removed the effect, but now I have the FX icon on every audio and video clip in my timeline, none of which have any effects on them, and they won't go away, even after relaunching the app.

Where are Project Settings in Premiere Pro CC?

forums_noreply@adobe.com — Tue, 18 Jun 2013 19:54:55 GMT

Where'd the Project Settings go?

Is CUDA always on? What if I want to turn it off an use software rendering?

New features in Pr - Coming Soon!

forums_noreply@adobe.com — Thu, 04 Apr 2013 16:13:37 GMT

http://provideocoalition.com/ssimmons/story/an-early-look-at-the-next-version-of-adobe-pre miere-pro

Thanks for listening to some of my feature-requests, Adobe!

Pr CS7 Feature Requests

forums_noreply@adobe.com — Wed, 25 Apr 2012 15:07:03 GMT

I am excited about getting my hands on CS6, and congratulate the Adobe team for their hard work.

However...

I haven't seen anything in the web pages or videos about these features that are vital to working editors, already requested by me and many others, but still not implemented or announced here:

http://blogs.adobe.com/premiereprotraining/2012/04/premiere-pro-cs6-whats-new-and-changed. html

Please join me in requesting these features be implemented ASAP:

-----

Ability to save track or clip based audio effect user presets.

A Scrub Audio shortcut toggle - NOT a user pref.

Ability to map multiple Keyboard Shortcuts to the same function (a la Avid: E & R keys, same as I and O). Very convenient for two-handed editors.

Show Match Frame (Add Edit) function.

Heal Match Frame (Add Edit) command.

Dupe Detection indications in Timeline.

Shortcuts to Scale image zoom in Source and Program tabs.

Temporary Snap on or off (AKA Reverse Snap Behavior) keyboard modifier.

More obvious indicator that Timeline Snap is on.

Indicator on Clips in the Timeline that indicate Frame Blend is enabled.

Ripple Sequence and Chapter Markers.

Ripple Audio Track Keyframes.

Ability to save user/custom transition presets.

Constrain clip time movement between tracks by holding shift key, just like all other applications.

Lasso multiple keyframes.

Constrain keyframe values while holding shift key and moving them in time.

Clip Label only works on AV clips. Not V-only. Please make it work on V-only clips as well as AV clips.

A Track Matte function that allows us to pan and scale the clip being matted without affecting the matte size or position. CRITICAL!

Ability to change the dimensions of a Sequence after it's been created. (Actually, this may be in CS6; I'm not clear.)

Make it possible to solo and mute audio in the Timeline panel; not just the Audio Mixer.

Make it brilliantly obvious when audio tracks are being soloed (or muted); not some tiny little icon that's 1/100 the size of the interface. When you mute or solo a track in the Audio Mixer, that should be indicated in the Timeline icons and tracks as well, perhaps by shading or color, stripes, etc.

Please give us the ability to copy between in/out in a Sequence and paste elsewhere. Workaround is to add edits (razor) where you want the in and outs before you can copy that region. Or, you can set in/outs and lift or extract, then immediately undo. This is a time waster; counterproductive.

No Auto-Saving right in the middle of an operation or playback, please. Make it wait for a few seconds of inactivity before it kicks in. No auto-saves when no changes have been made; long periods of inactivity.

Please make all Adobe apps NOT force the computer system to switch to the app that's launching or saving after that operation is compete. It's VERY ANNOYING to be typing an email and have Adobe switch apps for me when it decides it's ready. VERY ANNOYING.

Please after using Clip > Scale to Sequence, DO NOT have the new Scale factor in the Motion tab change the clip's scale to 100%. That's misleading, confusing and I see no good reason for that number to change. If I'm using a HD clip in an SD Sequence, I want to know exactly how much more I can scale it up before it exceeds the actual scale of 100%. So, rather than it showing me 100%, it should show 40%, or whatever the real scale factor is.

Provide a way to save TRACK AUDIO FX settings. I work in a native Sequence to edit, and copy and paste it into an AJA sequence for color correction. ALL my TRACK BASED AUDIO needs to carry over into the new sequence. Without a way to save my settings, I have to manually recreate them by jumping back and forth between the old and new sequence. Time-killer.

Change the paste behavior into a new Sequence to exactly match the track configuration from the "parent" (copy from) sequence.

Have the Program monitor remember the Zoom level for each Sequence; don't have Zoom scale set universally by the project. When switching between Sequences of different size, we have to reset the Zoom level each time (and with the mouse, too; not a keyboard shortcut). Time waster.

Consistent Mouse Wheel behavior across all apps in CS, please. Ae, Au, and Pr have different scroll wheel behaviors.

=====

I intend to submit these to Adobe AGAIN a nanosecond after I discover they're not in Pr CS6. I hope you will all do the same. And share your suggestions with us. Strength in numbers.

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Please share experiences: FCP7 vs Pr CS6 on a MBP

forums_noreply@adobe.com — Tue, 12 Mar 2013 19:32:04 GMT

I'm not new to Pr. I've been working with it on a MacPro 8-core. Before I was using FCP7. Pr is much faster, but much of that speed is because I have a CUDA card.

I just got a job to work on site doing some cutting on an MacBookPro4,1. Last two years, I used the same laptop, but was using FCP7. Footage was DVCProHD / P2.

I was hoping people who've done a significant amount of editing on a MBP with both FCP7 and Pr CS6 can give me their insight as to how the two compare on a laptop.

I will be on a tight deadline, and can't afford to get tied up rendering or exporting. FCP is a known entity. Pr isn't, to me, on a job like this.

Any relevant input will be appreciated. Thank you.

Is there any way to prevent Pr from seizing the foreground?

forums_noreply@adobe.com — Wed, 06 Feb 2013 15:47:31 GMT

I'm on Mac OS, when I launch Pr, and go back to my email, Pr persists in taking control of my computer and making itself the foreground application, interrupting my work. It does this even before the Project is completely open; so this can happen two or three times before it's really ready.

This is EXTREMELY ANNOYING, and I can see little benefit to this behavior. OK, maybe it would be nice to know when Pr is ready for projects that take a really long time to load. But, it seems to me that seizing the foreground should be an option in the Preferences. Many many many more times than not, I don't want Pr interrupting me.

I have already submitted my Feature Request, but if anybody knows a hack to the app that will stop this, I'd be most grateful to know it.

Oh, and "You Know Who," I know before you even say it what you're going to suggest: "Don't run any apps along with Pr." Thats doesn't cut it. Because Pr also seizes the FG when I'm working in Ae or Ps, and the CS is designed to have multiple apps opened at once. Modern OSs are designed for multi-tasking. We need to have FTP client, email, browser, etc. open all the time to conduct business. And having two computers isn't in the cards for all users. But, preventing annoying and mostly useless functions are.

November nVidia updates for Mac Quadro 4000

forums_noreply@adobe.com — Sun, 18 Nov 2012 18:28:26 GMT

I hope this hasn't already been covered, but I just noticed updates for my nVidia Quadro 4000 (1.3.4.0 (295.00.056f03)) and CUDA 5.0.3.7.

Has anybody loaded these an noticed an improvement with Pr? If so, what?

Thanks,

Jim C.

audio interface option MIA

forums_noreply@adobe.com — Tue, 30 Oct 2012 15:51:48 GMT

I have an AJA Kona LHi. When I launch Pr, my audio comes through the AJA. But, after editing a while and completely on its own, it stops coming through the AJA and starts coming through the USB interface I use for my non-video apps (a Tapco LINK.usb).

The AJA stopped showing up in my list of audio devices around Pr 6.0.1 or possibly 10.1 or 10.2 of the AJA Control Panel, not sure which.

Audio is usually (but not always) in perfect sync through and with the AJA, but not the Link.USB.

I don't know what's at fault here, whether it's Pr or my AJA driver.

Does anybody else experience this? Know of a fix? (Delete prefs / relaunch / reinstall / Disk Warrior don't do it.)

10.7.5 - Latest build of Pr and drivers throughout (nVidia, CUDA, AJA) Quadro 4000

Yesterday's Updates to Dynamic Link Media Server

forums_noreply@adobe.com — Tue, 09 Oct 2012 17:48:07 GMT

I woke to find four updates to CS6 (Au, Ae, Ps, and Pr) yesterday, which the Updater called "Dynamic Link Media Server CS6 1.0.1 Update."

I updated, and I updated my CUDA about the same time.

Pr started working slower. So, I reverted back, using my clone.

Not sure if this was a coincicence, or which update to blame.

I'm back to the performance from both that I was used to.

The CUDA update was for bugs I wasn't experiencing and for compatibility to 10.8, which I'm not running.

Was I too hasty? Do these Dynamic Link updates do anything? Improve anything?

MacPro3,1 - CS6 - Quadro 4000 - 10.7.4

New CUDA update (5.0.36) available

forums_noreply@adobe.com — Tue, 09 Oct 2012 01:16:53 GMT

But it appears to make things worse.

Anybody else?

I'm reverting.

MacPro 3,1 - 10.7.4 - Quadro 4000 Sticking with Cuda 5.0.24 for now.

Pr corrupts its own files

forums_noreply@adobe.com — Tue, 09 Oct 2012 01:14:50 GMT

I'm ready to to on record with this. The Serious Errors I get are caused by either corrupt preferences or corrupt media cache files.

It happens several times a day. Way too often.

Pr also can corrupt the nVidia driver.

The evidence: I will get repeated Serious Errors, and either deleting/replacing the prefs or deleting the Media Cache files and letting them rebuild will let me resume working... for a while.

I've even had to reinstall the my Quadro 4000 driver in order to get back to work.

MacPro 3,1; 10.7.4 Pr 6.0.3

Adobe Updater: New version 6.0.2. What?

forums_noreply@adobe.com — Thu, 04 Oct 2012 15:17:27 GMT

Adobe Updater informed me this morning that an update to Pr 6.0.2 is available; recommended for all users, etc.

What? I already had 6.0.2 installed. Weeks ago.

Is this a new update with the wrong version number?

Is Adobe Updater malfunctioning?

Has this happened to anybody else?

Can anybody from Adobe offer any insight?

I'm on Mac.

What's the trick to working with RED 4K?

forums_noreply@adobe.com — Mon, 03 Sep 2012 15:33:56 GMT

This is my first all 4K RED project. I'm two days into it, and it's been extremely frustrating.

First, I discovered that clips play best in the Timeline in a native 4K sequence set to 1/8 or 1/16 resolution. If I work at a lower resolution Sequence, my CPU usage increases or maxes out. Why the scaling isn't handled by the GPU, I don't know, because Adobe claims that's a benefit of a CUDA card (which I have, and is engaged).

Editing is extremely aggravating:

I hit play, and it takes a second before the Sequence plays. Other ops are instananeous, as they should be. Playing and scrubbing the Timeline or Program are not.

After doing an extract edit, the CTI jumps around the timeline. I have to wait about a second after each Extract to wait for it to stop jumping.

There is no real-time updating when scrubbing the Timeline or Program window.

This is odd, because scrubbing the Source is Fast! Exciting! Smooth!

When I scrub the Program or Timeline, I see maybe one out of every thousand frames, or maybe one out of every ten-thousand. There is no scaling, no effects; it's virtually the same unprocessed footage as the Player, yet scrubbing is severely hobbled. I guess this is the MPE. I make this conclusion because scrubbing a timeline in Avid and FCP is a VASTLY SUPERIOR experience, and the Source tab doesn't use MPE.

What we need is an off-line mode that turns off MPE. Feature request time.

Add these aggravations to standard Pr aggravations such as Pr not playing half the time when I hit the spacebar. CTI jumping around on its own and not going Home when I hit the Home key, etc.

If I'm doing something wrong, I'd appreciate the tips. I googled for Pr RED workflow, and followed the advice I found. It's not helping.

MacPro3,1 - 10.7.4 (tried running in 10.8.0 also; no improvement) - 32G RAM - Quadro 4000 latest drivers - 1.5 to 2 GB/s io ATTO R680 RAID Pr 601

I also have a Kona LHi, but Video Playback through it is disabled, because that slows Pr down even more.

Project Search function is useless.

forums_noreply@adobe.com — Fri, 31 Aug 2012 15:27:51 GMT

Whenever I click in the project Search field, I get a beachball for 10 seconds. I type a character, beach ball for 10 seconds. This happens for every character I type. When I hit return, I get the beach ball for 20-30 seconds. Then the results aren't filtered according to my search criteria.

Useless.

I'm working on a RED project. I imported all my media, which includes the proxies. I'm trying to segregate the _H files from the R3D and the _P, etc. When I enter "_H" in the search field, my results contain _M and _P as well.

Useless. I might as well just do my searching manually.

However, I should say that it does work some times, although the input beachballs are always there. There just seems to be no method to whether the results match my input criteria.

I have filed a bug report, but I'm wondering if anybody else has this problem.

Mac 10.7.4, Pr 601

HD title center cut guides

forums_noreply@adobe.com — Mon, 27 Aug 2012 16:51:33 GMT

These seem to be missing from Pr in both the viewers and the titler. Short of creating my own guides in Ae or Ps, and temporarily overlaying them every time I need to add or adjust some text, which would be a real drag on productivity, is there a way to turn them on in Pr?

I'm on Mac, if that matters.

How do I re-enable Adobe Crash Reporter?

forums_noreply@adobe.com — Sun, 26 Aug 2012 16:45:56 GMT

I hastily clicked the "don't show this again" button a few weeks ago, as that dialog box was a nuisance when Pr was crashing every five minutes. Now that it's not crashing quite so often, I would like to re-enable it. I think these reports could be valuable, if only Adobe engineers take time to read them, and follow the evidence to a fix for all the crashing.

I know I can re-enable it by un- and re-installing the Suite, but I really don't want to do that, if there's a simpler way.

Any ideas? I'm on Mac.

Thanks,

Jim

Use Previews not working in CS6 Mac

forums_noreply@adobe.com — Thu, 02 Aug 2012 15:58:05 GMT

It was working in 5.5, but appears to be broken for CS6.

I just rendered a spot using MB Looks on an adjustment layer. Took 6 minutes. I then immediately exported the sequence, and it took 6 minutes. My past experience is that the export should have taken about 18 seconds.

Anybody else seeing this? If so, I'll file a bug report.

MacPro3,1 - 10.7.4 - 32G RAM, Quadro 4000 w/stock OS driver; CUDA 4.2.10 - Pr CS 601

CC tools inconsistency

forums_noreply@adobe.com — Thu, 02 Aug 2012 19:20:13 GMT

The Fast Color Corrector and 3-Way have Levels controls built into them.

Try this: Set the input black and input white (RGB) values to the same number in all three plug ins.

Now, compare the looks between each plug in separately.

What I'm seeing is that they're all different.

I think they should be identical.

Bug? Feature? "Interesting" programming choices?

Top to bottom order: Levels, 3-way, Fast

Mac 10.7.4 - CS601 - Quadro 4000

So... Mountain Lion

forums_noreply@adobe.com — Mon, 30 Jul 2012 03:19:55 GMT

Working with a test partition and Pr for a couple of days now. So far... Pr has been solid, and I've experienced no Serious Errors! Yay!

Otherwise... Ae crashes too much, a few Ae plugs lost authorizations, and I get quite a few spinning beach balls that don't end in crashes, just delays.

Several other non-Adobe apps lost their authorization. Some were easy to re-authorize, and I'm still working on some others. Mountain Lion overall seems faster on some things, slower on others.

I wish Apple would perfect an OS before they move on to an "upgrade." Most of the new ML synching functions are lost on me, as I'm not an Apple customer, outside of the MacPro and MBP.

But, my limited experience so far is that Pr is GREATLY improved in terms of overall snappiness and stability, at this early point in my testing on a real job.

I did have one Ae linked Comp that wouldn't link. That's a bad thing.

I've only run a few other Adobe apps on ML, and I can say is that Ai didn't crash while I was using it. But, Ps won't open my important DVD label template and several other mostly recent PSD files ("Strtable error" What?). I still have PS5.5 installed, so at least I'm not out of business. But, I have serious concerns about Ps and ML at this point. Something's rotten.

Overall, ML seems to exhibit typical Apple dot-oh OS problems. Usually, x.4 is when they start to look dependable. This version will likely be no exception, based on past performance... but, I'd like to be wrong.

Since this is the Pr forum, the bottom line is that this OS seems, in my short experience, a worthwhile upgrade for Pr.

What remains to be seen, for me at this point, is whether the cons outweigh the pros. My plan is to stay booted into ML this week, and see what else I can break.

If you'd care to share your experiences, I will read them.

MacPro3,1, 10.8 partition for this post, Quadro 4000 wCuda updates and NO additional nVidia driver installed, 32G RAM, CS6 all updates, ATTO R680 SAS RAID5 (up to and over 2GB/s reads)

AME CS6 Mac always crashes on quit

forums_noreply@adobe.com — Fri, 13 Jul 2012 04:08:43 GMT

More an annoyance than anything. My renders are fine. Is there a fix for this?

MacPro3,1 8-core, 32G RAM, 10.7.4, Quadro 4000, ATTO R680 RAID5, Adobe Production Premium CS6, all updates installed.