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.

Branches - Semi-modular synth by Willow & Oak AB

1246

Comments

  • @kennylovrin said:

    @espiegel123 said:
    @kennylovrin : I am finding the envelope to be not as responsive as I'd expect. The Decay parameter has less impact than I'd expect. I find it tricky to get the sort of 'plucky' envelopes so beloved in West Coast synthesis. Would also love to have the wavefolding be more aggressive.

    thanks for the feedback, i'll note it and have a look at it when the time comes.

    for now you can try to change the response of the LPG, which gives you a different response curve, it can in some cases give you a more snappy feel, could perhaps get you a little closer to where you want to go.

    I have played with the response curve and it felt like the Release was impacted much more than decay

  • @kennylovrin said:
    @skiphunt Haha, I think I may have confused the right and left LPG in the tip for tuning the sequencer which might explain the issue you had, I wrote that you should patch into the complex oscillator then raise the volume of the left LPG, but the left LPG is for the modulation oscillator, so it's a typo on my end. might be the reason you experience "it does nothing", or it could be something else.

    Anyway, here's a patch for you to try if you feel like it, it is essentially what I'm trying to demonstrate in the tip, just a bit more involved for the fun of it:

    I'll try to briefly walk through it for those interested:

    • The function generator is in cycle mode, it's rate is set by the rise/fall knobs, at the end of each rise it sends a trigger out of EOR, that trigger is patched to advance the sequencer one step.

    • The output of the sequencer is patched to an attenuverter, the attenuverter is set to a low positive number to scale down the output of the sequencer, essentially making the span of the sequencer sliders smaller so that they are easier to control for pitch. The output is then taken from the attenuverter into the quantizer, which will snap the pitch to scale, making it even easier to not sound out of pitch. then that quantized output is sent to pitch of both oscillators.

    • Back to the func gen, the EOR pulse is also patched to the envelope which will open the LPG on each pulse. Note that this is a trigger and not a gate, it works, but you have only Attack/Release as there is no gate to sustain the envelope.

    • The EOR of the func gen is also taken to the trigger divider, then every 3rd trigger is sent to trigger the randomizer to sample. The output of the randomizer is then also patched to the quantizer. This will sum the random voltage with the sequencer voltage at the input of the quantizer, so we get a bit of random variation to the sequenced melody.

    @kennylovrin "Haha" indeed. I wasted an hour an a half due to a typo?! Damn you to HELL and back!!!

    Just kidding. lol ;)

    Yes, it's working now that I'm adjusting the right LPG instead of the left. Sounds great! And thanks for the patch image. Will play with that later. Cool :)

  • edited November 2020

    For those interested, v1.0.2 has been approved now and should be live (or at least about to go live depending on where you are) now. I recommend everyone to download it, the responsiveness should be greatly improved (I measured about 1/3rd of the CPU load compared to before, when adjusting encoders).

  • Thanks for the screenshot patches and tips! This is turning out better and better and is making sense. I wonder what the name means, I guess they are into tree's. I like them oak and willow trees.

  • @kennylovrin said:
    For those interested, v1.0.2 has been approved now and should be live (or at least about to go live depending on where you are) now. I recommend everyone to download it, the responsiveness should be greatly improved (I measured about 1/3rd of the CPU load compared to before, when adjusting encoders).

    Very nice 'speed boost' on the UI. No more lags on my ancient iPad Air 2 :)

    I mostly use the AUv3 so the 'scaling/layout issues' that still affect the stand-alone when not using the 'default' Text Size (Display & Brightness -> Text Size) is no longer bothering me.

    Personally I'm not a huge fan of 'Dark Mode' in iOS/iPadOS but I would love to be able to choose the default color theme for Branches AUv3. It always seems to use the 'bright' color theme?

    Don't know if the other issue is 'user malfunction' but sometimes (ie. when the window is not maxed out and there is a need to pan/scroll the view) it's next to impossible to patch the cables. The line is 'drawn' but it doesn't snap to the destination!?

    Cheers, and thanks for the update!
    /Samuel

  • @kennylovrin said:
    For those interested, v1.0.2 has been approved now and should be live (or at least about to go live depending on where you are) now. I recommend everyone to download it, the responsiveness should be greatly improved (I measured about 1/3rd of the CPU load compared to before, when adjusting encoders).

    Much better response indeed! Thanks.

  • @Samu said:
    Very nice 'speed boost' on the UI. No more lags on my ancient iPad Air 2 :)

    I mostly use the AUv3 so the 'scaling/layout issues' that still affect the stand-alone when not using the 'default' Text Size (Display & Brightness -> Text Size) is no longer bothering me.

    Personally I'm not a huge fan of 'Dark Mode' in iOS/iPadOS but I would love to be able to choose the default color theme for Branches AUv3. It always seems to use the 'bright' color theme?

    Don't know if the other issue is 'user malfunction' but sometimes (ie. when the window is not maxed out and there is a need to pan/scroll the view) it's next to impossible to patch the cables. The line is 'drawn' but it doesn't snap to the destination!?

    Cheers, and thanks for the update!
    /Samuel

    I'm glad you appreciate it - the speed improvement should be fairly significant yes. :)

    Some notes on what you're describing:

    I think I will rework the UI as a matter of fact and allow it to scroll by design rather than try to obsessively squeeze it into the available screen estate. This would allow me both to potentially add more features that have already been requested and for example also support iPhone. That could potentially also mean that it would properly respect text size system settings. I have to think more about this, but I am actively thinking along these lines. Even adding a little UI for presets require screen estate that I don't quite have at the moment, etc.

    On top of that, the bug you are experiencing when you can't make a connection is a known to me. It seems to happen only when running in Aum, I think because it allows the user to resize the window. I don't mean that Aum is the issue, I just mean that there is something in the UI of Branches that doesn't resize properly with the resize of the window in Aum, so sometimes the hit area calculations are off. My plan is to fix this as part of a general UI adjustment, this is quite important. For now it seems to be possible to get it to work by resizing the window a bit, or even open and close it, you can try to get by that way for now - sorry about the inconvenience.

    Re dark/light mode.. I have specifically opted to use the system setting rather than allow the user to choose, so you should get the light theme if your device is set to light. It's one of those typical developer things - "this is the correct way to do it as it respects the system setting" - then everyone goes "I want dark mode always no matter my system setting". So I am quite likely to end up with a manual toggle in a future release. ;)

  • @kennylovrin said:

    Re dark/light mode.. I have specifically opted to use the system setting rather than allow the user to choose, so you should get the light theme if your device is set to light. It's one of those typical developer things - "this is the correct way to do it as it respects the system setting" - then everyone goes "I want dark mode always no matter my system setting". So I am quite likely to end up with a manual toggle in a future release. ;)

    The dark/light mode works fine in the stand-alone but the AUV3 is always 'bright' regardless of the system setting.
    A 'built-in' limiter could be handy to avoid iOS/iPadOS 'freaking out' (ie. all audio goes silent) due to extreme clipping.

    As an example it's possible to patch multiple Envelope Out's to the CV's (the 'cables' just get darker) and at some point it's 'click of death' and all audio goes silent and the hosts needs to be restarted and in worst case scenario reboot of the iPad is needed.

    No biggie, in same cases it can be handy to boost low signal levels, just need to be careful :)

    I'm in no way any expert in this kind of synthesis as I'm more used to trackers and old-school chip stuff being a SID junkie...

    Cheers!

  • I have just spent the last three weeks submerged in Material Design theming and palettes, dark and light mode. Unbelievable how much of a knowledge toilet that whole area is. Vast amounts of articles, tutorials, guides all amount to telling people how to do unmaintainable unprofessional hacks that just get you by for now. I've never experienced such a rabbit mine of misinformation and the blind leading the blind. An astounding mess.

    Anyway, that's me on dark mode/light mode for now. How's your day been.

  • Hey, @SoundForMore, any chance you've got something cooking for Branches?

  • I have a thing for West Coast synthesis but I’ll probably won’t be able to get my hands on a hardware one anytime soon. I own the (desktop) Arturia Easel, Ripplemaker, and have explored a good amount of combinations of waveshaping and LPGs in Drambo and mirack with various results—my problem is that these options end up with patches that are too large to enjoy in the same way as an instrument.

    Branches’ clean interface and Easel-inspired sequencer and modulator are right up my alley, and the sound is really wonderful; a different palette from Ripplemaker which should make for good combinations. The complex osc is fantastic as well and the 2 midi inputs allow for wonderful two-voice patching. Can’t compare with the sound of hardware (sine I don’t own any) but so far the wavefolding and envelope snappiness are hitting the spot for me!

    So far, I’ve enjoyed the app a lot and have a few observations/suggestions/kind requests which would make Branches a top iOS variation on the Easel and 0-coast:

    1. More modulation inputs: at least the Function Generator’s rise/fall parameters should have inputs (can’t do true Krell patches without them)
    2. The Modulator OSC could switch between LFO and audio rate (I believe the Easel has this)
    3. Also from the Easel, gate outs from the sequencer (allows for great polyrhythms)
    4. The attenuator module could double as a mult/mixer
    5. Outputs for the Modulator and Complex OSC for rerouting and audio-rate modulation
    6. Preset voltage pads from the Easel
      +1 for effects to be integrated in the AUv3: I prefer having most of my parameters in one screen if possible.

    A couple of things which might be bugs:
    1. I can see MIDI CC parameters exposed in AUM but they don’t seem to be working (on-screen MIDI CC mapping would be great).
    2. The negative side of the attenuverter does not seem to be working
    3. Instant crash: patch the FG’s EOC or EOR to FG’s own trigger. Patch FG’s out to LPG input. This crashes the app. (This way of cycling the FG wouldn’t work anyway because there is no manual trigger for the FG)

    These are just minor suggestions for future developments; it’s a great app and I’d recommend it to anyone who’s into the quirky west coast stuff!

  • This is becoming more fun than normal. There are no saves or presets right? The concept perhaps being the analog old school thing (where what you see is what you get no saves)?

    dvi: a secret well organized analog FBI synthesis agent. Your totally blowing your cover, we know. Cheers

  • @dvi said:
    I have a thing for West Coast synthesis but I’ll probably won’t be able to get my hands on a hardware one anytime soon. I own the (desktop) Arturia Easel, Ripplemaker, and have explored a good amount of combinations of waveshaping and LPGs in Drambo and mirack with various results—my problem is that these options end up with patches that are too large to enjoy in the same way as an instrument.

    Branches’ clean interface and Easel-inspired sequencer and modulator are right up my alley, and the sound is really wonderful; a different palette from Ripplemaker which should make for good combinations. The complex osc is fantastic as well and the 2 midi inputs allow for wonderful two-voice patching. Can’t compare with the sound of hardware (sine I don’t own any) but so far the wavefolding and envelope snappiness are hitting the spot for me!

    So far, I’ve enjoyed the app a lot and have a few observations/suggestions/kind requests which would make Branches a top iOS variation on the Easel and 0-coast:

    1. More modulation inputs: at least the Function Generator’s rise/fall parameters should have inputs (can’t do true Krell patches without them)
    2. The Modulator OSC could switch between LFO and audio rate (I believe the Easel has this)
    3. Also from the Easel, gate outs from the sequencer (allows for great polyrhythms)
    4. The attenuator module could double as a mult/mixer
    5. Outputs for the Modulator and Complex OSC for rerouting and audio-rate modulation
    6. Preset voltage pads from the Easel
      +1 for effects to be integrated in the AUv3: I prefer having most of my parameters in one screen if possible.

    A couple of things which might be bugs:
    1. I can see MIDI CC parameters exposed in AUM but they don’t seem to be working (on-screen MIDI CC mapping would be great).
    2. The negative side of the attenuverter does not seem to be working
    3. Instant crash: patch the FG’s EOC or EOR to FG’s own trigger. Patch FG’s out to LPG input. This crashes the app. (This way of cycling the FG wouldn’t work anyway because there is no manual trigger for the FG)

    These are just minor suggestions for future developments; it’s a great app and I’d recommend it to anyone who’s into the quirky west coast stuff!

    Thanks, these are really nice words, I appreciate it and I'm happy you seem to get what I've been trying to achieve. :)

    Most of the things you mention that would be nice features are things that do exist on my todo-list at different priorities, so it's always nice to get this kind of feedback to help prioritize what to do and so on.

    The instant crash is interesting, I will look into that!

  • @oceansinspace said:
    This is becoming more fun than normal. There are no saves or presets right? The concept perhaps being the analog old school thing (where what you see is what you get no saves)?

    dvi: a secret well organized analog FBI synthesis agent. Your totally blowing your cover, we know. Cheers

    There are no save/preset right now no, but a lot of people are asking for it so my preliminary plan is to add support for it quite soon, can't say exactly when though.

  • edited November 2020

    .

  • @dvi said:
    So far, I’ve enjoyed the app a lot and have a few observations/suggestions/kind requests which would make Branches a top iOS variation on the Easel and 0-coast:

    1. More modulation inputs: at least the Function Generator’s rise/fall parameters should have inputs (can’t do true Krell patches without them)

    Yes! VC of rise/fall is an essential part for autogenerated patterns, algo great controlling with the sequencer

    1. The Modulator OSC could switch between LFO and audio rate (I believe the Easel has this)

    Yes, the easel have a switch for that

    1. Also from the Easel, gate outs from the sequencer (allows for great polyrhythms)

    The first time I saw the branches sequencer I thought the buttons in the sequencer section are the active trigger switches... Had a time looking for the trigger output from the sequencer.. That also open up the posibilities a lot.

    1. The attenuator module could double as a mult/mixer
    2. Outputs for the Modulator and Complex OSC for rerouting and audio-rate modulation
    3. Preset voltage pads from the Easel
      +1 for effects to be integrated in the AUv3: I prefer having most of my parameters in one screen if possible.
      These are just minor suggestions for future developments; it’s a great app and I’d recommend it to anyone who’s into the quirky west coast stuff!

    Really good sugestions @dvi !
    I Use and have some west coast systems since mny years ago, Serge and Buchla 200 Modulars, Music Easel and also have a 0-coast here. Tried the Arturia Easel in the computer and have ripplemaker for iOS.

    I`d like to add some other sugestions that would make branches a first class West coast synth. I like the sound of Branches but would be great to have some inestabilities built in, I use the Random module thru the attenuinverter connected to the pitch to bring some organic drift but it takes two important modules just for that. Would be great having a "drift" or vintage "toggle" for the oscillators.

    Also I miss attenuinverters in each VC input! two for all the functions is no enought and also requieres patching. The joy of the west coast systems is because the great possibilities with a reduced set of modules, even with just one! ( ie. the Serge Slope generator is genious multimode module) BUT all of them have Voltage control inputs and attenuinverters for each function! the same as the Easel have a VC level for each input. Please consider to add this so Branches is not crippled and can show the full potential

  • Does this have presets or preset saving?

  • Thanks, I dig the purist 'no preset' concept but in reality I want to save it or at least record it. Cheers to your tree of life blooming.

  • @oceansinspace I wish I was with the FBI, then I would be able to afford some hardware! I’m just an unemployed academic who discovered mirack and drambo in the midst of a pandemic and dove right in.

    For anyone interested, it has state saving in AUM so you can save presets there. I use it to set an Init patch and clear the board quickly.

    @kennylovrin awesome! Looking forward to seeing some of these details come through! If there’s a priority, MIDI CC Parameter control would be high on the list; all the other features in @Synthi’s list and mine can be supplied from mirack/drambo that way.

    By the way, I’ve spent some more time with the reverb in the standalone and I really like its sound, so I’d insist in including it as part of the AUv3. The FM also sounds particularly good to my ears.

    I’m thrilled for branches, thanks for your work!

  • @kennylovrin : I am finding it difficult to disconnect things. In the standalone, I often am not able to disconnect patch chords. It would be very helpful to have a one touch way of resetting to the default patch.

  • @kennylovrin : is the release time of the envelope intentionally tied to decay time? One of the frustrations I have with the envelopes is that it seems that the maximum release time is a function of the decay time. So super short decay severely limits the release time in a way I’ve not encountered with other envelope generators.

  • @espiegel123 said:
    @kennylovrin : I am finding it difficult to disconnect things. In the standalone, I often am not able to disconnect patch chords. It would be very helpful to have a one touch way of resetting to the default patch.

    Same. plus no presets blows.

  • Dvi : nice cover. I know your lab is full of top secret gear/jk. But hey branches has some ufo disclosure via audio format for sure. They are usually in disguise by tonal note brainwave 'beamrays'. Cheers to this app as its become amazing (as I learn) and I will keep at it!

  • edited November 2020

    Is there any way to initialise?

    Plus I just updated to iPadOS 14.2 and now it doesn't fit on the screen.

  • wimwim
    edited November 2020

    Yeh, I definitely would like an empty init patch.

  • So to show im not a a robot, here is my best branch so far. I see all the stop sign in the picture and zyxywq io ok. JK all is well https://youtube.com/watch?v=aW8WNBjcqL8

  • edited November 2020

    Hey, there's been a lot of posts so I will just generally address some of the things straight from brain.. :)

    It's really interesting that the suggestion of instability comes up, it's quite specific, and I actually had that in the very beginning in a "prototype version" of the app. I do however have some plans to try a different type of oscillator logic that I potentially think could have a subtle improvement in "naturalness", that could potentially include a tiny bit of instability, so we'll see what happens there.. :)

    I will check UI issues on iPadOS 14.2 as soon as I get a chance, there might be something that breaks it. I have however also started reworking major parts of the UI for an upcoming release, I plan to move away from the "it has to fit on screen at all times", as it both is very tricky to add features and also it's much easier to handle different screen sizes if it allows scrolling. The drawback of course being, scrolling. I'll try to strike somewhat of a balance and we'll see how it's perceived. Generally speaking UI is very important as it just sets the tone of the whole experience, so it's high prio for me, but sometimes it takes a few tries.. :)

    My current & preliminary plan is that the next update will have this new UI logic and some initial type of presets. Depending on how it goes it might be two releases, we'll see, but at least that is my aim. And of course, if there are any more critical things they have to take priority. The UI improvements are quite important, both for different iPad sizes, but also for the upcoming ARM Macs that will be able to natively run iPad apps, and then of course also for potentially supporting iPhone as well as a universal app.. We'll see, we'll see.. :)

    Much of everything else you all mention is very much on the todo list, but so far not prioritized.

    Anyway, thanks again for your support and interest.

  • By the way, I have a question. I might regret asking this, but I'll do it anyway and then I'll have to take a decision later:

    Those of you that have used Branches so far, and other modular-style apps would you prefer a Synthi-style patch matrix instead of dragging "cables" around? A patch matrix (in this case) is unlikely to fit on screen at all times, so imagine tapping a button to open it in some sense. Aum is using this type of patch layout as well for example.

    You would think I prefer cables for obvious reasons, but actually I don't like it, but I don't quite like a patch bay either as it easily gets huge (I've tried both in fact). So why not ask the users and see what they say.. :)

  • edited November 2020

    I hope you get some interesting feedback on this. To me, wires are both a nice instant visualization, but also maybe a skeuomorphic romantic affectation. They can get in the way, cause visual clutter, and be difficult to reroute. I don't want to be a "every problem can be solved with Drambo!" drum beater, but I do like the approach Drambo has taken to "quantum" connections.

    I'm sure I fall into a small niche, but I would love a text editable configuration language. It solves the 2D matrix linear growth as well as preset management. gasp patches in a git repo! swoon

  • @Liquidmantis said:
    I hope you get some interesting feedback on this. To me, wires are both a nice instant visualization, but also maybe a skeuomorphic romantic affectation. They can get in the way, cause visual clutter, and be difficult to reroute. I don't want to be a "every problem can be solved with Drambo!" drum beater, but I do like the approach Drambo has taken to "quantum" connections.

    I haven't used Drambo, so not sure what you mean here, but I will look into it. I was thinking of a "tap the jack, show a popup with potential destinations" UI as well, is that what you mean? Problem with my thought there is that you can't really see a patch.

    I'm sure I fall into a small niche, but I would love a text editable configuration language. It solves the 2D matrix linear growth as well as preset management. gasp patches in a git repo! swoon

    Haha, well yes, that might be a bit niche, but ironically I was thinking about presets and preset sharing yesterday and was thinking about it being some kind of text file. Internally all modules have user readable names so it's theoretically possible for me to leave them editable, but I'll have to see and think about sharing and other integrations etc as well.

Sign In or Register to comment.