VP14 BUG - Keyboard shortcuts to scripts are removed on exit

NickHope wrote on 9/20/2016, 5:43 AM

I have found a bug in VEGAS Pro 14.0 (Build 161) wherein keyboard shortcuts assigned to VP14 scripts (i.e. .js and .cs scripts in C:\Program Files\VEGAS\VEGAS Pro 14.0\Script Menu ) are removed from the keyboard map when exiting VP14.

For example I have this customized keyboard.ini file (or something.ini file) in %APPDATA%\VEGAS Pro\14.0\

[SfKeyMap]
Name=[Default]
[Global]
View.WindowLayouts.Load.UserLayout0=F10
[TrackView]
Script.Delete from event start to cursorV14=I
TrackView.Select.MarkIn=Ctrl+I
Script.Delete from cursor to event endV14=O
TrackView.Select.MarkOut=Ctrl+O
Script.SplitV14=S
Edit.Split=Alt+S
Edit.Trim.Start=Alt+VK_219
Edit.Trim.End=Alt+VK_221

After exiting VP14 the assignments to scripts are simply stripped out of the .ini file:

[SfKeyMap]
Name=[Default]
[Global]
View.WindowLayouts.Load.UserLayout0=F10
[TrackView]
TrackView.Select.MarkIn=Ctrl+I
TrackView.Select.MarkOut=Ctrl+O
Edit.Split=Alt+S
Edit.Trim.Start=Alt+VK_219
Edit.Trim.End=Alt+VK_221

Can anyone else confirm this?

As a workaround I have to copy a backup of the .ini file (with the script shortcuts) into %APPDATA%\VEGAS Pro\14.0\, overwriting the existing .ini file, before I start VP14 again. If it's not fixed I suppoe I could a batch file to do that copy operation then start VP14.

I have submitted a support request, [Ticket#2016092017004051]

Comments

NickHope wrote on 9/21/2016, 9:27 PM

I had a reply by email from MAGIX support that included this:

"Thank you for reporting this issue.  I have escalated this to development/QA to reproduce and enter it into our bug tracker."

VEGASDerek wrote on 9/22/2016, 10:55 AM

Yes...Eric has escalated this up to us on the development team.  We have reproduced the problem and we have a resolution for it that will be available in the next update.  

NickHope wrote on 9/22/2016, 11:38 AM

Thank you Derek, that's great news!

john-mollaghan wrote on 9/28/2016, 3:40 AM

Great to hear there is a fix on the way. I've put tool bar buttons for the scripts as an interim measure.

Grazie wrote on 9/28/2016, 4:22 AM

Ah! This makes sense. I had a spurious response to a Contour Shuttle Pro2 Button that I HAD assigned a Keystroke. I'll hunt it down and report it.

NickHope wrote on 10/23/2016, 1:43 AM

This is fixed in VEGAS Pro 14.0 (Build 178).

wilvan wrote on 10/23/2016, 10:46 AM

Build 178 ? How and where can one find new releases and what the improvements are , if any .

Am still having difficulties in trying to understand this magixal website lay-out :-)

Sony  PXW-FS7K and 2 x Sony PXW-Z280  ( optimised as per Doug Jensen Master Classes and Alister Chapman advices ) Sony A7 IV
2 x HP Z840 workstations , each as follows : WIN10 pro x 64 , 2 x 10 core Xeon E5-2687W V3 at 3.5 GHz , 256 GB reg ECC RAM , HP nvidia quadro RTX A5000 ( 24GB ), 3 x samsung 970 EVO Plus 1TB M.2 2280 PCIe 3.0 x4  , 3 x SSD 1TB samsung 860 pro , 3 x 3TB WD3003FZEX.
SONY Vegas Pro 13 build 453  ( user since version 4 ) , SONY DVDarch , SONY SoundForge(s) , SONY Acid Pro(s) , SONY Cinescore ( each year buying upgrades for all of them since vegas pro 4 )
(MAGIX) Vegas pro 14 ( bought it as a kind of support but never installed it )
SONY CATALYST browse 
Adobe Photoshop  CC 2023
Adobe After Effects CC 2023 & Adobe Media Encoder CC 2023
Avid Media Composer 2022.xx ( started with the FREE Avid Media Composer First in 2019 )
Dedicated solely editing systems , fully optimized , windows 10 pro x 64 
( win10 pro operating systems , all most silly garbage and kid's stuff of microsoft entirely removed , never update win 10 unless required for editing purposes or ( maybe ) after a while when updates have proven to be reliable and no needless microsoft kid's stuff is added in the updates )

paul-marshall wrote on 11/6/2016, 11:21 AM

It is not fixed in 178 for me. I am trying to assign numeric pad 5 to 'Trim Right'.  Numeric pad 5 is normally 'enter extended mode' but although I delete Num 5 from that function it keeps coming back, as well as the function I assigned. So although it keeps added functions it does not remove unwanted ones.

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 21 latest version. Vegas user since V10

 

james-ollick wrote on 11/6/2016, 12:32 PM

Have you tried the latest? It is build 189.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

NickHope wrote on 11/7/2016, 1:35 AM

It is not fixed in 178 for me. I am trying to assign numeric pad 5 to 'Trim Right'.  Numeric pad 5 is normally 'enter extended mode' but although I delete Num 5 from that function it keeps coming back, as well as the function I assigned. So although it keeps added functions it does not remove unwanted ones.

I'm not sure exactly what you mean by "Trim Right", but in general this is working fine for me in builds 178 and 189.

Try not doing a "Remove" for TrackView.EnterExpandedEditMode but simply doing the "Add" for Num 5 for "Trim Right". That should put a line at the end of your keyboard.ini (or whatever.ini) that overrides the default use of Num 5 for TrackView.EnterExpandedEditMode.

If that doesn't work, try deleting keyboard.ini and starting afresh.

If you still have trouble please paste the contents of your keyboard.ini file here and explain exactly what "Trim Right" is.

paul-marshall wrote on 11/8/2016, 9:06 AM

Sorry I called it trim right, it should be trim end  "Trim the end of the selected event to the cursor position" normally asigned to Alt+]

I tried 189 it is still the same. It was ok in VP13. I deleted keeyboard.ini and started again. This is all keyboard.ini has now:

[SfKeyMap]
Name=[Default]
[TrackView]
TrackView.EnterExpandedEditMode=Ctrl+Shift+X
Edit.Trim.Start=Num 4
Edit.Trim.End=Num 5

But Edit.Trim.End=Num 5 is ignored and Num 5 still does TrackView.EnterExpandedEditMode.
Num 4 works as it should and so does Ctrl+Shift+X.

If i DO remove TrackView.EnterExpandedEditMode = num 5 (in the shortcuts editor) then I get this:

[SfKeyMap]
Name=[Default]
[TrackView]
TrackView.EnterExpandedEditMode=Ctrl+Shift+X
Edit.Trim.Start=Num 4
Null.0=Num 5
Null.1=Num 5

and then num 5 does nothing at all.

I know this is a very minor problem compared to many other issues but i've got used to these keys and its hard to get out of 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 21 latest version. Vegas user since V10

 

NickHope wrote on 11/8/2016, 9:50 AM

Well I just spent ages testing this in VP13 and VP14 and I can't get it to work in either. Only Num 4 works reliably for me (doing Edit.Trim.Start). The other 2 shortcuts you want don't work. In addition I got weird behaviour. At one point in VP13 Num 5 did start working for Edit.Trim.End but it stopped working after I restarted. At another point Num 5 started doing the TrackView.EnterExpandedEditMode despite having set it to Edit.Trim.End. It's definitely buggy but I couldn't establish a clear failure pattern. I suggest you submit a support request via http://support.magix.com/vegas , including as much detailed information about the problem as you can.

paul-marshall wrote on 11/8/2016, 9:59 AM

Many thanks Nick for taking the time to check it's not just me, I will submit a request now. 

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 21 latest version. Vegas user since V10