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.

Synthmaster One is out!

1232426282948

Comments

  • edited July 2018

    While I have a lot of respect for this synth and its developers commitment to it, I do understand one aspect of the discourse above. I’m not wanting to stir that pot. But I do want to reiterate a specific point of frustration with the hopes that it might become a consideration for a future build. And perhaps it might already be on the roadmap and I’ve just missed it. Apologies if I’m beating a dead horse.

    From a sound design perspective the Waveform / Wavetable menu navigation is simply not good UI design. I’m sorry @MobileMusic , I know you probably disagree. But, again, from a sound design perspective, repetitively navigating 3 and 4 levels deep into drop downs in order to audition a suitable Waveform / Wavetable each time isn’t an enjoyable experience. It truly does become a frustration when repeated dives are necessary; a process that intuitive and accommodating UI design sets out to solve.

    Additionally, the lack of any sort of labeling to identify the waveform/table in use is incredibly frustrating when auditioning. I’m often unsure of the previously selected file, or, if I want to revisit a patch and determine what square one consists of I’m simply out of luck? Correct me if I’m wrong here.

    Those are my biggest gripes. And I respect that for a lot of users these things may never even matter. But I’m incredibly excited over the handful of presets I’ve already made for this synth, and I really want to capture that momentum to generate many more. It has proven itself more than capable....I just wish it to be a little more user-friendly* in the patch creation department. That is all.


    I’ll use *Serum by Xfer Records again as an example as its UI design for this exact functionality is excellent. An option for SM1, with no visual changes, a swipe gesture on the waveform display to navigate through the files would make a galaxy of difference. Or left / right navigation arrows. And adding the currently selected waveform/table name to the header of the pop-out menu would add another galaxy of difference.

  • @Chaztrip said:
    New update. Clicks and pops. Sounds of Israel’s after love dies preset. Really notice it there. 2017 12.9 iPad Pro.

    Hmmm maybe it’s just that preset. Sorry.

    Hmmm... Now you writing in wrong forum thread!
    Sound of Israel is pathes for Synth One (open source-synth for free), not Synthmaster One...

  • @Chaztrip said:
    New update. Clicks and pops. Sounds of Israel’s after love dies preset. Really notice it there. 2017 12.9 iPad Pro.

    Hmmm maybe it’s just that preset. Sorry.

    Do we have that preset :smiley:

  • The user and all related content has been deleted.
  • I already submitted v1.1.1 to AppStore. Should be approved today hopefully

  • The user and all related content has been deleted.
  • @ErrkaPetti said:

    @Chaztrip said:
    New update. Clicks and pops. Sounds of Israel’s after love dies preset. Really notice it there. 2017 12.9 iPad Pro.

    Hmmm maybe it’s just that preset. Sorry.

    Hmmm... Now you writing in wrong forum thread!
    Sound of Israel is pathes for Synth One (open source-synth for free), not Synthmaster One...

    Yes sooooo sorry. Jeez. Hostile people in here.

  • Not a big deal but I’m still wanting that handsome blue skin 🤩

  • Allright fellows, v1.1.1 is out the door

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

    @brice said:
    While I have a lot of respect for this synth and its developers commitment to it, I do understand one aspect of the discourse above. I’m not wanting to stir that pot. But I do want to reiterate a specific point of frustration with the hopes that it might become a consideration for a future build. And perhaps it might already be on the roadmap and I’ve just missed it. Apologies if I’m beating a dead horse.

    From a sound design perspective the Waveform / Wavetable menu navigation is simply not good UI design. I’m sorry @MobileMusic , I know you probably disagree. But, again, from a sound design perspective, repetitively navigating 3 and 4 levels deep into drop downs in order to audition a suitable Waveform / Wavetable each time isn’t an enjoyable experience. It truly does become a frustration when repeated dives are necessary; a process that intuitive and accommodating UI design sets out to solve.

    Additionally, the lack of any sort of labeling to identify the waveform/table in use is incredibly frustrating when auditioning. I’m often unsure of the previously selected file, or, if I want to revisit a patch and determine what square one consists of I’m simply out of luck? Correct me if I’m wrong here.

    Those are my biggest gripes. And I respect that for a lot of users these things may never even matter. But I’m incredibly excited over the handful of presets I’ve already made for this synth, and I really want to capture that momentum to generate many more. It has proven itself more than capable....I just wish it to be a little more user-friendly* in the patch creation department. That is all.


    I’ll use *Serum by Xfer Records again as an example as its UI design for this exact functionality is excellent. An option for SM1, with no visual changes, a swipe gesture on the waveform display to navigate through the files would make a galaxy of difference. Or left / right navigation arrows. And adding the currently selected waveform/table name to the header of the pop-out menu would add another galaxy of difference.

    @kv331audio_bulent,

    I posted a comment on SM1's YouTube video last year (alias Shekar Reddy) when it was initially featured saying 3-level deep menus in any app would offer a bad UX and suggested to limit them to no more than 2 levels (some menus in SM1 are actually 4-level deep). After seeing them in action in SM1 now - with the popular items shown on the top of the menu for 1-tap quick access without having to drill-down any submenus - I thought maybe they offer some kind of smart structure/organization of categories and types which is why I suggested to keep the menus open until tapped on the synth areas above but not the keyboard so we can continue with choosing other forms/tables (available in v1.1.1). Multi-level submenus result in more drilling down but offer the benefit of LESS scrolling with smaller lists :smile: A graceful solution is to offer a 2-level menu option like Alchemy in GB which would be ideal and user-friendly. The type (Basic, Analog, Digital, etc) can be added as an additional display column in the lists along with any extra columns (FM, Random, etc) for information purposes with ability to sort the lists in ascending/descending order by tapping on column headers like Cubasis Media browser that would make it replete. Tapping on Type column should sort the list by Type + form/table name (default sort order).

    A Recents submenu option/list showing 25-50 recently chosen waveforms/wavetables would be nice too, to quickly go back to one of them (these should get saved/persist across relaunches). These should be sorted by their selection order/timestamp and not by name or offer the option to re-sort them by name/recency by tapping on the headers. Also, a Recents bank in the Browser :smile:

    Also suggested to display the selected waveform/wavetable names in the UI and to auto-navigate/drill-down/scroll to the current waveform/wavetable and highlight them on tapping on the controls as a visual cue in my previous comments:

    https://forum.audiob.us/discussion/comment/509389/#Comment_509389
    https://forum.audiob.us/discussion/comment/502024/#Comment_502024

    Swipe gesture on controls (like in GB) and left/right arrow keys would be nice too if it displays the names in the UI after the navigation. Swipe gesture could be implemented on many controls in the UI including the one on the top-middle where it displays the current preset name with left/right arrow keys. Also suggested to use condensed fonts like the ones in Synth One, FL Studio, Alchemy Mobile, etc to cram more content in less space if necessary. Condensed fonts also look elegant and contemporary (not saying the current fonts are looking bad - just cramming more content in available room).

    For the reasons we know when SM1 is used as AU that scrolls horizontally to access its other sections, the ability to turn off swipe gestures as a preference setting would be ideal too so we do not swipe on a control and go to its next/previous item accidentally and mess up our stuff :neutral:

  • Haow does it work as an fx?
    What is the routing?
    Thanks for any help!

  • @kv331audio_bulent said:

    @RockySmalls said:
    back to the App folks..

    I submitted v1.1.1 this morning, hopefuly it'll be released to AppStore tonight. Here are more fixes:

    1. AU FX init preset should set osc1 type to audio in L, osc2 type to audio in R
    2. Dropdowns should not close when user is playing the builtin keyboard
    3. SynthMaster One AUv3 crashes when zoom button for the arpeggiator is pressed
    4. SynthMaster One crashes when osc type is set to audio in
    5. When osc waveform is changed from the menu, the osc still plays the old waveform
    6. 'Set to default' menu doesn't work for knobs/sliders

    Great.. just diving into this beauty...

    @kv331audio_bulent said:
    Allright fellows, v1.1.1 is out the door

    Just got the update.. The Browser works fine on first glance... makes a big difference...

    Thanks..

    Back to dig...

  • edited July 2018

    @realdawei said:
    Not a big deal but I’m still wanting that handsome blue skin 🤩

    Also, Charcoal/Dark/Stealth theme :smile:
    Do keep the current Warm theme with a preference option to switch themes under Settings.

  • edited July 2018

    @Dawdles said:
    Auditioning wavetables, auditioning lfo shapes etc.... This stuff should always be audible? I've never come across a synth with a 'hold' function that was designed this way before. It feels very slow/un-intuitive to do things like this? Again it's been enough for me to put the app on hold until it feels less difficult/slow to do basic things. I'm just too used to things not being this way on other instruments. Maybe it's just me? Or is there a setting I'm missing somewhere?

    Waveforms/wavetables/filters types etc many DISCRETE parameters are updated when a new note is pressed, that's been my implementation all along (for the past 10 years) I will think about how to update those when the parameter is edited when the note is playing.

  • @flo26 said:
    Haow does it work as an fx?
    What is the routing?
    Thanks for any help!

    You can instantiate the FX inside AUM for instance. When you instantiate it click on the preset name, choose "Init Preset" (will default to this in the next update!). Osc1 wave type is set to Audio In L, and Osc2 wave type is set to Audio In R.

    To pass the audio through, you should send a MIDI note on message to the FX plugin. You can bring up the builtin keyboard for instance, and then after pressing the HOLD key, you can press a note. That'll pass the incoming audio through the signal chain inside SM1

  • edited July 2018
    The user and all related content has been deleted.
  • @flo26 said:
    Haow does it work as an fx?
    What is the routing?
    Thanks for any help!

    @kv331audio_bulent,
    Hi Bulent, What about the SynthMaster One Effect that comes in desktop installation?

  • @Dawdles said:
    Thanks for reply. Its just a very weird way of doing things compared to all other hardware and software synths I ever used. Changing an lfo shape should immediately alter the audible sound. Same with osc type, filter type etc. Hopefully it's an easy fix..

    Actually it's not :)

  • edited July 2018

    @Dawdles said:
    Thanks for the update. I really want to keep things constructive this time so I'm reluctant to even post, but I just tried it and it's almost de ja vu.... Now the 'hold' button works properly, and menus stay open (thanks :) but changes made to params and Oscs etc aren't audible while notes are held? Seems very odd and unintuitive. I thought I'd hit an instant bug at first when disabling osc1 but it still coming out of the headphones... Surely all parameter changes should effect the sound coming from the output? Auditioning wavetables, auditioning lfo shapes etc.... This stuff should always be audible? I've never come across a synth with a 'hold' function that was designed this way before. It feels very slow/un-intuitive to do things like this? Again it's been enough for me to put the app on hold until it feels less difficult/slow to do basic things. I'm just too used to things not being this way on other instruments. Maybe it's just me? Or is there a setting I'm missing somewhere?
    Thanks

    As suggested before, tap the Expand button before switching to Mod Matrix and now you have 2 keyboards to play with as you tweak mods. No need to use the Hold button.

  • @Dawdles said:
    Precisely the kind of immediate workflow issues I found with this app. I was blunt with my feedback, apologies if dev's feelings got hurt. I wasn't aiming my feedback at him personally. But this is what I was getting at.

    No worries. Cheers :smile:

  • BTW, in my workflow I use MIDI controllers connected via camera connection kit. That's why I never needed the Hold button to edit parameters.

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

    @Dawdles said:

    @kv331audio_bulent said:
    BTW, in my workflow I use MIDI controllers connected via camera connection kit. That's why I never needed the Hold button to edit parameters.

    Sorry but that doesn't really make sense... There are hundreds of hardware synths with built in keyboards that have hold/latch. And they all respond instantly to parameter changes without needing to hit a new note... I'm not trying to be argumentative etc, that's just fact...

    @kv331audio_bulent,
    It's a glitch that needs to be fixed. Until then, this is a workaround.

  • The user and all related content has been deleted.
  • @Dawdles said:
    Thanks for the update. I really want to keep things constructive this time so I'm reluctant to even post, but I just tried it and it's almost de ja vu.... Now the 'hold' button works properly, and menus stay open (thanks :) but changes made to params and Oscs etc aren't audible while notes are held? Seems very odd and unintuitive. I thought I'd hit an instant bug at first when disabling osc1 but it still coming out of the headphones... Surely all parameter changes should effect the sound coming from the output? Auditioning wavetables, auditioning lfo shapes etc.... This stuff should always be audible? I've never come across a synth with a 'hold' function that was designed this way before. It feels very slow/un-intuitive to do things like this? Again it's been enough for me to put the app on hold until it feels less difficult/slow to do basic things. I'm just too used to things not being this way on other instruments. Maybe it's just me? Or is there a setting I'm missing somewhere?
    Thanks

    Very weird, it is working as expected in my version : if I hold a key and change parameters, changes can be heard just fine in real time (without having to hit another key). I tried to remove Osc1, change waveforms/tone/index, modify Lfo parameters or change cutoff frequency, everything has an immediate impact on the sound.
    I have the beta version installed

  • Thanks so much!!
    Have fun!!

  • The user and all related content has been deleted.
  • @Dawdles said:

    @Sygma said:

    @Dawdles said:
    Thanks for the update. I really want to keep things constructive this time so I'm reluctant to even post, but I just tried it and it's almost de ja vu.... Now the 'hold' button works properly, and menus stay open (thanks :) but changes made to params and Oscs etc aren't audible while notes are held? Seems very odd and unintuitive. I thought I'd hit an instant bug at first when disabling osc1 but it still coming out of the headphones... Surely all parameter changes should effect the sound coming from the output? Auditioning wavetables, auditioning lfo shapes etc.... This stuff should always be audible? I've never come across a synth with a 'hold' function that was designed this way before. It feels very slow/un-intuitive to do things like this? Again it's been enough for me to put the app on hold until it feels less difficult/slow to do basic things. I'm just too used to things not being this way on other instruments. Maybe it's just me? Or is there a setting I'm missing somewhere?
    Thanks

    Very weird, it is working as expected in my version : if I hold a key and change parameters, changes can be heard just fine in real time (without having to hit another key). I tried to remove Osc1, change waveforms/tone/index, modify Lfo parameters or change cutoff frequency, everything has an immediate impact on the sound.
    I have the beta version installed

    Yup thats weird. The dev just said that it isn't easily possible to make this happen in an update? Maybe we're talking about different parameters? Try changing an lfo shape, osc type, filter type etc and see if any joy while holding note/s...

    Yep, I tried again and everything is fine here. There must be a misunderstanding somewhere...

This discussion has been closed.