Premiere Pro CC multiprocessing behavior

Hi ppl. I've switched from my old workhorse Macpro to a Win8 pro 64bit setup w/ intel i7 4770K - 32gb ram- samsung pro SSD - GTX 760 2GB.
I' ve seen huuuuge improvement to my after effects workflow in terms of speed. Not the same for Premiere CC though. Already read all the threads about slow export speeds etc but cant realize something basic.
When i render-export a 2.5 hour 1440x1080 sony nx5 movie the best i get is a 3-4 hours of estimation. It starts with 7-8 hours est. but stabilizes to 3-4hr.
My issue is this. why only 25% of the ram and the cpu is utilized? No multiprocessing here?
thnx in advance..

Yes, my camera is delivering .mts avchd standard files. Also i m using some MB Looks effects in the specific footage so i guess i have to put the blame on it.
My question rised because whenever i render in After Effects i notice a full cpu utilisation of the 4 cores and all the ram i allowed the app to use. In Premiere i notice, as stated in my initial post, just a 25% ulitlisation of my system;s resources and no multiple cpu threads.
is there any way to bring Pr to use the whole resources? Its a pitty not to be able to take advantage of the systems procc power..
Thank you all for your replies

Similar Messages

Premiere Pro 2.0 crazy behavior in Windows 7

I have Premiere Pro 2.0 on a purchased disc. Yes, it's old, but perfectly good for my purposes. I was able to upload it into windows 7. The program opens fine. I can import projects made on my previous XP system. So far, so good. The problem occurs when I try to do anything with the video.
If I click on the timeline, the timeline turns white. If I click on an effect, the effects window turns white. If I click on the monitor, it turns white. Waiting for things to return doesn't help.
I suppose that the answer is that Windows 7 is not Windows XP, but this is the first time I have ever seen a new system that wasn't back-compatible with previous versions. It's only 5 years, not Windows 98!!
If anyone has a solution to this, or even an explanation, I would appreciate hearing it.

What video card do you have? What is the video card driver?
That would be my first place to look.
Good luck,
Hunt

Odd ProRes sequence set-up behavior in Premiere Pro CC

When I create a new sequence by dragging a ProRes HQ file onto New Item icon, it creates a DNxHD sequence. My ProRes HQ footage is captured by the Blackmagic Shuttle2 recorder, and MediaInfo verifies it is ProRes. Yet the sequence settings in Premiere Pro CC show:
Editing Mode: DNX 145 1080i
Video Previews box:
Preview File Format: DNX 145 1080i 59.94
Codec: DNxHD
I am on a Mac with Quicktime 7 installed. There is no problem ingesting and importing the ProRes HQ camera video files into Premiere Pro. I am just not seeing a ProRes sequence being created. Is there something else I should test for?
Thanks.

No, sadly.
I went into great deal about it here: http://forums.adobe.com/message/5457995#5457995 , and here :http://forums.creativecow.net/readpost/3/942978 ; it seems to be a 'well known' bug?
I can work around the sequence not matching the clip properties, but I want the export settings to match the clip properties (which is why I wanted the sequence settings to match the clip properties; because then I can do an export using sequence settings). I can't do that now unless I do it manually....anyway, see my first link above for the details.
Thanks!
~Michael

Adobe's move to a more "Final Cut" Premiere Pro is not all good.

Hi everyone. I don't post very often and I decided to do so because I want to hear people's comments on this subject. I have been a premiere pro user since Premiere Pro 2.0 and I've a good handle on Final Cut and Media Composer. To this day, I've always preferred Premiere for a number of reasons.
As of late, many Final Cut users have been migrating to other NLEs and in response to that the latest iteration of Premiere (Premiere CC) has included some decidedly FCP-ish features (And some Media Composer-ish stuff too). In my opinion, some are rather welcome additions and some are not.
What prompted me to write this is the feeling I got when I started using CC. It felt like in the rush to welcome the newcomers, some things were lost for those of us who has stuck by adobe for years.
Here's my list of good and bad:
Good stuff:
1) Auto Locate - Premiere is now smarter at finding your files. Awesome!
2) You can now select clips and move them up and down in tracks with keyboard shortcuts. Great!
3) You can move target and source tracks with keyboard shortcuts! In fact there are many new things you can do with keyboard shortcuts! (Can you tell I like keyboard shortcuts?) I'll leave the keyboard alone now. Yay! Ok now I'll leave it alone.
4) Audio Clip mixer. Now, I really don't see when I would use this, but sure. Why not? It's not invasive and they kept my track mixer as awesome as ever. I'm sure final cut users could shed some light as to it's utility. Specifically, what can you do now, that you couldn't without the Clip Mixer?
5) There are a few cool ways to expand tracks. (I've heard it works a lot like Media Composer).
6) You can now customize the buttons on your audio tracks. Sweet! (Also feels a bit Media Composerlike)
Bad stuff:
1) Symmetrical transitions - This is meant as a feature for Final Cut users but it's actually horrible to me. I don't want my start point to mess with my end point. I want to put them both exactly where I need them and have them stay. I know you can hold shift to get the old behavior back but I find I'm holding shift a lot these days.
2) Transition icon changed to a suspiciously fcp looking transition. It's smaller. I don't see the advantage of changing the look. I certainly don't see the advantage of making it smaller. Not a big deal, but not a fan.
3) The "fx" box replaced the name of the parameter whose keyframes you are currently seeing inside the clip. Now you can't tell which parameter you are looking at. Is this an attempt at removing clutter? Cause I think allow for the user to customize clip info is a better approach than simply removing stuff.
4) The clips now turn white when selected. Again I remember complaints of clips not being obviously selected but now you lose the label color when you select a clip. This means that if you select a bunch of clips, you can't use the color to see if you picked up something that should've stayed unselected.
5) Audio display now shows half of the wave instead of the doubled mirrored wave it always showed before. This sucks. Every DAW I've ever used (Pro Tools, Digital Performer and Audition to name a few) shows the mirrored wave. It's kinda standard. This new view is actually harder to look at. The negative view of the wave (the part of the wave that isn't the sound) looks like the bottom part of a wave. It's very distracting and annoying.
6) Work area bar is gone. This isn't such a big deal since the functionality has been added to the in and out marks, but since the work area bar is also a part of After Effects, this makes Premiere work differently than it's family of apps. I would think that having overlapping or similar tasks performed similarly throughout the Creative Cloud Apps would make a lot of sense to Adobe.
Again, Adobe Premiere Pro has been and still is my NLE of choice. This isn't an angry rant. I simply felt it was an update that removed some great functionallity and wondered if others felt the same. I'm sure my list is both incomplete and of course simply an opinion. I'd love to hear people's reaction to the new Premiere Pro CC. Do try and be nice though.

Jim.
Agreed. You can't please everyone every time. Though user customization goes a long way I think. And I definitely feel like this release was not really targeting me.
shooternz - Too bad. I did know this. It's not such an imposition but it does change the way I work without gaining anything I wanted. Seems like a lot of people actually like the symmetrical transitions though. Me, I think it is only useful when you don't care about being very precise. Maybe not. Maybe there's a good use for it. I haven't found it. I just wish there was a way to make the default behavior what it used to be and the symmetrical transitions work with shift. I'm already getting used to holding shift all the time so I'm not worried. I just don't see much advantage.

Mercury Engine in After Effects CS5.5? Or, why is After Effects so much slower the Premiere Pro?

Take this quote :
"by Todd Kopriva on Apr 25, 2010 at 8:08:14 am
'Mercury' is a marketing name for these performance improvements in Premiere Pro: - multiprocessing
- multithreading
- 64-bit application
- use of CUDA to to some processing on supported hardware
The first three of these are in After Effects CS5. (The first two have been in After Effects for much longer.)"
However, if I drop my Canon 5D Mark II footage (h264) into Premiere Pro it plays back SO MUCH better then the exact same footage in After Effects. Why is that? I DO NOT have an NVideo card and I have NOT applied any effects or scaling to the clip, just raw footage dropped into each program.
I do notice that After Effects has to render to play back (green bar being generated above footage). But it does slow very slowly, like 9fps. Premier Pro seems to cruise right along at near realtime. This is 24fps 1080p footage. One other point of interest, I have encoded the clip into Cineform codec as well. On Premier Pro I can tell a difference, the cineform scrubs a lot smoother then the original H264 clip. But, again, in After effects both the h264 and Cineform clips are very slow to render and scrub.
Any improvements along these lines for CS5.5?
Am I just missing something obvious?
Thanks for any info,
--greg.

Gregory Seattle wrote:
I think the problem is that hitting the space bar and hitting '0' (ram preview) both draw that green bar, and both seem to use it if it is already there. I guess the real difference is how that green bar gets generated. It does seem to get generated faster when I ram preview as opposed to hitting the space bar. Using both cores I have I guess (early 2009 24" iMac).
When you hit the space bar, AE TRIES to play back as it renders each frame. Imagine what happens if it's a comp with 120 3D layers that all accept lights and cast shadows. That's why you don't use the space bar.
In a RAM Preview, AE fills up the memory available to it with rendered frames, then plays them back from RAM. Depending on processor speed, dimensions of comp & frame rate, this may or may not be real time, but there are ways to get real time. With the space bar, you don't stand a chance at real time.
Gregory Seattle wrote:
From what I hear new iMacs are due out soon with the new Thunderbolt (!) and Sandy Bridge processors/chipsets. Should be a LOT faster then what I have now.
For AE work I'd say maybe yes, maybe no. To make AE REALLY speedy, you need a lot of processor cores and a boatload of RAM. iMacs aren't known for either of those things.

Premiere Pro crashes after quit - Mac OSX Lion

Greetings,
Symptoms:
I'm experiencing a consistent crash behavior after quiting Premiere Pro (ver 5.5.1 and 5.5.2). The complexity of the project doesn't seem to matter and once it crashes, i get the prompt indicating the app encountered a serious error and will try to save the project. I then get the usual crash report prompt to send to apple followed by the adobe crash report a few minutes later (must be why i see "dynamiclinkmanager" in top for a bit after PP crashes).
If I reopen PP, I'm prompted with a dialog box asking if I want the last project opened. If I say yes, I'm back to a crash before any assets load (unexpected serious error and the app will need to close) followed by the crash reports again for apple and adobe. Basically, i get one chance to make a project and it goes bad when closing the application.
I'm using an install from a DVD, but had also tried the web version. I was able to create a couple projects with the web version (trial) and then when I got the DVD, i believe i used that for updating/authenticating, etc - maybe that's where things went south (anyone else observe a similar pattern?). I didn't think too much of mixing the DVD content with the web install, so the steps around how i mixed those two sources is somewhat fuzzy.
For reference, i'm pasting the crash report inline. To reproduce, I just had to open PP, click no when asked to open the last project that unexpectedly quit, and then just hit quit and got the crash. I didn't do anything other than accept the project defaults in order to test out hitting command-Q.
If I can provide futher info to help with a repro, please let me know.
Any help is appreciated and thanks in advance,
Todd
<<begin crash report>>
Process:         Adobe Premiere Pro CS5.5 [280]
Path:            /Volumes/VOLUME/*/Adobe Premiere Pro CS5.5.app/Contents/MacOS/Adobe Premiere Pro CS5.5
Identifier:      com.adobe.AdobePremierePro
Version:         5.5.2 (5.5.2)
Code Type:       X86-64 (Native)
Parent Process: launchd [126]
Date/Time:       2011-12-08 21:42:17.998 -0800
OS Version:      Mac OS X 10.7.2 (11C74)
Report Version: 9
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
objc[280]: garbage collection is OFF
terminate called without an active exception
abort() called
Message was edited by: Jeff Bellune. Edited for brevity.

Thanks for reply zikade, here's my rig:
Model Name:          Mac Pro
Model Identifier:          MacPro5,1
Processor Name:          6-Core Intel Xeon
Processor Speed:          2.66 GHz
Number of Processors:          2
Total Number of Cores:          12
L2 Cache (per Core):          256 KB
L3 Cache (per Processor):          12 MB
Memory:          64 GB
ATI Radeon HD 5770:
Chipset Model:          ATI Radeon HD 5770
Type:          GPU
VRAM (Total):          1024 MB
Regarding en/disabling the mercury engine, is there another place to toggle that? I didn't think i had any other choice at this time with my card option (until i get a nvidia cuda card). FWIW, When creating a new project, the options in the drop down menu for "Video Rendering and Playback" is greyed out with "Mercury Playback Engine Software Only" as the selected option.
I was also thinking of putting a fresh Lion install on another disk (bah, would prefer to not have to do this since I have other stuff all nice and set up on current OS install), but at this point I'm fine to take the hit and level the playing field w/ a fresh OS, image that for downstream testing if a fresh install is needed again, and then start installing things one at a time until something goes wrong.
It seems (i hope) this error could be caused by something pretty basic as it is a complete showstopper. Unless somehow what I'm doing is super unique, there would be other folks out there dead in the water, to, but making waves.

Premiere Pro CS5.0.4 -Will not play any video- reinstall didn't help

here's my system info -
Model: MacPro5,1, BootROM MP51.007F.B03, 4 processors, Quad-Core Intel Xeon, 3.2 GHz, 16 GB, SMC 1.39f11
Graphics: ATI Radeon HD 5870, ATI Radeon HD 5870, PCIe, 1024 MB
   ----------------I only use one monitor, 1920x1200, 32bit color depth
   ------------------No Capture Card, No Sound Card or I/O box
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Serial ATA Device: HL-DT-ST DVD-RW GH61N
Serial ATA Device: TSSTcorp CDDVDW SH-222AL
Serial ATA Device: Hitachi HDS722020ALA330, 1.82 TB
---------- This 2tb Hitachi is my data drive - there are 600GB free (33%)
Serial ATA Device: OWC Mercury Extreme Pro SSD, 223.57 GB
   ---------This 250gb SSD drive is my system/application drive - 120GB free (50%)
Serial ATA Device: OWC Mercury Extreme Pro SSD, 111.79 GB
------------this 125GB SSD I use as a project-specific drive to serve up video very quickly when i'm generating Video material using the software VDMX
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd300000 / 2
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0220, 0xfd320000 / 3
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000 / 2
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x5a110000 / 3
FireWire Device: built-in_hub, Up to 800 Mb/sec
i've been using Premiere Pro for about a year and a half with no trouble, no crashes that i can remember.   I updated to 5.0.4 when it came out and experienced no problems.
I have not made any changes to my system (drivers, programs, etc.) since the last time i worked with Premiere Pro with no trouble. The only difference is that i generated approx. 52GB of new video files (mov. uncompressed 32bit 640x480 resolution) that i was beginning to edit in to a music video.
My current problem is:: there is absolutely no playback of video in 5.0.4.   not in the tiny project window preview, not in the source preview, and not in the timeline/canvas window.   when i push PLAY, the button turns into a square STOP button, but nothing happens.   this is independent of project or file type. The project i was working on when playback stopped is using uncompressed 640x480 32bit Quicktime files and one 44khz/16bit .AIFF file.   as a quick doublecheck, I just added a 640x480 Apple Intermediate Codec file and it also will not play back.   I opened older projects and none of them will playback.
My problem started while i was working on a project. I was working on the project for probably an hour and a half with no trouble. Then it seemed to get a bit sluggish and i could hear the HD churning a little more.   After rendering out a short section (just under 10 seconds), PPro did not play back the just rendered (now greenline) section. Immediate playback of rendered material was the default behavior, and this was the first time ever that the just rendered section did not play back.   I then discovered that no video would play back at all--in any of the windows.   I can scrub through all the video without any trouble--all the frames are there.
I shut down PPro, & restarted. No change.   I restarted my computer. No change.
Realizing that the problem was likely related to a lack of space on my data drive, i deleted approx. 500GB of files off my 2 TB drive, leaving just under a 1/3 of it free. i checked the drive for errors, and defragmented it. Premiere Pro still wouldn't play any file from any project.
The files are fine, they will playback anywhere else (several different file types involved in different projects). The files are compatible with Premiere Pro (uncompressed VGA resolution Quicktime .mov), i was editing on the timeline with them for hours before all video playback stopped.   All other Adobe programs (After Effects, Photoshop work fine).
I tried to find an answer/solution on these forums, unsuccessfully.   After uninstalling PPro and reinstall (did not help), and entire Suite uninstall, Adobe Clean, and reinstall, neither version 5.0.0 or 5.0.4 will play video --the no playback problem has persisted.
I was running out of HD space --i had less room than i thought -- down to about 7% of free space, a bone-headed move on my part. I'm not surprised that playback performance got compromised due to lack of space.   But i'm shocked that the problem is persisting.   Fortunately, i had just backed up my entire system the day before. (i've backed up many times before and this never affected PPro performance)
i tried to "CLEAN" the media cache for the sequence but it had no effect (in searching the forums, i saw somebody else have their 'crashing Premiere Pro' problem solved by hitting this button). I just took a look in the user/application support/adobe/common/5.0 to look at the "Media Cache" folder and the "Media Cache Files" folder.   Neither of them are empty, even after hitting the CLEAN cache button in the main preferences 'Media' settings window.   I don't know if this is the correct behavior or not.   (i'd expect a "clean" command to empty the folder, but i'm not the programmer)
This does not appear to be the ATI/5.0 problem that so many Mac users suffered (i was lucky to never have that problem).    Again, i've never had any problems with Premiere Pro over the last year and a half, until working on this latest project with the Hard Drive very low on space.   I'm 99.9% positive that's at the heart of the issue.
I don't understand why a clean reinstall did not help in this regard. The problem is clearly PPro specific.   I found one topic in the forum where someone else experienced this same "no video playback" problem, but there was never follow-up from the user saying whether or not his problem was solved (or what was done to correct the problem).
I'd love to get some help--- seems to be a very rare issue, but right now, i can do no video editing. btw, i started a new project as well and imported a .mov file -- same problem, no video playback.
the weird thing is that i can actually still edit video. i just rearranged my timeline assets and rendered out a minute-long quicktime (Apple Intermediate Codec) .mov and it looks and plays as it should.    This is really weird. I'm baffled -- there must be some way to fix this.   I don't want to have to go back to Final Cut, certainly not when i've already paid for Create Suite 5 Production Premium and EVERYTHING works except for video playback in PrPro.
thanks in advance for your help
Message was edited by: magneticjak
Message was edited by: magneticjak

hello.   hey, thanks very much for writing back. i got some good info with a search or two. (info about what regedit is and what corresponds to it in OS X -- regedit allows you to edit "preference" keys for individual programs, OSX's equivalent for these keys are the .plists in User & System: Preferences and Application Support)
what i ended up doing was uninstalling Premiere Pro (not the suite, just PPro).   Then i deleted a few preference files:
from User /Preferences/Adobe:
com.adobe.AdobePremierePro.plist
com.Adobe.Premiere Pro.5.0.plist
and from System Preferences:
the file: Adobe Premiere Pro Prefs
and..
/.../Premiere Pro/5.0/...
AMEPrefs.xml     (i noticed that there's also a preference file in Media Encoder's own folder so i didn't sweat this one)
Debug Database.txt
Placeholder Preset.epr
PostEncodeCmds.pref
PresetCache.xml
Trace Database.txt
NOTE:
of course i don't know if deleting any files beyond the 2 .plist files in User Prefs was necessary, but... it seems to have worked.
I then reinstalled Premiere Pro CS5, and fired up an old project and i've got playback of HD and DV files, and snappy editing and rendering, so hopefully i'm good to go.   I'm just going to stick with v5.0.0 because i actually don't remember ever having any trouble with it, and i don't remember v5.0.4 adding anything i was 'missing' or 'needed'
hopefully, this thread will be useful for any future folks that run into trouble - and it's got a solution for both Windows and OS X
happy editing,
peace

Why does my entire computer freeze while opening or using After Effects or Premiere Pro CS5?

Just built a computer to meet all requirements for Adobe, Autodesk 3ds Max, and UDK, for school.
Specs;
Motherboard - ASRock X79 Extreme 4-M, Socket 2011 - Micro ATX - 4 DDR3 1600/1333/1066/800 - 3 PCI-E 3.0 x 16 - 7.1 CH HD Audio - PCIE GLAN - 3 SATA3 - eSATA3 - 4 SATA2 - 4 USB 3.0 - 10 USB 2.0
Processor - Intel Core i7 Processor - i7-3820 LGA 2011
Processor fan - Intel Thermal Solution RTS2011 AC
RAM - Ballistix by Crucial - 2x 8GB Tactical PC3 - 12800 CL8 1.5 VW/XMP = 16GB RAM
SSD - Crucial M4 SSD 128GB - Comptatibility with 6Gb/s & backward compatible with SATA 3Gb/s
HDD - Seagate Barracuda 1TB - 7200 RPM up to 32mb cache
Power Supply - Cooler Master Extreme Power Plus 700W
Graphics Card - EVGA - NVIDIA GeForce GTX480 - DirectX11 - CUDA - OpenCL Support - PhysX Technology - OpenGL 4.1 (so says the box it came in; but if I'm not mistaken I think the command prompt had shown OpenGL 3 or 3.2)
Disc Driver - LG DVD/CD RW... It is an OEM, Windows claims it is updated.
I use an external component - USB Microsoft Wireless Mouse & Keyboard 2000.
I have, as far as software goes...
Windows 7 64-bit SP1
Adobe Creative Suite 5, student version or what have you.
- I do have several plugins installed as well for After Effects only.
Autodesk 3ds Max 2012
-I have several maxscripts as well as a couple plugins for 3ds Max.
UDK 2-2012 & 3-2012
NVIDIA PhysX Lab 1.1
NVIDIA Texture Tools 2
NVIDIA plugin for Photoshop
xNormal
ConTEXT
UnCodeX
Quicktime
AVG Free
Malwarebytes
7-Zip
Java
Sculptris
As for anything else giving me issues I haven't noticed anything besides a previous Graphics Card wasn't supported very well at all with 3ds Max, it would freeze while using the material editor which was fixed with replacing a GTX550 ti with a more compatible GTX480. Thought maybe the upgrade would also solve the fact that almost everytime I go to start up and/or use After Effects or Premiere Pro CS5 my whole system freezes. Whether or not I'm doing anything, it occasionally happened during "Scrubbing" the timeline, but also during the splash load up screen. Would take the time to wait for several minutes but nothing would change. Hard reboot was needed. After countless hours of searching online I stumbled upon what is called an "Unlock" for Premiere Pro/After Effects to allow accelerated GPU and CUDA cores. Simple procedure, seems as if things go faster... When it is working. But still, I encounter freezes on my entire system. It isn't a crash back to Windows or anytihng. Just a complete freeze on the entire system. I have not extensively used other Adobe programs besides Photoshop quite briefly just so I could open menus and force a freeze within 5 minutes and noticed nothing wrong. Which in AE & PP just running through any of the menu windows can quickly cause a sudden freeze.
note* I have alternated shutting off and turning on OpenGL as well as multiprocessing. Doesn't matter, it really doesn't seem to change much of anything.
Alas, I am absolutely sure, after checking and re-checking 80+ hours over the past 2 weeks that yes, everything is updated as far as each individual program, software or hardware will allow me to update them. I have reinstalled Windows as well as each program up to 3 times, and 1 system (restore?) I had Windows dump everything, started from scratch, backed up nothing. To reinstall everything from scratch, while not installed several "Utilities" or software components from stuff like the Motherboard and its XFAST USB/LAN or whatever, thinking maybe it was cluttering up anything.
Please, if anyone has any ideas upon this and could give me advice, whether you notice any other incompatibilities or anything. Any and all advice would be greatly appreciated. Thank you.
note* I do not have a wired Keyboard or mouse to disable the USB plugin and attempt that route.. at least not yet, its on my list of things to do. Also, I did run Memtest86+ during a boot and it claims that everything there had passed 100%. I am not "overclocking" anything either. I just wanted something I could work smoothly on, that would have decent rendering capabilities. I used to use my girls' laptop which was an HP with 3GB RAM and never experienced crashes or freezes and I could use AE, PPro, 3ds Max with some lag but not any issues. Rendering took forever on it, but I usually avoided that 'cuz it would start heating up pretty fierce. Saved my rendering for school computers where I could. But either way, now I have this expensive piece and it is getting frustrating that I cannot work on it.
note* Also, incase it does help, I have Windows as well as any major components installed onto the C: drive (aka SSD for my system) while all my secondary software, such as Adobe, Autodesk, etc. are all installed directly to my D: drive (or HDD) And everything is set up to go through Windows Firewall as well.

Thanks all. I have just tried a few things, installing them onto the C drive as you all specified as not being one of them. I can understand it, but at the same time i have a classmate who has their software on a seperate drive and it runs smoothe. I'm on my second GPU in 2 weeks, unless I have terrible luck it seems doubtful being that I can run games and a majority of the software no problem. Through further testing around with a corded mouse and keyboard I've noticed the following...
The computer freezes entirely only when I'm performing a "scrubbing" action or using a mouse. Left clicking, scrolling, or moving it around. Otherwise if I do not use the mouse and I make all my actions, such as "scrubbing" in AE via "Page Up & Down" keys, there's no freeze and it preloads the preview no problem.
"Scrubbing" does not load a preview (the green bar doesn't load at all while scrubbing). But, also noticed no matter how smoothe everything is running in 3ds Max as well as PPro, once I start performing a "scrubbing" action with whatever timeline I use, it will definately freeze my whole computer, Windows and all. Hard reboot is neeed.
With having gone through 2 GPU's, done a full memtest via Windows 7 and Memtest86+, there seems to be no issue with my memory or GPU. Like I said, I've run UDK without an issue. Whether the editor or game. The USB doesn't seem like it's the cause, I've used both wireless as well as wired keyboards/mouse. Still freezes, but now only when using a mouse to "Scrub".
Is it possible my motherboard could be incompatible somewhere? I mean, really.. everything is brand new but 2 weeks of troubleshooting.
And I do plan on trying to run my software off the C drive, I just wanted to make sure it wasn't something else, like I said, I've seen and used a computer where it all runs off the D drive and it runs perfectly, actually better on his computer than off the C drive at my schools. So if it is an issue would it lie within the fact that I'm using an Nvidia GPU? Considering my classmate is using a AMD/ATI Radeon or something like that.
Again, to those who replied, your shared knowledge is greatly appreciated, thank you.

Vob Import Question in Premiere Pro CS4 4.1

Hello,
Prior to posting, I read numerous posts related to importing vob files in Premiere. None of them seemed to address the particular problem I am experiencing, and I was hoping to find an answer here in the forums. Here's what I am attempting to accomplish:
1) Export the vob files (there are 4 of them) from a commercial movie DVD to hard disk
2) Import the vob files into a Premiere Pro CS4 4.1 project
3) Build a sequence out of the 4 vob files
4) Replace the sound in two very short segments to eliminate profane language so that my children may watch the movie
5) Import the sequence into Encore CS4 and burn a standard DVD
I was successful in all of the above steps 1-5. So what's the problem? I noticed, when viewing the output DVD, that at a certain point (only a single point) in the movie, the sound was garbled and the frames got 'wonky' (a technical term I picked up from Deke McClelland). My first assumption, was that I had messed something up somewhere in my editing process. When I navigated to the problematic time in my Premiere project, I saw that there was a problem in that at a certain point, the video would flicker, after which the audio would be out of sync with the video and would remain so until the end of the sequence. If instead, I simply navigated within the sequence to a few seconds past where the problematic frames seemed to be, all would be well (audio and video in sync). So, this means to me, that at the point where the problematic frames seem to be, Premiere has trouble interpreting them, and from that point on, the sequence is affected. If the seemingly problematic frames are skipped, then Premiere does not enter its bad state.
The next troubleshooting step was to start afresh, and see if the problem existed prior to making any edits to the sequence (i.e. steps 1-3 above). The problem still existed.
The next troubleshooting step was to see if a media player exhibited the same behavior as Premiere. So I took the same vobs and viewed them with Windows Media Player 11. There was no problem viewing the exact same vob in Media Player 11 that essentially is not viewable in Premiere Pro CS4 4.1. Hmm.
The next troubleshooting step was to see if an encoding program would exhibit the same behavior as Premiere. I imported the same vobs into TmpEnc, and when viewing them, no problems were exhibited.
Although not conclusive, it appears that there is a bug in Premiere Pro CS4 4.1.
Another problem that I noticed with vobs, is that sometimes, Premiere Pro CS4 4.1 does not recognize the proper frame rate of a standard DVD vob file, e.g. given 5 vobs that comprise a single movie, the first vob is shown as simply a video file (i.e. no audio at all) @ 29.97 fps in the Project panel, but the subsequent 4 vobs are recognized correctly as having both audio and video @ 23.976 fps. As before, I validated that the apparently problematic vob (from the Premiere Pro CS4 4.1 point of view) renders/plays perfectly fine in other applications (i.e. no audio or video problems). I attempted to use 'Interpret Footage' to rectify the problem with the vob, and when I type in 23.976 fps, it takes it, but then displays in the Project panel as 23.98 fps. It didn't fix the problem, but I was wondering if diplaying 23.976 as 23.98 (as opposed to 23.976 which is shown for the non-problematic vobs) is another problem.
Thanks much for any and all help,
Matt
My system specs, if needed:
OS - Vista Ultimate SP2, x64, fully updated
CPU - Xeon e5440 x 2
RAM - 16 Gb
Master Collection CS4 with all updates installed

Welcome to the forum.
Now, you have several problems, but most are with your choice of equipment and your workflow, not your choice of an NLE.
I took a wedding video from 1990 on a VCR tape and turned it to digital via a Dazzle hardware unit that plugs into the computer. It gives me vob files with no menus or anything like that
Few people have ever been able to get a Dazzle to work. This is true, even with the Pinnacle software, that often comes with it. It is an AVID product now, as they bought Pinnacle, and if you can get it to work at all, you are ahead of 99% of all owners. Stop by the Pinnacle fora and type in Dazzle. You will get the idea quickly.
A far better workflow would be to use a VHS player, hooked to an A-D device, like the Canopus/Grass Valley 110, or their 300. Use the Edius software that comes with it, to Capture DV-AVI Type II files w/ 48KHz 16-bit Audio. There will be zero OOS issues.
Most other equipment and workflows are kludges and seldom work at any level.
A good workman does not blame his tools. He might blame his choice of tools, but not the tools. Unfortunately, you chose a piece of hardware that doesn't usually work with the included software, and are blaming a great NLE program, because you are trying to work with horribly bad footage.
Please do yourself a favor. Donate the Dazzle to Goodwill, and look at the Canopus/Grass Valley 110. The price differential is not that great, and you will keep all of your hair.
Good luck,
Hunt
PS just did 34 VHS tapes via the above suggestions (some LP and some EP), and got many hours of usable footage. Not one glitch. No OOS. Every file edited perfectly in PrPro and I delivered 15 DVD-5's, that the client loved. I paid for a Canopus 300 with just my time on one project.
PPS, please see my post #5 for a link to an article on VOB files.
Message was edited by: the_wine_snob Added PPS

Premiere Pro CS6 - A low level exception has occurred in ImporterMPEG

Hi Adobe Community,
I'm having a bit of an issue with the ImporterMPEG.prm plugin for Premiere Pro CS6 that's causing playback and exporting issues.
Computer Specs: Win7 PC, NVIDIA GeForce 6150SE nForce 430 graphics card
Description: After playing back video for a while, Premiere will eventually start repeatedly reporting "A low level exception has occurred in ImporterMPEG". The preview player will be completely frozen, and I'll be unable to export. The exporting will fail with a generic "Unexpected error" message.
This issue has only started a week ago. Until now, I've been able to use Premiere Pro CS6 with no issues. If possible, I'd like to avoid upgrading to CC 2014, because the CS6 version was working fine before.
So far, I've tried a few things:
• Deactivating and reactivating (which, by the way, apparently doesn't help subscription users like me, per my recent chat with Adobe support on this issue)
• Uninstall and reinstall (I didn't know about the CC Cleaner tool at the time, so I haven't tried a clean uninstall yet)
• Change the Preview File Format in Sequence Settings (from I-Frame Only MPEG which had worked since I installed the software over a year ago to Microsoft AVI)
• Crying silently to myself (this did not help, the computer is cold and cruel)
• Clearing out the media cache (which I'd never done before and let it get up to ~75GB without me noticing)
• Moving the plugin from its location in Program Files, hoping that maybe Premiere Pro would notice it was missing and to try to find a new fresh one (it didn't work)
So far, only the Preview File Format change seemed to bring relief, but the bad behavior came back after about a week.
I'm thinking maybe the ImporterMPEG.prm plugin got corrupted somehow? The one notable thing I can remember with the computer in the last few weeks was a power event that shut down my computer unexpectedly. I think I had Premiere Pro open at the time.
If it's relevant, I mostly work with .AVI, .MP4, and .TS files in my projects, all varying resolutions and FPS. I'm usually working with about 1GB of files in a project, very rarely more than 2GB.
Has anyone else had this issue? Or, even better, has anyone else resolved this issue?
Thanks!

But really, the real solution for me was to not update Premiere Pro CS6 after a reinstall. The most recent updates just do not like my computer, I guess.
Figured I should post this solution here in case anyone in the future has this problem. (relevant: xkcd: Wisdom of the Ancients)
-Sam

Premiere Pro CC 2014 with NVIDIA system freezes (Win7x64)

It appears after perhaps the last update Premiere Pro CC 2014 started freezing during editing. It appears to happen mostly with 4K material and using the Ultra key and alpha blending but may also occur with 4K titles. The sequences are 23.976 1080p, with mixed footage from the Sony A7S (50 Mbps XAVC-S/H.264) and GH4 (4K 100 Mbps H.264). There are also frequent crashes with GPUFoundation.dll (Mercury + CUDA). No freezing with software only rendering. I tried a variety of drivers when using a Quadro 5000 with no change in freeze behavior. I tried a new GTX 770 (clean driver install) and the freeze behavior and GPUFoundation.dll crashes are the same, however now even the mouse freezes. With the Quadro 5000, the entire Windows GUI would freeze (become inactive), however the mouse would still move. Thus, it appears there are issues with both NVidia drivers and Premiere Pro CUDA code path on Windows (app errors shouldn't be able to lock up the entire GUI). GPU Meter shows low GPU and GPU memory utilization during the freezes. The freezes typically occur when switching between clips during playback or scrubbing (more often with fast scrubbing). As a developer, it feels like some kind of semaphore lock / race condition, since during the freezes CPU, GPU, and memory utilization are very low. Additional hardware info: 2010 MacPro 12-Core, 24GB RAM running Win7x64 (with latest updates). Side note: PPro used to hang in memory on exit, but stopped after a recent Microsoft forced update (PPro now crashes sometimes on exit but no longer hangs in memory (used to have to kill it after exiting every time)). Has this been reported before? (A7S XAVC & GH4 4K footage is relatively new)

This crash occurred when dragging Black Video with Noise and other effects on top of alpha composited layers (+3 layers). CUDA turned the rendered area black, so I switched to OpenCL. This crash happened a few minutes later. While this would appear to be an Nvidia driver error (OpenCL), perhaps the developers can investigate. The system is very stable except when doing complex operations in PPro (and only PPro crashes). A tried and true Quadro 5000 crashed in the same way (totally different hardware and drivers).
The full debug info wouldn't post, edited shorter:
     Application Specific Signatures:
     Graphics hardware encountered an error and was reset: 0x0000001f
Process:         Adobe Premiere Pro CC 2014 [380]
Path:            /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Identifier:      com.adobe.AdobePremierePro
Version:         8.0.1 (8.0.1)
Code Type:       X86-64 (Native)
Parent Process: launchd [191]
Responsible:     Adobe Premiere Pro CC 2014 [380]
User ID:         501
Date/Time:       2014-10-01 03:13:25.803 -0700
OS Version:      Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: 3E030FD4-F38F-857C-3EB9-85D10E36AB49
Crashed Thread: 11 Dispatch queue: opencl_runtime
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x0000001f
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   com.apple.CoreFoundation       0x00007fff8bb10f15 __CFRunLoopServiceMachPort + 181
3   com.apple.CoreFoundation       0x00007fff8bb10539 __CFRunLoopRun + 1161
4   com.apple.CoreFoundation       0x00007fff8bb0fe75 CFRunLoopRunSpecific + 309
5   com.apple.HIToolbox           0x00007fff8d375a0d RunCurrentEventLoopInMode + 226
6   com.apple.HIToolbox           0x00007fff8d3757b7 ReceiveNextEventCommon + 479
7   com.apple.HIToolbox           0x00007fff8d3755bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
8   com.apple.AppKit               0x00007fff86c7424e _DPSNextEvent + 1434
9   com.apple.AppKit               0x00007fff86c7389b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
10 com.apple.AppKit               0x00007fff86c6799c -[NSApplication run] + 553
11 com.adobe.Frontend.framework   0x00000001000ca38d FE::MacApplication::RunSelf() + 45
12 com.adobe.Frontend.framework   0x000000010004898a FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
13 com.adobe.Frontend.framework   0x00000001000cbc44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
14 com.adobe.Frontend.framework   0x00000001000d2e25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
15 com.adobe.AdobePremierePro     0x00000001000018ac main + 508
16 com.adobe.AdobePremierePro     0x00000001000016a4 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib         0x00007fff8bcc4662 kevent64 + 10
1   libdispatch.dylib             0x00007fff8a0c2421 _dispatch_mgr_invoke + 239
2   libdispatch.dylib             0x00007fff8a0c2136 _dispatch_mgr_thread + 52
Thread 2:
0   libsystem_kernel.dylib         0x00007fff8bcc464a kevent + 10
1   com.adobe.dvatransport.framework 0x0000000100e294fc boost::asio::detail::kqueue_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&) + 236
2   com.adobe.dvatransport.framework 0x0000000100e291a7 boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 375
3   com.adobe.dvatransport.framework 0x0000000100e28d18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
4   com.adobe.dvatransport.framework 0x0000000100e18157 SkyConnectionEnv::MainLoop() + 167
5   com.adobe.dvatransport.framework 0x0000000100e17c09 SkyConnectionEnv::StaticThreadFunc(SkyConnectionEnv*) + 9
6   com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
7   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
8   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
9   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 3:
0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
1   libsystem_pthread.dylib       0x00007fff8c0d0c3b _pthread_cond_wait + 727
2   com.adobe.dvacore.framework   0x000000010036a0ab boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 139
3   com.adobe.dvacore.framework   0x0000000100369e18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
4   com.adobe.dvacore.framework   0x0000000100369bda boost::asio::detail::posix_thread::func<boost::asio::detail::resolver_service_base::work_ io_service_runner>::run() + 42
5   com.adobe.dvatransport.framework 0x0000000100e29bb3 boost_asio_detail_posix_thread_function + 19
6   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
7   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
8   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 4:
0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
1   libsystem_pthread.dylib       0x00007fff8c0d0c3b _pthread_cond_wait + 727
2   com.apple.CoreServices.CarbonCore 0x00007fff824bc800 TSWaitOnCondition + 108
3   com.apple.CoreServices.CarbonCore 0x00007fff824bc9ff TSWaitOnConditionTimedRelative + 172
4   com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
5   com.adobe.dvacore.framework   0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
6   com.adobe.dvacore.framework   0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
7   com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
8   com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
9   com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
10 libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
11 libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
12 libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 5:
0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
1   libsystem_pthread.dylib       0x00007fff8c0d0c3b _pthread_cond_wait + 727
2   com.adobe.GPUFoundation.framework 0x000000010941b8d6 void boost::condition_variable_any::wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&) + 70
3   com.adobe.GPUFoundation.framework 0x0000000109419705 GF::Device::AcquireExclusiveAccess() + 117
4   com.adobe.PlayerMediaCore.framework 0x0000000129518684 AdobePlayer::PlayerDisplay::UpdateWindow() + 372
5   com.adobe.PlayerMediaCore.framework 0x000000012952b2a5 AdobePlayer::PlayerMain::OnUpdate() + 21
6   com.adobe.PlayerMediaCore.framework 0x0000000129530501 PrPlayModule<AdobePlayer::PlayerMain>::PlayEntry(int, pmStdParms*, void*, void*) + 241
7   com.adobe.PlayerMediaCore.framework 0x0000000129530390 xPlayEntry + 16
8   com.adobe.PlayerHost.framework 0x00000001057238c4 ML::CallPlayerModuleGuarded(int (*)(int, pmStdParms*, void*, void*), int, pmStdParms*, void*, void*, int*, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 276
9   com.adobe.PlayerHost.framework 0x0000000105721669 ML::PlayerModule::CallPlugin(int, void*, void*) + 153
10 com.adobe.PlayerHost.framework 0x0000000105745c36 ML::VideoPlayer::CallPlayModuleSelector_Update() + 86
11 com.adobe.PlayerHost.framework 0x000000010573421d ML::VideoPlayer::ForceDisplayRedraw(ML::PlayerOutputQuality) + 205
12 com.adobe.PlayerHost.framework 0x0000000105728a34 ML::PlayModuleThreadQueue::ExecuteDeferredCall(ASL::ObjectPtr<ML::DeferredCallBase, ASL::AtomicValue>) + 340
13 com.adobe.PlayerHost.framework 0x0000000105727935 ML::PlayModuleThreadQueue::ServiceQueue() + 293
14 com.adobe.dvacore.framework   0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
15 com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
16 com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
17 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
18 libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
19 libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
20 libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 6:
0   libsystem_kernel.dylib         0x00007fff8bcc3716 __psynch_cvwait + 10
1   libsystem_pthread.dylib       0x00007fff8c0d0c77 _pthread_cond_wait + 787
2   com.apple.CoreServices.CarbonCore 0x00007fff824bc9e7 TSWaitOnConditionTimedRelative + 148
3   com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
4   com.adobe.dvacore.framework   0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
5   com.adobe.dvacore.framework   0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
6   com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
7   com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
8   com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
9   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
10 libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
11 libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 7:
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   libcuda_334.01.03_mercury.dylib 0x00000001223f85a2 cuosEventWait + 210
3   libcuda_334.01.03_mercury.dylib 0x000000012233e922 intHandlerMain + 114
4   libcuda_334.01.03_mercury.dylib 0x00000001223f9479 cuosPosixThreadStartFunc(void*) + 41
5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 8:
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   libclh.dylib                   0x000000011ae0fe19 0x11a800000 + 6356505
3   libclh.dylib                   0x000000011a8c5df2 0x11a800000 + 810482
4   libclh.dylib                   0x000000011ae10c69 0x11a800000 + 6360169
5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 9:
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   libclh.dylib                   0x000000011ae0fe19 0x11a800000 + 6356505
3   libclh.dylib                   0x000000011a8c5df2 0x11a800000 + 810482
4   libclh.dylib                   0x000000011ae10c69 0x11a800000 + 6360169
5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 10:
0   libsystem_kernel.dylib         0x00007fff8bcbfa1a mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff8bcbed18 mach_msg + 64
2   libclh.dylib                   0x000000011ae0fe19 0x11a800000 + 6356505
3   libclh.dylib                   0x000000011a8c5df2 0x11a800000 + 810482
4   libclh.dylib                   0x000000011ae10c69 0x11a800000 + 6360169
5   libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
6   libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
7   libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
Thread 11 Crashed:: Dispatch queue: opencl_runtime
0   libsystem_kernel.dylib         0x00007fff8bcc3866 __pthread_kill + 10
1   libsystem_pthread.dylib       0x00007fff8c0cf35c pthread_kill + 92
2   libsystem_c.dylib             0x00007fff8c131bba __abort + 145
3   libsystem_c.dylib             0x00007fff8c131b29 abort + 140
4   libGPUSupportMercury.dylib     0x00007fff89db41ca gpusKillClient + 111
5   libGPUSupportMercury.dylib     0x00007fff89db4b51 gpusQueueSubmitDataBuffers + 155
6   libclh.dylib                   0x000000011a90ee26 0x11a800000 + 1109542
7   libclh.dylib                   0x000000011a8b104a 0x11a800000 + 725066
8   libclh.dylib                   0x000000011a8b10a1 0x11a800000 + 725153
9   libclh.dylib                   0x000000011a8b4394 0x11a800000 + 738196
10 libclh.dylib                   0x000000011a910425 clhCtxSynchronize + 21
11 com.nvidia.web.GeForceGLDriverWeb 0x00001234402e627d gldFinishQueue + 234
12 com.apple.opencl               0x00007fff87917abe 0x7fff87911000 + 27326
13 com.apple.opencl               0x00007fff87931123 0x7fff87911000 + 131363
14 com.apple.opencl               0x00007fff8793414a 0x7fff87911000 + 143690
15 libdispatch.dylib             0x00007fff8a0c028d _dispatch_client_callout + 8
16 libdispatch.dylib             0x00007fff8a0c6a18 _dispatch_barrier_sync_f_slow + 460
17 com.apple.opencl               0x00007fff87933faa 0x7fff87911000 + 143274
18 com.apple.opencl               0x00007fff8792a202 clEnqueueMapBuffer + 631
19 com.adobe.RendererGPU.framework 0x0000000111714245 GF::ScopedRecordedHostMemory::Map() const + 133
20 com.adobe.RendererGPU.framework 0x00000001117685ea RendererGPU::PointwiseFilterHostNode::ApplyConcatenatedPointwiseFilters(ASL::InterfaceRef <MF::IVideoFrame, MF::IVideoFrame> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame> const&, boost::shared_ptr<RenderResults> const&, std::vector<RendererGPU::PointwiseFilter, std::allocator<RendererGPU::PointwiseFilter> > const&) + 826
21 com.adobe.RendererGPU.framework 0x0000000111767daf RendererGPU::PointwiseFilterHostNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 831
22 com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
23 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
24 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
25 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
26 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
27 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
28 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
29 com.adobe.RendererGPU.framework 0x00000001117194d5 RendererGPU::CompositorNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 1413
30 com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
31 com.adobe.RendererGPU.framework 0x000000011170f36f RendererGPU::(anonymous namespace)::RendererGPU::ProduceFrame(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, std::string*, ASL::ParamRect<int>) + 1279
32 com.adobe.PlayerMediaCore.framework 0x0000000129535bf0 AdobePlayer::RenderRequest::ProduceFrame(ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, RenderParams const&, std::string*, ASL::ParamRect<int>) + 96
33 com.adobe.PlayerMediaCore.framework 0x000000012951cefd AdobePlayer::PlayerDisplay::PresentRenderRequestImpl(boost::shared_ptr<AdobePlayer::Rende rRequest> const&) + 1901
34 com.adobe.PlayerMediaCore.framework 0x00000001295204db AdobePlayer::PlayerDisplay::PresentLastCompletedRenderRequestImpl() + 267
35 com.adobe.dvacore.framework   0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
36 com.adobe.dvacore.framework   0x00000001003919ac boost::function0<void>::operator()() const + 28
37 com.adobe.dvacore.framework   0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
38 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
39 libsystem_pthread.dylib       0x00007fff8c0ce899 _pthread_body + 138
40 libsystem_pthread.dylib       0x00007fff8c0ce72a _pthread_start + 137
41 libsystem_pthread.dylib       0x00007fff8c0d2fc9 thread_start + 13
External Modification Summary:
Calls made by other processes targeting this process:
    task_for_pid: 319
    thread_create: 0
    thread_set_state: 0
Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
Calls made by all processes on this machine:
    task_for_pid: 56776
    thread_create: 1
    thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=679.6M resident=223.0M(33%) swapped_out_or_unallocated=456.6M(67%)
Writable regions: Total=19.5G written=15.6G(80%) resident=14.2G(73%) swapped_out=3.0G(16%) unallocated=5.3G(27%)
REGION TYPE                      VIRTUAL
===========                      =======
ATS (font support)                 32.0M
ATS (font support) (reserved)         8K        reserved VM address space (unallocated)
CG backing stores                  23.8M
CG image                            584K
CG raster data                       48K
CG shared images                    204K
CoreImage                             8K
Foundation                            4K
IOKit                              78.3M
IOKit (reserved)                    268K        reserved VM address space (unallocated)
Image IO                           1032K
Kernel Alloc Once                     8K
MALLOC                              1.5G
MALLOC (admin)                       32K
MALLOC_LARGE (reserved)             512K        reserved VM address space (unallocated)
Memory Tag 241                      128K
Memory Tag 242                       12K
Memory Tag 249                      192K
Memory Tag 251                       24K
OpenCL                              1.0G
OpenGL GLSL                        1664K
STACK GUARD                        56.8M
Stack                             113.7M
VM_ALLOCATE                        52.6G
VM_ALLOCATE (reserved)             30.4M        reserved VM address space (unallocated)
__DATA                             71.6M
__IMAGE                             528K
__LINKEDIT                        225.7M
__NV_CUDA                           456K
__TEXT                            453.8M
__UNICODE                           544K
mapped file                        84.0M
shared memory                        68K
===========                      =======
TOTAL                              56.3G
TOTAL, minus reserved VM space     56.3G
Model: MacPro5,1, BootROM MP51.007F.B03, 12 processors, 6-Core Intel Xeon, 2.93 GHz, 24 GB, SMC 1.39f11
Graphics: NVIDIA GeForce GTX 770, NVIDIA GeForce GTX 770, PCIe, 2048 MB
Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 3, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 7, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.7f3 14616, 3 services, 15 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce GTX 770, Display Controller, Slot-1
PCI Card: pci1095,3132, SATA Controller, Slot-2
PCI Card: NVIDIA GeForce GTX 770, NVDA,Parent, Slot-1
PCI Card: pci1b73,1100, USB eXtensible Host Controller, Slot-4
Serial ATA Device: HL-DT-ST DVD-RW GH61N
Serial ATA Device: WDC WD1001FALS-41Y6A0, 1 TB
Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
Serial ATA Device: WDC WD4001FAEX-00MJRA0, 4 TB
USB Device: Scarlett 2i2 USB
USB Device: Keyboard Hub
USB Device: USB-PS/2 Optical Mouse
USB Device: Apple Keyboard
USB Device: My Passport 0741
USB Device: My Passport 0820
USB Device: USB3.0 Media Reader
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Logitech RumblePad 2 USB
USB Device: Mobile Keys 49
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:

Adobe premiere pro cc 2014 - constantly crashing

Naturally, my project is under deadline..
My system is running OS X 10.9.4 (13E28)
late-2012 MacBook Pro Retina
2.6 GHz Intel Core i7
16GB 1600 MHz DDR3
Intel HD Graphics 4000
NVIDIA GeForce GT 650M
768Gb Flash Hard Drive
My project consists of DSLR footage (h.264 compressed files) and Zoom H4N Audio (.WAV files)
Even after spending most of Thursday and Friday on the phone with Adobe support; deleted all files from media cache, re-imported project, waited for premiere to re-conformed footage, etc..
...I still find my project loading sluggishly.. like it takes 15 minutes until video clips in the sequence will fully loads & appear in the project window... it becomes momentarily operable before quickly becoming inoperable as the video and audio no longer playback or respond to the cursor.
At that point (when playback no longer works) I can still save the project.
It seems as though the software loses the dynamic link between the footage as it completely goes black.
Then when I try to exit Premiere CC 2014.. the program locks up and crashes with no report.
The crash reports I have are from a few days ago when they first began and before they stooped generating reports.
Majority of the errors were:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
It also crashed a few times with the following errors:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5fbfdef0
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
Any help would be greatly appreciated!

First I must say.. ADOBE PREMIERE PRO CC 2014 is glitchy as hell (and in my three weeks editing a documentary or rather two weeks bc I lost an entire week due to this issue) I have come to learn and identify some workaround solutions..
Here is what I originally wrote after speaking to five different Adobe engineers...
It is only an issue with PrCC2014 and the temporary solution before the upcoming update is to...
1) Go into Preferences... Audio... and UNCHECK the box next to "Maintain pitch while shuttling."
[this is a new feature in PrCC2014 that is processor intensive, causes audio dropouts, and is a major player in why the playback suffers]
2) Go into your sequences settings for each sequence you have for DSLR footage and change the Editing Mode preset to "CUSTOM"
3) Next scroll down to Video Previews and change the preview file format to "QuickTime" and the codec to "Animation."
4) Uncheck the box next to "Composite in Linear Color (requires GPU acceleration or max render quality).
[this is another new feature that is also processor intensive & is also a key suspect to the problem]
THE KEY TO FIXING (temporarily) THE BEHAVIOR
When your computer begins to show signs of the glitchy - sluggish playback behavior..
Stop.. go back into your SEQUENCE SETTINGS and change it to a different EDITING MODE (only temporarily) and click OK.
You could change yours from ProRes to CUSTOM (as indicated in step #3)
Next a prompt will pop up asking you...
Click okay then immediately go back to SEQUENCE SETTINGS and change it back to your original setting, in your case, ProRes.
Somehow, by DELETING those PREVIEW FILES it essentially resets the issue... until the dreaded glitchy behavior returns.
I have had luck with this trick and hopefully you will too..
Cheers!

Adobe Premiere Pro CC 2014 operating very slowly

A colleague of mine is editing a documentary. The entire length of the timeline is about 90 minutes. Every keystroke within Premiere is painfully slow. The computer operates outside of Premiere normally.
Is there something we could do to optimize her experience with Premiere? She is an Avid and Final Cut user and has never experienced this type of sluggish behavior with documentaries before.
Here are her specs:
Project specs: (she is not ready to consolidate the project at this time)

Dual video problems - Do you have dual graphics adapters?
Go to the Windows Control Panel and select Hardware and Sound and then select Device Manager... In Device manager you click the + sign to the left of Display Adapters... and see if 2 are listed
IF YES, read below
-http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
-http://forums.adobe.com/thread/1001579
-Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
-link to why http://forums.adobe.com/message/4685328
-http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2

"Media Offline" in Premiere Pro CS3 .. but it's not offline!

If anyone is able to advise on a technical problem in Adobe Premiere Pro (CS3), I'd be most appreciative I'm hoping someone will be around anywhere to help solve this...
Please look at:
http://www.thepfjstudios.com.au/images/PremiereProblem.jpg
to understand my issue better. (Img 1440x900, approx 210kb)
In the upper left box are the videos in the project. This issue is with all videos in the project, but for the example, I'm looking at the highlighted video, MOV03C_03.mpg. The thumbnail at the top of the list shows the video is working, I can play it fine by pressing the play button next to the thumbnail.
The same video, MOV03C_03.mpg, is in the timeline at the current point of the cursor. The current timecode is 00:00:55:22 (hh:mm:ss:ff). I don't understand why the monitor on the upper right corner is showing the video (and all videos in the project) as "media offline", when they're all in the project and able to be played, therefore *not* offline.
Is there some way I can fix this? It's for a university project that I'm needing to deliver to our customer this week...

The guy that said "if an Asset appears as Off-line, it is because the Asset IS Off-line" obviously hasn't seen this problem before.
You are absolutely correct here. Most users have not seen this problem before. In my search of these fora, I found only this, and one other thread where this behavior was reported. In all others, the problem came about because of things like Paths changing (external drive letter changes were the most common). There were cases where the Path was changed by Renaming, Moving and Deletion, but only this, and one other instance, where something else intruded.
Now, it appears that you also encountered the issue, so that runs the count up to three. There are possibly others, who have never posted here, but we cannot count them, unless one searches every possible forum on the Internet.
It is good that you have found a way to get around the issue, and thank you for posting that.
I do, however, have a little problem with your attitude. A forum respondent can only comment of problems that they have had, observed from others, or have read about. If few users have encountered this issue, it might seem that it is related to but a few Projects, systems, or users' actions. If it were a universal Bug, it would seem most logical, that many others would have encountered it, and reported it.
You are correct. I have not encountered this problem, and it appears that most other users are in the same exact position. Maybe we do something differently, or our systems and Projects are different enough, that we have just been spared. I am not sure that is a bad thing.
Again, thanks for posting your keystrokes to handle the problem, when it arises. I hope that will help others, when they show up.
Good luck,
Hunt

Syncing footage with music track issue in Premiere Pro CC

My experience with Premiere Pro is still limited to basic editing. Recently I've been asked to help out a friend to edit a music video. I've done this before in Final Cot Pro X but decided to switch due to the integration of Adobe CC.
The issue I am facing is that all footage that has been shot is delivered to me at 23.976 fps but with the audio playing faster. The audio track after importing is being played back at 29.97 fps and plays at normal speed.
The solution I have found so far is to slow down each clip to 80% so it matches the original audio track. This is not ideal I found out while editing, so it would be better to have each clip rendered to its original state of 29.97 fps.
After some more research I discovered that it is possible to re-render each clip to its original speed in After Effects, and even apply frame blending. Then import all back in Premiere Pro.
My question is if the road I am following here is the correct one.
Thank you!

by reducing the speed in the timeline, i think it does the same thing as forcing interpret footage. the difference is by changing it in the bin before starting, you can change all clips at once. just make sure to set the sequence fps to the final output fps, not matching the changed fps of clips. you can also right click the footage on the timeline and choose frame blend, but i think it ends up doing the same thing as the export option you are using. the difference on the timeline is you can see the frame blend while editing. AE is extremely slow and might not look any better, so where u are on deadline, forget about it. so in premiere i think frame blend on vs off is your only real option to change the behavior of the slow-mo.
the slow mo trick is nice for music videos, but yeah, for best results the camera needs to be sped up with the song on set. then in post both are slowed back down, replacing the song/audio with the original song at normal speed. 23.976 or 29.97 are both acceptable in NTSC usa land. 23.976 has gotten alot of attention as the "film look" since it has more motion blur, while 29.97 has a cleaner video look. below are some numbers i found somewhere and kept. so if the final render fps is known, can choose the correct shooting fps for on set with matching sped up or slowed down music. the italic values would be used to end up with sped up footage, while the Bold values would be used for slo-motion effect. i haven't used these but the numbers look right. he could have shot at 29.97(30) fps and slowed it down to 23.976 in post to get the 80% slow-mo.
For an NTSC/US, using a 24p timebase, for the following frame rates, adjust the song speed to:
12 fps: make song last 1.956x longer by stretching it to 51.1% speed
18 fps: make song last 1.333x longer by stretching it to 75.0% speed
20 fps: make song last 1.226x longer by stretching it to 81.6% speed
22 fps: make song last 1.067x longer by stretching it to 93.7% speed
26 fps: make song last 0.907x as long as normal; play it at 110.25% speed
30 fps: make song last 0.800x as long as normal; play it at 125% speed
32 fps: make song last 0.747x as long as normal; play it at 133.87% speed
36 fps: make song last 0.672x as long as normal; play it at 148.81% speed
48 fps: make song last 0.498x as long as normal; play it at 200.80% speed
60 fps: make song last 0.400x as long as normal; play it at 250.00% speed
For an NTSC/US, using a 30p timebase, for the following frame rates, adjust the song speed to:
12 fps: make song last 2.445x longer by stretching it to 40.91% speed
18 fps: make song last 1.667x longer by stretching it to 60.00% speed
20 fps: make song last 1.533x longer by stretching it to 65.23% speed
22 fps: make song last 1.333x longer by stretching it to 75.01% speed
24 fps: make song last 1.250x as long as normal; play it at 80.00% speed
26 fps: make song last 1.134x as long as normal; play it at 88.22% speed
32 fps: make song last 0.933x as long as normal; play it at 107.14% speed
36 fps: make song last 0.840x as long as normal; play it at 119.05% speed
48 fps: make song last 0.622x as long as normal; play it at 160.73% speed
60 fps: make song last 0.500x as long as normal; play it at 200.00% speed

Premiere Pro CC multiprocessing behavior

Similar Messages

Maybe you are looking for