Vegas Pro 8.0c (http://www.sonycreativesoftware.com/download/updates/vegaspro)


Vegas Pro 8.1X64 (http://download.sonymediasoftware.com/current/vegaspro81_x64.exe)
Note: this link is to an exe file from the Sony software archive.


8.0c README FILE:

Notable fixes/changes in version 8.0c

* Added support for rendering 1920x1080 AVCHD video.
* Added XDCAM HD422 support.
* Added widescreen option for AJA print-to-tape.
* Added presets for AVCHD stereo output.
* Added ability to save markers in AVCHD output.
* Added ability to read certain MPEG-2 files with AC-3 audio.
* Added support for importing video from AVCHD camcorders (File > Import > AVCHD Camcorder).
* Added support for importing video from Sony CF card recording devices (File > Import > Memory Recording Unit).
* Added support for Nikon D90 MJPEG movies.
* Added support for XDCAM partial import with PDW-U1 drive.
* Enhanced Trimmer window with integral video monitor, separate external monitor, Enable Timeline Overwrite, and Fit to Fill modes.

When the Show Video Monitor button in the Trimmer window is selected, video that you preview from the Vegas Explorer and Media Manager windows is played back in the Trimmer. Because the Trimmer is placed in the same window dock as the Explorer and Media Manager, you will not see your video preview. To preview Explorer and Media Manager video, you can drag the Trimmer to a new dock group, or you can turn off the Show Video Monitor button to preview in the Video Preview window.

* Enhanced XDCAM Explorer pane with double-click and keyboard Enter key behavior that matches the Vegas Explorer pane.
* ProType Titler: added ability to copy envelope points and curve blocks using Ctrl+drag.
* ProType Titler: added ability to save effects and add/replace effects via drag-and-drop.
* Added support for opening Vegas Movie Studio 9 projects.
* Improved the number of MPEG-2 clips that can be active on a timeline.
* Improved HDV/AVCHD reading.
* Improved reading for certain 3GP and MP4 files.
* Improved device resolution choice for Windows Secondary Display when set the Display mode is set to Automatic Size Settings and the project is larger than the display.
* Fixed a problem that could cause masked video to appear incorrectly on an external monitor.
* Fixed a problem reading certain AVI files using DivX with MP3 audio.
* Fixed a problem reading certain Xvid format files.
* Fixed a problem reading some FLAC files.
* Fixed an issue saving markers in MXF format.
* Fixed a problem rendering to certain WAV/WAV64 variants
* Fixed Paste Event Attributes so it doesn't create phantom transitions that are then called out as missing during project load.
* Fixed a crash with the Matshita UJ-832D DVD-RW drive.
* Fixed issues that prevented Wave Hammer and Acoustic Mirror from functioning properly in some cases.
* Fixed duplicate file numbering of MP_ROOT MAS (SD) and MAQ (QVGA) files when using the Export to PSP™ command.
* Fixed an audio buzz that could occur with certain combinations of automated track muting.
* Fixed an issue with SDI capture when using non-dropframe timecode.
* Fixed an audio clicking issue with certain 29.97 or 59.94 fps MXF clips.
* Corrected ToolTip display for edited fade lengths when the timeline ruler is offset.
* Changed Cinescore detection to look for Pro version first and then Studio version.
* Fixed an issue reading certain MXF metadata.
* Fixed an issue with the Height Map plug-in not functioning properly at certain settings with high project resolutions.
* TWAIN initialization now occurs when Get Photo is used instead of during Vegas startup. This change prevents crashes due to bad drivers.
* Fixed a potential crash that could occur when switching to Markers or Regions view in the Edit Details window.
* Fixed eyedropper color picker under Windows Vista Aero Glass.
* Fixed a problem with long startup time when a computer is connected to a network but not the Internet.
* Improved scanning for VST plug-ins.
* Fixed a bug where VST effects would not always be notified of sample rate changes.

Still can't read native files from EX1 or EX3 ?

I'll install (c) tomorrow and try to import.
I want to get away from rewrapping to MXF.

Paul.

What? No DVCPRO HD? What a surprise. ;)

But it does support the D90. Cool.

soooooo.... can we import MXF from P2's without raylight re-wrap???

of the memory leak problem with stills?

Jon & Fred, there was a thread the other day (Panasonic vs Sony Vegas) where a Panasonic user (AG-HVX201) was complaining about not being able to import the footage directly into Vegas.
Jan Crittenden Livingston, a Panasonic Product Manager chimed in and said that, for a variety of reasons, Sony & Panasonic will probably never work together.
He said that Raylight is still the best alternative for Vegas users.

No support for MPEG4 wrapper in 8.0c just tested it....Very disappointing as After Effects handles them no problems...Come on Sony...Even Adobe can handle the raw files... Saving this support for version 9 seems crazy... as the Camera has been out a year now. I do not like having to use the browser and converting to MXF before I can edit..

One detail that I hadn't thought of, Ultimate S will not work with this new version, which is very disappointing. Since I depend so much on it, completely on it, I cannot abandon 32 bit just yet. I have discovered that reel paks still show up in the effects pane, which is nice.

I must say it seems quicker and more responsive...I like it so far. Rendering is faster, what previously took 20 minutes rendered in 14 minutes. Playback with effects has improved somewhat as well.

Sorry the issues you refer to aren't addressed Bill. I still shoot in SD, so the many issues that many have aren't even on my radar yet.

u gotta be kidding me! This is the long awaited 8.0c? Considering the HUGE number of issues 8b has that weren't addressed, this is a slap in the face. What a joke.
Well, goodbye vegas.

Ultimate S, that will also mean Celluiloid also wont work (I guess). Time to crack open the VMWare and give this a go in there before I upgrade.

what about 8.1 ? Does it have all the improvements from 8.0c ?

It would seem 8.1 is the same as 8.0c but just in 64bit.

As soon as I find out if Celluloid and MB Looks works I will be looking to switch although at the moment Reg Giant dont even suppor their apps on a 64bit OS so doubt there will be a 64bit version.

Why vendors are so behind is beyond me. 64bit has been mainstream for some years now and 64bit apps on 64bit hardware on a 64bit OS is faster. Its just at the moment 64bit vista is emulating 32bit.

Ive been on 64bit vista for a good few months now and its perfect. No probs what so ever and means I can make use of all 4gb. Drivers exist.

I think the problems many have had have been with their older or custom built rigs which use hardware without proper 64bit support i.e Nvidia cards as only 8series and above work properly.

Hi,

Just read in the Vegas forum that 8.1 is missing some new features, that were added to 8.0c (at least some things missing in the trimmer window - some of its new view possibilities).

This is proof that the development work for 8.0c and 8.1 parted some time ago. They are not exact replicas, the other 32 and the other 64 bit. I think too that it's very odd. And stupid.

Christian

"Why vendors are so behind is beyond me. 64bit has been mainstream for some years now..."

Danny, your wording is inaccurate. 64 bit apps, etc are not even close to mainstream even today. You might have meant they have been "available" for awhile. But 64 bit OSs will not be mainstream for a good while yet.

I am very disappointed also, but it is paritally my own fault. 32 bit plug-ins will not work with this release, and I should have thought of that before now.

What I meant is 64bit hardware has been around for years. Vista is the first real mainstream 64bit OS as XP 64 was just no good for anything. Vendors still dont support 64bit Vista and even less make true 64bit apps. Adobe are very behind and dont even offer 64bit flash support.

No, you're right Danny. It stinks...really does.

Despite my disappointment, I still give Sony kudos for being the first 64 bit NLE (they are the first, aren't they, or am I mistaken?).

I became disenchanted with Vegas a few months ago, but after looking around at the alternatives (for the tenth tiime) I've made my peace with it and have to admit that dollar for dollar, Vegas is a great program. Luckily I'm still shooting in SD, or I'd be singing a different song, I'm sure.

Biggest disappointment by far is the lack of 64 bit plug-ins. I still can't believe I didn't think of that in advance...

Great Thread-

I understand the Panny/Sony market share issues, and thanks. We've been a bit behind on the P2 technology but just purchased 3 200's. Amazing camera! We will start the Raylight wraps i guess. Can someone advise if the EX1 in Vegas is a better decision for workflow? Also with so much 64b disqualifications, could someone start a list of what will not work? Because it will suck bad if I download "c" or .1 and my plug ins turn grey...

Thanks

No, you're right Danny. It stinks...really does.

Despite my disappointment, I still give Sony kudos for being the first 64 bit NLE (they are the first, aren't they, or am I mistaken?).

I became disenchanted with Vegas a few months ago, but after looking around at the alternatives (for the tenth tiime) I've made my peace with it and have to admit that dollar for dollar, Vegas is a great program. Luckily I'm still shooting in SD, or I'd be singing a different song, I'm sure.

Biggest disappointment by far is the lack of 64 bit plug-ins. I still can't believe I didn't think of that in advance...

Ive been down that road also, and still keep coming back. We produce one of the few National Broadcasts totally created in Vegas and our EP just ordered all shows for 09 to be cut on FCP or AVID. My time is running out...

Actually Fred, your 32 bit will work just fine after installing 8.1...and 8.1 appears to be totally backwards compatible, no issues there. You can work on a project in 64 bit, reopen it in 32 bit seamlessly...and go back and forth all you like. I imagine it would be possible that some kind of file corruption could occur, so I'm not going to go back and forth unnecessarily...

My Ultimate S works great still with my original 32 Vegas installation and yours should also.

Jeff, are you saying 8.0 and 8.1 can co-exist on the same machine?

Hi,
This is proof that the development work for 8.0c and 8.1 parted some time ago. They are not exact replicas, the other 32 and the other 64 bit. I think too that it's very odd. And stupid.



You'd think so unless you carefully watched Task Manager when Vegas 8.1 started. Later versions will come from synchronized code.

Fred: Absolutely, that is what I've found...and Sony says (somewhere, forgot where I read it) that 8.1 is backward compatible.

I've opened up a lengthy project created in 32 bit, resaved it with another name to be safe, opened it up with 64 bit, and then reopened it in 32 bit then saved and reopened in 64 bit again.......no problems at all.

As I mentioned, though, I'm not going to press my luck by going back and forth unecessarily. At this early stage that is only asking for problems until more is known. Other than the freezing of 8.1 when attempting to view with firewire display, it is a painless installation, and so far I see NO danger of using it alongside the 32 bit version.

hmmmm...

I've been playing with the preview window and WFM, 8-bit vs. 32-bit float. Could it be? Did Sony fix the preview monitor and WFM problems? It's behaving differently than v8b. No mention of a fix in the 8c changes, but, perhaps there is more to this than Sony wants to admit. It would have been nice to annunciate whether the WFM calibration is REC601 or 709.

I think despite unaddressed issues and imperfections this is a decent first version of a 64 bit NLE. I hope there is more to it than they have said...would be a pleasant surprise. Now, if I could only get it to preview on my JVC, I'd much happier.

Any thoughts Bill?

This might be a dumb question but can a .veg created with Vista 64bit be openned with the 32 bit version?

Garrett,

Look at Jeff's reply 4 boxes up ;)

New issue for me: in 64 bit, two clips appear to be invisible to Vegas when playing back and when rendered. Very strange. When I open the project in 32 bit, it is fine.

If the project had been created in 64 bit, I bet the problem wouldn't be there.

I uninstalled it. I'm done with it for now. Hopefully when I reinstall windows, etc, one day it will go better.

Overall, Vegas 8.1 seems fine, just a couple of bugs that I cannot workaround. It definitely runs fast and renders faster. At this point 64 bit is a novelty, and not much more.

With the issue of no plug-in support, I don't suppose it's worth much to me as it is. And with the inability to preview and AND invisible clips, I just don't have time for it.

I plan to keep an eye on these threads and see you how the rest of you do. What is strange to me is that so few are reporting their experiences...I would have expected droves of reports by now...

What is strange to me is that so few are reporting their experiences...I would have expected droves of reports by now...

It's a friday, most people will start speaking up over the weekend.

I was lucky enough to read this thread before I upgraded. I ended up installing 8c rather than the 64bit based on your experiences. I'm in the middle of episode one of an eight episode project, so I think going to hold off until I finish.

I plugged in our Cannon HG10 and the software now imports and plays its flavor of avchd files flawlessly (so far). Other than that I like the new trim window...

I'm suprised I've not heard any comments/feedback related to the notorious black frame issue. Wasn't that to be fixed in this release? I frankly have never quite been able to figure out what the problem was that people were having but many Vegas users complained of this problem and it seemed a major one due to be "fixed".

Any word on this?

Jon

the issue was fixed by a beta release of a v8b .dll, a few weeks ago.

Actually, I've never read about it before, but I've experienced first hand with 8.1. Glad you mentioned it...now I know I'm not completely crazy nor am I the only one that's had it.

hmmm..something strange still happening with vegas preview window and scopes. it shows the cineform codec to be full RGB0-255, while both Avid and edius show the same color bar pattern to be broadcast RGB. but, funny thing is, I believe what I see, now, unlike with v8b.

Vista is the first real mainstream 64bit OS as XP 64 was just no good for anything.

Interesting. Vegas 8.0b has yet to crash under XP64 on my laptop and the newly downloaded 8.1 seems to offer a 20-25% speed increase on the same laptop. It's not twice as fast, but I'll gladly take the improvement.

I've only had a brief play on the laptop, I'm editing on my desktop, and like the other member mentioned above, I won't think of upgrading till the current project is finished.
Have noticed it handles AVCHD better, but a big bug for me is you can't preview from explorer with the auto play option, it plays the sound but not the video. Still has the still's problem for ram leak as well. But as I said only had a few minutes on it so far. Can't believe they broke something like the preview function!

Have noticed it handles AVCHD better, but a big bug for me is you can't preview from explorer with the auto play option, it plays the sound but not the video. Still has the still's problem for ram leak as well. But as I said only had a few minutes on it so far. Can't believe they broke something like the preview function!


It is not a bug but a new feature.
From the readme file:

When the Show Video Monitor button in the Trimmer window is selected, video that you preview from the Vegas Explorer and Media Manager windows is played back in the Trimmer. Because the Trimmer is placed in the same window dock as the Explorer and Media Manager, you will not see your video preview. To preview Explorer and Media Manager video, you can drag the Trimmer to a new dock group, or you can turn off the Show Video Monitor button to preview in the Video Preview window.

I jumped ship from vegas to fcp last year due to too many problems including no mxf handling, funny scope readings that i could never trust, unpredctable renders in regards to color, lack of third party support and many more things but i always said to myself i will go back once sony sort themself out because hands down it's the most user friendly program out there. However....after seeing the new installmenst from sony a year later, I can't say I'm impressed, many of the problems i left sony for are still aparant and I feel like while vegas is clearly leading in some respects (64bit, excellent audio editing etc) the other NLE's have paid attention to areas that are in demand from their users and thus this is the reason why I'm sticking with FCP, but i may keep sony around for some audio work but nothing else.

hmmm..something strange still happening with vegas preview window and scopes. it shows the cineform codec to be full RGB0-255, while both Avid and edius show the same color bar pattern to be broadcast RGB. but, funny thing is, I believe what I see, now, unlike with v8b.

Thanks Bill.

I'm interested in any more of your thoughts on Vegas 8b vs 8c colorspace / levels madness.
I have not had time to check out 8c.
I hope it has improved.

It is not a bug but a new feature.
From the readme file:

It is not a bug but a new feature.
From the readme file:

Quote:
When the Show Video Monitor button in the Trimmer window is selected, video that you preview from the Vegas Explorer and Media Manager windows is played back in the Trimmer. Because the Trimmer is placed in the same window dock as the Explorer and Media Manager, you will not see your video preview. To preview Explorer and Media Manager video, you can drag the Trimmer to a new dock group, or you can turn off the Show Video Monitor button to preview in the Video Preview window.

Gilles, how can I get back the same old video preview and not on the trimmer. I always take snapshot of the video in the preview mode. Now there is no auto preview, I am finding it very in-convenient. If there is no way out, I guess I will have to stick to 8.0b

Gilles, how can I get back the same old video preview and not on the trimmer. I always take snapshot of the video in the preview mode. Now there is no auto preview, I am finding it very in-convenient. If there is no way out, I guess I will have to stick to 8.0b

As mentioned in the readme file, you have to Uncheck « Show video monitor » in trimmer window

Hi Steve...

I really wish Sony would provide more documentation. Relative to 32-bit mode, their help files says ...
*32-bit floating point is recommended when working with 10-bit YUV input/output or when using xvYCC/x.v.Color media.

*When using 8-bit input/output, the 32-bit floating point setting can prevent banding from compositing that contains fades, feathered edges, or gradients.

I notice, also, that using 32-bit mode allows some file types(mxf, m2t) to display superwhites. Turning 32-bit mode off shrinks everything to broadcast luma ranges. This is most apparent when importing a colorbar pattern from either my EX1 or HD110. Of course, in 8-bit mode, if I want full 0-255 RGB, I have to apply a levels filter. Why is that? The files are certainly not 10-bit, and the excessive render time in 32 bit mode is unwieldly. If I, first, convert my native mxf file to avi with Cineform Neo HD and import the result, I get full 0-255 RGB, regardless of the bit depth. Now, that adds to my confusion.
edit: the inconsistency with cineform seems to have been a problem with cineform, which is now fixed

Of particular concern is that some render codecs apply an RGB conversion on top of what Vegas already applies, resulting in washed out images. So, for example I start with a colorbar pattern in 8-bit, that shows RGB 16-235. I render this out with something like DVCPRO50, and the result shows a colorbar pattern with RGB 33-225, which is clearly incorrect.

I continue to be baffled. Sony continues to not provide any explanation, documentation or advice regarding this behavior. There are plenty of 3 party pundits who claim to explain the behavior, however, I've yet to understand their logic.

I tried to download 8.0c, but my ICON still says 8.0a. Am I doing something wrong? Do I download and save to Vegas 8.0 file? Also, same issue with DVD 5.0. Any suggestions? Bob

Bob, did you also install it? You can always see what version you're running by starting Vegas. The splash screen will indicate your version. If Vegas is already started, you can go to Help - About and that screen will also tell you the actual version.

I agree with Edward, it sounds like you downloaded the .exe file, but didn't actually run it. You need to click on the file that you downoaded and install the program.

Ed/Jeff, thanks for your replys. I re-downloaded this morning and "saved" it to Vegas 8. Last time I think I screwed up and saved it to my documents. After reloading, I restarted the computer and there it was. Vegas 8.0c. Tonight I will upload dvd 5.0. Thanks again. Bob

You don't have to "Save it" any place in particular. You shouldn't store the exe file in your vegas folder...you are wasting space there.

Just download a file like this to your desktop, or anywhere. Click on it, let it run and then when it's finished delete it. Or if you are like me save it on another hd IN your software folder.

Thanks Bill...
Man, I was really hoping Sony would address this madness.

Right when I think I now know how to deal with certain footage with RGB level corrections (that should not be needed in the first place), things can go astray in the end by the time its rendered to the final media.

What the....



Hi Steve...

I really wish Sony would provide more documentation. Relative to 32-bit mode, their help files says ...
*32-bit floating point is recommended when working with 10-bit YUV input/output or when using xvYCC/x.v.Color media.

*When using 8-bit input/output, the 32-bit floating point setting can prevent banding from compositing that contains fades, feathered edges, or gradients.

I notice, also, that using 32-bit mode allows some file types(mxf, m2t) to display superwhites. Turning 32-bit mode off shrinks everything to broadcast luma ranges. This is most apparent when importing a colorbar pattern from either my EX1 or HD110. Of course, in 8-bit mode, if I want full 0-255 RGB, I have to apply a levels filter. Why is that? The files are certainly not 10-bit, and the excessive render time in 32 bit mode is unwieldly. If I, first, convert my native mxf file to avi with Cineform Neo HD and import the result, I get full 0-255 RGB, regardless of the bit depth. Now, that adds to my confusion.
edit: the inconsistency with cineform seems to have been a problem with cineform, which is now fixed

Of particular concern is that some render codecs apply an RGB conversion on top of what Vegas already applies, resulting in washed out images. So, for example I start with a colorbar pattern in 8-bit, that shows RGB 16-235. I render this out with something like DVCPRO50, and the result shows a colorbar pattern with RGB 33-225, which is clearly incorrect.

I continue to be baffled. Sony continues to not provide any explanation, documentation or advice regarding this behavior. There are plenty of 3 party pundits who claim to explain the behavior, however, I've yet to understand their logic.