Al Bergstein
Forum Replies Created
-
Charles, I too use Pr in a similar configuration on W7 (and also run on a Mac Pro at times), I shoot on a 7D and have not had any problems with crashing under the 7D footage. I just edited a 12 minute video that was over 2 hours of raw footage. I suspect something with the hardware not the footage, though you could try transcoding as mentioned above and see if things change.
When you say you are ‘crashing’ does that mean that you are having a Blue Screen of death or is Pr simply crashing on you and you can restart the project? As you might know, BSOD’s are usually hardware related these days. Occasionally they are graphics card software. I’ve found problems with latest versions of nVidea drivers. I didn’t see if you were running dual monitors on that one card, but if you are, fall back to one monitor and see if it helps. I’ve come to the conclusion, through trial and error, that dual monitors on one lower end card, leads to more problems than it’s worth (that was through troubleshooting Sony Vegas installations, not Pr). I recommend to friends that they get two cards for two monitors, if they aren’t running high end cards.
The only crash I’ve experienced on W7 under Pr in the last few months, was when I was using a couple of video players open at once, (viewing clips outside of Pr while working on other stuff inside Pr), something didn’t work together well. Have had more problems on my Mac Pro (G).
I too would recommend that you look at your antivirus software. After troubleshooting numerous problems for friends and seeing Norton cause them, I’ve gone over to Microsoft’s antivirus Security Essentials. It seems to do the job with the least amount of grief. Check out what services are running to see if something odd is in the background processes.
I also assume you have your footage on one of the external drives and your program on your SSD along with your OS. Make sure that you don’t have some kind of hard drive ‘sleep’ program (common on newer ‘green’ drives), as I think that drives coming out of sleep may be causing some problems for video editing.
No need to go the Mac, though I’m a fan of it as well at times, but Pr seems to be the most rock solid package I’ve used on Windows. Wonderful to see all the cores cooking away when rendering, etc. And there are plenty of issues with the Mac too, as other posts on these forums show…
Al
-
True enough Bob. Some packages run just fine in a VM, *it’s all about whether the devs coded it properly*. Always hard to tell. Adobe has usually had a better team than most. Glad to hear that Elements ran well.
Al
-
From an earlier post on the Internet using a Google Search for audio drivers win7 xpmode
XP Mode, as every Virtual PC virtual machine, can not access or use the hardware components of your host computer (except disks and drives). Instead virtual machines use their own emulated hardware. There simply is no way to change this, to install other sound or video controllers to XP Mode.
The emulated sound card in all vm’s running in Virtual PC is a Soundblaster 16 compatible WDM card, and GPU is S3 Trio.
I assume that information is correct.
I also assume from your comment that the sound card was working, you upped the RAM allocation, and it stopped working, and the driver is no longer present (?). If that is correct, I would reinstall the sound driver in XPmode. If that fails, you may have to reinstall the XPmode to get it back.
I was aware that XPmode was a VM, but could not tell if you were running multiple VMs on the machine.
An aside not related directly related to your problem:
No VM is as good as using a true OS, whether it’s Apple or MSFT. The nature of creating virtuals require emulation of hardware. There is no way to test to all situations, and manufacturers like Adobe rarely ever support VM implementations because of that.One future suggestion is that I always set a restore point on Windows before making any configuration change or software install. If something goes haywire, restore points allow a quick reversal.
Best of luck.
Al
-
Glad to hear it.
Al
-
Which version of the MBP are you running? What year model? ie. I have 8GBs of RAM on my latest model MBP 2.7 i7 but it does not have the high end graphics card in it. Seems to be speedy enough, given the usual caveats. I don’t use it for production use though. I am not using Mplayerx though. The low end MBP (like I have) is not a good choice, even with 8GBs of RAM, for editing HD footage on a regular basis. Not a good enough graphics card, nor internal drive. I bought mine knowing I would use a desktop for editing.
You don’t mention if you are on 5.5 or not. There may be upgrades needed to fix the problem, if it is Pr causing your slowness. You also don’t mention if you have your work on an external drive. The internal drive on my machine is only 5400 RPMs which is not the kind of speed you want to edit HD.
Fully loaded into RAM on my Mac, Pr only takes 346MB of RAM before loading a lot of footage in (I have loaded just a bit of AVCHD footage to trial it).
The OS is using, in total 7.6 GBs of RAM, but that’s normal. That’s actually including other programs I’m running with some free memory available. It’s not being hogged by Pr. Pr will use it as it needs it, I assume.
Make sure you don’t have a lot of background or other programs running, like the browser. Safari and Flash together take more RAM that Pr.
Al
-
You say you are getting the “spinning icon” so I assume you are on a Mac. Also you say all the ‘assets’ are on the box. On different drives or all on the same one?
Has this been happening since you first started using Pr or is it a new problem? i.e. did Pr work fine before recently?
How fast is the drive on your Mac?
How much RAM does your video card have?
PS. You might want to fill out your profile with your system. Saves us asking the same questions about system configuration, or making mistaken assumptions.
Al
-
On the XP Compatability mode front. Help us by clarifying something. You say you have W7. Under it you installed XP Mode. You also installed a virtual machine. I assume that was parallel to the XP compatibility mode? So you have three OS’s installed on your machine? (W7, XP Compatability Mode with XP installed, and a VM with XP on it. Correct?) Is the sound driver working correctly on *any* of those setups? Was the sound driver working correctly when you installed Premiere and the installation process knocked it out?
The answer might be easier to come to if we understand that. i.e. is all three machines sound driver not working? Or just the XP version? And under which version of XP? Sound drivers are the easiest thing to go wrong, it’s been my experience. We’ll do our best given the limited ability to actually “see” the machine.
Thx.
Al
-
Trevor, I just bought a Marshall 5″ and for a DSLR it is a nice fit. I traded in a 9″ monitor for it. I like the design of the Marshall, but SmallHD is also selling some nice monitors these days, and have about the same feature set as the marshals. Just be sure to get the third party battery add ons, as having rechargeable larger batteries is a must on these. Standard Sony, Canon, Panny or A.B. batteries that work with your workflow are great.
Al
-
Dave, is your computer stand alone or on some kind of network in your company? The reason I ask is that I am also running W7, and did not get this kind of conversion ever on my system, in fact it’s been more stable than my Mac Pro has been running CS5.5. One possiblity is that this message means you have a network setup that uses Active Directory (for log ins to a corporate network). I say that because when it’s telling you to adjust group policies, that’s usually setup by a corporate IT person, that may have properly set it up for your network but you need it overridden to run Premiere. Did someone set this machine up for you?
It may also be that the crash is related to the compatibility setting. Some of the issues that could cause this are that whoever setup the machine may have done it in a way incompatible with CS5.5. For example, if you are not running as a privileged user (like admin privs) CS 5.5 might not let you run as a non privileged user. Someone might have set you up purposely that way, and Windows, recognizing that you weren’t setup right, upgraded your privileged. That would likely be a good thing for trying to get the software to run right. On my machine, I am a member of the Administrators group. Does anyone know whether CS 5.5 needs to be run as a member of that group?
A way around that issue is to try starting Premiere, by right clicking on the icon, (not the one in the bottom tray, but the one under the Adobe folder in the Start menus) and choose “Run as Administrator”. That would temporarily bypass a user setting, and give the right priviledges to the program. Again,I have not needed that on a similarly configured machine.
The web site that discusses these settings and the error message you got, is here. Since Premiere 5.5 is not *an older program* there seems to be something odd about your configuration.
https://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows
Al
-
I agree with Jeff’s suggestion. You might also want to compare and contrast the media management aspects of the two. While similar, I think Adobe has a ways to go before they catch up with FCP 7.0 and in some ways is better, if you like using OnLocation, which doesn’t work for my needs.
Al