Well, well, well. I see that in my absence, a-m-v.org has undergone multiple changes, hopefully for the better. That's good.
I also noticed that a new guide to WMM was posted, which attempts to address the export issues commonly found in complex AMV projects. I used it with some success at first--previously I didn't know that you had to specify a framerate in DirectShow to open a DV-AVI--but after significant testing I came across the same problem I'd always had.
Which is. At first, a DV-AVI will save my project with stunning video quality and will always save, no matter how complex my project is. Great. But upon playing the resulting DV file, the audio sounds like it's 96kbps and skips whenever there's a "complex" scene change (anything from an effect to a speed modification). So I figured, fine, I'd just open the DV-AVI in VirtualDub, mux the original MP3 in, and save as HuffYUV AVI.
Which works. Except that now, while the audio is perfect, the video progressively gets out of sync. My theory is, as it has always been, that there's something about the DV-AVI exporter which causes it to "stretch" the audio in an attempt to match the source footage. Which doesn't make a lick of sense to me.
Interestingly, not all of my videos go out of sync when exported. My rather simple G Gundam video remains the same whether I export to DV-AVI or WMV. The audio issue is still present, but muxxing in the original MP3 solves it without loss of sync.
The Evangelion vid I'm working on goes out of sync if saved as DV-AVI. The glitched audio is "in sync," but when the original MP3 is muxxed, it gets worse and worse as the video progresses.
The Elfen Lied video I have in progress also loses sync if saved as DV-AVI, same way as the Evangelion one.
The G Gundam and Evangelion videos both use 23.976 FPS source footage. The Elfen Lied video I didn't Decimate it before saving the clips, so the original clips are 29.97 FPS (except for a few scenes from the OVA, which used 120 FPS...).
I can provide example videos showing the phenomenon if need be... but hopefully someone out there has experienced this and figured out a countermeasure. Being able to do one single encode sure would save me a lot of time... :)





