Bret Williams
Forum Replies Created
-
If you scale it, obviously only scale it horizontally or you’ll create field mush. I vote for ignore it. The pixels should be well under the overscan of a TV. You could also add black to the menus sides so they match.
-
It’s the sleep mode probably. Since upgrading to tiger I was having the same issues witih my old dual G4. I rebuilt the system twice before I realized it was mostly crashing or freezing or just acting plain wacky after waking up. I disabled sleep all together (except screen saver) and it hasn’t acted the slightest bit wacky in months.
Maybe just a driver problem, but it works.
-
Probably announced at WWDC in August is the latest best guess.
-
I just tested your workflow and it worked just fine on my machine. I opened a project, did a save as, deleted a clip, saved, then quit fcp and opened the saved as project. Clip was deleted.
You’re doing something weird or your machine isn’t operating correctly. Are you SURE you’re overwriting the same project you are later opening? Perhaps you have 2 copies on different drives or something? Perhaps you’re overwriting a copy in “FCP projects” and then later trying to open a copy from the desktop?
I think you just need another set of eyes over your shoulder, because the workflow you described should be fine.
-
I do that. But I also make project backups. Duplicate timelines is pretty useless for project corruption problems.
-
A little math answers the question…
1920/1080 = 1.77 (not 1.33)
16/9= 1.77
So the pixels are square. Set interpretation to square in AE and you’ll be dead on.
-
This is kinda scan line 101, but I don’t doubt the power G holds.
-
You’re obviously confusing projects. For example if you do a save as project1, project2, project3, and then continue to work, just which project are you now making the new changes in? Perhaps you’re making changes to project 2 instead of project 3, etc. It’s easy to confuse things if you have more than one project open.
I highly discourage the save as practice anyway. It is not the way FCP was designed to work. It complicates the media folder structure exponetially. Every time you render or digitize in the new project name, FCP creates a new media folder for the new project. If you want to use save as for backup purposes, I’d suggest doing a save as project-backup1, project-backup2, etc. But continue to always work withe the file called “project.” Since doing a save as will open the save as project name, that can be a problem if you forget to save as, close the project, open the old project.
Autosaves fix this problem, but some of us like a little more control. I personally simply go to the finder and right click on my project and choose ‘duplicate” every so often. It numbers it and everything for me and it’s quicker and simpler than save as.
When you open a backup, wheter it be your own or an autosave, you need to first change the name of the backup to your current project name so that the media folders all stay nice and neat. It will also keep autosave from making an autosave of an autosave, which is just ugly.
-
strobe filter
-
The G5 would only be faster in the older, non-universal apps. If the apps aren’t universal (written for the pentium) then they’re using Rosetta – an emulation to run on the pentium. Slowing them down to roughly 25% speed (of the pentium) which is still slower than the native G5 speed of course.
I’ve yet to see specs say anything but speed on universal apps. Never seen one score slower! Especially since a duo is the equivalent of 2 g5s or faster.