new build - much better!

megabit wrote on 6/11/2015, 11:40 AM

I'm taking it back. Must have the clip in RAM or something - new clip old choking.

Piotr

Steve_Rhoden wrote on 6/11/2015, 11:42 AM

I hope this soothes much of the negative comments by many posters here,
especially those regarding XAVC long-GOP support, but unfortunately i know
there's gonna be something else found to gripe over!

David Johns wrote on 6/11/2015, 1:26 PM

Yes, playing XAVC-L here too at last but it chokes as soon as you do anything other than playing a clip. For example, add a crossfade and it stutters and slows even in Preview quality. Still, at least it can read the files now, eh?!

Cheers
David

NormanPCN wrote on 6/11/2015, 2:39 PM

Finally, the WaveHammer activation bug has been fixed. Only took more than a year!?

Grazie wrote on 6/11/2015, 4:13 PM

Excellent Norman!

G

John_Cline wrote on 6/11/2015, 5:00 PM

GoPro files now play back smoothly.

NormanPCN wrote on 6/11/2015, 9:04 PM

"GoPro files now play back smoothly."

I see that also. Seeks (position cursor) within an event are now as fast as other 1080p60 sources such as GH3 and Vegas XAVC-S.

monoparadox wrote on 6/11/2015, 11:09 PM

Looks like I can finally remove Vegas 12.

--tom

NickHope wrote on 6/12/2015, 1:54 AM

Thanks for the update SCS, and for addressing some very important issues.

Now please move on to these oustanding issues:

1. Crash when renaming files in Vegas Explorer window
2. Panasonic GH4 23.976p and 24p clips have extended video
3. Crash after paste event attributes
4. Bug loading windows layout at startup
5. GPU bug: Pale edges of imported Photoshop layers
6. Sony Sharpen behaves differently with GPU
7. Project Properties Frame Rate Undo Bug
8. Crash clicking empty header of VP Explorer column

megabit wrote on 6/12/2015, 3:46 AM

I tested some X70 4k XAVC-L clips again on my friends super-fast computer and a 50" plasma HDTV (not UHD) and I must say something is terribly wrong with the quality - as if the clips were interlaced or something; there is a lot of jerkiness in panning and jagged lines. If that is the final quality of the troublesome X70 4k XAVC-L codec - the camera is seriously flawed...

Piotr

PS. 4k material I tested so far (AX100, AX1) is absolutely stunning when compared to the X70 with this codec! Also, I can see the same artefacts in VLC, so it's not Vegas fault this time.

Aaron Weaver wrote on 6/12/2015, 4:04 AM

I'm terribly afraid I'm going to jinx myself, but here goes...

This latest version fixed almost all my problems and crashes. I was literally in tears over the past several weeks and had downloaded Avid Media Composer with the intention of limping along in Vegas to get the pilot finished and then migrate to Avid Media Composer. Trouble is, I don't have the time to learn Avid.

Came home from work today and launched Vegas. Nervously I awaited as the download finished. Launched a 44 minute pilot I've been working on for months. With the previous build I would edit and with every single keystroke I would follow up with a save. Crashes all the time...between 6-12 crashes per work session.

I installed the latest build and it's smooth as butter. I ran it through the processes that caused the crashes and it completed the tasks without hiccup.

Still having problems with unreasonable launch times because Vegas rebuilds the audio waveforms each time. I believe I have found the issue to be the USB 3 external drive. I have two workstations running Vegas and have never had a problem with excessive launch time in the older workstation. The older machine has all eSATA RAID drives attached, The new, problematic machine, has only one USB 3 RAID drive.

I've found little online concerning the forced waveform rebuild, particularly with the more recent versions of Vegas. But, I've also read a lot of posts on various fora indicated a lot of problems with various USB 3 drives.

I just want to thank the engineers at SCS for squashing the bugs that caused me so much pain and anxiety.

Aaron

megabit wrote on 6/12/2015, 5:00 AM

When comparing all these new 4k cameras using Vegas, we must remember that not all of them (or their codex) have been made equal - and when something doesn't work (or works worse than the rest of the bunch), it's not always Vegas Pro's fault.

As I have stated, 4k from the AX1/AX100 cameras plays back stunningly, with this "out-of-the-window" wow look. But I forgot about one more camera that also plays absolutely wonderful in Vegas: the JVC GY-HM200. Even though the native samples I have are in the dreaded MOV wrapper, they play full speed at Best/Full and the picture is amazing. Oh, and the 4k codec is 8 bit 420, but not overly compressed at 150 Mbps (the fps is 25). If only the sensor was a tad bigger and better in low light...

Piotr

wwjd wrote on 6/12/2015, 8:24 AM

yeah that GH4 thing just isn't popular enough to fret about compatibility.... :D

Pedro Rocha wrote on 6/12/2015, 8:56 AM

playing XAVC-L here too at last but it chokes as soon as you do anything other than playing a clip. For example, add a crossfade and it stutters and slows even in Preview quality.

Now that the PXW-X70 records proxy files you can use the XDCAM workflow using the XDCAM Explorer window and work with proxy files on the timeline and after your editing is done replace (conform) them by the high resolution ones (pag. 406).

Or creating proxy files within the Vegas Pro 13 (pag. 102).

Pedro

monoparadox wrote on 6/12/2015, 9:55 AM

4k from Phantom 3 Pro now smoothly playing back on timeline at full frame.

Confirmed Wavehammer fix, too.

-- tom

NormanPCN wrote on 6/12/2015, 2:23 PM

To add to items that have been fixed. I had an AVC MP4 file downloaded from Youtube that did not play in Vegas. I just got a green screen for video and audio was fine.

The new AVC decoder in Build 453 fixes this playback problem.

A render problem with GPU on for XAVC Intra has been fixed. Previous bad result was corrupt green blocks flashing around the screen.

The HSL effect GPU bug still exists.

A problem with the Radial Blur effect when GPU is OFF still exists. GPU ON is correct.