Loopy Pro: Create music, your way.

What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Loopy Pro is here!

1…3738404243…50

Comments

  • AlmostAnonymousAlmostAnonymous

    @audiblevideo said:

    @AlmostAnonymous said:
    I'll use turnado all day live, but not for studio work. One of the nice things about turnado is that it does send bi directional midi.
    If you like its interface, you can use it and send the midi to other effects.

    Please excuse my potential misunderstanding. Are you saying you can use Tunados Dictator with an effects chain outside of what Turnado provides? For example using Turnado to turn knobs on an external bitcrusher and or delay.

    Like this?

  • espiegel123espiegel123

    Nice jam by coffebeats

  • Michael_R_GrantMichael_R_Grant
    edited January 2022

    @wim said:

    @galmandsværk said:

    @aaronpc said:

    @tahiche said:

    @Jumpercollins said:
    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

    Has anyone else here downloaded this guy’s template from the YouTube page? When I open it, there is no audio input. It records silence into the slicer and donuts, and the mic is flatlined.

    All LP’s built-in templates work fine.

    I’m guessing it might be because he used an external mic, and it may have introduced a bug when the template was shared. Or I missing something stupid.

    I can’t figure out what’s going on, but I created a new mic input and that made everything work fine (you can even drag and drop the effects from the original mic input). I’ve tried to check if there are any differences in the two mic inputs, but they seem to be absolutely similar, except the original one is completely silent.

    Anyways, a new mic input makes it work. It’s a fun template. I wish there’ll be more of these to share and explore. This one is totally different from my normal work flow, but it’s very inspiring to try out different ways of using LP.

    I'm guessing that it wasn't the device mic input at all but input from an interface. It doesn't surprise me that a different input source wouldn't work if not present on the device. The confusion is they're all represented with a mic icon.

    Yes, I pointed out this issue with one of the original templates that was to be included with Loopy Pro. Any template created when an audio interface is being used won’t have an internal mic channel routed to the donuts or the outputs, which would obviously be very confusing for new users and make them think the template/app was broken. This was the case with the template I’m talking about, but happily the author was able to rush through a new version which had an internal mic channel, before the launch button was hit on the app! Phew!

    It’s a good idea to have a different icon when using an interface. I’ll post this suggestion in the Slack channel.

    EDIT: Done! I’ve suggested 2 things:

    • a different mic icon for audio interfaces if possible.
    • an auto-detect, where mic channels default to the internal mic if an audio interface previously used in the project is no longer detected.
  • audiblevideoaudiblevideo

    @AlmostAnonymous said:

    @audiblevideo said:

    @AlmostAnonymous said:
    I'll use turnado all day live, but not for studio work. One of the nice things about turnado is that it does send bi directional midi.
    If you like its interface, you can use it and send the midi to other effects.

    Please excuse my potential misunderstanding. Are you saying you can use Tunados Dictator with an effects chain outside of what Turnado provides? For example using Turnado to turn knobs on an external bitcrusher and or delay.

    Like this?

    Oh shit! And no shit?! The things I learn the apps I have will do. Thank you. Off I go to merrily experiment.

  • MisplacedDevelopmentMisplacedDevelopment

    Has anyone managed to get MIDI Guitar 2 working inside Loopy? I think I have it wired up correctly with MG added as an effect on mic input then the “A” instance added as a MIDI lane but it does not send any MIDI out to the destinations I have selected (tried a few synths and MIDI monitor). The internal MG synths respond OK to input so that part is working correctly but LP is not seeing the MIDI out.

    Odd…just restarted Loopy and now MG in the MIDI lane is labelled as “B” version and it and is sending MIDI out correctly. I can reproduce the original problem though by removing MG and adding it back in again.

  • espiegel123espiegel123

    @Michael_R_Grant said:

    @wim said:

    @galmandsværk said:

    @aaronpc said:

    @tahiche said:

    @Jumpercollins said:
    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

    Has anyone else here downloaded this guy’s template from the YouTube page? When I open it, there is no audio input. It records silence into the slicer and donuts, and the mic is flatlined.

    All LP’s built-in templates work fine.

    I’m guessing it might be because he used an external mic, and it may have introduced a bug when the template was shared. Or I missing something stupid.

    I can’t figure out what’s going on, but I created a new mic input and that made everything work fine (you can even drag and drop the effects from the original mic input). I’ve tried to check if there are any differences in the two mic inputs, but they seem to be absolutely similar, except the original one is completely silent.

    Anyways, a new mic input makes it work. It’s a fun template. I wish there’ll be more of these to share and explore. This one is totally different from my normal work flow, but it’s very inspiring to try out different ways of using LP.

    I'm guessing that it wasn't the device mic input at all but input from an interface. It doesn't surprise me that a different input source wouldn't work if not present on the device. The confusion is they're all represented with a mic icon.

    Yes, I pointed out this issue with one of the original templates that was to be included with Loopy Pro. Any template created when an audio interface is being used won’t have an internal mic channel routed to the donuts or the outputs, which would obviously be very confusing for new users and make them think the template/app was broken. This was the case with the template I’m talking about, but happily the author was able to rush through a new version which had an internal mic channel, before the launch button was hit on the app! Phew!

    It’s a good idea to have a different icon when using an interface. I’ll post this suggestion in the Slack channel.

    EDIT: Done! I’ve suggested 2 things:

    • a different mic icon for audio interfaces if possible.
    • an auto-detect, where mic channels default to the internal mic if an audio interface previously used in the project is no longer detected.

    Personally, I would hate mic channels being automatically assigned to channels if an interface was used. That happening in AUM is something many complain about as it is a source of awful feedback.

  • espiegel123espiegel123

    @MisplacedDevelopment said:
    Has anyone managed to get MIDI Guitar 2 working inside Loopy? I think I have it wired up correctly with MG added as an effect on mic input then the “A” instance added as a MIDI lane but it does not send any MIDI out to the destinations I have selected (tried a few synths and MIDI monitor). The internal MG synths respond OK to input so that part is working correctly but LP is not seeing the MIDI out.

    Odd…just restarted Loopy and now MG in the MIDI lane is labelled as “B” version and it and is sending MIDI out correctly. I can reproduce the original problem though by removing MG and adding it back in again.

    I have the same issue.

  • Michael_R_GrantMichael_R_Grant

    @espiegel123 said:

    @Michael_R_Grant said:

    @wim said:

    @galmandsværk said:

    @aaronpc said:

    @tahiche said:

    @Jumpercollins said:
    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

    Has anyone else here downloaded this guy’s template from the YouTube page? When I open it, there is no audio input. It records silence into the slicer and donuts, and the mic is flatlined.

    All LP’s built-in templates work fine.

    I’m guessing it might be because he used an external mic, and it may have introduced a bug when the template was shared. Or I missing something stupid.

    I can’t figure out what’s going on, but I created a new mic input and that made everything work fine (you can even drag and drop the effects from the original mic input). I’ve tried to check if there are any differences in the two mic inputs, but they seem to be absolutely similar, except the original one is completely silent.

    Anyways, a new mic input makes it work. It’s a fun template. I wish there’ll be more of these to share and explore. This one is totally different from my normal work flow, but it’s very inspiring to try out different ways of using LP.

    I'm guessing that it wasn't the device mic input at all but input from an interface. It doesn't surprise me that a different input source wouldn't work if not present on the device. The confusion is they're all represented with a mic icon.

    Yes, I pointed out this issue with one of the original templates that was to be included with Loopy Pro. Any template created when an audio interface is being used won’t have an internal mic channel routed to the donuts or the outputs, which would obviously be very confusing for new users and make them think the template/app was broken. This was the case with the template I’m talking about, but happily the author was able to rush through a new version which had an internal mic channel, before the launch button was hit on the app! Phew!

    It’s a good idea to have a different icon when using an interface. I’ll post this suggestion in the Slack channel.

    EDIT: Done! I’ve suggested 2 things:

    • a different mic icon for audio interfaces if possible.
    • an auto-detect, where mic channels default to the internal mic if an audio interface previously used in the project is no longer detected.

    Personally, I would hate mic channels being automatically assigned to channels if an interface was used. That happening in AUM is something many complain about as it is a source of awful feedback.

    Doesn’t Loopy Pro have a default mic input channel in a default project, though?

  • espiegel123espiegel123

    @Michael_R_Grant said:

    @espiegel123 said:

    @Michael_R_Grant said:

    @wim said:

    @galmandsværk said:

    @aaronpc said:

    @tahiche said:

    @Jumpercollins said:
    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

    Has anyone else here downloaded this guy’s template from the YouTube page? When I open it, there is no audio input. It records silence into the slicer and donuts, and the mic is flatlined.

    All LP’s built-in templates work fine.

    I’m guessing it might be because he used an external mic, and it may have introduced a bug when the template was shared. Or I missing something stupid.

    I can’t figure out what’s going on, but I created a new mic input and that made everything work fine (you can even drag and drop the effects from the original mic input). I’ve tried to check if there are any differences in the two mic inputs, but they seem to be absolutely similar, except the original one is completely silent.

    Anyways, a new mic input makes it work. It’s a fun template. I wish there’ll be more of these to share and explore. This one is totally different from my normal work flow, but it’s very inspiring to try out different ways of using LP.

    I'm guessing that it wasn't the device mic input at all but input from an interface. It doesn't surprise me that a different input source wouldn't work if not present on the device. The confusion is they're all represented with a mic icon.

    Yes, I pointed out this issue with one of the original templates that was to be included with Loopy Pro. Any template created when an audio interface is being used won’t have an internal mic channel routed to the donuts or the outputs, which would obviously be very confusing for new users and make them think the template/app was broken. This was the case with the template I’m talking about, but happily the author was able to rush through a new version which had an internal mic channel, before the launch button was hit on the app! Phew!

    It’s a good idea to have a different icon when using an interface. I’ll post this suggestion in the Slack channel.

    EDIT: Done! I’ve suggested 2 things:

    • a different mic icon for audio interfaces if possible.
    • an auto-detect, where mic channels default to the internal mic if an audio interface previously used in the project is no longer detected.

    Personally, I would hate mic channels being automatically assigned to channels if an interface was used. That happening in AUM is something many complain about as it is a source of awful feedback.

    Doesn’t Loopy Pro have a default mic input channel in a default project, though?

    a few things:

    • the default mic channel has monitoring off to avoid feedback if the internal speakers are used
    • many are awaiting savable default template to not have that default mic channel
    • even with the default mic channel having monitoring off if using speakers, it is on through headphones which can be hugely annoying if auto-substitution is done.
    • The default mic has no effects on it. If your file has an amp sim or boosting eq, the result of auto-substitution is really gnarly.

    Imo, confusion about inputs on the mixer is less major than the issues caused by automatic reassignment. People sharing templates intended for an intern could add a text note on the templates.

    There are probably ramifications to auto-reassignment, I am overlooking for some templates.

    Any confusion about inputs on the mixer is easily remedied and a one off occurrence. The downsides of automatic reassignment leads to ongoing inconvenience for people that frequently switch between being connected to an interface and not.

    I honestly don’t think this is a major source of confusion.

  • muzkamuzka

    Sorry if this has been asked, I've searched online with no joy so any help would be greatly appreciated

    Anyone know if it possible to export individual clips/loops?

    Thanks

  • espiegel123espiegel123

    @muzka said:
    Sorry if this has been asked, I've searched online with no joy so any help would be greatly appreciated

    Anyone know if it possible to export individual clips/loops?

    Thanks

    Yes. There are several ways. Swipe up on a clip to get the clip details popup and tap the export icon is one way.

    The wiki pages about Loopy are also worthwhile (there is info about exporting there):

    https://wiki.audiob.us/doku.php?id=loopy_pro

    If you haven't ventured into Loopy's manual (available from its Help menu) it is worthwhile even if it is not 100% complete.

  • muzkamuzka

    @espiegel123 said:

    @muzka said:
    Sorry if this has been asked, I've searched online with no joy so any help would be greatly appreciated

    Anyone know if it possible to export individual clips/loops?

    Thanks

    Yes. There are several ways. Swipe up on a clip to get the clip details popup and tap the export icon is one way.

    The wiki pages about Loopy are also worthwhile (there is info about exporting there):

    https://wiki.audiob.us/doku.php?id=loopy_pro

    If you haven't ventured into Loopy's manual (available from its Help menu) it is worthwhile even if it is not 100% complete.

    Thats perfect, thank you.

    I checked the manual and jumped straight to export which isn't finished yet. Need to start from the beginning and work through. Just got the app few hours ago and linked up the lppro mk3 and having endless fun

    Thanks again

  • wimwim

    @espiegel123 said:

    @Michael_R_Grant said:

    @wim said:

    @galmandsværk said:

    @aaronpc said:

    @tahiche said:

    @Jumpercollins said:
    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

    Has anyone else here downloaded this guy’s template from the YouTube page? When I open it, there is no audio input. It records silence into the slicer and donuts, and the mic is flatlined.

    All LP’s built-in templates work fine.

    I’m guessing it might be because he used an external mic, and it may have introduced a bug when the template was shared. Or I missing something stupid.

    I can’t figure out what’s going on, but I created a new mic input and that made everything work fine (you can even drag and drop the effects from the original mic input). I’ve tried to check if there are any differences in the two mic inputs, but they seem to be absolutely similar, except the original one is completely silent.

    Anyways, a new mic input makes it work. It’s a fun template. I wish there’ll be more of these to share and explore. This one is totally different from my normal work flow, but it’s very inspiring to try out different ways of using LP.

    I'm guessing that it wasn't the device mic input at all but input from an interface. It doesn't surprise me that a different input source wouldn't work if not present on the device. The confusion is they're all represented with a mic icon.

    Yes, I pointed out this issue with one of the original templates that was to be included with Loopy Pro. Any template created when an audio interface is being used won’t have an internal mic channel routed to the donuts or the outputs, which would obviously be very confusing for new users and make them think the template/app was broken. This was the case with the template I’m talking about, but happily the author was able to rush through a new version which had an internal mic channel, before the launch button was hit on the app! Phew!

    It’s a good idea to have a different icon when using an interface. I’ll post this suggestion in the Slack channel.

    EDIT: Done! I’ve suggested 2 things:

    • a different mic icon for audio interfaces if possible.
    • an auto-detect, where mic channels default to the internal mic if an audio interface previously used in the project is no longer detected.

    Personally, I would hate mic channels being automatically assigned to channels if an interface was used. That happening in AUM is something many complain about as it is a source of awful feedback.

    +1
    Auto assignment has far more downsides that positives.

  • NoiseFlooredNoiseFloored

    @wim said:

    @espiegel123 said:

    @Michael_R_Grant said:

    @wim said:

    @galmandsværk said:

    @aaronpc said:

    @tahiche said:

    @Jumpercollins said:
    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

    Has anyone else here downloaded this guy’s template from the YouTube page? When I open it, there is no audio input. It records silence into the slicer and donuts, and the mic is flatlined.

    All LP’s built-in templates work fine.

    I’m guessing it might be because he used an external mic, and it may have introduced a bug when the template was shared. Or I missing something stupid.

    I can’t figure out what’s going on, but I created a new mic input and that made everything work fine (you can even drag and drop the effects from the original mic input). I’ve tried to check if there are any differences in the two mic inputs, but they seem to be absolutely similar, except the original one is completely silent.

    Anyways, a new mic input makes it work. It’s a fun template. I wish there’ll be more of these to share and explore. This one is totally different from my normal work flow, but it’s very inspiring to try out different ways of using LP.

    I'm guessing that it wasn't the device mic input at all but input from an interface. It doesn't surprise me that a different input source wouldn't work if not present on the device. The confusion is they're all represented with a mic icon.

    Yes, I pointed out this issue with one of the original templates that was to be included with Loopy Pro. Any template created when an audio interface is being used won’t have an internal mic channel routed to the donuts or the outputs, which would obviously be very confusing for new users and make them think the template/app was broken. This was the case with the template I’m talking about, but happily the author was able to rush through a new version which had an internal mic channel, before the launch button was hit on the app! Phew!

    It’s a good idea to have a different icon when using an interface. I’ll post this suggestion in the Slack channel.

    EDIT: Done! I’ve suggested 2 things:

    • a different mic icon for audio interfaces if possible.
    • an auto-detect, where mic channels default to the internal mic if an audio interface previously used in the project is no longer detected.

    Personally, I would hate mic channels being automatically assigned to channels if an interface was used. That happening in AUM is something many complain about as it is a source of awful feedback.

    +1
    Auto assignment has far more downsides that positives.

    I agree. The only way I see this working reasonably well is adding some kind of virtual input that always auto assigns to the first one in the system (same for a virtual output auto assigning to the first output stereo pair).

  • espiegel123espiegel123

    @NoiseFloored said:

    @wim said:

    @espiegel123 said:

    @Michael_R_Grant said:

    @wim said:

    @galmandsværk said:

    @aaronpc said:

    @tahiche said:

    @Jumpercollins said:
    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

    Has anyone else here downloaded this guy’s template from the YouTube page? When I open it, there is no audio input. It records silence into the slicer and donuts, and the mic is flatlined.

    All LP’s built-in templates work fine.

    I’m guessing it might be because he used an external mic, and it may have introduced a bug when the template was shared. Or I missing something stupid.

    I can’t figure out what’s going on, but I created a new mic input and that made everything work fine (you can even drag and drop the effects from the original mic input). I’ve tried to check if there are any differences in the two mic inputs, but they seem to be absolutely similar, except the original one is completely silent.

    Anyways, a new mic input makes it work. It’s a fun template. I wish there’ll be more of these to share and explore. This one is totally different from my normal work flow, but it’s very inspiring to try out different ways of using LP.

    I'm guessing that it wasn't the device mic input at all but input from an interface. It doesn't surprise me that a different input source wouldn't work if not present on the device. The confusion is they're all represented with a mic icon.

    Yes, I pointed out this issue with one of the original templates that was to be included with Loopy Pro. Any template created when an audio interface is being used won’t have an internal mic channel routed to the donuts or the outputs, which would obviously be very confusing for new users and make them think the template/app was broken. This was the case with the template I’m talking about, but happily the author was able to rush through a new version which had an internal mic channel, before the launch button was hit on the app! Phew!

    It’s a good idea to have a different icon when using an interface. I’ll post this suggestion in the Slack channel.

    EDIT: Done! I’ve suggested 2 things:

    • a different mic icon for audio interfaces if possible.
    • an auto-detect, where mic channels default to the internal mic if an audio interface previously used in the project is no longer detected.

    Personally, I would hate mic channels being automatically assigned to channels if an interface was used. That happening in AUM is something many complain about as it is a source of awful feedback.

    +1
    Auto assignment has far more downsides that positives.

    I agree. The only way I see this working reasonably well is adding some kind of virtual input that always auto assigns to the first one in the system (same for a virtual output auto assigning to the first output stereo pair).

    In my opinion, even that does not work well -- auto-assigning a mic (particularly if monitoring is on) is an invitation to feedback. I think the problem of someone not having learned how the audio inputs on the mixer work (a one-time issue that is unlikely to recur once someone knows how input channels work) is better solved by things other than automated remapping.

    That being said, a simple way of manually reassigning inputs would be beneficial. (And I suspect something like this is in the works).

  • JumpercollinsJumpercollins

  • NoiseFlooredNoiseFloored

    @espiegel123 said:

    @NoiseFloored said:

    @wim said:

    @espiegel123 said:

    @Michael_R_Grant said:

    @wim said:

    @galmandsværk said:

    @aaronpc said:

    @tahiche said:

    @Jumpercollins said:
    Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!

    Has anyone else here downloaded this guy’s template from the YouTube page? When I open it, there is no audio input. It records silence into the slicer and donuts, and the mic is flatlined.

    All LP’s built-in templates work fine.

    I’m guessing it might be because he used an external mic, and it may have introduced a bug when the template was shared. Or I missing something stupid.

    I can’t figure out what’s going on, but I created a new mic input and that made everything work fine (you can even drag and drop the effects from the original mic input). I’ve tried to check if there are any differences in the two mic inputs, but they seem to be absolutely similar, except the original one is completely silent.

    Anyways, a new mic input makes it work. It’s a fun template. I wish there’ll be more of these to share and explore. This one is totally different from my normal work flow, but it’s very inspiring to try out different ways of using LP.

    I'm guessing that it wasn't the device mic input at all but input from an interface. It doesn't surprise me that a different input source wouldn't work if not present on the device. The confusion is they're all represented with a mic icon.

    Yes, I pointed out this issue with one of the original templates that was to be included with Loopy Pro. Any template created when an audio interface is being used won’t have an internal mic channel routed to the donuts or the outputs, which would obviously be very confusing for new users and make them think the template/app was broken. This was the case with the template I’m talking about, but happily the author was able to rush through a new version which had an internal mic channel, before the launch button was hit on the app! Phew!

    It’s a good idea to have a different icon when using an interface. I’ll post this suggestion in the Slack channel.

    EDIT: Done! I’ve suggested 2 things:

    • a different mic icon for audio interfaces if possible.
    • an auto-detect, where mic channels default to the internal mic if an audio interface previously used in the project is no longer detected.

    Personally, I would hate mic channels being automatically assigned to channels if an interface was used. That happening in AUM is something many complain about as it is a source of awful feedback.

    +1
    Auto assignment has far more downsides that positives.

    I agree. The only way I see this working reasonably well is adding some kind of virtual input that always auto assigns to the first one in the system (same for a virtual output auto assigning to the first output stereo pair).

    In my opinion, even that does not work well -- auto-assigning a mic (particularly if monitoring is on) is an invitation to feedback. I think the problem of someone not having learned how the audio inputs on the mixer work (a one-time issue that is unlikely to recur once someone knows how input channels work) is better solved by things other than automated remapping.

    That being said, a simple way of manually reassigning inputs would be beneficial. (And I suspect something like this is in the works).

    True, I was trying to come up with a reasonable implementation for those that want it. I still prefer what you're saying about easier manual reassignment :)

  • lmbrownlmbrown

    Is there a way to select next empty clip? I want to bind a midi note from a controller so that when I tap it it records retrospectively into the next empty clip without having to tap it on the screen. "Next clip" selection seems to only work for donuts that have already been recorded into.

  • espiegel123espiegel123

    @lmbrown said:
    Is there a way to select next empty clip? I want to bind a midi note from a controller so that when I tap it it records retrospectively into the next empty clip without having to tap it on the screen. "Next clip" selection seems to only work for donuts that have already been recorded into.

    There isn’t a next empty clip target (yet, fingers-crossed that it might happen). Next clip should work whether the next clip isempty or not, though.

  • lmbrownlmbrown

    @espiegel123 said:

    @lmbrown said:
    Is there a way to select next empty clip? I want to bind a midi note from a controller so that when I tap it it records retrospectively into the next empty clip without having to tap it on the screen. "Next clip" selection seems to only work for donuts that have already been recorded into.

    There isn’t a next empty clip target (yet, fingers-crossed that it might happen). Next clip should work whether the next clip isempty or not, though.

    Okay, cool. Thanks! That would be an awesome feature.

  • espiegel123espiegel123

    @lmbrown said:

    @espiegel123 said:

    @lmbrown said:
    Is there a way to select next empty clip? I want to bind a midi note from a controller so that when I tap it it records retrospectively into the next empty clip without having to tap it on the screen. "Next clip" selection seems to only work for donuts that have already been recorded into.

    There isn’t a next empty clip target (yet, fingers-crossed that it might happen). Next clip should work whether the next clip isempty or not, though.

    Okay, cool. Thanks! That would be an awesome feature.

    Are you experiencing next clip not going to the next clip if it is empty?

  • JojoJojo

    Hey again! I think my comment was buried… anymore ideas on what my mapping issues might be? Here is my response to a response with a YouTube video showing the process. Thanks!

    @wim said:
    @Jojo, how did you get to that point? I don't see any action such as "Press" and I don't see any CC type such as "On CC 16" or "Hold CC 16". I haven't figured out any way to get to a button setting that looks like what you show.

    A little late, but my demo ran out ….and I had almost two feet of snow to deal with - haha! Here’s a video. Hopefully it makes sense…I couldn’t upload it here, so I put it up on YouTube.

    https://youtube.com/shorts/d9ALPq198Co?feature=share

  • espiegel123espiegel123

    @Jojo said:
    Hey again! I think my comment was buried… anymore ideas on what my mapping issues might be? Here is my response to a response with a YouTube video showing the process. Thanks!

    @wim said:
    @Jojo, how did you get to that point? I don't see any action such as "Press" and I don't see any CC type such as "On CC 16" or "Hold CC 16". I haven't figured out any way to get to a button setting that looks like what you show.

    A little late, but my demo ran out ….and I had almost two feet of snow to deal with - haha! Here’s a video. Hopefully it makes sense…I couldn’t upload it here, so I put it up on YouTube.

    https://youtube.com/shorts/d9ALPq198Co?feature=share

    i cant really tell what is going on enough to know what was going on. It is notably odd that the Action field doesn't show the name of the action being mapped. The midi monitor window isn't large enough to show the values...and it would be helpful to see the actions already mapped in MIDI Control.

    For getting a pedal set up, it is useful to first set up a pedal with the default project to eliminate the possibility that something about the project is interfering.

    Normally, when you MIDI Learn a widget, the initial panel should show the action being mapped is in this picture

    There is a tutorial video that walks through setting up a Morningstar pedal. It might have some info helpful to you. There are also some troubleshooting tips now in the wiki related to making sure a pedal isn't inadvertently getting midi from Loopy Pro that it shouldn't

  • wimwim
    edited January 2022

    @Jojo said:
    Hey again! I think my comment was buried… anymore ideas on what my mapping issues might be? Here is my response to a response with a YouTube video showing the process. Thanks!

    @wim said:
    @Jojo, how did you get to that point? I don't see any action such as "Press" and I don't see any CC type such as "On CC 16" or "Hold CC 16". I haven't figured out any way to get to a button setting that looks like what you show.

    A little late, but my demo ran out ….and I had almost two feet of snow to deal with - haha! Here’s a video. Hopefully it makes sense…I couldn’t upload it here, so I put it up on YouTube.

    https://youtube.com/shorts/d9ALPq198Co?feature=share

    That's really hard to follow. Here's what I think I'm seeing:

    1. Turn on MIDI Learn and tap the Rec/Play/Stop widget
    2. Tap the foot switch and it registers CC 16, hold
    3. Manually change the action to On/Off
    4. Oddly no action shows. Normally it should say "Press" by default
    5. Close down midi learn and try triggering the widget with the foot pedal.
    6. Streambyter shows activity, but not the CC 16 from the foot pedal. Perhaps it doesn't have its midi input set properly?
    7. The widget doesn't trigger? Or, it triggers, but it doesn't do what you expect?

    I'm not clear what's coming from the Vocalive pedal, but it seems like you probably don't want On/Off for the setting in #3 above. That should probably be On.

    Point 4 is most likely the key. I don't know how you got to the point where it doesn't show anything for the Action. I've never seen that. If you can, try setting that to Press by tapping the arrow next to.

    Streambyter isn't registering the foot switch press. But I'm guessing that isn't the issue because the midi learn is working. However, getting it set up to work right might shed light on some things if the above don't help.

    It would be good to know what the actions assigned to that widget are as well. A screenshot of the Action settings for that widget might be useful if none of the above helps.

  • espiegel123espiegel123

    @wim: i think all we see of streambyter's monitor is the timestamp . And that the cc is on channel 1. the window is too narrow to see the control number or value.

    there is also a Sysex value being sent by the pedal.

    @Jojo : we could almost certainly help you get it straightened out. but don't have enough info to know what was going on. if your pedal has an option to ignore midi input, i would set it up to do so.

  • JojoJojo

    @wim said:
    That's really hard to follow. Here's what I think I'm seeing:

    1. Turn on MIDI Learn and tap the Rec/Play/Stop widget
    2. Tap the foot switch and it registers CC 16, hold
    3. Manually change the action to On/Off
    4. Oddly no action shows. Normally it should say "Press" by default
    5. Close down midi learn and try triggering the widget with the foot pedal.
    6. Streambyter shows activity, but not the CC 16 from the foot pedal. Perhaps it doesn't have its midi input set properly?
    7. The widget doesn't trigger? Or, it triggers, but it doesn't do what you expect?

    I'm not clear what's coming from the Vocalive pedal, but it seems like you probably don't want On/Off for the setting in #3 above. That should probably be On.

    Point 4 is most likely the key. I don't know how you got to the point where it doesn't show anything for the Action. I've never seen that. If you can, try setting that to Press by tapping the arrow next to.

    Streambyter isn't registering the foot switch press. But I'm guessing that isn't the issue because the midi learn is working. However, getting it set up to work right might shed light on some things if the above don't help.

    It would be good to know what the actions assigned to that widget are as well. A screenshot of the Action settings for that widget might be useful if none of the above helps.

    So, sort of, 1-3 are correct... But for point 4, If I press ‘new’ after 1-3 and then the back arrow it shows the binding as ‘press’…strange, I know. But, it seems to be set properly. I’ve tried the ‘on/off’ setting and ‘on’. Streambyter actually IS registering the press and it triggers it as an ‘on’ signal one press, then an ‘off’ the next. So, I would think ‘on/off’ would give me the most consistent performance….But the widget isn’t registering it, even though streambyter is showing the signal passing through.

    Streambyter’s sysex message actually happens when I simply pressed the widget with my finger at the end to show that the widget is set up properly…also, I should note that with this exact setup, I can setup my IK Blueboard to trigger the widgets properly (sort of)…I’m not a huge fan of the soft pedals for triggering loops and it was still a little buggy every once in awhile.

  • JojoJojo

    @espiegel123 said:
    @wim: i think all we see of streambyter's monitor is the timestamp . And that the cc is on channel 1. the window is too narrow to see the control number or value.

    there is also a Sysex value being sent by the pedal.

    @Jojo : we could almost certainly help you get it straightened out. but don't have enough info to know what was going on. if your pedal has an option to ignore midi input, i would set it up to do so.

    Thanks for responding! I said this in my last message to @wim, but the sysex message appears when I just straight up press the widget on screen at the end in order to show that it’s set up to record a ‘selected’ loop. The proper cc shows up from the pedal according to Streambyter, but it won’t trigger it. However, I can seem to get my IK Blueboard to work…just not my Voicelive 3 or my Airturn 200 s-4

  • wimwim

    @Jojo said:

    @espiegel123 said:
    @wim: i think all we see of streambyter's monitor is the timestamp . And that the cc is on channel 1. the window is too narrow to see the control number or value.

    there is also a Sysex value being sent by the pedal.

    @Jojo : we could almost certainly help you get it straightened out. but don't have enough info to know what was going on. if your pedal has an option to ignore midi input, i would set it up to do so.

    Thanks for responding! I said this in my last message to @wim, but the sysex message appears when I just straight up press the widget on screen at the end in order to show that it’s set up to record a ‘selected’ loop. The proper cc shows up from the pedal according to Streambyter, but it won’t trigger it. However, I can seem to get my IK Blueboard to work…just not my Voicelive 3 or my Airturn 200 s-4

    Is the BlueBoard sending CCs or Notes?

  • ecce_celloecce_cello

    Holly shit!! Finallyyyyyyyyyyy
    AAAAAHHHHHHHHHHHHHHHHHHHHHHHH

    Congrats Michael! I thought you would keep on developing it until you become grandpa. Sick perfectionist!!

    I was one of the first ones to get Loopy 12 years ago or so. Loopy changed my life and my work. Now I am doing other things in my life besides looping, but I will download it anyway!!

    Wwwaaaaaaawwwwwww

  • echooperaechoopera

    Well this is starting to happen in a big way and i love it. Knobs+Pads+Synths+Chords+Drums+Samples+Loops

    YES!!

Sign In or Register to comment.