DidierP,

Yes, Sony Vegas 10a is decoding CineForm files as cRGB instead on sRGB (the codec supports both), Sony is aware of the problem and is working on a fix.

David Newman
CTO, CineForm

Hopefully they are also working on the Cineform Archive bug I've been waiting over a year for a fix for. Worked great in Vegas 8 but since Vegas 9 I can know longer archive my edited Cineform projects using Save As>Copy media with project>Create trimmed copies of media. Sony has acknowledged the bug, told me it's on the list they are working in order of receiving but each release seems to set it to the back burner while newer bugs get fixed. Their support for the Cineform codec has been less then stellar.

After all of the talk from Cliff and Perrone, I have installed the current version of the Avid Codecs. Something tells me that I am going to need them for a number of things coming up.

Now is my time to be dumb. Is there a primer of which of the CODEC selections are which? There are 6 formats and each has slightly different setting available.

Keith - I've moved to DSLR within the past 45 days and it has changed my views on what can be done with these cameras.

For the bulk of my work which currently goes to the web, I transcode my Canon DSLR clips to 720p 110mbps 10 bit to give me a similar type intermediate to the Cineform. I've dropped these clips on the timeline in Vegas Pro 9 (and now 10) 64bit and they play back beautifully on both machines listed in my sig.

You can select any option and as long as you don't change the framerate, you can use any setting available. I'm currently working on a tutorial for my blog on using MPEG Streamclip and DNxHD to batch encode DSLR clips accordingly. If you're working with other acquisition clips (m2t, etc) it requires a little more work to get them batch encoded unless you're using some form of batch encode scripting within Vegas.

Perrone may have some additional input and it was he who got me turned on to DNxHD after the timecode fiasco I had with Cineform - and transcoding to DNxHD is the foundation of my post production workflow in Vegas Pro

HTH,

Cliff Etzel
Solo Visual Journalist | Micro Documentary Film Maker
bluprojekt | SoloVJ Blog
--------
Desktop: OS: Win7 x64 | CPU: Q9400 | Mobo: Intel DG33TL | 8GB G.Skill Dual Channel RAM | Boot/Apps Drive: Seagate 160GB 7200RPM | Audio Drive: Seagate 160GB 7200RPM | Video Source: WD Black 2x750GB RAID 0 | Video Card: nVidia GeForce GT 220 1GB

Laptop: Dell Latitude D620 | C2D 2.0Ghz | 4GB G.Skill RAM | OS: Win7 x64 | Primary HD: WD 320GB 7200RPM | Video HD: Seagate 500GB 7200RPM

I was actually looking to find out the particulars or differences between the formats;
Avid DV
Avid DV 100
Avid Meridien Compressed
Avid Meridien Uncompressed
Avid Packed
Avid RGBPacked

Keith,

You may glance at this: http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=372319#Avid_Codecs

Thank you. That is what I was looking for. It doesn't address the AvidRGBPacked and the CODEC package I installed doesn't show the DNxHD format, but this gives me a start.

What did you install???

Open up your quicktime MOV codecs option and have a look and see if you see DNxHD.

I found where it was hiding. It was right under my nose.

so if i have a couple hours of avchd laid out in the timeline do i just render it all to one giant QT??


or do i have to render each clip one at a time?


(trying to figure out some sort of batch workflow?)

You convert the source files BEFORE opening Vegas and putting them on the timeline.

convert using what?

i use After Effects or Vegas for batch operations... there's a bunch of other apps that do batching but i haven't used 'em.

1) in AE i cook up a custom output setting then use it for all output files

2) in Vegas i use region markers to define the in/out of each clip and run a batch script called BatchRenderv7GUI (JHM)

I use Mpeg Streamclip to do my conversions. But this may or may not work for you.

@ robwood

it sound like neither method allows easy (automatic) file naming?

so the file 00065.MXF would be 00065.MOV - without having to name each file pre-transcode?

--

Along those lines, am I correct that each file HAS to remain exact name or it will not be easy to "swap out" (as if in changing a proxy to full rez).

I am just nervous that i would get done editing a long project with a codec and then something goes wrong using that codec and I cant exchange the footage (with all edits in place) for the original footage or another codec.

AE does automatic file naming based on the name of the source.


Vegas generates #1, #2, etc or u can type in specific names to the region marker (the script i use applies any name info in the region markers to the file).

when using Vegas+ script, i use copy/paste... ... takes a few seconds for each clip.
1) right-click properties of media
2) ctrl-c
3) double-click media to set region (press R)
4) right-click region marker, select re-name
5) ctrl-v


there's also a bunch of batch render apps for Vegas by Ed Troxel (Excalibur), VASST (Ultimate S Pro4), Sony (Production Assistant) and Peachpit (Veggie Toolkit 3.0)

what if I edit the project and then change my mind?

is the work flow for changing source file this:

1. move current folders/files that Vegas is referencing to new location
2. open Vegas
3. use "replace footage" dialog

?

An easier way to swap media files is to use the "Batch Replace" script found here:

http://sony.vegas.1.free.fr/

It's one of my favorite scripts.

not sure i understand the "change my mind" bit.

what i do is store all the related files in ONE folder (obviously this could suck if u have large amounts of image-sequences, etc, but assuming that isn't a concern)

then i copy the VEG file into the folder containing the media: Vegas automatically saw the files there and grabbed them... didn't even have to use replace footage command (tho i did change the name of the original folder to hide it just to make sure the VEG file didn't link to it instead).

i have to use multiple folders because i do multicam shooting.

my folders are like:

cam1
cam2
cam3
cam4


it makes me wonder even about if I could "replace" or "Batch Replace" without trouble.

I just noticed that I have alot of the same same named files:

e.g.

cam1 > 00000.MXF, 00001.MXF...
cam2 > 00000.MXF, 00001.MXF...

how would that work in a replace workflow?

You are WAY overthinking this.

Create two top level folders... one named Proxy, one named Full.

Create your folder structure underneath that... a folder for each cam, etc., whatever. Before you fire up Vegas to cut, rename the "Proxy" folder to "working".

Do the edit
Close Vegas
Rename "Working" to Proxy
Rename "Full" to "Working"
Open Vegas.

As long as the file structure is the same, and the files have the same name and folder structure as the Proxy, the changeover happens seamlessly. No scripts, no work. I've done this dozens of times. Creating DNxHD 36 proxies, and DNxHD 175 full.

Anything that is shared between the two versions is in a folder outside of the Proxy/Full so it's the same in both versions. Typically that's stuff like audio.

>I just noticed that I have alot of the same same named files:

You can use Device Explorer to import your footage and it will give each clip a unique name.

/jerry