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.
DX7 cartridge generator
This website generate parches for the dx7 and packages them into a cartridge...if you run it in safari on your iPad you can simply use open in to send the cartridge to KQ Dixie.
Comments
I’ve tried it. Some of it’s unusable and some of it’s awesome and even inspiring. I used to have a random patch generator for my Casio CZ’s. Similar experience. There was enough brilliance to be well worth doing.
@anickt Where is the CZ one? I'd love to try that.
Some of the patches are wonderful. Thank you!!!
+1
https://lewismidi.com/czpl/
This is the Cz1 patch generator / librarian thingamajig
We talked about this the other day, or you would be getting more responses.
That’s going back to my hardware days. It was an app on my C64.
This is really cool. Nice find. Thanks for the share.
Ace !!! Muchas Gracias !
The next Streambyter or Mozaic project: A patch generator generating pseudo-random MIDI SysEx patch data to feed into your hardware synth 😅
Is there enough data type support in Mozaic to send out the required Sysex bytes? Seems like it only offers integers and decimals and does some internal type casting into floats when needed but nothing like HEX codes. No HEX is one of the things that makes Mozaic easier to jump into as a newbie over StreamByter which started out with a bias towards HEX and slowly added integers and decimals.
Hm, it's certainly possible in Streambyter but I don't know much about Mozaic tbh.
Hex is just a different representation, if Mozaic lets you compose sysex messages and supports randomization then you should be good to go.
This box doesn't generate anything, you'll have to load your existing patches into it.
The iOS app SysexBase by SecretBaseDesign can do the same, and you can use real names for your patches. It also supports folders for categorizing.
Yes, there definitely is. There is full support for Hex in Mozaic. To notate a number in hex just preface it by 0x (example 0xB7). Integer math operations work the same as with non-hex notated numbers, and you can use math operators such as
&to do things like isolating particular bites of a multi-byte number.Sysex messages are simply structured sets of hex bytes. Sysex support is covered in detail on pages 40-43 of the Mozaic manual.
Cool. So, is the structure of a DX7 syses file documented somewhere so randomized
versions could be sent to a KQ Dixie instance using the sysex commands?
The sysex implementation must be documented somewhere or people wouldn't have been able to develop apps that use it. But about 20 minutes of digging didn't turn anything up.
An approach that might be a little easier to manage would be to send randomized cc's mapped to relevant exposed AU parameters. There are some Mozaic scripts that generate random cc values. The initial mapping would be a pain though.
Seems like a lot of trouble to go to when there's already a tool available, but hey, I'll use it if you make it.
I made some progress looking at the HEX DUMPS of a couple "RAM CARTRIDGES". Here's a typical HEX listing for one preset - the preset name comes at the end starting 4 characters from the end of "0df0" line and wraps around and can be up to 9 characters in length.
00000d90 00 00 39 00 00 0a 00 4b 15 24 3f 63 5a 55 00 00 |..9....K.$?cZU..|
00000da0 00 00 00 30 04 35 02 01 35 13 29 28 30 3a 14 09 |...0.5..5.)(0:..|
00000db0 00 00 00 00 38 04 5a 02 02 57 0a 35 1f 63 5e 56 |....8.Z..W.5.c^V|
00000dc0 00 00 00 00 00 38 0c 63 02 00 21 1a 35 19 63 00 |.....8.c..!.5.c.|
00000dd0 50 33 00 00 00 00 38 06 63 02 00 2d 14 35 2f 63 |P3....8.c..-.5/c|
00000de0 5a 00 00 00 00 00 00 38 00 63 02 00 12 3c 5f 3c |Z......8.c...<_<|
00000df0 32 32 32 32 06 0f 23 00 0b 02 18 18 56 4f 49 49 |2222..#.....VOII|
00000e00 48 53 20 20 20 20 63 48 30 11 63 60 00 00 00 00 |HS cH0.c`....|
There are 32 of these packed into a sysex file with a standardized header:
00000000 f0 43 00 09 20 00 63 30 14 19 63 63 00 00 12 00 |.C.. .c0..cc....|
Some more comparisons of preset might disclose a bit more about the formatting of
the preset parameters.
@wim - do you think Mozaic has the variable structures to create these HEX values after randomly changes and outputting it via the sysex commands. The only storage tool
Mozaic offers is the 1024 space variables and I guess 2 HEX values per slot makes sense.
It would be fun to press a pad and get a new batch of KQ Dixie presets to tinker with
but I'd appreciate you take on feasibility of the data structures. I'll crack the Mozaic manual in the morning too for the sysex details.
Eh. Sorry, I’m not really getting the point of this. I’m sure you can use Mozaic to construct and send the sysex messages, but not really interested in delving into how to go about that.
Sorry.
Also, I’m not sure you can assume what’s stuffed into those files directly correlates to any sysex streams sent to the app or device.
You would be better off seeing if you can intercept the actual data flow. I don’t have any ideas for you as to how to do that though.
@McD, @wim: Some useful info here & for anyone else who wants to dive in:
Building DX7 SysEx messages:
https://homepages.abdn.ac.uk/d.j.benson/pages/html/dx7.html
(See "C program to convert from raw files to sysex files")
The DX7 patch parameters deciphered:
https://github.com/asb2m10/dexed/tree/master/Documentation
C code but it may be another good source for understanding the structure:
http://www.parnasse.com/dx72csnd.shtml
or
https://homepages.abdn.ac.uk/d.j.benson/pages/dx7/csound
KQ Dixie can be used to control a hardware DX7 via midi. That implies that it puts out compatible Sysex when you adjust controls. Capturing and analyzing that output might yield some useful results.
But, seeing that you can midi map every control in the app, again, it seems like you would spend less effort just by mapping them all then sending random values for each cc. It would only take one small
forloop to blast out 128 random cc’s. Thirty minutes mapping cc’s to controls plus 10 minutes programming seems a lot more practical to me.Even less effort just to download from the web tool 32 patches at a time. Sorry ... just not feelin’ this one.
I admire your enthusiasm for the challenge though.
Any good info /resource available on understanding the KQ Dixie File saving/import process?
Also, Rename function doesn’t appear to work on some file types. Like the files from this cool Cartridge Generator.
Is there a neat way to make sure these appear in the AUv3?
I’ve spent 30 mins on it now but nothing is too clear. Cheers.
Cool shit!
Big Thanks!
Sorry about that other thing!
LOL! It's not intuitive. Are you on iOS 13? If so, when you tap on Click Here To Generate you will get a Do You Want To Download box. Tap Download. Tap on the download icon in Safari. Then tap on the downloaded file. You will get a screen with a share icon in the upper right. Tap on it and choose Copy to KQ Dixie. A confirm box will come up in KQ. Tap load. The cartridge contents will be loaded on the right. Choose DX+, set it to 32 and iCloud and hit save. It will be in the iCloud folder in KQ.
Thanks for this. I’ll give that a go. Cheers!
EDIT: Works just as you described. Appreciated!
Glad to help. To rename a cartridge tap on the Info icon to the right of the cartridge name.
Yeah, that i button > rename wasn't working for me on iOS 12 or 13. I'll see if following the previous steps changes that outcome. Ta.
Is there a way to change the names of each patch?
Yes - hold on to your hat. Choose the cartridge with the voice you want to rename and choose the voice. Tap on the name on the left just above the keyboard. It will open a window showing contents of the cart. Remember the current name and position of the voice so you don’t overwrite something else. Clear the voice name in the upper left. Make sure to clear it completely including any leading or following spaces. Type in the name you want. Tap Save. Tap on the position you want to save it to (most likely its original position). You should see the name you entered in that position. Click Done. Critical step next - Save the cartridge - cartridge with arrow pointing down icon. Make sure you keep track of which cartridge because it will deselect when you hit the Save icon. It’s really not too bad once you’ve done it a couple of times. The key is to follow the steps exactly and always Save The Cartridge. It will ask if you want to overwrite. Usually you’ll want to.
Woah, I never would have figured out the last steps. Thank you! Some of the coded names are cool, but I also like the name to hint at what the sound is...
Can anyone point to a simple tutorial or explanation of how to make up your own carts of voices using the tools in KQ Dixie? I’ve looked at the icons @SpookyZoo has screen grabbed above, but I’m afraid I don’t really understand how to use them. I have loads of distinctive voices scattered across multiple virtual carts and all I want to do is manually gather together the ones I like into my own new ‘greatest hit’ carts, or failing that, just shift all the good ones into one massive folder so I can ditch the million indifferent EP and bell patches clogging up all freebie cart collections I’ve scooped off the net. This generator website seems to have quite a high hit rate of actually useable keepers, but the problem of editing the good stuff out remains.
@Svetlovska, it's a pain in the butt, I have to say:
Repeat for every friggin' patch. Be very careful to follow each step in order.
There may be some more streamlined way, but I don't think so. Considering all the mind-blowing amazingness of the rest of the app, the patch and cart save mechanism is truly a head scratcher.