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.

KORG Arp ODYSSEi frustration thread

With the feint hope of someone who can administer change reading this, i thought i start this thread out of love for this great synth. I was just playing some patches that i created when i got this synth, and still am so impressed by the amazing sound of it. It would be a damn crime if this synth would get lost like so many others, just because of some mistakes that should be simple to fix. I´m leaving Gadget and the inability to share patches with Lexington out on purpose, since it´s a separate topic.

  1. The user interface. The iPad layout is BAD, on an Air 2. Can´t even imagine how it is on the mini. The faders are way too short to handle properly. I´ve read of users actually using the pen on the iPad Pro, that´s how bad it is. The solution is so simple, get rid of the stupid, useless keyboard, and scale the damn thing to the whole screen. The overlaying Keyboard or Kaoss Pads are blocking vital controls already, so it wouldn´t matter at all if you just keep the overlaying layout of those, it would even make more sense. Or shrink it to dimensions similar to the iPhone Keyboard. Right now it doesn´t make sense at all.
  2. The IAA Integration into Cubasis is bad. Doesn´t work as MIDI track, you have to setup an audio track with IAA input. And a separate MIDI track to route MIDI from Cubasis to ODYSSEi. It´s a stupid hassle and just not acceptable for an app that is little over one month old. The problem doesn´t exist with iM1 or iWavestation, on iWavestation there´s even the IAA Badge to remote control Cubasis.
  3. The worst one of all: Tempo Sync. How do you build in a massive step sequencer / arpeggiator with tremendous capabilities, when the whole synth isn´t able to sync to MIDI-Clock, Ableton Link, WIST etc. etc. NOTHING. IT SYNCS TO NOT A DAMN THING. Of course the LFO doesn´t sync to MIDI either. Who green lights such an atrocity?

Those are the three things that bother me the most. I don´t care about the 20 bucks, i love the sound of this synth, and i want to use it. It is at 2 1/2 stars at the moment in the german App Store, and it is a damn shame.

I´d like to invite anyone who shares my grievances to post directly on the KORG Forum: https://support.korguser.net/hc/en-us/community/posts/115000024766-Frustration-with-ODYSSEi-wasted-potential Thanks!

What do you guys think?

KORG ODYSSEi problems
  1. Do you share the complaints of the OP?29 votes
    1. No, ODYSSEi is fine. L2p.
      27.59%
    2. Some of it bothers me, but i suck it up.
      48.28%
    3. It pisses me off that bad, so i don´t use it as often, especially in the AUv3 age.
      24.14%
«1345

Comments

  • Same here. Soundwise it's probably my favorite ios synth. Still not comfortable syncing up external synths to auria or cubasis in general so i wasn't aware that the sync is just nonexistent with ODYSSEi. Hope this gets sorted although korg seems to ignore a lot of stuff.

  • Have faith, 2 months ago I informed they had a problem with Gadget not updated to latest Audiocopy SDK and they updated it. Other people complained about Odyssei being out of tune and they updated it. Have faith!

  • I tend to agree, point 2 in particular. It's a shame as it's a fantastic synth otherwise. Also a shame that it's lovely Arp features aren't available in Gadget.

  • wimwim
    edited December 2016

    Need a fourth option:

    • I agree with the main points but without the ranting

    [Edit] Crappy thread title IMO as well. Besides this post, I think I prefer to stay out of the discussion so as to not promote such an inflammatory topic.

  • edited December 2016

    @Igneous1 said:
    I tend to agree, point 2 in particular. It's a shame as it's a fantastic synth otherwise. Also a shame that it's lovely Arp features aren't available in Gadget.

    This is the most baffling to me, the Arp features are very powerful, but they are severely limited in not being able to tempo sync it.

  • edited December 2016

    @AlexB said:
    Have faith, 2 months ago I informed they had a problem with Gadget not updated to latest Audiocopy SDK and they updated it. Other people complained about Odyssei being out of tune and they updated it. Have faith!

    I hope you´re right! But i´m not so confident, especially with the user interface. The fixed keyboard is just incredibly bad design. I like to compare ODYSSEi to two other legendary synths from about that era. iVCS and Model 15, they both have beautiful solutions how to make the best use of screen real estate with floating keyboard etc.

  • AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

  • I can see it is not ideal. I however am willing to put up with its problems for the sound. Bit like I always put up with most of my hardware that had problems for their sound.

    Yeah it's helpful in some ways to air our perceived issues with software, to express our concerns. I'm not sure I see the point of the vote though as without that your comments were reasonably balanced.

    I do have faith that Korg will fix some of the issues in time. I am however not going to wait, the app is still great for many uses and those that give really low reviews are giving a slightly scewed impression IMO.

    In retrospect, I would still pay the initial price for the app, even if those issues never get fixed.

  • @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

  • @Fruitbat1919 said:
    I can see it is not ideal. I however am willing to put up with its problems for the sound. Bit like I always put up with most of my hardware that had problems for their sound.

    Yeah it's helpful in some ways to air our perceived issues with software, to express our concerns. I'm not sure I see the point of the vote though as without that your comments were reasonably balanced.

    I do have faith that Korg will fix some of the issues in time. I am however not going to wait, the app is still great for many uses and those that give really low reviews are giving a slightly scewed impression IMO.

    In retrospect, I would still pay the initial price for the app, even if those issues never get fixed.

    Im genuinely interested in what others think. I never rule out the user as the source of the problem (=me). Sounds like Answer 2 suits you nicely, thanks for participating!

  • @Patric_Bateman said:

    @Fruitbat1919 said:
    I can see it is not ideal. I however am willing to put up with its problems for the sound. Bit like I always put up with most of my hardware that had problems for their sound.

    Yeah it's helpful in some ways to air our perceived issues with software, to express our concerns. I'm not sure I see the point of the vote though as without that your comments were reasonably balanced.

    I do have faith that Korg will fix some of the issues in time. I am however not going to wait, the app is still great for many uses and those that give really low reviews are giving a slightly scewed impression IMO.

    In retrospect, I would still pay the initial price for the app, even if those issues never get fixed.

    Im genuinely interested in what others think. I never rule out the user as the source of the problem (=me). Sounds like Answer 2 suits you nicely, thanks for participating!

    Yeah about right for me. As you say it's good to get opinion. I have done many votes on here myself. I have found however that most of the vote questions are often biased in some ways towards what we already perceive. I've always been surprised at then what some of the forum members come up with in comments. So for myself the vote is probably not worth much, but it's the great comments some members will surprise us all with :)

  • I love it cause it sounds great. I mean, it sounds really great to me! This and Model 15. Kick-ass sound. Love it.
    Also got Korg's ipolysix, that one sounds great too! Polyphonic analog for the win!

    I guess when I'm so taken with the sound, I can't find it within me to worry much about any of the other features.

  • @Fruitbat1919 said:

    @Patric_Bateman said:

    @Fruitbat1919 said:
    I can see it is not ideal. I however am willing to put up with its problems for the sound. Bit like I always put up with most of my hardware that had problems for their sound.

    Yeah it's helpful in some ways to air our perceived issues with software, to express our concerns. I'm not sure I see the point of the vote though as without that your comments were reasonably balanced.

    I do have faith that Korg will fix some of the issues in time. I am however not going to wait, the app is still great for many uses and those that give really low reviews are giving a slightly scewed impression IMO.

    In retrospect, I would still pay the initial price for the app, even if those issues never get fixed.

    Im genuinely interested in what others think. I never rule out the user as the source of the problem (=me). Sounds like Answer 2 suits you nicely, thanks for participating!

    Yeah about right for me. As you say it's good to get opinion. I have done many votes on here myself. I have found however that most of the vote questions are often biased in some ways towards what we already perceive. I've always been surprised at then what some of the forum members come up with in comments. So for myself the vote is probably not worth much, but it's the great comments some members will surprise us all with :)

    I think it´s a great quick way for anyone to express their opinion, even if they´re not in the mood to post a comment..

  • @Patric_Bateman said:

    @Fruitbat1919 said:

    @Patric_Bateman said:

    @Fruitbat1919 said:
    I can see it is not ideal. I however am willing to put up with its problems for the sound. Bit like I always put up with most of my hardware that had problems for their sound.

    Yeah it's helpful in some ways to air our perceived issues with software, to express our concerns. I'm not sure I see the point of the vote though as without that your comments were reasonably balanced.

    I do have faith that Korg will fix some of the issues in time. I am however not going to wait, the app is still great for many uses and those that give really low reviews are giving a slightly scewed impression IMO.

    In retrospect, I would still pay the initial price for the app, even if those issues never get fixed.

    Im genuinely interested in what others think. I never rule out the user as the source of the problem (=me). Sounds like Answer 2 suits you nicely, thanks for participating!

    Yeah about right for me. As you say it's good to get opinion. I have done many votes on here myself. I have found however that most of the vote questions are often biased in some ways towards what we already perceive. I've always been surprised at then what some of the forum members come up with in comments. So for myself the vote is probably not worth much, but it's the great comments some members will surprise us all with :)

    I think it´s a great quick way for anyone to express their opinion, even if they´re not in the mood to post a comment..

    That's cool then B)

  • edited December 2016

    @RulesOfBlazon said:
    I love it cause it sounds great. I mean, it sounds really great to me! This and Model 15. Kick-ass sound. Love it.
    Also got Korg's ipolysix, that one sounds great too! Polyphonic analog for the win!

    I guess when I'm so taken with the sound, I can't find it within me to worry much about any of the other features.

    Honestly right now i wish it wouldn´t sound that great. I wish it would sound just kinda "meh", so i could forget about the App and delete it. Plenty of other "fish in the sea". But i can´t, i love the sound. I want it!

  • edited December 2016

    Well I bought it for my iPhone and
    A. Turns out I didn't need another synth. That's on me though, but
    B. The graphics/resolution/I dunno what are strangely horrible. Very straining on the eyes, like the resolution is poor or something, hard to tell. Perhaps it's the color combo, but I can barely stand to look at it before my eyes feel strained. A problem I do not have with iWavestation and gadget, both on iPhone. Oddly enough, Lexington has the same problem within gadget.

  • @db909 said:
    Well I bought it for my iPhone and
    A. Turns out I didn't need another synth. That's on me though, but
    B. The graphics/resolution/I dunno what are strangely horrible. Very straining on the eyes, like the resolution is poor or something, hard to tell. Perhaps it's the color combo, but I can barely stand to look at it before my eyes feel strained. A problem I do not have with iWavestation and gadget, both on iPhone. Oddly enough, Lexington has the same problem within gadget.

    Well at least there are different colors available, for just 5 bucks you can relieve the pain from your eyes :-)

  • @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

  • edited December 2016

    @philowerx said:

    @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

    Gold star for @philowerx

    PS: What, exactly, is the difference between a "generator" and an "instrument"? AUM frequently gives me the option to choose. I always choose "instrument," mostly because it sounds more, I don't know, pure. (I'd rather play an instrument than a generator, right?)

  • @Patric_Bateman said:
    2. The IAA Integration into Cubasis is bad. Doesn´t work as MIDI track, you have to setup an audio track with IAA input. And a separate MIDI track to route MIDI from Cubasis to ODYSSEi. It´s a stupid hassle and just not acceptable for an app that is little over one month old. The problem doesn´t exist with iM1 or iWavestation, on iWavestation there´s even the IAA Badge to remote control Cubasis.

    Yes that´s exactly what i´m complaining about :D But the distinction between IAA Generators and Instruments is very interesting, i always wondered how there could be two different implementations of supposedly the same standard in the same App (Cubasis).

  • @ExAsperis99 said:

    @philowerx said:

    @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

    Gold star for @philowerx

    PS: What, exactly, is the difference between a "generator" and an "instrument"? AUM frequently gives me the option to choose. I always choose "instrument," mostly because it sounds more, I don't know, pure. (I'd rather play an instrument than a generator, right?)

    IAA Generator is Audio only, IAA Instrument is Audio & MIDI. IAA Effect is Audio only, IAA Music Effect is Audio & MIDI.

  • @philowerx said:

    @ExAsperis99 said:

    @philowerx said:

    @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

    Gold star for @philowerx

    PS: What, exactly, is the difference between a "generator" and an "instrument"? AUM frequently gives me the option to choose. I always choose "instrument," mostly because it sounds more, I don't know, pure. (I'd rather play an instrument than a generator, right?)

    IAA Generator is Audio only, IAA Instrument is Audio & MIDI. IAA Effect is Audio only, IAA Music Effect is Audio & MIDI.

    Thank you so much.

  • edited December 2016

    @philowerx said:

    @ExAsperis99 said:

    @philowerx said:

    @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

    Gold star for @philowerx

    PS: What, exactly, is the difference between a "generator" and an "instrument"? AUM frequently gives me the option to choose. I always choose "instrument," mostly because it sounds more, I don't know, pure. (I'd rather play an instrument than a generator, right?)

    IAA Generator is Audio only, IAA Instrument is Audio & MIDI. IAA Effect is Audio only, IAA Music Effect is Audio & MIDI.

    That makes perfect sense now, ty!. Why would KORG use IAA Instrument for some synths (iM1, iWavestation) and IAA Generator for others? And is the IAA "Badge" part of a proper implementation?

  • edited December 2016

    Been there done that, which is why all my non-AU apps have been permanently retired. IAA militates against creativity.

  • @realdavidai said:
    Been there done that, which is why all my non-AU apps have been permanently retired. IAA militates against creativity.

    AUv3 would need fullscreen plugin support to really retire IAA, imagine Moog Model 15 in the AUv3 box? Kills any creativity.

  • @ExAsperis99 said:

    @philowerx said:

    @ExAsperis99 said:

    @philowerx said:

    @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

    Gold star for @philowerx

    PS: What, exactly, is the difference between a "generator" and an "instrument"? AUM frequently gives me the option to choose. I always choose "instrument," mostly because it sounds more, I don't know, pure. (I'd rather play an instrument than a generator, right?)

    IAA Generator is Audio only, IAA Instrument is Audio & MIDI. IAA Effect is Audio only, IAA Music Effect is Audio & MIDI.

    Thank you so much.

    Give this man ten thousand something or others.

  • @philowerx said:

    @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

    I have a special place where I put special things and I put this thing in that place. Thank you.

  • @Patric_Bateman said:

    @philowerx said:

    @ExAsperis99 said:

    @philowerx said:

    @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

    Gold star for @philowerx

    PS: What, exactly, is the difference between a "generator" and an "instrument"? AUM frequently gives me the option to choose. I always choose "instrument," mostly because it sounds more, I don't know, pure. (I'd rather play an instrument than a generator, right?)

    IAA Generator is Audio only, IAA Instrument is Audio & MIDI. IAA Effect is Audio only, IAA Music Effect is Audio & MIDI.

    That makes perfect sense now, ty!. Why would KORG use IAA Instrument for some synths (iM1, iWavestation) and IAA Generator for others? And is the IAA "Badge" part of a proper implementation?

    When you say IAA do you mean the IAA Transport in some IAA Instruments and Generators? The IAA Transport does show the app developer has a deeper understanding of coding for IAA. Unfortunately Apple doesn't have a IAA app vetting process so proper IAA implementation is completely up to each developer. Developing for IAA and MIDI has been largely shot in the dark as Apple provides very little support or documentation. In general IAA is better when you see IAA Instruments with IAA Transport or IAA Music Effects options.

  • @JohnnyGoodyear said:

    @philowerx said:

    @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

    I have a special place where I put special things and I put this thing in that place. Thank you.

    You're welcome!

  • @philowerx said:

    @Patric_Bateman said:

    @philowerx said:

    @ExAsperis99 said:

    @philowerx said:

    @Patric_Bateman said:

    @ExAsperis99 said:
    AS for No. 2. That's a known Korg bug, I believe. Every time I try to add Module or something by Korg, it doesn't show up as a midi instrument, and I have to do the trick workaround, which is either on the Cubasis forum (most likely) or the Korg forum. When I find it, I'll post the solution.

    It is very common among Korg Apps, but not the case on the iM1 and the iWavestation...

    Cubasis and IAA Generators
    Some IAAs don't fully follow the IAA spec as they were designed specifically for AudioBus but since AB joined the IAA protocol they will work as IAA Generators. Unlike other IAA Host, Cubasis handles IAA Generators differently than IAA Instruments. For IAA Generators in Cubasis:
    1) create an audio track
    2) click on routing
    3) click on mono input
    4) change it to "inter-app"
    5) choose your IAA Generator from this list (If your IAA Generator does not load, you'll need to start the IAA Generator app first then select from Cubasis)
    6) create a new MIDI track
    7) click on routing
    8) point it to your instrument
    9) also set the MIDI track instrument to no instrument
    (Otherwise you will hear both the Cubasis piano and your IAA)

    Gold star for @philowerx

    PS: What, exactly, is the difference between a "generator" and an "instrument"? AUM frequently gives me the option to choose. I always choose "instrument," mostly because it sounds more, I don't know, pure. (I'd rather play an instrument than a generator, right?)

    IAA Generator is Audio only, IAA Instrument is Audio & MIDI. IAA Effect is Audio only, IAA Music Effect is Audio & MIDI.

    That makes perfect sense now, ty!. Why would KORG use IAA Instrument for some synths (iM1, iWavestation) and IAA Generator for others? And is the IAA "Badge" part of a proper implementation?

    When you say IAA do you mean the IAA Transport in some IAA Instruments and Generators? The IAA Transport does show the app developer has a deeper understanding of coding for IAA. Unfortunately Apple doesn't have a IAA app vetting process so proper IAA implementation is completely up to each developer. Developing for IAA and MIDI has been largely shot in the dark as Apple provides very little support or documentation. In general IAA is better when you see IAA Instruments with IAA Transport or IAA Music Effects options.

    Yes that is exactly what i meant. I have a weird feeling that there´s a lot of code "recycling" going on at Korg, and some stuff just seems very outdated. The similarities of the iMS-20 and the ODYSSEi are just there, weirdly enough the ancient iMS-20 offers better handling due to zooming in, and rotary knobs that can actually be adjusted the way they should be. They all seem to have a very limited MIDI-Implementation. When in other Apps you could actually choose the MIDI-Device for Input, have a visual indicator for incoming clock, and so on.

Sign In or Register to comment.