Ron Moody
Forum Replies Created
-
Alright! The truth comes out!
I hate XP. I mean real, honest disgust with a fair amount of hopelessness mingled in on the side. I’ve been on the boat since DOS and using it for video since the Fast Video Machine made editing possible on underpowered PC’s.
For a while there, I had hope with Win2K which was both more powerful and more stable than the OS that preceeded it, but then XP came along and continued the trend of slower and more resource intensive OS that had been the case in every version except win2k from Dos forward.
The Mac on the other hand is based on Mach or BSD, is stable, fast, and beautiful as well. I would love to move to it completely, but have this set of software (Production Studio Pro) that cost me more than the laptop will.
If I can have the wonderful functionality of the Mac OS, along with the ability to use XP when I edit, or at least until OSX native Adobe apps are released, I’ll be a happy camper.
There, I’ve said it.
ron -
Perhaps I wasn’t clear. The review I read included performance of the mac laptop running XP as well as OSX. It ran XP quickly; in fact, one review said that the macs ran xp faster than any other laptop, even those intended for the Microsoft OS. It sure impressed me.
Sorry for the confusion.
P.S. I don’t present myself as an expert, I’m just echoing some thing’s I’ve come across that caught my interest.
ron
-
Perhaps I wasn’t as clear as I thought I was. The reviewer said it worked and it worked well. The glitches were minor and related to driver issues. For example, I think bluetooth didn’t work under XP, stuff like that, but the display and audio; all the important stuff worked just fine.
I was wondering if anyone had seen a review of how the 2gig dual core performed in contrast with my plain vanilla 3.2gig P4. It slows so much when running both Premiere and AFX: toggling back and forth. I assume each app might get a full core’s attention. Is that how it would work out in real life?
ron
-
By the way, I’ve been on the Premiere train from the beginning as well. I’m one of those that had the Matrox DC30 card (the generation before the 30+). I haven’t had the luxury of owning the latest and greatest hardware to go with each new version so perhaps the weaknesses and ineficciencies with Premiere along the way were more apparent to me.
I almost didn’t switch to PP2 since 1.5 was working (except for the green screen on stills thing), and I’d heard about some stability issues in version 2. However I did make the move and so far, am glad I did.
While it does crash more often that 1.5 did, and when it does, the damage is more severe with titles in the project rather than as independent files, it communicates much better with the rest of the Adobe family. It’s better in most ways, but I hope they dont’ stop working on it. There’s still a ways to go.
ron
-
I agree that it’s the most efficient. In my experience it has slowed down over time. For example, I never migrated from version 6 to 6.5 because it was widely argued that the real time elements introduced in 6.5 slowed down the app. I never tried it because that wasn’t a critical issue for me at the time. I did go to PP1, pp1.5, and PP2.
My reason for writing the post however was to bring up the issue of crashing while moving clips with alt>. Do you have any insight into this element?
ron -
My guess is that your drive is formatted under the FAT file system rather than under NT. If I remember correctly, the maximum file size using a File Allocation System formatted drive is 2 gig which works out to about 9 minutes or so in the DV format. Using drives formatted under the NT file system removes this limitation (or at least places the file size so high, it’s not a realistic limit anyway).
Ron Moody
-
It seems like I remember reading that Nero can do that. So you could create a master DVD and copy the master off two-at-a-time (or three, or four…).
ron -
Thanks for responding.
When I try to build the full DVD, which means that it would sequentially transcode all three avi files, it almost always crashes.
ron
-
Apparently your rendered files were deleted since you last worked on the project. Re-render the project and you should be set.
ron -
Thanks on the Imaginate idea. I already have AfterAffects and it just feels like it would be wasteful to throw the extra money at it when I have a tool that will already accomplish the same thing. I’m sure though, that Imaginate would do it much quicker though.
I did re-save every photo as a JPG and guess what… it works perfectly. Apparently Adobe products work better with file formats other than their own. Good to know! Now to get down to the job of editing.
Thanks all on your input.
It’s interesting that no-one ever responded to my previous post about other Premiere and still photo problems. Oh well, my main issue is resolved. Time to get to work.
Thanks again!
a tip for anyone reading. Want to create customized countdowns in Premiere? Create a normal countdown in Premiere, then use a luminance key to key out the grey or white (however you have it set up) background, replacing it with your own video. Throw your own audio underneath with beeps on the second and you have something that is unique to you with minimal work.