Yes, I have 3 pcs and a few more for other things like a firewall, proxyserver, a.s.o., which is not important here.

Celeron 800 is for capturing only
Celeron 1300 is for video-editing and rendering
and the Celeron 1000 is a Samba-fileserver for the video-files. No, I don't copy the files, I use netvolumes. A Samba-Fileserver is a Linux Server, which - simply said - makes Win think there is a Win-fileserver. In other words I would like to use VV with the 1300 and store the files on the 1000 via 100Mbit Ethernet. Note: Till now I could not save files, since I have the demo only. I am asking in advance to speed up the start, when VV arrives.

Transcode is - simple said - something like tmpgenc. For more informations see http://www.theorie.physik.uni-goettingen.de/~ostreich/transcode/ (in English)

The advantage of this combination is:
I can work with the client all the time, while the Samba-fileserver encodes a SVCD. If I capture at the same time with the 800 it works without dropped frames to write on the same harddisk of the Samba-Server via Ethernet. Even I can capture with the 800 using Linux to a file on the Sambaserver and start a few minutes later encoding the *same* capture-file with transcode.

My problem now is - as mentioned - that I need a rendered file from VV in dv(raw)-format, since *I* have problems with avi-files and transcode. Is this possible?

I'm not sure I'm going to be the one that can answer your question with absolute certainty. But, here's what I think. If I'm wrong, maybe someone who knows for sure can correct me.

First let me ask another question in case my ignorance completely cancels out everything below. In your original post, what did you mean that with AVI files you have the 4:42 problem?

After looking at Transcode's web page it seems to me that there shouldn't be a problem processing DV encoded AVI files. The Transcode flow chart shows MPEG, DV, RAW, DIVX, and MJPEG compression codecs under the AVI container. I can't tell for certain what Transcode is refering to by RAW, but if they are simply meaning the absence of any compression then Vegas does offer the ability to render to an uncompressed AVI.

If you are generaly having trouble with all AVI files then perhaps there is a problem with Transcode's codecs. From what I can see there shouldn't be a problem. In addition, as far as I know, Vegas outputs industry standard DV formating. But, there is a check box on the video tab in the options for the DV codec that says:

[]Create an OpenDML (AVI version 2.0) compatible file.

which was checked by default on my copy. I'm not sure what the file turns into if it is not checked.

I guess my suggestion is this...

Read the last paragraph on the "About" page on the Transcode web site.
http://www.theorie.physik.uni-goettingen.de/~ostreich/transcode/html/intro.html#about

Then check to make sure you have the latest version with the latest codecs.

JBJones




P.S.
After writing all of this I got to wondering if when you mentioned 4:42 in your original post if you were trying to say you were getting recompression artifacts from the 4:2:2 DV compression. If that's the case then, I guess, an uncompressed AVI is all you were wanting to know about, which Vegas will do.

Whew! That's a lot of stuff to type.

Thanks! I see I have to try the different formats and options.

I get *excellent* quality from different avi-files with transcode, but unfortunately encoding stops after 4:42 everytime. Since nobody else in the transcode-mailinglist knows this problem, there must be something wrong within my system. Maybe it is bug, which was solved in the newest version 0.6.3, while I use 0.6.2. But I am happy that 0.6.2 works as it does. It is hard job to compile transcode. So I use transcode as a compiled package from http://packman.links2linux.de/index.php4?action=150&vn=2 and there is no newer one.

I recall a similar 4:42 issue a while back. The short answer is in Options => Preferences... => General, make sure that "Strictly conform to AVI2 specification" is not checked (unchecked is the default).

For a more extensive explanation, read:

http://www.sonicfoundry.com/forums/ShowMessage.asp?ForumID=4&MessageID=97685

Hope this helps!

Oh. That's what you meant by 4:42. After 4 minutes and 42 seconds transcode stops. That's interesting. Let me think on this a little while.

By the way. Were you saying that version 0.6.3 actually fixed that problem or are you hoping it will?

JBJones

It is not checked here