Sony generated MPG2, no audio, crashes DVD Arch4.5

Easy-E wrote on 5/21/2009, 11:00 PM
I have a Sony HDR-SR7 camera.

I used the motion picture borwser app that comes with it to convert my HD movies to MPEG2.

You would think that it being made by the same company, this file would work just fine in DVD Architect. Nope. No audio comes in.

So next step, I export just the audio as a separate audio file with the same name as the corresponding video clip from Vegas Studio 8.

Now it's crashing constantly... I get the following error message when I try to save:

(INTERESTING TO NOTE THAT THIS DOES NOT HAPPEN WHEN I USE THE TRIAL DOWNLOAD OF DVD ARCH STUDIO PRO 5.0!!!!)

Sony DVD Architect Studio
Version 4.5d (Build 107)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x63CF97
In Module 'dvdarchst45.exe' at Address 0x400000 + 0x23CF97
Thread: Main - Run ID=0x1078 Stack=0x12D000-0x130000
Registers:
EAX=00000000 CS=001b EIP=0063cf97 EFLGS=00210246
EBX=00000000 SS=0023 ESP=0012d79c EBP=051ad7b4
ECX=00000007 DS=0023 ESI=08aa7938 FS=003b
EDX=000002c2 ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
0063CF97: F3 A5 5F B8 01 00 00 00 .._.....
0063CF9F: 5E C2 08 00 CC CC CC CC ^.......
Stack Dump:
0012D79C: 051AD7BC 04DD0000 + 3DD7BC
0012D7A0: 08AD89D4 08880000 + 2589D4
0012D7A4: 0046CE52 00400000 + 6CE52 (dvdarchst45.exe)
0012D7A8: 08AA7930 08880000 + 227930
0012D7AC: 0012D7BC 00030000 + FD7BC
0012D7B0: 051AD7BC 04DD0000 + 3DD7BC
0012D7B4: 00000273
0012D7B8: 0047BDC1 00400000 + 7BDC1 (dvdarchst45.exe)
0012D7BC: 00000000
0012D7C0: 00000000
0012D7C4: 0012F0F4 00030000 + FF0F4
0012D7C8: 0063F2A6 00400000 + 23F2A6 (dvdarchst45.exe)
0012D7CC: 00000273
0012D7D0: 0012D7E8 00030000 + FD7E8
0012D7D4: 00000000
0012D7D8: 0012F0F4 00030000 + FF0F4
> 0012D7EC: 7C839AD8 7C800000 + 39AD8 (kernel32.dll)
> 0012D7F0: 7C810040 7C800000 + 10040 (kernel32.dll)
> 0012D81C: 006375FA 00400000 + 2375FA (dvdarchst45.exe)
0012D820: 08C2BFC8 08880000 + 3ABFC8
0012D824: 0012D874 00030000 + FD874
0012D828: 00000018
0012D82C: 00000000
> 0012D838: 00637355 00400000 + 237355 (dvdarchst45.exe)
0012D83C: 00000000
0012D840: 00000000
0012D844: 0003F090 00030000 + F090
> 0012D848: 006386BF 00400000 + 2386BF (dvdarchst45.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0072CB07 00400000 + 32CB07 (dvdarchst45.exe)
0012FFFC: 00000000

So what gives? Why should I have ANY issues with files generated with other Sony products???

Comments

Steve Grisetti wrote on 5/22/2009, 5:22 AM
Well, I'm not sure brand names are nearly as important as codecs and formats in this case, Easy.

The MPEG2s that your exporting from the Motion Picture Browser: Are they hi-def MPEGs or standard MPEGs? What audio codec are they using? Is your original audio stereo or 5.1 Dolby?

What happens if you just take the video from the camcorder, load it into Vegas and export a standard MPEG (not a hi-def one) from there? (Unless your ultimate goal is to create a BluRay disc, there's no point in keeping everything in hi-def throughout the workflow.)

Also, Vegas should output your MPEG with an audio codec that should be perfectly compatible with DVD Architect.
Easy-E wrote on 5/22/2009, 8:30 PM
They are SD MPEGS as I have no intention to master a blu ray disc for now. As far as the codec goes, I have no idea specifically the one they use, but it is MPEG2. The camera export doesn't offer you anything above hi-quality and low quality for the settings. It imports OK to Vegas, and yes, it's 5.1 surround.

If I change the project settings to 2 channels, it works OK when exporting from Vegas. Sure, I can run each clip through Vegas, compressing 5 channels to 1 to get DVD Arch to recognize the sound. That doesn't make any sense to me though.

The crashing issue is something entirely different. Loading the same project into Pro 5.0, running through the same steps actually works, where in 4.5 it fails.

I don't think it is too much to ask that a manufacturer keep consistency with it's products. After all, what's the point in going with Sony's camera, and it's software if it lacks the most basic compatibility between them? Therein, lies my frustration.
Steve Grisetti wrote on 5/23/2009, 8:05 AM
Again, brand names aren't the issue here. It's like complaining that some Volkswagens use gasoline and some use diesel. It has to do with the engine you have installed.

If working through Vegas resolves the issue, I'm not sure the value in doing an unnecessary conversion through Motion Picture Browser. It's an extra step, and it seems to be causing your problems.
Easy-E wrote on 5/23/2009, 12:27 PM

Running it through Vegas does not solve the problem.

The problem is 2 parts: 1) it won't recognize an MPEG2 and it's audio file, which CAN be solved running it through Vegas, exporting a 2 channel .ac3 file, I already figured out that much (it's a royal pain in the ass when you have a lot of clips to manage) 2) More importantly, it's crashing when I try to add them. In this case to one of my sub menus.

Again, this same setup works with 5.0 pro. I am simply adding another clip to a sub menu, and every time I do it, and then try to save, it crashes with the previously posted error report.

I am annoyed when software is implemented like this. Across product lines, it's not hard to try to make sure that your codecs work with all of your products. Your analogy is a little off the mark. I am not trying to burn an obscure animation file to a DVD with the expectation that it'll work, I am trying to load an MPEG2, plain and simple.

I do 3d visual FX for film and TV, and I've been doing it for 15 years, graphics overall for 20. That being said, I am well aware of software issues and sometimes you have to work around things. It would be understandable if it were some kind of esoteric application using formats not widely available. My point is that I am using a consumer level camera, with consumer software, using a file format that is widely available, and they all come from the same company.

On that point, your analogy is a bit off the mark. If Apple's Quicktime files couldn't be properly loaded into their Final Cut Pro app without processing it in a 3rd program first. That is exactly what is occurring here.
musicvid10 wrote on 5/23/2009, 1:33 PM
This is a peer forum.
Steve is not paid to be here, nor are any of us. He is only trying to help.
There is a contact for Sony Technical Support at the top of this page.
You may want to take it a bit "Easy" on your fellow users.
Steve Grisetti wrote on 5/24/2009, 6:16 AM
Thank you, musicvid. That is probably the best solution here.
Easy-E wrote on 5/25/2009, 10:50 AM
Jeez... Really?

I didn't use abusive language. Make insulting statements. I simply pointed out that I am not a newbie and that the dismissive analogy wasn't even a close to describing the situation.

You're right. I should have gone to Tech Support first as I haven't gotten any closer to finding out why DVD Arch crashes.

I am however, closer to understanding that (somehow) I am wrong when I make an assumption that there should be compatibility within Sony's product line. I'll be sure to factor that into the purchases I make in the future.

Typical users forum nonsense.
musicvid10 wrote on 5/25/2009, 11:09 AM
Typical users forum nonsense.

Yes it certainly is.

If you would like to post the details about the files you are trying to import into DVDA 4.5, someone with similar experience may be able to help you. If you are interested in finding a solution here that's how it works, whether you are a professional or newbie. Otherwise, tech support may still be your best option, although they will undoubtedly ask you for the same details.

If the video files from your camcorder import program are truly dvd compliant and of the right size, with AC-3 audio, there is a very simple method that may open them with audio directly in DVDA, and prepare them for burning without having to render again. That's what you wanted, wasn't it? I don't know if this is where Steve was headed, but he was sure knocking at the right door. So let's start with the file details first and save the critique of Steve's analogy (one that I really kind of liked) for later.

File size:
File extension:
Video encoder:
Video resolution:
Video bitrate:
Video frame rate:
Video Profile:
Audio encoder:
Audio bitrate:
Audio sample rate:
Audio channels:

If you don't know or are unable to determine this information, there is a little tool called MediaInfo that you may find quite useful.

At the slight risk of sounding dismissive, good luck!