VP14 BUG - Keyboard shortcuts to scripts are removed on exit

Nick Hope 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

Nick Hope 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."

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

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.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

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 :-)

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.

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, 32 gigs Corsair Vengeance RGB 32GB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 580 graphics card, Corsair 1000 watt power supply.

Nick Hope 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!

.

 

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