Is everyone cool with 10.0d so far?

Tim L wrote on 5/17/2011, 9:22 AM
I'm a low-demand, home hobbyist user, but just finished a project in 10.0b and now would be a good time to update.

I know there are a lot if issues that didn't get fixed in 10d, but other than that there's been very little drama on the forum about 10d. Has the update gone smoothly for everyone? Any new problems in 10d that weren't there before?

Tim L


bsuratt wrote on 5/17/2011, 9:41 AM
No problems.
reberclark wrote on 5/17/2011, 9:56 AM
So far so good here in 64bit Windows 7 running 10d 64bit. No problems.
JohnnyRoy wrote on 5/17/2011, 9:59 AM
Very solid here. I edit with it daily.

AGB Productions wrote on 5/17/2011, 10:18 AM
Seems to crash a lot on the large multicamera projects we do. So far, the only project that it hasn't crashed on was a slide show for a reception. We're using 10d on Windows 7/64 with a fast dual processor and a grunch of RAM. It's faster than our V9 on XP/32 (which we still use).
vtxrocketeer wrote on 5/17/2011, 11:29 AM
Tim, I'm a very high-demand home hobbyist. :P 10.0d has been OK on my system (Win 7 64-bit Ultimate, 8GB RAM),with one exception.

Others and I have been able to reliably crash 10.0d 64 and (especially) 32-bit when executing single or multiple (un)delete actions on events (HDV or Cineform avi; 1440x1080p or 1920x1080p project presets) that have at least one third party (i.e., non-Sony) event-level OFX applied. The OFX so far is capable of multi-threading and floating point processing, even though crashes occur in projects with 8-bit color depth, too.

It's a slam dunk especially when preview is full/best and RAM preview is a low number, e.g., 128MB. But see below: previewing in full/best is how I color grade!

Reversion to 10.0(c) 64-bit ELIMINATED the OFX-related crashes. Sony has been made aware of this issue.

Practically, this is what happens: lock down an edit and then start to color grade, apply FX, etc. Decide that you don't want a clip on second thought. Delete --> WHAM. Instant crashville. Maybe third thought -- add back the clip or move it elsewhere...nah, can do without it after all. Delete --> WHAM. Crash.

JJKizak wrote on 5/17/2011, 1:33 PM
I have 10d on Vista 64 bit ultimate and it seems solid although haven't done much with it. My other computer has Windows 7 and there is not much loaded on it (for online use only) and I have had 5 blue screens and 4 out of 5 times Windows 7 repaired itself. The one time it didn't it said the computer was no good so I cold booted it and it worked fine. One of the blue screens occurred during shutdown and Win 7 prevented the shutdown and repaired itself. XP was on the same machine before and it was fine. So as you can see I am not a believer in Win 7 32 bit pro.
SWS wrote on 5/17/2011, 2:16 PM
Seems I can pretty much crash 10d any and all times...
when I DELETE (Ctrl x) and then UNDO (Ctrl z) ,a few times or even once, with any video clip.... HDV or even old DV clips with or without FX's applied. This is getting real bad for me at least.

Windows 7 Pro 64bit

P.S. Still have Vegas 9e on this machine so I tried the same situation...NO PROBLEM AT ALL!

P.P.S. And it was the same problem back to 10b. All fresh installs of version 10 have the same UNDO problem for me.

Motherboard: ASRock TAICHI
Intel Z690 Chipset Cores:16
CPU: Intel Core i9 12900KS Enhanced Performance Processor
GPU: NVIDIA GeForce RTX 3090
RAM: 64GB DDR5-4800 MHz (2 - 32GB DIMMS
Disks: 2.0TB SSD NVMe/PCIe 3.0/4.0 M.2 Drive
SSD: (4) 4TB
O/S: Microsoft Windows 10 Professional 64-bit SP1

ritsmer wrote on 5/17/2011, 2:28 PM
10.0e 64 bit on Windows 7 Ultimate and with AVCHD full HD input: rock solid.

64 bit Windows + 64 bit Vegas seem to cure many of the strange issues seen before.
Remember i.e. the "Reds" ? - haven't seen one of the dreaded pink clips for a year now :- )

Edit @ SWS: just did 10 Ctrl+X and Ctrl+Z - but no problems here in 10.0e.
Mindmatter wrote on 5/17/2011, 2:31 PM
I have frequent crashes with mxf files,and ironically, according to the crash reports they are related to the sony mxf plugin. Never had those with 10c, and its the same files as in a larger project I worked on last year.

AMD Ryzen 9 5900X, 12x 3.7 GHz
32 GB DDR4-3200 MHz (2x16GB), Dual-Channel
NVIDIA GeForce RTX 3070, 8GB GDDR6, HDMI, DP, studio drivers
7.1 (8-chanel) Surround-Sound, Digital Audio, onboard
Samsung 970 EVO Plus 250GB, NVMe M.2 PCIe x4 SSD
be quiet! System Power 9 700W CM, 80+ Bronze, modular
2x WD red 6TB
2x Samsung 2TB SSD

Tim L wrote on 5/17/2011, 2:50 PM
Thanks for all the replies. I guess I should have added that I'm using Win 7 Pro 64-bit, and have only installed the 64-bit version of Vegas 10.0b at this point (on a new computer build from Dec. last year). HDV and DV only -- no MXF, no AVCHD, etc.

I'm a bit surprised at the mixed results reported here -- especially things that seemed to work fine in 10.c but cause problems in 10.d. I don't have any OFX plug-ins -- in fact I only have the plugins installed by Vegas at this point.

@ritsmer -- You say you are running 10.0e. Did you mean "d"? Or are you doing top-secret testing for SCS?

@JJKizak -- Are you saying that your blue-screens are Vegas -related on the Win7 PC? Or just that you're having crashes on a Win7 PC?

Thanks again, everybody. I may wait another day or two to see how this thread shapes up...
Woodenmike wrote on 5/17/2011, 4:28 PM
I'm still on XP 32bit and have had fewer problems with this last release, 10d...however, i'm still experiencing some funkiness when going between sound forge 10 and Vegas. In 10c, I would lose audio when going to Sound Forge and that issue has been fixed in, however, SOMETIMES when i go to Sound Forge, edit an audio clip and then go back into Vegas, vegas will lock up for a while and not play at all. It does come back after a minute or two, but there is definitely something processing from the trip back from Sound Forge.
farss wrote on 5/17/2011, 5:22 PM
On my WinXP 32 bit system with maxed out RAM V10.0d / 32 is still like editing while tip toeing on egg shells. V9.0e is WAY WAY more stable. The cause seems fairly obvious. V10 uses way more resources and can run out of them with ease. Taking steps to reduce the resources it needs helps a lot e.g. minimal number of thumbnails and dropping preview quality.

Testing V10.0d / 64 on my office PC which is running Win7 / 64 is a different experience despite the much slower CPU, the availability of the extra RAM makes a big difference.

I think SCS would have done themselves a favour by being upfront and not releasing a 32 bit version of V10 or at least warning users that they could expect a bumpy ride running the 32bit version under a 32bit OS.

xberk wrote on 5/17/2011, 7:42 PM
So far I've just cut one 7 min project on 10d .. no problems. Win7 64 bit.

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

ritsmer wrote on 5/18/2011, 1:46 AM
@ Tim L: Sorry, you are right - I meant "d" - and no: I am not among The Chosen Ones :- )
ushere wrote on 5/18/2011, 2:06 AM
so far so good 64bit - but i haven't really been pushing it to hard ;-)
Stereodesign wrote on 5/18/2011, 3:51 AM
Ok with me, 64 bit W7 and 64 bit Vegas 10d.

i7 2600k, 8gb RAM
JJKizak wrote on 5/18/2011, 4:27 AM
No problems with 10d but I do have problems with Win 7 on another computer not related to 10d.
Former user wrote on 5/18/2011, 8:24 AM
I had a project done in 10.0c that seemed to contain every element and circumstance that would induce instability. Running the same project in 10.0d has been an entirely different experience, so I'm much happier (and less tense) with 10.0d.

i7 920
Win7 x64
VP 10.0d x64
Seth wrote on 5/18/2011, 11:17 AM
So far so good. Quite pleased.
DonLandis wrote on 5/18/2011, 1:29 PM
There is a major bug in the use of MVC 3D clips imported from the Sony HDR TD10. It generates a crackling sound when importing DD5.1 clips in 3D. It is not triggered by excessive volume but only by an audio sound event. with pink noise it is constant. 2D clips DD5.1 it is not present and 3D clips with DD2.0 it is not present. The crackling distortion is not present on the clips when played outside Vegas. Only shows up in the Trim viewer and the timeline. When present it also stays and appears on all renders. I made an extensive report in this thread:

As in the past, I trust Sony will address this problem since presently the use of DD5.1 on 3D MVC clips in Vegas is unusable.
ingvarai wrote on 5/18/2011, 2:42 PM
Vegas 10 in general crashes so much for me that it is getting a problem. And every time I opt for sending the report to Sony, hopefully it will tell them something.
But I am not going to complain, yet. Vegas is very important to me, and it does its job. I have gotten used to Ctrl + S every other 10 seconds, to save my work.

It usually happens when going back and forth on the time line, playing a clip here, suddenly copying something and playing a clip another place. In general it happens when doing a lot of things as fast as the Windows user interface allows.
I have a SUPER fast computer, dual Xeon 5680 CPUs which means 24 cores all together, and I suspect it is too fast for Vegas. I need two instances of Vegas running in parallel rendering MPG to get the CPU usage gauge up at 90% on task manager.
Of course everything now is taking much less time than before, which is very nice. But Vegas crashes, very often, which is becoming more and more irritating.

Adobe After effects and all the other [heavy] multi media applications I use, like Cakewalk Sonar, Mocha etc. never crash, it is Vegas that does.
vtxrocketeer wrote on 5/18/2011, 8:20 PM
Ingvar, I'm afraid that something definitely is wrong with your computer. If you'd like to swap computers, just PM me. ;)
ingvarai wrote on 5/19/2011, 2:02 AM
>Ingvar, I'm afraid that something definitely is wrong with your computer. If you'd like to swap computers, just PM me. ;)

Hm.. maybe I will try to fix it :) It might also be something with the sound devices, I have an external sound card (breakout box) .

I built the computer myself:
EVGA Classified SR-2
I broke the bank, yes, but hopefully I do not need a new machine the first 4-5 years..
ushere wrote on 5/19/2011, 3:53 AM

all that and no onboard firewire?