[Fred Robinson]

Thanks. This seems to work fine.

Of course, in doing this, I’ve now come up with a new question…

Since I’m using a 5dMkii and now this cineform codec to convert its H.264 files into the new edit-friendly, lossless AVI files, should my project be set to 8-bit, 32-bit 2.222 (Video), or 32-bit 1.000 (Linear). I note that, through interpolation, the cineform codec improves the chroma from 4:2:0 to 4:2:2. I could be wrong but isn’t a feature of this that the pixel depth moves from 8-bit to 10-bit in the resulting AVI files? I’m also led to think that the 5dMkii has a range 0-255, rather than the narrower range starting at 16. Do all these factors mean I should use the 32-bit 1.000 Linear pixel depth setting for my projects?

I did three renders of the same 1 minute 29seconds sub-project. The resultant file sizes were:

8-bit = 1374187KB
32-bit Video = 1375235KB
32-bit Linear = 1380000KB

Interesting that they’re all so similar in size. What was different though was the render times. The first two were the same at about 4 minutes, but the linear one took just over double the time to do.

So – in your expert opinion, given my media types and my demand for best quality, which of the three options should I use prior to performing the renders through the cineform codec?

Thanks once again.

Fred

[Fred Robinson]

I tried loading just the third veg and it worked fine. Weird!

Anyway – I now have the neoscene thing. How do I get vegas to ‘see’ it?

Can I go into each of my 10 sub-projects and ‘render as’ to the cineform format thereby ending up with ten cineform avi files?

OR

Do I have to go into my original media, create a cineform avi for each and then go into each of my ten sub-projects and use the ‘replace media’ command to replace the original files with the new, cineform ones?

Cheers,

Fred

[Fred Robinson]

Ooops, look like it’s $129 now (cineform neoscene)! I will certainly get a copy though. Thanks again for this tip.

I’ll get back to you shortly regarding the test you want me to do.

I can guarantee that all the project settings are identical though!

Cheers,

Fred

[Fred Robinson]

Hmmm, I am having major problems trying to import veg files (as nested) into a new ‘master’ project. Even though the project settings are all identical throughout the sub-projects and the master.

I’ve tried importing the veg files one at a time. The first couple work fine, in that a SFAP0 (proxy) file gets rendered, but then the third one appears in the media pane as transparent. If I put it into the timeline as an event, it is transparent throughout. Something very odd is going on there and I’ve no idea what it is.

When I tried importing all (ten) in one go instead of one-at-a-time, the cursor went to ‘busy’ for about a minute then back to the arrow. But nothing can be done in Vegas now. Clicking anywhere has zero effect. The PC isn’t locked though as I can still open other apps if I want to. The task manager shows that the FileIOSurrogate.exe is running with about 2.5Gig of memory (of my 8gig), and it shows Vegas itself as ‘running’. Overall RAM use is about 4Gig.

So – I can think of only two solutions…

1. Try nesting only two at a time to end up with 5 projects, then again, then again, then again ’til I end up with just the one (like a pyramid with the master project at the top). But I canl;t see why this should be necessary. And even if it worked, I don;t think I’d trust it, so to speak.

or

2. Go back to rendering each of the sub-projects and make a master project from those. Now, in the context of my original post, you said to use a lossless codec for this. Which one would you suggest for my 1080/30p stuff?

Better still, maybe you have a solution to the nesting phenomena I’ve described?

Thanks again.

Fred

[Fred Robinson]

Gotchya. Thanks again.

Good point re the ‘RE’. Will have to get one or two. Silly me!

Fred

[Fred Robinson]

I had no end of problems with this too with Vegas Pro 9e. A large part of the fix was tweaking the IOSurrogate exe program (found in Vegas’s x86 folder) to allow it to behave like a 64 bit program and handle large files. You do this using a program such as CFF Explorer. Since I did this I’ve had no more crashes. Seems like Sony released the 64 bit version without making it capable of handling the larger file sizes, i.e. a main benefit of having 64 bits!! The giveaway for me was that the program lives in the x86 folder (i.e. 32 bit).

Other things I always do now when starting Vegas are:

– Open Vegas as administrator
– Hold down Alt+Shift too, and tick ‘yes’ to clear previous cache, and click ‘no’.

These two steps have got rid of the problems I was having with ‘media file missing’ etc.

Good luck.

Fred

[Fred Robinson]

Thanks John, very helpful response.

So – when I get to the point of making the final Blu-Ray on DVD Architect Pro 5, there is no 30p, or even 29.97p option. So – what is the best approach once I move into that package? So far I’ve used the 1080i / 60fps option and it seems to lose a bit of colour quality – plus any fast pans (there are only a couple) get messy. Maybe this latter issue is resolved by your ‘disable resampling’ tip. Although I think you were still talking about Vegas when you said that.

Happy to keep trialing and erroring! But blu-rays ain’t that cheap to keep binning! 🙂

If I can learn from someone elses mistakes I’ll be very grateful.

Thanks again John.

Fred

[Fred Robinson]

I have Vegas Pro 9e and all the media and other project files on a 64GB SSD (eSATA-connected), and I have Windows 7 on the internal standard 5400rpm HD. This means I can use my laptop for editing very well indeed. I’m really looking forward to these drives getting larger and cheaper. Incidentally, I’m editing a 20 minute short filmed on 5DMkii, 30fps 1080p, and this set-up is great now. However; BEFORE I added the SSD – it was unusable. Since the laptop has a i7 CPU, 8gig of RAM etc etc, it simply had to be the 5400rpm HDD causing all the bottle-necks. And it was of course.

Fred