10.0e Look at the sticky

amendegw wrote on 7/5/2011, 10:10 AM
Subject says it all

...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

Comments

Grazie wrote on 7/5/2011, 10:14 AM
Well? Anybody dipped their tootsies in the water yet?

Grazie

Robert Johnston wrote on 7/5/2011, 11:01 AM
I've been using the 32-bit version for almost an hour now and haven't had any crashes. Downloading the 32-bit version was quick. Downloading the 64-bit version was slow.

Intel Core i7 10700K CPU @ 3.80GHz (to 4.65GHz), NVIDIA GeForce RTX 2060 SUPER 8GBytes. Memory 32 GBytes DDR4. Also Intel UHD Graphics 630. Mainboard: Dell Inc. PCI-Express 3.0 (8.0 GT/s) Comet Lake. Bench CPU Multi Thread: 5500.5 per CPU-Z.

Vegas Pro 21.0 (Build 108) with Mocha Vegas

Windows 11 not pro

Former user wrote on 7/5/2011, 11:26 AM
Downloaded & insatlled the 64-bit. So far so good. Not noticing anything wacky. Mind you, 10d was good for me, and I'm working on a personal project today, so I can risk the upgrade. :-)

But yeah...smooth sailing so far.
Tom Pauncz wrote on 7/5/2011, 11:33 AM
Dipped entire body! :-)

So far so good.

Tom
Randy Brown wrote on 7/5/2011, 1:23 PM
I was sure hoping the random replacement of footage issue would be fixed : (
Christian de Godzinsky wrote on 7/5/2011, 1:24 PM
No wonder why this forum is soooo sluggish.... with all the download activity going on...

I didn't see some of my problems on the fixed issues list. Remains some testing...

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

Ros wrote on 7/5/2011, 1:25 PM
I was hoping they fixed copy / paste events with OFX from a Vegas session onto a second Vegas session, but sadly it isn't, still crashing in 64 bits mode. Will have to rely on 32 bits mode :(
Randy Brown wrote on 7/5/2011, 1:45 PM
Hmmm...I just downloaded/installed the new release and opened 2 instances...is it my imagination or could this new version be twice as fast when loading and opening projects and files?
Tom Pauncz wrote on 7/5/2011, 2:03 PM
Not your imagination Randy. I am seeing the same thing.

However, as disappointing as it may be, my "undo" issue is still unresolved after 3 updates - first reported (and repro'd by SCS) against 10.0a.

Otherwise I haven't found anything broken.

Tom
Steve Mann wrote on 7/5/2011, 2:09 PM
I upgraded mid-project - typical of me - and no problems noted.
Erni wrote on 7/5/2011, 7:56 PM
No problem here. 64bit version over W7Ultimatte 64.

Thanks guys.

Erni
John_Cline wrote on 7/5/2011, 8:16 PM
10.0e works great here...
ushere wrote on 7/5/2011, 8:18 PM
win7/64 - vegas 64 10e - so far so good.....

(not that i had any complaints beforehand)
PeterWright wrote on 7/5/2011, 8:41 PM
32 bit installed fine ... 64 bit didn't - "Error 1603 occurred during installation"

I downloaded again in case something was corrupted - same result.
Anyone else get this?

Not a big deal - no hassles with 10d.

I suppose I should write to Support, grrrr - it takes so long filling in all those boxes with already known information......
Steve Mann wrote on 7/5/2011, 8:54 PM
Call customer service, not tech support. (If I recall) A 1603 error is from too many registrations.
Rory Cooper wrote on 7/6/2011, 12:27 AM
I only installed 10d last week and nearly every existing project was a hang and crash ????

Hope this sorts that out.
Marton wrote on 7/6/2011, 12:36 AM
Does this release open VMS11 projects?
How about the MVC bitrate? Can it be more than 25mbps?
Can i preview stereo projects with nvidia 3d vision on secondary, 120Hz monitor?

thx
PeterWright wrote on 7/6/2011, 12:46 AM
Thanks Steve - if that's what Error 1603 means, it must be an error - one registration can't be too many!

Anyway, I won't bother to phone - it's not urgent and it'll be good to see how long online support takes.
DonLandis wrote on 7/6/2011, 2:18 AM
Bug report:


I found a two serious bugs so far:
upgraded from 10d 64bit to 10e 64 bit.

1. After upgrading to Vegas 10e my blue ray drives are no longer recognized by Vegas 10e. They remain recognized and functional in DVDA 5.2.
They are listed in the Burn Blue Ray section but are grayed out and no option to select operation except render to iso image only.

2. Immediately after upgrading to Vegas 10e, My Vegas Studio v11 crashes upon launch becoming non responsive at the part where it says loading Video services.


I tested the Blu-Ray burn to image only which is the only option remaining since my drives are grayed out in 10e and it rendered 3D iso image fine.
I then loaded the 3D iso image file in DVDA 5.2 and it burned the file properly and the disk plays fine in a standard BluRay player.

Why is my Blu-Ray burner no longer recognized in Vegas 10e?
Rob Franks wrote on 7/6/2011, 3:14 AM
"1. After upgrading to Vegas 10e my blue ray drives are no longer recognized by Vegas 10e"
It's only a 'bug' if it's reproducible.... which I can't do. My drives are okay. I also have no issues with my copy of VMS. I would say as a result that these are not 'bugs' but something not quite right with your machine.
DonLandis wrote on 7/6/2011, 5:20 AM
I understand that. It could be a corrupted upgrade or bad download file for 10e as the drives are recognized with all other applications. Even prior versions of Vegas 32 and 64bit.

I've checked for driver and firmware updates on the burner and they are current. Next I plan to uninstall Vegas Pro altogether and do a fresh download and install at the 10e level.
Stom wrote on 7/6/2011, 7:12 AM
Here you have a list of windows installer error messages.

http://msdn.microsoft.com/en-us/library/aa372835%28v=vs.85%29.aspx
PeterWright wrote on 7/6/2011, 7:26 AM
Thanks Stom. That's very helpful. I'm in mid-render right now, but when it's done I'll restart W7, try another instal and see if that solves it.

[1603 - The file is being held in use by the following process: A system restart may be required because the file being updated is also currently in use. Users may be given the opportunity to avoid some system restarts by using the FilesInUse Dialog or the MsiRMFilesInUse Dialog. For more information, see System Reboots and Logging of Reboot Requests.]

... edit/update: It worked! I had made a point of closing Vegas before trying to upgrade, but anyway all I had to do was reboot Windows and all was well. I wish the error message had said "You need to reboot ..." I had no idea that Error 1603 was a Windows thing - I thought it was Sony's. I'll keep that URL that Stom supplied for furutre refernce ......
DonLandis wrote on 7/6/2011, 7:28 AM
Update on the BD burner problem.

I uninstalled versions of Vegas Pro 10e and redownloaded it again and installed. got same results. I reverted my install back to v10d which worked after first uninstalling everything again. Vegas 10d recognizes the drives and allows burning too. Upgraded the 10d to 10e and it failed again. I checked and the drives are recognized by Vegas in the about Vegas Pro multimedia devices menu as well as recognizing them as DVD burners in the burn DVD selection. All drivers are reported up to date.
I submitted a bug report.

BTW- It is quite incorrect that everyone must see a flaw for it to be a bug. All that needs to be done is for a given system to repeatedly produce a flaw and then it can be said that the bug is present under those conditions. If the hardware ( as in Blue ray burner) flaw only shows up with one application ( Vegas Pro 10e ) and it works fine with all other applications as well as previous versions of the same software, then it is a bug that surfaced in this configuration by the update.