Page 1 of 1

VS-12 crash and other issues during DVD creation

Posted: Mon Nov 17, 2008 6:14 am
by GeoffW
I have a problem with VS-12 at the DVD creation step that I have not seen discussed in other threads.

Starting with an empty project:
Share --> Create Disk --> DVD
Add media --> Add Video files --> Add a clip : any clip (including NTSC DVD MPEG2 files rendered by VS12), same symptoms regardless. Here's the properties of one example clip:
File format: NTSC DVD
File size: 58,114 KB
Duration 53.487 sec
Video type: MPEG-2 Video, Lower field first
Total frames: 1603
Attributes 24 bits, 720 x 480, 4:3
Frame rate: 29,970 frames/sec
Data rate: Variable bit rate (Max 8000 kbps)
Audio type LPCM audio
Total samples: 2,567,367 Samples
Attributes: 48000 Hz, 16 bit stereo

Click on the clip that was just added and click on "i" to show the media clip information - no data at all appears.

Click the "Recover possible lost AV data" button, results in status="Not supported" yet the clip loads/plays just fine in VS-12 and any other Video player.

Click Add/Edit chapter - the play/pause and all other buttons are greyed out. The only available chapter option is "Auto Add chapters". Attempting to perform this operation inevitably results in a VS-12 crash: AppName: vstudio.exe AppVer: 12.0.0.0 ModName: mfmediaservice.dll ModVer: 1.0.0.1 Offset: 00007172.

It is possible (if one avoids the previous step) to click "Next" to get to the SmartScene menus. The DVD menus can be manipulated as expected. Clicking on "Preview" brings up the Remote Control, but clicking "Play" results in a blue progress bar underneath the preview area for a fraction of a second followed by nothing. The Preview window continues to show "Press 'Play' button to start preview".

It is also possible to click "Next" to proceed to the DVD burning step and in fact the burn is successful and produces a working DVD.

So in summary I can create a DVD but cannot create/edit chapters and cannot preview prior to burning.

I have a 3.2 GHz Pentium 4 running Windows XP Pro with 3GB of memory and 23 GB of free space on the disk that VS is using for working directories. Graphics card is an ATI 9800 All-In-Wonder with 128 MB memory. DirectX was updated to 9.0c as part of the VS-12 install then further updated via directx_nov2008_redist.exe

I have tried uninstalling my old version, VS-8, and uninstalling / re-installing VS-12 all to no avail.

Any suggestions??

Posted: Mon Nov 17, 2008 7:36 am
by Ken Berry
Welcome to the forums!

I can't think of a reason why you can't preview since that is normally corrected with the DirectX update.

With manually adding chapters, you actually have to drag the pointer below the preview screen on the Chapter page to the right before the other choices become active. Manual insertion of chapter points is, well, manual -- so you have to drag that pointer to the spots where you want to add a chapter marker, and then manually insert it. :lol:

Also, as far as that i button not giving you any read-out, when you right click on the added video clip, does 'Media Clip Properties' give you anything?

Posted: Tue Nov 18, 2008 5:25 am
by GeoffW
In the Add/Edit Chapter window the preview screen is blank and there isn't a pointer below the preview screen to drag. Click here for a screenshot of the Add/Edit chapter window so that you can see what I mean.

Right clicking on the added video clip and selecting "Media Clip Properties" appears to do nothing - it does not bring up a window with the clip properties.

Is the "Recover Possible Lost AV Data" usually available as an option on the right-click menu? Click here to see how my right-click menu looks.

Posted: Tue Nov 18, 2008 5:59 am
by Ken Berry
This is all rather weird. Normally, other people who have had similar problems with missing bits and pieces, or even missing processes, in the burning module, have fixed them with the DirectX update. But that did nothing for you. Hopefully, someone else might have other suggestions. But at this stage, the only thing I can think of is a full uninstall/reinstall.

As for the 'Recover Possible Lost AV Data', I have to be frank and admit that I have never noticed that before... :oops: So I am not even aware what it means, or whether it is a new feature of VS12. (It is also on my version of the program, regardless of the video I insert in the burning timeline -- I just checked, with a few diverse clips.)

Posted: Thu Nov 20, 2008 4:42 am
by GeoffW
Well Ken, as you were so insistent that it sounded like a DirectX related problem, I re-ran the directx_nov2008_redist.exe and now everything is working just fine. All I can think is that maybe it's order dependent. I don't recall for sure but it may be that first time around I had updated DirectX and then done the VS-12 uninstall/re-install. Maybe it needs the DirectX update after installing VS12. Regardless, it looks like my problem is solved. Thanks for the help - without you pointing out the likelyhood of this being a DirectX related issue I don't think I would have persisted with this path. :D

Posted: Thu Nov 20, 2008 5:35 am
by Ken Berry
:lol: :lol: Glad to hear it. You had me worried there for a while that maybe the DirectX update isn't the panacea it otherwise seems to be! :lol:

Posted: Thu Nov 20, 2008 6:26 am
by HPG
Thanks!! I was baffled by exactly the same behaviour of X2, and it was driving me nuts. Running directx_nov2008_redist.exe at your suggestion fixed it, and normal life can now resume. Whew! :D

Posted: Thu Nov 20, 2008 10:33 am
by Ron P.
Out of curiosity I checked VS10+ and VS11+ right-click menu option, and found the Recover Possible lost A/V data was also included in them...:oops: Like Ken, I've never noticed it before...

link to the redistrib

Posted: Sun Nov 23, 2008 3:12 am
by buercky
http://www.microsoft.com/downloads/deta ... laylang=en


had same crash as above and this fixed mine as well

Posted: Sun Nov 23, 2008 9:21 am
by Ron P.
Really no need to repost the link, as it is in the Announcement thread.

Posted: Sun Dec 21, 2008 6:07 pm
by manicx
Just wanted to say thanks to GeoffW for reporting back how he solved the problem. I had the exact same problem and the update of DX to November release fixed it for me! :)