HELP!! crashes and problems with z7e card transfe

Hitime wrote on 6/22/2008, 2:50 PM
I have upgraded the memory on my pc to 2 gb and am using a z7e for the first time and need to work out the problems I am faced with VERY QUICKLY as I am starting a shoot that will last 2 months. HELP PLEASE

I have tried to edit stuff captured onto the card of a z7e and V8e exits with exception errors or locks up.

I have 3 questions.

1) v8b crashes -- well whats new? -- when can we hope to see the next release?

2)Even though the z7 was left running for 1/2 hr without a stop there are 2 files on the card. There seems to be a slight gap between the two files. Is this corruption on the card or is there a max file size that I exceeded?

3)Is there a max length of HD file that that V8b can use?

v7e does not like the files either although Eduis 4.5 seems OK with them.

I dropped Acid 6 recently for Sonar 7 -- much improved in 7 -- because acid was not handling Kontakt properly.

I have been with Vegas since v2. Stability was always its selling point ...... !!!!

thanks in advance.

Comments

Darren Powell wrote on 6/22/2008, 5:45 PM
Ground Control to Sony ...

Your software doesn't work.

I repeat ...

Your software doesn't work.

Where's 8.0c?

Ground Control to Sony?

Are you there ... over?

Has a space alien eaten your brain?

I repeat.

Your software doesn't work.

Darren Powell
Sydney Australia

Oops ... just tried to open a little 10 minute project with m2t's.

-----------------------------------------------------------------

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x258ED79C IP:0xD12F221
In Module 'mcmpgdmux.dll' at Address 0xD120000 + 0xF221
Thread: ProgMan ID=0x878 Stack=0x306F000-0x3070000
Registers:
EAX=00000000 CS=001b EIP=0d12f221 EFLGS=00010246
EBX=0000003d SS=0023 ESP=0306f130 EBP=0306f16c
ECX=78134c58 DS=0023 ESI=257f8f48 FS=003b
EDX=016a0608 ES=0023 EDI=258d4f48 GS=0000
Bytes at CS:EIP:
0D12F221: 8B 87 54 88 01 00 50 56 ..T...PV
0D12F229: E8 12 F7 FF FF 83 C4 08 ........
Stack Dump:
0306F130: 25809058 24340000 + 14C9058
0306F134: 257F8F48 24340000 + 14B8F48
0306F138: 0D12B52E 0D120000 + B52E (mcmpgdmux.dll)
0306F13C: 257F8F48 24340000 + 14B8F48
0306F140: 258D4F48 24340000 + 1594F48
0306F144: 00000000
0306F148: 25782F48 24340000 + 1442F48
0306F14C: 3BFFDD90 3A0C0000 + 1F3DD90
0306F150: 2322453A 23200000 + 2453A (mcmpegin.dll)
0306F154: 257F8F48 24340000 + 14B8F48
0306F158: 257971B8 24340000 + 14571B8
0306F15C: 00000000
0306F160: 00000000
0306F164: 7C838F36 7C800000 + 38F36 (kernel32.dll)
0306F168: 7C838F36 7C800000 + 38F36 (kernel32.dll)
0306F16C: 00000000
> 0306F170: 33BBB3DA 33BB0000 + B3DA (mcplug.dll)
> 0306F188: 33BBB520 33BB0000 + B520 (mcplug.dll)
> 0306F194: 33BB8449 33BB0000 + 8449 (mcplug.dll)
> 0306F1AC: 01163691 01150000 + 13691 (vegas80k.dll)
0306F1B0: 05DC1EF8 05AD0000 + 2F1EF8
0306F1B4: 0306F1E8 02F70000 + FF1E8
0306F1B8: 0000A6B4
0306F1BC: 3A47EF3C 3A0C0000 + 3BEF3C
> 0306F1E0: 01163578 01150000 + 13578 (vegas80k.dll)
0306F1E4: 05DC1EF8 05AD0000 + 2F1EF8
0306F1E8: 3BFFDD90 3A0C0000 + 1F3DD90
0306F1EC: 3A47EEF0 3A0C0000 + 3BEEF0
0306F1F0: 00000000
> 0306F1F4: 007425B2 00400000 + 3425B2 (vegas80.exe)
0306F1F8: 01FC6870 01F30000 + 96870
0306F1FC: 3A47EF3C 3A0C0000 + 3BEF3C
0306F200: 3A47EEF0 3A0C0000 + 3BEEF0
0306F204: 00000000
> 0306F21C: 00744E70 00400000 + 344E70 (vegas80.exe)
0306F220: 0306F234 02F70000 + FF234
0306F224: 00000000
0306F228: 0306F7A8 02F70000 + FF7A8
0306F22C: 00000000
> 0306F294: 7C910945 7C900000 + 10945 (ntdll.dll)
> 0306F298: 7C91094E 7C900000 + 1094E (ntdll.dll)
> 0306F2AC: 7C914190 7C900000 + 14190 (ntdll.dll)
> 0306F2B4: 7C901005 7C900000 + 1005 (ntdll.dll)
> 0306F2C4: 7C90EE18 7C900000 + EE18 (ntdll.dll)
> 0306F2C8: 7C910970 7C900000 + 10970 (ntdll.dll)
> 0306F2CC: 7C97E4C0 7C900000 + 7E4C0 (ntdll.dll)
> 0306F2D0: 7C913E6F 7C900000 + 13E6F (ntdll.dll)
> 0306F2D4: 7C913E62 7C900000 + 13E62 (ntdll.dll)
> 0306F308: 006E006C 00400000 + 2E006C (vegas80.exe)
- - -
0306FFF0: 00000000
0306FFF4: 005258F0 00400000 + 1258F0 (vegas80.exe)
0306FFF8: 00ADA678 00400000 + 6DA678 (vegas80.exe)
0306FFFC: 00000000

Cliff Etzel wrote on 6/22/2008, 6:25 PM
Holy Shnikees Darren!!!

This doesn't bode well for me on this upcoming project I'm developing - I'm actually giving Avid MEdia Composer a serious look. I found someone who has a copy installed on their machine and had to open my mind to the way Avid edits. Brought a series of m2t files I captured in Vegas - Media Composer can't open them!!!

Here's the actual error message:

Exception: DIOTSPParser::Parse - bufferSize (245248) is invalid

Whiskey Tango Foxtrot!?!?!

That tells me Vegas capture utility is mangling my m2t files in some way that Media Composer can't overcome. I thought m2t files were just m2t files. Guess not. I was going to go thru some tutorials my colleague has on his computer with some of my captured footage - but it seems I can't even do that.

Combined with your continued challenges with Vegas Darren, I'm becoming more hesitant to rely upon Vegas for longer projects that require lots of clips. What little I saw from the colleagues editing session, Media Composer is FAST! Real time playback from the timeline - I was impressed. I only use cuts, dissolves, basic titles and color correction. MC seems like the ideal tool for this - but it's audio tools aren't up to snuff...

Cliff Etzel - Solo Video Journalist
bluprojekt | SoloVJ.com
Darren Powell wrote on 6/22/2008, 7:34 PM
Roger Wilco. What's Your Vector Victor?

Yeh, I only upgraded because of the audio stuff in Vegas ... now I'm Wallaby Teds brother (Roo Ted).

Farss has given me some options with the Veggie Toolkit converting m2t's into YUV files ... (the m2t's do appear to be getting mangled by Vegas ... by the looks of your error message going into MC ... maybe that's the source of the problem? ... who knows ...)

the m2t to YUV is sort of working but it's slow and torturous ...
would be much easier just to go 'Render' and watch the thin blue line go to 100% and produce a HD file ...

Cheers,

Darren Powell
Sydney Australia


Hitime wrote on 6/23/2008, 1:32 AM
Since writing this I have found the sony utility to stitch the mrc1 files together (took about an hour digging thro the sony site) WHY OH WHY COULD NOT SONY HAVE SUPPLIED THIS UTILITY ON THE DVD THAT CAME WITH THE Z7E???!!!

However the problem is not solved by using it. I am still getting lock ups in both v7e and v8b. SO I STILL HAVE A PROBLEM!!!

I have also captured the tape that ran in sync with the mrc1. This seems to work ok SO FAR!!!!
Hitime wrote on 6/23/2008, 1:37 AM
does avid support MTC sync? I 'll try it if it does.

farss wrote on 6/23/2008, 1:39 AM
I'm not familiar with the Z7e so bear with me here.
Does it have a prerecord option?
With the HD60 Sony HDD recorder the short m2t clips that the prerecord function writes seem to bring Vegas to its knees.

Bob.
Hitime wrote on 6/23/2008, 9:46 AM
not sure what a prerecord option is have not found it in the manual.

the z7e allows to record to tape and CM card simultaneously via the hvr mrc1. That is what I was using. The captured tape works in v8b but the download via the ru_util.exe utiliity found on the Sony website (which prime support confirm I should use) locks up v8b and v7e but not Edius 4.5.

Short clips seem OK so far. The only file that has failed was the only one i have made that exceeds the 4GB limit and so needs stitching.
the faulty clip should have been about 30 mins long and had 2 components on the CM card.

The HD60 seems to need the same utility so I guess produces similar files.

The utility seems to work ok so i gues that the CM card is not at fault and the stitdhed file works in edius 4.5
Hitime wrote on 6/24/2008, 2:55 AM
WOULD YOU BELIEVE IT!!! I can edit the file in v6d that I found lurching around on my sound machine!!

Obviously something REALLY bad happened between v6d and v7e!!

farss wrote on 6/24/2008, 6:42 AM
"WOULD YOU BELIEVE IT!!! "

Doesn't surprise me at all. V7.0e should have been called V7.1a. V7.0e projects may not open in V7.0d if they contain nested projects.

Which CF cards are you using. Spot some time ago seemed to believe that cards that were just a little too slow could be causing Vegas grief.

The pre record option in the HD60 keeps video being written to RAM in the unit. When you hit record the RAM buffer is written to disk, very handy for shooting wildlife I imagine. However the buffer ends up in it's own little file and according to at least one poster here (Megabit) that caused Vegas grief. This again says to me that Vegas's main problem is in the MC codec although Vegas has always had problems with mpeg-2 and unclosed / split GOPs. In the past you just lost a few frames at the join. More grievous defects such as correctable errors do seem to be the cause of crashes.

Bob.
Hitime wrote on 6/27/2008, 7:41 AM
CF card -- as supplied with z7e.

I took the offending footage to a demo day at my dealer. Sony Guys tried it on their PC (1gb 2.0GHz dual laptop) and it worked OK on their v8b -- no probs`. Very patient very helpful!!

The v6d I used was on my sound pc -- they thought might be good idea to re - install v8b -- it was done over v7e originally -- try that when I can and report back.