|
Post by surferdargile on Apr 28, 2021 19:33:54 GMT
Hello all ! I've started exploring my first AE rack , and I'm so glad with the encounter ! Great sounding and possibilites
After one hour of noodling, I came to the obvious question : I want to test another patch but this one is funny ... How can i remember how to set up my 35 jumper cables and knobs ? So i made an libroffice calc sheet adapted to my rack to make a patch storage system... Every module of my rack has its output listed , and you can select module destinations from here, then choose the input pin of the destination module... The lower rows helps to store switches and base knob position
here it is , if you want you or I can adapt it to your own rack by adding your module inputs and outputs and make more lists..
Bye bye
|
|
|
Post by keurslagerkurt on Apr 29, 2021 10:21:01 GMT
Very interesting! I remember when I started out, I also tried to write down my patches, but I was too lazy to keep doing it haha!
Also some of the modular magic for me personally, is starting from scratch without 'rebuilding' something. On the other hand, I remember making a kick some months ago that i LOVED, but I can't seem to quite recreate it anymore haha, should have written that one down..
|
|
|
Post by admin on Apr 29, 2021 11:06:22 GMT
|
|
|
Post by surferdargile on Apr 29, 2021 19:29:15 GMT
Thank you all !! I feel like the lonely guy who tried to reinvent the wheel
BUt anyway it was a good exercise to try manage it by myself before finding lot better ways to do this !
I agree a lot with you Kurt, that it is always better to start from scratch and record, but trying to understand where are the good combinations is also useful for a noob like me thinking about patch storage helps you a lot understanding the signal paths ... super aemodular, great instrument and community . EDIT : inputting the patch datas with text in a spreadsheet (as Carsten did) can be fast, also creating a visual feedback using patch pro, as seen on the "template" thread is very interesting, but you need to script every data ... Using lists in a spreadsheet can be faster (navigating with arrows keys, selecting in the list outputs and inputs, reorganizing your patch sheet as your rack... Wil try to stick on it ... At the end, what i understand is that you never "remake a patch" , it is way more fun to start something else . But Kurt will admit , if this KICK was great , it is cool to write it somewhere
|
|
|
Post by spacedog on Apr 30, 2021 8:45:04 GMT
From a personal point-of-view, making notes was more about recording how I did something, and the more I did that, the more I understood what it was that I was doing to arrive at the desired (or more usually, lucky) sound. Certainly, in the early days of the patch challenges there were requests for diagrams and I just drew mine by hand in a notebook and then scanned them - and that was certainly fun...!!! As the feedback loop between what I patched and how that patch sounded developed, I needed fewer diagrams as I was learning how to achieve a desired sound and I was learning how to create big chunks of a patch (e.g. sound generation, modulation, etc.). Rather like admin said, I would then play with/record that patch and then break it down, safe in the knowledge that I could probably work out how I achieved it, even if not exactly, and anyway I'd got what I wanted from it in terms of both learning and recording. There's an interesting point: I was learning how to translate what I heard in my head into what I could hear with my ears - or I could get close, with happy accidents thrown in. Along the way, I would discover new things that added to this knowledge. Gradually, my translation ability got better with practice - it's still not perfect and I'm still training it with exposure to ever more interesting modules via other routes, and matching ever more challenging sounds in my head. My point here is that keeping notes is perfectly good practice and we'll all find a level that works for us - and a method. For some, it can be like a lab book, with very detailed notes on the setup and outcomes, and for others it can be a few scant words as a memory jogger. I believe we all find a comfortable place on that continuum. So, wheels aren't being re-invented, never fear, it's just a case of following your own learning path and shaping the exact parameters of your personal version of that wheel (IMO, of course ).
|
|
|
Post by surferdargile on Apr 30, 2021 9:50:21 GMT
thanks spacedog for your input , also admin and all .. It is so true, noting patche as a way to learn, until you don't need it anymore ... every analog synth I had , i never need to note something ( exception to my Yamaha CS 30 that had so much routings and very precise reactions ) ..But with this AE Modular, the fact that you can always reinject a module in a module make it easier to forget;.. I think with time I'll will throw my spread sheet, but anyway it learned me a bit of Excel also We can also share some patches ( with the basic modules I have )
|
|
|
Post by spacedog on Apr 30, 2021 11:50:51 GMT
thanks spacedog for your input , also admin and all .. It is so true, noting patche as a way to learn, until you don't need it anymore ... every analog synth I had , i never need to note something ( exception to my Yamaha CS 30 that had so much routings and very precise reactions ) ..But with this AE Modular, the fact that you can always reinject a module in a module make it easier to forget;.. I think with time I'll will throw my spread sheet, but anyway it learned me a bit of Excel also We can also share some patches ( with the basic modules I have ) Ah well, the CS-30 is quite the beast You'll be fine with the AE Modular if you can understand the routing on that Yamaha...!!!
|
|
|
Post by williamv on May 1, 2021 1:14:07 GMT
i have found a good way to save patches. get a notebook and remove leads one by one and note it down . continue until you dont have any more leads .yes of course knob positions are not noted but at least you will not be far away from the original sound
|
|
|
Post by surferdargile on May 1, 2021 10:10:04 GMT
Yes also a good way ... But I try not to type anything, just using a kind of predefined virtual matrix on spreadsheet , like a virtual VCS3 noting system
|
|
pol
Wiki Editors
Posts: 1,349
|
Post by pol on May 1, 2021 19:49:25 GMT
Hello all ! I've started exploring my first AE rack , and I'm so glad with the encounter ! Great sounding and possibilites
After one hour of noodling, I came to the obvious question : I want to test another patch but this one is funny ... How can i remember how to set up my 35 jumper cables and knobs ? So i made an libroffice calc sheet adapted to my rack to make a patch storage system... Every module of my rack has its output listed , and you can select module destinations from here, then choose the input pin of the destination module... The lower rows helps to store switches and base knob position
here it is , if you want you or I can adapt it to your own rack by adding your module inputs and outputs and make more lists..
Bye bye
Thanks for thinking of sharing with the Forum, I tend to just take a photo but it isn't always clear where what goes to and from.... I only have 2 patches I've used in songs but as I get going I may well use your spreadsheet if patches get more complicated and I need to keep....
|
|
|
Post by surferdargile on May 1, 2021 20:52:52 GMT
Ah well, the CS-30 is quite the beast You'll be fine with the AE Modular if you can understand the routing on that Yamaha...!!! It's a very logical routing, and also very deep ! but reversed !! you select the source at the destination , when you get this you can patch it very quick and it's actually very clever =) Super synth, but I did'nt used it enough anymore, for lack of place ) family growing, had to let it go .. I sold it recently then jumped into Ae because nothing can't cure my synthesizer addiction
|
|
|
Post by surferdargile on May 1, 2021 20:58:13 GMT
Thanks for thinking of sharing with the Forum, I tend to just take a photo but it isn't always clear where what goes to and from.... I only have 2 patches I've used in songs but as I get going I may well use your spreadsheet if patches get more complicated and I need to keep....
You're welcome ... If you need to adapt it to your rack I can help (adding your specific modules input and output so they appear in the sheet, using correlated lists)
Just write here the input and outputs and modules name you need (avoid spaces and symbols) ... if you're already a libroffice patcher and know how to do it , then sorry If not i can update the document.
|
|
|
Post by stephen on May 17, 2021 20:09:20 GMT
I wrote in an older thread about my patchnotes systems. (Go check that thread out!) Whenever I create a patch, I also try to write it down. The goal is to create something in my patch notebook that is as beautiful as the music it represents.
|
|
|
Post by funbun on May 18, 2021 12:18:52 GMT
I tried saving patches in the beginning, but it is so tedious that it ran counter to how my brain works. For some each patch is an experiment; each has it's own life span. It's born, it lives, and it dies. Not to be too suggestive, but it doesn't take much to remember how to make babies, lol! The beauty of every patch is the life between the beginning and end.
If you spend enough time with the machine, you will learn what each module does. You'll develop an intuition about each input and output of every module without the need of a spreadsheet or diagram. Part of the philosophy of modular synthesis is that it is non-notatable. It isn't meant to be written down. It's based purely on the sound. That's something the Western world has a hard time excepting.
|
|
|
Post by MikMo on May 18, 2021 18:48:37 GMT
Actually i think storing patches is counterproductive when seen in a modular perspective. I sometimes rip all the patchcables of a good patch out knowing that i will probably never be able to make exactly the same patch again. But i do know that i learned something from the patch, and that i probably can make another patch (or sound) that derives from the good patch.
So as others have mentioned the lack of patch storage, banks, programs, slots is maybe the very soul of modular synthesis.
I stopped mourning the lost patch, and instead celebrate the next patch that does inherit from it's ancestors. Sounds a little cheesy, i know, but if we could store patches, less development would be seen.
I know people who have amazingly powerfull synths who have only ever played with the factory default sounds, because there are so many, and they sound so good.
|
|
|
Post by surferdargile on May 23, 2021 22:45:44 GMT
that"s true , better count on the next patch and let the previous go after an audio recording if it's worht recording it . I'm not searching to write presets banks "for live gigs" keyboards (that I use a lot)... but as a noob on the AE system, when i learn some particular modules, I find it's cool to note somewhere what did produce that "internal reaction" . the fact that I note it make it more easy to remember as a process. I only consulted my patches sheet only two or three times. It's the logic of noting, also reviewing and thinking about signal path that helps me to improve my understanding... at a certain skill on Ae modular (or other) , i'm sure i'll be evoluting towards this point of view.
|
|
|
Post by pt3r on May 24, 2021 8:13:10 GMT
Actually i think storing patches is counterproductive when seen in a modular perspective. I sometimes rip all the patchcables of a good patch out knowing that i will probably never be able to make exactly the same patch again. But i do know that i learned something from the patch, and that i probably can make another patch (or sound) that derives from the good patch. So as others have mentioned the lack of patch storage, banks, programs, slots is maybe the very soul of modular synthesis. I stopped mourning the lost patch, and instead celebrate the next patch that does inherit from it's ancestors. Sounds a little cheesy, i know, but if we could store patches, less development would be seen. I know people who have amazingly powerfull synths who have only ever played with the factory default sounds, because there are so many, and they sound so good. This.
|
|
|
Post by pt3r on May 24, 2021 8:20:07 GMT
that"s true , better count on the next patch and let the previous go after an audio recording if it's worht recording it . I'm not searching to write presets banks "for live gigs" keyboards (that I use a lot)... but as a noob on the AE system, when i learn some particular modules, I find it's cool to note somewhere what did produce that "internal reaction" . the fact that I note it make it more easy to remember as a process. I only consulted my patches sheet only two or three times. It's the logic of noting, also reviewing and thinking about signal path that helps me to improve my understanding... at a certain skill on Ae modular (or other) , i'm sure i'll be evoluting towards this point of view. Sometimes I also like keep note of some ideas that work really well and that I have not internalized in my musical muscle memory, whether its a cool patching trick or whether its some musical knowhow like which pentatonic scale is the most interesting to improvise over a major chord... The patchsheets, are In that train of thought, indeed a very useful musical tool in much the same way that muscial notation is useful; it allows you to remember more easily how to play a tune but it does not give you a guarantee to reproduce a tune exactly like you heard it before or played it before.
|
|