|
Post by spacedog on Aug 26, 2019 15:11:26 GMT
Reading the recent thread on video tutorials made me think...
I'm old school, I imagine, as I like to read about things rather than watch videos OK, that doesn't mean that I don't like videos, it's more that I can derive a lot from a well-written manual as well as watching a video. I'd been thinking about this and I know that many people have commented on working out how a module works and this seems to happen by a combination of existing knowledge and trial-and-error testing. Luckily, errors don't seem to have summoned forth the magic smoke for anyone yet - with only +5V to play with, we're a bit more constrained in that department. We have a lot of knowledge floating around in this forum, and in the heads of users, some documented (albeit in various threads) and some not, so I thought that we could could do some crowd sourcing for module documentation. Take a module every week (or month, if there's little take-up) and just post what we know about it. Then we pull it together into a standard format (picture, intended use, inputs, outputs, controls, etc.) and upload it. Stick a version number on it and control changes and we have the start of the full manual - plus it takes the burden away from Robert and allows him to get on with the more interesting things, including looking after himself. Robert can agree them and then put them on the Tangible Waves website, if he wants. Say what you think here...?
If there's interest (that's code for " I'm not doing this on my own" ), then we can work something up within the group. Rather like the Patch Challenges, it would be nice if someone different takes the reins, this time for each module.
|
|
|
Post by moruial on Aug 26, 2019 16:36:56 GMT
It's a very good idea indeed. I'm in if my very little knowledge can be of any help.
On the topic of video, as a non native english speaker, I find it a bit more easy to understand sometimes as I can see what's going on and hear at the same time.
|
|
|
Post by Gaëtan on Aug 26, 2019 19:15:20 GMT
We are indeed in great need of written documentation. I think a wiki would work quite well.
|
|
pol
Wiki Editors
Posts: 1,349
|
Post by pol on Aug 26, 2019 19:16:29 GMT
I could certainly assist with this, although I can't go deep into the electrical design I have taught subtractive synthesis to a lot of people over the years... I assume this would be intend to complement the AE Modular technical guide? It covers all the basics but doesn't really delve into each module. forum.aemodular.com/thread/93/ae-modular-technical-guide
|
|
Lugia
Wiki Editors
Ridiculously busy...ish.
Posts: 556
|
Post by Lugia on Aug 26, 2019 22:01:06 GMT
Well, I've actually taught aspects of electronic music and studio production back during my undergrad studies. Was a while ago, but you don't exactly forget how the basics of edjamacation get done...
|
|
bahm
Full Member
Posts: 154
|
Post by bahm on Aug 26, 2019 22:12:12 GMT
I think explaining what a module and it's connections and knobs do shouldn't be too hard for most poeple here. A wiki would be really cool and we could include videos and or audio examples.
|
|
|
Post by admin on Aug 26, 2019 23:30:39 GMT
I think the wiki is a great idea. I have flagged this with Robert and will see if we can set this up as a semi-official site, like the grid. I think it would be good to have some control over who has editorial access so it doesn't get flooded with spam, but I'm happy to administrate this.
We already have a body of written documentation in Google Docs format, Robert and I are just too slow to finalise this.
|
|
|
Post by rockysmalls on Aug 27, 2019 11:21:46 GMT
Reading the recent thread on video tutorials made me think...
I'm old school, I imagine, as I like to read about things rather than watch videos OK, that doesn't mean that I don't like videos, it's more that I can derive a lot from a well-written manual as well as watching a video. I'd been thinking about this and I know that many people have commented on working out how a module works and this seems to happen by a combination of existing knowledge and trial-and-error testing. Luckily, errors don't seem to have summoned forth the magic smoke for anyone yet - with only +5V to play with, we're a bit more constrained in that department. We have a lot of knowledge floating around in this forum, and in the heads of users, some documented (albeit in various threads) and some not, so I thought that we could could do some crowd sourcing for module documentation. Take a module every week (or month, if there's little take-up) and just post what we know about it. Then we pull it together into a standard format (picture, intended use, inputs, outputs, controls, etc.) and upload it. Stick a version number on it and control changes and we have the start of the full manual - plus it takes the burden away from Robert and allows him to get on with the more interesting things, including looking after himself. Robert can agree them and then put them on the Tangible Waves website, if he wants. Say what you think here...?
If there's interest (that's code for " I'm not doing this on my own" ), then we can work something up within the group. Rather like the Patch Challenges, it would be nice if someone different takes the reins, this time for each module. definitely! I originally was tasked with english ‘proof reading’ the guide and manual for Robert.. it’s been a couple of years now ( where did that time all go!! ) and the manual is needed even more now with so many new modules.. I think to some extent the modules are self explanatory to those with some synthesis experience BUT the main thing is all the quirks and specific ‘hidden’ or not entirely obvious functions of specific modules. plus the different generations of ones that have been updated.. To this end I had started a “makeshift manual” to keep notes on useful info for each module as and when such info came to light ( usually in conversation with robert or from others questions in threads on this forum.. just looked at it and I’ve only done 3 modules!! so that’s not very useful of me... But.. I if i can contribute to this idea in some way then I will make every effort.. at least on the modules i actually have available to me.. maybe.. as you say, like the challenges.. just start a thread for each soecific module and people can pitch in with their findings/experiences.. then its just a cut and paste collation job and add in the .png of the module front panel..
|
|
|
Post by spacedog on Aug 27, 2019 11:53:46 GMT
[...] maybe.. as you say, like the challenges.. just start a thread for each soecific module and people can pitch in with their findings/experiences.. then its just a cut and paste collation job and add in the .png of the module front panel.. Yes, rockysmalls, that was what I had in mind, but I am open to people starting a wiki. Whatever gets the job done.
|
|
|
Post by Gaëtan on Aug 27, 2019 12:10:37 GMT
I think they are complementary. A wiki is great for archival and summarizing information (it would even be easy enough to generate a PDF from it), but a forum is better for asking questions. The forum will fuel the wiki's content.
Now that I think of it, weird that there is no real modular synth wiki, especially for Eurorack. Seems like the kind of thing that would be very useful considering the amount of manufacturers, differences in implementation, and general lack of documentation.
|
|
|
Post by admin on Aug 28, 2019 23:24:14 GMT
Hi all,
Just a quick heads up. Robert has approved the wiki idea and I'm in the process of setting this up with a basic structure over the weekend.
I wouldn't make it completely open for anyone to edit but would rather like to invite a few dedicated editors. Please PM me if you're interested to participate.
|
|
|
Post by rodney on Aug 29, 2019 2:19:40 GMT
I'm definitely up for it.
Wikis are great and organic. I do like a printed manual though.
Maybe a set of tutorials to bring an absolute synth beginner along , covering basic acoustics etc. then into the depths of DIY.
anyways, will think some more...
|
|
|
Post by spacedog on Oct 10, 2019 9:14:54 GMT
Hi all, Just a quick heads up. Robert has approved the wiki idea and I'm in the process of setting this up with a basic structure over the weekend. I wouldn't make it completely open for anyone to edit but would rather like to invite a few dedicated editors. Please PM me if you're interested to participate. Did this ever get any traction...? With apologies, I admit that I missed the "sign up" via PM.
|
|
|
Post by admin on Oct 10, 2019 9:34:17 GMT
Hi all, Just a quick heads up. Robert has approved the wiki idea and I'm in the process of setting this up with a basic structure over the weekend. I wouldn't make it completely open for anyone to edit but would rather like to invite a few dedicated editors. Please PM me if you're interested to participate. Did this ever get any traction...? With apologies, I admit that I missed the "sign up" via PM. YES! I have been busy preparing a Wiki and will unveil it over the weekend and I'm also still seeking for editors, but more on that soon.
|
|
|
Post by sycophante on Oct 10, 2019 14:14:39 GMT
I'm definitely up for it.
Wikis are great and organic. I do like a printed manual though.
Maybe a set of tutorials to bring an absolute synth beginner along , covering basic acoustics etc. then into the depths of DIY.
anyways, will think some more...
I thought of this too! Most synthesizers manuals have cool patch ideas : I think it would be cool too look into general modular synthesis theory, or other synths manuals, and transcribe them as technics directly appliable to AEM with schematics and list of needed modules (some ideas could be, use VCAs to make stereo sound and modulation, make AM with AEM, creative way to use beat divider, multidivider or 3vcswitch, maybe some ideas on interracting with eurorack and/or other famous patchwire synth, and so on) + of course diving into DIY. Don't now if this fit into a wiki though...
|
|
|
Post by rockysmalls on Oct 10, 2019 16:03:27 GMT
Did this ever get any traction...? With apologies, I admit that I missed the "sign up" via PM. YES! I have been busy preparing a Wiki and will unveil it over the weekend and I'm also still seeking for editors, but more on that soon. i noticed some of the more esoteric modules now have pdf’s linked in their TW page descriptions is that yr doing Carsten ? or Robert & you?
|
|
|
Post by admin on Oct 10, 2019 22:20:10 GMT
Most synthesizers manuals have cool patch ideas : I think it would be cool too look into general modular synthesis theory, or other synths manuals, and transcribe them as technics directly appliable to AEM with schematics and list of needed modules (some ideas could be, use VCAs to make stereo sound and modulation, make AM with AEM, creative way to use beat divider, multidivider or 3vcswitch, maybe some ideas on interracting with eurorack and/or other famous patchwire synth, and so on) + of course diving into DIY. Don't now if this fit into a wiki though... The wiki would be the perfect place for this! In fact I have set up a few (empty) pages for this kind of thing that just need someone to fill them with content Again ... I will release more information about this project over the weekend, but I'm very happy that some of you seem to be keen to chip in! A wiki is really just a more structured, more permanent extension of the forum and it lives from input from the community!
|
|
|
Post by robertlanger on Oct 11, 2019 8:29:12 GMT
YES! I have been busy preparing a Wiki and will unveil it over the weekend and I'm also still seeking for editors, but more on that soon. i noticed some of the more esoteric modules now have pdf’s linked in their TW page descriptions is that yr doing Carsten ? or Robert & you? For a few modules I managed to write a user guide like SEQ16, and all the time I was thinking "I must complete the manuals"; but, sorry, I simply found absolutely no free time for it :-( So I'm super happy about the upcoming wiki - thanks Carsten for your work and time! Of course I will contribute my part by checking and writing this and that.
|
|
|
Post by admin on Oct 12, 2019 10:17:41 GMT
|
|