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

1235»

Comments

  • Matt_Fletcher_2000Matt_Fletcher_2000
    edited December 2016

    @u0421793 said:
    Something's just occurred to me. How on earth do I get a user patch off this synth, for example, to make available to someone else?

    I'd be interested if you find the answer to this.

    I would absolutely love a secondary market (free or paid) of patches for this thing.

    I know that right now I wouldn't be able to port them into Gadget. But I could copy the settings of any patches I wanted to use in Gadget fairly easily.

  • CarnbotCarnbot

    @Matt_Fletcher_2000 said:

    @u0421793 said:
    Something's just occurred to me. How on earth do I get a user patch off this synth, for example, to make available to someone else?

    I'd be interested if you find the answer to this.

    I would absolutely love a secondary market (free or paid) of patches for this thing.

    I know that right now I wouldn't be able to port them into Gadget. But I could copy the settings of any patches I wanted to use in Gadget fairly easily.

    It seems like the old fashioned way only, by sharing an image of the patch settings. Whether this is because Korg want it to be exactly like the hardware in this regard is open for question. I'd be interested in the hardware but would have liked the option to automate cc via midi which you can't unfortunately.

  • Patric_BatemanPatric_Bateman

    So the iM1 and the iWavestation can import patches from the actual Hardware, but ODYSSEi can´t import patches from Lexington o0

  • u0421793u0421793

    @Patric_Bateman said:
    So the iM1 and the iWavestation can import patches from the actual Hardware, but ODYSSEi can´t import patches from Lexington o0

    Worse, yours can't import a patch from mine.

  • Aud_iOSAud_iOS

    @Telefunky said:
    Korg re-vitalized the ARP company, they didn't just buy the brand.
    They did this for the hardware, which received quite positive feedback, so a module version without keyboard was added to the line.

    The step into the app market may be an attempt to gain additional revenues, but (imho) it mainly serves as a promo for the hardware.
    Seriously - app sales as a business works with gimmicks, but not with maintained software. Even Korg can afford it only because they already HAD the modelling ready and they can re-use touch interface experience in other hardware devices.

    Yes! Platform economics 101 at play - and why I don't buy into Korg apps... other
    co's do the same, but with the softer touch of soc. Media interactions, and throwing some bones toward openness. Korg makes me feel like it's the 80's and I'm being six sigma'ed under the grey smoke-stacked skies.

  • dysamoriadysamoria

    It might be redundant of me to say this, but for every person here who feels something is missing, broken, or difficult to operate in a Korg app, they should go directly to Korg and tell them. If you don't have an account over here:

    https://support.korguser.net/hc/en-us/community/topics

    and you are a Korg customer, then go make an account and speak up.

    I've been thinking that it might be a good idea to start submitting some things as bug reports over here:
    https://support.korguser.net/hc/en-us/requests/new

    For example: the fact that almost every Korg app works as an IAA generator instead of an IAA synth. Clearly their contractors chose the wrong API when they implemented IAA on SYNTHS. In fact, I might go do exactly this...

  • realdavidairealdavidai

    @dysamoria said:
    It might be redundant of me to say this, but for every person here who feels something is missing, broken, or difficult to operate in a Korg app, they should go directly to Korg and tell them. If you don't have an account over here:

    https://support.korguser.net/hc/en-us/community/topics

    and you are a Korg customer, then go make an account and speak up.

    I've been thinking that it might be a good idea to start submitting some things as bug reports over here:
    https://support.korguser.net/hc/en-us/requests/new

    For example: the fact that almost every Korg app works as an IAA generator instead of an IAA synth. Clearly their contractors chose the wrong API when they implemented IAA on SYNTHS. In fact, I might go do exactly this...

    Godspeed :)

  • Patric_BatemanPatric_Bateman

    @dysamoria said:
    It might be redundant of me to say this, but for every person here who feels something is missing, broken, or difficult to operate in a Korg app, they should go directly to Korg and tell them. If you don't have an account over here:

    https://support.korguser.net/hc/en-us/community/topics

    and you are a Korg customer, then go make an account and speak up.

    I've been thinking that it might be a good idea to start submitting some things as bug reports over here:
    https://support.korguser.net/hc/en-us/requests/new

    For example: the fact that almost every Korg app works as an IAA generator instead of an IAA synth. Clearly their contractors chose the wrong API when they implemented IAA on SYNTHS. In fact, I might go do exactly this...

    I already started a thread there, but it can never hurt! Thx 4 your effort!

Sign In or Register to comment.

© Vanilla Keystone Theme 2025