SonicEPM
It is the full version not Beta.
The File is 234 MB.
The File is 1hr 24min long.
I can burn a regular Mpeg with both streams together.
I even rendered to wave64 and it did the same thing. It Looks like
it has to do something with when I'm trying to burn seperate audio and video streams.
I'm trying to use it in a single movie project template.
All I have to do is wave the mouse pointer over the file and DVDA imediatly stops responding.
I'm running XP Pro duel AMD ASUS MoBo
512 Meg RAM
Terratec sound card
SCSI drives so it shouldn,t be a resourse problem.
I did another test burn over the weekend. Rendered audio as pcm with the same
vedio file I was using earlier and it works fine. Hope this helps shed some light
on the subject.

Any help is appreciated. Barry

I have not been able to reproduce this after many attempts.

what app generated the MPEG file?
is the ac-3 5.1 or stereo?

I rendered in VV4 with NTSC DVD for DVDA Template for the video.
The AC3 audio was also rendered in VV4.
I can import the video just fine, but when I try to import the audio the drop down
file manager opens for me to select the audio file, If I just wave the mouse pointer
over the AC3 file DVDA stops responding and I have to use task manager to close it.
Thanks Barry
OH I forgot, the AC3 file is a 5.1

I tried to duplicate this as closely as possible, works on my machine just fine.

Can you make a smaller pair of MPEG and AC-3 test file and try those?

SonicEPM
I will try that when I get home and post the results.
Thanks for your help! Barry

SonicEPM
I tried a new video of 2min and rendered just like the other one and it worked
just fine, rendered a AC3 stero and a AC3 5.1 file and both worked.
I am in the process of rendering about 2 min of the project that was giving me
problems, to make another test with. I think I might be on to something with the
audio track.
I renderered 2 min of the problem project and it wotkrd.
I rendered the entire project again last night and it dosen't work.
I will try to render longer and longer loop regions to see if it's a problem with the length of the project.

Thanks Barry

When you select the long .AC3 in DVDA, what is the longest you have waited.
I found I had to wait nearly 20 seconds for an .AC3 to register as being stereo or 5.1 (and that it was truly AC3) on the file-requester-dialogue when the track length was a few hundred megabytes. - Just a thought, maybe an itchy Ctrl-Alt-Del salute?

I don't even have to click on the file, all I have to do is hoover the mouse pointer
over the file name and the program locks up and task manager say's its not responding
and I have to end task in task manager.
Thanks Barry

OK, you're quite right - I forgot that the hover initiates the check (I'm new to V4 and only a casual user of VV3 (more than a year)).

Just wondered if you've ever decided to just wait, go have a cup of tea whilst waiting for it to determine etc? I don't wish to patronise or belittle your predicament Barry.

I think AC3 is tested that bit longer than some of the other multimedia types. Interesting that nobody else has remarked on the same trouble in these important launch days. Is the file really big and your file system NTFS? Perhaps more details of your specific machine and the file are required by SoFo?

RBartlett
Thanks for your suggestion, when I get home I will try waiting for a couple of minutes and see if it makes a difference. Shouldn't task manager say (running) if DVDA is working instead of (not responding) if its trying to read the file.
Thanks for Suggestion
Barry

"not responding" - I know that doesn't mean broken. If it was - I'm sure M$ would kill the task automatically. I see "not responding" on many windows apps when they are busy and I am trying to work with them. Same goes for windowed applications that don't update the screen and seem to be able to snapshot any other windowed applications that happen to move over their viewport, in a strobe fashion. Very much part of the signature of Windows.

Multimedia apps are certainly where you are going to get a few "busy" lights!

Let us know how you get on? I do hope I've got something useful for you.

I agree - "Not Responding" does not necessarily mean the program is "dead" - it is just too busy to respond to Window's status queries.

Thanks guy's I learn somthing new every day. I will try waiting longer tonight
and see what happens. I hope thats all the problem is.
Thanks again
Barry