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.

Released: ToneBoosters Flowtones - virtual analog synthesizer

191012141519

Comments

  • edited August 2021

    how do you specify which modulation will be applied via aftertouch or mod-wheel?

  • @BCKeys said:
    Can this could emulate a prophet 5 ?

    It’s still missing oscillator sync hard sync so that type of sounds is a no can do at the moment.
    Don’t know of hard-sync is something that @DJB plans to add in the future?

    Also don’t know the specifics of each filter model but the filter plays a huge part of the sound in the prophet 5.

    I’m more worried about the execssive ‘anti-aliasing’ that makes it impossible to do on/off modulation of parameters.

    When using the squarewave of the lfo to modulate stuff it’s more like fade-in/fade-out at slower speeds and at higher speeds squarewave acts more like a triangle-wave. Also when using an LFO to modulate pitch the notes ‘glide’ to each other like if portamento was being used but it’s just the LFO depth being interpolated to the new note.

    I do love the sound of the TB FlowTones but these small things make me go back to Dramo when I want to experiment with sounds & synthesis especially at the lower level.

    Cheers!

  • DJBDJB
    edited August 2021

    @Samu said:

    When using the squarewave of the lfo to modulate stuff it’s more like fade-in/fade-out at slower speeds and at higher speeds squarewave acts more like a triangle-wave. Also when using an LFO to modulate pitch the notes ‘glide’ to each other like if portamento was being used but it’s just the LFO depth being interpolated to the new note.

    this has been fixed (for square and step waves).

  • @DJB said:

    @Samu said:

    When using the squarewave of the lfo to modulate stuff it’s more like fade-in/fade-out at slower speeds and at higher speeds squarewave acts more like a triangle-wave. Also when using an LFO to modulate pitch the notes ‘glide’ to each other like if portamento was being used but it’s just the LFO depth being interpolated to the new note.

    this has been fixed (for square and step waves).

    I tried it last night 1.0.7 and will give it another spin with the newly released 1.0.8…
    The best way I can describe it is like a quick glide which is noticeable when the depth is set to 12 semitones for ‘octave jumps’ and speed at 1hz. The pitch does not instantly ‘switch’ between two values it ‘glides’.

    On the plus side the envelopes can go crazy fast and if for example the volume was modulated at high speeds it would cause some serious aliasingdistortion which in some causes could be used to create really harsh sounds :sunglasses:

    Cheers!

  • DJBDJB
    edited August 2021

    @Samu said:

    @DJB said:

    @Samu said:

    When using the squarewave of the lfo to modulate stuff it’s more like fade-in/fade-out at slower speeds and at higher speeds squarewave acts more like a triangle-wave. Also when using an LFO to modulate pitch the notes ‘glide’ to each other like if portamento was being used but it’s just the LFO depth being interpolated to the new note.

    this has been fixed (for square and step waves).

    I tried it last night 1.0.7 and will give it another spin with the newly released 1.0.8…
    The best way I can describe it is like a quick glide which is noticeable when the depth is set to 12 semitones for ‘octave jumps’ and speed at 1hz. The pitch does not instantly ‘switch’ between two values it ‘glides’.

    On the plus side the envelopes can go crazy fast and if for example the volume was modulated at high speeds it would cause some serious aliasingdistortion which in some causes could be used to create really harsh sounds :sunglasses:

    Cheers!

    The square wave LFO (and the pulse and step waves) now switch waaaaaay faster than before even if the LFO speed is extremely slow. You may still hear a fraction of a millisecond of sliding frequencies to avoid aliasing but should be far better than before.

    Given that the LFOs are nicely band limited as well, we may be able to make it a bit faster if desirable.

  • @DJB said:

    @Shabudua said:
    @DJB i just updated to 1.0.7, and now any time i try to save a patch, it is instantly converted to sound like The Flowing Tones. So all the patches ive saved since the update are , sound-wise, copies of The Flowing Tones. Again, am I doing something wrong?

    I'm not able to reproduce that. Could you give a step-by-step description of how to trigger that? Please include all taps and button interactions on the way, thanks!

    [edit] ah found it. The default settings are accidentally loaded if you've saved a patch. Please go into the hamburger menu, and hit 'clear default settings' as a temporary workaround. We'll fix this ASAP

    And... the fix is now available in the App Store :-)

  • @DJB said:

    The square wave LFO (and the pulse and step waves) now switch waaaaaay faster than before even if the LFO speed is extremely slow. You may still hear a fraction of a millisecond of sliding frequencies to avoid aliasing but should be far better than before.

    Given that the LFOs are nicely band limited as well, we may be able to make it a bit faster if desirable.

    Gotcha, here's an example where the 'slide' is clearly audible...
    I made a somewhat similar patch in both FlowTones and Drambo to demonstrate the effect the 'slide' has.

    First Flowtones, make note of the transition between the pitches.
    https://www.dropbox.com/s/r52gd9m0huesoea/Flow.MP4?dl=0

    Next Drambo
    https://www.dropbox.com/s/slmim0llch98yjj/Drambo.MP4?dl=0

    I think you'll clearly hear difference :sunglasses:

    Don't get me wrong FlowTones is a very nice synth and the effects are top-notch!
    Knowing the arsenal of tools TB has the modulator from DualVCF could be a nice addition to flow-tones (and yes, I would use it to modulate pitch among other things).

    Cheers!
    /Samuel

  • Thanks @Samu for the demo. The bandwidth (and hence transition speed) of the LFO is fully parameterised so it's just one number to increase to make it as fast as we want it to be (under the constraints of not producing aliasing obviously).

  • @DJB said:
    Thanks @Samu for the demo. The bandwidth (and hence transition speed) of the LFO is fully parameterised so it's just one number to increase to make it as fast as we want it to be (under the constraints of not producing aliasing obviously).

    I guess it depends on what is being modulated?

    Modulating amplitude will create 'edges' and that can sometimes be used when it comes to sound-design.
    (I mean some modular users trigger a sample-n-hold module with a square oscillator for 'analog style' decimation, ie. the frequency of the triggering square oscillator sets the 'sample rate' at which the input signal is 'sampled' and holds the sampled input value until next trigger).

    Since you mention that the LFO is band limited those 'settings' could be used to simulate a sample-n-hold circuit for stepped output as well no? (ie. freely select how many 'levels/steps' the LFO outputs and how often the value is read and applied to the destination parameter similar to the filter steps in the filter?).

    Over all I do like FlowTones and it will be interesting to see how it evolves over time :sunglasses:
    Cheers!
    /Samuel

  • Just bumping this in case it got lost in sea of requests as I think it could be easy to implement and would definitely give a lot more flexibility for modulating the oscs. If it’s not possible for whatever reason, alles klar!

    @ronnieb said:
    @DJB Is there any reason the volume of each osc is limited to -40db? When using a lot of drive on the filters and bitcrushing/distortion I’ve already found it to be a quite limiting. It also seems like there is no way to mute one vco but still use it to modulate the other. Would be useful to be able to fully mute with the volume on each osc

  • @ronnieb said:
    Just bumping this in case it got lost in sea of requests as I think it could be easy to implement and would definitely give a lot more flexibility for modulating the oscs. If it’s not possible for whatever reason, alles klar!

    @ronnieb said:
    @DJB Is there any reason the volume of each osc is limited to -40db? When using a lot of drive on the filters and bitcrushing/distortion I’ve already found it to be a quite limiting. It also seems like there is no way to mute one vco but still use it to modulate the other. Would be useful to be able to fully mute with the volume on each osc

    >

    +1

  • @ronnieb said:
    Just bumping this in case it got lost in sea of requests as I think it could be easy to implement and would definitely give a lot more flexibility for modulating the oscs. If it’s not possible for whatever reason, alles klar!

    @ronnieb said:
    @DJB Is there any reason the volume of each osc is limited to -40db? When using a lot of drive on the filters and bitcrushing/distortion I’ve already found it to be a quite limiting. It also seems like there is no way to mute one vco but still use it to modulate the other. Would be useful to be able to fully mute with the volume on each osc

    >

    Got it; would a mute button for each VCO work? Extending a range of a slider is tricky because hosts often use normalised parameter values with an assumed fixed mapping from normalised parameter to actual dB values (for example for automation); hence extending a range of a parameter when something is out in the wild can cause all kind of issues...

  • I’m going to have to pick this up soon!! What I’ve heard is really good! Hopefully in a couple weeks!

  • edited August 2021
    The user and all related content has been deleted.
  • @DJB said:

    @ronnieb said:
    Just bumping this in case it got lost in sea of requests as I think it could be easy to implement and would definitely give a lot more flexibility for modulating the oscs. If it’s not possible for whatever reason, alles klar!

    @ronnieb said:
    @DJB Is there any reason the volume of each osc is limited to -40db? When using a lot of drive on the filters and bitcrushing/distortion I’ve already found it to be a quite limiting. It also seems like there is no way to mute one vco but still use it to modulate the other. Would be useful to be able to fully mute with the volume on each osc

    >

    Got it; would a mute button for each VCO work? Extending a range of a slider is tricky because hosts often use normalised parameter values with an assumed fixed mapping from normalised parameter to actual dB values (for example for automation); hence extending a range of a parameter when something is out in the wild can cause all kind of issues...

    A mute would work for the mod side fore sure. You could even just have the mod sliders bypass the ‘on’ switch of the oscs, if that’s easier?

  • edited August 2021

    @DJB said:

    @ronnieb said:
    Just bumping this in case it got lost in sea of requests as I think it could be easy to implement and would definitely give a lot more flexibility for modulating the oscs. If it’s not possible for whatever reason, alles klar!

    @ronnieb said:
    @DJB Is there any reason the volume of each osc is limited to -40db? When using a lot of drive on the filters and bitcrushing/distortion I’ve already found it to be a quite limiting. It also seems like there is no way to mute one vco but still use it to modulate the other. Would be useful to be able to fully mute with the volume on each osc

    >

    Got it; would a mute button for each VCO work? Extending a range of a slider is tricky because hosts often use normalised parameter values with an assumed fixed mapping from normalised parameter to actual dB values (for example for automation); hence extending a range of a parameter when something is out in the wild can cause all kind of issues...

    Mute button would work, but would it make sense to have a button that extends the range of the osc level to -inf instead of muting it?

  • @DJB Regarding pitch modulation in general...
    ...would it be possible to extend the range from +/-12 to maybe +/-24 or even 36?

    As for the LFO waveforms in general they could be made 'musical' if the stepped intervals corresponded to 'scaled notes?'
    Think of this as running the LFO waveform thru a 'scale quantizer' before it reaches the destination.

    So for example if the pitch modulation depth is set to 12 semitones (uni-polar) the LFO steps could correspond to semitones in various chords? (So as an example a '4-step' ramp up/down/triangle the steps could correspond to 0,4,7,12, or 0,3,7,12 semitones which would be added/subtracted to/from the oscillators pitch value?).

    Other 'things' that could be nice to have are additional filter models with fully resonant alternatives?

    And well, if oscillator hard-sync and ring-modulation is on the to-do list that would be sweet :sunglasses:
    Cheers!

  • @Samu said:
    Other 'things' that could be nice to have are additional filter models with fully resonant alternatives?

    And well, if oscillator hard-sync and ring-modulation is on the to-do list that would be sweet :sunglasses:

    +1

  • @DJB Another 'thing' I've been thinking about is a play head for the Sequencer in FlowTones?

    I know there's the small dot the travels on the top left but it makes no sense since it doesn't show on the note-grid..
    ...so a 'vertical line' that displays the actual sequence location could be handy especially when zoomed in?

    And well, if there's even a remote possibility to increase the font-size of the app it would be most welcome!
    I have it installed on my iPhone 8 as well but it's barely usable, can't see sh*t, it's too tiny!

    Don't know if the UI if FlowTones is vector based but if so, being able to scale the UI elements could be handy.
    (The TB desktop apps have a UI scale function which seems to be missing in all the TB iOS/iPadOS apps).

    Cheers!

  • Would it be possible to implement standard dialogue box scrolling behaviour (i.e. two-fingers on trackpad) in the app? It’s really fiddly as it is currently, if you are using a trackpad.

  • Does the gui on the iOS version not scale?

    A shame if not, that puts me off for the time being, I like how it scales in the Vst3 demo.
    I downloaded demo and initially I was not warming to it, as most of the presets aren't to my taste and that's usually your first impression of a new synth.
    But as I've come back to it, it's winning me over. It's so easy to program and quickly get to interesting sounds it's on my list.

    But a scaleable gui is ideal. :)

  • edited August 2021

    @Carnbot said:
    Does the gui on the iOS version not scale?

    It does 'scale' but not as well as the desktop version with also makes the controllers bigger...
    ...I would love to see the knobs/controllers get 'bigger' on the iOS/iPadOS version when zooming the UIs is it is now they are more or less 'spread across' the screen instead of made bigger and an option to simply 'disable/hide' on onscreen keyboard when the plug-in is show in 'full-screen'.

    In the standard 'letterbox mode' the controllers are very small and text is barely readable.

    (iPad Air 2)

    There's a 'sweet spot' on the Zoom (at 175%) on the desktop when I run the plug-in on my 4K monitor.

    This kind 'of zoom' with disabled keyboard on the iPad would be ideal considering my degrading eye-sight.

    Don't know if @DJB has any plans to improve visibility of the iOS/iPadOS app-portfolio with focus in the size of the UI elements and readability?

    Anyways, it's an awesome synth and it's starting to grow on me...

    Cheers!

  • With the recent improvements it is now possible to make dozens of great sounding and very usable patches in very short order. Huge productivity booster!

  • @Samu thanks for the info, yeah the desktop scaling of the knobs etc is something I hope they can replicate on the iOs version, it makes sound design much more inviting on a touch screen.

  • DJBDJB
    edited August 2021

    Just FYI - the UI rescaling on iPad and desktop is identical with the exception that font sizes on iPad are slightly larger; iPhone is different because it uses more tabs to work with the smaller screen. The difference between iPad and desktop is that the rescaling drop down menu and the little dragger in the bottom right corner is not available on iOS because rescaling is handled by the host when running as AUv3 (like you can freely rescale it in AUM like you can on the desktop) or always running in full screen mode as standalone.

    In GarageBand the letterbox mode isn't ideal (need to think about how to solve that given the tiny tiny amount of vertical space!) but it provides support for larger sizes as well; simply click on the expand button in GarageBand to get a taller UI with much larger knobs and text.

  • @DJB said:
    Just FYI - the UI rescaling on iPad and desktop is identical with the exception that font sizes on iPad are slightly larger; iPhone is different because it uses more tabs to work with the smaller screen. The difference between iPad and desktop is that the rescaling drop down menu and the little dragger in the bottom right corner is not available on iOS because rescaling is handled by the host when running as AUv3 (like you can freely rescale it in AUM like you can on the desktop) or always running in full screen mode as standalone.

    In GarageBand the letterbox mode isn't ideal (need to think about how to solve that given the tiny tiny amount of vertical space!) but it provides support for larger sizes as well; simply click on the expand button in GarageBand to get a taller UI with much larger knobs and text.

    Gotcha, even when using AUM I can’t fully replicate the desktop behaviour, that’s why I thought it would he a good idea to simply disable the on-screen keyboard when using ’full-screen’ or ’enlarged’ view which should in theory give more space to make the knobs and fonts bigger?

    In TB DualVCF there’s this nice ’arrow’ that can replace the other filter view with the ’modulator’.
    In the case of Flowtones a similar arrow could be used to switch between keyboard and knobs which could be especially handy on say and iPhone (ie. bigger keys to play on and biggner knobs to tweak the synt, a win-win no?).

    Guess I’ll just have to bring out the magnifying glass :sunglasses:
    Cheers!

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

    Im so sorry it took me so long to get back to you, I’m in vacation since a week so I don’t really watch at internet at all, thank you for this very good explanation, Samu 🙏
    Flowtones looks very interesting, still !
    Cheers

    No worries. Flowtones is a good synth and the developer has a good track-record of fixing issues so I feel pretty safe with it...
    ...even though I do get some 'brain-bugs' as to why a square LFO waveform has to act like a 'rounded square' to avoid aliasing.

    I mean it's 'stepped modulation' should be just that 'stepped' and not 'glide from value to another', but that's just me...

    One 'thing' about it that took me by a bit of a surprise was how heavy on the CPU it is, but then again I'm on an Air 2 and have stopped expecting miracles :sunglasses:

  • I've made 30 presets for this synth, but at the moment the sharing workflow isn't user-friendly (you have to import them one-by-one). Once @DJB is able to implement import/export of user banks I will share these with the community.

    The video should at least give some idea of what the synth is capable of in terms of lo-fi and ambient sounds and textures.

  • @richardyot said:
    I've made 30 presets for this synth, but at the moment the sharing workflow isn't user-friendly (you have to import them one-by-one). Once @DJB is able to implement import/export of user banks I will share these with the community.

    The video should at least give some idea of what the synth is capable of in terms of lo-fi and ambient sounds and textures.

    Very nice, Richard. I plan to upload some patches here myself soon. This is an extraordinary synth and I think there could be a lot more coming for it.

Sign In or Register to comment.