Alright so, now for my setup. Windows XP SP2. Plenty of memory/virtual memory. 1.6GHz p4. 300GB HD with 100GB free. Great quality audio/video. Enough said about that :p
And my videos: two very standard avi video captures from a DV at 740x480 NTSC 29.98 fps, each about one hour and 30 minutes long. Each file about 20GB. Each file contains audio and video.
Here are the exact stats of my video files...

Each file is recorded with the same settings as shown above.
Each file is a recording of a church service, recorded simultainiously from different angles in the auditorium.
The idea: to take these two videos and combine them into one video with the camera view switching between each view about every 30 seconds, to make it look more professional. Obviously the two videos would need to be in perfect sync from beginning to end.
Now, can some smart person tell me what is wrong with this picture...

Don't hurt yourself trying to figure that picture out! Yes, all three of those points are considered by the program to be the same spot in the time line. So then, if all three points are the same spot in the time line... what's up with the 30 second gap stuck in there? Very good question. I think the answer is probably going to be the same... "dude, read the sticky, follow the recommended procedure. Remember that YOU are responsible for fixing the bugs in VS9."
Heh. Anyway... I'm about ready to go look for some other video editing program and see if I can get my money back on VS9. The sticky isn't helping me. I'm not editing mpeg2 files, which are what all the stickies are for.
So if I'm not editing mpeg2 files, then you might ask how I managed to get such a huge out of sync issue. Well, I did split my video into many individual parts, each part being about 30 seconds long... and split the audio obviously, as you can see in my screen shot. But though I split my video so many times, that doesn't explain the absurdity of that screen shot. Yes, the program says the end of that video is as long as the audio, yet you can plainly see in the time line view that they are not. And when you play it, you can hear the difference. They start in sync but by the end of the video they are way off like that.
So I got really smart and I decided to "time stretch" my audio to make it as long as the video is showing to be. Well, when I time stretch my audio it does it, but then when I try to preview OR render the project to anything it crashes. It doesn't crash when I don't time stretch the audio. So without the ability to time stretch the audio, I really can't see any way to sync it up. Which is why I say I guess I need to go buy some other program that isn't so buggy :p
If it's any consolation, I do think that Ulead Videostudio9 is better than Pennicle studio 9 when it comes to video editing... mainly because I'm not willing to pay extra to unlock Pennicle's video effects... and Pennicle doesn't seem to have an video overlay layer like Ulead. Pennicle does capture better, at least on my computer, because I have the pennicle PCI capture card. So I capture in Pennicle and edit in Ulead. But Ulead is so riddled with bugs I can't even begin to name them all. For example, I *always, without exception* have to convert my rip my audio out of my avi files prior to rendering in Ulead. Why? Well because if the audio is part of the avi video then Ulead will always drop the last 1/3rd of my audio, giving me silence at the last 1/3rd(ish) of my movie. But if I convert my avi movie's audio in wav, and then mute the sound in my video and use the wav as like a music layer on top of the movie... then it renders fine. I invented that bug fix, har har. But it's a pain nonetheless, and Pennicle studio does not cut out the last 1/3rd of the audio when rendering. Likewise, in Ulead, if I was to take one of my movies with the same settings I just mentioned, and try to encode it in mono instead of stereo... it alters the speed of the audio, slowing it down by I guess 50%... so that the women sound like men, and the men sound like cows mooing in slow motion.
Bugs! Arrrge! VS9 should be in beta stage and not in final release in my opinion :p You can't blaim all of this on hardward or codec software... this is just plain ol' bugs in the Ulead program itself.
Aaron

