[Bill Thompson]

Its interesting that this issue only seems to happen with *some* camera output files. So some h.264/AAC mp4 files work fine and others trigger the problem? In this case, the amount of sync error varied among several files but was always there to some extent.

Are the problem files are bad or is it an issue with the decoder?

Is there a way to analyze the mp4 files that would point to the problem?

–Bill

[Bill Thompson]

Hi Wayne,

That’s pretty amazing. Its also amazing that Magix has let the problem persist through V18! I’m glad I’ve stopped upgrading, I don’t do enough video work to make it worth the money.

I followed your very clear instructions and now everything works like it should. I never would have got there on my own. I didn’t know about holding <SHIFT> while hitting Preferences to expose “internal” options. Did you figure that out yourself? Nice work!

The other thing I noticed is that the preview is much smoother, it was jumpy before, and I no longer seem to get the frequent Vegas lockups when moving the audio clip.

Thanks again so much!

–Bill

[Bill Thompson]

Ouch. That’s pretty bad IMHO. Do you know if the problem persists in Vegas 12?

Busted software combined with a company that doesn’t listen does not inspire me to keep sending them my money. This problem doesn’t keep me from editing, it just makes a potentially great feature very annoying.

Oh, well, thanks for the quick response.

–Bill

[Bill Thompson]

Well, its hard to argue with that. If I use my Avermedia card and capture using the Huffyuv codec, the resulting avi file imports into Premiere Pro just fine. The previews are sometimes a bit jerky, because of the high data rate I think, but the video renders fine.

–Bill

[Bill Thompson]

That looks functionally equivalent to my Datavideo DAC100 box. I imagine it would do the job fine. You did say you didn’t want to degrade your video with DV compression like this box or my DAC100 will do. I imagine that with your digi-beta source you might get a very slightly more crisp picture with a lossless scheme like the Avermedia/Huffyuv I mentioned before. If you don’t already have a camera or AV to DV box that can do the conversion that would be a cheaper solution as well but its fussier and eats disk space.

–Bill

[Bill Thompson]

I’ve used a cheap Avermedia DVD EZMaker PCI card to digitize analog video. If you use the Huffyuv codec you have lossless compression and a fast machine will keep up with the video stream. Be ready to use about 60g of disk space per hour of video. You need a very clean incoming analog video source or you will drop frames and perhaps lose audio sync. See http://www.avermedia.com.

I’ve also just used my Sony VX2000 camera to convert the analog video to DV. You say you don’t want to do that but my experience with this method has been good. On the best VHS tape sources I have, I don’t notice degradation due to the DV compression, I use “only” 13g of disc space per hour, and using some various cleanup filters have been able to remove enough VHS artifacts to make the copy look better than the original. I also have a Datavideo DAC100 box which does the same thing for about $200. I know you said you don’t want to do that but if you have a DV camera or converter and haven’t tried that method you might want to see if the DV compression is really an issue to you

–Bill

[Bill Thompson]

I’m seeing the same thing on the version 1.5 tryout. As hard as it is for me to believe, it looks like the artifacts come from the internal dv codec in Premiere.

I installed the Panasonic vfw dv codec and changed premiere’s export to DV AVI from Microsoft DV AVI (I think), then selected the Panasonic codec. The export is clean. I can’t get an export without the lines you describe using the default codec (no other choice) in Microsoft DV AVI format.

If I just generate black video and export it, I see the lines. If I’m using my firewire monitor, I always see the lines on it. I think Premiere always uses the same codec to render to it.

I was wondering if my AMD processor was somehow to blame, however I see you’re using a Pentium 4.

I’d be very interested in hearing from anyone else with experience with this issue.

–Bill