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 v1.3 Universal live

1…810121314

Comments

  • kv331audio_bulentkv331audio_bulent
    edited January 2020

    @roman_ch said:
    Thanks for the interesting guide to Apple documentation, but how can it helps us?
    **Can it return worked automation someway to us? **

    As I wrote above, I will revert back the parameter indexes to v1.1, so it WILL work for older users, but will break for projects created after v1.3 (if they used automation)

  • roman_chroman_ch

    @kv331audio_bulent said:

    @roman_ch said:
    Thanks for the interesting guide to Apple documentation, but how can it helps us?
    **Can it return worked automation someway to us? **

    As I wrote above, I will revert back the parameter indexes to v1.1, so it WILL work for older users, but will break for projects created after v1.3 (if they used automation)

    Maybe it was released too early?
    Of course, NAMM was coming soon and there were many good reasons for the new version promo.
    But maybe it is a good time to fix?

  • espiegel123espiegel123

    @roman_ch said:

    @kv331audio_bulent said:

    @roman_ch said:
    Thanks for the interesting guide to Apple documentation, but how can it helps us?
    **Can it return worked automation someway to us? **

    As I wrote above, I will revert back the parameter indexes to v1.1, so it WILL work for older users, but will break for projects created after v1.3 (if they used automation)

    Maybe it was released too early?
    Of course, NAMM was coming soon and there were many good reasons for the new version promo.
    But maybe it is a good time to fix?

    Roman: what you might not be understanding is that the bug is BM3's. @kv331audio_bulent has agreed to workaround BM3's bug. While I can understand your frustration, it seems like Intua is at fault for this.

  • espiegel123espiegel123

    @kv331audio_bulent : on my iPad gen 6, running iOS 12.3.1, SM1's interface won't display at all in BeatMaker 3. Where the synth's u.i. should appear, there is only an empty background

  • AudioGusAudioGus

    @kv331audio_bulent said:

    @roman_ch said:
    This fixes are very important.
    Your synth is great, but make it affordable and useful for all customers, please!

    I will be happy to change my review completely, immediately after the fix.

    Our synth is already affordable, compare its feature set + content with other iOS synths.

    As per Apple documentation on AUv3 parameter indexes (addresses) :

    Parameter addresses are not necessarily persistent, unless the individual audio unit promises to maintain its addressing scheme. Hosts should bind to parameter key paths instead of parameter addresses.

    I will go ahead and make parameter indexes compatible with v1.1, but that might break automation of projects created after v1.3...

    It is a shame that BM3 is not following the documented advice.

    In this particular case since it looks like somewhere around 80-90% of the AU parameters are now missing in BM3 (vital ones like filter cutoff) I doubt anyone is actually recording much automation with 1.3 now. I doubt there would be any fallout if v1.1 compatibility is restored.

  • AudioGusAudioGus

    @roman_ch said:

    @kv331audio_bulent said:
    As per Apple documentation on AUv3 parameter indexes (addresses) :
    Parameter addresses are not necessarily persistent, unless the individual audio unit promises to maintain its addressing scheme. Hosts should bind to parameter key paths instead of parameter addresses.

    Thanks for the interesting guide to Apple documentation, but how can it helps us?
    **Can it return worked automation someway to us? **

    Sorry for this example, but please look how SugarBytes warn their customers:

    He did say "I will go ahead and make parameter indexes compatible with v1.1"

    So that should fix it.

  • AudioGusAudioGus
    edited January 2020

    @espiegel123 said:
    @kv331audio_bulent : on my iPad gen 6, running iOS 12.3.1, SM1's interface won't display at all in BeatMaker 3. Where the synth's u.i. should appear, there is only an empty background

    if you go back into it does it then appear? I have some synths that do this in BM3. it seems to be a BM3 issue in the cases I have had.

  • roman_chroman_ch

    @espiegel123
    Thank you for joining in.

    Everything was quite clear to me.
    I got a question from Kv331_audiobulent and responded.

    I did my best to describe the problems that I encountered in the product. Really. I have nothing more to add.

    Intua has not updated since November 2019.
    How it is related to broken automation in the January 2020 update, I can't get.

    Guys thanks. I just an existing customer. I have product with some problems.
    I want to help to solve them, but I faced the something another here.

    This is the SynthMaster UI in GarageBand:
    GB is not an Intua product

    Peace :(

  • AudioGusAudioGus

    @roman_ch said:
    @espiegel123
    Thank you for joining in.

    Everything was quite clear to me.
    I got a question from Kv331_audiobulent and responded.

    I did my best to describe the problems that I encountered in the product. Really. I have nothing more to add.

    Intua has not updated since November 2019.
    How it is related to broken automation in the January 2020 update, I can't get.

    Yah it is weird but that is often how this sort of thing goes. Imagine a house built on weak ground (lots of loose dirt or sand). The house stays up for a few years and then when the owners decide to put a hottub in the whole patio and part of the back yard caves in, revealing the faulty earth underneath.

  • espiegel123espiegel123

    @roman_ch said:
    @espiegel123
    Thank you for joining in.

    Everything was quite clear to me.
    I got a question from Kv331_audiobulent and responded.

    I did my best to describe the problems that I encountered in the product. Really. I have nothing more to add.

    Intua has not updated since November 2019.
    How it is related to broken automation in the January 2020 update, I can't get.

    Guys thanks. I just an existing customer. I have product with some problems.
    I want to help to solve them, but I faced the something another here.

    This is the SynthMaster UI in GarageBand:
    GB is not an Intua product

    Peace :(

    The BM3 bug is this: BM3 stores the wrong information for AU parameters. Essentially, it is as if it records the order of the parameter rather than its proper unique identifier. It is as if it were a navigation program that stored a house’s address as “the third house on the left” instead of using the actual address: “3493 My Street”. That works until a new house is built between the second and third house. At that point a navigation program that uses location instead of address will now send you to the wrong place.

    BM3 was using the wrong info to store the parameters. So, the bug wouldn’t show up until, a developer changed the order of things which is totally legal since apps aren’t supposed to rely on the order. There is a unique stable ID they are supposed to use.

    (Apologies for any inexactness in the analogy.)

  • espiegel123espiegel123

    @AudioGus said:

    @espiegel123 said:
    @kv331audio_bulent : on my iPad gen 6, running iOS 12.3.1, SM1's interface won't display at all in BeatMaker 3. Where the synth's u.i. should appear, there is only an empty background

    if you go back into it does it then appear? I have some synths that do this in BM3. it seems to be a BM3 issue in the cases I have had.

    Even after reboot and creating a new project, I get the same result.

  • AudioGusAudioGus
    edited January 2020

    @espiegel123 said:

    @AudioGus said:

    @espiegel123 said:
    @kv331audio_bulent : on my iPad gen 6, running iOS 12.3.1, SM1's interface won't display at all in BeatMaker 3. Where the synth's u.i. should appear, there is only an empty background

    if you go back into it does it then appear? I have some synths that do this in BM3. it seems to be a BM3 issue in the cases I have had.

    Even after reboot and creating a new project, I get the same result.

    I mean when you see it blank if you exit that screen and simply re-enter it, is it still blank?

  • espiegel123espiegel123

    @AudioGus said:

    @espiegel123 said:

    @AudioGus said:

    @espiegel123 said:
    @kv331audio_bulent : on my iPad gen 6, running iOS 12.3.1, SM1's interface won't display at all in BeatMaker 3. Where the synth's u.i. should appear, there is only an empty background

    if you go back into it does it then appear? I have some synths that do this in BM3. it seems to be a BM3 issue in the cases I have had.

    Even after reboot and creating a new project, I get the same result.

    I mean when you see it blank if you exit that screen and simply re-enter it, is it still blank?

    Yes.

  • AudioGusAudioGus

    @espiegel123 said:

    @AudioGus said:

    @espiegel123 said:

    @AudioGus said:

    @espiegel123 said:
    @kv331audio_bulent : on my iPad gen 6, running iOS 12.3.1, SM1's interface won't display at all in BeatMaker 3. Where the synth's u.i. should appear, there is only an empty background

    if you go back into it does it then appear? I have some synths that do this in BM3. it seems to be a BM3 issue in the cases I have had.

    Even after reboot and creating a new project, I get the same result.

    I mean when you see it blank if you exit that screen and simply re-enter it, is it still blank?

    Yes.

    ugh, bummer!

  • kv331audio_bulentkv331audio_bulent
    edited January 2020

    @roman_ch said:
    This is the SynthMaster UI in GarageBand:
    GB is not an Intua product

    Peace :(

    Please tap on an empty area, hold your finger there and scroll left/right. That's how scrolling works in that UI (It's always been like that since v1.0)

    If it's not scrolling, that's a bug (I can't reproduce because I don't have the 12.9 iPad with me, tomorrow I'll be able to test it)

  • espiegel123espiegel123

    @kv331audio_bulent have you been able to reproduce this crash? I wonder if the size issue could be involved in SM1 not being able to load its interface (see note a few posts up) in BM3

  • kv331audio_bulentkv331audio_bulent

    @espiegel123 said:
    @kv331audio_bulent have you been able to reproduce this crash? I wonder if the size issue could be involved in SM1 not being able to load its interface (see note a few posts up) in BM3

    I've just tested with my 10.5 iPad Pro, and it works fine.

  • roman_chroman_ch

    @kv331audio_bulent said:

    @roman_ch said:

    Please tap on an empty area, hold your finger there and scroll left/right. That's how scrolling works in that UI (It's always been like that since v1.0)

    If it's not scrolling, that's a bug (I can't reproduce because I don't have the 12.9 iPad with me, tomorrow I'll be able to test it)

    @kv331audio_bulent thanks, I recorded the video.
    I can't get it scrolled.

    This is the one more video. I tap and move on the "header" (the grey element on the top of panel). But it doesn't want to react.

  • espiegel123espiegel123

    @kv331audio_bulent said:

    @espiegel123 said:
    @kv331audio_bulent have you been able to reproduce this crash? I wonder if the size issue could be involved in SM1 not being able to load its interface (see note a few posts up) in BM3

    I've just tested with my 10.5 iPad Pro, and it works fine.

    This is not a 10.5" iPad. As noted in the video, this is an iPad 6th generation. I suspect screen size matters. Several of us mentioned this a week or two ago. On my iPad the crash is 100% reproducible.

  • MobileMusicMobileMusic
    edited January 2020

    @kv331audio_bulent said:

    @MobileMusic said:
    @kv331audio_bulent

    Clear / Remove Modulation does not work (tap on a knob that has modulation and choose these menu options but modulation persists)

    Which knobs? Some modulations can not be removed, like filter cutoff <-> mod env entries.

    I tried removing mods form Fine knob in the Osc but it doesn’t work - VLFO mods stay. I guess this is one of those reserved knobs where it cannot be removed due to its purpose.

  • MobileMusicMobileMusic
    edited January 2020

    @kv331audio_bulent

    I don’t see menus on some controls -

    Vibrato knob in Osc
    LFO and MOD knobs in Filter
    Velocity knobs in Amp and Mod envelopes
    Mid Speed, Mod Amount, Diffusion, Density knobs in Reverb effect
    The 2 Target knobs in Mod Matrix

    They could have a menu with at least Set To Default item (or double tap - but menu would be more consistent with other controls and less confusing so we don’t have to remember which ones have menus and which ones have double tap) to reset their values so users don’t have to struggle to dial accurate default values to reset them manually.

    Also the menus should stay open while touching the keyboard so sound designers don’t have to navigate menus again for every tap (this behavior was working fine but got broken). Users could close the menus by its close button or touching synth sections when needed.

  • MobileMusicMobileMusic
    edited January 2020

    @kv331audio_bulent said:

    @MobileMusic said:
    @kv331audio_bulent The about page with user info is missing on iPhone Settings or Help (accessible from tapping the logo on top left)

    Workaround: Click on "Download Bonus Presets" menu, user registration dialog will pop up, and will show current user name and email address.

    You could add a Register button on Settings and Help pages that takes the user to Download Bonus Presets page (for iPhone only) so it reduces future support questions from users who cannot quickly locate it.

  • kv331audio_bulentkv331audio_bulent

    @MobileMusic said:
    I tried removing mods form Fine knob in the Osc but it doesn’t work - VLFO mods stay. I guess this is one of those reserved knobs where it cannot be removed due to its purpose.

    Correct, they can NOT be removed.

  • kv331audio_bulentkv331audio_bulent

    @MobileMusic said:
    @kv331audio_bulent

    I don’t see menus on some controls -

    Vibrato knob in Osc
    LFO and MOD knobs in Filter
    Velocity knobs in Amp and Mod envelopes
    Mid Speed, Mod Amount, Diffusion, Density knobs in Reverb effect
    The 2 Target knobs in Mod Matrix

    Those are not regular parameters, they are modulation amounts.

  • kv331audio_bulentkv331audio_bulent
    edited January 2020

    @espiegel123 said:
    This is not a 10.5" iPad. As noted in the video, this is an iPad 6th generation. I suspect screen size matters. Several of us mentioned this a week or two ago. On my iPad the crash is 100% reproducible.

    Aaarg, I don't have a regular iPad, just ordered an 11 inch model to add the 11 inch skin. Looks like I'm gonna have to purchase the 9.7 iPad too, yet another Apple expense... Just ordered :)

  • espiegel123espiegel123

    @kv331audio_bulent said:

    @espiegel123 said:
    This is not a 10.5" iPad. As noted in the video, this is an iPad 6th generation. I suspect screen size matters. Several of us mentioned this a week or two ago. On my iPad the crash is 100% reproducible.

    Aaarg, I don't have a regular iPad, just ordered an 11 inch model to add the 11 inch skin. Looks like I'm gonna have to purchase the 9.7 iPad too, yet another Apple expense... Just ordered :)

    Would the crash logs be helpful? Do AU crashes generate them?

  • kv331audio_bulentkv331audio_bulent

    @espiegel123 said:

    @kv331audio_bulent said:

    @espiegel123 said:
    This is not a 10.5" iPad. As noted in the video, this is an iPad 6th generation. I suspect screen size matters. Several of us mentioned this a week or two ago. On my iPad the crash is 100% reproducible.

    Aaarg, I don't have a regular iPad, just ordered an 11 inch model to add the 11 inch skin. Looks like I'm gonna have to purchase the 9.7 iPad too, yet another Apple expense... Just ordered :)

    Would the crash logs be helpful? Do AU crashes generate them?

    Yes, would be very helpful

  • espiegel123espiegel123

    @kv331audio_bulent said:

    @espiegel123 said:

    @kv331audio_bulent said:

    @espiegel123 said:
    This is not a 10.5" iPad. As noted in the video, this is an iPad 6th generation. I suspect screen size matters. Several of us mentioned this a week or two ago. On my iPad the crash is 100% reproducible.

    Aaarg, I don't have a regular iPad, just ordered an 11 inch model to add the 11 inch skin. Looks like I'm gonna have to purchase the 9.7 iPad too, yet another Apple expense... Just ordered :)

    Would the crash logs be helpful? Do AU crashes generate them?

    Yes, would be very helpful

    How do I get them to you?

  • yowzayowza

    Settings/Privacy/Analytics/Data

    They have time stamps.

  • espiegel123espiegel123

    @yowza said:
    Settings/Privacy/Analytics/Data

    They have time stamps.

    I guess I wasn't clear. My question is where to send them.

This discussion has been closed.