|
Post by asilvestrado on Sept 23, 2018 10:24:23 GMT
El sistema creado por Robert Langer requiere construir parches, y para trabajar con ellos.
Espero que os sirva.
Saludos.
The system created by Robert Langer requires to build Patches, and to work with them I have configured this template. I hope it serves you. Greetings.
ttps: //ruidoprocesado.blogspot.com/2018/09/ae-modular-template-patch.htmlAttachments:
|
|
gaeel
New Member
Posts: 22
|
Post by gaeel on Sept 23, 2018 21:24:51 GMT
|
|
|
Post by NightMachines on Sept 23, 2018 22:48:52 GMT
I wrote the ModularGrid people an email and posted on their forum, asking to include AE Modular on their site by the way. Hope they implement it! I really like ModularGrid esp coals because I can organize various formats (Euro, 5U, Serge, etc,).
|
|
|
Post by admin on Sept 23, 2018 22:54:42 GMT
I wrote the ModularGrid people an email and posted on their forum, asking to include AE Modular on their site by the way. Hope they implement it! I really like ModularGrid esp coals because I can organize various formats (Euro, 5U, Serge, etc,). I talked about this with Robert and he told me that he had approached them before and they declined because there aren't enough users of the format yet. But it seems that this is changing rapidly Maybe if we all write to them they will get an idea that there is a growing demand!
|
|
Lugia
Wiki Editors
Ridiculously busy...ish.
Posts: 556
|
Post by Lugia on Sept 23, 2018 23:23:38 GMT
Right...both Robert and I had pitched the notion to MG some months back, and we got much the same response at around the same time. Very disappointing and unconstructive, I thought. However, if the point is made that there are quite a few pinpatch devices in formats such as Eurorack already, plus a host of pinpatch instruments by other manufacturers, AND that AE now have their Eurorack 'carriers' ready (which make transitioning between formats a breeze) and a few other makers are playing with the format, maybe they'll respond more constructively this time out. This needs to happen. MG is regarded by much of the electronic music community as a 'standard reference' for modular hardware, and a lot of what happens in that scene revolves around what's listed in MG's databases. However, I can understand their being skeptical; they've gotten yanked around before, with one notable example being the promising-but-vaporware 'Geeklapeeno' Euro case system, which was heavily-touted when it popped up but which still continues to fail to materialize some years on. They did the programming to add that as a case format in the Eurorack database...and then, it never seems to have materialized, much to a lot of peoples' annoyance.
BTW, I still think the AE carrier Eurorack modules need to be listed in the Eurorack section on MG. Seriously. That'll be a sizable part of letting MG's admins know that this is a format that needs to be added, I feel.
|
|
|
Post by asilvestrado on Sept 29, 2018 10:21:07 GMT
Hi Gael, ok. when I create a patch, before I drew it, now I use this template. I modified the template to indicate the value of the knob
|
|
|
Post by asilvestrado on Sept 29, 2018 10:34:36 GMT
Template modified
|
|
|
Post by admin on Oct 2, 2018 22:05:45 GMT
Hello asilvestrado I really like your idea of the template. Have you used it yet to record one of your patches? Would you mind sharing an example with us?
|
|
|
Post by thetechnobear on Oct 3, 2018 13:08:41 GMT
hmm, this is a great idea.... Ive a random thought though, so everyone has different modules, and everyone will (potentially) lay them out in a different way so my idea is quite simple. what if we just had a copy of each of the modules as an image. then you could drop these into your 'favourite' graphics program, and then create the lines with the drawing tool. what i would tend to avoid is trying to replicate the actual rack layout, rather just place modules, so that its clear... avoid cramming things together, and also it can place emphasis on important (to the patch working) modules/module groups. something like this : ok, this is badly drawn (i just grabbed the first image editor I had (pages) which is not really suitable) the reason to not use a rack layout, is i think you can make it clearer, since you can position as you see git. to do this 'ideally' I think what we would need is a) some good quality module images, preferable with the dial indicator erased (so we could draw out own positions) b) work out a free/cheap editor for each OS, that makes this quick and easy to do. of course the drawback with this process, is you cannot just print it on a piece paper and scribble on it, which is really useful! ... but I guess im kind of more interested in the sharing side, which tends to be digital. I half remember there was another project, which I think was distinct from Eurorack, where they are discussing how to 'document patches', anyone remember this... or shall i dig it up? I suspect it was either on muffs or lines, but would need to dig it up.. it was a small project, so perhaps they might be interested in AEM. (note: this is distinct from ModularGrid which is documenting setups/racks)
|
|
|
Post by admin on Oct 7, 2018 2:55:42 GMT
So I also did some googling and found this thread on Muffwiggler. That sent me over to this video which uses a very minimalistic block diagram to describe the patch: I also thought that a more functional diagramming technique would maybe look like this: I used the fantastic, free, web based diagramming app draw.io for this.
|
|
|
Post by admin on Oct 7, 2018 3:06:45 GMT
Also very interesting is this project Patchbook which strives to create a parseable pseudo code patch description language which can be used to generate diagrams. For example this code: VOICE 1:
- Metropolis (Pitch) p> Aether VCO (CV) - Metropolis (Gate) g> Maths (Ch 1 Trigger) - Metropolis (Gate) g> Maths (Ch 4 Trigger) * Aether VCO: LFO Freq = 5 | LFO PWM = 7 - Aether VCO (Pulse) -> Mixer (Ch1) - Aether VCO (Sub 1) -> Tides (Clk) - Tides (Bi) -> Mixer (Ch2) - Aether VCO (Sub 2) -> Z3000 (HSync) - Z3000 (Saw) -> Mixer (Ch3) - MultiLFO (LFO 1) >> Tides (Smoothness) - MultiLFO (LFO 2 Triangle) >> Tides (Shape) - MultiLFO (LFO 3 Triangle) >> Z3000 (PWM) * MultiLFO: | LFO 1 Freq = 3.8 | LFO 1 Shape = Sine | LFO 1 S&H = 0 | LFO 2 Freq = 1 | LFO 3 Freq = 1 * Tides: PLL Mode = True | Freq = 60% | Smoothness = 70% * Z3000: Freq = 1pm - Maths (Ch 1) >> Multifilter (CV) - Maths (Ch 4) >> uVCA (Ch1 CV) - Mixer (Output) -> Multifilter (Input) - Multifilter (LPF) -> uVCA (Ch1 Input) - uVCA (Ch1 Output) -> AUDIO INTERFACE (In 3)
generates this image:
|
|
|
Post by thetechnobear on Oct 7, 2018 13:58:32 GMT
patchbook... thats the one i was thinking of its cool, because iirc, it has no concept of the format or modules, so we could easily use it for AEM. also honestly, I think, once you get the hang of the text format, its actually quicker to scribble down than drawing graphs
|
|
pol
Wiki Editors
Posts: 1,277
|
Post by pol on Oct 25, 2018 20:48:56 GMT
I like the template idea as I currently take a photo of a patch I particularly like, but it doesn't show the connections very well, works fine for non-modular synths and mixers....
|
|
|
Post by mobius on Oct 26, 2018 2:22:42 GMT
Personally I prefer a text/module independent based format, since modules and arrangements will vary greatly in the modular world.
When I've jotted down patches, it's been closer to the Patchbook format. May not be as easy to look at first glance and figure out what's going on, but I find it easier to recreate something if I can go line by line making the various connections and setting knobs to the denoted values.
But then again that's me reading my own notes, so... for what it's worth at its utmost.
|
|
|
Post by ecleinjr on Oct 26, 2018 20:01:07 GMT
patchbook... thats the one i was thinking of its cool, because iirc, it has no concept of the format or modules, so we could easily use it for AEM. also honestly, I think, once you get the hang of the text format, its actually quicker to scribble down than drawing graphs I totally agree. I think the text format is great and I can see myself getting a hang of it really quickly. I've always strayed away from visually representing patches because it takes forever to get graphics the way I want them to look. Downloading patchbook right now...
|
|
|
Post by thetechnobear on Oct 26, 2018 20:27:02 GMT
Downloading patchbook right now... let us know how you get on, Ive been meaning to try it for ages, but never got around to it...
|
|
|
Post by thetechnobear on Nov 29, 2018 17:25:38 GMT
Ive been playing with Patchbook (on and off) for a while now, and Im really getting to like it a couple of tips, a) you dont need to download or install it ,there is an online version patchbook-converter.herokuapp.com/what I do is create my 'patch' in a normal text editor, and then paste it into this, submit it, then you copy and paste the result into dreampuf.github.io/GraphvizOnline/b) Graphviz if you select png image , then you can right click and save it . c) AE modular Graphviz/patchbook does not like having modules names beginning with numbers! so 2OSC, 4ATT/MIX all cause grief - so Ive started putting AE_ in front of them similarly, special characters can cause issues, so 4ATT/MIX wont work, so I just get rid of them also a module has to have a 'unique' name, so if you have multiple LFOs in your patch, you'll want to number so put together I might have an example like - AE_2OSC_1 (sq2) >> AE_2OSC_1(sync) - AE_2OSC_1 (sq1) >> AE_2VCA_1(in1) - AE_2OSC_1 (buscv) p> AE_2OSC_1(cv1) - AE_ENV_1 (out) >> AE_2VCA_1(cv1) - AE_ENV_1 (busgate) g> AE_ENV_1(gt1) - AE_2VCA_1 (out1) -> AE_4IO_1(in1) - AE_4IO_1(mix) -> AE_MASTERIO(audio1)
* AE_2OSC_1: | freq_1 = 25% | freq_2 = 35% | pw = 50%
* AE_2VCA_1: | cv1 = 100%
* AE_ENV_1: | attack = 0% | decay = 10% | shape = AD | speed = fast
* AE_4IO_1: | level1 = 100% | mix1 = on
produces (oops noticed I should have had the oscillator outputs into VCA as audio, oh well ) general impression once you get over the few oddities (like naming, making sure there is a space before = ) , its really quick to type, and because there is no 'completeness' checking, you can easily just document the essence of a patch , (we could make it quicker for ourselves by saving the 'module' attributes definition (the second part, with *) ) I think its definitely quicker to use this than say drawing in a graphics program, and because there is so little 'syntax' its pretty quick to learn. perhaps the limitation is if the patch got really big, it'd probably get quite wide, but perhaps not, would need to play some more to see
|
|
bert
Junior Member
Posts: 54
|
Post by bert on Dec 28, 2018 22:58:39 GMT
Hi!
I was also looking for a way to save my patches, and saw that some of you liked Patchbook so I tried it out. I like the idea of writing patches in a text format. However I think the graphical rendering is not so great. For me personally I think it would be easier to look at a patch and to recreate it if the rendering was more realistic. So I decided to make some modifications to the script that greatly improve the looks of AE modules.
You can find my modifications here: github.com/bertfrees/PatchbookBelow is an example patch: VOICE 1: * AE_vco: | modtype = PW | moddepth = 320° | coarse = 135° | fine = 250° | pulsewidth = 40°
* AE_noise: | rate = 40° * AE_lfo 1: | timerange = FAST | shape = SAW | rate = 240° | pulsewidth = 40° * AE_lfo 2: | timerange = SLOW | shape = TRIANGLE | rate = 120° | pulsewidth = 40° * AE_filter 1: | freq = 200° | cv1 = 320° | resonance = 240° * AE_filter 2: | freq = 150° | cv1 = 310° | resonance = 150°
* AE_env 1: | sustain = FULL | timerange = FAST | attack = 85° | decay = 130° * AE_env 2: | sustain = FULL | timerange = FAST | attack = 85° | decay = 155° * AE_mixer44: | levela1 = 180° | levela2 = 220°
* AE_wavefolder: | drive = 320° | shapecv = 320° | shape = 180°
* AE_delay: | delaytime = 215° | feedback = 190° | drywet = 280° - AE_lfo 2 (triangle) >> AE_wavefolder (cvshp) - AE_env 1 (out) >> AE_filter 1 (cv2) - AE_env 2 (out) >> AE_vco (mod) - AE_env 2 (out) >> AE_filter 2 (cv2) - AE_divider (÷8) >> AE_delay (cv) - AE_lfo 1 (pulse) c> AE_divider (clk) - AE_divider (÷4) g> AE_2sh (in1) - AE_divider (÷32) g> AE_env 2 (gt1) - AE_2sh (out1) g> AE_env 1 (gt1) - AE_noise (crout) t> AE_2sh (trig1) - AE_vco (saw) -> AE_wavefolder (in) - AE_vco (triangle) -> AE_wavefolder (in) - AE_vco (square) -> AE_filter 1 (in) - AE_filter 1 (lp) -> AE_delay (in) - AE_wavefolder (out) -> AE_filter 2 (in) - AE_filter 2 (lp) -> AE_mixer44 (a1) - AE_delay (out) -> AE_mixer44 (a2) This is the result:
Note that the names of the modules, inputs, outputs and parameters need to be exactly as in the example. If an unknown module is encountered, the tool falls back to the generic rendering. I have only added the modules that I have used in this example, but it is not hard to add more.
To try it out yourself you need Python 3, ImageMagick and Graphviz. I noticed that when converting to SVG the cable connections are slightly off, so it's best to convert to PNG.
|
|
|
Post by admin on Dec 29, 2018 1:05:49 GMT
Hi! I was also looking for a way to save my patches, and saw that some of you liked Patchbook so I tried it out. I like the idea of writing patches in a text format. However I think the graphical rendering is not so great. For me personally I think it would be easier to look at a patch and to recreate it if the rendering was more realistic. So I decided to make some modifications to the script that greatly improve the looks of AE modules. Hello bert, this is just absolutely amazing! It seems this only works on Linux or OSX?
|
|
bert
Junior Member
Posts: 54
|
Post by bert on Dec 29, 2018 12:31:06 GMT
Thank you :-) Oh, right. I didn't think about testing it on Windows. However in theory it should work, if ImageMagick is installed, and the "%PATH%" environment variable contains the directory that contains ImageMagick's "convert.exe" program.
By the way I saw your PM. I will reply tonight.
|
|
bert
Junior Member
Posts: 54
|
Post by bert on Jan 1, 2019 20:42:49 GMT
|
|
|
Post by sycophante on Mar 13, 2019 12:59:30 GMT
Patch symbols and patch editor are now available on their website : patchandtweak.com/Good way to share or ideas here, and there are even some ideas already shared in the patch editor!
|
|
Lugia
Wiki Editors
Ridiculously busy...ish.
Posts: 556
|
Post by Lugia on Mar 15, 2019 20:56:06 GMT
This is smart...the use of the symbols reminds me to a great extent of what Beaver & Krause outlined on "The Nonesuch Guide..." but this implementation makes more sense.
|
|
|
Post by admin on Nov 7, 2019 0:22:53 GMT
|
|
anton
New Member
Posts: 29
|
Post by anton on Nov 7, 2019 10:30:12 GMT
|
|