[Al Bergstein]

Which version of Vegas are you using? 11 and 12 can actually use the CUDA, for better and worse. If it’s an older version, it didn’t use CUDA but used that memory of yours to render. That might be why it works better, but I have no idea if Parallels has some oddities with it’s use of the non CUDA card on the Mac. So it seems you are saying you are using both a Windows version of Premiere 6 and Vegas under Parallels on the Mac? Personally, I wouldn’t expect the best performance from the graphics on that setup. there’s always overhead going from the underlying OS to the hosted one. It’s not a recipe for best performance, just a recipe for being able to occasionally run Windows apps on a Mac. Virtualization is usually better reserved for low performance apps. We are running apps like Vegas and Pr that should be running natively on the computer they are on. You might get by with simple clips working as you claim, but it seems when the clip gets complex, the engine is stalling. I nest routinely using multi clip, but don’t have performance problems.

If you have to stay on the Mac, then get Adobe to switch out your version and reload it as a Mac version of the app. But remember, you still don’t have a CUDA based card, so your rendering will not be optimized. But running natively it might run better because Adobe *might* be able to manage the graphics better with the engine running with your 16GBs directly. See if you can prove that first if some of your coworkers have the same setup with Pr on Apple.

I also have Pr running on a “backup” machine, a 13″ mac book Pro i7 8GBs RAM with no CUDA. Performance sucks. It’s only for field use and then I don’t expect it to be anything but sluggish in the renders. And that’s running natively!

Al

[Al Bergstein]

I assume you mean you are using W7 64 bit. (I know that’s a “duh” statement, but you likely know the old saying that assumptions can make an *ss of u and me”.

You may be running out of resources under Windows. Can you bring up Taskmanager (cntrl/alt/delete and choose Task Manager) and see what your actual memory useage is at that point? Whey you say “10 films” do you mean 10 clips or that you are importing 10 unique projects with all their attendant Fx? And what if you just render it directly from Premiere rather than throwing it to Encoder, a problem that seems to crash as much as it runs on some days (“headless” crash reports).

Al

[Al Bergstein]

By the way, my original MXF footage is Canon xf305. It’s worked fine until now. The whole thing has worked fine until now. If I could get by deleting all the files Adobe has created (essentially if I could reset the program without reinstalling), I’d love to try that. I’m not that deep into this project that I couldn’t recreate all the rendered views. The odd thing is that when I render the footage so that the timeline is green all the way through (or black, meaning that the footage matches, right?) then it works, at least until I add some new footage to it. That’s how I’m ‘limping” along, as well as killing the Adobe process and restarting the app.

To be clear, I’ve been using Pr for about a year, having come from both Vegas Pro and a couple of years of FCP 7, and this is my first major problem with it. I’ve loved that it’s been rock solid until now. Wish it had more of the automation tools that FCP had though.

I’ll limp through today, in case anyone has a better idea, and will go post over on the Adobe forums.

Al

[Al Bergstein]

Didn’t seem to change anything. I just got the error again. Things seem to be curiously messed up. I tried to render a sequence out to MXF. The headless crashed each time, (not totally unusual, but it couldn’t complete even once). I also got an error message when I bypassed the Media Encoder and just went strait to rendering it out within Pro. It managed to continue to render it to MXF but when I got done and imported it into Pro, it didn’t play the clip when I clicked on it.

The interesting thing to me is that to totally clear Adobe from RAM, I have to go into Task Manager and kill the process after exiting the program. So it’s not closing properly, it appears. Once I kill the process and reopen the app, I can then play the sequence, for a while. It’s very curious. Task manager also shows lots of RAM open, no memory leaks at work, nothing unusual. It appears, to be just choking on footage, sort of like it can’t quite process the audio (like when you bring in new footage and it has to process that audio). What’s happening is like it sees the audio at first when I bring it in at startup of the app, then loses it. If I exit without killing the Premiere process (or shutting down the machine), then it still exhibets the behavior on startup again.

So this project is large, for me. It is showing as 34 MBs. I have a wide variety of clips at play here, but only MXF and MOV. The MXF are the default sequence(s) unless I shot nothing but MOV.
I have tried rendering the visualization, all green lines on top but that doesn’t seem to fully help.

There are no special effects, yet.

Is it worth re-installing Premiere? This has cost me the better part of a day screwing around with this.

Let me detail this again:
Premiere is installed on C There hundreds of GBs of storage avaialble there.

All project files are on F which is a RAID 1 array. It appears to be functioning normally. 800 GBs free space on 2TBs.

All Renders are taking out to an external drive like I always do. Lot s of space available there too.

I’d really like to not reinstall as I have Boris installed and it would take me hours.

Thoughts?

Al

[Al Bergstein]

Tom, the media cache files say that the location is C:UsersAlAppDataRoamingAdobeCommon.

Under it the Media Cache Database is located at F:adobe media cache

Should I delete both? I assume only the cache files on C:

Al

[Al Bergstein]

Updating this post. I just encountered this very issue today.
Using Adobe CS 6.0.3
Windows 64 Bit 8 GBs RAM
Happens in new projects and old.
New timelines also affected, it appears.
Was not happening as recently as yesterday.
No changes made to the computer.
Only changes is that I have combined timeines (Imported) from one project to another.
Video shows yellow or Green.
I have rerendered the footage to show all green on timeline.
Only way around it is to reboot the computer, it comes back after a while. The problematic timelines work fine for a while, then this starts happening.

Anyone have a clue?

Al

[Al Bergstein]

What Guy Said. (G). Also, I have a 5Dmkiii and it runs fine with the Mixpre-d when I need two mics. I can turn off the AGC, and I assume that the newer GH3 allows the same, but Guy’s thoughts are likely correct. The GH3 seems to be a fabulous camera for the price, a good friend got one.

Question for Ty: I have that splitter cable, but doesn’t that cut the signal strength in half also, meaning more gain and likely more hiss? I read that somewhere after buying the cable. Of course, hiss removal is relatively simple these days.

Al

[Al Bergstein]

I’m curious. I’ve not needed to mic Skype yet for live recording, but would think that if you have a computer feeding Skype to a studio, why would you have a problem if you are running the audio feed out of the computer’s audio jack and into a mixer, then mixing it with the rest of the room you are in? If the speaker(s) are using a headset mic, or even a standard studio radio hanging in front of them, and feeding back into the computer it would likely be ok, right? At the far end, they would simply be hearing what you were saying into the mic. Or not? I ask be I occasionally help out at a local radio station and they haven’t yet set themselves up doing this kind of thing, and I have thought it would be a good idea.

Just figuring I’d be prepared for the day this happens.

Al

[Al Bergstein]

Brad, what are you trying to render? I have the 570 also. I found that it Vegas 11 was unstable when using multimonitors, or working with NewBlueFX in the same timeline as the video clips. How I stabilized it was to simply only ever use one monitor, and to do all FX editing I could on a new timeline, render it and then add the rendered footage back in. I work in primarily mxf footage off a Canon and also do some work with MOV using Canon HDSLR work.

Oddly, my work (I have been reworking some older projects) has been extremely stable since I started doing that. Depressing in that it severely limits the usefullness of Vegas “Pro”.

Specifics:
[Display]
Operating System: Windows 7 Ultimate, 64-bit (Service Pack 1)
DirectX version: 11.0
GPU processor: GeForce GTX 570
Driver version: 306.97
DirectX support: 11.1
CUDA Cores: 480
Core clock: 732 MHz
Shader clock: 1464 MHz
Memory data rate: 3800 MHz
Memory interface: 320-bit
Total available graphics memory: 4096 MB
Dedicated video memory: 1280 MB GDDR5
System video memory: 0 MB
Shared system memory: 2816 MB
Video BIOS version: 70.10.49.00.78
IRQ: 16
Bus: PCI Express x16 Gen2

[Components]

easyDaemonAPIU64.DLL 1.10.8.0 NVIDIA Update Components
WLMerger.exe 1.10.8.0 NVIDIA Update Components
daemonu.exe 1.10.8.0 NVIDIA Update Components
ComUpdatus.exe 1.10.8.0 NVIDIA Update Components
NvUpdtr.dll 1.10.8.0 NVIDIA Update Components
NvUpdt.dll 1.10.8.0 NVIDIA Update Components
nvui.dll 8.17.13.0697 NVIDIA User Experience Driver Component
nvxdsync.exe 8.17.13.0697 NVIDIA User Experience Driver Component
nvxdplcy.dll 8.17.13.0697 NVIDIA User Experience Driver Component
nvxdbat.dll 8.17.13.0697 NVIDIA User Experience Driver Component
nvxdapix.dll 8.17.13.0697 NVIDIA User Experience Driver Component
NVCPL.DLL 8.17.13.0697 NVIDIA User Experience Driver Component
nvCplUIR.dll 4.8.750.0 NVIDIA Control Panel
nvCplUI.exe 4.8.750.0 NVIDIA Control Panel
nvWSSR.dll 6.14.13.0697 NVIDIA Workstation Server
nvWSS.dll 6.14.13.0697 NVIDIA Workstation Server
nvViTvSR.dll 6.14.13.0697 NVIDIA Video Server
nvViTvS.dll 6.14.13.0697 NVIDIA Video Server
NVSTVIEW.EXE 7.17.13.0697 NVIDIA 3D Vision Photo Viewer
NVSTTEST.EXE 7.17.13.0697 NVIDIA 3D Vision Test Application
NVSTRES.DLL 7.17.13.0697 NVIDIA 3D Vision Module (0)
nvDispSR.dll 6.14.13.0697 NVIDIA Display Server
NVMCTRAY.DLL 8.17.13.0697 NVIDIA Media Center Library
nvDispS.dll 6.14.13.0697 NVIDIA Display Server
NVCUDA.DLL 8.17.13.0697 NVIDIA CUDA 5.0.1 driver
nvGameSR.dll 6.14.13.0697 NVIDIA 3D Settings Server
nvGameS.dll 6.14.13.0697 NVIDIA 3D Settings Server

Al

[Al Bergstein]

Find someone with a Windows machine and see if it can read it.

Al