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.

SideRack by NovoNotes Connects DAWs with iOS Apps

245678

Comments

  • I would also immediately buy if there was a windows vst version.

    My pc and iOS environments are so segregated right now. I’ve been looking for this type of connection app for a veerrrryy long time.

    Personally I found iconnectivity to be extremely clunky even after taking the time to set it up properly.

  • @triple7 said:
    i tested siderack... and it worked well enough> @GrimLucky said:

    @mistercharlie said:
    I'm also getting big CPU spikes, up to ~90%, but not always. Very neat app though! Just Works™

    Seems to be working better for me now after playing around with the buffers and sample rate, I think iPhone is locked to 48k.

    I’m getting some hanging notes when using multi channel midi fx so have sent a feedback form.

    Really good app though, and was pleased to see it render everything nicely in Ableton.

    would you be able to do a test with midi sync'ing or ableton link if you get time.. & tell us if these syncing is working while connected to that plugin??
    thanks!

    I think the plugin and app has it’s own sync to the desktop host, turning link on in Ableton didn’t seem to make any difference.

  • @GrimLucky said:

    @triple7 said:
    i tested siderack... and it worked well enough> @GrimLucky said:

    @mistercharlie said:
    I'm also getting big CPU spikes, up to ~90%, but not always. Very neat app though! Just Works™

    Seems to be working better for me now after playing around with the buffers and sample rate, I think iPhone is locked to 48k.

    I’m getting some hanging notes when using multi channel midi fx so have sent a feedback form.

    Really good app though, and was pleased to see it render everything nicely in Ableton.

    would you be able to do a test with midi sync'ing or ableton link if you get time.. & tell us if these syncing is working while connected to that plugin??
    thanks!

    I think the plugin and app has it’s own sync to the desktop host, turning link on in Ableton didn’t seem to make any difference.

    The developer said as much here:
    https://forum.audiob.us/discussion/comment/1306909/#Comment_1306909

  • edited March 4

    @Rudd_Ruse said:
    Personally I found iconnectivity to be extremely clunky even after taking the time to set it up properly.

    I'm so glad it haven't bought it last month, It was close.

  • @jebni said:
    Considering @wim's point: if cost were no factor, what’s the most friction free way for an iPad to essentially be an effects send bus for local tracks in a Mac DAW? IDAM can't do this, correct?

    We believe SideRack is the most friction free in many cases. IMO, while IDAM can manage very simple use cases, such as sending MIDI and receiving stereo audio for a single synth instance, SideRack provides many advantages in more complex scenarios, which makes your workflow smooth.

  • @tyslothrop1 said:
    @satoshiszk This looks really cool. If it were available for windows PCs I would get it right away. Is there any chance of a windows version?

    Thank you for your comment! We highly value our users' requests when prioritizing our development tasks.

    Certainly, we'd love to make our plugin available on Windows, and have explored ways to achieve this. However, we encountered technical challenges, leading us to adopt a Mac-specific approach for the initial release.

    Given that this is one of our most frequently requested features, we will give it high priority. However, I must admit that the task is quite challenging and is expected to take at least six months.

  • edited March 7

    Let me clarify our roadmap.

    Currently working towards the next release:

    • Fixing crash on macOS 11 duaring license activation
    • Enabling Duo to run in the background (already implemented but requires negotiation with Apple)
    • Small bug fixes
    • Performance optimizations

    Needs triage:

    • Dark mode GUI
    • Override screen auto-lock timer while using Duo

    Important, but requires investigation before any planning:

    • Windows support for the SideRack plugin
    • Monitoring AUv3 plugin sounds through an audio interface on iOS devices
    • Settings for internal buffer size to control the plugin latency
  • edited March 5

    @GrimLucky said:

    Seems to be working better for me now after playing around with the buffers and sample rate, I think iPhone is locked to 48k.
    I’m getting some hanging notes when using multi channel midi fx so have sent a feedback form.

    I'd like to clarify that while it's not confirmed that the iPhone is locked to a specific sample rate, our plugin indeed is sensitive to changes in buffer size and sample rate compared to many other plugins. We recommend users carefully adjust these settings to prevent CPU spikes and noise.

    Thanks for sending feedback to the form. We will investigate that issue soon.

  • @satoshiszk said:

    @tyslothrop1 said:
    @satoshiszk This looks really cool. If it were available for windows PCs I would get it right away. Is there any chance of a windows version?

    Thank you for your comment! We highly value our users' requests when prioritizing our development tasks.

    Certainly, we'd love to make our plugin available on Windows, and have explored ways to achieve this. However, we encountered technical challenges, leading us to adopt a Mac-specific approach for the initial release.

    Given that this is one of our most frequently requested features, we will give it high priority. However, I must admit that the task is quite challenging and is expected to take at least six months.

    Nice, hope you find a way to make it happen :)

  • @satoshiszk said:
    Let me clarify our roadmap.

    Currently working towards the next release:

    • Bug fixes
    • Performance optimizations
    • Enabling Duo to run in the background (already implemented but requires negotiation with Apple)

    Important, but requires investigation to implement:

    • Windows support for the SideRack plugin
    • Monitoring AUv3 plugin sounds through an audio interface on iOS devices

    Awesome! In the meantime, could you at least override the user's screen auto-lock timer while the app is open? At the moment, the connection is broken when my iPad goes to the lock screen after a couple of minutes of not touching the screen. Is that a separate issue to running in the background?

    I know it's a thorny interaction design problem, and circumventing the lock is not an ideal solution, since if I leave such lock-overriding apps open and walk away while my iPad might not be charging, my battery will just drain. But I think the alternative of having a broken connection is more of a hassle.

    (And users shouldn't be expected to remember to turn their auto-lock on and off whenever they have a session that might involve intensive but long stretches of interaction-free use. Is there another way to take non-touch activity into account, so that if nothing is truly happening, the screen gets locked?)

  • @jebni said:

    Awesome! In the meantime, could you at least override the user's screen auto-lock timer while the app is open? At the moment, the connection is broken when my iPad goes to the lock screen after a couple of minutes of not touching the screen. Is that a separate issue to running in the background?

    I know it's a thorny interaction design problem, and circumventing the lock is not an ideal solution, since if I leave such lock-overriding apps open and walk away while my iPad might not be charging, my battery will just drain. But I think the alternative of having a broken connection is more of a hassle.

    (And users shouldn't be expected to remember to turn their auto-lock on and off whenever they have a session that might involve intensive but long stretches of interaction-free use. Is there another way to take non-touch activity into account, so that if nothing is truly happening, the screen gets locked?)

    Thank you for giving us details about your request. Receiving feedback is very beneficial to our development process.

    Implementing your "override auto-lock timer" idea seems doable. However, the issue of "broken connection when iPad goes to the lock screen" should be resolved once background mode arrives. Even in the lock screen state, audio processing will continue, and you can immediately resume the previous operation once the lock is unlocked. Would this solve your problem?

  • This is so cool! This was on my wishlist for a very long time. I really like that it saves everything in the DAW project. But the latency is a bit of a bummer, I wouldn't consider 85ms as low latency. Will this be getting substantially better in the future? Like about <15ms or so? If not, could there be a mode which uses an external audio interface for the audio output?

  • As a sad Studiomux refugee, SideRack is looking really interesting. Just been playing with the demo and very impressed in the short bursts I've attempted, although @satoshiszk please can you extend the demo time? 5 mins is way too short to test things out properly.

    Has anyone had any joy with Loopy Pro? I can't seem to send audio or get Loopy to respond to the clock. I have had success sending and recording audio in Salome and Enso, also clock working properly with EG Nodes.

    Not tried more than two synths in a rack yet (Nambu and FRMS), but all very promising so far. Thank you NovoNotes, definitely filling a gap. I have a Lewitt Connect 6 that I will continue to use to combine AUM sessions with my laptop, but this looks like it will give great additional / alternative functionality.

  • @figgelz said:
    But the latency is a bit of a bummer, I wouldn't consider 85ms as low latency. Will this be getting substantially better in the future? Like about <15ms or so?

    Where is your 85ms latency figure coming from? I'm not noticing any audible latency playing synths here. That's with M1 MacBook Pro and an iPad Pro 2017. I even had success yesterday with my old iPad Air 2 and Moog Mariana (though I did have to adjust the buffer to avoid distortion). Response from playing my controller keyboard was as if it was a plugin hosted directly in my DAW.

  • edited March 5

    @satoshiszk

    Great app! I couldn't notice any input lag trying the demo with Ableton 12.

    Is there a dark mode planned? The bright UI is a bit disturbing in a dimmed environment with the iPad in front below a monitor.

    Would it be possible to switch tracks/racks from the iPad app when there are plugins on different tracks in the DAW?

    The only way to change it that Ive found is by opening the corresponding instance on a track which switches the iPad view to the other rack.

  • edited March 6

    Please allow me to add an explanation about latency.

    First, I would like to divide it into two types.

    1. The time it takes for the audio signal from the DAW to be sent to the iPad and then returned to the DAW.
    2. The time it takes for sound to be outputted from the Mac after touching the UI such as the keyboard on the iPad.

    Type 1 requires a round trip transfer, whereas type 2 is one-way. Therefore, theoretically, the latency for type 1 should be higher. However, the latency for type 1 is not much of an issue in most cases because most major DAWs have an automatic compensation function. Tracks using SideRack and those not using it are perfectly synced with sample-level accuracy. This is an advantage of SideRack over hardware products. The plugin latency reported by many DAWs refers to this type 1 latency. I guess the 85ms mentioned by @figgelz is referring to the latency of type 1.

  • edited March 6

    @figgelz said:
    Will this be getting substantially better in the future?

    Yes. We are continuously updating this plugin and optimizing its performance. (Although due to our plugin's nature, the latency will not be zero.)

    If not, could there be a mode which uses an external audio interface for the audio output?

    The roadmap includes "Monitoring AUv3 plugin sounds through an audio interface on iOS devices."
    https://forum.audiob.us/discussion/comment/1307142/#Comment_1307142

    Is this what you are mentioning?

  • @steve99 said:
    Just been playing with the demo and very impressed in the short bursts I've attempted, although @satoshiszk please can you extend the demo time? 5 mins is way too short to test things out properly.

    Sorry, this is our mistake. I intended to set it to 10 minutes, but it seems to have been mistakenly set to 5 minutes. It is planned to be fixed in the next update.

  • @kirmesteggno said:
    Is there a dark mode planned? The bright UI is a bit disturbing in a dimmed environment with the iPad in front below a monitor.

    OK. I added the "dark mode" feature to our roadmap. Thanks for your feedback!
    https://forum.audiob.us/discussion/comment/1307142/#Comment_1307142

  • edited March 6

    Would it be possible to switch tracks/racks from the iPad app when there are plugins on different tracks in the DAW?

    Please tap the rack name on the header. We'll consider how to improve the GUI design.

  • edited March 6

    @satoshiszk said:

    @figgelz said:
    Will this be getting substantially better in the future?

    Yes. We are continuously updating this plugin and optimizing its performance. (Although due to our plugin's nature, the latency will not be zero.)

    From my observation of the plugin... it shows on reaper that the PDC is in the range of 4096 samples....
    now although i dont fully understand the spl's measured from a Plugin delay compensation standpoint(its noticeable from a performance perspective....
    notes from synths do suffer a latency hit when the audio-effect plugin is in use ...
    i may need to tweak my internal settings to get something decent re latency to compensate for the plugin PDC *shrugs

    it would be appreciated if we could have an adjustment slider, which is coupled to the most significant part of the internal chain of the plugin...that would give us some control over the latency... as a means of balancing latency

    whether this request would begin to cause degradation of audio doing this realtime.. as one might expect throwing things out of whack... i dont know...
    but if we could balance the spl's before initiating the play button allowing for buffering to refresh... this balancing of latency would allow us to see whats possible & whats NOT possible re latency vs device cpu-load and accounting for our projects plugins

    perhaps the (spl's)expectation was set based upon multiple instances of siderack being initiated... thus a high spl count would be required *shrugs
    im just guessing here... and really talking from my rear end LOL
    in any case... i purchased the plugin a day or so ago... and will await a fix on the Big Sur license issue *smiles
    For all that which is good in the world... i do appreciate the plugin and the value it will bring
    thanks Team Novonotes!

  • edited March 6

    @satoshiszk said:

    @kirmesteggno said:
    Is there a dark mode planned? The bright UI is a bit disturbing in a dimmed environment with the iPad in front below a monitor.

    OK. I added the "dark mode" feature to our roadmap. Thanks for your feedback!
    https://forum.audiob.us/discussion/comment/1307142/#Comment_1307142

    Thanks a lot 🙌

    @satoshiszk said:

    Would it be possible to switch tracks/racks from the iPad app when there are plugins on different tracks in the DAW?

    Please tap the rack name on the header. We'll consider how to improve the GUI design.

    I've revisited the config and I think it was my fault too, I didn't press on the iPad link in the plugin popup on the second track in Ableton itself. I thought that I don't have to connect again once it was connected to the iPad on the other track, thats why I didn't get the list overview of the different tracks.

    A text label like "add plugin to Duo plugin list" or "add to Duo plugin overview" or "add to select rack screen" instead of just the iPad link could work well I think.

  • @satoshiszk - thanks for joining the forum, sharing your development plans and providing support for SideRack. After a couple of days testing I've bought the full version. I'm very impressed with what it can do so far and looking forward to future development...👍

  • edited March 6

    Can I use this to send multichannel such as 12 channel audio from iPad to Mac? I want to use both my TX6 on iPad and Ableton to multitrack record

    Does USB work if I also have the TX-6 audio interface connected to the iPad via USB?

  • @satoshiszk said:
    Please allow me to add an explanation about latency.

    First, I would like to divide it into two types.

    1. The time it takes for the audio signal from the DAW to be sent to the iPad and then returned to the DAW.
    2. The time it takes for sound to be outputted from the Mac after touching the UI such as the keyboard on the iPad.

    Type 1 requires a round trip transfer, whereas type 2 is one-way. Therefore, theoretically, the latency for type 1 should be higher. However, the latency for type 1 is not much of an issue in most cases because most major DAWs have an automatic compensation function. Tracks using SideRack and those not using it are perfectly synced with sample-level accuracy. This is an advantage of SideRack over hardware products. The plugin latency reported by many DAWs refers to this type 1 latency. I guess the 85ms mentioned by @figgelz is referring to the latency of type 1

    I think it's the Latency Type 2 here, because I loaded the Instrument VST of SideRack in Ableton, so no audio would be send to the iPad. Ableton has a nice feature, where it shows you the latency of a plugin, when you hover your mouse over the top bar of the pluginbox in the lower row, where you place your plugins.

    @triple7 said:

    From my observation of the plugin... it shows on reaper that the PDC is in the range of 4096 samples....
    now although i dont fully understand the spl's measured from a Plugin delay compensation standpoint(its noticeable from a performance perspective....
    notes from synths do suffer a latency hit when the audio-effect plugin is in use ...
    i may need to tweak my internal settings to get something decent re latency to compensate for the plugin PDC *shrugs

    This correlates with what Ableton shows me. I'm on 48kHz samplerate so the math is 4096smpls/48000Hz = 0,0853333s which are 85ms.

    Would be really nice, if there was a setting to set the buffersize to lower values.

    FYI: I'm running Ableton Live 12 on my MacBook M1 Pro with macOS Sonoma 14.2.1 together with an M1 iPad Pro 11". As an audio interface i'm using the Babyface Pro FS from RME with a buffersize set to 128.

  • @satoshiszk said:

    @figgelz said:
    Will this be getting substantially better in the future?

    Yes. We are continuously updating this plugin and optimizing its performance. (Although due to our plugin's nature, the latency will not be zero.)

    If not, could there be a mode which uses an external audio interface for the audio output?

    The roadmap includes "Monitoring AUv3 plugin sounds through an audio interface on iOS devices."
    https://forum.audiob.us/discussion/comment/1307142/#Comment_1307142

    Is this what you are mentioning?

    Yeah, with monitoring you could reduce the latency a lot, but only when we would have the possibility to reduce the buffersize in the Duo App on the iPad.

    The latency would then be like about

    • ~5ms from the iPad
    • ~5ms Inputlatency from Ableton
    • ~5ms Outputlatency from Ableton.

    This would add up to ~15ms, which is a tolerable value i guess.

    But the best way would be clearly with the audio coming over USB. Because of lesser cables, no noise in the audio path and no fiddeling around with the "External Instrument" in Ableton

  • @figgelz said:

    This correlates with what Ableton shows me. I'm on 48kHz samplerate so the math is 4096smpls/48000Hz = 0,0853333s which are 85ms.

    Would be really nice, if there was a setting to set the buffersize to lower values.

    FYI: I'm running Ableton Live 12 on my MacBook M1 Pro with macOS Sonoma 14.2.1 together with an M1 iPad Pro 11". As an audio interface i'm using the Babyface Pro FS from RME with a buffersize set to 128.

    thanks for the confirmation....

  • @triple7 said:

    it would be appreciated if we could have an adjustment slider, which is coupled to the most significant part of the internal chain of the plugin...that would give us some control over the latency... as a means of balancing latency

    OK, I've added that feature to our road map. Thanks for your feedback.
    https://forum.audiob.us/discussion/comment/1307142/#Comment_1307142

  • @wahnfrieden said:
    Can I use this to send multichannel such as 12 channel audio from iPad to Mac? I want to use both my TX6 on iPad and Ableton to multitrack record

    The maximum audio channel count per SideRack plugin instance is 2. Currently, there is no feature to interact with the audio interfaces on your iPad. The iPad simply receives audio from the Mac and then returns the processed audio.

    Does USB work if I also have the TX-6 audio interface connected to the iPad via USB?

    Our app will not affect any audio interface issues because there's no interaction.

  • edited March 7

    @figgelz said:

    @satoshiszk said:
    Please allow me to add an explanation about latency.

    First, I would like to divide it into two types.

    1. The time it takes for the audio signal from the DAW to be sent to the iPad and then returned to the DAW.
    2. The time it takes for sound to be outputted from the Mac after touching the UI such as the keyboard on the iPad.

    Type 1 requires a round trip transfer, whereas type 2 is one-way. Therefore, theoretically, the latency for type 1 should be higher. However, the latency for type 1 is not much of an issue in most cases because most major DAWs have an automatic compensation function. Tracks using SideRack and those not using it are perfectly synced with sample-level accuracy. This is an advantage of SideRack over hardware products. The plugin latency reported by many DAWs refers to this type 1 latency. I guess the 85ms mentioned by @figgelz is referring to the latency of type 1

    I think it's the Latency Type 2 here, because I loaded the Instrument VST of SideRack in Ableton, so no audio would be send to the iPad. Ableton has a nice feature, where it shows you the latency of a plugin, when you hover your mouse over the top bar of the pluginbox in the lower row, where you place your plugins.

    I'm not 100% sure because I don't know the internal implementation of Ableton Live, but the latency shown by Ableton when you're using an Instrument VST is likely Type 1. The reasons are:

    • Our plugin has an internal buffer of 4096 samples, and it communicates this figure to Ableton to compensate the potential latency.
    • Our Instrument VST plugin receives silent audio buffer from Ableton. (And writes the processed audio data to that buffer.)
    • Since there's no direct means for Ableton to communicate with the Duo app, it seems impossible to implement timing measurements starting from the Duo app. Thus Ableton cannot display Type 2 latency.

    Would be really nice, if there was a setting to set the buffersize to lower values.

    I've added the request to our roadmap. I realize that many here are deeply concerned with latency issues. Thanks for your feedback.

Sign In or Register to comment.