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.

Bram Bos says, “sayonara” to iPhone

13

Comments

  • @CracklePot said:

    @u0421793 said:
    I’ve more or less stopped using my iPad Pro for anything useful other than browsing the interweb, since I got my iPhone 8 Plus. I do a lot of music on my iPhone (which is a new experience, as I’ve always been 100% android for phones up till now) and it is proving far more productive than my iPad is. I never take my iPad Pro out of the house, but with my iPhone 8 Plus I frequently almost miss my stop on the train several times every day because I’m engrossed in doing something in Gadget. When I get home, I’m over to Gadget on the Mac Mini, and the iPad Pro simply never gets a look in now.

    If I PM you my address, will you forward the Pro to me? :D

    Upon receipt of suitable monies, certainly.

  • edited March 2018
    The user and all related content has been deleted.
  • @Max23 said:
    makes sense,
    no headphone jack without adapter and a notch
    why support this?

    Bluetooth airpods. Not much lag, and lag is a total non-issue when working with Brambos apps. It's not like you are trying to play keyboards or pads in sync with other music - where slight lag can be really annoying.

  • edited March 2018
    The user and all related content has been deleted.
  • edited March 2018

    @Samu said:
    Can't help it but the 'notch' on the iPhone X is just awful by design and forcing developers to 'adapt' to it is just a stupid, stupid move.

    For productivity apps it's just a big WTF especially in landscape mode, when you rotate the screen on one side there's the notch and on the other side there's no notch. Apple needs to fire the person who decided to say OK to the notch and allow 'letter boxed' apps. Sorry Ive you've totally lost it...

    This time around Apple could learn a thing or two from Samsung...

    If the 'notch' is here to stay it's bad for everyone.
    (Let us just hope that the new iPads are 'notch free').

    Hahaha, you want apple to fire Jony Ive?. This is just so funny.

    While I don’t have the iPhone X (I’m neutral on it until I try one) what has Samsung done right? Avoid the notch by making the bezel bigger? That it’s all?

    I’ll give this to apple, the X design it’s bold and it’s not afraid, Apple probably did it to avoid looking like every premium android phone on the market, they all look the same from the front, the Samsung design it’s safer and not as striking, certainly not as distinctive, I can immediately tell when I see a person with an iphone X on the street. The s9 and note 8 get lost in a sea of sameness even if they’re premium phones. (Until the notch can disappear completely it’s here to stay, it’s new distinctive thing in iPhones like the home button used to be)

    I might hate the notch if I ever buy an iPhone X, either the looks or the software, but for now i think at least apple took the risk while Samsung and all other android OEMs played it safe and if the number of Chinese clones that are coming out right now it’s any proof I think apple succeeded, in 2014-2015 every new android phone on the market, even the first google pixel, looked like the iPhone 6.

  • The notch looks cheap. There, I said it.

  • Bloody hell if the new iPads have a notch it will thoroughly piss me off since I pretty much use them in landscape....

  • edited March 2018

    @gonekrazy3000 said:
    Bloody hell if the new iPads have a notch it will thoroughly piss me off

    A notch on an iPad would so much smaller relative to screen size. I’m thinking it would truly be a non-issue, because even on iPhone X it’s barely a problem.

  • @gonekrazy3000 said:
    Bloody hell if the new iPads have a notch it will thoroughly piss me off since I pretty much use them in landscape....

    Yepp, especially since it would cover part of the apps UI if it was rotated in the 'wrong' direction :)

    Those rolling with an iPhone X what happens the to 'sides' of the app such as Gadget when it's used in landscape mode rotated in both directions, do the piano keys on the side get 'covered' by the notch when editing a sequence or does to UI get jumpy and scale down so the the notch wont cover the content?

    There's simply too little feedback from iPhone X owners regarding the music apps which could somehow be an indication that it's not so popular?! (Or they simply won't admit that their $1000 phone has a 'design flaw' and silently blame it on the app developers).

    What worries me more are the rumours that the new iPads will not have a 3.5mm jack.
    The latency of BT wireless headphones at least on iOS is un-acceptable for anything remotely close to realtime.

  • edited March 2018

    @Samu said:

    @gonekrazy3000 said:
    Bloody hell if the new iPads have a notch it will thoroughly piss me off since I pretty much use them in landscape....

    Yepp, especially since it would cover part of the apps UI if it was rotated in the 'wrong' direction :)

    Those rolling with an iPhone X what happens the to 'sides' of the app such as Gadget when it's used in landscape mode rotated in both directions, do the piano keys on the side get 'covered' by the notch when editing a sequence or does to UI get jumpy and scale down so the the notch wont cover the content?

    There's simply too little feedback from iPhone X owners regarding the music apps which could somehow be an indication that it's not so popular?! (Or they simply won't admit that their $1000 phone has a 'design flaw' and silently blame it on the app developers).

    What worries me more are the rumours that the new iPads will not have a 3.5mm jack.
    The latency of BT wireless headphones at least on iOS is un-acceptable for anything remotely close to realtime.

    Gadget has the notch in its own ‘bevel’ on iPhone X in landscape mode. Doesn’t obstruct anything at all. If Gadgets bevel were darker/true black you wouldn’t even see the notch

  • edited March 2018

    I’d guess most app developers are ignoring the ‘notch’, and so the Apple designers are stamping their feet that their cleverness isn’t being appreciated.

    It’s an example of designers having no knowledge of the platform they’re designing for, or communicating with people who do. See it all the time when print designers create graphics and layouts for the web, but have no experience of responsive design or building websites.

    I wouldn’t worry, it’ll be gone on the next generation.

  • @realdavidai said:

    Gadget has the notch in its own ‘bevel’ on iPhone X in landscape mode. Doesn’t obstruct anything at all. If Gadgets bevel were darker/true black you wouldn’t even see the notch

    Do you mean 'dark borders' on left and right side of the screen when the device is held in landscape mode?
    (If that's the case it is not optimised for iPhone X but uses a work-around that is not considered proper iPhone X implementation and in practice would contain just about the same amount of information as the screen on iPhone 8 but would use the 3x assets instead of 2x).

    Personally I'm leaning towards the iPhone 8 but at the moment I have no rush since my iPhone 5 still serves me well for day to day phone related tasks :)

  • edited March 2018

    @Samu said:
    Do you mean 'dark borders' on left and right side of the screen when the device is held in landscape mode?
    (If that's the case it is not optimised for iPhone X but uses a work-around that is not considered proper iPhone X implementation and in practice would contain just about the same amount of information as the screen on iPhone 8 but would use the 3x assets instead of 2x).

    Indeed, and unless Korg have special arrangements with Apple this is no longer allowed since early February. Not even when doing just a minor update on an existing app - which is what I ran into with the Ruismakers and why they got rejected repeatedly. Compatibility mode is being banned. From now on any submitted apps must run natively on the X, and provide X-specific App Store material (your store images aren't even allowed to show a non-X phone as an example anymore), etc. etc.

    Which is the primary reason of my annoyance and my rant against iPhone support becoming even more of a hassle... :#

  • edited March 2018

    @brambos said:
    Up until now they allowed apps to run in legacy mode on the iPhone X, but they’ve started bullying developers into including X-specific UI design and behavior. Not sure if iPhone support is worth the effort anymore: very few users, lots of different screen sizes

    yeas, apple completely fucked up iphone seqment, it's now almost same crap like android .. cook is asshole, jobs was always pushing just one unified display size exactly because he doesn't wanted to move iphone to super-segmented market like android crap ..

    cook is slowly destroying apple, moving it from technological leader and pro-devices maker to consumer segment aimed for neohippies and hipsters ..

  • @brambos said:

    Which is the primary reason of my annoyance and my rant against iPhone support becoming even more of a hassle... :#

    This must really be a total pain for developers who have 'universal apps' and need to push out an update even it would just be a 'bug fix' that has nothing to do with the UI?!

    The idea of implementing a 'notch' is simply bad by design as are rounded displays & corners.
    Sure it might 'look cool' for some but it's just meh from a usability perspective...

  • @Samu said:

    @realdavidai said:

    Gadget has the notch in its own ‘bevel’ on iPhone X in landscape mode. Doesn’t obstruct anything at all. If Gadgets bevel were darker/true black you wouldn’t even see the notch

    Do you mean 'dark borders' on left and right side of the screen when the device is held in landscape mode?
    (If that's the case it is not optimised for iPhone X but uses a work-around that is not considered proper iPhone X implementation and in practice would contain just about the same amount of information as the screen on iPhone 8 but would use the 3x assets instead of 2x).

    Personally I'm leaning towards the iPhone 8 but at the moment I have no rush since my iPhone 5 still serves me well for day to day phone related tasks :)

    This is how it looks in landscape

  • @Samu said:

    @brambos said:

    Which is the primary reason of my annoyance and my rant against iPhone support becoming even more of a hassle... :#

    This must really be a total pain for developers who have 'universal apps' and need to push out an update even it would just be a 'bug fix' that has nothing to do with the UI?!

    Exactemundo: your quick bugfix turns into a mandatory UI overhaul at the least convenient moment imaginable.

  • edited March 2018

    @brambos said:

    @Samu said:
    Do you mean 'dark borders' on left and right side of the screen when the device is held in landscape mode?
    (If that's the case it is not optimised for iPhone X but uses a work-around that is not considered proper iPhone X implementation and in practice would contain just about the same amount of information as the screen on iPhone 8 but would use the 3x assets instead of 2x).

    Indeed, and unless Korg have special arrangements with Apple this is no longer allowed since early February. Not even when doing just a minor update on an existing app - which is what I ran into with the Ruismakers and why they got rejected repeatedly. Compatibility mode is being banned. From now on any submitted apps must run natively on the X, and provide X-specific App Store material (your store images aren't even allowed to show a non-X phone as an example anymore), etc. etc.

    Which is the primary reason of my annoyance and my rant against iPhone support becoming even more of a hassle... :#

    I don’t think Korg is using compatibility mode here. There aren’t black pillars, it’s just that there are no useable controls being obscured by the notch, there’s a designed ‘surface’ under it :)

  • @Samu said:

    @brambos said:

    Which is the primary reason of my annoyance and my rant against iPhone support becoming even more of a hassle... :#

    This must really be a total pain for developers who have 'universal apps' and need to push out an update even it would just be a 'bug fix' that has nothing to do with the UI?!

    The idea of implementing a 'notch' is simply bad by design as are rounded displays & corners.
    Sure it might 'look cool' for some but it's just meh from a usability perspective...

    I see it as a design trade-off. Similar to the the camera “bump” on back. Computer “Vision”, depth sensing, night time compatibility, robust facial biometrics etc cool things to invest in.

  • edited March 2018

    @realdavidai said:

    I see it as a design trade-off. Similar to the the camera “bump” on back. Computer “Vision”, depth sensing, night time compatibility, robust facial biometrics etc cool things to invest in.

    It's a branding move for sure.

    It makes the iPhone X (and future iPhones) recognisable right away, just like to home button before it - I think it will be here to stay for some time. Chinese phone makers are already copying it :wink:

    Their other option would have been to do like Samsung and have a small forehead all the way across the top, but that would make the phone look like any other "full screen" type device. They don't want that, they want you to be able to recognise an iPhone right away, which is why they insist on developers embracing it instead of hiding it.

  • @Peter321 said:

    @realdavidai said:

    I see it as a design trade-off. Similar to the the camera “bump” on back. Computer “Vision”, depth sensing, night time compatibility, robust facial biometrics etc cool things to invest in.

    It's a branding move for sure.

    It makes the iPhone X (and future iPhones) recognisable right away, just like to home button before it - I think it will be here to stay for some time. Chinese phone makers are already copying it :wink:

    Their other option would have been to do like Samsung and have a small forehead all the way across the top, but that would make the phone look like any other "full screen" type device. They don't want that, they want you to be able to recognise an iPhone right away, which is why they insist on developers embracing it instead of hiding it.

    I can see that, and a strong brand helps ensure the survival of the product. iPhone/iPad go away we are back to the dreaded desktops

  • edited March 2018

    @brambos said:

    @Samu said:
    Do you mean 'dark borders' on left and right side of the screen when the device is held in landscape mode?
    (If that's the case it is not optimised for iPhone X but uses a work-around that is not considered proper iPhone X implementation and in practice would contain just about the same amount of information as the screen on iPhone 8 but would use the 3x assets instead of 2x).

    Indeed, and unless Korg have special arrangements with Apple this is no longer allowed since early February. Not even when doing just a minor update on an existing app - which is what I ran into with the Ruismakers and why they got rejected repeatedly. Compatibility mode is being banned. From now on any submitted apps must run natively on the X, and provide X-specific App Store material (your store images aren't even allowed to show a non-X phone as an example anymore), etc. etc.

    Which is the primary reason of my annoyance and my rant against iPhone support becoming even more of a hassle... :#

    If I read this correct. The trick that Apple is pulling is that devs will stop developing their apps for all iPhones without the Notch. So all Apple iPhone users will have to buy new iPhones with a Notch in the (very near) future because developing different versions of an app becomes more and more a hassle. So as a users you only can get your updated apps on a new iPhone with a notc. And Apple wants this to happen asap of course, because the huge 2nd hands iPhone market with older models is not really profitable for Apple. This reminds me somehow of battery gate... looks like same strategy.

    Again it's Apple's way or no way. And the only goal is to keep de profits pushing to the ceiling.

  • edited March 2018

    Xequence does the same as Gadget, and so far this has passed review without a notch hitch. It really isn't too hard to implement? Just add 30px (can't remember the exact Apple recommendation) padding to the bottom, left and right sides of your app in landscape... if the UI is structured cleanly then this should be easy...

  • @realdavidai said:

    This is how it looks in landscape

    Good to know. This means that there's even less room vertically on the iPhone X when used in landscape mode than on the regular iPhone 8 due to the 'scroll swipe bar thing' at the bottom :)

    Care to share a screenshot of GarageBand?
    (It was not installed on the demo phone in the store when I checked yesterday).

  • I don't believe Apple would put the notch on iPads screen, they would be fools to do so when it's not all about fitting it in your pocket, they have more space to play with.
    And also not just music apps but all apps would suffer including watching films which is done in landscape mode.

  • @SevenSystems said:
    Xequence does the same as Gadget, and so far this has passed review without a notch hitch. It really isn't too hard to implement? Just add 30px (can't remember the exact Apple recommendation) padding to the bottom, left and right sides of your app in landscape... if the UI is structured cleanly then this should be easy...

    So on a 10.5 inch Pro that means you are losing 6.6% of screen real estate just to accommodate the notch - with UI space at a premium it sounds like a lot to me.

  • @Samu said:

    @realdavidai said:

    This is how it looks in landscape

    Good to know. This means that there's even less room vertically on the iPhone X when used in landscape mode than on the regular iPhone 8 due to the 'scroll swipe bar thing' at the bottom :)

    Care to share a screenshot of GarageBand?
    (It was not installed on the demo phone in the store when I checked yesterday).

    This is how GB supports the notch. Also the scroll swipe thing doesn’t take up vertical space per se

  • edited March 2018

    @SevenSystems said:
    Xequence does the same as Gadget, and so far this has passed review without a notch hitch. It really isn't too hard to implement? Just add 30px (can't remember the exact Apple recommendation) padding to the bottom, left and right sides of your app in landscape... if the UI is structured cleanly then this should be easy...

    Indeed. I dread the day I start blowing every little thing I read out of proportion. It’s a humanity thing I suppose. If I start doing it please someone talk me off the ledge :# :D

  • @realdavidai said:

    This is how GB supports the notch. Also the scroll swipe thing doesn’t take up vertical space per se

    Thanks! If you rotate it the other way around the notch just covers parts of the tracks and the mixer fully at at other the edge? (or is the same 'margin' present there as well?).

    For no I'm leaning towards the regular iPhone 8. Remains to be seen what happens at WWDC'18.

Sign In or Register to comment.