[Hannah Radcliff]

I got the “hack” removed straight away. It’s not there anymore. I’m gonna do a clean install of OS x this evening and try to reinstall premiere under the root user. All the reading I’ve been doing suggests a number of issues may be occurring. Some say it’s actually an audio driver issue, some say it’s disk permissions, and some say that the files were not put in the right place during the installation.

FCP seems to be ok as long as I’m not in a hurry. I’m rendering out a burlesque performance shot on my T2i right now and used some third-party effects plug ins to make it look all neat-o. It’s like a third-party Rock Horror Picture Show rendering nightmare at my house! Good time to go out and get some coffee.

[Hannah Radcliff]

Hrm……..not recently. I’ll try it and get back to you to see if that works.

[Hannah Radcliff]

I tried a number of them–web, NTSC, and DSLR (since it’s an h.264, I thought it was worth a shot). But the problem happens before I get the clip into the sequence.

I think I’m going to call this bunk and stick with FCP on my Mac at home 🙁

[Hannah Radcliff]

Yeah, hah, I whole heartedly agree with the QT aspect. I hope they’ll tie some of the issues up with the release of FCP8. I hated to see QT 7 pro go under the wayside to QT X.

This is part of why I tried PPro5 in the first place–I lost faith in the development on FCP 8. It’s very frustrating when you only have rumors to rely on. Thought I’d find an easy alternative, and now I’m back to square one.

Anyways, I’m reaching the decision that PPro5 is not going to be a solution for me, as long as FCP 7 is still doing its job. I wish I could be more ahead of the curve with a program that can work with DSLR footage natively and also has an already built in workflow for R3D files. Even Sony Vegas is surpassing FCP in some ways.

If I can justify the expense of a new video card, I may go that route. But at the moment my tower works fine for what I’m doing with FCP with a Pro Res workflow, save for longer render times. I think I’ll just stick to that at the sacrifice of mobility. Hey, it’d save a lot of headaches, and after all, the end product is more important than the process. And Excedrin is probably glad to have my business.

[Hannah Radcliff]

Sure!

Here is the clip: https://dl.dropbox.com/u/1344358/Spectrum%20Short%20Clip2.mov

I used QT7 to trip the original, well, the h.264 version of the still sub Pro Res 422 version of the original which was comprised of a mixture of DV and 550D footage. I can’t account for the quality or aesthetic of the vid, I didn’t shoot it. Just editing this one.

However, when I try to edit native 550D footage it is very irritating.

Also, FYI, here is a link to a demo of the issue: https://dl.dropbox.com/u/1344358/Problem%20demo.mov

If you watch, you’ll see me try to scrub the preview window, then the preview freezes. You won’t see it on screen b/c screenium makes its own cursor apparently, but the spinning wheel of doom pops up for the last 5 secs of the video.

In this vid I show the file info and show it playing and scrubbing fine in the QT X preview:

https://dl.dropbox.com/u/1344358/Mouse%20Demo.mov

Also as an update I read on another forum that an option is to log in as the root user and open the application there, close it, then reboot as a normal user. Didn’t work!

Thinking you’re on to something with the compression compatability, although if it can edit DSLR footage natively, it should be equipped to handle a h.264 I’d imagine….

[Hannah Radcliff]

I’ve attempted to edit footage from my Canon 550D natively, which Premiere is supposed to do well. When that didn’t work I tried a few different compressions. I resorted back to my FCP workflow and encoded to Pro Res 422, which is usually uber sweet. Didn’t work. Tried exporting to DV res for grins, still no go. The Pro Res versions work great in FCP on my Mac Pro tower but still suffer from playback issues on Premiere even on that machine.

As for hard drives, I use an external drive to transfer files to my laptop. I usually just use the laptop for small edits and for multitasking when I have multiple projects going on at once. Anyhow, the built in drive is small but not bad. It’s a 5400PRM Hitachi–only 250GB but I keep it clean. When I’m using my Mac Pro I edit from a 2TB 7200RPM Seagate Barracuda. Hard drives are probably not the issue.

[Hannah Radcliff]

BG = GB, I’m dyslexic….

[Hannah Radcliff]

Thanks! Yeah I’m hesitant to do any hacks on my machine. The only things I’ll download or try are straight from Nvidia–I’ve heard too many horror stories. I know that the graphics card I have sucks, but my point is that it shouldn’t be as bad as it is.

I had a 5BG clip with a 1hr running time. It was a 640×360 h.264, I just wanted to see if I could use Premiere to cut a montage from the video. The preview kept freezing and the program crashed after 5 minutes of spinning wheel of doom. For grins I tried it on the old G5 at work that was running FCP5.

I mean, FCP5 on a PowerPC with 2GB ram and a 128 MB graphics card cut through the footage like butter., and I was in and out in about 15 minutes.

So if that machine can handle it with no drama, seems like my laptop should be more than capable….