Comments

ushere wrote on 4/20/2009, 7:13 PM
i haven't read anything about avchd improvements in anything as yet - of course there may well be in the actual release....

other than a lot of 'bells and whistles' (nice, but not exactly major), and the ability to handle larger graphics (most welcome), there's not a lot that tempts me.

i was hoping that avchd would (should) have been sorted in 8 - making the purchase of a couple of small hd cameras a practical option.
Tomsde wrote on 4/21/2009, 4:49 AM
I echo the questioin; is AVCHD handling improved in Vegas Pro 9? I would have thought that this would have been a big thing that needed addressing. It could be an "under the hood" issue that's improved but not mentioned. I did notice that AVCHD handling was better in Movie Sudio Premium Pro 9--I can only assume that it is better in this version.
blink3times wrote on 4/21/2009, 5:09 AM
There is nothing to indicate "full resolution playback" (and by that I assume you mean setting preview up for "best" preview.... which can't even really be done with HDV) Point of fact.... NOTHING edits native avchd very well. Not Pinnacle, not Grass valley, not FCP, not Premiere... This is not the fault of the nle but rather the complicated compression scheme involved Other nle's have gotten around this by converting it to something else before editing. Short of that, pure horse power and a BM intensity card would be the ultimate weapon for "full resolution playback"

You may see a MILD improvement in handling, but I wouldn't get the hopes too high.

If you want to yell at somebody, then yell at sony/panasonic camera devision for pushing this avchd so hard in the first place and offering little in the way of other options.

Avchd may be a great delivery format, but it will absolutely STINK as an editing medium for years to come.
Hulk wrote on 4/21/2009, 6:35 AM
I remember 10+ years ago when people were authoritatively that we'll NEVER be able to edit MPEG-2 without hardware support because the compression was too complex. A year or two later we were editing it no problem. MPEG-2 SD handling has been trivial for many years now.

I, and many others, are editing AVCHD right now on fast duals and quads. Yes there is the Quad core rendering issue that I am reading about, and the limited output options, and some stability issues, but we are doing it.

Is it too much to ask for Quad core rendering to work with Sony Vegas Pro 9 and AVCHD?

It is too much to ask for all cores to be utilized 100% when previewing? It's a shame to see the processing power go to waste when previewing. I have a feeling AVCHD preview is not so much number of cores dependent but frequency dependent. So upgrading to a dual i7 Xeon with 16 cores (physical plus virtual) wouldn't do much for AVCHD previewing without some help from the internal code from Sony.

But then again this wouldn't look so good on the side of the box for V9:

"Quad core rendering bug FIXED!!!"
"Multicore capable preview that NOW actually utilizes all cores at 100% during previews!!!"

blink3times wrote on 4/21/2009, 6:57 AM
"Is it too much to ask for Quad core rendering to work with Sony Vegas Pro 9 and AVCHD?"
And you've tried it already and therefore know it doesn't work... right?

""Quad core rendering bug FIXED!!!""

Why? Was there something wrong with it? It works fine for me.... maybe it's the operator?

Christian de Godzinsky wrote on 4/21/2009, 2:10 PM
The Quad core rendering IS a real problem. Why do you b3t again insist just the opposite? You of all - that have even brought to our joy a "fix" for this annoyance???

Please do not blame us "operators" when the issue is at SCS. How can you be so naiive and believe that if everything runs smoothly for you, that no-one else could have problems??? You might not USE Vegas Pro the same way as other people do - that have problems... It is still SCS to blame if the sw does not do what it is supposed to do - edit and render video thrown at the timeline - at any promoted and listed format - without derailing...


Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

blink3times wrote on 4/21/2009, 2:43 PM
" You of all - that have even brought to our joy a "fix" for this annoyance???"

Precisely... so it's no longer a problem... correct?
Christian de Godzinsky wrote on 4/21/2009, 3:13 PM
The problem is that I don't understand this:

Why? Was there something wrong with it? It works fine for me.... maybe it's the operator?

What does it actually mean with this - honestly?

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

blink3times wrote on 4/21/2009, 3:31 PM
Since I have applied my work around I have not had any issues at all and there seems to be reports of the same. Is not working for you?
FilmingPhotoGuy wrote on 4/21/2009, 11:20 PM
Hey Blink, I really appreciate your valuable input and work around methods and tips you offer on other threads here. I have tried many of your suggestions and I can see that you know your stuff. However, please don't don't humiliate other "operators" who don't have powerful PC's and are definitly having issues. These forums are meant for us to "discuss" issues that bother us.

Thanks for your insightful advice so far, keep it up :)

- Craig