PneuDeCorb
Member
I have been running 4.0 for quite a while (4.0 beta tester), but I never tried running compressor, until I actually purchased an upgrade (from 3.0) for my wife.
Compressor ran for quite a while until it displayed a popup indicating it would use physical disk space for some of the compression operations. After pressing ok on this dialog the 4.0 VM locked up completely. In fact, it locked up my wife's Macbook Pro completely and had to perform a power cycle.
So, after rebooting, the VM came up, but it was running significantly slower than a 3.x VM.
I decided to try it on my copy of 4.0 that I run on my Intel iMac (4GB ram). The compressor application locked up my vm at the exact same point.
As a person that has run parallels for quite a while (since 2.0 -- beta tester for 3.0 and 4.0), I am quite dissatisfied with this release from Parallels.
Parallel's 4.0 running as an upgrade to 3.0 on my wife's macbook pro, and fresh install on my intel iMac not only locks up running compressor at the same point, it is definitely slower.
Anybody else experiencing issues running Compressor?
Pneu
Compressor ran for quite a while until it displayed a popup indicating it would use physical disk space for some of the compression operations. After pressing ok on this dialog the 4.0 VM locked up completely. In fact, it locked up my wife's Macbook Pro completely and had to perform a power cycle.
So, after rebooting, the VM came up, but it was running significantly slower than a 3.x VM.
I decided to try it on my copy of 4.0 that I run on my Intel iMac (4GB ram). The compressor application locked up my vm at the exact same point.
As a person that has run parallels for quite a while (since 2.0 -- beta tester for 3.0 and 4.0), I am quite dissatisfied with this release from Parallels.
Parallel's 4.0 running as an upgrade to 3.0 on my wife's macbook pro, and fresh install on my intel iMac not only locks up running compressor at the same point, it is definitely slower.
Anybody else experiencing issues running Compressor?
Pneu