Vegas Pro 8.0a and DV Arch 4.5a Released today

john-beale wrote on 10/18/2007, 2:04 PM

Ok, I installed the V8a trial. It does open and view my deadly .m2t clip of roses that crashed V7e, so far so good.

I wanted to try out the new feature exporting Sony AVC with the Blu-Ray 1440x1080 60i, 8 Mbps template. I don't know what to do with the .AVC file but if I set it to generate .MP4 then I can play the output using Nero ShowTime 2 and it looks fine. (VLC Player 0.8.6c and Quicktime Player 7.2 could not handle it- maybe because it is interlaced?). I assume the .AVC format is intended only for Blu-Ray burning software (?)

blink3times wrote on 10/18/2007, 4:32 PM

jbeale:
Thanks for replying. I can confirm the error that you are seeing in Vegas 7.0e. We will not be releasing any further updates to version 7 of the program.

You can always return to 7d which does not have this problem. It's only 7e and the original version8 with the stability problems on HDV.

ken c wrote on 10/18/2007, 5:27 PM

Right, John....

I've still been using v7 this last month for production, just peeking at 8 now and then...
NOW I'll start using v8... thx to all who helped them iron out the release bugs these last few weeks, looks like it's ready to put into production... :p

we live and learn... Now it's time for a V8!

-k

Mahesh wrote on 10/18/2007, 11:12 PM

Quote:The veg files have a new icon too. Looks nice. j razz

Beauty is in the eye of beholder. This beholder thinks Ugllllly:)

megabit wrote on 10/19/2007, 2:45 AM

OK, so with regards to my problem of importing media from the DR60 drive:

SCS didn't even confirm the flaw existed, until I proved it to them "with a little help from my friends" of the Sony Prime Support. In 8.0a, the chunks get connected and the resulting, single file per DR60 directory, now is seen in its full length (over 1 hour; before 8.0a it was only seen as some 2 mins long), and even can be put on the timeline (impossible before). However:

- it still doesn't play correctly; it can be srubbed from the beginning to the end, but when I hit play, there is no audio (even though the peaks have been built)

- the target drive gets awfully fragmented; I just saved a new project including such a concatenated clip (over 12GB) and on re-opening, Vegas got stuck at 15% opening the project. I'm waiting...

- the resulting clip is seen as Upper field first, even though the source clips were progressive

- I have black frames at the beginning and end of the clip.

So, there is some progress, but still it's far from perfect.

megabit wrote on 10/19/2007, 9:17 AM

Just to update those affected like me: the DR60 import/concatenation problem is most probably audio related.

Also, I canot confirm the HDV smartrendering being clean - still plenty of pixelation even outside any edit points.

24Peter wrote on 10/19/2007, 9:54 AM

So just to clarify for someone who's been on the fence about going from V 7e to 8:

- I still don't have the ability to create BluRay DVD's using DVDA 4.5. All I can do is burn, what, BluRay or hi-def DVD-R's straight from the V8 timeline? (If that's anything like printing to tape from the timeline, it must be a disaster.)

- I'll get better previews of my HDV .m2t files using V 8 and reduced rendering times b/c of smart render? (Better previews alone might justify the $150 upgrade cost.)

Wolfgang S. wrote on 10/19/2007, 1:49 PM

You are right - the DVDA 4.5 cannot create a Blu Ray structure, the DVDA is still for SD-DVDs only. As you said, you can create a Blu Ray structure from the timeline - without menus, but you can either generate an iso, and burn that with another tool; or you burn directly to DVD/BD-R. It seems to be no disaster, even if that is still a new feature - and takes ongoing tests.

Better preview - hmm, the preview capabilites in Vegas are mainly driven by your processor power. With a duo-core or quad-core processor, you have excellent preview capabilites for m2t files. Smart rendering seems to work fine now in V8a - but that is not related to your preview capabilities really, even if the decoder seems to be newer now. The smartrender capability improves render times significantly, especially on older PCs. So, if you edit HDV, V8 is the better choice, compared with V7e.

DGrob wrote on 10/19/2007, 5:19 PM

OK, I did it. Just uninstalled V7e. Everything from here on out will be Vegas Pro 8a. What'a ride! Darryl

NickHope wrote on 10/19/2007, 9:13 PM

>> - I'll get better previews of my HDV .m2t files using V 8

I don't think there's any significant improvement if your m2t files are decoded by the Sony codec. That's already great in version 7. I have noticed a big improvement if your m2t files are decoded by the Mainconcept codec. (link)

and reduced rendering times b/c of smart render? <<

Certainly if you're rendering back to HDV m2t, yes. Not sure about the improvment if you're rendering to other formats.

megabit wrote on 10/20/2007, 2:43 AM

From what has been said above, I'd expect the m2t files encoded from the m2ts as copied from my DR60 dirve, using "Render as... HDV 1080/50i", to be seen by VP8.a as Mainconcept -encoded, right?

Well, mine still show the m2tsplug.dll as the plug-in...

Also - and this is something that beats me - the smart-rendered files play clean in Nero Showtime provided its hardware acceeleration is off; otherwise all bottom part of the picture freezes or pixelates.

Can anybody explain this?

NickHope wrote on 10/20/2007, 10:05 AM

>> From what has been said above, I'd expect the m2t files encoded from the m2ts as copied from my DR60 dirve, using "Render as... HDV 1080/50i", to be seen by VP8.a as Mainconcept -encoded, right?

Actually my smart-rendered HDV 1080/50i that includes both video and audio is also showing Sony's m2tsplug.dll as the plug-in.

If I render without the audio, but everthing else as per the default template, it still smart renders, and the playback performance is just as good, but MainConcept mcplug.dll is shown as the plug-in.

Playback performance of 1080/50i that shows the mcplug.dll in version 7 is much inferior.

I guess the Sony plug-in is only listed if it's a fully HDV-compliant transport stream.

Sorry if I misled you a bit.