[Stu Smythe]

youtube HD is 2.5Mb bit rate.

But it will ALWAYS re-encode whatever you toss up to it. So there is little point in uploading anything at higher than around double that bitrate (on the grounds that that will provide it adequate quality for the re-encode).

I stick with around 5Mb, and multipass. 1080p if you have it.

So for an 11 minute movie, you should be aiming for around 400MBytes upload size.

stu

[Stu Smythe]

yes, as I say searching works. what does not work is saving your search as a smart folder. that gets you the weird error.

[Stu Smythe]

hmm. It’s not really an FCP7 thing – its a meta-data thing.

I’d give a better comparison with Aperture.

Here I have similar structures, metadata, tags, etc.

In aperture I may very well have done certain shoots for certain client projects, however I am building a database of material as I go.

When I later work with a new client project, I have an easy way of looking through all my ‘night skyline’ footage and selecting some across my whole catalog of shots.

That is the beauty of meta-data. It can be organised in 100s of different ways all ‘at once’ rather than via a fixed folder style structure.

And the idea of having to move events in and out of the folder is really naff and clunky. The whole idea is to abstract the media out of the file system so the user does not need to know about it (hence autosave, Lion’s hiding of the file system, etc). Facts like sneeking behind the scenes and changing your footage breaks the links to the media in the event bare this out.

What FCPX does is give you this, but ONLY to the level of an event, and above that you still have a fixed folder type structure (events only).

I am positive this is just a bug. When I try to create the smart folder I get ‘The operation could not be completed. No information is available about the problem’ dialog.

Which sounds like a bug to me.

[Stu Smythe]

You mean instead of importing AVCHD/H264 m2t files into vegas, covert to cineform HD first, then import ?

OK, I’ll give that a try, but it isn’t a very convienient solution if it does work.

If you mean on the render out, the format specified there should have no affect on the project preview video window. And I’ve rendered out to huffuv, cineform, wmv9, mjpeg and all work fine.

I compared the frames in detail last night:

-on one monitor the rendered video (H264 720p60 in this case, but cineform, etc all behave the same way) in virtualdub.

-on the other monitor the vegas preview window.

I could then frame advance in both applications to compare the frames: this confirms my first post:

-the rendered output video is fine, each frame showing as a clearly defined frame (vegas has correctly created by bobbing up a single field)

-the vegas preview window just shows each ‘tween’ frame as a duplicate of the previous one.

Note: if I import the rendered output (the 60 FRAMES per second) video into vegas it previews each frame fine. So I agree that vegas does not have a problem handling 60fps video.

The point I’m making is that the preview window does not correctly split the fields into seperate frames like an output render does while ‘converting’ 60 FIELDS per second video to 60 FRAMES per second video on the timeline.

stu