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.

Dhalang MG Updated :)

Dhalang just got a fresh update. This dev is really on the ball. It's obviously a labor of love and he keep refining this incredible app.

https://itunes.apple.com/us/app/dhalang-mg/id1140174276?mt=8

My current favs are Dhalang MG and loving Reactable's ROTOR too.

Got my eyes on Phasemaker I think for my next purchase, but wanted to see what the Halloween sales would be first. ;)

Anyway, just a quick note that this dev just keeps making this very unique app, even better.

Looks like the desktop OSX version got the same update too.

Comments

  • @skiphunt Top stuff, cheers :)

  • Impressed with the rapidity of the work here. Only problem is that every time it gets updated I imagine (in my yellow heart) that it's even more difficult to figure out and so I creep back further into the cave.

  • @JohnnyGoodyear said:
    Impressed with the rapidity of the work here. Only problem is that every time it gets updated I imagine (in my yellow heart) that it's even more difficult to figure out and so I creep back further into the cave.

    It's a deep app for sure, but it's not that hard to get into it. It's the sort of thing that you can get to a place where you're making very interesting stuff, with full control over what you're doing, without understanding how it's doing it. Kinda hard to explain, but his last videos that he redid with text (6 of them at last count) are very helpful.

    I can only speak for myself obviously, but I haven't tired of it yet. Learn new stuff, and it also helps me understand other cyptic apps in the process.

    I'm not a veteran here to iOS apps like many of you are. So, if I can learn how to use this thing and get off on it, I think anyone can. :)

  • @skiphunt said:

    @JohnnyGoodyear said:
    Impressed with the rapidity of the work here. Only problem is that every time it gets updated I imagine (in my yellow heart) that it's even more difficult to figure out and so I creep back further into the cave.

    It's a deep app for sure, but it's not that hard to get into it. It's the sort of thing that you can get to a place where you're making very interesting stuff, with full control over what you're doing, without understanding how it's doing it. Kinda hard to explain, but his last videos that he redid with text (6 of them at last count) are very helpful.

    I can only speak for myself obviously, but I haven't tired of it yet. Learn new stuff, and it also helps me understand other cyptic apps in the process.

    I'm not a veteran here to iOS apps like many of you are. So, if I can learn how to use this thing and get off on it, I think anyone can. :)

    Fair and encouraging comment. Least I can do is put aside another hour and go through the videos again.

  • Thank you very much for the update and all the new and improved features. Great

    A couple of requests please, and I promise that's it ;)

    Could you add please the IAA logo and transport bar, so Dhalang can be played in sync with other apps? This is really necessary...

    Can you have a look at the MIDI clock and synchronisation in Dhalang? There is a major sync/clock problem within the app and with other apps.
    If I start to record something (internally or externally), the recording is always OFF time.
    Look at the drift of recording from a sequencer synced @ 100 BPM.
    Those are kick drums (sent and recorded) from a sequencer that I hit play with the metronome. If I missed the 1st beat is not important, look at the time drift within a couple of bars and resolution is 1/16....

    Vector and Matrix simply don't sync with the metronome and can start to record when ever they feel like it.
    I think that everything should be somehow internally synced to a master time.

    Also the MIDI send/receive/off doesn't work. (When I load it in AUM, the transport bar stops working)

    And another problem is that if I reload a sample with fixed pitch, like bass note: C3 in either Matrix or Vector, after changing the sample few times, the pitch goes up by 3-4 octaves and what used to be a bass line sequence is now a high pitch lead.
    I mean that I load a new sample and the new one is nothing like the original that I just loaded-pitch wise...(don't think it happens with loops..pitched or not...not sure)
    And there is NO way of lowering the pitch like in Touch play or elsewhere I tried.

    Again, thank you for your updates, fixes and new features, they are most welcome.

  • @JohnnyGoodyear said:
    Impressed with the rapidity of the work here. Only problem is that every time it gets updated I imagine (in my yellow heart) that it's even more difficult to figure out and so I creep back further into the cave.

    I share your trepidation and cardiac colorations on this app. Perhaps it's the sinister green on black interface, reminding me that there was a time when we had the Apple IIe and "Kobol" was a thing. But Mr. Rawlinson's video almost got me to come back out of my hole:

  • I just have so many apps I waste money on that I really don't need.

    I am considering saving the app money and returning to hardware and some Ableton upgrades.

    App looks great, but I don't feel like I need it.

    I don't have the time now.

    I wish I had more time.

    I need more money.

    And a larger penis would always make life even better.

    Well, I guess the app is the safest and surest bet after all.

    Maybe I will try it. ;)

  • @Hypertonal ...

    Further exploration with the app...yesterday I recorded a sequence from Matrix using a loop of percussion on Track 1.
    (I kept everything as simple as possible so I could follow the progression)...not too many notes...
    I had to quantise the recording on track 1 because the timing drifted off.

    sometimes sequence will start to play OFF sync with metronome, it almost sounds like the app and metronome are not connected together.

    Today I added a bass sample into Vector with 4-Xs and 4-Ys space/time...
    A very simple melody bass line that repeated regularly. I post the snapshot so you can see the pattern.

    Then I recorded the pattern on track 2 and selected the actual loop. To see.

    On the snapshot, the notes in yellow were supposed to fit into a 4/4 time bar but didn't and the whole loop "drifts" across the piano roll, being offset by a fraction every metronome tick.

    Another thing I discovered was why the recording was 3 octaves lower...for some reason the octave setting in (track record) was to -1 from the original C3...so the bass sample was barely audible rumble. This probably also answers my question about the pitch being 3 octaves up in my post above...
    Why can't pitch be recorded in default form, as I hear them and after I record it, then I could change the pitch up,down

    These are the things that frustrate me and I don't think they are "necessary," I have to always double check and CORRECT settings which should be default set on correct values...

    Sorry, I really like the app.....I thought I mention it...but hate to be the one reporting

  • edited October 2016

    As you have already noticed, new update is out.

    I am not going to change the program core functionalities in any drastic ways, and the biggest future addition is a matrix state machine, but that is almost the same as vector state machine and follows the same idea. Most new features are to make the old features more understandable and clear (like overall routing map/editor of the program) and naturally bug/ui fixes found on the way. All old project files will be usable with new program versions and will sound/play the same, so no worries about the software changing into something completely different just after getting into it.

    Some more complex AI ideas and more modular environments area ideas not for Dhalang MG but for some software in far future.

    I recorded a new tutorial video (about Feeds) and I am currently selecting/editing some music sketches into it - a scary thing to do. Will upload it in few days.

    @soundklinik said:
    @Hypertonal ...

    Further exploration with the app...yesterday I recorded a sequence from Matrix using a loop of percussion on Track 1.
    (I kept everything as simple as possible so I could follow the progression)...not too many notes...
    I had to quantise the recording on track 1 because the timing drifted off.

    sometimes sequence will start to play OFF sync with metronome, it almost sounds like the app and metronome are not connected together.

    Today I added a bass sample into Vector with 4-Xs and 4-Ys space/time...
    A very simple melody bass line that repeated regularly. I post the snapshot so you can see the pattern.

    Then I recorded the pattern on track 2 and selected the actual loop. To see.

    On the snapshot, the notes in yellow were supposed to fit into a 4/4 time bar but didn't and the whole loop "drifts" across the piano roll, being offset by a fraction every metronome tick.

    if the pattern would fit in a 4/4 bar with that Grid setting, the X pattern sum should be 16 - and not 10. Just the amount of steps in rhythm pattern does not tell how long it will actually be, as the step lengths in pattern must be also counted as a sum of of steps.
    I programmed those patterns to a vector and played and the result is slightly different. Shouldn't there be a fourth and seventh note on those empty positions, two notes below of what is currently lowest, or did you edit them away ? They show on your vector progression preview though.

    Another thing I discovered was why the recording was 3 octaves lower...for some reason the octave setting in (track record) was to -1 from the original C3...so the bass sample was barely audible rumble. This probably also answers my question about the pitch being 3 octaves up in my post above...
    Why can't pitch be recorded in default form, as I hear them and after I record it, then I could change the pitch up,down

    This might be related to your other problem with sample pitch. When loading a sample file to the sampler, it reads the sample file's "inst" or "smpl" data chunk that can have a midi note number in it to correspond the sample base note and frequency. If there is no such data, it is assumed that the sample is in C and when played it will be shifted in that relation. I realized there is a bug when base note/freq was read from some sample file and set to extremely low or high, and then loading the sampler again with some other sample that does not have that data chunk, the samplers pitch relation will remain that of previous sample even though the new sample is definitely not that high/low sound. I will fix this to reset it always to initial C when that data chunk is not found in the file.

    I made some tests by playing samples with vectors and then recording them into piano roll tracks after running "Auto-connect to Tracks" in the settings view (with this the octave/rectype/target settings of piano roll tracks and sequence generators will always match), and what was recorded played back 1:1 as the vector generation. I also played samples with virtual keyboard and recorded them and the playback was also the same.. so I am not sure what your octave problems are if not explained by the pitch data issue above.

    After some sync testing I noticed sync messages were ignored by default on rt midi library.. nice... well now it works. I see almost all sequencers send midi time clock at 24 ticks per quarter note, and this not directly compatible with dhalang (should be 64 ticks per quarter note) I will find some workaround for this for the next update.

  • edited October 2016

    Thank you very much @Hypertonal for reply and explanation...and THANKS for the updates, fixes, fulfilled requests and additions....greatly appreciated.

    I am not asking you to change the core program features, or anything, all I'm interested in is CLOCK - SYNC fix, and MIDI fix, so I can slave it and/or sync it with other apps,..and so it doesn't drift all over the place...the rest I don't care. It is working just fine now, as far as features go.

    Maybe (if I could have a wish,) it would be nice to "normalise" the common functions in all pages, so for example the transport bar is always top left, with record/octave/scale icons next to it, etc...so I don't have to look for things, sort of more intuitive navigation, but these are just extras...now I know where things are...

    hypertonal said:
    if the pattern would fit in a 4/4 bar with that Grid setting, the X pattern sum should be 16 - and not 10. Just the amount of steps in rhythm pattern does not tell how long it will actually be, as the step lengths in pattern must be also counted as a sum of of steps.
    I programmed those patterns to a vector and played and the result is slightly different. Shouldn't there be a fourth and seventh note on those empty positions, two notes below of what is currently lowest, or did you edit them away ? They show on your vector progression preview though.

    I didn't edit anything because I don't want to confuse you or anyone. I only highlighted the notes in first bar, (or what I thought should be a bar)...and also made a snapshot of Vector so you can see the note progression and maybe you can see what I was doing wrong or what was setup wrong....all was recorded and set as you see. No editing.

    I also re-tested the sample pitch and it got corrected with the octave settings in piano roll. One thing would be really helpful is if the octaves a number of octave next to the lines in octaves, so if the recording is going on and I see I'm recording a bass line in C5-C6.

    Thank you for all the updates and your time for trouble shutting and explaining things.

    I recorded a new tutorial video (about Feeds) and I am currently selecting/editing some music sketches into it - a scary thing to do. Will upload it in few days

    Thanks looking forward to this one.

  • edited October 2016

    @Hypertonal , thanks for bringing the "SUM" UP.
    I loaded 3 different samples a kick for short notes, a bass note for longer notes and a pad for long tones and started experimenting in Vector with 4 "bars" and SUM16 or a combination of 16 and settings in resolution = [-,1,2,4,8,16,32] to hear the different results....the combinations are just unbelievable...and everything IS perfectly aligned in the grid...

    So Is there a timing problem? I'm really confused and apologise because just in this instance there is NO timing problem. All is perfect over 8 bars ..I have been recording the results just to see how notes get distributed.Was it my misunderstanding of Vector? I wonder :#

    In experiments I got a 4 bar pad and a 64 beat kick roll (in 1 bar.) Two extremes. Easy :)

    PS. I am still having a lot of problems with the octaves changing their pitch without any doing on my part...just by changing a different scale or tuning....and after a while I am on octave 6 and no way to fix it?

  • edited October 2016

    @soundklinik said:
    @Hypertonal , thanks for bringing the "SUM" UP.
    I loaded 3 different samples a kick for short notes, a bass note for longer notes and a pad for long tones and started experimenting in Vector with 4 "bars" and SUM16 or a combination of 16 and settings in resolution = [-,1,2,4,8,16,32] to hear the different results....the combinations are just unbelievable...and everything IS perfectly aligned in the grid...

    So Is there a timing problem? I'm really confused and apologise because just in this instance there is NO timing problem. All is perfect over 8 bars ..I have been recording the results just to see how notes get distributed.Was it my misunderstanding of Vector? I wonder :#

    Let's say you have a vector with X/Time in pattern mode, and pattern length is 4, so there are four steps in the pattern. Let's say those four values are 6, 2, 6, 2 and the Grid is set to 16. this means the rhythm is: 6 x (1/16) = 6/16 = 3/8th note, 2 x (1/16) = 2/16 = 1/8th note, and again 3/8th, and the final one another 1/8th. so. 3/8, 1/8, 3/8, 1/8 . SUM is 6+2+6+2 = 16 = 16 x 1/16 = 1/1 which is a full 4/4 bar of 16th notes. So the SUM is an indicator of how many beats (defined by the grid) the pattern duration is. If the the song overall measure length, or Beats in Block, is 16, then this is the sum length for a full bar rhythm pattern.

    Y/Space works similarly but the steps have plus, minus and zero values. These correspond to interval movements in the pattern, +2 meaning two notes upwards, while -2 means two notes downwards, and naturally zero means no change in pitch (repetition of the last one). Here the SUM is an indicator for how much is the full pattern movement after each round the pattern is played from start to end. if the sum is positive, the pattern always starts next round the sum amount higher than previously, and again and again.. rising infinitely or at least when without return note, limits and Feed reading.. If the SUM is zero, the pattern ends at the same note it started.

    Both X and Y can have also stochastic modes, of which the X is kinda trivial but Y little more complex, as there is a mini sequencer at the bottom part "Y Direction" that sets the up or down direction according the probability values D1-D10, if the D value is at zero the progression goes always downwards, if 100, the progression goes always upwards, and the values between.. more or less up than down, and at 50 it's equally probable to go up or down.. so 50/50. Direction cycle length defines how many steps is in use of this mini sequencer and direction cycle rate defines how many ticks (of Grid setting) each Direction step takes. There are also scale settings for upward and downward progressions (like in Indian raga music, where different scales are used for ascending and descending parts)

    Note lengths on a vector are either defined by "Note Length" setting, that with value "X" takes the note length from the X pattern or stochastic selection lengths directly (note length is equal to step length ). When the value is "Gen" a note length is generated by the parameters below "Gen Base" and "Jit" . Base is the fixed center value (= length) and Jit a Jitter or random addition factor for the Base. Which means for example a Base with value 4 and Jit with value 2 will result note lengths 4, 5 and 6 for vector generation. As you can see, Note lengths are not the strongest feature in any of the sequencer generators and it's usually good to record a sequence to piano roll track and then edit note lengths by hand if needed.

    PS. I am still having a lot of problems with the octaves changing their pitch without any doing on my part...just by changing a different scale or tuning....and after a while I am on octave 6 and no way to fix it?

    The scales are quite safe to change on the fly in scale editor and sequencers etc.. but changing the whole tuning system is not encouraged without at least full stop of sequencers and synthesizers and then continue play with another tuning system. Changing tuning on the fly can cause some polyphonic voices (sampler and additive) to get stuck on some notes, but all voices can be killed/reseted with the Panic! button on settings view.

    I'll try to look into this, but I haven't actually been able to cause this by myself yet. If you could provide me a step by step guide to show how this happens, and maybe provide also one sample file that does this, so I could test and see what's going on. Maybe a private message ?

  • @hypertonal said:
    Let's say you have a vector with X/Time in pattern mode, and pattern length is 4, so there are four steps in the pattern. Let's say those four values are 6, 2, 6, 2 and the Grid is set to 16. this means the rhythm is: 6 x (1/16) = 6/16 = 3/8th note, 2 x (1/16) = 2/16 = 1/8th note, and again 3/8th, and the final one another 1/8th. so. 3/8, 1/8, 3/8, 1/8 . SUM is 6+2+6+2 = 16 = 16 x 1/16 = 1/1 which is a full 4/4 bar of 16th notes. So the SUM is an indicator of how many beats (defined by the grid) the pattern duration is. If the the song overall measure length, or Beats in Block, is 16, then this is the sum length for a full bar rhythm pattern.

    Thank you for the detail breakdown of the SUM. It is starting to "sync" into my thick scull. ;)
    This "math breakdown" is very important and explains the workings inside Vector.
    What I find great is how well it does rhythms using a tone=C3, (I used a sample that can play long or short, not only very short staccato like BD) where I can hear and see the length (I record and loop 8 bars) of the bass (pitch disabled in Y)....and then count and analyse.

    Then I started to move the "bars" (pattern steps) up/down in Y to get pitch variations...

    Vector is actually one of the most powerful sequencers that I have ever used...

    Thank you for the tutorial ^^^^ :)

  • Soundklinik,can I ask you what version of the iPad are you using? I have an Air 1 and it is freezing in the logo just to open it with the new update.My IOS is 9.3.5. Thank you

  • I have two iPads: air 1 and 2. Both on iOS 10.0.2 no freezes or crashes. Works perfectly on air 1.
    Just tested.
    You're welcome :)
    ...maybe time to update?

  • I'm sure I posted a message here but nothing has appeared.. but anyways,
    I uploaded a new tutorial video about Feed channels. I also made a
    compilation video of musical sketches made with vector&matrix
    sequencers using time synchronization and feeds with internal sounds
    and some acoustic drum samples. In the clips I am mostly
    changing trivial mixer settings and a master vector sequencer
    that guides all other sequencers.

  • edited November 2016


    Thanks great videos an d music in sketches :)

  • Just uploaded some new videos:

    Tutorial 7 about Feed channels.
    https://youtu.be/K3w_u8POP4o

    Some musical sketches I made during last week, in chronological order.
    First ones with a clear head, latter ones with not that clear B)
    https://youtu.be/-kLPDPEem-Y

  • Just uploaded some new videos:

    Tutorial 7 about Feed channels.
    https://youtu.be/K3w_u8POP4o

    Some musical sketches I made during last week, in chronological order.
    First ones with a clear head, latter ones with not that clear B)
    https://youtu.be/-kLPDPEem-Y

Sign In or Register to comment.