Blast from the past! (Vegas 12 Window problem)

Arthur.S wrote on 12/3/2019, 1:10 PM

Many moons since I last posted here, but here I am hoping one of you gurus can offer some advice to this problem. This is actually a problem that my Dad (88 years young) is having (and hence me :-) ). When starting Vegas 12 the start up window jumps to the left and becomes smaller then jumps back to the middle, but remains smaller. It then finishes starting but opens with a small window/workspace. Even selecting a saved Window layout doesn't correct it. Has to be manually set up to his normal layout. OK, not the end of the world, but opening ProType Titler for instance shows TWO work spaces of it (the titler) both in the same window! Which makes it impossible to use. I have never seen anything like this in all the years I've been using Vegas (from version 6).

Things I've tried so far;

Resetting Vegas to default (shift+ctrl on startup)

Complete clean re-install (removal of all Sony vegas related items in the registry and in Windows explorer).

Installed an older version (11). This fixed the problem at first, but on the next restart of Vegas the problem returned. I then tried Vegas 9. Same problem.

I don't have the option of installing a newer version than 12. I should add that both his and my versions of Vegas are running on Windows 10 with the latest updates. No problems whatsoever with mine. Wondering if a Windows update on his PC has messed something up? Any ideas will be gratefully accepted!

Comments

j-v wrote on 12/3/2019, 2:13 PM

Because those old versions are not good to use with the modern Windows 10, I think it will be the best for you to uninstall everything very good and than rightclick on the install file and choose properties/comtability modes and than choose the Windows version for that Vegas version was made. Install it as Administrator.
I have on one of my desktops all versions good running that way from Vegas Pro 10-16.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 23H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
522.22 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2127
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 522.22 and Intel UHD Graphics 630 with driver 31.0.101.2127
Vegas software: VP 10 to 21 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)

 

rraud wrote on 12/3/2019, 4:15 PM

As j-v suggested, I would experiment with the compatibility settings and enable or disable the high DPI option. Right-click the VP <.exe> file or shortcut and select "Properties> Compatibility"

fifonik wrote on 12/3/2019, 4:32 PM

Can you show screenshot?

Have you tried to Right Click to title bar and Maximize and then Right Click and Restore?

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

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 5700X, RAM: G'Skill 16 GB DDR4@3200, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), Samsung 870 Evo, HDD WD 4TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

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

Former user wrote on 12/3/2019, 5:01 PM

I use Version 12 with Windows 10 without making any compability adjustments. This sounds like a video card driver problem, not a Vegas problem.

Arthur.S wrote on 12/4/2019, 9:55 AM

Thanks to all for your suggestions. Should have mentioned that I did install as administrator and also used the Windows compatibility tool. This PC is my old editing rig that I passed on to my Dad when I updated mine about 3 years ago. I left all the software on it and Vegas 12 was working perfectly then. He used it briefly then but has had no reason to since. So my money is on either a Windows update, and/or a display driver as suggested above. When I was using it to make a living, I kept this PC off line and update free but Dad is using it as a general workhorse so can't do that. I'll delve into rolling back the display drivers and Win10 updates the next time I'm seeing him, but it may be too late now (if it's a 2 year old update for instance). I'll report back here afterwards.

Thanks again all!

Arthur.S wrote on 12/4/2019, 9:57 AM

I'll also post a screenshot here if I can't fix it.

Arthur.S wrote on 12/5/2019, 6:25 AM

OK, so all suggestions tried. I rolled the display drivers back to last update (2016!) Did another clean install as Administrator and using Win 7 compatibility mode, but no success. I've attached a video showing the problem. Not great quality as done using a Remote connection. Also note the oddness of the 'File, Edit, View, menu at top left. http://vimeo.com/377531528

j-v wrote on 12/5/2019, 7:02 AM

The oddness you mention I have to check on my desktop with Vegas 12, later this day, but I think for your problem with the ProType Titler you have to enlarge that PTT Window by dragging>>> look

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 23H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
522.22 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2127
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 522.22 and Intel UHD Graphics 630 with driver 31.0.101.2127
Vegas software: VP 10 to 21 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)

 

Arthur.S wrote on 12/5/2019, 1:00 PM

Yes J-V, but there are 2 workspaces - you can see 2 x zoom tools. Also look at the File/edit/view et menus etc on the top left of the Vegas screen. Part of the wording is missing.

Arthur.S wrote on 12/6/2019, 6:16 AM

OK, problem sol-ved (in my best inspector Clouseau voice). I went back to Win 95 basics and Deleted the graphics card in device manager and let Win 10 reinstall it. That sorted it. Thanks to you all for taking the time to offer advice.