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.

Open beta - Wireless Audio AUv3

12346

Comments

  • wimwim
    edited January 2022

    @SecretBaseDesign said:
    A fix for the folks who need to route into semi-broken DAWs!

    The Wireless Audio AUv3s are compatible with my old Apollo Sound Injector app -- which supports IAA. The latency correction in the new AUv3s is smarter, but the old stuff will still work. Injector can connect to Transmit, and then you should be able to send audio into more places; I just used it to send drums from AUM into Garageband.

    I had put the old IAA stuff on the back burner; still in the store, and free, because IAA was so flaky and such a pain in the butt. The right solution, though, is to get everything on to AUv3. AUM and Loopy Pro have gotten it sorted out, and I hope other DAWs do too.

    I don't really understand why you consider the DAW's broken when clearly they can host audio plugins with no issue. I'm not in any way qualified to judge, but it seems to me it's a shortcoming of the plugin itself rather than the DAWs. The other plugin that does this kind of thing can manage it, so I assume it's doable.

    Sorry, I'm probably way out of line, not ever having successfully made an AUv3 plugin (not for lack of trying though).

    I really don't expect DAW developers to "fix" something that I don't think they consider broken. Which means unfortunately that a change coming from that direction is unlikely.

  • SecretBaseDesignSecretBaseDesign

    @wim said:

    @SecretBaseDesign said:
    A fix for the folks who need to route into semi-broken DAWs!

    The Wireless Audio AUv3s are compatible with my old Apollo Sound Injector app -- which supports IAA. The latency correction in the new AUv3s is smarter, but the old stuff will still work. Injector can connect to Transmit, and then you should be able to send audio into more places; I just used it to send drums from AUM into Garageband.

    I had put the old IAA stuff on the back burner; still in the store, and free, because IAA was so flaky and such a pain in the butt. The right solution, though, is to get everything on to AUv3. AUM and Loopy Pro have gotten it sorted out, and I hope other DAWs do too.

    I don't really understand why you consider the DAW's broken when clearly they can host audio plugins with no issue. I'm not in any way qualified to judge, but it seems to me it's a shortcoming of the plugin itself rather than the DAWs. The other plugin that does this kind of thing can manage it, so I assume it's doable.

    Sorry, I'm probably way out of line, not ever having successfully made an AUv3 plugin (not for lack of trying though).

    I really don't expect DAW developers to "fix" something that I don't think they consider broken. Which means unfortunately that a change coming from that direction is unlikely.

    Apple is trying to move developers away from IAA. The new AUv3 is a lot more extensible, and I think lower CPU demand too. It's easy to instantiate multiple copies. Long term, AUv3 is going to cause a lot less drama and grief.

    If an app is already an AUv3 host and can capture audio, it shouldn't be hard to add support for generator nodes -- everyone has a for loop to scan the installed plug-ins, and the only change needed is to list both AUMU and AUGN plugs. Not much more than an if statement added to the code, and it should work. My hope is that's what happens; DAWs make the tweak to support generator nodes, rather than having to patch together IAA or do some sort of crazy track routing.

    I suppose calling DAWs "broken" is a bit strong -- more likely, it hadn't occurred to some devs that the generator nodes would be useful, so they never got put in. Maybe the Wireless plug will nudge some devs to hack their code a little bit.

  • wimwim
    edited January 2022

    @SecretBaseDesign said:

    @wim said:

    @SecretBaseDesign said:
    A fix for the folks who need to route into semi-broken DAWs!

    The Wireless Audio AUv3s are compatible with my old Apollo Sound Injector app -- which supports IAA. The latency correction in the new AUv3s is smarter, but the old stuff will still work. Injector can connect to Transmit, and then you should be able to send audio into more places; I just used it to send drums from AUM into Garageband.

    I had put the old IAA stuff on the back burner; still in the store, and free, because IAA was so flaky and such a pain in the butt. The right solution, though, is to get everything on to AUv3. AUM and Loopy Pro have gotten it sorted out, and I hope other DAWs do too.

    I don't really understand why you consider the DAW's broken when clearly they can host audio plugins with no issue. I'm not in any way qualified to judge, but it seems to me it's a shortcoming of the plugin itself rather than the DAWs. The other plugin that does this kind of thing can manage it, so I assume it's doable.

    Sorry, I'm probably way out of line, not ever having successfully made an AUv3 plugin (not for lack of trying though).

    I really don't expect DAW developers to "fix" something that I don't think they consider broken. Which means unfortunately that a change coming from that direction is unlikely.

    Apple is trying to move developers away from IAA. The new AUv3 is a lot more extensible, and I think lower CPU demand too. It's easy to instantiate multiple copies. Long term, AUv3 is going to cause a lot less drama and grief.

    I wasn't talking at all about IAA. I wouldn't suggest that for anyone, and I wouldn't use it if available.

    If an app is already an AUv3 host and can capture audio, it shouldn't be hard to add support for generator nodes -- everyone has a for loop to scan the installed plug-ins, and the only change needed is to list both AUMU and AUGN plugs. Not much more than an if statement added to the code, and it should work. My hope is that's what happens; DAWs make the tweak to support generator nodes, rather than having to patch together IAA or do some sort of crazy track routing.

    I suppose calling DAWs "broken" is a bit strong -- more likely, it hadn't occurred to some devs that the generator nodes would be useful, so they never got put in. Maybe the Wireless plug will nudge some devs to hack their code a little bit.

    My point is, I think Receiver could perhaps have an audio unit type identifier that the hosts support. Why not make it an AUMU rather than expecting the DAWs to support AUGN plugins? Or, include two versions of the plugin? Is there a reason that I don't understand for this? (Sorry ... I studied what I could of this some time ago, and could well not know at all what I'm talking about)

    Would the fact that it doesn't respond to midi to produce sound be a real issue? Could not a "do nothing" handler for incoming midi be added? I believe aumu apps can also generate sound on their own not in response to midi, so I don't think that would be an issue, but I could be wrong.

    Sorry if I'm talkin' out of me arse here. :D

  • SecretBaseDesignSecretBaseDesign

    @wim said:

    @SecretBaseDesign said:

    @wim said:

    @SecretBaseDesign said:
    A fix for the folks who need to route into semi-broken DAWs!

    The Wireless Audio AUv3s are compatible with my old Apollo Sound Injector app -- which supports IAA. The latency correction in the new AUv3s is smarter, but the old stuff will still work. Injector can connect to Transmit, and then you should be able to send audio into more places; I just used it to send drums from AUM into Garageband.

    I had put the old IAA stuff on the back burner; still in the store, and free, because IAA was so flaky and such a pain in the butt. The right solution, though, is to get everything on to AUv3. AUM and Loopy Pro have gotten it sorted out, and I hope other DAWs do too.

    I don't really understand why you consider the DAW's broken when clearly they can host audio plugins with no issue. I'm not in any way qualified to judge, but it seems to me it's a shortcoming of the plugin itself rather than the DAWs. The other plugin that does this kind of thing can manage it, so I assume it's doable.

    Sorry, I'm probably way out of line, not ever having successfully made an AUv3 plugin (not for lack of trying though).

    I really don't expect DAW developers to "fix" something that I don't think they consider broken. Which means unfortunately that a change coming from that direction is unlikely.

    Apple is trying to move developers away from IAA. The new AUv3 is a lot more extensible, and I think lower CPU demand too. It's easy to instantiate multiple copies. Long term, AUv3 is going to cause a lot less drama and grief.

    I wasn't talking at all about IAA. I wouldn't suggest that for anyone, and I wouldn't use it if available.

    If an app is already an AUv3 host and can capture audio, it shouldn't be hard to add support for generator nodes -- everyone has a for loop to scan the installed plug-ins, and the only change needed is to list both AUMU and AUGN plugs. Not much more than an if statement added to the code, and it should work. My hope is that's what happens; DAWs make the tweak to support generator nodes, rather than having to patch together IAA or do some sort of crazy track routing.

    I suppose calling DAWs "broken" is a bit strong -- more likely, it hadn't occurred to some devs that the generator nodes would be useful, so they never got put in. Maybe the Wireless plug will nudge some devs to hack their code a little bit.

    My point is, I think Receiver should have a version that has the audio unit type identifier that the hosts support. Why not make it an AUMU rather than expecting the DAWs to support AUGN plugins? Or, include two versions of the plugin? Is there a reason that I don't understand for this? (Sorry ... I studied what I could of this some time ago, and could well not know at all what I'm talking about)

    Would the fact that it doesn't respond to midi to produce sound be a real issue? Could not a "do nothing" handler for incoming midi be added? I believe aumu apps can also generate sound on their own not in response to midi, so I don't think that would be an issue, but I could be wrong.

    Sorry if I'm talkin' out of me arse here. :D

    Whole can of potential worms! I can list the plug as AUMU, but then the DAW host would likely only record MIDI sent to the plug, and ignore the audio entirely. You could potentially route the audio out of the first track, and then record it into a second track; that would 100% work. But for every person who gets that working, there'd be 100 angry technical support emails -- and I'd have to figure out how to do things in every DAW.

    If I insert the Receive plug as an effect (the same as Transmit), many DAWs won't flow audio through a track unless there's audio at the top being generated. This means you'd need to add a mic input at the top, the mic audio gets ignored completely, and the effect plug overwrites, and creates the audio. The trouble here -- most DAWs only record the raw input at the mic step (because there's a good chance someone will want to tweak the effects setting during mixing). Reaper has the ability to record the output -- but that's the only DAW I know of that does this.

    IMO, the right solution is what AUM and Loopy Pro are doing -- recognize that audio is coming out of a node spontaneously, and record it. If the DAW has support for a microphone -- then it's essentially "treat this like a microphone."

  • 0tolerance4silence0tolerance4silence

    Just adding to discussion...
    When beta became available, Drambo had (current AppStore version still has) the same ‘issue’.
    When I mentioned this to the dev, he enabled the type of plugin to be listed and that’s all.
    The main problem seems to be that some hosts are no longer actively developed / devs went quiet.

  • wimwim
    edited January 2022

    The VCO plugin that comes with iVCS3 is an example of an aumu (I think) that generates sound on its own > @SecretBaseDesign said:

    @wim said:

    @SecretBaseDesign said:

    @wim said:

    @SecretBaseDesign said:
    A fix for the folks who need to route into semi-broken DAWs!

    The Wireless Audio AUv3s are compatible with my old Apollo Sound Injector app -- which supports IAA. The latency correction in the new AUv3s is smarter, but the old stuff will still work. Injector can connect to Transmit, and then you should be able to send audio into more places; I just used it to send drums from AUM into Garageband.

    I had put the old IAA stuff on the back burner; still in the store, and free, because IAA was so flaky and such a pain in the butt. The right solution, though, is to get everything on to AUv3. AUM and Loopy Pro have gotten it sorted out, and I hope other DAWs do too.

    I don't really understand why you consider the DAW's broken when clearly they can host audio plugins with no issue. I'm not in any way qualified to judge, but it seems to me it's a shortcoming of the plugin itself rather than the DAWs. The other plugin that does this kind of thing can manage it, so I assume it's doable.

    Sorry, I'm probably way out of line, not ever having successfully made an AUv3 plugin (not for lack of trying though).

    I really don't expect DAW developers to "fix" something that I don't think they consider broken. Which means unfortunately that a change coming from that direction is unlikely.

    Apple is trying to move developers away from IAA. The new AUv3 is a lot more extensible, and I think lower CPU demand too. It's easy to instantiate multiple copies. Long term, AUv3 is going to cause a lot less drama and grief.

    I wasn't talking at all about IAA. I wouldn't suggest that for anyone, and I wouldn't use it if available.

    If an app is already an AUv3 host and can capture audio, it shouldn't be hard to add support for generator nodes -- everyone has a for loop to scan the installed plug-ins, and the only change needed is to list both AUMU and AUGN plugs. Not much more than an if statement added to the code, and it should work. My hope is that's what happens; DAWs make the tweak to support generator nodes, rather than having to patch together IAA or do some sort of crazy track routing.

    I suppose calling DAWs "broken" is a bit strong -- more likely, it hadn't occurred to some devs that the generator nodes would be useful, so they never got put in. Maybe the Wireless plug will nudge some devs to hack their code a little bit.

    My point is, I think Receiver should have a version that has the audio unit type identifier that the hosts support. Why not make it an AUMU rather than expecting the DAWs to support AUGN plugins? Or, include two versions of the plugin? Is there a reason that I don't understand for this? (Sorry ... I studied what I could of this some time ago, and could well not know at all what I'm talking about)

    Would the fact that it doesn't respond to midi to produce sound be a real issue? Could not a "do nothing" handler for incoming midi be added? I believe aumu apps can also generate sound on their own not in response to midi, so I don't think that would be an issue, but I could be wrong.

    Sorry if I'm talkin' out of me arse here. :D

    Whole can of potential worms! I can list the plug as AUMU, but then the DAW host would likely only record MIDI sent to the plug, and ignore the audio entirely. You could potentially route the audio out of the first track, and then record it into a second track; that would 100% work. But for every person who gets that working, there'd be 100 angry technical support emails -- and I'd have to figure out how to do things in every DAW.

    If I insert the Receive plug as an effect (the same as Transmit), many DAWs won't flow audio through a track unless there's audio at the top being generated. This means you'd need to add a mic input at the top, the mic audio gets ignored completely, and the effect plug overwrites, and creates the audio. The trouble here -- most DAWs only record the raw input at the mic step (because there's a good chance someone will want to tweak the effects setting during mixing). Reaper has the ability to record the output -- but that's the only DAW I know of that does this.

    IMO, the right solution is what AUM and Loopy Pro are doing -- recognize that audio is coming out of a node spontaneously, and record it. If the DAW has support for a microphone -- then it's essentially "treat this like a microphone."

    Thanks for the clear answer. I can certainly respect that choice, though I'll admit it does make me less excited about the app.

    So, @MisplacedDevelopment - I guess we have some developer contacts to make if we hope to be able to use this to get sound into Cubasis, NS2, Zenbeats, Auria, etc. eventually. That'll be on my todo list for tomorrow. ;)

  • nuno_agogonuno_agogo
    edited January 2022

    just tried to receive with multiple devices at the same time but as soon i want to connect another device the first disconnects.

    the idea was to setup an audio installation with multiple ipads that receive the same signal but processing the input differently on each and at other places in the room or moving.

    would be great to be able to receive on multiple devices. guess the traffic would be to much in the end.

  • wimwim
    edited January 2022

    @nuno_agogo said:
    just tried to receive with multiple devices at the same time but as soon i want to connect another device the first disconnects.

    the idea was to setup an audio installation with multiple ipads that receive the same signal but processing the input differently on each and at other places in the room or moving.

    would be great to be able to receive on multiple devices. guess the traffic would be to much in the end.

    Sonobus is more complicated and has significantly more latency, but it does what you mention.

  • nuno_agogonuno_agogo

    @wim said:

    @nuno_agogo said:
    just tried to receive with multiple devices at the same time but as soon i want to connect another device the first disconnects.

    the idea was to setup an audio installation with multiple ipads that receive the same signal but processing the input differently on each and at other places in the room or moving.

    would be great to be able to receive on multiple devices. guess the traffic would be to much in the end.

    Try Sonobus. It's more complicated and has more latency. I prefer Wireless Audio for these reasons. But Sonobus does do what you want.

    was also thinking to accomplish it with sonobus. it just that streamlined workflow that would make things so easy to setup with WirelessAuv3 :)

  • SecretBaseDesignSecretBaseDesign

    @nuno_agogo said:

    @wim said:

    @nuno_agogo said:
    just tried to receive with multiple devices at the same time but as soon i want to connect another device the first disconnects.

    the idea was to setup an audio installation with multiple ipads that receive the same signal but processing the input differently on each and at other places in the room or moving.

    would be great to be able to receive on multiple devices. guess the traffic would be to much in the end.

    Try Sonobus. It's more complicated and has more latency. I prefer Wireless Audio for these reasons. But Sonobus does do what you want.

    was also thinking to accomplish it with sonobus. it just that streamlined workflow that would make things so easy to setup with WirelessAuv3 :)

    In the current setup, a new connection from Receive will close a current connection. I'm trying to keep the network bandwidth demands low, so that communications are low latency and reliable. I've got another thing in the works that will handle multiple connections, but that's a ways off yet.

  • Aud_iOSAud_iOS

    Just playing today with the app. If you’re connecting to a Mac, you can disable Wi-fi if you’re using the Internet Sharing feature, and the Mac is connected via Ethernet. Also both plugs load and work in Hosting AU! Cool stuff!

  • wimwim

    @Aud_iOS said:
    Just playing today with the app. If you’re connecting to a Mac, you can disable Wi-fi if you’re using the Internet Sharing feature, and the Mac is connected via Ethernet. Also both plugs load and work in Hosting AU! Cool stuff!

    M1 Mac I presume?

  • SecretBaseDesignSecretBaseDesign

    Good to hear that people are having success with the Mac (M1 macs, right?). I'm planning on making a native Mac version, which will be bundled with the iOS app in the app store -- so x86 Macs can get on board too.

    I was hoping to have this released by now, but it'll take a little more time. Apple reviewers didn't like that the main app doesn't do anything; just having AUv3s isn't enough. The main app will be able to be a transmitter or receiver, and I'll add the ability to use the mic, or host an IAA app (giving an easier way to bridge in IAA to an AUv3-only host).

    With a little bit of luck, and a lot of coffee, I'll have it all done soon.

  • espiegel123espiegel123

    @SecretBaseDesign said:
    Good to hear that people are having success with the Mac (M1 macs, right?). I'm planning on making a native Mac version, which will be bundled with the iOS app in the app store -- so x86 Macs can get on board too.

    I was hoping to have this released by now, but it'll take a little more time. Apple reviewers didn't like that the main app doesn't do anything; just having AUv3s isn't enough. The main app will be able to be a transmitter or receiver, and I'll add the ability to use the mic, or host an IAA app (giving an easier way to bridge in IAA to an AUv3-only host).

    With a little bit of luck, and a lot of coffee, I'll have it all done soon.

    Btw, sending from AUM to Loopy Pro on the same device on an iPad 6 running with a 128 buffer, the one way latency is from 40-60 ms. Is that about what other are getting?

  • Aud_iOSAud_iOS

    @SecretBaseDesign said:
    Good to hear that people are having success with the Mac (M1 macs, right?). I'm planning on making a native Mac version, which will be bundled with the iOS app in the app store -- so x86 Macs can get on board too.

    I was hoping to have this released by now, but it'll take a little more time. Apple reviewers didn't like that the main app doesn't do anything; just having AUv3s isn't enough. The main app will be able to be a transmitter or receiver, and I'll add the ability to use the mic, or host an IAA app (giving an easier way to bridge in IAA to an AUv3-only host).

    With a little bit of luck, and a lot of coffee, I'll have it all done soon.

    @SecretBaseDesign Is there a way to connect to Apple's AUNetReceive plugin? I tried creating an entry in the directory with myip:8675. I loaded the Transmit plugin in an Audiobus FX slot with some audio playing, enabled Transmit, then hit the connect button on the AUNetSend plugin. No audio transmission - but when I disconnect that AUNetSend session - it forces the Transmit plugin to the Restart state - so something is happening. I did check the addresses in the browser. Should this work?

  • SecretBaseDesignSecretBaseDesign

    @Aud_iOS said:

    @SecretBaseDesign said:
    Good to hear that people are having success with the Mac (M1 macs, right?). I'm planning on making a native Mac version, which will be bundled with the iOS app in the app store -- so x86 Macs can get on board too.

    I was hoping to have this released by now, but it'll take a little more time. Apple reviewers didn't like that the main app doesn't do anything; just having AUv3s isn't enough. The main app will be able to be a transmitter or receiver, and I'll add the ability to use the mic, or host an IAA app (giving an easier way to bridge in IAA to an AUv3-only host).

    With a little bit of luck, and a lot of coffee, I'll have it all done soon.

    @SecretBaseDesign Is there a way to connect to Apple's AUNetReceive plugin? I tried creating an entry in the directory with myip:8675. I loaded the Transmit plugin in an Audiobus FX slot with some audio playing, enabled Transmit, then hit the connect button on the AUNetSend plugin. No audio transmission - but when I disconnect that AUNetSend session - it forces the Transmit plugin to the Restart state - so something is happening. I did check the addresses in the browser. Should this work?

    My stuff isn't compatible with the Apple AUNet Send/Receive plugs -- I don't know what protocol they use (apart from the foundation of TCP/IP).

  • The Krazy WabbitThe Krazy Wabbit

    Hi. Just signed up. Gear. IPad Air 2020 on latest iOS 15.2.1 and iPhone 12 Pro Max with same iOS. AUM previously installed on both devices. iPad set up as the transmit. Loaded BLEASS Omega. IPhone the receiver running into Koala. Bingo! Worked great. I have not set up or checked latency as I am just excited to get this work as ironically today I was looking for something like this setup and someone mentioned in social media about this beta program. THANK YOU!!!

    As this is in beta, are we allowed to share this on social media or make YouTube videos?

  • SecretBaseDesignSecretBaseDesign

    @DigableCreative said:
    Hi. Just signed up. Gear. IPad Air 2020 on latest iOS 15.2.1 and iPhone 12 Pro Max with same iOS. AUM previously installed on both devices. iPad set up as the transmit. Loaded BLEASS Omega. IPhone the receiver running into Koala. Bingo! Worked great. I have not set up or checked latency as I am just excited to get this work as ironically today I was looking for something like this setup and someone mentioned in social media about this beta program. THANK YOU!!!

    As this is in beta, are we allowed to share this on social media or make YouTube videos?

    Go ahead and social media/YouTube/whatever.

    The full release is a bit delayed -- Apple wants more functionality in the main app, and I'm slammed with another project (and start of the semester!), so it'll be a bit before I can get that done. Need more coffee. Need more time. Hope to have it done soon.

  • PoppadocrockPoppadocrock

    @SecretBaseDesign said:

    @DigableCreative said:
    Hi. Just signed up. Gear. IPad Air 2020 on latest iOS 15.2.1 and iPhone 12 Pro Max with same iOS. AUM previously installed on both devices. iPad set up as the transmit. Loaded BLEASS Omega. IPhone the receiver running into Koala. Bingo! Worked great. I have not set up or checked latency as I am just excited to get this work as ironically today I was looking for something like this setup and someone mentioned in social media about this beta program. THANK YOU!!!

    As this is in beta, are we allowed to share this on social media or make YouTube videos?

    Go ahead and social media/YouTube/whatever.

    The full release is a bit delayed -- Apple wants more functionality in the main app, and I'm slammed with another project (and start of the semester!), so it'll be a bit before I can get that done. Need more coffee. Need more time. Hope to have it done soon.

    Hey @SecretBaseDesign i know you said you were backed up and busy just wanted to check in on this one since I really liked the app and the beta expired. No rush, hope all is well, cheers!

  • SecretBaseDesignSecretBaseDesign

    @Poppadocrock said:

    @SecretBaseDesign said:

    @DigableCreative said:
    Hi. Just signed up. Gear. IPad Air 2020 on latest iOS 15.2.1 and iPhone 12 Pro Max with same iOS. AUM previously installed on both devices. iPad set up as the transmit. Loaded BLEASS Omega. IPhone the receiver running into Koala. Bingo! Worked great. I have not set up or checked latency as I am just excited to get this work as ironically today I was looking for something like this setup and someone mentioned in social media about this beta program. THANK YOU!!!

    As this is in beta, are we allowed to share this on social media or make YouTube videos?

    Go ahead and social media/YouTube/whatever.

    The full release is a bit delayed -- Apple wants more functionality in the main app, and I'm slammed with another project (and start of the semester!), so it'll be a bit before I can get that done. Need more coffee. Need more time. Hope to have it done soon.

    Hey @SecretBaseDesign i know you said you were backed up and busy just wanted to check in on this one since I really liked the app and the beta expired. No rush, hope all is well, cheers!

    Good to know -- I'll see if I can push out another beta, and keep everyone going who's been using it. I keep thinking I'll get more time to work on stuff, and instead, the real world keeps crashing in.

  • espiegel123espiegel123

    @SecretBaseDesign said:

    @Poppadocrock said:

    @SecretBaseDesign said:

    @DigableCreative said:
    Hi. Just signed up. Gear. IPad Air 2020 on latest iOS 15.2.1 and iPhone 12 Pro Max with same iOS. AUM previously installed on both devices. iPad set up as the transmit. Loaded BLEASS Omega. IPhone the receiver running into Koala. Bingo! Worked great. I have not set up or checked latency as I am just excited to get this work as ironically today I was looking for something like this setup and someone mentioned in social media about this beta program. THANK YOU!!!

    As this is in beta, are we allowed to share this on social media or make YouTube videos?

    Go ahead and social media/YouTube/whatever.

    The full release is a bit delayed -- Apple wants more functionality in the main app, and I'm slammed with another project (and start of the semester!), so it'll be a bit before I can get that done. Need more coffee. Need more time. Hope to have it done soon.

    Hey @SecretBaseDesign i know you said you were backed up and busy just wanted to check in on this one since I really liked the app and the beta expired. No rush, hope all is well, cheers!

    Good to know -- I'll see if I can push out another beta, and keep everyone going who's been using it. I keep thinking I'll get more time to work on stuff, and instead, the real world keeps crashing in.

    Great!

  • SecretBaseDesignSecretBaseDesign

    Open Beta updated -- should be good to go for a while. The end of the semester is in sight, and I might be able to free up some time to get it app-store ready. I'm thinking I'll add IAA hosting to the main app, and maybe microphone input too, and hopefully that'll be enough to make Apple happy. Here's the link to the beta if anyone needs it. Let me know if you have trouble!

    https://testflight.apple.com/join/zHC6006R

  • PoppadocrockPoppadocrock

    @SecretBaseDesign said:

    @Poppadocrock said:

    @SecretBaseDesign said:

    @DigableCreative said:
    Hi. Just signed up. Gear. IPad Air 2020 on latest iOS 15.2.1 and iPhone 12 Pro Max with same iOS. AUM previously installed on both devices. iPad set up as the transmit. Loaded BLEASS Omega. IPhone the receiver running into Koala. Bingo! Worked great. I have not set up or checked latency as I am just excited to get this work as ironically today I was looking for something like this setup and someone mentioned in social media about this beta program. THANK YOU!!!

    As this is in beta, are we allowed to share this on social media or make YouTube videos?

    Go ahead and social media/YouTube/whatever.

    The full release is a bit delayed -- Apple wants more functionality in the main app, and I'm slammed with another project (and start of the semester!), so it'll be a bit before I can get that done. Need more coffee. Need more time. Hope to have it done soon.

    Hey @SecretBaseDesign i know you said you were backed up and busy just wanted to check in on this one since I really liked the app and the beta expired. No rush, hope all is well, cheers!

    Good to know -- I'll see if I can push out another beta, and keep everyone going who's been using it. I keep thinking I'll get more time to work on stuff, and instead, the real world keeps crashing in.

    Totally understandable. Awesome and thanks. Wow, That was quick. Cheers!

  • wahnfriedenwahnfrieden
    edited June 2022

    How's it going? Eagerly awaiting the M1 macOS version. edit: I see now there's M1 macOS beta available

    Are you open to licensing or partnering on integrating the core of this into another AUv3 project? Or open sourcing if you're not commercializing it? Thanks

  • SecretBaseDesignSecretBaseDesign

    @wahnfrieden said:
    How's it going? Eagerly awaiting the M1 macOS version. edit: I see now there's M1 macOS beta available

    Are you open to licensing or partnering on integrating the core of this into another AUv3 project? Or open sourcing if you're not commercializing it? Thanks

    Still on the to-do list, and my schedule is a little better this summer. Hoping to get this knocked out and in the store for real before Fall.

  • wahnfriedenwahnfrieden

    Can I contact you? I'm a professional iOS developer with a music project

  • SecretBaseDesignSecretBaseDesign

    @wahnfrieden said:
    Can I contact you? I'm a professional iOS developer with a music project

    Sure -- drop me an email at [email protected]

  • PynchonPynchon
    edited June 2022

    [Deleted)]

    (Ups, I confused Secret Based Desig with Living Memory Software, I deleted this)

  • [Deleted User][Deleted User]

    @SecretBaseDesign said:
    Open Beta updated -- should be good to go for a while. The end of the semester is in sight, and I might be able to free up some time to get it app-store ready. I'm thinking I'll add IAA hosting to the main app, and maybe microphone input too, and hopefully that'll be enough to make Apple happy. Here's the link to the beta if anyone needs it. Let me know if you have trouble!

    https://testflight.apple.com/join/zHC6006R

    On clicking the link TestFlight informs me that the beta is not accepting new users. Is this correct?

  • SecretBaseDesignSecretBaseDesign

    @prtr_jan said:

    @SecretBaseDesign said:
    Open Beta updated -- should be good to go for a while. The end of the semester is in sight, and I might be able to free up some time to get it app-store ready. I'm thinking I'll add IAA hosting to the main app, and maybe microphone input too, and hopefully that'll be enough to make Apple happy. Here's the link to the beta if anyone needs it. Let me know if you have trouble!

    https://testflight.apple.com/join/zHC6006R

    On clicking the link TestFlight informs me that the beta is not accepting new users. Is this correct?

    Looks like the current beta version in TestFlight has expired -- I'll try to get another build together in the next few days, and open it up again. Things have really gone sideways this summer, and I'm behind schedule on getting a "final" version into the app store.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025