Bret Williams
Forum Replies Created
-
Did you realize that on some of the Lacie drives, the big blue light is a power on/off button?
-
Ok, I just checked. My fairly el cheapo 3 year old epson perfection photo is 1200 dpi optical. Not interpolated. Nobody should be having any trouble scanning slides these days. They’re $35 on eBay.
-
Shouldn’t be. A slide is larger than 1″. Even if all you can get is 600dpi optical, that’s still just about 720 pixels wide. And if it’s interpolating a little to give you 1200 dpi, then that should easily be enough to do some basic pushes without losing any rez. Heck, even a 720×480 frame in FCP looks ok for just a slow creep in at 110-115%.
But I’m using slides right now in iphoto and printing full bleed iphoto 6×8 images that I’ve even cropped in on a little. Look great.
Epson Perfection 1260. I’m sure they have a different model now. Mine is 2 years old.
-
It only gives that notification if your in point or out point splits a transition. There’s no need to delete all transitoins to perform your edit.
If you’re deleting, then you are probably trying to execute a ripple delete, and your mark in or mark out splits a transiton. The computer has no way of replicating 3/4 of a transition, or deciding which transition needs to be deleted or adjusted or what.
Normally, you wouldn’t make the decision to split a transition on a ripple delete, insert edit or overwrite edit. So during normal editing procedure if that box comes up, it’s generally a helpful heads up. Not an annoyance.
If you’re trying to overwrite a large number of transitions, or delete a large number of transitons, you will not get this error. Only if one of your points intersects the transition.
-
My $80 epson perfection 1260 does slides and negatives at 1200. Not sure if it’s interpolated or not, but it looks damn good. Plenty of resolution for a ken burns effect.
But it’s no different than a regular scan. Just save it as a tif, pict, jpeg, whatever you want. Then drag it into a bin in final cut and animate away.
-
All good. Except it doesn’t matter what frame of the clip you’re on. It’ll bring up the clip with the ins and outs marked.
The reason you can’t adjust it in the timeline is because you’re making the clip longer or shorter. FCP doesn’t know what frames it can delete or add to keep the clip the same length but change the speed.
IMHO though, it should simply default to just clipping off extra frames or lengthening the clip and let the user deal with it after that. Rippling the timeline is pretty extreme and no application should ever do that unless the user specifies. That can really screw up a project.
-
In short, you’ve basically said that your system dislplays random flashing pixel boxes on all DV playback, but never on uncompressed playback.
You mention that it occurs even in exported DV clips. My theory is that it does not get squeezed into exported DV clips as you say, but instead those clips simply suffer from the same DV playback problems. Random playback problems simply do not randomly find their way into exported clips. It just doesn’t work that way. The fact that your uncompressed clips are fine are evidence of this.
My guess is the odd combination of catpuring DV over firewire and playing it back over AJA IO is the source of your problem. I’m not sure exactly why there should be something there. AJA natively plays back and captures uncompressed clips. Using DV material with AJA requires rendering or on the fly processing.
So for output, I’d suggest you create a standard IO sequence that is for uncompressed material, and place your DV footage into the sequence and render. It may say it can play it back in real time, but you’re obviously getting some sort of data bottleneck issue. Sounds like the system isn’t dropping frames, but is having some sort of problem processing the DV into uncompressed material on the fly.
If all your material is DV, try using just a DV sequence and outputting via a DV device like a DV deck or camera hooked up to a ntsc monitor and see if you get the same problem.
The whole thing could be as simple as updating AJA drivers or QT, or reinstalling or updating both. Sometimes rebooting the AJA IO solves lots of issues.
-
CatDV is freakin awesome. I had a producer have that on her laptop once. You have to have the more expensive version to output logs for FCP or Avid. Don’t fall for the cheaper version. So unfortunately I think you have to spend $300 or so.
But it does a great job of logging and capturing these little thumbnail movies. Perhaps it can capture full DV but I’m not sure. Anyway, it was a major bonus in the suite. While I was finessing a couple edits, music, VO etc she was looking for the next shot. But instead of looking at a log and asking me to play it, she was looking at a log and checking out a small sized movie on her laptop. So we really didn’t know if the shot would truely work until we tried it in context, but she was able to rule out 90% of the possible choices before asking me to try a shot.
-
I suppose the maximum width is determined by how many other columns you have in the bin. Delete all the other columns, then just grab the top right of the name column and drag it to the right.
Why FCP can’t print a bin is so lame. Exporting to excel isn’t great either. For one, you need excel. And it doesn’t export thumbnails.
-
He just said, the cheapest ones he can find.
You definitely have a problem. And it’s going to get worse. I’d go ahead and replace your burner. You’re obviously doing a lot of work. You may have just ragged it out. But I’m sure it’s paid for itself many times over. Time to replace it with a faster better one. Just buy a superdrive and stick it in there. It’s very easy. I’ve done it myself on a couple G4s.