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
You can save a snapshot in TB MIDI Stuff too and send all values to the circuit. Am hoping that will work!
Does saving the session save the synth preset ? I know it saves the macro positions but didn't think it saved anything else regarding the synth, other than which patch is used.
I am looking to be able to do this all from the Circuit/iPad, so I don't have to pack up a laptop from my work desk, take it home, plug it into the circuit, just to save a preset
If it does save the preset as part of the session, then great, I'll just take the circuit to work once a week and save then.
@AndyPlankton, I'm not sure if this explanation below helps or just repeats what you're getting at. You may also be very familiar with the owners group too. I'm not sure who's who across forums/groups
In my layman's terms (paraphrasing from Paul Cotton's explanations on the FB group):
Twiddling macros, plus changing settings in any editor, and then saving a session saves the current state of the 2 synth patches etc, with changes, but only to one of the 32 areas of session memory, as it were. Isotonik's official Novation Circuit Editor has a way to also save to the central patch bank memory, but how it does that loading and saving (I guess via SysEx strings) isn't yet known on the Circuit Owners Facebook Group. We know what the SysEx code is to request a full dump (of all patches, sessions, etc) (that backup request is F0 00 20 29 00 78 00 00 00 02 0E 00 00 00 00 00 01 0A 0D 00 00 00 F7) but we don't see to know publicly how to get at the specific area of patch memory or at specific patches. I'd love for our custom/mobile editors to be able to that, of course. Hopefully, before long!
In the meantime, as @ghostly606 suggested, we can save to session memory. To get that patch into another session (without copying the whole session) we'd need to currently either store patches as canvasses or the like on TB MIDI Stuff etc (which might get quite quite bulky on iPad), or hook up Isotonik's Editor to be able to pull it off the Circuit and save it to the actual patch bank.
P.S. Your Lemur template looks cool. Am keen to compare notes, though have been looking at TBMS and am not very experienced with editors or synths. One thing is that I now get how to setup a randomizer in TBMS, for a patch generator. Do you know if that's possible in Lemur? Have your considered it?
Thanks
Is there a way of monitoring the MIDI messages exchanged between the Circuit and the editor? You are right, it must be down to sysex stuff which makes me cross-eyed.
@Salamander69 thanks for the info....I don't use FB so had no idea that the owners group existed
, I don't know if I am missing something, but I cannot see the request going from isotonik to the circuit, only the sysex that comes back.
seems like you are pretty much in the same state as me, yes it is the individual patch sysex commands that I am after, and a description of the sysex itself, the return message is 350 bytes, I could go through tweaking one parameter at a time, then request patch through isotonik and see the sysex coming back using midi monitor, but that will take a while, documentation would be easier
I haven't yet found any file IO within Lemur of any sort so local storage on iPad is probably a no go.
One thought I have had is to have a play button in the template that will send all the CC's and NRPNS , this would allow sending a patch to different sessions via normal midi. Not sure how the iOS sequencers would cope with recording NRPN (in theory it should work as they are only CC's anyway), but having this it would be possible to record the MIDI coming out of lemur and then save that for recall later. I could then reload a patch by playing the midi back to lemur. This would require some hefty-ish programming in lemur though to process the incoming NRPN'S. Sysex dump would be far easier, Load current preset from circuit, edit it, save it lol.
Lemur has some great controls available, including ones that support physics, and yes random patch generation has crossed my mind, as has having 'flickable' physics controls to use as additional LFO's, there are lots of possibilities with Lemur, the scripting inside it is pretty impressive and you can do pretty much what you want.
Hmmmm, does this mean that we have actually effectively got 128 storage locations for patches.....64 presets and the 32 x 2 synth in sessions ?
That's pretty cool if we have
It does, but you can't copy the patch data between sessions.
Cool. I can live with that for now
Cheers peeps for the help
I opened a Facebook account just for a couple of groups. The format has pros and cons, but they're a great & mixed bunch of people on the Circuit Owners Group. Also, it was setup by Novation and is contributed to by folk (in an unofficial way) from Novation and Isotonik, kind of like this forum in a way.
good stuff !
Yes, use MIDI monitor from the Snoize site. I was planning on having a look at the editor at some point soon, though I'm guessing it'll be (very, very slightly) trickier than the dump messages as it'll likely have the patch numbers embedded in the message(s).
If the message to request current patch data is found, I wonder if an app like the new GigRig MIDI+ https://itunes.apple.com/app/id1090436811?mt=8
or Midi Tool Box app could be useful as patch librarians.
New one on the Circuit, midi through Wej to iPad.
Lol....
Hey @KlaatuNinja, there's an error on that video for some reason. Maybe it's my PC at work mind you...
Looks like it would work. I tried using my template for real this weekend, and where it seems to work great for editing there are a couple of issues that I need to work on.
With Lemur, it is sending midi out when I load the app corresponding to the buttons on screen, this means that if I start Lemur it automatically initializes the patch, which is not what I always want. I think I will have to not use the auto midi binding in Lemur and program the IO of the CC's myself, I had to do this for the NRPN's and the majority of the settings are NRPN so most controls are already done for MIDI Out,
In order to be able to use GigRig I need to write code for MIDI IN to allow the editor to respond to incoming MIDI I'll have to write code to process this as NRPN's are not automapped, and I'm probably gonna disconnect the CC's from automap as well now.
Still a lot of work to do, not as close to finishing as I thought.
Re Lemur editor:
Sounds pretty arduous. From what I can see of your screen shots, mind you, if you manage to pull it all off, it'll be by far the most comprehensive of any of the iPad options I've seen to-date. Here's wishing you a lucky break or 2!
So far with my trying to monitor what the Isotonik Editor sends out - most importantly the 'Get current patch from Circuit' message - I've not found anything on PC. I'll see if I get anything using a Mac. Am not sure that I have necessary cables. And am starting to get freaky and think it might be some java voodoo or something (what's the SysEx to json conversion about when it occurs? I don't know my stuff)
I've lodged a request for the get patch message with Novation support and Isotonik too, in case they're feeling extra generous. And email is far easier to monitor
What I get back from Circuit when the Editor sends its request is the current Synth session memory patch. Which is what we want, most of all, for an iPad Editor to corespond with Circuit, I'm thinking. And when I send it back to Circuit via MIDI-OX, it changes the session memory Synth (the one that's got focus on Circuit, I hope. Or perhaps Synth 1 or Synth 2 is designated in the SysEx: which would complicate things I imagine, but need to test for that.
Ever getting at the central patch bank memory would be he icing on the cake...
Me too
Synth 1 or 2 IS part of the sysex. Can't remember which byte in the systex off the top of my head, but it is one of the first five or six.
EDIT: Seems like sysex in Lemur is limited to 256 bytes, the sysex coming from Circuit is 350 bytes. BUMMER!
Yay!
Have got the SysEx messages to get the patches from session memory on Circuit. MIDI Monitor on Mac was able to spy better for me than I managed to on Windows.
Get Current Patch from Circuit - Synth 1
f0 00 20 29 01 60 40 00 00 f7
Get Current Patch from Circuit - Synth 2
f0 00 20 29 01 60 40 01 00 f7
Needs more testing but seems to do the job. For example, in theory ought to allow an iPad editor to ascertain the settings so you can instantly edit the current patch as it is in the current session on Circuit. Note that, these particular messages don't get at patch bank memory. But it's a start!
Note also that it may be the 8th byte (this count inludes the f0) in the received patch data which designates that it has come from either synth (00 for synth 1, 01 for synth 2. Thanks @AndyPlankton for the lead on that.
Wahey good going.....
Thing to do now is set a patch to 0 values for everything, get the sysex.
Change one parameter in the patch, get the sysex, compare it to the 0 patch and see whats changed, then do that 300 odd times, once for each available parameter.
Gutted that Lemur only has 256 bytes for sysex, means my template is pretty much useless
this is what i got from google:
That's about it
Just a headsup for any interested Circuiteers who might not have seen that Modstep now includes a template for said box of wonders. Available for fresh reinstalls or from devs website I hear.
Nice, thanks for the heads up!
Sorry for anyone getting this more than once, but...
A little more SysEx pogress. Uploading to the patch bank seems to be controlled by 2 bytes: hex byte 7 (I'm including the header byte f0 in this count across the array) (value 01) and byte 8 (value 00 for slot 1, 01 for slot 2, through to 0f for slot 16, 10 for slot 17, through to 18 for slot 25, and 3f for slot 64). So If we, for example, use the 'Request synth 1 patch from session memory' sysex string (f0 00 20 29 01 60 40 00 00 f7), we can keep that patch on file in a Sysex librarian, open the file anytime we want, eg in MIDI Tool Box on iOS, and edit bytes 7 and 8 to upload the patch to the patch bank, or leave the file as is to upload it to synth 1 in the current session, or change only byte 8 to 01 (leaving byte 7 as 00) to send the patch to synth 2 in the current session. And if you're not yet bored to tears by this stuff, I've found that macro knob 1 seems to be controlled by byte 214 (value 00 to 7f), knob 2 (byte 231), knob 3 (byte 248), knob 4 (byte 265), knob 5 (byte 282), knob 6 (byte 299), knob 7 (byte 316), and knob 8 (byte 333).
Keep it coming
Yeah, all 286 or so more parameters
I had spread my parameters over multiple panels but I reckon everything in sight works better, check out the Waldorf Blofeld editor:
The Blofeld is a more complicated synth but the way everything is incorporated is very clever. I'm on it!
On the Blowfeld editor or the circuit editor?
Doing a total makeover of my unfinished Circuit Editor, which was getting a bit unwieldy spread over 7 panels (osc, filter, env/lfo, mod, macro 1, macro 2, fx). In particular, use of sliders, sitting behind parameter name seems a quick way to get a lot of information in a limited space.
Anyone who has Lemur and Circuit who wants to give this a go is more than welcome
https://www.dropbox.com/s/aq4c197udmacfwn/Novation Circuit Editor.zip?dl=0
The template covers all parameters on synth 1 and synth 2
Copy the template to your device using iTunes, then edit the template and make sure the Circuit is selected as MIDI TARGET 0.
There is a midi transmit button in the centre of the Synth Engine screen, I had to do this to prevent the editor from overwriting your current circuit patch on startup.
Start the Lemur app, and when the template is loaded turn the MIDI button on (will go green) Then any changes made will be transmitted to the Synth1 or Synth 2 in your current session. COmms is one way at the moment so MIDI only goes from the editor to Circuit.
I have not tested every single parameter in detail but all seem to work on the face of it.