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.

Arpeggiator plugin that does not chop up monophonic playing into a staccato ?

2

Comments

  • Many thanks to the many replies in this thread! I love it to see how ideas start growing from a seed question. Great community here.
    @McD: Thanks a lot for taking action and modding the Mozaic script. I am going to mod that arpeggiator in the same way. And looking at the code I can see ways to implement the standard arp functions up - down - up down - up 2 down 2 etc...
    @wim: Thanks for mentioning Polytemus AU. Not exactly the solution, but I am thinking about a Mozaic script that does split notes to different channels according to how many are played together. So it could be plugged in front of any arpeggiator and allows this sort of playing with SPA and other apps.

  • @catherder said:
    Many thanks to the many replies in this thread! I love it to see how ideas start growing from a seed question. Great community here.
    @McD: Thanks a lot for taking action and modding the Mozaic script. I am going to mod that arpeggiator in the same way. And looking at the code I can see ways to implement the standard arp functions up - down - up down - up 2 down 2 etc...
    @wim: Thanks for mentioning Polytemus AU. Not exactly the solution, but I am thinking about a Mozaic script that does split notes to different channels according to how many are played together. So it could be plugged in front of any arpeggiator and allows this sort of playing with SPA and other apps.

    If you mod that please post it to patchstorage and share a link here if you would be so good!

  • @Gavinski said:

    @catherder said:
    Many thanks to the many replies in this thread! I love it to see how ideas start growing from a seed question. Great community here.
    @McD: Thanks a lot for taking action and modding the Mozaic script. I am going to mod that arpeggiator in the same way. And looking at the code I can see ways to implement the standard arp functions up - down - up down - up 2 down 2 etc...
    @wim: Thanks for mentioning Polytemus AU. Not exactly the solution, but I am thinking about a Mozaic script that does split notes to different channels according to how many are played together. So it could be plugged in front of any arpeggiator and allows this sort of playing with SPA and other apps.

    If you mod that please post it to patchstorage and share a link here if you would be so good!

    That's my plan.

  • ….> @Gavinski said:
    …,,

    2 quick questions

    • what is the point of the ‘upload”? I just saved and renamed it without uploading and it seems to work fine.

    >

    Editing you do does not become active till you upload (think of it as meaning “re-compile”) or save AND reload.

    If you edit a script and save (without uploading or loading the saved script), the new text is saved but changes in the script won’t be active until you either upload or load the saved script.

  • edited August 2023

    I checked my hardware, and with the exception of the Roland SH-01A all the other gear (Arturia KeyStep, Arturia MicroFreak, Volca FM) has arpeggiators that make no exception for monophonic playing.
    I am interested if there are any other arp implementations similar to what Roland uses in the SH-01A.

  • @_Ki: I hope you’re seeing this discussion and crude hack of your script. I know you like to program as a hobby in addition to your professional duties writing code. If you would like to capture feature requests for a 2.0 version please join in here otherwise there will be some forked instances of your wonderful script. As always the code is well documented… I finally tried that help knob and discovered the Easter Egg you added to the shift button: a Very nice doubler toggle.

  • @espiegel123 said:
    ….> @Gavinski said:
    …,,

    2 quick questions

    • what is the point of the ‘upload”? I just saved and renamed it without uploading and it seems to work fine.

    >

    Editing you do does not become active till you upload (think of it as meaning “re-compile”) or save AND reload.

    If you edit a script and save (without uploading or loading the saved script), the new text is saved but changes in the script won’t be active until you either upload or load the saved script.

    Thnx!

  • _ki_ki
    edited August 2023

    @Mcd As soon as i saw the discussion, i had the idea to in coorporate that ARP playstyle into In-Order-ARP; very cool that you also noticed that minimal changes are needed.

    Internally i worked again on that script about two years ago, it was was published 2019. I wanted to add the swing features i implemented in my AddSwing script. But never finished debugging that arp-with-swing update.

    This morging i had the idea to re-purpose the ARP on/off pad to include switching to the new ARP-Poly-Only mode (first thought about naming it SH-01 A mode, but its probably better to use a more descriptive name). BUT after playing around with the 1.0 for a while, i saw that the ON/OFF pad can be used as pause-arp and its fun toggling it while playing.
    So, no third state for that pad - and no ‚hey here‘s the new version in on day‘ ;-(

    I think i will pickup the UI changes i made to the internal v1.1, where the HELP page displays other knobs than the main page, allowing six instead of 3 settings knobs. Stuff that make sense to be changed during live play on the main page and basic configuration knobs on the HELP/CONFIG page.

  • @_ki said:
    @Mcd As soon as i saw the discussion, i had the idea to in coorporate that ARP playstyle into In-Order-ARP; very cool that you also noticed that minimal changes are needed.

    Internally i worked again on that script about two years ago - i wanted to add the swing features i implemented in my AddSwing script. But never finished debugging that arp-with-swing update.
    This morging i had the idea to re-purpose the ARP on/off pad to include switching to the new ARP-Poly-Only mode (first thought about naming it SH-01 A mode, but its probably better to use a more descriptive name). BUT after playing around with the 1.0 for a while, i saw that the ON/OFF pad can be used as pause-arp and its fun toggling it while playing.
    So, no third state for that pad - and no ‚hey here‘s the new version in on day‘ ;-(

    I think i will pickup the UI changes i made to the internal v1.1, where the HELP page displays other knobs than the main page, allowing six instead of 3 settings knobs. Stuff that make sense to be changed during live play on the main page and basic configuration knobs on the HELP/CONFIG page.

    This is great. Studying your code and techniques is useful for anyone interested in making MIDI tools. For the “New to @_Ki” user I use and recommend these scripts to solve important problems.

    MULTI-DIVISI:

    Divisi takes chord input and outputs notes on individual channels. I use this to send suggester chords to a MIDI recorder like Atom 2. Then I export the MIDI file for import into DAW’s with my most used DAW being Staffpad. So, I can select chords and get a strings arrangement in a manner of minutes without having to enter notes with the pencil in StaffPad:

    https://patchstorage.com/multi-divisi/

    SMART-CHORD-BASS:

    I use this to generate a bass line from a chord app like Suggester (@_Ki also has a note to chord script).

    https://patchstorage.com/smart-chord-bass/

    There are 39 more and they are worth checking out. The animation in the “AUM Transport Control” is mind boggling:

    https://patchstorage.com/aum-transport-control-demo/

  • @catherder said:
    I checked my hardware, and with the exception of the Roland SH-01A all the other gear (Arturia KeyStep, Arturia MicroFreak, Volca FM) has arpeggiators that make no exception for monophonic playing.
    I am interested if there are any other arp implementations similar to what Roland uses in the SH-01A.

    You could use Midi Tape Recorder to capture the midi out from the Roland.

  • @Wrlds2ndBstGeoshredr said:

    @catherder said:
    I checked my hardware, and with the exception of the Roland SH-01A all the other gear (Arturia KeyStep, Arturia MicroFreak, Volca FM) has arpeggiators that make no exception for monophonic playing.
    I am interested if there are any other arp implementations similar to what Roland uses in the SH-01A.

    You could use Midi Tape Recorder to capture the midi out from the Roland.

    Or Atom2 or whatever, if you need editing abilities.

  • @_ki said:
    @Mcd As soon as i saw the discussion, i had the idea to in coorporate that ARP playstyle into In-Order-ARP; very cool that you also noticed that minimal changes are needed.

    Internally i worked again on that script about two years ago, it was was published 2019. I wanted to add the swing features i implemented in my AddSwing script. But never finished debugging that arp-with-swing update.

    This morging i had the idea to re-purpose the ARP on/off pad to include switching to the new ARP-Poly-Only mode (first thought about naming it SH-01 A mode, but its probably better to use a more descriptive name). BUT after playing around with the 1.0 for a while, i saw that the ON/OFF pad can be used as pause-arp and its fun toggling it while playing.
    So, no third state for that pad - and no ‚hey here‘s the new version in on day‘ ;-(

    I think i will pickup the UI changes i made to the internal v1.1, where the HELP page displays other knobs than the main page, allowing six instead of 3 settings knobs. Stuff that make sense to be changed during live play on the main page and basic configuration knobs on the HELP/CONFIG page.

    @_ki thanks for this great Mozaic script and having a look into this. This could become THE Mozaic arpeggiator. I do have a few suggestions that I would like to share and that you might want to implement at one point:

    • I would love this arpeggiator to have all the usual arp modes ( up, down, up/down, up2down2, down/up, down2up2 and maybe random ). In the code I would have an equivalent of the noteList array but that stores the incoming notes in MIDI note id order. Doing the sorting on note arrival is probably less problematic than doing it in the actual arpeggiator loop. It should then be fairly easy to loop through that second array in any direction to have the other arp modes ready.
    • Looping over multiple octaves would be great.
    • About the UI: I would change the role of the SHIFT button so that it toggles between two sets of pads: a tempo page (the current set up) and a pattern page that allows for selecting the arp patterns and maybe the number of octaves. I would call the help page on a long press on SHIFT. The current SHIFT functionality (double note) would replace the ARP OFF pad, and the ARP OFF would be on the new pattern page. The current HELP knob could be used to set the minimum number of notes that need to be active simultaneously for the arpeggiation to start (Call it SH-01A function or whatever). If that knob is set to 1 it would mean the arpeggiator runs all the time.

    I hope that's not too much... Although I am a programmer myself, I feel reluctant to create a fork because I think one project of that kind is the best and the credits should go to you. To help people who use other arpeggiators, I have just upgraded my "FreaKontrol" script so that it has the ability to only route MIDI to the other configurable channels if more than X notes are active at the same time. Below X notes will stay on the input channel. This still needs some work, but the first upgrade is already on Patchstorage.

  • @Wrlds2ndBstGeoshredr said:

    @catherder said:
    I checked my hardware, and with the exception of the Roland SH-01A all the other gear (Arturia KeyStep, Arturia MicroFreak, Volca FM) has arpeggiators that make no exception for monophonic playing.
    I am interested if there are any other arp implementations similar to what Roland uses in the SH-01A.

    You could use Midi Tape Recorder to capture the midi out from the Roland.

    That would work, but I play mostly live and without DAW, so I do need something instant. The other option would be to use the Roland as MIDI sequencer / controller - the problem here is that it's one those synths that are almost always part of my music.

  • @catherder These are good ideas about a generalization of the in-order-arp skript. Note sorting isn‘t a problem, done that quite often in my scripts. But i‘m current not sure if i want to expand the use-case into the realm of commercial ARPs with an jack-of-all-trades ARP script.
    And i‘m missing a bit of challenge in that (ie i see no real hurdles in doing so that have to be overcome), developing a good and easy/fun to use UI will take a lot of time, and the whole idea sounds a bit like work.

    So, first i‘m going to add the Poly-Only mode into the In-Order-Arp with an updated UI and then we‘ll see further :)

  • @_ki said:
    @catherder These are good ideas about a generalization of the in-order-arp skript. Note sorting isn‘t a problem, done that quite often in my scripts. But i‘m current not sure if i want to expand the use-case into the realm of commercial ARPs with an jack-of-all-trades ARP script.
    And i‘m missing a bit of challenge in that (ie i see no real hurdles in doing so that have to be overcome), developing a good and easy/fun to use UI will take a lot of time, and the whole idea sounds a bit like work.

    So, first i‘m going to add the Poly-Only mode into the In-Order-Arp with an updated UI and then we‘ll see further :)

    I fully understand and I know the feeling of not wanting things to be like work. And thanks for adding poly-only to In-Order-Arp.

  • @catherder
    Here’s a very simple Arp patch.
    When one note is played, no Arpeggiator.
    When two notes or more are played, the Arpeggiator plays.

    The oscilloscope isn’t necessary, it’s there to check the gate signal.

  • @Gravitas that looks genius! I can’t seem to get it to work when setting up as in your picture.. I wonder whether that is because I can’t find a MIDI switch without 1-N or N-1.

  • @pruddo said:
    @Gravitas that looks genius! I can’t seem to get it to work when setting up as in your picture.. I wonder whether that is because I can’t find a MIDI switch without 1-N or N-1.

    Opps…..
    The Midi Switch is in the Beta….
    Damn….
    Okay, I’m going to rethink the patch and hopefully get myself out of trouble.
    Back soon.

  • edited August 2023

    Thanks! I do am enjoying thinking/messing with Drambo as you showed there never used those modules.
    Can’t quite comprehend how that poly to mono behaves when feeding it ‘voices’..

  • Updated patch so that you can use it with the App Store version using the Layers module.
    The second row of modules is with the Layers modules and you will be able to see the difference.

  • @Gravitas said:
    Updated patch so that you can use it with the App Store version using the Layers module.
    The second row of modules is with the Layers modules and you will be able to see the difference.

    Thanks for the work - awesome. I should have expected that "Drambo can do it" applies to this problem as well.
    Sadly I cannot find the "Pitch Switch" module.

  • @catherder said:

    @Gravitas said:
    Updated patch so that you can use it with the App Store version using the Layers module.
    The second row of modules is with the Layers modules and you will be able to see the difference.

    Thanks for the work - awesome. I should have expected that "Drambo can do it" applies to this problem as well.
    Sadly I cannot find the "Pitch Switch" module.

    I labelled it “Pitch switch” to differentiate the difference between each layer
    as there are three layers in this patch, one for velocity, gate and pitch respectively.
    Basically just use the Switch module.

  • @catherder said:
    Many thanks to the many replies in this thread! I love it to see how ideas start growing from a seed question. Great community here.
    @McD: Thanks a lot for taking action and modding the Mozaic script. I am going to mod that arpeggiator in the same way. And looking at the code I can see ways to implement the standard arp functions up - down - up down - up 2 down 2 etc...
    @wim: Thanks for mentioning Polytemus AU. Not exactly the solution, but I am thinking about a Mozaic script that does split notes to different channels according to how many are played together. So it could be plugged in front of any arpeggiator and allows this sort of playing with SPA and other apps.

    How does your modding work progress? Sometimes changing code can be tricky. I hacked the script to add a “Transpose” function in place of the HELP button. Since I tend to run 3-4 instances I might want to keep the transpose value in a Global Variable so they all change at once. Once you get an interesting arp running using the HOLD function then you can send that pattern around using Transpose. A page with interval pad options would also be a nice version. Then you can send the patterns around Chromatic Median intervals (+/- Major or Minor intervals). It’s very “Lord of the Rings” style… a fantasy musical genre pioneered by the great Bernard Herman who did the “Jason and the Argonauts” and “Journey to the Center of the Earth”. The original ideas probably came from Gustafson Holst’s “The Planets” orchestra suite.

  • I saved some arps using Atom 2 MIDI recorder and imported that MIDI into Staffpad and didn’t use the pencil once:

    Yes… there are hung notes from the transposing but some may like the added dissonance. What do you expect with a 5 minute experiment? I’ll work on stopping all active notes when the Transpose knob gets changed.

  • @Gravitas said:

    @catherder said:

    @Gravitas said:
    Updated patch so that you can use it with the App Store version using the Layers module.
    The second row of modules is with the Layers modules and you will be able to see the difference.

    Thanks for the work - awesome. I should have expected that "Drambo can do it" applies to this problem as well.
    Sadly I cannot find the "Pitch Switch" module.

    I labelled it “Pitch switch” to differentiate the difference between each layer
    as there are three layers in this patch, one for velocity, gate and pitch respectively.
    Basically just use the Switch module.

    Thanks for the explanation. It still doesn’t work. I wonder if the beta you are using has some bugs fixed that make it work:
    In my setup the poly to mono module outputs about 4 times the value of the incoming 4 voice polyphonic stream. This will never get past the A=B function. I tried to divide by 4 (divider and number module) but this doesn’t work either.

  • @McD said:

    @catherder said:
    Many thanks to the many replies in this thread! I love it to see how ideas start growing from a seed question. Great community here.
    @McD: Thanks a lot for taking action and modding the Mozaic script. I am going to mod that arpeggiator in the same way. And looking at the code I can see ways to implement the standard arp functions up - down - up down - up 2 down 2 etc...
    @wim: Thanks for mentioning Polytemus AU. Not exactly the solution, but I am thinking about a Mozaic script that does split notes to different channels according to how many are played together. So it could be plugged in front of any arpeggiator and allows this sort of playing with SPA and other apps.

    How does your modding work progress?

    Thanks for asking. I’m busy with a lot of work at the moment, so sadly nothing happening. I am happy that I could find the time to play some music with my friends tonight.

  • @catherder said:

    @Gravitas said:

    @catherder said:

    @Gravitas said:
    Updated patch so that you can use it with the App Store version using the Layers module.
    The second row of modules is with the Layers modules and you will be able to see the difference.

    Thanks for the work - awesome. I should have expected that "Drambo can do it" applies to this problem as well.
    Sadly I cannot find the "Pitch Switch" module.

    I labelled it “Pitch switch” to differentiate the difference between each layer
    as there are three layers in this patch, one for velocity, gate and pitch respectively.
    Basically just use the Switch module.

    Thanks for the explanation. It still doesn’t work. I wonder if the beta you are using has some bugs fixed that make it work:

    Most probably.

    In my setup the poly to mono module outputs about 4 times the value of the incoming 4 voice polyphonic stream. This will never get past the A=B function. I tried to divide by 4 (divider and number module) but this doesn’t work either.

    I’m having a play right now to see if I can improve it a bit.

  • @catherder could you post up a screenshot of where you’re got to so far.

    I’ve just looked at the gate signal from Poly to Mono into Function A=B
    through the oscilloscope and it is still 4 times the value of the incoming signal.
    I had designed it so that when both signals were equal to one then nothing happened,
    any signal greater than 1 would activate the Switch module/s.

  • edited August 2023

    @Gravitas said:
    @catherder could you post up a screenshot of where you’re got to so far.

    I’ve just looked at the gate signal from Poly to Mono into Function A=B
    through the oscilloscope and it is still 4 times the value of the incoming signal.
    I had designed it so that when both signals were equal to one then nothing happened,
    any signal greater than 1 would activate the Switch module/s.

    Problem solved, you just gave me the cue: I had the function connected to the pitch outputs and not the gates….
    I works fine now and I already converted it into a MIDI Rack.
    Thanks a lot.

  • @catherder said:

    @Gravitas said:
    @catherder could you post up a screenshot of where you’re got to so far.

    I’ve just looked at the gate signal from Poly to Mono into Function A=B
    through the oscilloscope and it is still 4 times the value of the incoming signal.
    I had designed it so that when both signals were equal to one then nothing happened,
    any signal greater than 1 would activate the Switch module/s.

    Problem solved, you just gave me the cue: I had the function connected to the pitch outputs and not the gates….
    I works fine now and I already converted it into a MIDI Rack.
    Thanks a lot.

    Awesome.

    No problem, enjoy.

Sign In or Register to comment.