Hardware requirements for Premiere Pro CS5 .versus Premiere Elements 9 ?
Hi
I have just started to work in Premiere Elements 9. What should it take to go up one "level" and start using Pro version (CS5) from a hardware performance point of view ?
Below are my overview specification for the machine I'm using. Will it take more power into consideration ?
Processor : Intel Core i7 930, 2,8 Ghz - 4 kernels, 8 logical processors
RAM memory : 6 GB
64 bit operating system Windows 7
HD Drive1 : Intel SSD Sa2M080 G2Gc ATA Device - 80GB
HD Drive2 : Samsung HD103SJ ATA Device - 1 TB
Video Card : NVIDIA GeForce Gt240 (1 GB RAM for video card)
BR
H
CS5 is at http://forums.adobe.com/community/premiere/premierepro_current
What KIND of files are you going to edit?
Your system should do OK for DV and HDV but "might" struggle a bit with something like AVCHD due to only 6 gig of ram (I know, saying "only" 6 gig sounds odd, but if you go to the Premiere Pro CS5 Benchmark http://ppbm5.com/ page and review results, you will see that some people have 24 gig)
As far as C drive size, I have Win7 64bit Pro and MS Office full install and CS5 Master Collection and some odds'n'ends, and I only use 50 gig of drive space, with as much as possible in the way of "work" files set to my 2 other drives
My CS5/AVCHD 1st Impressions http://forums.adobe.com/thread/652694?tstart=0 includes a link to the computer I built
My 3 hard drives are configured as...
1 - 320G WD Win7 and all programs (50 used)
2 - 320G WD Win7 swap file and PPro projects
3 - 1T WD all video files... read and write
Similar Messages
-
Hardware requirement for master collection cs5
hi guys, just a newbie here. i'm a web/flash game-animation hobbyist, just thought to take the notch next level by adding production softwares of adobe by taking in mc cs5.
I got a few questions before buying this monster suite.
my machine is a laptop dell stud 17 core i5 2.93Ghz max, 4MB RAM, 1GB VC, 64bit W7. 500GB HDD 7200rpm
my machine has only 1600x900 video display - mc cs5 recommends 1280x1024; what is the disadvantage, if i don't use their recommended spec and stick to my min display?
what is the "DVD-ROM drive compatible with dual-layer DVDs for?" is it required in installation or just a requirement in video production; say burning/reading dual layer format disc as reference and or burning in that format as final projects? my dvd is just the regular +/- single layer RW drive. No blue ray at the moment.
Adobe-certified GPU card for GPU-accelerated performance in Adobe Premiere Pro--- will 1GB ATI Mobility Radeon™ HD 5650 Graphics Card do the job? this is all i have.
Any help will do. thanks guys!!I wanna ask is it my display or something else. Im using 1366x768.
Yes it is. The system requirements are there for a reason, not just for fun. These apps all have tons of palettes and require extra space for displaying timelines, compositions and video previews and even if they could be installed with such a small screen res, working with them would be no fun at all because things would get cut off or you would be forced to shuffle palettes around all the time. You really need a qualified computer.
Mylenium -
Premiere Pro CS5.5 vs Elements 9
Hi,
I'm about to upgrade my Premiere version; I have an opportunity to get CS5.5 at a deep discount so that the price difference to Elements 9 doesn't matter. Having said this, I am only a home user who edits AVCHD 1080p movies to blu-ray, I'm not doing heavy sophisticated editing, and I don't see myself using more advanced features in the future. My hardware is Win 7 Pro 64bit, AMD Phenom 1090T (6x core 3.2GHz), 8GB RAM, GeForce 210 graphics.
My questions:
- How much faster is CS5.5 vs Elements 9 on the given hardware for processing AVCHD?
- What do I loose in Ease-of-use and pre-created material such as menus for CS5.5 vs. Elements 9?
- What would you recommend?
Thanks,
AlexHi Harm,
thanks for your response! I'm looking for a "point-and-shoot" solution, but one that has the best performance on my hardware. Simply speaking, I'd like the quickest way to produce raw AVCHD footage into a reasonably polished BD, both quick in terms of editing effort and conversion processing.
To take the DSLR comparison, while common DSLRs allow all kinds of manual manipulation, they have all the automatic modes of the point-and-shoot cameras. If CS5 would be the same, my decision would be easy. But given that CS5 apparently leaves out the "point-and-shoot" modes, I would only go for it if it is dramatically faster than Elements.
Thanks,
Alex -
Premiere Pro CS5.5 Upgrade is Downloaded and Installed, but 5.0 Isn't Updating
Hi there. I may be missing something very simple here, but here goes: I already have Premiere Pro CS5 on my system, and I just purchased, downloaded and installed the 5.5 upgrade a little while ago, but CS5 isn't upgrading. It's still opening as Version 5.0.3.
It didn't ask me for my serial number at installation, which made me think it found what it was upgrading, and I've tried restarting, but to no avail.
Any help is much appreciated. Am I missing a step?
Thanks!
StephenHi,
Premiere pro CS5 and Premiere Pro CS5.5 are installed as seperate programs.
So Premiere Pro cs5.5 might have installed as a seperate program.
Check the all program list for the same.
If you face issues, just contact adobe technical support. -
Premiere Pro CS5 Crashing "Adobe Premiere has stopped working"
Premiere CS5 has started on my Windows 7 64 system, after working for only about 10-15 minutes. After doing a reinstall, reading through forums, and updating drivers, nothing's working. It really doesn't seem like anyone else has had this problem. Based on the suggestions of someone with a similar problem in Photoshop CS5, I ran a registry fix up. The problem persists.
My event viewer showed the follwoing error, which I have posted below. This is slowing me down tremendously, so help is appreciated. It might also be worth noting that, thinking this was a Windows error, I contacted their forums. They thought it was an Adobe code error.
SS
Log Name: Application
Source: Application Error
Date: 05/12/2010 1:58:38 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Owner-PC
Description:
Faulting application name: Adobe Premiere Pro.exe, version: 5.0.2.0, time stamp: 0x4c731297
Faulting module name: MSVCR90.dll, version: 9.0.30729.4926, time stamp: 0x4a1750b0
Exception code: 0xc0000417
Fault offset: 0x0000000000054fc0
Faulting process id: 0xf18
Faulting application start time: 0x01cb94479d2ad0e5
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba 83fe554\MSVCR90.dll
Report Id: 15ce75e0-003d-11e0-b0a2-485b3914204f
Event Xml:
1000
2
100
0x80000000000000
6595
Application
Owner-PC
Adobe Premiere Pro.exe
5.0.2.0
4c731297
MSVCR90.dll
9.0.30729.4926
4a1750b0
c0000417
0000000000054fc0
f18
01cb94479d2ad0e5
C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba8 3fe554\MSVCR90.dll
15ce75e0-003d-11e0-b0a2-485b3914204fThe way that I would work this would be to do a search on my system for msvcr90.dll. I expect you'll find half a dozen or more. Compare the version numbers of the files that you find in Adobe Media Encoder to the ones you have in Premiere Pro. If all the version numbers match except for one, replace the one that doesn't match. On the other hand... if all the version numbers match, replace the ones in Premiere Pro with the ones in Media Encoder. When you replace files make sure you copy files from one location to another, don't actually remove the files from the source location.That probably goes without saying, but better safe than sorry.
Make sure to post back and let others know whether you have success or failure with this trick.
Mitch -
Adobe premiere pro cs5 hangs at start up
Hi everyone
I have a question. Upon starting adobe premiere pro cs5 64 it hangs at startup. Can any one suggest a solution.
thanks you!!!I have the same issue. Hangs at the splash at "Loading Importer Quicktime Bundle". Last update today 7/3/2011 (ver. 5.0.4). Since my initial purchase, I have never been able to load this program and been muddling along with iMovie begrudginly (I have used earlier versions of PP with little problems).
Here is my configuration:
Model: iMac11,3, BootROM IM112.0057.B00, 4 processors, Intel Core i7, 2.93 GHz, 8 GB, SMC 1.59f2
Graphics: ATI Radeon HD 5750, ATI Radeon HD 5750, PCIe, 1024 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 2.1.14.5
Bluetooth: Version 2.4.0f1, 2 service, 19 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HDS722020ALA330, 1.82 TB
Serial ATA Device: OPTIARC DVD RW AD-5680H
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfd100000
USB Device: My Book 1130, 0x1058 (Western Digital Technologies, Inc.), 0x1130, 0xfd130000
USB Device: My Book 1110, 0x1058 (Western Digital Technologies, Inc.), 0x1110, 0xfd140000
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0xfd110000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0xfd120000
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfa100000
USB Device: My Book 1130, 0x1058 (Western Digital Technologies, Inc.), 0x1130, 0xfa130000
USB Device: Hub, 0x04cc (NXP Semiconductors), 0x1521, 0xfa140000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0xfa111000
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0xfa120000
The Apple problem report error for PP CS5 contains the following:
Date/Time: 2011-07-03 21:23:36 -0400
OS Version: 10.6.7 (Build 10J869)
Architecture: x86_64
Report Version: 7
Command: Premiere Pro
Path: /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/Adobe Premiere Pro CS5
Version: 5.0.4 (5.0.4)
Parent: launchd [219]
PID: 2128
Event: hang
Duration: 7.63s (sampling started after 2 seconds)
Steps: 37 (100ms sampling interval)
Pageins: 19
Pageouts: 27
Process: Adobe Premiere Pro CS5 [2128]
Path: /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/Adobe Premiere Pro CS5
UID: 501
Thread 1df4a
User stack:
37 start + 52 (in Adobe Premiere Pro CS5) [0x100003494]
37 main + 167 (in Adobe Premiere Pro CS5) [0x100003bd7]
37 (anonymous namespace)::CallStartupFramework(int, char const* const*) + 288 (in Adobe Premiere Pro CS5) [0x100003650]
37 (anonymous namespace)::LaunchFrontendFramework(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*) + 168 (in Startup) [0x10b5c9c08]
37 AppMain + 214 (in Frontend) [0x10b481736]
37 FE::Initializer::Initializer(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 60 (in Frontend) [0x10b47146c]
37 FE::Initializer::PrivateImpl::PrivateImpl(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 124 (in Frontend) [0x10b47334c]
37 FE::(anonymous namespace)::MZInitializer::MZInitializer() + 411 (in Frontend) [0x10b4726cb]
37 MZ::Initializer::Initializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool) + 106 (in Mezzanine) [0x10579394a]
37 MZ::(anonymous namespace)::FullInitializer::FullInitializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool) + 447 (in Mezzanine) [0x10579a2cf]
37 MZ::(anonymous namespace)::MLInitializer::MLInitializer() + 247 (in Mezzanine) [0x105799ed7]
37 ML::PluginSupport::LoadAllPlugins() + 80 (in PluginSupport) [0x10287acd0]
37 ML::PluginSupport::LoadAllPlugins(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > > const&) + 70 (in PluginSupport) [0x10287ab96]
37 ML::PluginSupport::LoadAllPlugins(std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > > const&) + 311 (in PluginSupport) [0x102879bd7]
37 ML::LoadPlugins(std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > > const&) + 2136 (in PluginSupport) [0x10285e888]
37 ML::(anonymous namespace)::LoadPluginList(ML::PluginNameList const&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1423 (in PluginSupport) [0x10285d67f]
37 ML::(anonymous namespace)::AddPlugin(ML::PluginEntry const&, bool&) + 1672 (in PluginSupport) [0x102859b98]
37 ML::LocalImporterModule::SerializeToRegistry(ASL::RegistryKey&, bool&) + 1488 (in ImporterHost) [0x103c59d20]
37 ML::LocalImporterModule::GetOneFormat(int, ML::FileDesc&) + 234 (in ImporterHost) [0x103c57dfa]
37 ML::LocalImporterModule::GetOneFormat(int, int*, int*, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&, char*, std::vector<ML::SubTypeDesc, std::allocator<ML::SubTypeDesc> >&) + 97 (in ImporterHost) [0x103c577c1]
37 ML::LocalImporterModule::CallImportModule(int, void*, void*) + 193 (in ImporterHost) [0x103c57191]
37 xImportEntry + 81 (in ImporterQuickTime) [0x1297c5d11]
37 PrImportModule<ImporterQuickTime>::ImportEntry(ASL::ResourceCollection const&, int, imStdParms*, void*, void*) + 513 (in ImporterQuickTime) [0x1297c6511]
37 ImporterQuickTime::GetIndFormat(ASL::ResourceCollection const&, imStdParms*, int, imIndFormatRec*) + 202 (in ImporterQuickTime) [0x1297be3da]
37 QT32Client::QT32Client::GetImportableFileExtensions(std::vector<QT32Server::QTImportableF ileExtensionItem, std::allocator<QT32Server::QTImportableFileExtensionItem> >&) + 487 (in QT32Client) [0x10c6061d7]
37 dvacore::threads::SyncPoint::Wait() + 127 (in dvacore) [0x100177c8f]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df58 DispatchQueue <multiple>
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff867c4128]
37 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff867c47fe]
37 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff867c4cd4]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Thread 1df5f
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 AMTThread::Worker(void*) + 28 (in amtservices) [0x120d4ecbe]
37 _AMTThreadedPCDService::PCDThreadWorker(_AMTThreadedPCDService*) + 92 (in amtservices) [0x120d47cce]
37 AMTConditionLock::LockWhenCondition(int) + 37 (in amtservices) [0x120d4ec53]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df60
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 PrivateMPEntryPoint + 63 (in CarbonCore) [0x7fff88c82335]
37 ASL::(anonymous namespace)::TaskProc(void*) + 96 (in ASLFoundation) [0x100461810]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df73
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df74
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 SkyConnectionEnv::StaticThreadFunc(SkyConnectionEnv*) + 9 (in dvatransport) [0x100605039]
37 SkyConnectionEnv::MainLoop() + 76 (in dvatransport) [0x100604fcc]
37 boost::asio::detail::task_io_service<boost::asio::detail::kqueue_reactor<false> >::run(boost::system::error_code&) + 517 (in dvatransport) [0x100627405]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Thread 1df75
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 asio_detail_posix_thread_function + 25 (in dvatransport) [0x10060d379]
37 boost::asio::detail::posix_thread::func<boost::asio::detail::resolver_service<boost::asio ::ip::tcp>::work_io_service_runner>::run() + 53 (in dvatransport) [0x100628135]
37 boost::asio::detail::task_io_service<boost::asio::detail::kqueue_reactor<false> >::run(boost::system::error_code&) + 831 (in dvatransport) [0x10062753f]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df76
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df77
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df78
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df79
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df7a
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df7e
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df80
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 CAPThread::Entry(CAPThread*) + 125 (in CoreAudio) [0x7fff82fd1745]
37 HALRunLoop::OwnThread(void*) + 152 (in CoreAudio) [0x7fff82fe4776]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 1df82
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1df83
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1dfd2
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()()> const&, boost::function<void ()()> const&) + 99 (in dvacore) [0x100178613]
37 boost::function0<void>::operator()() const + 46 (in dvacore) [0x100110ebe]
37 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 143 (in dvacore) [0x10018027f]
37 MPWaitOnQueue + 215 (in CarbonCore) [0x7fff88caa173]
37 TSWaitOnConditionTimedRelative + 177 (in CarbonCore) [0x7fff88cb0268]
37 TSWaitOnCondition + 118 (in CarbonCore) [0x7fff88d40e13]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1dfd3
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 thread_proxy + 132 (in boost_threads) [0x1000c8ac4]
37 SkyConnectionEnv::StaticThreadFunc(SkyConnectionEnv*) + 9 (in dvatransport) [0x100605039]
37 SkyConnectionEnv::MainLoop() + 76 (in dvatransport) [0x100604fcc]
37 boost::asio::detail::task_io_service<boost::asio::detail::kqueue_reactor<false> >::run(boost::system::error_code&) + 517 (in dvatransport) [0x100627405]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Thread 1dfe6
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 asio_detail_posix_thread_function + 25 (in dvatransport) [0x10060d379]
37 boost::asio::detail::posix_thread::func<boost::asio::detail::resolver_service<boost::asio ::ip::tcp>::work_io_service_runner>::run() + 53 (in dvatransport) [0x100628135]
37 boost::asio::detail::task_io_service<boost::asio::detail::kqueue_reactor<false> >::run(boost::system::error_code&) + 831 (in dvatransport) [0x10062753f]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 1e0d6
User stack:
32 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
32 __workq_kernreturn + 10 (in libSystem.B.dylib) [0x7fff867c3f4a]
Kernel stack:
32 bsdthread_create + 1313 [0x4d22d1]
Binary Images:
0x100000000 - 0x100003fff com.adobe.AdobePremierePro 5.0.4 (5.0.4) <95920D41-C4A7-3166-A177-A98B1AE92CBD> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/Adobe Premiere Pro CS5
0x1000c6000 - 0x1000ceff3 com.adobe.boost_threads.framework boost_threads version 5.0.0 (5.0.0.0) <76962F4C-CF91-F183-6A31-B125F2E0C9CE> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/boost_threads.framework/Versions/A/boost_threads
0x1000dd000 - 0x10025dfe7 com.adobe.dvacore.framework dvacore version 5.0.0 (5.0.0.0) <EE0F0B45-64C9-8876-3AD6-C3E977A43A2E> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/dvacore.framework/Versions/A/dvacore
0x100428000 - 0x10048eff5 com.adobe.MediaCore.Frameworks.ASL.Foundation 1.0 (1.0) <4FF2D43F-B418-E775-89B6-B73C2156BA59> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/ASLFoundation.framework/Versions/A/ASLFoundation
0x1005e2000 - 0x100658ff7 com.adobe.dvatransport.framework dvatransport version 5.0.0 (5.0.0.0) <F301D928-436B-73AD-D192-73344BC87744> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/dvatransport.framework/Versions/A/dvatransport
0x102852000 - 0x102889fff com.adobe.MediaCore.Frameworks.PluginSupport 1.0 (1.0) <E07FDF10-7D8A-87A9-16FD-B4F406612A9E> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/PluginSupport.framework/Versions/A/PluginSupport
0x103b79000 - 0x103d1eff7 com.adobe.MediaCore.Frameworks.ImporterHost 1.0 (1.0) <DD4913EC-FFA7-BDD8-EBD9-522F98217029> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/ImporterHost.framework/Versions/A/ImporterHost
0x105635000 - 0x105cc4fff com.adobe.Mezzanine ??? (1.0) <7F6314D6-EC48-C6FE-1D71-24EF3BA91C74> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/Mezzanine.framework/Versions/A/Mezzanine
0x10b401000 - 0x10b4d3ff5 com.adobe.premiere.frontend 1.0 (1.0) <04994BF5-94AE-9F07-A4A4-82407CD4E00F> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/Frontend.framework/Versions/A/Frontend
0x10b5c4000 - 0x10b5e4fef com.adobe.premiere.startup 1.0 (1.0) <E749566C-465E-D0E4-C037-92398FE605FF> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/Startup.framework/Versions/A/Startup
0x10c604000 - 0x10c666ff7 com.adobe.MediaCore.Frameworks.Utilities.QT32Client 1.0 (1.0) <217176A4-10FB-2C95-C8F8-25B8785F17EA> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/MacOS/../Frameworks/QT32Client.framework/Versions/A/QT32Client
0x120d2b000 - 0x120d9bff6 com.adobe.amt.services AMTServices 3.0.0.64 (BuildVersion: 3.0; BuildDate: Mon Jan 26 2010 21:49:00) (3.0.0.64) <52FF1F9B-9991-ECE2-C7E3-09DA1B368CBE> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/Frameworks/amtservices.framework/Versions/A/amtservices
0x1297b8000 - 0x1297fbfff com.adobe.MediaCore.ImporterQuickTime 1.0 (1.0) <2388FA12-4964-DC63-2E71-67CA12B92B3C> /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/Plug-ins/Common/ImporterQuickTime.bundle/Contents/MacOS/ImporterQuickTim e
0x7fff82fb3000 - 0x7fff83032fe7 com.apple.audio.CoreAudio 3.2.6 (3.2.6) <1DD64A62-0DE4-223F-F781-B272FECF80F0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff867a9000 - 0x7fff8696afff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff876b5000 - 0x7fff8782cfe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff88c7b000 - 0x7fff88faffff com.apple.CoreServices.CarbonCore 861.34 (861.34) <B5680539-CB31-6C6D-C0AD-606D4D46E7F5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framew ork/Versions/A/CarbonCore
Process: Adobe QT32 Server [2139]
Path: /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/Adobe QT32 Server.app/Contents/MacOS/Adobe QT32 Server
UID: 501
Process: AdobeCrashDaemon [2130]
Path: /Applications/Adobe Premiere Pro CS5/Adobe Premiere Pro CS5.app/Contents/Frameworks/AdobeCrashReporter.framework/Versions/A/Resources/AdobeCrashD aemon.app/Contents/MacOS/AdobeCrashDaemon
UID: 501
Process: AirPort Base Station Agent [260]
Path: /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
UID: 501
Thread 611 DispatchQueue 1
User stack:
37 ??? (in AirPort Base Station Agent + 5692) [0x10000163c]
37 NSApplicationMain + 364 (in AppKit) [0x7fff83a931a8]
37 -[NSApplication run] + 395 (in AppKit) [0x7fff83a9a48b]
37 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 (in AppKit) [0x7fff83ad47a9]
37 _DPSNextEvent + 718 (in AppKit) [0x7fff83ad4e64]
37 BlockUntilNextEventMatchingListInMode + 59 (in HIToolbox) [0x7fff8485d4ac]
37 ReceiveNextEventCommon + 310 (in HIToolbox) [0x7fff8485d5f3]
37 RunCurrentEventLoopInMode + 333 (in HIToolbox) [0x7fff8485d7ee]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 621 DispatchQueue 2
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff867c4128]
37 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff867c47fe]
37 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff867c4cd4]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Thread 6ff
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib) [0x7fff867ede52]
Kernel stack:
37 sleep + 52 [0x48eeb0]
Thread 700
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 ??? (in AirPort Base Station Agent + 117988) [0x10001cce4]
37 ??? (in AirPort Base Station Agent + 106856) [0x10001a168]
37 ??? (in AirPort Base Station Agent + 118817) [0x10001d021]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Binary Images:
0x100000000 - 0x100027fff com.apple.AirPortBaseStationAgent 1.5.5 (155.2) <00010203-0405-0607-0809-0A0B0C0D0E0F> /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
0x7fff83a91000 - 0x7fff84487fff com.apple.AppKit 6.6.7 (1038.35) <9F4DF818-9DB9-98DA-490C-EF29EA757A97> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff8482f000 - 0x7fff84b2dfff com.apple.HIToolbox 1.6.5 (???) <AD1C18F6-51CB-7E39-35DD-F16B1EB978A8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Ver sions/A/HIToolbox
0x7fff867a9000 - 0x7fff8696afff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff876b5000 - 0x7fff8782cfe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
Process: aosnotifyd [291]
Path: /usr/sbin/aosnotifyd
UID: 501
Thread 7a3 DispatchQueue 1
User stack:
37 start + 52 (in aosnotifyd) [0x100000e20]
37 main + 806 (in aosnotifyd) [0x10000201e]
37 CFRunLoopRun + 70 (in CoreFoundation) [0x7fff87700b46]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 7ae DispatchQueue 2
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff867c4128]
37 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff867c47fe]
37 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff867c4cd4]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Thread 7b9
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib) [0x7fff867ede52]
Kernel stack:
37 sleep + 52 [0x48eeb0]
Binary Images:
0x100000000 - 0x100011ff7 aosnotifyd ??? (???) <64A261C1-4C9B-22D5-803C-8C57D5669673> /usr/sbin/aosnotifyd
0x7fff867a9000 - 0x7fff8696afff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff876b5000 - 0x7fff8782cfe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
Process: AppleSpell [359]
Path: /System/Library/Services/AppleSpell.service/Contents/MacOS/AppleSpell
UID: 501
Thread cd9 DispatchQueue 1
User stack:
37 ??? (in AppleSpell + 4816) [0x1000012d0]
37 ??? (in AppleSpell + 5472) [0x100001560]
37 -[NSSpellServer run] + 72 (in Foundation) [0x7fff836ffeee]
37 CFRunLoopRun + 70 (in CoreFoundation) [0x7fff87700b46]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread cdc DispatchQueue 2
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff867c4128]
37 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff867c47fe]
37 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff867c4cd4]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Binary Images:
0x100000000 - 0x1000a9fe7 com.apple.AppleSpell 1.6.2 (62.2) <B3C504CB-5E66-639E-9F2A-2F184565496A> /System/Library/Services/AppleSpell.service/Contents/MacOS/AppleSpell
0x7fff83681000 - 0x7fff83904fe7 com.apple.Foundation 6.6.6 (751.53) <476E617B-B59B-53DE-991D-98C1993BCBCE> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff867a9000 - 0x7fff8696afff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff876b5000 - 0x7fff8782cfe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
Process: autofsd [45]
Path: /usr/libexec/autofsd
UID: 0
Thread 16c DispatchQueue 1
User stack:
37 ??? (in autofsd + 5340) [0x1000014dc]
37 ??? (in autofsd + 6461) [0x10000193d]
37 CFRunLoopRun + 70 (in CoreFoundation) [0x7fff87700b46]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 1a9 DispatchQueue 2
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff867c4128]
37 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff867c47fe]
37 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff867c4cd4]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Binary Images:
0x100000000 - 0x100001ff7 autofsd ??? (???) <37489FFE-D80E-6AB2-C294-9448EEF27DEC> /usr/libexec/autofsd
0x7fff867a9000 - 0x7fff8696afff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff876b5000 - 0x7fff8782cfe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
Process: blued [44]
Path: /usr/sbin/blued
UID: 0
Thread 16b DispatchQueue 1
User stack:
37 ??? (in blued + 5384) [0x100001508]
37 ??? (in blued + 151651) [0x100025063]
37 -[NSRunLoop(NSRunLoop) run] + 77 (in Foundation) [0x7fff836cc6a3]
37 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 270 (in Foundation) [0x7fff836cc7c4]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 23c DispatchQueue 2
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff867c4128]
37 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff867c47fe]
37 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff867c4cd4]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Thread 4b7
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib) [0x7fff867ede52]
Kernel stack:
37 sleep + 52 [0x48eeb0]
Binary Images:
0x100000000 - 0x100046fe7 blued ??? (???) <29B9C27D-C2DC-F6BB-6A7C-74676B61665C> /usr/sbin/blued
0x7fff83681000 - 0x7fff83904fe7 com.apple.Foundation 6.6.6 (751.53) <476E617B-B59B-53DE-991D-98C1993BCBCE> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff867a9000 - 0x7fff8696afff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff876b5000 - 0x7fff8782cfe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
Process: CleanApp Daemon [50]
Path: /Library/Application Support/CleanApp/CleanApp Daemon.app/Contents/MacOS/CleanApp Daemon
UID: 0
Process: CNQL1212_ButtonManager [272]
Path: /Library/CFMSupport/CNQL1212_ButtonManager.app/Contents/MacOS/CNQL1212_ButtonManager
UID: 501
Process: configd [13]
Path: /usr/libexec/configd
UID: 0
Thread 13b DispatchQueue 1
User stack:
37 start + 52 (in configd) [0x100000cf0]
37 main + 2051 (in configd) [0x100001506]
37 server_loop + 72 (in configd) [0x100001d5c]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 13c DispatchQueue 2
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff867c4128]
37 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff867c47fe]
37 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff867c4cd4]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Thread 13e
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 plugin_exec + 1440 (in configd) [0x1000034c3]
37 CFRunLoopRun + 70 (in CoreFoundation) [0x7fff87700b46]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 146
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 _io_pm_force_active_settings + 2271 (in PowerManagement) [0x1000ac3c5]
37 CFRunLoopRun + 70 (in CoreFoundation) [0x7fff87700b46]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 182
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib) [0x7fff867ede52]
Kernel stack:
37 sleep + 52 [0x48eeb0]
Thread 1c5
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 pppcntl_run_thread + 1595 (in PPPController) [0x10071290d]
37 CFRunLoopRun + 70 (in CoreFoundation) [0x7fff87700b46]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 1e0da
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 __workq_kernreturn + 10 (in libSystem.B.dylib) [0x7fff867c3f4a]
Kernel stack:
37 bsdthread_create + 1313 [0x4d22d1]
Binary Images:
0x100000000 - 0x100026ff7 configd ??? (???) <74FC6898-E16A-3A28-B6B5-5E185A6B1D19> /usr/libexec/configd
0x1000a9000 - 0x1000baff7 com.apple.SystemConfiguration.PowerManagement 160.0.0 (160.0.0) <11BDE066-A91E-EF41-F46E-6E05053C216D> /System/Library/SystemConfiguration/PowerManagement.bundle/Contents/MacOS/PowerManagement
0x100700000 - 0x100729fff com.apple.SystemConfiguration.PPPController 1.5 (1.5) <FD1F16E7-AA64-54FA-0985-85A5A0C43F5A> /System/Library/SystemConfiguration/PPPController.bundle/Contents/MacOS/PPPController
0x7fff867a9000 - 0x7fff8696afff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff876b5000 - 0x7fff8782cfe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
Process: ConnectService [276]
Path: /Library/Application Support/ArcSoft/Connect Service/ConnectService.app/Contents/MacOS/ConnectService
UID: 501
Process: coreaudiod [178]
Path: /usr/sbin/coreaudiod
UID: 202
Thread 440 DispatchQueue 1
User stack:
37 ??? (in coreaudiod + 2964) [0x100000b94]
37 ??? (in coreaudiod + 26320) [0x1000066d0]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 441 DispatchQueue 2
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff867c4128]
37 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff867c47fe]
37 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff867c4cd4]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Thread 443
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 CAPThread::Entry(CAPThread*) + 125 (in CoreAudio) [0x7fff82fd1745]
37 HALRunLoop::OwnThread(void*) + 152 (in CoreAudio) [0x7fff82fe4776]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 1e0e1
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 __workq_kernreturn + 10 (in libSystem.B.dylib) [0x7fff867c3f4a]
Kernel stack:
37 bsdthread_create + 1313 [0x4d22d1]
Binary Images:
0x100000000 - 0x10001fff7 coreaudiod ??? (???) <9A14795C-2B28-130F-43A3-183AB48F75D8> /usr/sbin/coreaudiod
0x7fff82fb3000 - 0x7fff83032fe7 com.apple.audio.CoreAudio 3.2.6 (3.2.6) <1DD64A62-0DE4-223F-F781-B272FECF80F0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff867a9000 - 0x7fff8696afff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff876b5000 - 0x7fff8782cfe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
Process: coreservicesd [56]
Path: /System/Library/CoreServices/coreservicesd
UID: 0
Thread 18e DispatchQueue <multiple>
User stack:
37 ??? (in coreservicesd + 3756) [0x100000eac]
37 _CoreServicesServerMain + 522 (in CarbonCore) [0x7fff88d2bace]
37 CFRunLoopRun + 70 (in CoreFoundation) [0x7fff87700b46]
37 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff87700dbf]
37 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff87701932]
37 mach_msg_trap + 10 (in libSystem.B.dylib) [0x7fff867aa29a]
Kernel stack:
37 ipc_mqueue_receive_continue + 0 [0x210cea]
Thread 18f DispatchQueue <multiple>
User stack:
37 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff867c3fc5]
37 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff867c4128]
37 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff867c47fe]
37 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff867c4cd4]
37 kevent + 10 (in libSystem.B.dylib) [0x7fff867c312a]
Kernel stack:
37 kevent + 97 [0x4783e9]
Thread 299
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 fmodWatchConsumer + 347 (in CarbonCore) [0x7fff88cdf76e]
37 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff867e4f8a]
Kernel stack:
37 semaphore_wait_continue + 0 [0x22a3e1]
Thread 29a
User stack:
37 thread_start + 13 (in libSystem.B.dylib) [0x7fff867e33a9]
37 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff867e34f6]
37 read + 10 (in libSystem.B.dylib) [0x7fff867b4986]
Kernel stack:
37 lo64_unix_scall + 77 [0x2a144d]
37 unix_syscall64 + 617 [0x4f6075]
37 read_nocancel + 158 [0x49dac1]
37 write + 312 [0x49d345]
37 get_pathbuff + 3054 [0x306b84]
37 tsleep + 105 [0x48f0eb]
37 wakeup + 786 [0x48ecc4]
37 thread_block + 33 [0x2272eb]
37 thread_block_reason + 331 [0x22725d]
37 thread_dispatch + 1966 [0x226fbe]
37 machine_switch_context + 753 [0x2a8a6e] -
Premiere Pro CS5 crash when adjusting audio gain
Premiere Pro CS5 crash when adjusting audio gain
The same on another workstations.
Have any idea?Hi Dennis,
I just had a go and can reproduce the problem straight away too.
Created a new project then a new XDCAM EX 1080p25 sequence. Imported a short Sony PMW-350 clip. Dragging it straight to the timeline and then setting audio gain is OK (Source channel mapping preferences set to mono).
However, if I Modify - Audio Channels and then set track format as stereo or mono as stereo and then drag the clip to the timeline and right click - gain, Premiere crashes about 1/2 to 1 second after the audio gain dialogue box appears. Error log below if it's useful.
Asus Rampage III extreme
Intel i7 980x @ 3.33GHz
24Gb ram
Windows 7 64 bit
Using onboard sound - Realtek HD 6.0.1.6037
Incidentally, I tried with both the default Windows 7 audio drivers and then the Realtek HD drivers installed (I'd previously forgotten to install the Realtek driver when I built the PC)
Log Name: Application
Source: Application Error
Date: 12/08/2010 14:28:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: Adobe Premiere Pro.exe, version: 5.0.1.0, time stamp: 0x4bf119d2
Faulting module name: MSVCR90.dll, version: 9.0.30729.4926, time stamp: 0x4a1750b0
Exception code: 0xc0000005
Fault offset: 0x000000000001dfcd
Faulting process id: 0x16ec
Faulting application start time: 0x01cb3a21ad8357e4
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba 83fe554\MSVCR90.dll
Report Id: 8b5dda37-a615-11df-8de4-20cf3011131b
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-12T13:28:51.000000000Z" />
<EventRecordID>2401</EventRecordID>
<Channel>Application</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>Adobe Premiere Pro.exe</Data>
<Data>5.0.1.0</Data>
<Data>4bf119d2</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.4926</Data>
<Data>4a1750b0</Data>
<Data>c0000005</Data>
<Data>000000000001dfcd</Data>
<Data>16ec</Data>
<Data>01cb3a21ad8357e4</Data>
<Data>C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe</Data>
<Data>C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e 1a05ba83fe554\MSVCR90.dll</Data>
<Data>8b5dda37-a615-11df-8de4-20cf3011131b</Data>
</EventData>
</Event> -
System requirements for Premiere Pro CS5
Adobe has on its website the Adobe Premiere Pro CS5: System Requirements
Unfortunately, this overview is severely lacking in realism and a lot of people were disappointed when their system met these minimum requirements, but still would not do what they expected, or at least not without jerkiness, hiccups and similar issues.
The problem with these requirements as stated is that they are really bare minimum requirements to install the software, but unfortunately it does not tell how well a certain system will perform with the myriad of codecs used and the different needs and expectations people may have about their editing rig. Since this issue is nearly a year old now and nothing tangible has changed, I decided to write this article to help people understand what is realistic to expect, what influences the hardware choices in order to use CS5 to full satisfaction.
CAVEAT: This is my personal opinion, in no way authorized or endorsed by Adobe, who have not seen anything I write here till the moment it has been published here.
Context:
The nature of one's editing projects can have a major impact on the hardware required to run projects effectively. Long form documentaries, delivered on BRD demand different hardware and priorities in hardware setup then music clips with lots of multicam work and color effects delivered to the web, or wedding video's delivered on DVD. And unfortunately, there is no simple rule saying that if you edit X, you need Y hardware.
The second thing that has a major impact is the source material, the codec used. Back in the old days things were very simple, you had DV material from a tape based camera and that was it. Nowadays, things have grown much more complex. The number of codecs used in source material has grown enormously, the number of formats and frame rates has grown in a similar fashion. We used to have 480, now we have added 720, 1080, 2K, 3K, 4K plus various DSLR and other formats, we had interlaced, now we have progressive as well, we used to have 25 or 29.97 FPS, now we have 24, 25, 29.97, 60 and even more frame rates. We had DV, now we have MPEG2, HDV, XDCAM, P2, AVCHD, RED, Cineform, Matrox, and numerous other codecs.
This makes it all the more confusing for people to know what they need when they start out with video editing to run CS5 successfully.
The codec issue:
Some codecs are easy to handle for a computer, others are difficult to handle. It is generally known that DV material is very easy to handle and AVCHD is pretty tough to handle. The general rule is that the more compressed the material is, the harder it is for the computer to edit this. GOP (Group of Pictures) structure is an extra burden. The higher the resolution, the harder it is on the computer.
To simplify matters one could differentiate codecs and source material in three categories, based on their properties:
Of course boundaries when using three categories are not always very clear, but the tendency is rather clear. Easy codecs are in the upper left corner, difficult codecs are in the lower right corner. For that reason we have identified three categories, Easy, Intermediate and Difficult.
This is somewhat similar to the color coding PR uses with none, yellow and red in the time line. It is not complete in the overview of common codecs, but is intended to show what the impact can be of different codecs and the hardware requirements.
I realize this is a limited overview and generic in nature. It will not answer all questions, but may be helpful to avoid disappointments. It also has a number of limitations. For instance, uncompressed MS AVI SD material. No GOP structure, no compression, low resolution, that should be at the top left corner, right? Wrong. Uncompressed does not burden the CPU, but is a definite burden on the memory and disk I/O system.
What does that mean in terms of requirements?
System requirements:
If the codecs you generally use are slightly more than just plain "easy", look at the improvemnts in the next column and repeat for the next column if applicable.
I hope this can benefit people to understand there is more to choosing a system than just following the Adobe site.
Additions or suggestions for improvements are welcome.Harm,
A while back you gave me some advice re a kit build for Production Premium, which I submitted for consideration, and for your thoughts I thank youl. Several months on, the powers that be (UK Civil Service) have decided to go a different purchase route. The request has ended up in the hands of a well known computer supplier 'chain' (a prefered supplier) and because they can't supply the Sabertooth board you recommended they have come back to my bosses with a their recommendation based on what they will supply. My question is, would you accept it, will it take advantage of CUDA and do you foresee any problems:
I am shooting with a Panasonic AG-HMC151E AVCHD. H.264 MPEG-4 compression.
The chain are quoting:
Windows 7 64 Ultimate
CS5.5 PP
on:
Intel DX58sO2 Extreme
i7-970
Trudata 12GB DDR3 PC3-8500 1066MHz Unbuffered 204-pin
HP NVIDIA Quadro 4000 2.0GB
1 x WD 450 velociraptor 10k
3 x WD 1TB AV-GP Greenpower 64MB SATA-II (NO RAID)
800W PSU
The problem with preferred suppliers is you get what you are given. Do you think there any 'conflicts' in the above spec?
Appreciate your opinion
Regards
Peter -
Good Premiere pro Cs5.5 Video Editing Computer Set Up For Under $3000
Hey everyone im hopeing to hear for Harm Millaard input on this and anyone elses who understands PC computers for video editing. I need to build a computer set up for my specific needs. I am a youtuber who makes videos for a living and I need a speedy computer for editing primarily in premiere pro CS5.5 and sometimes in After effects. I use magic bullet 2.0 color grading in almost all my videos so that slows my computer down alot. The current computer I have now shuts off when ever it runs to much stuff and gives me the BSOD so its extreemly fusterating because editing something small can take me all day because of the constent shutting off. Mostly does BSOD when I uses Magic Bullet 2.0 I shoot with DSLR footage but once in a while it will happen out of the blue when running alot of things but mostly when exporting. I need a list of specs that will all work together to give a perfect workflow for my needs and I also would like advice on what Raid because I dont fully understand it as well as what back up drives etc should I have. I plan of buying the specs and having someone build it for me and set up raid etc that knows how to do all that. In case some of you wonder what type of computer I have now these are the specs if you need more information on what I have in my computer ask exactly what info you want to me to tell you and ill look it up.
If you have advice on specs I dont have to re-buy that I could take out of this computer to save money then that would be better as well. I currently have no back up external drives as well so Idk what I should buy for that as well. Thank you all for your time a head of time!Well!!!!.....where do I start?? You must spend some time here reading all the valuable info that has been presented and discussed many times here. Basically, PPro is a very demanding , PROFESSIONAL program that needs beefy and SPECIFIC hardware to run properly.
AMD CPU will not cut it.....it lacks the necessary instruction set that Intel has that apply to video processing.
You need a fast Intel i7 CPU for starters.
You do not mention video card.....NVidia CUDA card of over 1GB video memory is required to enable the "Mercury PlaybackEngine", which provides a TEN TIMES INCREASE in rendering speed of previews.....not to mention accelerating the export process by handling some specific effects during export.
Some DSLR codecs,( like Canon MOVs) cause PPro....which is a 64bit program..... to open the 32 bit " Quick time Importer" process, ( as Quick Time is 32 bit), slowing down the process, even with good hardware. Editing highly compressed consumer codecs,( AVCHD,etc.) in real time ,then exporting can be very taxing on a computer, requiring top -notch components. Even if you do it the old way and transcode to a more edit friendly codec before editing.....you would then need a larger,faster disk system to handle the huge files at a high speed!!!
16GB system memory is OK for 5.5.....with 6 and later, 32GB is better.
Two separate hard drives are the required minimum for PPro......currently, the best performing and cheapest setup would be : C drive= 120GB quality SSD, D drive = 2x 7200 RPM HDDs in onboard RAID 0 for pagefile,previews, and all cache files. E drive= same setup as "D", for media,project files, and export. F drive = large 7200 rpm disk for necessary backup of important files and backup of "D" drive. All drives should "indexing" and" compression" turned OFF,( under drive Properties window).
Less expensive would be just three separate 7200 RPM HDDs...that could be OK with just DSLR footage which is so compressed that it requires less actual MB/sec., unless you are using many tracks of video, upping the requirement needed.
Read the many posts and articles by Harm Millard and Bill Gehrke....they have contributed a tremendous wealth of knowledge and experience to the readers.....preventing many from making bad purchases and expensive mistakes when trying to construct a machine that will perform well....their website, PPBM5 is invaluable as it can show you all the video benchmark results of differently configured machines. It is a good guide as to what you may want to build,or, purchase.....Good Luck!! -
Optimal Hard Drive Configuration for Premiere Pro CS5 and Pro Tools
I am in the process of upgrading a workstation that is used primarily for multi-track audio recording in Pro Tools to use the following Adobe CS5 products for production of promotional videos in HDV (and AVCHD for the web) as well as printed marketing materials for bands and musicians: Premiere Pro, Encore, Photoshop, Illustrator and Soundbooth.
Since Premiere Pro is probably the most demanding application of the group, I have been studying the suggested hardware configurations on this forum with great interest, particularly HARM's suggestions (including his Generic Guideline for Disk Setup) to determine which hard drives to purchase and the optimal manner in which to configure them.
I am upgrading an HP Z800 with dual quad core 2.44 GhZ processors with hyperthreading (16 virtual cores), 12 GB of memory and an overclocked GeForce GTX 470. Without setting up a RAID configuration (which I cannot afford at the moment), I would like to use the 4 available HDD bays in the Z800 in the optimal manner for Premier Pro, using currently available drives. I am currently considering purchasing a 300GB VelociRaptor to use as my C drive because of the extended load times and demands placed on the drive by ProTools and the associated Waves plug-ins.
I would appreciate suggestions to improve my following plan: C (300GB WD VelociRaptor) for OS and Programs; D (1 TB WD Black Caviar) for Media and Projects; E (1 250 GB WD Black Caviar) for Pagefile (approx. 18 GB) and Media Cache; and E (2 TB WD Black Caviar) for Previews, Exports and Pro Tools audio files.
I have great respect for the knowledge of the members of this forum and eagerly await your suggestions.
/BillI very much appreciate the responses to my email because I know that all of your time is valuable and that you have chosen to use some of that valuable time to help an unknown individual. This forum is remarkable because of the wealth of knowledge available and the willingness of so many to assist others.
I now wish to narrow my questions to save you time and so that I can get specific advice. I may not have not been clear that I have already upgraded to the HP Z800 with dual quad core processors and overclocked GTX 470, primarily for the improved performance it will provide in ProTools. My question now is how to optimize its performance for Premiere Pro CS5. Based upon my research, I am considering the following two upgrades, but I am open to other suggestions if they would provide better results at a similar cost
1. I am considering purchasing a 600GB WD VelociRaptor ( WD6000HLXH) for my C drive on which I would place OS (Windows 7, 64 Bit) and programs in an effort to reduce loading times of large programs. I have two questions: (1) Are members of the forum seeing a significant improvment in program loading times with the VelociRaptor because I am still not convinced that the price performance of SSD's justifies their use; and (2) There are so many models of VelociRaptors now that I want to be certain that I am purchasing the best version for my needs. In addition to the usual 10000 RPM speed, this model has 32MB Cache and a 3.5" form factor as well as a SATA 6.0GB/s interface (which I doubt my motherboard can take advantage of but it might extend the useful life of the drive with future configurations).
2. I currently have available for installation in the Z800 the following drives: (1) WD 2TB Black Caviar; (1) WD 1TB Black Caviar; (2) Hitachi 1TB. I believe that the Z800 can accept up to 5 SATA hard drives which I will have if I purchase the Velociraptor. Although I am reasonably knowledeable when it comes to hardware, I have never set up a RAID configuration. Therefore, it would be helpful if someone could recommend one of the various RAID configurations and brieflyexplain why it would seem to be best for my needs. I can then focus my research on understanding that one configuration.
I was planning to follow Scott's suggestion for my current 3 drives: OS and programs on C (WD 600 GBVelociRaptor), media and projects on D (WD 1TB Black Caviar), export files and Pro Tools files (all live musician tracks, no samples) on E (WD 2TB Black Caviar). However, I have been reading about the benefits of a RAID configuration so I am interested in further suggestions now that I have clarified my questions.
Thank you all for your help.
Bill -
Exporting For YouTube - Premiere Pro CS5 (Canon XL2)
I shot a promo video with my Canon XL2, and would like to upload the finished product to YouTube at the highest possible quality in order to help promote the company I work for.
Footage shot in 30p at 29.97 fps, 16:9 - NTSC.
Sequence settings are all correct and match my footage perfectly.
I have exported the video as H.264, AVI, MOV, MP4, MP2, WMV and countless other formats. When played on my computer the video quality is SUPERB. I am ecstatic at how it turned out, HOWEVER, when I upload the video -in any format- to YouTube, it looks absolutely horrible - as though it were shot with a webcam.
Does anyone have any advice as to what I might be doing wrong? Anyone had any experience with the XL-2 and Premiere Pro videos being ugly when uploaded to YouTube?
Thanks a bunch!Be very careful when using Adobe's presents for YouTube, Vimeo, etc. They have a fixed frame rate but it doesn't always match your source frame rate and this adds additional render time and can drop or add (adding is much worse) frames.
The worst offender is a preset that is for non drop-frame 30.0 fps (instead of drop frame 29.97) because every 3 seconds 3 frames get added.
Also be aware that when exporting for the web (or most anything other than to DVD), you want to use square pixels.
This might require a bit of tweaking with the presets but it is well worth the effort.
864x480 is the square pixel equivalent to 720x480 widescreen (1.21...).
For more indepth info on the presets (and my rants on the matter) - have a look at my CS5 and C5.5 articles.
http://www.eventdv.net/Articles/News/Feature/Benchmarking-Adobe-Premiere-Pro-CS5-70277.htm
(under the heading "Don't trust the presets")
http://www.eventdv.net/Articles/ReadArticle.aspx?ArticleID=74852
(under the heading "Working with watch folders in Adobe Media Encoder CS5.5") -
Mac Premiere Pro CS5 update only for DVD installations?
Received notice that there is a patch or update for the newly released CS5 Premiere Pro for Mac. This does not appear within the app's check update menu option. Further, when the patch is located on Adobe's website, it indicates that it is for the DVD installation of PPro CS5 only. The version I work with was a download purchase, and no, it does not work with the available patch. The question is - anyone (Adobe?) know how the update is to be applied to download CS5 purchases, and why the difference anyway?
Not exactly. The patch applies to both DVD and downloaded installations. If you are getting the patch via Adobe.com, pick the one for electronic installations - it's there. We had a change to our installers this cycle and will require separate patches for DVD vs. downloaded installations for the time being.
If you are running Premiere Pro CS5 that was downloaded from the site, it does not include the patched code. We never make changes to the electronic versions of the code on Adobe.com - no matter when you download CS5, it's the same as the application that's on the DVD.
If you are updating via AUM, it will know which patch to install.
Sheri -
Are these good laptops for Premiere Pro Cs5?
Okay so I will be going off to college soon (September) and I will be buying my first laptop for this reason, but I will be doing full HD videos on it. I help photographers and videographers with photo retouching and video editing as well as making music videos and I need a laptop that will handle Premiere Pro Cs5 (acutally the whole production premium suite). I can't buy a desktop yet because my first semester is abroad and I can't travel with much weight. These are the ones I have been looking at:
Asus G73JH-RBBX05
http://www.bestbuy.com/site/Asus+-+Laptop+/+Intel%26%23174;+Core%26%23153;+i7+Processor+/+ 17.3"+Display+/+6GB+Memory+/+500GB+Hard+Drive+-+Black/9741729.p?skuId=9741729&ci_src=14110 944&ci_sku=9741729&ref=06&loc=01&id=1218165344675
ASUS N61JQ-X1
http://www.newegg.com/Product/Product.aspx?Item=N82E16834220696&nm_mc=OTC-Froogle&cm_mmc=O TC-Froogle-_-Notebooks-_-ASUS-_-34220696
Asus G51JX-X2
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=5592727&SRCCODE =GOOGLEBASE&cm_mmc_o=VRqCjC7BBTkwCjCECjCE
Dell Studio 17
http://configure.us.dell.com/dellstore/config.aspx?oc=dndotw5&cs=19&dgvcode=ss&c=US&l=EN&d gc=SS&cid=27399&lid=627062
I'm open to sugestions but I won't buy anything from HP, Sony, or Toshiba because I have had problems with their products.
Also would an intel core i5 handle Premiere and After Effects?
I usually make 3 to 4 videos and 100 images every 10 days but I can reduce the production to 2 and 70 if I have to.
Thank you in advance.I recently purchased the Dell Studio
16 XPS with SSD and an i7 processor to do
nothing but Photoshop, Lightroom, and PP CS5
processing for approx 2 TBs of past & present video
footage (including AVCHD) and full HD 24P and 30P
footage from my DSLR; I run WIN 7 with 64 bit in 8 GB ram; all
my cache's are on the SSD and I have gigabit network
that serves up my source files at approx 40-70 MBytes/sec
(depending on the file or files); I use the QNAP TS259 Pro as
my NAS; the Dell has the ATI hi-performance graphics card
that only partially takes advantage of the Mercury Playback
Engine(no hardware acceleration with the ATI); I'm extremely
happy with the technologies; I can do the majority of my video
editing W/O pre-rendering altho at times for precision stuff I do
pre-render; having the historical perspective of using PS & PP since
1997 on Windows platforms I can assuredly tell you that the
performance and productivity uplifts from the marriage of these
software & hardware technologies is nothing short of miraculous;
I couldn't be happier; don't skimp on your laptop: 1)i7 2)8GB or more
DDR3 RAM 3) fast disks or SSD 4)HD capable monitor and 5) graphics
card that preferably takes full advantage of the Mercury Engine; you'll need
to shell out about $2500 for all of this (excluding the 30" monitor that I use with mine)
Hope this helps.... -
Where can I find Plugins / Transitions for Premiere Pro CS5 (not Cs 5.5 or 6) ?
Hello,
I am searching and searching for transition packs for Premiere Pro CS5, there are lots for 5.5 or 6 but none for 5. At least I could't find them.
Any ideas anyone?
Thanks in advance
Alexhttps://www.adobe.com/products/premiere/extend.displayTab4.html
Chances are most plug-ins working for the later versions will also work for CS5, but you can check with each company if you're not sure. -
Creative Wedding Transitions & Effects for Adobe Premiere Pro CS5 or CS5.5
Hi!
I am Professional Wedding Video Editor. before that i was using Pinnacle Studio 14 and Canopus Edius Pro but these Sucks, Now i have Intel Core i7 Extreme 64 bit OS and using Windows 7. I just Buye the Adobe Creative Suite 5. and soon i will Upgrade to Adobe CS5.5 . this is the Great Video Editing Software i Ever Seen. But i found some standard Dissolve & wipe Transitions in it.
My Question is that can i Use 3rd Party Creative Video Effects & Transitions with Adobe Premiere Pro CS5?
i want to know about thier names. that has Great transitions and smooth Transitions ever.
Thanks
Looking forward for Great Response.
Regards,
WaseemOnce, one could use the Hollywood FX Transitions (available from Pinnacle), but I believe that as of about CS4, that is no longer possible, but since Zac did not mention it (also, I think that Pinnacle no longer works with Hollywood FX, and they might be history?), I assume that CS5/CS5.5 does not support them either.
Pixelan (mentioned above) is a great resource for Transitons, and I recommed them highly.
I also have ProDAD's Adorage, but do not use those that often.
My normal Transitions are just Butt-cut, Cross-Dissolve and Dip-to-Black.
Good luck,
Hunt
Maybe you are looking for
-
I am using final FCP 5.1.2 and OS 10.4.8 with the black magic deck link sp to acess beta SP. My problem is that when I try to capture DV via a fire wire it does not recognize the source. It does however control the device but no vidoe or audio comes
-
Aperture does not recognize that there are images to be imported on an SD card. My workaround is to copy the images from the SD card to a folder and then import the images from the folder. Aperture also imports incredibly slowly after the update to 3
-
Reconcile - ALTER DDL. Dropped (offline) and absent (online) for same table
JDeveloper 10.1.3.2.0 1) Offline database table -> refresh from my_connection 2) Could have done some changes to the offline table here, but it is not needed to run into problems 3) (The same) Offline database table -> Generate or Reconcile to my_con
-
Setting password limits on SYS, SYSTEM, DBSNMP
We are having a security audit conducted and the auditors want us to set password limits for system accounts (SYS, SYSTEM, DBSNMP). They're asking us to set PASSWORD_LIFE_TIME, PASSWORD_GRACE_TIME, PASSWORD_REUSE_MAX, PASSWORD_REUSE_TIME. I have not
-
REAR CAMERA IMAGE VERY POOR AFTER 4.4.2 KITKAT UPGRADATION
HI LENOVO DEVELOPER TEAM, IM USING S920 FROM FEB-14 AND THE CAMERA WAS WORKING VERY NICE BUT AFTER UPGRADING TO 4.4.2 KITKAT, IT IS WROST NOW. VERY DISAPOINTED TO SEE THE RESULT OF CAMERA. IT WAS SUPER FINE IN PREVIOUS VERSION. PLS. DO THE NEEDFUL TO