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.

Odessa (LIVE - IT FINALLY HAPPENED!)

13233343537

Comments

  • trying to use odessa baseline and send it out to apps outside of aum. If i send out via virtual midi out, or point midi at the app itself, nothing seems to be coming out of aum! am i missing something? also, the playhead in baseline disappears randomly, even though aum play button is engaged? need help. thanks guys
    .

  • edited November 2017

    @eross said:
    trying to use odessa baseline and send it out to apps outside of aum. If i send out via virtual midi out, or point midi at the app itself, nothing seems to be coming out of aum! am i missing something? also, the playhead in baseline disappears randomly, even though aum play button is engaged? need help. thanks guys
    .

    I think you might be mixing up outputs and inputs here? In the screenshot, you haven't connected Odessa Bassline to SynthMaster player. Also, you have connected it to itself, which might not be a good idea.

    Note that "AUM" destination is a virtual midi destination, that other apps can send to to get midi into AUM, not the other way around. So outside of AUM it's a destination, and inside the AUM matrix it's a source that you can connect to other destinations (external as well as internal, but it's mainly/only meant for connecting to internal destinations).

  • @j_liljedahl said:

    @eross said:
    trying to use odessa baseline and send it out to apps outside of aum. If i send out via virtual midi out, or point midi at the app itself, nothing seems to be coming out of aum! am i missing something? also, the playhead in baseline disappears randomly, even though aum play button is engaged? need help. thanks guys
    .

    I think you might be mixing up outputs and inputs here? In the screenshot, you haven't connected Odessa Bassline to SynthMaster player. Also, you have connected it to itself, which might not be a good idea.

    Note that "AUM" destination is a virtual midi destination, that other apps can send to to get midi into AUM, not the other way around. So outside of AUM it's a destination, and inside the AUM matrix it's a source that you can connect to other destinations (external as well as internal, but it's mainly/only meant for connecting to internal destinations).

    i just tried this setting still no luck.

  • @j_liljedahl said:

    @eross said:
    trying to use odessa baseline and send it out to apps outside of aum. If i send out via virtual midi out, or point midi at the app itself, nothing seems to be coming out of aum! am i missing something? also, the playhead in baseline disappears randomly, even though aum play button is engaged? need help. thanks guys
    .

    I think you might be mixing up outputs and inputs here? In the screenshot, you haven't connected Odessa Bassline to SynthMaster player. Also, you have connected it to itself, which might not be a good idea.

    Note that "AUM" destination is a virtual midi destination, that other apps can send to to get midi into AUM, not the other way around. So outside of AUM it's a destination, and inside the AUM matrix it's a source that you can connect to other destinations (external as well as internal, but it's mainly/only meant for connecting to internal destinations).

    i just tried this setting still no luck. also no matter how i set it up. no e of the synth apps outiside of aum can see aum as a midi input source. is midi coming out of aum not an option? I’m sure it’s just some simple setting i’m missing.

  • @eross said:

    To get midi out of AUM you have to use the AUM matrix, so send from a source in the AUM matrix to a virtual port in another app (which will appear in the matrix if the app supports sending to virtual ports) The AUM matrix will see any core midi ports which are open in the background.

    So the "AUM port" is for receiving midi only and not for sending to other apps.

  • @eross said:

    @j_liljedahl said:

    @eross said:
    trying to use odessa baseline and send it out to apps outside of aum. If i send out via virtual midi out, or point midi at the app itself, nothing seems to be coming out of aum! am i missing something? also, the playhead in baseline disappears randomly, even though aum play button is engaged? need help. thanks guys
    .

    I think you might be mixing up outputs and inputs here? In the screenshot, you haven't connected Odessa Bassline to SynthMaster player. Also, you have connected it to itself, which might not be a good idea.

    Note that "AUM" destination is a virtual midi destination, that other apps can send to to get midi into AUM, not the other way around. So outside of AUM it's a destination, and inside the AUM matrix it's a source that you can connect to other destinations (external as well as internal, but it's mainly/only meant for connecting to internal destinations).

    i just tried this setting still no luck. also no matter how i set it up. no e of the synth apps outiside of aum can see aum as a midi input source. is midi coming out of aum not an option? I’m sure it’s just some simple setting i’m missing.

    AUM does not have or need a MIDI output port, you can route to any MIDI destination in the matrix. You will never see "AUM" as a midi source in any other app.

    The routing of Odessa Bassline -> Synthmaster virtual port as you did is correct. The reason that it's not working must be something else: is the transport in AUM playing? is Synthmaster configured to receive on its virtual port? Do you have a pattern in Bassline?

  • @eross said:

    @j_liljedahl said:

    @eross said:
    trying to use odessa baseline and send it out to apps outside of aum. If i send out via virtual midi out, or point midi at the app itself, nothing seems to be coming out of aum! am i missing something? also, the playhead in baseline disappears randomly, even though aum play button is engaged? need help. thanks guys
    .

    I think you might be mixing up outputs and inputs here? In the screenshot, you haven't connected Odessa Bassline to SynthMaster player. Also, you have connected it to itself, which might not be a good idea.

    Note that "AUM" destination is a virtual midi destination, that other apps can send to to get midi into AUM, not the other way around. So outside of AUM it's a destination, and inside the AUM matrix it's a source that you can connect to other destinations (external as well as internal, but it's mainly/only meant for connecting to internal destinations).

    i just tried this setting still no luck. also no matter how i set it up. no e of the synth apps outiside of aum can see aum as a midi input source. is midi coming out of aum not an option? I’m sure it’s just some simple setting i’m missing.

    Sending to an app outside AUM puts you at the mercy of the various implementations of MIDI on iOS.

    In the case of SynthMaster P, I usually need MidiFire or a similar app to communicate with SynthMaster, even when I’m hosting it as IAA in other apps.

  • @Fruitbat1919 said:
    Here’s AUM with Odessa Baseline sending midi to SynthMaster Player:



    I did it!!! thanks to your screenshots. I uncheck abelton Link button, and it worked! I new it was something simple i was missing. you guys are awesome.... thanks.

  • @eross said:

    @Fruitbat1919 said:
    Here’s AUM with Odessa Baseline sending midi to SynthMaster Player:



    I did it!!! thanks to your screenshots. I uncheck abelton Link button, and it worked! I new it was something simple i was missing. you guys are awesome.... thanks.

    Obviously be aware you may need to change Players settings if you send any other midi about, because it would pick up midi on any channel as I have it set in the pics. Glad it helped :)

  • This AUM is begging for a midi recorder... or maybe I am missing something here...

  • Ok so I looked on page 11 of this. But I still can’t get Odessa to trigger ElasticDrums. Can some one post that or help? Also maybe I should look at the dang manuals.

  • edited November 2017

    @Chaztrip said:
    Ok so I looked on page 11 of this. But I still can’t get Odessa to trigger ElasticDrums. Can some one post that or help? Also maybe I should look at the dang manuals.

    I was just fooling around with this today- In ED: in the midi input list select ED itself for notes...

    In AUM u can select EDs channel in midi routing

  • wimwim
    edited November 2017

    @Littlewoodg said:

    @Chaztrip said:
    Ok so I looked on page 11 of this. But I still can’t get Odessa to trigger ElasticDrums. Can some one post that or help? Also maybe I should look at the dang manuals.

    I was just fooling around with this today- In ED: in the midi input list select ED itself for notes...

    In AUM u can select EDs channel in midi routing

    Bloody hell it's hard to get this stable with ED. Setting it up as you suggested, I also needed to move it to a blank pattern, as there doesn't seem to be any way of keeping ED from playing as soon as you hit play in AUM. I started with just a simple four on the floor kick, and only about every 3rd note sounded in ED. I'm cool with just using ED's built in sequencer, so no loss for me, but ED seems buggered up as a midi receiver IMO.

  • @wim said:

    @Littlewoodg said:

    @Chaztrip said:
    Ok so I looked on page 11 of this. But I still can’t get Odessa to trigger ElasticDrums. Can some one post that or help? Also maybe I should look at the dang manuals.

    I was just fooling around with this today- In ED: in the midi input list select ED itself for notes...

    In AUM u can select EDs channel in midi routing

    Bloody hell it's hard to get this stable with ED. Setting it up as you suggested, I also needed to move it to a blank pattern, as there doesn't seem to be any way of keeping ED from playing as soon as you hit play in AUM. I started with just a simple four on the floor kick, and only about every 3rd note sounded in ED. I'm cool with just using ED's built in sequencer, so no loss for me, but ED seems buggered up as a midi receiver IMO.

    Yes me too. I would like to set up a “kit” in ED and not have it move on to patterns and have Odessa play that kit.

  • I have a hard time trying to send any midi from anywhere to ED.

  • wimwim
    edited November 2017

    @Chaztrip said:

    @wim said:

    @Littlewoodg said:

    @Chaztrip said:
    Ok so I looked on page 11 of this. But I still can’t get Odessa to trigger ElasticDrums. Can some one post that or help? Also maybe I should look at the dang manuals.

    I was just fooling around with this today- In ED: in the midi input list select ED itself for notes...

    In AUM u can select EDs channel in midi routing

    Bloody hell it's hard to get this stable with ED. Setting it up as you suggested, I also needed to move it to a blank pattern, as there doesn't seem to be any way of keeping ED from playing as soon as you hit play in AUM. I started with just a simple four on the floor kick, and only about every 3rd note sounded in ED. I'm cool with just using ED's built in sequencer, so no loss for me, but ED seems buggered up as a midi receiver IMO.

    Yes me too. I would like to set up a “kit” in ED and not have it move on to patterns and have Odessa play that kit.

    I'm pretty sure that issue is due to midi mappings. You probably have the notes that Odessa is sending mapped to trigger patterns. You can tell by going to the jam page, then settings, and turning on Midi learn. If you see note numbers in the "pat" boxes, then check to see if those are the same that Odessa is sending. If so then try mapping to some other notes.

    But ... that's just one of the hurdles. Midi in to ED is problematic (searched long and hard for a polite word there...).

    Oh ... and you need to be on a pattern with no notes in it, as I mentioned earlier.

  • @brambos said:

    @LeonLeroy said:
    bass is def no cooperating consistently in aum

    Can you elaborate please, so I can have a look into it?

    i got it going. had to hit play in aum

  • edited November 2017

    @wim said:

    @Littlewoodg said:

    @Chaztrip said:
    Ok so I looked on page 11 of this. But I still can’t get Odessa to trigger ElasticDrums. Can some one post that or help? Also maybe I should look at the dang manuals.

    I was just fooling around with this today- In ED: in the midi input list select ED itself for notes...

    In AUM u can select EDs channel in midi routing

    Bloody hell it's hard to get this stable with ED. Setting it up as you suggested, I also needed to move it to a blank pattern, as there doesn't seem to be any way of keeping ED from playing as soon as you hit play in AUM. I started with just a simple four on the floor kick, and only about every 3rd note sounded in ED. I'm cool with just using ED's built in sequencer, so no loss for me, but ED seems buggered up as a midi receiver IMO.

    ED can be a pain in the neck, in terms of interconnectivity. When I use it, it’s usually as standalone, to build loops for export, to AUMs file player in particular

    Speaking of drumsynth It was a pleasant discovery to host DM-2 in AUM, with the map Odessa includes for it. (I’d never been able to host DM-2 in my preferred hosts and had deleted it, until I noticed the Odessa map.) The map and hosting is smooth with iElectribe as well though here again you have to clear the song or make blank presets. There’s cc mapping’s for iElectribe available as well for use with LFO and XY setups http://www.korguser.net/ielectribe/en/midi.html

    I haven’t tried the map for Seekbeats, yet.

  • @wim said:

    @Chaztrip said:

    @wim said:

    @Littlewoodg said:

    @Chaztrip said:
    Ok so I looked on page 11 of this. But I still can’t get Odessa to trigger ElasticDrums. Can some one post that or help? Also maybe I should look at the dang manuals.

    I was just fooling around with this today- In ED: in the midi input list select ED itself for notes...

    In AUM u can select EDs channel in midi routing

    Bloody hell it's hard to get this stable with ED. Setting it up as you suggested, I also needed to move it to a blank pattern, as there doesn't seem to be any way of keeping ED from playing as soon as you hit play in AUM. I started with just a simple four on the floor kick, and only about every 3rd note sounded in ED. I'm cool with just using ED's built in sequencer, so no loss for me, but ED seems buggered up as a midi receiver IMO.

    Yes me too. I would like to set up a “kit” in ED and not have it move on to patterns and have Odessa play that kit.

    I'm pretty sure that issue is due to midi mappings. You probably have the notes that Odessa is sending mapped to trigger patterns. You can tell by going to the jam page, then settings, and turning on Midi learn. If you see note numbers in the "pat" boxes, then check to see if those are the same that Odessa is sending. If so then try mapping to some other notes.

    But ... that's just one of the hurdles. Midi in to ED is problematic (searched long and hard for a polite word there...).

    Oh ... and you need to be on a pattern with no notes in it, as I mentioned earlier.

    Yeah just checked, I can’t get ED to work without that running and having a blank sequence. Almost not worth the hassle setting that up.

  • New BM3 beta has AUv3 midi support. Might not make it into 3.0.6 retail but available for testing now. Looking forward to testing it shortly.

  • @MonzoPro said:
    Yeah just checked, I can’t get ED to work without that running and having a blank sequence. Almost not worth the hassle setting that up.

    My thoughts too. ED's sequence is plenty good itself, so no huge loss. But it's always kind of annoying when stuff doesn't work like it should.

  • 1.0.1 update was just rejected by Apple because they couldn't find any functionality in standalone mode. So it looks like I'll have to waste time adding some b.s. feature in standalone mode to keep the reviewers happy.

    Not impressed with Apple lately. :/

  • @brambos said:
    1.0.1 update was just rejected by Apple because they couldn't find any functionality in standalone mode. So it looks like I'll have to waste time adding some b.s. feature in standalone mode to keep the reviewers happy.

    Not impressed with Apple lately. :/

    I vote you put in a side scrolling game module that just happens to also send midi, so you can write the score while you score.

  • @aaronpc said:

    @brambos said:
    1.0.1 update was just rejected by Apple because they couldn't find any functionality in standalone mode. So it looks like I'll have to waste time adding some b.s. feature in standalone mode to keep the reviewers happy.

    Not impressed with Apple lately. :/

    I vote you put in a side scrolling game module that just happens to also send midi, so you can write the score while you score.

    Damn beaten to the punch....I was thinking snake!

  • @brambos said:
    1.0.1 update was just rejected by Apple because they couldn't find any functionality in standalone mode. So it looks like I'll have to waste time adding some b.s. feature in standalone mode to keep the reviewers happy.

    Not impressed with Apple lately. :/

    So which genius let v1.0 out the door with "non-functional standalone mode" as is? Unbelievable...

  • That does seriously suck, though. Wish you could point them to a 37 page thread somewhere that could illuminate them on the app's functionality.

  • @brambos said:
    1.0.1 update was just rejected by Apple because they couldn't find any functionality in standalone mode. So it looks like I'll have to waste time adding some b.s. feature in standalone mode to keep the reviewers happy.

    Not impressed with Apple lately. :/

    Hows about a page to inject our own templates in to rhythm :)
    On a completely separate note, is there anyway to save our own note templates for rhythm ?

  • @Samplemunch said:

    @brambos said:
    1.0.1 update was just rejected by Apple because they couldn't find any functionality in standalone mode. So it looks like I'll have to waste time adding some b.s. feature in standalone mode to keep the reviewers happy.

    Not impressed with Apple lately. :/

    Hows about a page to inject our own templates in to rhythm :)
    On a completely separate note, is there anyway to save our own note templates for rhythm ?

    Not discreetly but you can save AU presets. That includes the sequencer so just leave it blank to use it as a template.

Sign In or Register to comment.