Vegas 11 Users: Guinea Pig Volunteers?

Comments

paul_w wrote on 1/30/2012, 3:02 PM
Interesting that it plays in a stand alone player but not Vegas.
Suggests the file is itself ok.

PS. and after some changes (its 5.1), the audio part of the file does play in Vegas. So its vision codec related perhaps.

Paul.
Steve Mann wrote on 1/30/2012, 3:04 PM
Yes, it crashes for me on V11. It does open on the only non-Vegas editor I have here - here's its output:
http://dl.dropbox.com/u/1421565/00137%20%28crashes%20Vegas%2010.0e%20every%20time%29.wmv
JJKizak wrote on 1/30/2012, 3:06 PM
Windows media player plays it just fine. V10E 32 crash. V11520 crash. This is a Vista 64 bit machine.
JJK
Tox wrote on 1/30/2012, 5:03 PM
Opens just fine in VP 8.1 64bit (build 171) -- crashes VP 11 64bit (build 521)
on a Vista 64 bit Machine.
Birk Binnard wrote on 1/30/2012, 5:58 PM
The clip plays fine in Windows Media Player on my Win7-64 SP1 system. But when I put the clip on the VMS timeline I get the message "THis clip has multiple audio tracks. Do you want to convert to 5.1 sound." (or words to that effect.

When I click Yes I get the crash immediately after VMS creates the new audio tracks.

What camera records 5.1 sound anyway?
johnmeyer wrote on 1/30/2012, 6:24 PM
What camera records 5.1 sound anyway?An awful lot of the newer cameras do. Of course you don't get a whole lot of separation, and the .1 channel is not going to be of much use, but the sound portion of the video is indeed 5.1.

I just did a quick look at the cameras on Slashcam and of the 61 models introduced in the past year, my rough estimate is that close to, or perhaps slightly more, than 50% of the new camcorders have 5.1 sound.

Erni wrote on 1/30/2012, 6:27 PM
Here crashes Vegas Pro 11 64 521 in all windows.

Works fine in A d o b e P r e m i e r e 5.5.2 and E d i u s 6.02. With audio 6 ch

Erni
Erni wrote on 1/30/2012, 6:29 PM
When copy/paste the error info of Vegas crash, this forum reject my message:

Your request has been blocked.

If you feel you have been blocked in error, please contact Sony Creative Software for assistance.

You will need to reference incident ID number.

The incident ID number for this request is: blablablabla.

Strange, not?

Erni
john_dennis wrote on 1/30/2012, 8:04 PM
The file caused Vegas Pro 11-521 on WIndows 7 64 bit to crash and start a report.

I remuxed to transport stream (ts) in tsMuxer and got these errors for those who know about transport streams.

MTS to ts Error

Attempt to demux

Vegas 8.0 worked.
VidMus wrote on 1/30/2012, 8:04 PM
"What camera records 5.1 sound anyway? "

My two Sony HDR-XR500V's do. I could turn that feature on, record a video and see if it will load in Vegas 11.

Last time I tried it was with version 10 and it did not crash so it has been a while.

VidMus wrote on 1/30/2012, 8:20 PM
I downloaded this clip and it crashes on Vegas versions 9 through 11. It crashes on load so I do not have to do anything else.

If I reload the video I will see the built peaks so it does build the peaks and then it crashes.

Vegas does not like this file. I sent the error reports each time. It will be interesting to see what happens with my cameras 5.1 files.
Steve_Rhoden wrote on 1/30/2012, 8:48 PM
It doesnt necessarily crashes Vegas 10.0e immediately
for me, but an error Dialogue box comes up as soon as
i try to play or try to do anything else.
Dale7 wrote on 1/30/2012, 9:07 PM
Vegas 8.0c
It plays video & audio

Vegas 9.0e
"Vegas Pro has stopped working" error as soon as it is dropped on timeline.
VidMus wrote on 1/30/2012, 10:34 PM
My camera video with 5.1 audio loads fine in Vegas.

Looking at the properties of the videos in Windows and also looking at the details your video shows 6 channels and mine shows 2. With Vegas set to separate each channel to a track your video has 6 channel and mine also has 6 channels. Mine has two streams and yours has ? number of streams. I cannot find out how many streams yours has as far as Vegas is concerned because of the crash.

Just for kicks I used Hand Brake to convert your video to MP4 with 6 discrete channels. It will load into Vegas 11 just fine with all 6 channels and looks just as good as the original.

So there is something in the way your original video is created that does not agree with Vegas 9 through 11.
Steve Mann wrote on 1/30/2012, 10:45 PM
"... close to, or perhaps slightly more, than 50% of the new camcorders have 5.1 sound."

The latest consumer buzzword?
farss wrote on 1/31/2012, 12:05 AM
"So its vision codec related perhaps."

Almost certainly.
I think if the camera was switched to 30p there would be no problem.

Bob.

farss wrote on 1/31/2012, 1:02 AM
Borrowed CX700.
Shot some 50p and 25p.
I really expected the 25p to work and the 50p to cause issues but both worked just fine, even the surround looked like it should.

All attempts to add your 60p sample I downloaded caused an instant crash in both V10 and V11.
I was able to add it to the Project media but adding it to the T/L caused a fairly prompt crash after it had finished displaying the waveform.
At one time did have some joy if I first Muted All Video. I could then add it to the T/L and at least see the thumbnails. All attempts to repeat this have failed, very strange.

I can only conclude that my previous idea that the problem is related to 50/60p not being part of the AVCHD spec is wrong.

Bob.
TheRhino wrote on 1/31/2012, 7:40 AM
Through the years I have found that Vegas is unforgiving if there are errors in the imported media file. To work-around this I have used PP or other applications to re-render the file to the same file format. I always check to make certain the new file is about the same file size as the old just to make sure I didn't accidently degrade the quality settings, etc. I also check the sound sync at a few points near the beginning, middle and end. Since I let the program render when I am doing other things, it really does not waste much time. It's a lot more efficient than trying to figure-out which Vegas version will work long-enough cycles between crashes to get any work done...

Workstation C with $600 USD of upgrades in April, 2021
--$360 11700K @ 5.0ghz
--$200 ASRock W480 Creator (onboard 10G net, TB3, etc.)
Borrowed from my 9900K until prices drop:
--32GB of G.Skill DDR4 3200 ($100 on Black Friday...)
Reused from same Tower Case that housed the Xeon:
--Used VEGA 56 GPU ($200 on eBay before mining craze...)
--Noctua Cooler, 750W PSU, OS SSD, LSI RAID Controller, SATAs, etc.

Performs VERY close to my overclocked 9900K (below), but at stock settings with no tweaking...

Workstation D with $1,350 USD of upgrades in April, 2019
--$500 9900K @ 5.0ghz
--$140 Corsair H150i liquid cooling with 360mm radiator (3 fans)
--$200 open box Asus Z390 WS (PLX chip manages 4/5 PCIe slots)
--$160 32GB of G.Skill DDR4 3000 (added another 32GB later...)
--$350 refurbished, but like-new Radeon Vega 64 LQ (liquid cooled)

Renders Vegas11 "Red Car Test" (AMD VCE) in 13s when clocked at 4.9 ghz
(note: BOTH onboard Intel & Vega64 show utilization during QSV & VCE renders...)

Source Video1 = 4TB RAID0--(2) 2TB M.2 on motherboard in RAID0
Source Video2 = 4TB RAID0--(2) 2TB M.2 (1) via U.2 adapter & (1) on separate PCIe card
Target Video1 = 32TB RAID0--(4) 8TB SATA hot-swap drives on PCIe RAID card with backups elsewhere

10G Network using used $30 Mellanox2 Adapters & Qnap QSW-M408-2C 10G Switch
Copy of Work Files, Source & Output Video, OS Images on QNAP 653b NAS with (6) 14TB WD RED
Blackmagic Decklink PCie card for capturing from tape, etc.
(2) internal BR Burners connected via USB 3.0 to SATA adapters
Old Cooler Master CM Stacker ATX case with (13) 5.25" front drive-bays holds & cools everything.

Workstations A & B are the 2 remaining 6-core 4.0ghz Xeon 5660 or I7 980x on Asus P6T6 motherboards.

$999 Walmart Evoo 17 Laptop with I7-9750H 6-core CPU, RTX 2060, (2) M.2 bays & (1) SSD bay...

amendegw wrote on 1/31/2012, 8:05 AM
"I can only conclude that my previous idea that the problem is related to 50/60p not being part of the AVCHD spec is wrong"1080 50/60p including 5.1 audio is a part of the AVCHD 2.0 Addendum

...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

ritsmer wrote on 1/31/2012, 8:06 AM
I just did a 5.1 and 50p (sorry, but I´m in PAL-land) video recording with my own CX700 (actually model CX690 = 700 without internal flash memory) and the Mediainfo looks precisely the same except for the 50/60p

Results here:

johnmeyer-clip: crashed 10.0e and 11/521 immediately

my own clip: no crash and works well with 10.0e and 11/521.


@johnmeyer: have you tried other clips from the same camera too? - maybe recorded directly to a SD card?
Jose M. Estrada wrote on 1/31/2012, 9:57 AM
It crashes both Vegas Pro 10e 64bit, Vegas 11 64 bit 521. PP CS 5.5 does not
Win 7 Pro 64bit
johnmeyer wrote on 1/31/2012, 11:10 AM
Many thanks to everyone for all their help. I think I now have the information I need to let SCS know that this particular problem extends to Vegas 11.

I really appreciate the TSMuxer information. I think that gets to the heart of what is going on.

Also, I got a PM, via YouTube from a lurker here who says that the file loads into SoundForge 9 just fine. I surmise that the MainConcept AVCHD decoder, which according to what we've discovered in this thread is used in Vegas 8, but not in later versions, is probably used in SF9 as well.

What I am hoping is that SCS can find a way to determine if an AVCHD file is "compliant" with the obviously stricter specs that they require for the file to be read and displayed on the timeline using their own AVCHD decoder, and if it doesn't meet those specs, the older, slower but more forgiving (less crash prone) MainConcept decoder be used instead.

As I have mentioned recently in other threads, this is exactly how things worked (and maybe still work) with HDV. In that case, the MainConcept MPEG-2 decoder was used for HDV in the early days, but then starting with Vegas 7, SCS developed their own HDV decoder in order to improve performance when editing HDV directly (i.e., without first converting to Cineform or other intermediate). They obviously did some sort of check because the HDV captured with HDV Split was handled using the MainConcept decoder, whereas the same HDV material captured with the Vegas HDV capture applet was (is) decoded by the SCS decoder.

ChristoC wrote on 1/31/2012, 3:46 PM
The plot thickens - on my WinXPproSp3 PC, where these applications are loaded:

SoundForge9e: not recognized as a 'known media file', but can open = only 2-track Audio appears, no Video.

SoundForgePro10c: recognized as a 'known media type'; file opens with Video and 6-track Audio. Plays fine.
File name 00137 (crashes Vegas 10.0e every time).MTS
Location C:\TempFile size 127.29 MB (130,337,956 bytes)
File attributes - --a- ----
Last saved 2012-02-01 08:15:40
File type MPEG-2 Transport Stream
Audio format Dolby AC-3
Audio sample rate 48,000
Audio bit rate 56,000 bytes/sec
Audio bit depth 16 bit
Audio channels 6 (5.1 Surround)
Audio length 00:00:40.157 (1,927,525 samples)
Video format AVC
Video attributes 1920x1080x32, 59.940 fps
Video length 00:00:40.157 (2,407 frames)
Video field order None (progressive scan)
Video pixel aspect ratio 1.0000 (Square)

VegasPro8c: recognized as a 'known media type'; file opens with Video and 6-track Audio. Plays fine.
General
Name: 00137 (crashes Vegas 10.0e every time).MTS
Folder: C:\Temp
Type: MPEG-2 Transport Stream
Size: 127.28 MB (130,337,956 bytes)
Created: Wednesday, February 01, 2012, 8:15:36 AM
Modified: Wednesday, February 01, 2012, 8:15:38 AM
Accessed: Wednesday, February 01, 2012, 8:15:38 AM
Attributes: Archive
Streams
Video: 00:00:40.157, 59.940 fps progressive, 1920x1080x12, AVC
Audio 1: 00:00:40.157, 48,000 Hz, 5.1 Surround (stereo downmix), Dolby AC-3
Audio 2: 00:00:40.157, 48,000 Hz, 5.1 Surround, Dolby AC-3

VegasPro9e: recognized as a 'known media type' but crashes (6-Chan Audio appears, Video track = grey) when added to timeline.

VegasPro10e: recognized as a 'known media type' but crashes (6-Chan Audio appears, Video track = grey) when added to timeline.

DVDArchitectPro5.0b: recognized as a 'known media type'. Plays fine.

DVDArchitectPro5.2_124 recognized as a 'known media type', can add to project, but crashes when attempt to Play.


and on another Win7_64 PC:

VegasPro11_520_32b = crash as above

DVDArchitectPro5.2_133 recognized as a 'known media type', can add to project, but crashes when attempt to Play.

Interesting that I had no luck opening the whole caboose with SoundForge9, whereas your 'lurker' did, and that there's no apparent problem with SoundForgePro10.

farss wrote on 2/1/2012, 12:19 AM
John,
there's another possibility given that the 50p from the Region50 variant of the camera works.

The region50 cameras are usually built after the initial batch of region60 cameras, maybe, just maybe, Sony realised there was a minor glitch in the 60p encoding and that was fixed in time for the region50 camera builds. It might pay to check if there's a firmware update for the camera.

Bob.