[Jon Howard]

Thanks for your response Angelo! Unfortunately I’m not using Speed Grade in this case for grading purposes. I love Resolve, but have run into the same issue with it as far as trying to use it as a hack conform module for Premiere.

I’m strictly trying to conform DPX files that were graded elsewhere (which I receive from telecine facilities like Company 3 usually and in the case of the project I’m on right now, The Mill LA) and send the conformed sequence to Premiere rather than go through the laborious shot-by-shot and eye-matching method required by conforming in AE with Immigration.

If you conform an EDL to DPX files in Resolve and try to export an XML, you’ll get an error that it can’t do XMLs for image sequence-based media, only clip-based media.

It’ll be exciting to see how far Adobe goes with Speed Grade and Premiere re: conforming. Production Premium becomes as powerful as Smoke on Mac, maybe moreso, if it can add a good conform workflow.

Jon

[Jon Howard]

I had a similar issue. The project size got up to over 3GB. For what I was experience, I could repeat the problem by doing one or both of the following things:

– drag and drop Premiere Pro sequences from my PP project into media encoder for batch exporting. Using the “add Premiere Pro sequence” can take longer, but doesn’t appear to bloat the project

– enabling “use Preview files” when exporting a sequence. Going into the project file with Text Wrangler showed a huge number of links to preview files added that weren’t in the project prior to exporting with this option.

I’ve also read that using the Warp Stabilizer within Premiere can cause project bloating. Using “Save As” used to as well, but supposedly that was fixed.

Hope this is helpful!

Jon

[Jon Howard]

Hopefully this is helpful to someone because it took me a pretty ridiculously long time to figure it out. From digging around several dozen forums, it seems there are two things at play here:

1) The Nvidia Quadro 4000 mac drivers are already in OS X Mountain Lion and don’t need to be installed from the Nvidia website.

2) The CUDA drivers are a separate install.

Since my Quadro 4000 seems to be working fine, with the exception of CUDA, I downloaded the latest driver from this page:

https://www.nvidia.com/object/mac-driver-archive.html

Interestingly, this is the driver I originally downloaded and it worked fine. I didn’t run into issues until I installed a new driver from the System Preferences CUDA pane. I restarted and now Premiere CS6 is seeing CUDA and all is well.

So, the lesson I’ve gleaned from this experience and reading other posts is DO NOT install the latest CUDA drivers from NVidia. If what you have works, don’t fix it. The 5.0.37 drivers are a case in point. Fortunately, you can either run the driver restore app or the Single User mode command listed in my second post (pasted from the Nvidia website) and reinstall older CUDA drivers from the link above.

Really hope this saves somebody a headache.

Jon

“If you can describe what it is, that’s not it.”

[Jon Howard]

Quick update. On the Nvidia website I found the following info, which I followed:

To uninstall this driver and restore your original Mac OS X v10.8.2 driver, follow the steps below:

STEP 1: During the installation process, a backup archive of your current drivers will be created. If for any reason you need to uninstall the 304.00.05f02 driver, the “NVIDIA Driver Restore.mpkg” is located in /Library/Application Support/NVIDIA.

IMPORTANT: Do not move this package from its default location. Doing so will invalidate the uninstall/restore process. Also, this process is only valid with Mac OS X v10.8.2. Installing any newer version of the OS over this driver will also invalidate the uninstall/restore process.
STEP 2: After locating the NVIDIA Driver Restore.mpkg archive, double-click on the package. You will be guided through the driver restoration process. Click Continue after you read the Welcome screen.

STEP 3: Click Install on the Standard Installer screen. You will be required to enter an Administrator password to continue.

STEP 4: Click Continue Installation on the Warning screen: The Warning screen lets you know that you will need to restart your system once the installation process is complete.

STEP 5: Click Restart on the Installation Completed Successfully screen.

ALTERNATE METHOD – If for any reason you are unable to boot your system to the desktop and wish to restore your original Mac OS X v10.8.2 driver, you can also do so from “Single-User” mode:

STEP 1: Restart your Macintosh computer and hold down the “Command” (apple) key and the “s” key to boot into “Single User” mode.

STEP 2: When the system finishes loading to a command prompt, type the command “NVIDIARecovery” (no quotation marks), and hit the “Return” key.

STEP 3: The 304.00.05f02 driver will be uninstalled and your original Mac OS X v10.8.2 driver will be restored. The computer will then reboot automatically.

The NVidia Driver Restore application failed to install, just like the drivers (installation failed screen), so I tried the single user mode. I no longer have CUDA drivers on my machine, which is good, but I’m now unable to install them. Still get installation failure.

I’m in the middle of a project that got moved to this machine and, as soon as I’m done, I’m going to reinstall OS 10.7 and see if that solves the issue. I had similar “Installation Failed” issues with my Wacom Intuos driver and, from what I could find, that was Mountain Lion related.

If anyone else is having any similar issues, please let me know. It would be great to knock heads on this and figure out what’s happening.

Thanks in advance!

Jon

“If you can describe what it is, that’s not it.”

[Jon Howard]

I’m considering a switch as well and am interested to hear about Windows 8. In general, though, how necessary is it to update the Windows OS? Seems like a lot of pros are still using 64 bit XP Professional. What would you potentially be losing by just sticking with Windows 7?

Jon

“If you can describe what it is, that’s not it.”

[Jon Howard]

I’ve already checked the Adobe forums. I’ve found other people experiencing project bloating but no one else reporting the issue correlating to click and dragging into Media Encoder. I posted my query from Creative Cow on the Adobe forums and have 72 views with zero replies.

My original post mentioned the fix about importing the project into a new project. Unfortunately when the project gets this big (3.7 GB in this case), that takes hours and, in my case, failed.

It would be really great to hear something back from Adobe about this, either acknowledging the bug or explaining what I’m doing wrong.

At this point, though, our project is out the door and we’re onto the next one.

[Jon Howard]

Correct. The project file was initially 20MB. After a few click-drag exports from ME, it’s now 3.71GB. There are versions of the project in the Autosave folder that are 477MB and 840MB.

[Jon Howard]

Hi there,

The Autosave folder actually documents the project bloating. We have our max number of autosaves set to 5, so I didn’t see the full picture, but for every export he made, the project size doubled in the Autosave folder. The earliest one is 477 MB, then it jumps to 840MB, then 1.6GB.

In fact, the problem first became apparent because of the amount of time it was taking for the project to perform its Autosaves. This is what I initially noticed back in CS5 and stopped using the click-drag method of getting sequences into Media Encoder. Since I nipped it in the bud back then, I never experienced the project bloating to this extent.

The problem is fixed by importing the bloated project into a new project, but this can take a long, long time. I let the 3.7GB project import overnight, and I came in this morning and it had made no progress. Fortunately I was able to import the 477MB one successfully, also overnight, so there was only about 90 minutes of work lost (not including the time spent trying to fix the project). Not great, but could have been much, much worse.

I opened up the projects in TextWrangler to see if there was an obvious difference in the actual code. Sure enough, the 840MB project had about a million lines of code compared to the 400,000 lines from the original 20MB project.

Most of that new, extra code appears to be devoted to links to render files. Doing some research on this problem, there was apparently a bug in CS5 and 5.5 that caused the project’s links to its render files to be duplicated within the project code whenever you did a “Save As…” command. This issue with the Media Encoder is probably connected to that older bug in some way.

I love Premiere CS6 and we’re not going to stop using it because of this, but it’s a doozy of a problem that should be addressed ASAP, in the short term by some sort of community notice so that people don’t walk into this problem and lose work, and in the not-as-short-term with an update that fixes this.

Jon

“If you can describe what it is, that’s not it.”

[Jon Howard]

Hi there,

It’s a bit of a hack workaround, but it works for me. Set your in and out in the Premiere timeline and then use either the lift or extract keystroke (by default it’s the semicolon key for lift and apostrophe key for extract). The section you had marked with the in and out will be removed from the timeline and saved to your clipboard.

Now, Command-Z to undo and your timeline will be repaired, but the clipboard contents will still be intact. From here you can paste the content you had just lifted/extracted anywhere you like.

It’s functionally the same as Command-C to copy, with only the added Command-Z keystroke to slow things down slightly.

Very much looking forward to having Copy/Paste from a marked timeline section added to a future release. I’ve submitted that as a feature request on Adobe’s site and I recommend you do the same, since I’ve read they prioritize feature requests by the number of times a feature is requested.

Hope this is helpful!

Jon

[Jon Howard]

Well, not totally solved.

The above solution works for single camera projects. However, the project I’m dealing has a section that was shut with 2 cameras and the source monitor, when viewing the 2 synced cameras, will not send a signal for either camera to my broadcast monitor.

Interestingly, when I conform my PAL footage to 23.98 using Modify > Interpret Footage, the broadcast monitor will do a full frame display of whichever camera is selected. However, no matter how rejigger the PAL the footage, I’m getting nothing in my broadcast monitor.

Any thoughts would be greatly appreciated. Thanks!

Jon