Using Sony Vegas Pro 13.0 on 4K UHD monitors?

Alexander Vasilchenko wrote on 7/24/2015, 4:05 PM

I use Sony Vegas Pro 13.0 ona Dell XPS 15 with 4K display. All work perfect so far but Vegas interface has very tiny icons in 4K resolution...

All Windows 8 display scaling features did not help - they allow to enlarge some Vegas GUI elements but not icons. Is there any solution for this issue? Maybe an unofficial patch? A custom icons set? I have asked Sony Vegas support but they not really helpful....

My Sony Vegas is Version 13.0 (Build 453)

Thank you!


ritsmer wrote on 7/26/2015, 8:49 AM
If nothing else helps you can change the resolution of the screen to lower values than 4K while using Vegas.

Planning for a new main editing monitor larger than my 30" 2560x1600 I have been contemplating 4K monitors too - but as the scaling can be a problem - as you have experienced - I now have finally decided for a Philips 40" monitor with a native resolution of 3,840 x 2,160.
This gives approximately the same pixel size as I have now - so I look forward to / hope that such a monitor will be comfortable to work with.
Alexander Vasilchenko wrote on 7/27/2015, 2:36 PM
Neither one Windows scaling workaround did work well for me...Some Sony Vegas GUI elements were scaled OK, but NOT toolbar icons. Hacking an application I've paid 500 bucks is kinda gross :) However, I've escalated and got this response from Vegas support:

Hi Alexander,

Thank you for contacting Sony Creative Software.
We were able to reproduce the issue in house and it has been escalated to development.
I will be setting this incident to Development status in the meantime, and I will update it as soon as I have further information. Thank you for your patience while we continue to research this matter.
wwjd wrote on 7/27/2015, 5:51 PM
I bought new "Readers" glasses to help 4K Vegas :)
ShawnKlein wrote on 1/12/2016, 1:56 PM
Hi Alexander,

Well it's 2016 and I'm still having the same problems as you on my XPS 15.

Did you ever find a viable solution or hear anything more from Sony on when this might be resolved.

Lucius Snow wrote on 2/8/2016, 9:34 AM
Same problem here (:
rcarlton wrote on 7/31/2016, 9:36 PM
Kit wrote on 8/1/2016, 2:04 AM
I appreciate that scaling in Windows is woeful but it's a poor job that Vegas doesn't offer different sizes of icons. I'Ve been stuck with editing on a laptop the last view days and not only are the buttons small but the contrast is so bad I often can't tell if some settings are active or not. A real headache with the ripple button.
rcarlton wrote on 8/2/2016, 6:05 PM
I wonder if Magix will elevate this issue and have it solved for version 14? Hint, hint.
Tim L wrote on 8/2/2016, 8:03 PM
As mentioned previously on this forum, Sony was very close to releasing Vegas 14 earlier this spring. Artwork and information had been sent to websites, and product listings were popping up all over the web. Those pages were then removed and the Vegas 14 release went dark until the MAGIX deal was announced.

The information I found on a page (Google cached copy) indicated that VP14 was supposed to now have support for high DPI monitors:

[I]Vegas Pro 14 Edit delivers pure Vegas Pro core technology in a cost-effective package. New features include smart restoration and upscale features, interoperability with HitFilm 4 Pro, new plug-ins by Sony, and NewBlueFX, new hardware support for High DPI monitors, Blackmagic, AJA SDI devices and RED cameras, and application wide performance improvements. Vegas Pro 14 Edit offers more formats, supports more workflows, and provides the tools for more creative control than ever before.[/I]

NOTE: These were features of the almost-released Sony version of Vegas 14. It is not clear whether the above-mentioned 3rd party features will still be part of the MAGIX release this fall.
monoparadox wrote on 8/3/2016, 5:39 PM
Alexander, I was having the same issue with Photoshop and ran across this solution:

If one could figure out the manifest file for Vegas I would think it might accomplish the same result. Hopefully, at least a clue to get you going down the road to a solution.

-- tom
Allegretto wrote on 8/4/2016, 2:55 PM
Appears the manifest is in the executable. I looked at the VP 12 executable named vegas120.exe. I opened it in Notepad++ which handles everything much better than the standard notepad. Then I searched for some of the text in manifest.txt that was included in that link from tom (e.g. Microsoft.Windows.Common-Controls) and found it.

That should help you get farther along. Keep us posted if you can get it to work.