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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
Wrote a couple patches last night. Really like the amount of waves supplied for the granular oscillator. Resonator effect is awesome, too! Gonna explore the control surface options more this weekend.
Another vote here for sample import for the granular oscillator
If midi sync is in the pipeline, would there be an option possible for quantizing performances to an external clock? or is this not possible?
Already a great app though and am now hoping for TC-data to go on sale or in a bundle
Thanks, my mistake. I was thinking of TC11, not the Science Fair version
@Sinapsya said: Can you add a sample import...with Audioshare support, please?
Always and forever.
This is the intelligent version of my previous post and I approve this message etc.
Are you using TC Data with Gadget? Care to share more about your setup? That sounds pretty awesome.
Sounds good - I'll make some longer tutorials.
There is an appendix that explains • vs •••, ↑ and ↓, etc. in the manual (p. 63). The Help screen also has some animations to try and explain things as basically as possible. The long version is this:
• vs. •••
• (big single dot) means a controller / module that sends one value for the whole group, which is why I call these 'Group' controllers. For example, the Average Touch Size is a single value of all the touch sizes.
••• (three dots) means a controller / module that sends a unique value per touch, so called 'Touch' controllers. Example: the X Position of each touch is different, so each touch gets its unique value.
Try this simple experiment: create a new Default patch, and set the Osc A Frequency controller to Touch ••• >> Distance >> Distance to Center. See how each touch gets its own frequency? Now set the controller to Group • >> Distance >> Average Distance To Center. Now each touch gets the same frequency value, so you'll hear the same pitch coming from all touches.
↓ vs. ↑
↓ means 'when the touch begins,' because many of the controllers only send when a touch / group begins. For example, 'X Position ↓' means 'the x position of the touch, sent only when it begins.'
↑ means 'when the touch ends.' For example, 'X Position ↑' means 'the x position of the touch, sent only when it ends.'
I have TONS of ideas for sample-based objects. Because of that and the infrastructure needed to work with audio files, I've decided to make a separate app dedicated to it. TC-11 will stay straight synthesis.
@BitShapeSoft i have a similar request for TC-Data but if both apps have the same functions i'll pick it up from those.
Can you upload the patches for us to try out?
Will do that a bit later on tonight, at work right now. Fair warning, they're pretty basic (I didn't change anything about the surface area).
@BitShapeSoft I've been testing out using TC-11 in audiobus with this simple setup (see pic). Unfortunately I'm getting some glitches and performance issues when playing apps like seekbeats at the same time, also tried with other apps with the same result.
I'm using an ipad mini retina ios 8.2. Does anyone else experience this? I'm also set on 1024 frames.
This is why I would like a cpu meter in audiobus (and perhaps a measurement for each app so you can see what's going on).
I can see this app being really great for playing directly into a laptop or desktop, but is the performance too cpu intensive for most iPads to handle along with other apps?.....or is this a bug or Audiobus problem?
(edit: It's happening outside of Audiobus too so I guess it's cpu overload problem?)
I guess the Air 2 would play better with other apps......
Ps the glitches don't happen at all times with all patches but enough to be annoying. Love the app though, performance issues aside
Thanks for the explanations. Very helpful! I did look at the TC-11 guide and was more interested in if these same terms apply to TD-Data. Also noticed the ".->.*" in the sequencer as an option. Is that new in TC-11? TC-Data 1.2?
cheers...
Yes, the symbols are the same for TC-11 and TC-Data. •→• is only applicable to Sequencers on TC-11 because it connects each successive sequence value to the next active touch (so it cycles through all the active touches, see the patch Halogen, for example).
Tutorial! Can you split the screen into pieces?
Hi all / @thesammiller
In terms of telling more about my TC Data > Gadget setup, I discuss it in this thread and you can download the template.
http://forum.audiob.us/discussion/8034/lfo-midi-ccs-from-tc-data-into-gadget-free-template#latest
Here I'm sending LFO data into gadget - so you can basically attach an LFO to modulate absolutely any control in any gadget.
What I've been working on recently is what I'm calling my Figure emulator. So that's using the way that Proppellerheads Figure lets you play - but remaking this in TC Data and firing notes and ccs off to Gadget. I've basically got it working and even syncing / quantising to Gadget (just like the way Figure quantizes) as long as you set the TC Data sequencer off at the same time as Gadget starts a new bar. I'm loving it basically. When it's perfected I will share the template.
Edit: it goes beyond figure too. Because you can modulate more stuff and create any rhythm pattern you like.
@Matt_Fletcher_2000 you are off into the rarefied air now Mister Fletcher, off beyond the clouds that we mere knockers and tappers can only dimly imagine. Godspeed to you Sir....
@bitshapesoft thanks! I'll run through those steps later but example setups like that would be great for TC-Data.
@Matt_Fletcher_2000 very generous of you sir!
Yep, i'm thinking a video might help... but I need to find the time... but you'll all get it if you see a video...
Imagine playing Figure with that lovely way it always makes it sound like you can play in time and in rhythm ( - and you can restrict to certain notes and pick different rhythms to use - and modulate expressively on the y axis) - but it's sending it's midi out to Gadget... A.W.E.S.O.M.E.
@Bitshapesoft - quick question... "Tutorial! Can you split the screen into pieces?" - does this work for TC Data? Can I have 2 different performance areas set up differently in TC Data?
@Bitshapesoft:
Checked the new user guide and found all the new appendices with the good details. Happy to see all that!
I originally did not look deeper in the new tc-data manual since it still showed version 1.0 on the first page;)
@Bitshapesoft - i'll answer my own question above and say "yes - by using a 2 parts table". I found some time to watch the whole tutorial video through... Very nice. I'll have to get my head around relate everything to either half of the table - but that's for a another day...
I must say - you must a be total freaking genius to programme all this stuff... It's so.... deep... it's scary.
One request - would be nice to have a bit more flexibility one day to "paint" on the performance screen - right now it's just a single x grid and a y grid - but it would be nice to do things like have root notes marked in a different shade, create different grids on different parts of the screen if you are splitting the screen in half and then splitting again within each half etc... To aid playing.
Thanks, gonna put some time into it this weekend.
How do I initialize a program? I can't seem to get to a blank canvas..
edit: Got it!
@aleyas - how do you get a blank canvas please?
blank Canvas in TC-11 = "Default" patch, it's both in the patch list, and you have the option in one of those save buttons when you're editing a patch proper.
haha, developer should write "TC-11 For Dummy!"
Is the 'Touch Size' controller not available on iOS7? I'm seeing it as greyed out, and the patches that have it included are unaffected by differing touch sizes.
I can confirm with ios 8.3 the glitches are so far not happening for me which is great news.
That's right. Long story short: that property was always available on UITouch objects, but your app would be rejected if you included it. In iOS 8 they opened it up as a public property.
Happy to announce the first of a few upcoming surprises: TC-Orbiter!
http://www.bitshapesoftware.com/instruments/tc-orbiter/
It's a small utility for controlling device motion on your big iPad with your little orbiting iPhone / iPod touch. After performing a bunch with the iPad tethered to a table with cables coming out of all ends, I thought it would be nice to separate the motion control into the smaller form factors.
Plus: standard and Bluetooth LE MIDI output. I'm really happy with the latency / performance of Bluetooth MIDI for transmitting the device motion. You can use any of the TC device motion controllers and save configurations in-app.
Don't forget to update TC-11 and TC-Data today too!