what computer?

j.j. wrote on 10/16/2019, 11:47 AM

I purchased Vegas Pro 17 and found out it doesn't work on my computer.

I have a Windows 7, 2nd gen i7 with motherboard which is not W10 compatible, and of course DDR3 RAM. So I need to upgrade.

I have read the system requirements listed on the sonycreativesoftware site: 8th gen i7, Windows 10, at least 16GB DDR4. Later I read about the necessity of a QSV board, iGPU and 2666 RAM. Now I'm lost.

 

Can anyone just tell me which board, processor type (i9-9700K or H, or G?), graphics card (in addition to QSV still a Nvidia GX 2080 or 1660/1660i?), drives et cetera precisely I should get? I'd like to stop worrying and start editing.

 

Thanks.

Comments

john_dennis wrote on 10/16/2019, 12:05 PM

"sonycreativesoftware site"

Update your knowledge of the company that owns Vegas Pro software first.

TheDingo wrote on 10/16/2019, 1:55 PM

If you check the current Vegas Pro website ( https://www.vegascreativesoftware.com/us/newsletter/upgrade-vegas-pro/specifications/ ) you will see the current system requirements listed.

Operating system: Microsoft® Windows 10 (64-bit)

Processor: 6th Generation Intel Core i5 (or AMD equivalent) or better. 2.5 Ghz and 4 Core minimum. For 4k, 7th Generation Intel Core i7 (or AMD equivalent) or better. 3.0 Ghz and 8 Core minimum

RAM: 8 GB RAM minimum (16 GB recommended; 32 GB recommended for 4K)

Hard drive space: 1.5 GB hard-disk space for program installation; Solid-state disk (SSD) or high-speed multi-disk RAID for 4K media

Other: Microsoft .NET Framework 4.0 SP1 (included on application disc)

...From a performance perspective you might want to go with a new AMD Ryzen 3000 CPU and a good AMD 570 motherboard. AMD has next generation ThreadRipper CPUs coming out in November that will also include a 16 core consumer CPU along with a 64 core ThreadRipper CPU.

Musicvid wrote on 10/16/2019, 2:24 PM

What about your system is not Win 10 compatible?

I have Win 10 and Vegas Pro running on a far more modest system than that -- a Core Duo notebook.

j.j. wrote on 10/16/2019, 2:39 PM

As I said, I found the current system requirements on the Vegas Pro website. No mention of QSV, iGPU and type of ram. On the techgage site they state that AMD cpu's do not offer this capability. It's not difficult to find a list of cpu's that do. But there are several. The problem is the integration of the supposedly necessary components. What works together and what doesn't? What creates the best system for the money for running SVP17?

I can buy the fastest components that comply with the listed system requirements, and still end up with a system that doesn't run Vegas Pro efficiently. Therefor my question.

After I installed Windows 10 on my computer, I couldn't play sound through a sound card I had purchased just a few months ago. I contacted Asus about this. They said my motherboard didn't support Windows 10. I can run Vegas Pro 17. But without sound or the right drivers for the main board, as well as a cpu that is six generations too old, I think it is a lost cause to try and get the old system running SVP17.

fifonik wrote on 10/16/2019, 4:17 PM
After I installed Windows 10 on my computer, I couldn't play sound through a sound card I had purchased just a few months ago. I contacted Asus about this. They said my motherboard didn't support Windows 10.

I think they are wrong. What is your MB model name?

You should be able to fix your sound issue by installing correct audio driver manually or using some kind of driver installer program (such as Driver Easy, Driver Max or similar). Even Windows 10 troubleshooter might be able to fix the issue.

If for some unknown reason this does not work, it would be much cheaper and easier just buy separate sound card then replace PC. IMHO.

 

P.S. QSV is not mandatory. It is nice to have if you do not have discrete GPU. So AMD CPUs are fine (I'm using Vegas on PC with AMD CPUs long time).

Last changed by fifonik on 10/16/2019, 4:19 PM, changed a total of 1 times.

Camcorder: Panasonic X1500 + Panasonic X920 + GoPro Hero 11 Black

Desktop: MB: MSI B650P, CPU: AMD Ryzen 9700X, RAM: G'Skill 32 GB DDR5@6000, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), HDD WD 4TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17, 18, 19, 22

Author of FFMetrics and FFBitrateViewer

Former user wrote on 10/16/2019, 7:04 PM
 

P.S. QSV is not mandatory. It is nice to have if you do not have discrete GPU. So AMD CPUs are fine (I'm using Vegas on PC with AMD CPUs long time).

You would want correct combination as AMD hardware decode doesn't work. Intel cpu with either AMD or Nvidia GPU, or AMD cpu with Nvidia GPU, BUT NOT Amd CPU and Amd GPU. Also there's the hardware encode consideration, Nvidia Nvenc is the superior encoder & AMD hardware encode either doesn't work or low quality on most recent AMD GPU's (if not true please correct amd gpu enthusiasts)

wjauch wrote on 10/16/2019, 7:56 PM

FWIW I have Win 10 Pro running for several years on many work Dell PCs, about 10 years old with CoreDuo E7500 CPU, only recently upgraded from 2GB to 4GB RAM, RAM is DDR2. Win 10 will run on a far more modest system than yours, but as someone else posted above you may need a driver or to add an external sound card.

zdogg wrote on 10/16/2019, 9:11 PM

You can run it on Win 7 and will work just fine. Some very few third party things sold by Vegas, (Vegas Post) specifically Vegas Image ( FXHome Emerge) won't run on Win 7, which is their Photoshop like app, but other than that, you can, and maybe should, unless you are OK with the intrusiveness of Win 10, which I am not, elaborate workaround/mitigation schemes aside.

Just run it, if you don't like it, you can always try win 10, and you can go back again, (at least that was available at one time) - I did that myself, and get back to sanity, erh, I mean Win 7.....(you may detect a certain disdain for OS that mines your information shamelessly and locks you out, like a child, of any easy "tweaking" opportunities.

 

j.j. wrote on 10/17/2019, 2:21 AM

I installed Vegas 17 on under Windows 7 first, but it just wouldn't run. When I switched to Windows 10 and installed again, it ran fine. So why won't it run with Windows 7?

In the past I have always had issues with Vegas (latest version used is Pro12). Problems with playback/preview, rendering and sound. I disabled gpu per advice given here, which did improve things. But I'm worried that I'll have more problems using Vegas Pro 17 on my existing system, making it unuseable.

My mb is Asus P8P67LE. I contacted Asus about this. They say it is not compatible with Windows 10, there are no drivers for it, and the only solution would be to buy another mb.

 

zdogg wrote on 10/17/2019, 2:26 AM

 

My mb is Asus P8P67LE. I contacted Asus about this. They say it is not compatible with Windows 10, there are no drivers for it, and the only solution would be to buy another mb.

 

Upgrade your system, it's long in the tooth. It will, I'm sure run with Win 7, though 10 may work better, I don't know, some people are ok with it....I HATE windows 10, with a purple passion, though some say there are workarounds, and back door fixes to tame that rude beast, but that's above my pay grade.

Anyway, your beating a dead horse with your gear, if you can afford a better machine, that is the key, not the OS , or not as much, imho.

j.j. wrote on 10/17/2019, 2:42 AM

Hi zdogg

 

Thanks for your remarks. Okay, a new system is possible. I would much rather keep using Windows 7. Trouble is that after installing Vegas Pro 17 on it, it wouldn't run. I exchanged the Windows 7 ssd with one running Windows 10, again installed Vegas Pro 17 on it, and it did run. I haven't used it much yet, but Vegas works.

Would you have any idea why my installation under Windows 7 won't work?

 

Greetz

J.J.

fifonik wrote on 10/17/2019, 5:29 AM

More details needed to find out what's wrong with your Win7 installation. Most probably NET framework is missing. You will need to check Vegas installation FAQ.

As for your sound issue under Win10:

Based on specs, it has Realtek® ALC892 audio chip. This chip is used on many modern moderboards (I do have the same chip in my MB). It is supported by Windows 10 from the box and should not require any driver from manufacturer.

However, the issue might be that you are not connected your speakers/headphones into proper ports. Old Realtek audio drivers gives you ability to re-task audio jacks. New drivers (including one that is supplied with Win 10) do not. So you should double check in which socket you are connecting speakers (usually it should be green one). Alternatively, you can install old Realtek audio driver (R281) where the re-tasking is still available. Install it, reboot, disconnect speakers, re-connect speakers, you will see notification what you are connecting, choose speakers.

Last changed by fifonik on 10/17/2019, 5:31 AM, changed a total of 1 times.

Camcorder: Panasonic X1500 + Panasonic X920 + GoPro Hero 11 Black

Desktop: MB: MSI B650P, CPU: AMD Ryzen 9700X, RAM: G'Skill 32 GB DDR5@6000, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), HDD WD 4TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17, 18, 19, 22

Author of FFMetrics and FFBitrateViewer

j.j. wrote on 10/17/2019, 5:52 AM

Hi fifonik

Thanks for your elaborate reply. I will try and check for .NET framework.

The trouble with sound was that it was way too loud from the Asus Xonar soundcard. Even with volume up a tiny bit, the sound was heavily distorted. In the days of analog sound this would indicate a line signal on a microphone of phono input. There is sound, but it is horrable. So I did have the right connector (I did check the other ones), but it just was unusable.

 

Dexcon wrote on 10/17/2019, 6:17 AM

@j.j.

After I installed Windows 10 on my computer, I couldn't play sound through a sound card

Though my Creative soundcard is some years old, I did find that one of the W10 major updates (perhaps March this year) totally killed sound through my editing computer. Ditto with a very new Dell laptop with an on-board soundcard.

In both cases, I had to update the drivers for the sound cards which were readily available from Creative and Dell respectively, and the problem was solved in both cases. While this might not apply to your situation, I only provide it as a possibility.

Re the distortion you are now getting, it does seem very much like the analogue days (e.g. put a 240k resistor in line - or something like that - seemed to work well enough in the late 60s); however, I have not encountered this in the digital age.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

zdogg wrote on 10/17/2019, 9:24 AM

There are (at least) two or three sound "sources" that can comprise a "too loud" issue. Read whatever pdf manual that comes with your Creative card, or search online for that, for starters,

there is the Windows sound mixer, usually you can find in the Win 7 task bar in the lower right, right click speaker Icon, click "playback devices" find your device, and/or "speakers" and there is a "configure" button and you have a testing/adjust mechanism, or alternatively, look for advanced settings on that page or sub menu page.
Ok, so that is One,

You can also access Windows sound in the Control Panel under, guess what? "Sound" (speaker Icon)

#2 you want to check your levels inside Vegas, on the track, so track volume,
#3 on the event, event volume (there is a pull down adjust handle on each audio event.)
#4 the Mixer out, Master volume.
and sometimes there is a bus, with its own volume control, the track feeds before master out, (but not usually, unless you set that up).

And these all compile, so, watch each volume level at each stage. (this oversight is called "gain staging" )



 

walter-i. wrote on 10/17/2019, 11:29 AM

For me VP 11, 12,13,14,15 works flawlessly under WIN 7 - but the test version of VP 17 crashes constantly.

See also:
https://www.vegascreativesoftware.info/us/forum/will-gtx-750ti-work-with-vegas-pro17--117285/#ca730950

 

zdogg wrote on 10/17/2019, 11:53 AM

Yes, but that is not necessarily an OS issue, Pro 17 has been buggy as hell and a lot of people are having crashes, and most are running Win 10. I have it running fairly stable on Win 7. I can run for hours with no crashes, but it will crash, but it is usually a Black Magic card issue or the OFX problems with third party stuff, especially, which is really not the OS.

fifonik wrote on 10/17/2019, 6:36 PM

> After I installed Windows 10 on my computer, I couldn't play sound through a sound card I had purchased just a few months ago. I contacted Asus about this. They said my motherboard didn't support Windows 10. I can run Vegas Pro 17. But without sound or

> The trouble with sound was that it was way too loud from the Asus Xonar soundcard.

Mate, you should explain things better.

You claimed that your MB is not supported and you have "no sound" issue.

Then it turned out that your real issue nothing to do with MB and it is with discrete sound card that is supported (you can download driver for the sound card from Asus web site).

After quick reading I'm almost certain that the issue is with build-in amplifier and will be fixed by installing manufacturer driver.

Camcorder: Panasonic X1500 + Panasonic X920 + GoPro Hero 11 Black

Desktop: MB: MSI B650P, CPU: AMD Ryzen 9700X, RAM: G'Skill 32 GB DDR5@6000, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), HDD WD 4TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17, 18, 19, 22

Author of FFMetrics and FFBitrateViewer

j.j. wrote on 10/18/2019, 6:17 AM

Hi fifonik,

 

I'm sorry I haven't been clear enough. I installed the Asus Xonar soundcard driver several times, but never got acceptable sound from it. So I contacted Asus support. They asked me what mb I had. This, as it happens, is an Asus also. They told me the problem wasn't with the soundcard or its drivers, but with the mb for which there is no Windows 10 support or driver available....so they told me. All this is entirely their conclusion. I thought originally that it was just the soundcard. So I removed the card and driver and reinstalled them (the driver several times actually), always checking I had the correct and newest one. I also tried to install mb drivers for Windows 8 (that's as far as they go for this mb on Asus' site), hoping that the difference with Windows 10 would be inconsequential. Alas none of this was helpful.

From this I think I can safely conclude that it is not a soundcard driver problem. It seems to be a mb driver problem, But that's just what they tell me. And a solution to it I don't have.

 

TheRhino wrote on 10/19/2019, 8:38 AM

Your BEST bet is to do a Google search for hardware forums discussing your motherboard, sound card, etc.  Folks on those forums will have already discussed how they got a specific piece of hardware to work with Windows 10. If all of your hardware, sound, etc. is working in Windows 10, then Vegas 17 will run on it, just slower than more modern systems...

Motherboard, PCIe sound card, etc. manufacturers eventually stop providing driver updates for older products & therefore state that their old hardware no longer "supports" a new OS, like Windows 10. This does NOT mean that you cannot get it to work with Windows 10, they are just refusing to spend R&D money & time to develop updated drivers for legacy hardware. In some cases, Windows 10 provides its own driver set for older products. When this does not work, for some legacy products I have been able to use the Windows 7 64 drivers successfully within Windows 10. Currently I have 10 year-old ASUS P6T6 workstation class motherboards & 1st generation I7 & Xeons running Windows 10, Vegas 17, etc. I often complete smaller jobs on my older workstations while my newer 9900K is rendering-out multiple file types @ 100% cpu usage....

Workstation C with $600 USD of upgrades in April, 2021
--$360 11700K @ 5.0ghz
--$200 ASRock W480 Creator (onboard 10G net, TB3, etc.)
Borrowed from my 9900K until prices drop:
--32GB of G.Skill DDR4 3200 ($100 on Black Friday...)
Reused from same Tower Case that housed the Xeon:
--Used VEGA 56 GPU ($200 on eBay before mining craze...)
--Noctua Cooler, 750W PSU, OS SSD, LSI RAID Controller, SATAs, etc.

Performs VERY close to my overclocked 9900K (below), but at stock settings with no tweaking...

Workstation D with $1,350 USD of upgrades in April, 2019
--$500 9900K @ 5.0ghz
--$140 Corsair H150i liquid cooling with 360mm radiator (3 fans)
--$200 open box Asus Z390 WS (PLX chip manages 4/5 PCIe slots)
--$160 32GB of G.Skill DDR4 3000 (added another 32GB later...)
--$350 refurbished, but like-new Radeon Vega 64 LQ (liquid cooled)

Renders Vegas11 "Red Car Test" (AMD VCE) in 13s when clocked at 4.9 ghz
(note: BOTH onboard Intel & Vega64 show utilization during QSV & VCE renders...)

Source Video1 = 4TB RAID0--(2) 2TB M.2 on motherboard in RAID0
Source Video2 = 4TB RAID0--(2) 2TB M.2 (1) via U.2 adapter & (1) on separate PCIe card
Target Video1 = 32TB RAID0--(4) 8TB SATA hot-swap drives on PCIe RAID card with backups elsewhere

10G Network using used $30 Mellanox2 Adapters & Qnap QSW-M408-2C 10G Switch
Copy of Work Files, Source & Output Video, OS Images on QNAP 653b NAS with (6) 14TB WD RED
Blackmagic Decklink PCie card for capturing from tape, etc.
(2) internal BR Burners connected via USB 3.0 to SATA adapters
Old Cooler Master CM Stacker ATX case with (13) 5.25" front drive-bays holds & cools everything.

Workstations A & B are the 2 remaining 6-core 4.0ghz Xeon 5660 or I7 980x on Asus P6T6 motherboards.

$999 Walmart Evoo 17 Laptop with I7-9750H 6-core CPU, RTX 2060, (2) M.2 bays & (1) SSD bay...

fifonik wrote on 10/19/2019, 5:28 PM

I'd try:

- Use integrated audio to check if this works.

- Install Intel Driver & Support Assistant and allow it to find and install the most recent MB chipset drivers.

- As already suggested, install Driver Easy / Driver Max (free versions will work with some limitations) and allow them to install SOUND DRIVER ONLY.

- If above did not help, I'd start to google as TheRhino suggested :)

P.S. Have you tried to install fresh W10 or upgrade over your copy of W7?

Last changed by fifonik on 10/19/2019, 5:29 PM, changed a total of 1 times.

Camcorder: Panasonic X1500 + Panasonic X920 + GoPro Hero 11 Black

Desktop: MB: MSI B650P, CPU: AMD Ryzen 9700X, RAM: G'Skill 32 GB DDR5@6000, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), HDD WD 4TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17, 18, 19, 22

Author of FFMetrics and FFBitrateViewer

j.j. wrote on 10/20/2019, 3:09 AM

Thanks a lot, everybody. You've made some excellent points.

A good friend of mine heard of my trouble and bought a brand new system for me to use !

Awaiting that, I'll be updating the edit room to accommodate extra monitors.

 

Thanks again.

J.J.