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.

Flsm 3 popping with audio units and audiobus

13»

Comments

  • gregsmithgregsmith

    @Littlewoodg said:

    @gregsmith said:

    @studs1966 said:

    @gregsmith said:

    @Littlewoodg said:
    Just to be clear the popping mentioned in the OP doesn’t show up in the audio recording made from Audiobus using AUV3 synths...

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    It’s odd that you say this, see my PM.

    Interesting, didn’t think to try this. I’ll give it a go for Zeeon.

    @studs1966 said:

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    Actually, I have seen your requests on the beta section on there forum, (I stopped beta testing it a long time ago)…. Yep, it does look like your acknowledgement is not there. But I did request it at the beginning of this chaos at the beginning ( A long time ago). Scott did mention it was on there "To Do" list (Also Ableton Link when I was beta testing it)….. But I would imagine the dev team were focused(at the time) on getting FL Studio 20 ready & out... (Which it is now on Windows & Mac)…… :)

    After a long wait, I don’t think they did anything off their to do list in the last update! Not the to do list in the request forum anyway.

    Hopefully they’ll get on it soon. Might see if I can get into the beta program.

    Your probably right. Probably they wanted to get all the platform devices (iOS, Android & Windows) brought up to a certain workable order, to work with Mac/PC DAW version before adding the "To Do" list for each device. Good luck on the Beta journey. It's just taken a long time for them, which is quite a large challenge really. Now that FL Studio 20 is out (also, they will probably have to sort out certain bugs on PC) Maybe they concentrate more of a focus towards the mobile section?....... Who knows?....... ;)

    Yeah tbf it must be a hell of a challenge supporting all the platforms simultaneously. They’ve made an amazing app.

    It is an amazing app. And I’m psyched to have IAA (and Audiobus, with the clicks that don’t pollute the actual recordings)

    It’s also become a whole other kind of amazing when used with FL 20, but that’s another story.

    Amazing also with this reality check: I bought the first FL Mobile 6/11, I think $14.99 (in 2011 dollars).

    Yep it’s cheap as chips. I would literally pay the same price again for auv3 support tho :)

  • LittlewoodgLittlewoodg
    edited May 2018

    @gregsmith said:

    @Littlewoodg said:

    @gregsmith said:

    @studs1966 said:

    @gregsmith said:

    @Littlewoodg said:
    Just to be clear the popping mentioned in the OP doesn’t show up in the audio recording made from Audiobus using AUV3 synths...

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    It’s odd that you say this, see my PM.

    Interesting, didn’t think to try this. I’ll give it a go for Zeeon.

    @studs1966 said:

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    Actually, I have seen your requests on the beta section on there forum, (I stopped beta testing it a long time ago)…. Yep, it does look like your acknowledgement is not there. But I did request it at the beginning of this chaos at the beginning ( A long time ago). Scott did mention it was on there "To Do" list (Also Ableton Link when I was beta testing it)….. But I would imagine the dev team were focused(at the time) on getting FL Studio 20 ready & out... (Which it is now on Windows & Mac)…… :)

    After a long wait, I don’t think they did anything off their to do list in the last update! Not the to do list in the request forum anyway.

    Hopefully they’ll get on it soon. Might see if I can get into the beta program.

    Your probably right. Probably they wanted to get all the platform devices (iOS, Android & Windows) brought up to a certain workable order, to work with Mac/PC DAW version before adding the "To Do" list for each device. Good luck on the Beta journey. It's just taken a long time for them, which is quite a large challenge really. Now that FL Studio 20 is out (also, they will probably have to sort out certain bugs on PC) Maybe they concentrate more of a focus towards the mobile section?....... Who knows?....... ;)

    Yeah tbf it must be a hell of a challenge supporting all the platforms simultaneously. They’ve made an amazing app.

    It is an amazing app. And I’m psyched to have IAA (and Audiobus, with the clicks that don’t pollute the actual recordings)

    It’s also become a whole other kind of amazing when used with FL 20, but that’s another story.

    Amazing also with this reality check: I bought the first FL Mobile 6/11, I think $14.99 (in 2011 dollars).

    Yep it’s cheap as chips. I would literally pay the same price again for auv3 support tho :)

    I don’t think you’ll have to

  • studs1966studs1966

    :) > @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:

    @gregsmith said:

    @studs1966 said:

    @gregsmith said:

    @Littlewoodg said:
    Just to be clear the popping mentioned in the OP doesn’t show up in the audio recording made from Audiobus using AUV3 synths...

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    It’s odd that you say this, see my PM.

    Interesting, didn’t think to try this. I’ll give it a go for Zeeon.

    @studs1966 said:

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    Actually, I have seen your requests on the beta section on there forum, (I stopped beta testing it a long time ago)…. Yep, it does look like your acknowledgement is not there. But I did request it at the beginning of this chaos at the beginning ( A long time ago). Scott did mention it was on there "To Do" list (Also Ableton Link when I was beta testing it)….. But I would imagine the dev team were focused(at the time) on getting FL Studio 20 ready & out... (Which it is now on Windows & Mac)…… :)

    After a long wait, I don’t think they did anything off their to do list in the last update! Not the to do list in the request forum anyway.

    Hopefully they’ll get on it soon. Might see if I can get into the beta program.

    Your probably right. Probably they wanted to get all the platform devices (iOS, Android & Windows) brought up to a certain workable order, to work with Mac/PC DAW version before adding the "To Do" list for each device. Good luck on the Beta journey. It's just taken a long time for them, which is quite a large challenge really. Now that FL Studio 20 is out (also, they will probably have to sort out certain bugs on PC) Maybe they concentrate more of a focus towards the mobile section?....... Who knows?....... ;)

    Yeah tbf it must be a hell of a challenge supporting all the platforms simultaneously. They’ve made an amazing app.

    It is an amazing app. And I’m psyched to have IAA (and Audiobus, with the clicks that don’t pollute the actual recordings)

    It’s also become a whole other kind of amazing when used with FL 20, but that’s another story.

    Amazing also with this reality check: I bought the first FL Mobile 6/11, I think $14.99 (in 2011 dollars).

    Yep it’s cheap as chips. I would literally pay the same price again for auv3 support tho :)

    I don’t think you’ll have to

    Hey guys, I literally just had another update from FL Studio(Image Line) on iTunes this morning just now as I write....... I've just tested it.... Result....... Now IAA is broken "YET AGAIN!"........ FFS!........ Now this is really Pissing me off!....... WTF is the Dev doing?......

  • BiancaNeveBiancaNeve

    Call me cynical but I’m starting to think they don’t actually want IAA to work well so that eventually they can just abandon it. They talk it down at every opportunity.

    I don’t see them adding AU at anytime soon if ever either.

    One of the IL devs is on record on the forum as saying they want FLM to be a closed sandbox
    ‘The thing is that we want FLM to be a closed ‘sandbox’ thus not support open formats by purpose’

    Not to mention it would be simpler for them to keep os specific variations out of the app.

  • gregsmithgregsmith

    @BiancaNeve said:
    Call me cynical but I’m starting to think they don’t actually want IAA to work well so that eventually they can just abandon it. They talk it down at every opportunity.

    I don’t see them adding AU at anytime soon if ever either.

    One of the IL devs is on record on the forum as saying they want FLM to be a closed sandbox
    ‘The thing is that we want FLM to be a closed ‘sandbox’ thus not support open formats by purpose’

    Not to mention it would be simpler for them to keep os specific variations out of the app.

    I just updated and still seems to work for me with moog model d. Is multi core still turned off?

  • gregsmithgregsmith

    https://forum.image-line.com/viewtopic.php?f=1988&t=186997 - anyone care to answer cos hey never do :smiley:

  • LittlewoodgLittlewoodg
    edited June 2018

    @studs1966 said:

    :) > @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:

    @gregsmith said:

    @studs1966 said:

    @gregsmith said:

    @Littlewoodg said:
    Just to be clear the popping mentioned in the OP doesn’t show up in the audio recording made from Audiobus using AUV3 synths...

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    It’s odd that you say this, see my PM.

    Interesting, didn’t think to try this. I’ll give it a go for Zeeon.

    @studs1966 said:

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    Actually, I have seen your requests on the beta section on there forum, (I stopped beta testing it a long time ago)…. Yep, it does look like your acknowledgement is not there. But I did request it at the beginning of this chaos at the beginning ( A long time ago). Scott did mention it was on there "To Do" list (Also Ableton Link when I was beta testing it)….. But I would imagine the dev team were focused(at the time) on getting FL Studio 20 ready & out... (Which it is now on Windows & Mac)…… :)

    After a long wait, I don’t think they did anything off their to do list in the last update! Not the to do list in the request forum anyway.

    Hopefully they’ll get on it soon. Might see if I can get into the beta program.

    Your probably right. Probably they wanted to get all the platform devices (iOS, Android & Windows) brought up to a certain workable order, to work with Mac/PC DAW version before adding the "To Do" list for each device. Good luck on the Beta journey. It's just taken a long time for them, which is quite a large challenge really. Now that FL Studio 20 is out (also, they will probably have to sort out certain bugs on PC) Maybe they concentrate more of a focus towards the mobile section?....... Who knows?....... ;)

    Yeah tbf it must be a hell of a challenge supporting all the platforms simultaneously. They’ve made an amazing app.

    It is an amazing app. And I’m psyched to have IAA (and Audiobus, with the clicks that don’t pollute the actual recordings)

    It’s also become a whole other kind of amazing when used with FL 20, but that’s another story.

    Amazing also with this reality check: I bought the first FL Mobile 6/11, I think $14.99 (in 2011 dollars).

    Yep it’s cheap as chips. I would literally pay the same price again for auv3 support tho :)

    I don’t think you’ll have to

    Hey guys, I literally just had another update from FL Studio(Image Line) on iTunes this morning just now as I write....... I've just tested it.... Result....... Now IAA is broken "YET AGAIN!"........ FFS!........ Now this is really Pissing me off!....... WTF is the Dev doing?......

    Odd. The latest beta’s IAA (3.1.903, which is .003 of the 3.1.9 in the store) is all good -except there are a few IAA synths on my device that don’t appear on FL Studio Mobile’s IAA instrument list, and a few that are on the list that don’t connect via midi, issues I’ve had on all my other IAA hosts.

    @BiancaNeve said:
    One of the IL devs is on record on the forum as saying they want FLM to be a closed sandbox
    ‘The thing is that we want FLM to be a closed ‘sandbox’ thus not support open formats by purpose’

    When was that?

  • studs1966studs1966

    @Littlewoodg said:

    @studs1966 said:

    :) > @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:

    @gregsmith said:

    @studs1966 said:

    @gregsmith said:

    @Littlewoodg said:
    Just to be clear the popping mentioned in the OP doesn’t show up in the audio recording made from Audiobus using AUV3 synths...

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    It’s odd that you say this, see my PM.

    Interesting, didn’t think to try this. I’ll give it a go for Zeeon.

    @studs1966 said:

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    Actually, I have seen your requests on the beta section on there forum, (I stopped beta testing it a long time ago)…. Yep, it does look like your acknowledgement is not there. But I did request it at the beginning of this chaos at the beginning ( A long time ago). Scott did mention it was on there "To Do" list (Also Ableton Link when I was beta testing it)….. But I would imagine the dev team were focused(at the time) on getting FL Studio 20 ready & out... (Which it is now on Windows & Mac)…… :)

    After a long wait, I don’t think they did anything off their to do list in the last update! Not the to do list in the request forum anyway.

    Hopefully they’ll get on it soon. Might see if I can get into the beta program.

    Your probably right. Probably they wanted to get all the platform devices (iOS, Android & Windows) brought up to a certain workable order, to work with Mac/PC DAW version before adding the "To Do" list for each device. Good luck on the Beta journey. It's just taken a long time for them, which is quite a large challenge really. Now that FL Studio 20 is out (also, they will probably have to sort out certain bugs on PC) Maybe they concentrate more of a focus towards the mobile section?....... Who knows?....... ;)

    Yeah tbf it must be a hell of a challenge supporting all the platforms simultaneously. They’ve made an amazing app.

    It is an amazing app. And I’m psyched to have IAA (and Audiobus, with the clicks that don’t pollute the actual recordings)

    It’s also become a whole other kind of amazing when used with FL 20, but that’s another story.

    Amazing also with this reality check: I bought the first FL Mobile 6/11, I think $14.99 (in 2011 dollars).

    Yep it’s cheap as chips. I would literally pay the same price again for auv3 support tho :)

    I don’t think you’ll have to

    Hey guys, I literally just had another update from FL Studio(Image Line) on iTunes this morning just now as I write....... I've just tested it.... Result....... Now IAA is broken "YET AGAIN!"........ FFS!........ Now this is really Pissing me off!....... WTF is the Dev doing?......

    Odd. The latest beta’s IAA (3.1.903, which is .003 of the 3.1.9 in the store) is all good -except there are a few IAA synths on my device that don’t appear on FL Studio Mobile’s IAA instrument list, and a few that are on the list that don’t connect via midi, issues I’ve had on all my other IAA hosts.

    @BiancaNeve said:
    One of the IL devs is on record on the forum as saying they want FLM to be a closed sandbox
    ‘The thing is that we want FLM to be a closed ‘sandbox’ thus not support open formats by purpose’

    When was that?

    Update!...… I closed down my iPad(reset)……. Now it's working..... <3 Info for anybody else who probs...… Me Happy again...…. But I really hope to add AU instead if unreliable IAA?... Fingers Crossed? :*

  • gregsmithgregsmith

    @studs1966 said:

    @Littlewoodg said:

    @studs1966 said:

    :) > @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:

    @gregsmith said:

    @studs1966 said:

    @gregsmith said:

    @Littlewoodg said:
    Just to be clear the popping mentioned in the OP doesn’t show up in the audio recording made from Audiobus using AUV3 synths...

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    It’s odd that you say this, see my PM.

    Interesting, didn’t think to try this. I’ll give it a go for Zeeon.

    @studs1966 said:

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    Actually, I have seen your requests on the beta section on there forum, (I stopped beta testing it a long time ago)…. Yep, it does look like your acknowledgement is not there. But I did request it at the beginning of this chaos at the beginning ( A long time ago). Scott did mention it was on there "To Do" list (Also Ableton Link when I was beta testing it)….. But I would imagine the dev team were focused(at the time) on getting FL Studio 20 ready & out... (Which it is now on Windows & Mac)…… :)

    After a long wait, I don’t think they did anything off their to do list in the last update! Not the to do list in the request forum anyway.

    Hopefully they’ll get on it soon. Might see if I can get into the beta program.

    Your probably right. Probably they wanted to get all the platform devices (iOS, Android & Windows) brought up to a certain workable order, to work with Mac/PC DAW version before adding the "To Do" list for each device. Good luck on the Beta journey. It's just taken a long time for them, which is quite a large challenge really. Now that FL Studio 20 is out (also, they will probably have to sort out certain bugs on PC) Maybe they concentrate more of a focus towards the mobile section?....... Who knows?....... ;)

    Yeah tbf it must be a hell of a challenge supporting all the platforms simultaneously. They’ve made an amazing app.

    It is an amazing app. And I’m psyched to have IAA (and Audiobus, with the clicks that don’t pollute the actual recordings)

    It’s also become a whole other kind of amazing when used with FL 20, but that’s another story.

    Amazing also with this reality check: I bought the first FL Mobile 6/11, I think $14.99 (in 2011 dollars).

    Yep it’s cheap as chips. I would literally pay the same price again for auv3 support tho :)

    I don’t think you’ll have to

    Hey guys, I literally just had another update from FL Studio(Image Line) on iTunes this morning just now as I write....... I've just tested it.... Result....... Now IAA is broken "YET AGAIN!"........ FFS!........ Now this is really Pissing me off!....... WTF is the Dev doing?......

    Odd. The latest beta’s IAA (3.1.903, which is .003 of the 3.1.9 in the store) is all good -except there are a few IAA synths on my device that don’t appear on FL Studio Mobile’s IAA instrument list, and a few that are on the list that don’t connect via midi, issues I’ve had on all my other IAA hosts.

    @BiancaNeve said:
    One of the IL devs is on record on the forum as saying they want FLM to be a closed sandbox
    ‘The thing is that we want FLM to be a closed ‘sandbox’ thus not support open formats by purpose’

    When was that?

    Update!...… I closed down my iPad(reset)……. Now it's working..... <3 Info for anybody else who probs...… Me Happy again...…. But I really hope to add AU instead if unreliable IAA?... Fingers Crossed? :*

    I’ve had my fingers crossed so long I think I’m getting arthritis!

  • studs1966studs1966

    @gregsmith said:

    @studs1966 said:

    @Littlewoodg said:

    @studs1966 said:

    :) > @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:

    @gregsmith said:

    @studs1966 said:

    @gregsmith said:

    @Littlewoodg said:
    Just to be clear the popping mentioned in the OP doesn’t show up in the audio recording made from Audiobus using AUV3 synths...

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    It’s odd that you say this, see my PM.

    Interesting, didn’t think to try this. I’ll give it a go for Zeeon.

    @studs1966 said:

    @anickt said:

    @gregsmith said:

    @Littlewoodg said:

    @studs1966 said:

    @Littlewoodg said:

    @gregsmith said:

    @Littlewoodg said:
    Lately IAA in FLSM is working nicely has for me including Animoog, BeatHawk etc. (Including rendering to .wav)

    2 things made the difference: high buffer #s (1024) in the instruments, and turning off multi core processing in FLSM. (Working in Air 2, and now pro 10.5, current iOS.)

    Pretty psyched to bring synths into the mix that the in-app stuff doesn’t cover. I had tried Audiobus earlier and had the clicks as well, so I’m steering away currently, as IAA seems to be underway.

    For those of you having difficulty with IAA in FLSM, @anikt @purpan2 , what devices, OS are you using? And is multi core de-activated?

    Thanks for the heads up! Just tried Animoog-iPhone and Model D which instacrashed, but then I disabled multi core like you say and they seem to be working fine. One instance of each synth but I can live with that for now. This opens up about 10 new IAA synths and some IAA effects that I own.

    Cool!
    The in-app sound design potential in FLSM is so good, I didn’t think I’d be psyched to add the IAA stuff, but turns out I’m very psyched.

    Bloody hell!.. The first time it has ever worked. Turned off off Multicore in the settings & it worked!...... Animoog is up & running. Yay!...... Maybe need to tell Scott, or Maxx about it at FL Studio. Maybe a Multicore Bug thingy? But cheer for the suggestion mate. ;)

    Glad it’s working for you.
    (Posted the multi core thing on the FLSM beta thread couple days ago)

    Have you seen them mention auv3 at all? They ignore me completely!

    Never acknowledged my (multiple) requests for AU.

    Actually, I have seen your requests on the beta section on there forum, (I stopped beta testing it a long time ago)…. Yep, it does look like your acknowledgement is not there. But I did request it at the beginning of this chaos at the beginning ( A long time ago). Scott did mention it was on there "To Do" list (Also Ableton Link when I was beta testing it)….. But I would imagine the dev team were focused(at the time) on getting FL Studio 20 ready & out... (Which it is now on Windows & Mac)…… :)

    After a long wait, I don’t think they did anything off their to do list in the last update! Not the to do list in the request forum anyway.

    Hopefully they’ll get on it soon. Might see if I can get into the beta program.

    Your probably right. Probably they wanted to get all the platform devices (iOS, Android & Windows) brought up to a certain workable order, to work with Mac/PC DAW version before adding the "To Do" list for each device. Good luck on the Beta journey. It's just taken a long time for them, which is quite a large challenge really. Now that FL Studio 20 is out (also, they will probably have to sort out certain bugs on PC) Maybe they concentrate more of a focus towards the mobile section?....... Who knows?....... ;)

    Yeah tbf it must be a hell of a challenge supporting all the platforms simultaneously. They’ve made an amazing app.

    It is an amazing app. And I’m psyched to have IAA (and Audiobus, with the clicks that don’t pollute the actual recordings)

    It’s also become a whole other kind of amazing when used with FL 20, but that’s another story.

    Amazing also with this reality check: I bought the first FL Mobile 6/11, I think $14.99 (in 2011 dollars).

    Yep it’s cheap as chips. I would literally pay the same price again for auv3 support tho :)

    I don’t think you’ll have to

    Hey guys, I literally just had another update from FL Studio(Image Line) on iTunes this morning just now as I write....... I've just tested it.... Result....... Now IAA is broken "YET AGAIN!"........ FFS!........ Now this is really Pissing me off!....... WTF is the Dev doing?......

    Odd. The latest beta’s IAA (3.1.903, which is .003 of the 3.1.9 in the store) is all good -except there are a few IAA synths on my device that don’t appear on FL Studio Mobile’s IAA instrument list, and a few that are on the list that don’t connect via midi, issues I’ve had on all my other IAA hosts.

    @BiancaNeve said:
    One of the IL devs is on record on the forum as saying they want FLM to be a closed sandbox
    ‘The thing is that we want FLM to be a closed ‘sandbox’ thus not support open formats by purpose’

    When was that?

    Update!...… I closed down my iPad(reset)……. Now it's working..... <3 Info for anybody else who probs...… Me Happy again...…. But I really hope to add AU instead if unreliable IAA?... Fingers Crossed? :*

    I’ve had my fingers crossed so long I think I’m getting arthritis!

    Know what you mean. Infact, I kept my Toes crossed too.. my Left Toes are on my Right foot, & my Right Toes are on my Left foot......... Now I've got Myoxmatois. :D

  • wimwim
    edited June 2018

    Here’s one thing that works for AUv3

    • Put FLSM in AB3 midi input > AUv3 in midi output
    • On the audio tab put FLSM in an audio input or output to hear the rest of the FLSM output
    • Use MidiFlow Channels to use more than one AUv3 instrument
    • Use AUv3 FX in the audio channels.




  • gregsmithgregsmith

    @wim said:
    Here’s one thing that works for AUv3

    • Put FLSM in AB3 midi input > AUv3 in midi output
    • On the audio tab put FLSM in an audio input or output to hear the rest of the FLSM output
    • Use MidiFlow Channels to use more than one AUv3 instrument
    • Use AUv3 FX in the audio channels.




    Do you not get pops and crackles? I think this is what I was trying earlier in this thread. Apparently although you get problems on playback you don’t when recording into an audio track but I’m yet to try it.

  • wimwim
    edited June 2018

    It worked great when I first tried it, but then went haywire when I tried it with another AU app a few hours later. Beats me. I give up - as I always do with this app. I wish I could appreciate it as a stand-alone app like others do, but it bugs me too much to use something that is just so perennially broken.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025