Your system just doesn't have the resources it needs to do both at the same time. Since PP is the primary app, it's gets the resources.
I suspected it was on my end, I just didn't realize that safe guard was built into AME because when I say paused, I mean AME actually pauses and states it is doing so in the status bar.
I have to find out what is taking my resources, as I have checked when I run into the problems and both cpu usage and memory usage are low. It is happening very intermittently, as it has not happened since I posted this afternoon and I have been working all day.
The system is relatively new, a windows machine I built. Its a dedicated editing rig with an i7-2600K over clocked just a bit to about 4Ghz, plugged into a GIGABYTE GA-Z68X-UD3H-B3 Intel Z68 Motherboard with 16GB RAM. It has plenty of power as I am using a 850 watt corsair PSU. I thought it maybe was tempature based but the rig is running plenty cool. So I don't know, thought I would throw it out and see if anyone else experienced the same thing.
You don't mention your disk arrangement. You could be being bound by an IO bottleneck from a poor disk configuration. Use the tools in windows that allow you to see the hits on the CPU, Memory, and IO to see if you're bound in any of them. If the disk arrangement can't supply the data as fast as the CPU can use it, then the CPU will be in a low utilization state.
There is a thread in the FAQ that talks to configuration issues for high performance.
Thanks for the tip , I will investigate. I do not use raid arrays. I use a 1TB 7200rpm system drive that only houses the programs documents etc. My next upgrade is a SSD just waiting for them to be cost effective, the same goes for 10,000 rpm storage drives.
I then use seperate 2TB 7200 rpm drives for each project one for storing project media and used as media cache, and then another for all my outputting files. Every project I consider a raid array, but to be honest I am always hesitant to do it. Partly because of my inexperience with using them and partly because I read mixed reviews on which raid system to use and the actual benefit. I know performance will increase as it spreads the writing and reading over different drives, but my system has been as efficient as I have needed.
PS...everything is backed up to two other storage drives of my own and to a client drive for a total of three copies of everything, one of which is stored off site.
Thanks again....I am going searching for my bottle neck
This has nothing to do with your system configuration, we intentionally pause encoding so all available resources are available for playback.
why does it only happen intermittently? I imagine it depends on how much resources are needed to play the particular asset on the time line?
Thanks again for your help, at least I know I am not crazy. By the way, is this new as of the latest update to either AME or PPr, as I have just started noticing it?
Is there a way to shut this featurre off? It slows my work flow if I cannot background transcode while I work on other segments. I would rather have choppy playback on the timeline than nedia encoder pausing everytime I push play?
There's no user setting for this. Your only other option would be to wait for the export to finish.
I have the exact same issue here... Whenever I analze for poeple i.e. When I hit play in PPRO AME will stop (pause) analyzing...
Something liike the background rendering process in Final Cut X.... FCPx will render in the back as along as you dont hit play or do anything taking up sys-resources.
I dont think this issue pertains to system resources.. I think AME stops analyzing ASA you use Premiere !
Apparently its a new feature to give all resources to PPr when using playback. It is actually counter productive for me who encodes my sequences as I go along, while I continue to edit. I have found a bit of a work around though. It seems to only happen when I export from the time line to AME, then anytime after that if I hit play in Premiere AME pauses.
However, if after I export, I shut down Premiere and then open the project again, AME will continue its encode and I can work normally in premiere.
I totally agree, if I have time to wait for a render I'll export without using AME, the beauty of AME for me is that it's a background process and my machine is easily capable of allowing me to continue editing while AME does it's thing. Please consider adding a user option to disable this feature Adobe as I want my machine to be able to multitask.