New PC - No Solution

TDK wrote on 12/13/2019, 3:58 AM

Hi

I have been using Vegas since version 8. Recently I upgraded from Movie Studio to Vegas Pro 17.

My old laptop is a 2009 HP ProBook 450G1 MsWin7pro i5-4200M CPU @ 2.50GHz 16GBRAM SSD500G

My new laptop is a 2019 Razer Blade 15 MsWin10Pro i7-8750H CPU @ 2.20GHz 30GBRAM SSD1T

The reason I have bought a new laptop is that I've had some problems with rendering my 10-20min pfr100 HD Pro 17 projects. The laptop is also 10y old and its clock keeps on jumping to 1980 and the fan keeps a funny noise and a salesman in the computer shop said "any modern computer" would be better. Not much thinking I bought a second hand "modern" state of the art laptop thinking this would solve all my problems. Turns out it cant even play back the project for more than 2 seconds before crashing. I tried rendering over night but computer had crashed 20% into the process the next morning I looked. Just to be sure I loaded the exact same project onto my old computer and it previewed it perfectly without lag or crashing.

Are there any experts that could maybe pinpoint where the problem is located?

Thanks in advance, Tom

Here are more specs of my new laptop:

OS Name    Microsoft Windows 10 Pro
Version    10.0.18362 Build 18362
Other OS Description     Not Available
OS Manufacturer    Microsoft Corporation
System Name    DESKTOP-G4BS9DP
System Manufacturer    Razer
System Model    Blade
System Type    x64-based PC
System SKU    RZ09-02385N71
Processor    Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz, 2201 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date    Razer 1.05, 06/07/2018
SMBIOS Version    3.1
Embedded Controller Version    1.00
BIOS Mode    UEFI
BaseBoard Manufacturer    Razer
BaseBoard Product    C1_MB
BaseBoard Version    
Platform Role    Mobile
Secure Boot State    Off
PCR7 Configuration    Elevation Required to View
Windows Directory    C:\WINDOWS
System Directory    C:\WINDOWS\system32
Boot Device    \Device\HarddiskVolume2
Locale    United States
Hardware Abstraction Layer    Version = "10.0.18362.387"
User Name    DESKTOP-G4BS9DP\Tom
Time Zone    FLE Standard Time
Installed Physical Memory (RAM)    32,0 GB
Total Physical Memory    31,9 GB
Available Physical Memory    26,6 GB
Total Virtual Memory    36,9 GB
Available Virtual Memory    30,3 GB
Page File Space    5,00 GB
Page File    C:\pagefile.sys
Kernel DMA Protection    Off
Virtualization-based security    Not enabled
Device Encryption Support    Elevation Required to View
Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualization Enabled in Firmware    Yes
Hyper-V - Data Execution Protection    Yes
 

Comments

TDK wrote on 12/13/2019, 4:56 AM

Did some more testing this morning. Took my project and cut it to 10 seconds. Turns out the computer rendered it and while it was rendering I could use the computer as normal. My old computer became so slow that I could not use it at the same time it rendered. So maybe the entire projects rendering was unfulfilled last night because the computer put itself in sleep mode? I now changed the setting so that it does not ever go into sleep mode if its plugged into the wall socket. However, even though the project was 10 sec short I cannot preview it in the project. Pro 17 crashes after 2-3 seconds. Note that I loaded the Pro 17 version straight from the homepage yesterday thinking that would be the latest update.

TDK wrote on 12/13/2019, 5:15 AM

I think I have located the problem. As I started using the new computer I copied all my files from my old computer onto a external HD and then copied them to the new computer. As I opened up the project for the first time Pro17 could not find the media files. There was no option as to specify a new location for the files. Only 3 options. I had to locate every single media file separately. Thats a bumber because I have maybe up to 1000 files and it would take me a whole week just to do that for one project. I have 30 I'm working on. Even more. So I just checked "leave offline all files". Still the project loaded and everything seemed to be fine except for the preview functionality. Now I took a totally new project and loaded mediafiles physically to a dedicated folder, exactly as I always do with new projects. And the preview worked fine. Any thoughts?

j-v wrote on 12/13/2019, 5:24 AM

Any thoughts?

How should we?
You gave not the projecttype, sourcefiles, possible FX's a.s.o.
We know nothing where you store Vegas 17, your sourcefiles, your renderfile, rendertemplate, etc.

Last changed by j-v on 12/13/2019, 5:25 AM, changed a total of 1 times.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Dexcon wrote on 12/13/2019, 5:32 AM

As I opened up the project for the first time Pro17 could not find the media files. There was no option as to specify a new location for the files. Only 3 options. I had to locate every single media file separately.

@TDK ... Though I'm not sure it relates to your exact same circumstances, I have had something like that happen a few times particularly after changing a HDD (same drive number as before) and copying over all the media files in the same folder names to the new HDD. As I recall, the solution was to turn off and reboot the computer. Then, when re-opening the .veg project, the 'can't find media/4 options' dialogue box opened which then did allow 'nominate new media location' (or something like that) and then 'other media found in that folder, do you want to use' did appear, thus avoiding the one-by-one process.

 

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 19.0.3, 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

TDK wrote on 12/13/2019, 6:05 PM

Any thoughts?

How should we?
You gave not the projecttype, sourcefiles, possible FX's a.s.o.
We know nothing where you store Vegas 17, your sourcefiles, your renderfile, rendertemplate, etc.

I have Vegas Pro 17 installed on laptops HD and I have the project and all media files on the same HD.

TDK wrote on 12/13/2019, 6:06 PM

As I opened up the project for the first time Pro17 could not find the media files. There was no option as to specify a new location for the files. Only 3 options. I had to locate every single media file separately.

@TDK ... Though I'm not sure it relates to your exact same circumstances, I have had something like that happen a few times particularly after changing a HDD (same drive number as before) and copying over all the media files in the same folder names to the new HDD. As I recall, the solution was to turn off and reboot the computer. Then, when re-opening the .veg project, the 'can't find media/4 options' dialogue box opened which then did allow 'nominate new media location' (or something like that) and then 'other media found in that folder, do you want to use' did appear, thus avoiding the one-by-one process.

 

Ok, I have now reboted. Lets see what happens.

TDK wrote on 12/13/2019, 6:29 PM

I'm getting a bit frustrating. My 10y old laptop renders nicely. My new laptop crashes all the time. Just uninstalled the software and reinstalled. I also booted and had some win updates installed here in between. The software crashes again after just 2 seconds when on playback and does not render at all.

Musicvid wrote on 12/13/2019, 10:29 PM

There was no option as to specify a new location for the files. Only 3 options. 

Not true. Use the middle one:

"Specify a new location or replacement file."

When you've found one, you've found them all.

TDK wrote on 12/14/2019, 3:51 AM

Last night I put the exact same video to render on my old laptop that did not render on the new one and it rendered fine. Something strange here....

Dexcon wrote on 12/14/2019, 4:19 AM

@TDK ... I've just re-read your original post and just picked up on the fact that your newly purchased computer is a 2nd hand computer, not a new off-the-shelf computer. This raises a couple of questions. If it is a state-of-the-art computer (i.e. a recent build), I wonder if the original owner had problems with it as well? Do all your other apps and programs work without a problem on it? Has W10 been clean-installed after leaving the hands of the original owner? If no, then there may be some legacy issue with the W10 installation following the original owner's uninstallation of their apps/etc (and who knows what those apps may have been). And has the current W10 installation etc been thoroughly virus scanned?

If you are not sure about the provenance of the W10 installation particularly if you yourself did not do a clean W10 install after buying the computer, it may be worthwhile doing a clean install now and then see how Vegas Pro acts after doing that. Usually, there is a Recovery partition on the HD which allows for a clean re-install, or perhaps the computer came with a memory stick or the like to enable a clean re-install of W10.

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 19.0.3, 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

TDK wrote on 12/14/2019, 10:06 AM

Dexton - thank you for your thoughts. Yes, the new laptop is second hand. The guy said he was actually using Apple and he had tried a Window computer but that he went back to Apple. So evidently there was something wrong with this computer. He did a total reset with a new installation of W10. Yesterday it run some updates but it still crashes. Now when I come to think of it, it worked fine when I first started to use Pro17 with playback an all. Then it all of a sudden started to crash. BTW, just to test it I installed the Movie Studio 13 Platinum (best version of vegas as to this date). I had the same kind of problems with crashing at playback but now its rendering and it looks like ti will be the first successful render on this computer. Im gonna call the guy and ask him if he has any clue. Seemed like a nice honest guy.

j-v wrote on 12/14/2019, 10:23 AM

I have Vegas Pro 17 installed on laptops HD and I have the project and all media files on the same HD.

I there only one HDD?
That is not so goed when working with (sometimes heavy) videofiles, because there is only 1 proces that can read from it at the same time.
And also if you want to render the video it is not so good you have to render to the same HDD because of the former.
And if you have 1 HDD are there partitions with C:/ and ......???
Where is your pagefile stored?

 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

TDK wrote on 12/14/2019, 3:37 PM

j-v

So I should have the project on my C drive but render to another HD? Or should I have the project on another HD as well? I use external HD's for storidge but I thought that it would slow my computer down.

TDK wrote on 12/14/2019, 3:41 PM

Talked to the person who sold me the laptop. He said to be sure that the computer uses the state of the art graphics card and not the one supplied with the computer. I have now tried to find out what graphics card is being used but cannot find any place where graphics card can be chosen....

j-v wrote on 12/14/2019, 3:46 PM

No, Windows and Programs on C and further is it better to have the sourcefiles on other HDD's or at least on another partition if you have only one HDD.
Render is also better to another HDD.
My set up is working perfect, also on laptop with one SSD with a pretty small C partition of 125 GB and the other partition is for fast renders.
On the only other HDD I have more partitions for all Data, Pictures, Audio, Video and Windows backup, look

Last changed by j-v on 12/15/2019, 3:50 AM, changed a total of 1 times.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

TDK wrote on 12/14/2019, 6:04 PM

I just wrote a long testing report that got deleted as the page timed out without warning.... hmmmm.... something for the moderators to take note of.... as I have not had enough trouble already.

Anyway, I did 6 hours of testing today and documented it well. Now lost. Anyway, I also compared Movie Studio 13 Platinum to Vegas Pro 17 only to find out I could not make MS13P crash. The VP17 crashed every time. It seems that if I add any kind of effect to either the track or the video clips themselves VP17 crashes. I also tried to open the project from other HD as well but it only made every thing lag a lot and it crashed very quickly.

In the last test I took a brand new project and dropped a short 10 sec videoclip onto the timeline. I added a text track and start and end fade away's. Then I duplicated the video track 6 times and put it out of sync. Playback function worked fine. I did a quick render and the render was fine. Then I took and added a Sharpen effect to the first track. Everything worked well. Then I added a Sharpen effect to the second track and instantly VP17 crashed. This is odd. I never had this problem before. It seems that its the effects that makes the program crash. I dont think its a hardware problem or a V10 problem. I think it must be VP17.

Any developer on the watch here?

vkmast wrote on 12/14/2019, 7:06 PM

TDK wrote on 12/15/2019, 2:04 AM

I just wrote a long testing report that got deleted as the page timed out without warning.... hmmmm.... something for the moderators to take note of...

Unfortunately this happens, even to moderators. This has been reported previously and was most recently discussed on the Forum Auto Time Out / Log Out? thread. It has some suggestions to avoid losing your posts/comments. I usually copy and paste a back-up somewhere before clicking to send Comment or Post.

TheRhino wrote on 12/15/2019, 8:22 AM

Vegas renders can make laptops heat-up but good gaming laptops, like the Razer Blade 15, are designed to NOT overheat. IMO you should install the latest GPU driver from Nvidia vs. the one Windows automatically installs. Then, you can try installing the latest drivers from Razer vs. the ones Windows automatically installed. Set the Razer to run in "performance" mode making sure it is plugged-in to power supply. After that, try copying your video files to an external USB 3.0, then redirect your OLD computer to use those files (be renaming the original folders on the old computer so Vegas searches for the location on the USB 3.0 instead...). If the old computer is fine with the new location of the video files, then your new computer should be able to use them just as well...

If none of this works, see if he will take the laptop back & refund your money... Even Apple folks will keep their Razer for gaming because no Apple runs games as well... There have been a LOT of great deals on NEW laptops from Black Friday all the way until now. Not as good as a Razer, but I bought a Walmart "Evoo" brand 17" laptop with 144 Hz screen, i7-9750H 6-core cpu, and RTX 2060 GPU for $999. It came with a 1TB M.2 drive, slot for another M.2 drive, and an empty SSD bay & I added a 3 year protection plan for just $88 more. Even though "Evoo" is an off-brand the laptop designed around a popular chassis used by many high quality vendors. Therefore replacement parts are readily available & the cheaper 3 year protection plan makes it a no-brainer... (I also bought a HP Omen with Thunderbolt 3 for $900 but I like having 3 drives onboard vs. only 2...

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

Musicvid wrote on 12/15/2019, 9:01 AM

I like your Youtube Channel!

Some random thoughts here:

-- On a used computer, guys will have often loaded it up with mismatched RAM. Has been causing problems back to the stone ages.

-- Post your file properties for one of the renders that is taking forever or crashing intermittently. Both source and output properties, please.

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

-- Try turning off WIFI during editing and rendering. I just discovered that anytime my Wifi gets knocked offline, it does nasty things to whatever I am doing, including Vegas and Photoshop. Onboard Qualcom NIC here. A USB wifi adaptor does not seem to have the problem.

-- Are your external drives USB2 or USB3?

-- Clean all the dust bunnies from your fins. vents, and fans.

-- (Aside) Guys often put extra heat sink compound on their desktop CPUs, thinking it will "help." We were all stupid once. The ideal heat sink is a uniform layer 1 molecule thick.

-- You may have bought a used lemon. Did the seller stumble when you asked him "why" he was selling the computer?

TDK wrote on 12/18/2019, 4:25 PM

I finally found the problem. And the solution. It was my graphics card that was not installed properly. When the previous owner reinstalled W10 it somehow messed up the GC settings. I had to reinstall a new driver and that solved all the problems in Vegas I was experiencing. The former owner was very helpful. BTW, this laptop is like a whole new world. I can even edit in Vegas at the same time it is rendering an other project. Its fast and the picture is sharp and everything is just great. Except for this keyboard. I guess its because GAMERS have no need for a keyboard.

TDK wrote on 1/29/2020, 6:44 PM

Not long did my strike last... tomorrow I will take it to store and get the W10 reinstalled and then re-built from there, one peace at a time.

TDK wrote on 1/30/2020, 3:48 AM

Anybody else here using Vegas Pro with a laptop?

TDK wrote on 1/31/2020, 4:00 PM

UPDATE 2020013123:55

I have now re-setted the RazerBlade. New W10 and all drivers updated at a computer shop. Cost me a hundred bucks + expenses + TIME. But the Razer got a clean start. I downloaded VP17E (Build 387) and open a project from an external HD but the VP17E keeps on crashing like before so the reinstallation of W10 and drivers and VP17E did not help. So I download the old VegasMovieStudio13Platinum to the Razer and took an old project and massively duplicated all tracks for a really heavy project. Let's call it AMANDA. In VMS13P it played back nicely. Loaded AMANDA into VP17E and it crashed straight away in a matter of seconds. Next, I took AMANDA back to my old HP450 and it played nicely on the VP17E (Build 321) in the preview window. Any other VP17E project played nicely in the preview window. One more test. I downloaded VMS16P onto the Razer and tried AMANDA. Worked great.

In order to find out if the problem is build 387 of VP17E I decided to go and check if I could get an upgrade of some other Pro version. I go over to the site to find out that an upgrade to the VP17 would cost 249USD but there was a free trial version available. I uninstalled my VP17E and installed the new VP17 trial version. It asked my serial number, which it had there pre-entered, and I clicked next and got the program started. But it seems to be crashing again. Maybe I did not get the free trial version at all? New try. Interestingly enough I cannot install a free trial version on my computer. It asks for my serial number. If I don’t enter it I cannot go further. If I enter it, the free trial version is not an option any more. So if Vegas is wondering why nobody downloads any trial versions look no further.

Anyway, let’s see if I can take build 321 from my old HP and install it on the RazerBlade. Nope, did not work. Only build 387 available on the HP even if its build 321 that is installed.

What have I learned:

Vegas Pro 17 build 387 is not compatible with my Razer Blade but Movie Studio Platinum versions 13 and 16 are.

Vegas Pro 17 build 321 and Movie Studio Platinum versions 13 and 16 are compatible with my HP 450.

Conclusion:

Vegas Pro 17 build 387 has a bug, or

Vegas Pro 17 is not compatible with the Razer Blade for some unknown reason, or

Vegas Pro 17 build 387 needs to have some parameters set, or

Razer Blade needs to have some parameters set, or any combination of above or something completely different!

Any thoughts? Something I have overlooked?

Tom