Jump to content


  • Posts

  • Joined

  • Last visited

thirdspace's Achievements


Newbie (1/15)




Community Answers

  1. Thanks for the tip on Snoize - looks a useful utility and I'll give it a go. However, as a MIID monitor, for the example above I guess it will show me two messages, one for Switch On (BF 3C 7F) and one for Switch Off (BF 3C 00). What Logic wants however is a single message: BF 3C Lo7, so only guess the Learn function will show me that by pressing the switch twice - OK now I've 'learned' about Lo7 though as I can use that next time. Thanks for all the help - it's becoming clearer!
  2. Thanks for the confirmation. Do they have their own plist or equivalent file somewhere?
  3. Just started using IO Labels and I note that they appear to be preferences - that is changes made in project apply to all other projects. Is there a way to set these up by project? For example I use a variety of user interfaces depending on situation - the only way I can see to set up IO labels that relate to each interface is to create a new User account for each one - which seems a little inflexible. Any ideas?
  4. well that explains it - thanks - but doesn't help in terms of providing numbers for Logic Pro of course - oh well, back to the calculator...
  5. You are correct! Again my error - I missed the message type in my shorthand! What I meant to say was Type:Controller, Channel=16, CC #60, Value=127 Entering this info into the online 'converters' above gives an output of BF 60 127, where the hex (and what Logic wants) is BF 3C 7F. So what would make this easier is a converter that gives a true hex output given the above information - if you know of one? (or wouldn't it be nicer if Logic itself allowed the manual entry of the information without having to convert?)
  6. Thanks - apologies I wasn't being clear! Logic's hex is hex agreed, but these two online converters I found seem to give non hex outputs: http://www.xmlizer.net/hansLindauer/midiapp.html https://gigperformer.com/support/midi-to-hexstring-generator.html So starting with say 16 60 127 I'm wondering if there's one that gives an output that works in Logic without having to convert each number manually? The above converters give BF 60 127 of which only the first part is correct. Thanks for the tip re Calculator - never knew that!
  7. Great replies - thanks. Seems like the key is to 'click the switch on, then off again, before deactivating Learn.' This changes the MIDI message learned from Control Change CH1, 60, 0 to Control Change CH1, 60, Lo7. So yes I could type this in (in Hex of course - thanks Logic) - but what does Lo7 mean? Presumably some kind of variable? If typing in values I guess I would replace the 5th/6th hex numbers in the string with Lo7 ie B0 3C Lo7. Can you recommend a HEX generator that can convert MIDI messages in standard format to Logic's version of what I presume is Hex? The two generators I have found so far give B0 60 Lo7 for this example, where Logic wants B0 3C Lo7 Also - to 'reverse' the effect of the switch (Mute On becomes Mute Off and vice versa) - presumably the way to enter this in the Controller Assignments is to enter a Multiply value of -1.00? or is there a better way? Thanks for the help on this
  8. I feel like I'm really missing something obvious here so any help with this would be appreciated. I have a MIDI footswitch that is set up so the buttons can be setup as either two state (On/Off) or one state (trigger). I wish to map a two state button on the foot switch to a two state parameter such as a specific channel mute in Logic Pro. Example MIDI - the two state button might send the following two messages: On CH1 CC#60 Value 127 Off CH1 CC#60 Value 0 So what I thought was the method - open Controller Assignments, click Learn, Click the Mute button on the channel in Logic, press the footswitch, but this records the first value it receives, but not the second. And Logic's mute button only does the one thing as it only knows two respond to the one message it has learned. Thanks in advance
  9. Hi all What's the best Looper plugin (to enable asynchronous Loop pedal type operation) compatible with Monterey/Logic 10.7.2? Essentially I want to use Logic Pro as if it was a LoopStation (but without a 'click track' as the starting point - otherwise Live Loops are the obvious choice) MainStage/LoopBack is a cool option but I specifically wish to use Logic Pro for a variety of reasons. There's some very pretty looking paid-for options (MSuperLooper etc) and some free versions that no longer work (Mobius) - but what's best? Many thanks
  10. Hi all Is it possible, when recording Live Loops, to have the first loop recorded set the tempo? This is how I am used to using a Loop pedal - that is when improvising a loop based performance the first loop recorded is not recorded to a click track and it is unusual to know in advance how many bars/beats long it is either (rehearsed pieces are different of course). So what I want to achieve is this: Have no click when recording, not think in advance about how many bars/beats long the loop will be Click record Click 'stop record' - loop automatically plays, and loops from the point that recording was stopped Without any reference to a click, or having to consider whether I am going to play 1, 2 3, 4 bars. From this point - no issue with the idea of tempo driving the synchronisation of further loop recordings, but ideally it would also be great to have separate loop tracks also independent of tempo/number of bars (as you might achieve with two looper pedals) I am possibly not able to take this approach at all with Live Loops - in which case an appropriate plug-in choice is required (if only MainStage's Loopback existed in Logic all would be well!) Thanks in advance
  11. Hi all I want to create a setup that routes a guitar input to various Aux channels, each of which contains a specific plugin. I would then like to route each Aux channel on to a further Aux channel to create a routing setup that lets me switch the output of one plugin into another. There seems to be an issue with MainStage when doing this where the signal does not get passed on via the bus as expected. This behaviour is also unpredictable - if I set up the routing as shown on the screenshot attached, it might work as expected during setup up to a point but then adding say a plugin disables the signal flow into that channel. or saving and reopening a working version leads to different results. I have tested this against an identical setup on Logic Pro - which functions exactly as expected at all times - see screenshot. Is there something in the MainStage setup that I need to change to make this work reliably? Thanks in advance
  12. Thanks for the replies. Yes of course this is the issue - the particular combination of audio drive input and output I had selected (MacBook Pro microphone and MacBoo prop speakers) is one that disables input monitoring to avoid feedback (and the checkbox in preferences is greyed out as a result) is what caught me out. Lesson learned! Thanks again.
  13. I have set up a couple of bus sends on an audio track expecting them to route signal to Aux tracks - but for some reason this is not happening when the signal is arriving via input monitoring - see attached image. This routing works fine when playing back audio recorded on the track. I must be missing something pretty basic here!?!? Logic Pro 10.6.3/MacOS 11.6
  14. Thanks - I hadn't considered using Sets - is there a functional difference? For example, is there an advantage to using a Set for the Loopback plugin as opposed to having it at Concert level in this case?
  15. Thanks for the reply. The issue is caused because I wish to use plugins and have the sound they make continue while I then use other plugins. For example one bank on the footpedal is devoted to the Loopback plugin. Having set the loop going I would then want to go to another bank to control another plugin. If I set up a Patch in Mainstage for say the Loopback plugin, as soon as you switch to another bank the sound stops. So unless there is a an option to stop this happening I am obliged to add all these plugins at concert level so that the sounds persist as I move from one to another. If I add the plugins at concert level but then create a switching layout at Patch level, Mainstage won't let me map controls at Patch level. Hence I have ended up with a layout with multiple instances of the control layout shown above, which graphically is messy and not useful in a live context as I can't see the detail. Any suggestions welcome as I am probably missing something really basic here!
  • Create New...