Edit Visible Button Set

imaginACTION_films wrote on 10/1/2021, 1:43 AM

I understand this has been discussed already but I have a suggestion for the developers. I know I can click on the 'hamburger' in the track header and then select Edit Visible Button Set. But I find it wastes time to do this with every new project, because I like the complete button set to be there all the time.

Suggestion: Could you add this as an item in general Preferences, eg "Always make all track header buttons visible".

That way button nerds like me will always be happy, and those prefer button free-headers can choose that option.

Just a thought...😎

Comments

RogerS wrote on 10/1/2021, 1:46 AM

Can't you save the track defaults to whichever buttons you like? I do that to add Fx and track motion but not the other ones I don't use.

vkmast wrote on 10/1/2021, 1:57 AM

I "specify the controls" that I want and "Save Layout As...".

3POINT wrote on 10/1/2021, 4:02 AM

I "specify the controls" that I want and "Save Layout As...".

AFAIK there's no need to save as a layout, the changes you made to the visibility of the buttons with the hamburger menu(s) are saved on closure of Vegas. This layout shows up when you start Vegas next time.

VEGASDerek wrote on 10/1/2021, 6:11 AM

I understand this has been discussed already but I have a suggestion for the developers. I know I can click on the 'hamburger' in the track header and then select Edit Visible Button Set. But I find it wastes time to do this with every new project, because I like the complete button set to be there all the time.

Suggestion: Could you add this as an item in general Preferences, eg "Always make all track header buttons visible".

That way button nerds like me will always be happy, and those prefer button free-headers can choose that option.

Just a thought...😎

The button configuration should not reset every time you start a new project. It is a state of the application interface and, as previously said, is stored as part of a layout. If you are having problems with the buttons continuously being reset, this would be a bug and it would probably help us to get some more details on your system.

Roger Bansemer wrote on 7/5/2022, 6:57 AM

The "Edit visible button set" does NOT show up when I reopen a project that had the buttons set to visible. Why don't those buttons stick to a project that had them on there?

Former user wrote on 7/5/2022, 11:49 AM

@imaginACTION_films Hi, as @VEGASDerek & @3POINT say the visible buttons that are open are the ones still open when i launch Vegas the next time, I have all visible, @Roger Bansemer the little dots "Edit visible button set" disappear from the track header if the track is reduced in size, can you post a screenshot of how yours looks?

Reyfox wrote on 7/5/2022, 12:02 PM

+1

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Roger Bansemer wrote on 7/5/2022, 1:00 PM

jetdv wrote on 7/5/2022, 1:08 PM

My recommendation:

Open VEGAS, change the buttons to be the way you want them, Close VEGAS.

Now open VEGAS again and the buttons should remain and you will not have to worry about this issue again.

I've seen this happen if I've changed a button and I didn't exit VEGAS (perhaps it crashed, perhaps I opened another instance later and it was closed later, for whatever reason it was not closed to save the changes)

Howard-Vigorita wrote on 7/5/2022, 1:27 PM

... I know I can click on the 'hamburger' in the track header and then select Edit Visible Button Set. But I find it wastes time to do this with every new project, because I like the complete button set to

Haven't seen a Vegas hamburger since vp18. I know my vp19 with "..." normally saves changes to the visible track buttons on normal exits. But not on crashes or forced terminations with task manager or powershell scripts. Only exception is if multiple vps are running... I think the visible buttons on last one normally closed wins. Might get messed up if zombie vps from prior runs are still in memory so you might want to look out for that.

andyrpsmith wrote on 7/5/2022, 1:46 PM

They stay as you set them for me and they are carried over to other projects.

 

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

JMacSTL wrote on 10/25/2022, 10:32 AM

@Former user Same thing for me. Save a project, open it up later, buttons gone. I wonder if "Set Track Default Properties" (which is used to choose, for instance, your base plugins for a new project) would help. Imma try that.

UPDATE: It took several tries of making the buttons visible, closing vegas, reopening, setting default track properties (see photo), closing vegas, re-opening But I think it's finally (fingers crossed) stable and consistent. At one point, when I'd create a new blank session (which I do often rather than opening a template or similar) I'd get new audio tracks with automation ON and gain at some crazy low level. Weirdness, sure. But I"m guessing it culled that from some previous session. also, when I add a photo, it's no longer visible from my perspective. Anybody else see it here?

UPDATE 2 10-31-22: Nope. The buttons still disappear from time to time after opening up an existing project. Frustrating.

 

Last changed by JMacSTL on 10/31/2022, 10:27 AM, changed a total of 5 times.

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

paul-marshall wrote on 10/25/2022, 11:54 AM

My choice of visible buttons has not stayed put since VP20. I have tried all combinations of saving layouts, saving projects, closing and re-opening Vegas, and while they might stay around a short while at some point they will disappear.again. It was never an issue in any ealier version. Whille Vegas is now vastly improved in stability this is so frustrating.

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

diverG wrote on 10/25/2022, 4:20 PM

Why not create a 'default' project with your preferred settings/layout and save as such. To start a new project, open 'default', save as 'new' project and the add media, edit. Job done

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & 122(194), Edius 8.3WG and DVResolve19 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP17, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

paul-marshall wrote on 10/27/2022, 5:35 AM

Solved my problem with visible buttons. I make much use of window layouts for different parts of my workflow and the button sets for both tracks and events are stored as part of the user window layouts as well as the default. Makes sense, so different functions can have different buttons. Where it went wrong it seems was in copying my window layout files from VP18 to VP19 (was ok there though) then to VP20. I have now deleted all the layout files in C:\Users\xxxx\AppData\Roaming\VEGAS Pro\20.0\ and carefully rebuilt them making sure the layout folder in use was that one.
But wouldnt it be nice if there was a utility to transfer ALL settings from one version to the next!

The advantage of having your own layout(s) accessible on an f key(s) (or the default ALT D, D / 0-9 if you can remember that) is that any time it gets messed up or when starting a new project just hit the key and it's all back how you like it.


 

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

JMacSTL wrote on 11/3/2022, 11:55 AM

oooooohhhhhh. so the Visible Button Set is tied to the window layouts. So after you select "show all", you then need to resave your existing window layout. It's the little things, I swear. The little things.......

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

Grazie wrote on 11/3/2022, 9:37 PM

Visible Buttons Selection only stays selected IF it is saved to within the current Windows Layout and that Windows Layout is then Saved.

Using Relation Dbase jargon, Saving Visible Button Selection is NOT one to many, it is, stubbornly, ONE-TO-ONE. After many, many months of frustration I now also have to save my Visible Button Selection to/within the current Windows Layout.

Oh yes: As new VP Builds appear, this BUG-Feature reappears. Were it different, I’d be pleased 😉.

Grazie wrote on 11/3/2022, 9:43 PM

Oh yes, @JMacSTL, as I said, and until this hasn’t been rectified, we will revisit this as the next new Builds are rolled-out. Consequently, be prepared to re-read Users bumping into this. And don’t try and rely on using VP Preferences, it doesn’t help.