Funkagenda Posted May 15, 2009 Share Posted May 15, 2009 When I am using third party plugins and I try to enter numeric data on the GUI, quite a lot of the time it just flicks to one of my screensets. Anyone know a way round this? Note: It DOESN'T happen when I switch from the GUI to the plugin CONTROL view... A little help please? Quote Link to comment Share on other sites More sharing options...
chilisexnbeer Posted May 15, 2009 Share Posted May 15, 2009 Hi Funkagenda - I had the same problem and came up with this... 1. Create a new empty project in Logic 2. Delete all standard screensets except for the Screenset 1. 3. Duplicate screenset 1 to something like 69 (or whatever takes your fancy ) 4. Delete screenset 1. 6. Enter data into plugin as required... Save project as 'Empty screensets' or whatever for future use in same situation... Hope this helps (and makes sense...) big al Quote Link to comment Share on other sites More sharing options...
PaulSC Posted May 15, 2009 Share Posted May 15, 2009 Sharing keystroke focus between Logic and third-party plug-ins is sometimes wonky; issues seem to vary from user to user (possibly depending on the version of OS X ???). For me, the problem arose using Absynth, and I ended up solving it by remapping my screensets from 1, 2, 3, ... to shift-1, shift-2, shift-3, ... (I rarely use more than two or three screensets anyway). Quote Link to comment Share on other sites More sharing options...
Funkagenda Posted May 15, 2009 Author Share Posted May 15, 2009 Hmmm... Sadly I use my screensets constantly + I have had the same ones since Logic 5 so I am hoping somone can come up with a solution that doesn't mean I have to change them. They are like second nature to me now! lol Quote Link to comment Share on other sites More sharing options...
chilisexnbeer Posted May 16, 2009 Share Posted May 16, 2009 Not a problem in Logic 8 - can't remember for earlier versions.... When you create a new project and edit the screen-sets, it has no effect on other projects, templates, etc, unless you tell it to. Look again at the last part of my solution - save the empty screen-set project as a separate project in itself which you can use for future registrations... big al Quote Link to comment Share on other sites More sharing options...
trompetenick Posted May 16, 2009 Share Posted May 16, 2009 Some more solutions here: http://www.logicprohelp.com/viewtopic.php?t=38268&highlight=keycommands Remember to use the search funktion on this forum. Nick Quote Link to comment Share on other sites More sharing options...
Funkagenda Posted May 26, 2009 Author Share Posted May 26, 2009 Some more solutions here:http://www.logicprohelp.com/viewtopic.php?t=38268&highlight=keycommands Remember to use the search funktion on this forum. Nick Thanks for the link... although it doesn't solve what I am trying to do. I did use the search function but as with ALL search functions on forums, you can only find what you put in, and I guess the combination of words entered did not bring forth an answer. Quote Link to comment Share on other sites More sharing options...
Funkagenda Posted May 26, 2009 Author Share Posted May 26, 2009 So I guess this is just a fault with Logic then? Man I love the program, but s#!+ like this should be ironed out BEFORE we get to version 8! lol Quote Link to comment Share on other sites More sharing options...
trompetenick Posted May 26, 2009 Share Posted May 26, 2009 Thanks for the link... although it doesn't solve what I am trying to do. . It works: Create a set of keycommands without any numbers or single letters. Store this , to bring up when you have to type in a lot of serials, eg when setting up Logic on a new System. To create a "blank" keycommand list: -open keycommands -export under "empty" or whatever -show used -expand all -learn by -press backspace (until there is a non editble kommand or the segment ends) Export again under the same name ( overwrite) to make shure all is being saved. Credits for this go to Melino, of "Logicuser.de" and Meiermueller who put it into the FAQ there. There should be no problems at all, using this method. Nick Quote Link to comment Share on other sites More sharing options...
jaytranzmit Posted June 11, 2009 Share Posted June 11, 2009 But, he doesn't want to be doing that every single time he wants to type in a numeric setting on a plugin Yes that could be useful for authorising some plugins now and again but, not while trying to work. Quote Link to comment Share on other sites More sharing options...
trompetenick Posted June 11, 2009 Share Posted June 11, 2009 But, he doesn't want to be doing that every single time he wants to type in a numeric setting on a plugin No. you only do it once, and then SAVE THE KEYCOMMANDS so you can open them again when needed! Nick Oh sorry wrong thread. Shure, that's a pain, entering numeric values and the screensets keep on changing. ( I was on that thread with plugin-verification...) Quote Link to comment Share on other sites More sharing options...
joemagic Posted June 12, 2009 Share Posted June 12, 2009 I had this problem using an autoload song and older projects from Logic 7. A fresh template solved the problem. As a work around for entering authorization codes, I'd open the plugs in Garageband and enter serials there. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.