|
|
Post by spacedog on Dec 17, 2019 19:26:27 GMT
I still remember reading the excellent Beginner's Guide to Coding ByteBeats by NightMachines a while ago, I even played around quite a bit using the online coders (in fact, I'm playing with one again right now  ). If you haven't read it, do have a look, then you'll probably want an ALGODRONE, if you don't already. The module notes on the Tangible Waves page state that, " The ALGODRONE module contains a number of these algorithms plus three parameter knobs that change values within the current algorithm." So, I do have three quick questions: - How many algorithms are on board;
- Are they tweakable blueprints; and
- Can user-created algorithm blueprints be entered into the module (and then tweaked)...?
It's great fun creating and tweaking these digital sounds... here's the formula for one I adapted (i.e. most of the work was by someone else): (t>>8&t)*(t>>10&t) and you can hear it here. A lot of the fun is in the creation and experimentation, hence my questions. I can see how you could set up some basic blueprints and then tweak parameters within them - it's just knowing the blueprints on board. Apologies if it's obvious. Here's another interesting one: (sin(t/10+sin(t*Math.pow(2,t>>10))))*64+128 (again robbed from someone else's hard work and a bit more complex) and the player I linked lets you save to a wav file, so you can manipulate it... try entering that one yourself and have a play. |
|
ben
Full Member
Posts: 123
|
Post by ben on Dec 17, 2019 20:20:09 GMT
(I understand nothing but just had some fun playing on a web link and adjusting the values, thanks!)  |
|
|
|
Post by admin on Dec 17, 2019 21:41:21 GMT
Hi spacedog, the algorithms are fixed and I don't quite know how many there are. There is no facility for uploading your own. However the new GRAINS module is based on Arduino Nano and has a front facing micro USB port for uploading your own programs ... so potentially you could use that module for bytebeat experiments. |
|
|
|
Post by spacedog on Dec 17, 2019 22:26:10 GMT
Hi spacedog , the algorithms are fixed and I don't quite know how many there are. There is no facility for uploading your own. However the new GRAINS module is based on Arduino Nano and has a front facing micro USB port for uploading your own programs ... so potentially you could use that module for bytebeat experiments. Thanks, admin, it looks like an interesting module, as does GRAINS. I look forward to hearing what people do with them. |
|
|
|
Post by loopier on Dec 18, 2019 9:39:07 GMT
Hadn't heard of ByteBeats before (pardon my ignorance  ). It would be very interesting to have this at control rate to generate random (or algorithmic) melody loops, but since the module is mostly oriented to audio rate, do you think this could be achieved patching it through a sample & hold? Would that generate pseudo-looped melodies?
|
|
|
|
Post by rodney on Jan 3, 2020 19:50:36 GMT
(I understand nothing but just had some fun playing on a web link and adjusting the values, thanks!) what I love about bytebeat is that it is like circuit-bending with numbers. Even people who understand how it works can't really predict what a major change in the expression will do. |
|
|
|
Post by NightMachines on Jan 4, 2020 18:31:57 GMT
Hadn't heard of ByteBeats before (pardon my ignorance ). It would be very interesting to have this at control rate to generate random (or algorithmic) melody loops, but since the module is mostly oriented to audio rate, do you think this could be achieved patching it through a sample & hold? Would that generate pseudo-looped melodies?
If I remember correctly from Superbooth, you can pitch down the module for slower waveforms. From playing with the prototype there, it can definite act very well as a CV source. |
|
|
|
Post by loopier on Jan 5, 2020 8:27:19 GMT
If I remember correctly from Superbooth, you can pitch down the module for slower waveforms. From playing with the prototype there, it can definite act very well as a CV source. Grand! This is definitely good news. I ordered it a couple of weeks ago. : ) |
|
|
|
Post by rodney on Jan 6, 2020 5:05:55 GMT
Partly an excuse to blow my own trumpet but I think that it would be cool to be able to link up fragments of expression into larger ones, a bit like I do with this augmented reality bytebeat synth I build many moons ago. In this example, each block holds a string that works on its own. when these get used together with another, a vertical pipe character ' | ' is added to separate them. It's a bit like multi-tracking but each track messes with the others in some way.
The Bastl/Casper Bitranger goes a long way down this path. Of course, Felix gives us a great taste of what that can sound like!
|
|
|
|
Post by admin on Feb 13, 2020 10:47:32 GMT
...I do have three quick questions: - How many algorithms are on board;
- Are they tweakable blueprints; and
- Can user-created algorithm blueprints be entered into the module (and then tweaked)...?
Now that I actually have one of them I can answer those questions: 1. There are 67 are factory presets, but there is a random generator that can create random algorithms which can be stored in 30 user assignable slots. 2. The randomise button assembles a random algorithm, which can be slightly mutated any number of times and then stored into one of the user slots. 3. No, see above. I have made a good start on the documentation of the module on the Wiki: wiki.aemodular.com/pmwiki.php/AeManual/ALGODRONE |
|
|
|
Post by spacedog on Feb 14, 2020 10:50:50 GMT
...I do have three quick questions: - How many algorithms are on board;
- Are they tweakable blueprints; and
- Can user-created algorithm blueprints be entered into the module (and then tweaked)...?
Now that I actually have one of them I can answer those questions: 1. There are 67 are factory presets, but there is a random generator that can create random algorithms which can be stored in 30 user assignable slots. 2. The randomise button assembles a random algorithm, which can be slightly mutated any number of times and then stored into one of the user slots. 3. No, see above. I have made a good start on the documentation of the module on the Wiki: wiki.aemodular.com/pmwiki.php/AeManual/ALGODRONEThanks, admin , much appreciated, I also see from another post that you've now finished the wiki entry and robertlanger has cast his eye over it. Most interesting, although, of course, there's always that part of me that wants to understand a bit more about what's going on inside the module - not to the extent that I could build one, more as I'm really interested in how algorithms were selected/created, how the parameters for tweaking were selected, etc. I wonder if we could get a small piece on the development of this module...? A slight insight into the design process - how it started, how it developed, etc. I, for one, would love to have more of a insight into how modules are developed, and this could be an interesting one. I understand that Robert is busy, so maybe even something wider as an interview piece would be interesting. I know that I enjoyed the last one that you did - I learned a few things On a more basic level, whilst the wiki is fantastic (and a huge well done to all involved), it feels a bit like you're reverse engineering how the modules work. OK, that's fun, and a great way to learn, of course. There's a part of me (the same part as is interested in the development) that would love to see a very simple "cheat sheet" issued with each module, or even on the module description page. I still remember when someone discovered the undocumented point about the step repeats on the TRIQ164 - I had tried for a while and never got them working. Sometimes trial and error leads to frustration especially for newcomers. OK, it's on the wiki page now, and so is now documented, so these things are being captured. I'm not close to the work on the wiki, so I may be out of touch, but I wonder if we could stimulate more exploration (and hence documentation) by having a "Module of the Week" discussion, rather like the Patch Challenges...? This is similar to something that I mentioned a while ago and the wiki became the capture method. I would be happy to kick something off - and it would possiblly provide patch examples as well as exploration notes. As with all of these things, it can always be there and can also be a feed into the wiki itself. I'm asking, rather than just doing (my usual method), as I don't want to tread on the toes of the wiki, and also if there is zero interest it would simply be a vanity project. Just thinking out loud really. I love to explore as much as anyone, although a torn scrap from the corner of the map is sometimes useful, as is an understanding of the mapmaker's thoughts |
|
|
|
Post by NightMachines on Feb 14, 2020 11:28:28 GMT
A “Module of the Month” subforum or thread is a great idea spacedog! I think proper manuals, which ship with the modules, are in the process of being created. At least there was some discussion about that some time ago. ... and just out of curiosity, I’d also like to know a bit more about the ALGODRONE‘s stock algorithms, the random creation of new ones and their parameters. |
|
|
|
Post by NightMachines on Feb 14, 2020 11:36:02 GMT
Regarding admin’s wiki entry, I added “CV source” to the beginning as well. If I remember correctly, the module outputs unipolar DC signals, not “audio” signals, centered around +2.5V. So it’s great as a CV modulation source too and can be processed further as such. |
|
|
|
Post by admin on Feb 18, 2020 8:56:04 GMT
On a more basic level, whilst the wiki is fantastic (and a huge well done to all involved), it feels a bit like you're reverse engineering how the modules work. OK, that's fun, and a great way to learn, of course. There's a part of me (the same part as is interested in the development) that would love to see a very simple "cheat sheet" issued with each module, or even on the module description page. I still remember when someone discovered the undocumented point about the step repeats on the TRIQ164 - I had tried for a while and never got them working. Sometimes trial and error leads to frustration especially for newcomers. OK, it's on the wiki page now, and so is now documented, so these things are being captured. I'm not close to the work on the wiki, so I may be out of touch, but I wonder if we could stimulate more exploration (and hence documentation) by having a "Module of the Week" discussion, rather like the Patch Challenges...? This is similar to something that I mentioned a while ago and the wiki became the capture method. I would be happy to kick something off - and it would possiblly provide patch examples as well as exploration notes. As with all of these things, it can always be there and can also be a feed into the wiki itself. I'm asking, rather than just doing (my usual method), as I don't want to tread on the toes of the wiki, and also if there is zero interest it would simply be a vanity project. Hello spacedog, thank you again for your thoughts. There's a lot to process so I has taken me a while to find the time to answer. First off ... yes in the absence of an "official" documentation there is a bit of reverse engineering involved in writing these wiki pages, however Robert is always across the editorial process and lets us know when we write untrue things and helps when we can't figure things out ourselves. You can see the process of the wiki in this publicly accessible Trello board (it is also linked to from every documentation page on the Wiki) trello.com/b/HNd0dBt7/ae-manualsAnyone is invited to participate in the shaping of the wiki and I'm really glad for the work that a few have put in so far. There are still so many blank areas though so either a concerted effort or more people that want to get involved will be required to fill those in a timely manner. Otherwise it will still be done, in time, by me and a few people here and there. There's no rush, everyone is doing this in their free time. I love the idea of "Module of the week" and there is definitely space on the documentation page for each module to add more patch ideas and more videos to showcase the uses of each module. It could even be another patch challenge so we use that format "Make a track which shows an interesting use of module x". If you could kick this off, I would then be happy to collect all responses and put them in the wiki in the appropriate places. And again, don't fear of treading onto anyone's toes .. the forum and the wiki are there for you - the community - to shape. Yes, I am somewhat guiding this, but both assets are only as lively as how the members that are adding content and ideas. |
|
|
|
Post by spacedog on Feb 18, 2020 11:52:13 GMT
[...] I'm not close to the work on the wiki, so I may be out of touch, but I wonder if we could stimulate more exploration (and hence documentation) by having a "Module of the Week" discussion, rather like the Patch Challenges...? This is similar to something that I mentioned a while ago and the wiki became the capture method. I would be happy to kick something off - and it would possiblly provide patch examples as well as exploration notes. As with all of these things, it can always be there and can also be a feed into the wiki itself. I'm asking, rather than just doing (my usual method), as I don't want to tread on the toes of the wiki, and also if there is zero interest it would simply be a vanity project. Hello spacedog , thank you again for your thoughts. There's a lot to process so I has taken me a while to find the time to answer. [...] I love the idea of "Module of the week" and there is definitely space on the documentation page for each module to add more patch ideas and more videos to showcase the uses of each module. It could even be another patch challenge so we use that format "Make a track which shows an interesting use of module x". If you could kick this off, I would then be happy to collect all responses and put them in the wiki in the appropriate places. [...] Thanks for the considered reply, admin . I really shouldn't type whilst I'm drinking coffee I'll do something within the Patch Challenge (a "Module of the Moment", perhaps, so we're not tied to any frequency). Watch that space... and I really don't mind if someone else wants to start if I'm a bit slow. |
|
|
|
Post by NightMachines on Feb 25, 2020 13:20:58 GMT
Alrighty, here's my new demo/overview video of the ALGODRONE
|
|
|
|
Post by rodney on Feb 26, 2020 2:26:22 GMT
thanks Felix! great explanation. This will test my willpower desperately.
|
|
|
|
Post by admin on Feb 26, 2020 10:30:35 GMT
This is a great tutorial. Short and to the point with all necessary information. Thank you for beating me to it! |
|
|
|
Post by NightMachines on Feb 26, 2020 11:29:20 GMT
thanks Felix! great explanation. This will test my willpower desperately. Thanks! I need to look further into the random generation. I feel as if there are some real gems hiding in there. Got a lot of rhythmic pulse bytebeats recently, This is a great tutorial. Short and to the point with all necessary information. Thank you for beating me to it! Thanks to you as well! The more videos the merrier. Looking forward to see and hear how you use your ALGODRONE |
|
|
|
Post by rodney on Mar 3, 2020 0:05:03 GMT
the missing bytebeat algorithm:
(t<<3)*[8/9,1,9/8,6/5,4/3,3/2,0][[0xd2d2c8,0xce4088,0xca32c8,0x8e4009][t>>14&3]>>(0x3dbe4688>>((t>>10&15)>9?18:t>>10&15)*3&7)*3&7]
(not my original but someone had to put it here - a conceptual landmine for some brave soul...) |
|
|
|
Post by rodney on Mar 3, 2020 0:08:45 GMT
|
|
|
|
Post by rodney on May 7, 2020 6:39:58 GMT
the missing bytebeat algorithm:
(t<<3)*[8/9,1,9/8,6/5,4/3,3/2,0][[0xd2d2c8,0xce4088,0xca32c8,0x8e4009][t>>14&3]>>(0x3dbe4688>>((t>>10&15)>9?18:t>>10&15)*3&7)*3&7]
(not my original but someone had to put it here - a conceptual landmine for some brave soul...) Oh, come on! didn't anyone try that bytebeat string out? greggman.com/downloads/examples/html5bytebeat/html5bytebeat.html#t=0&e=0&s=8000&bb=5d00000100830000000000000000141d0398331485f67e0b28b0c176664eb1ec3bdae84654e054dc46ca9f83a3798889d917d3a224d0c4f5fbae609e8b4c91e47e82a89af25991299636276d2aaa41d468b25b8445f9bfcca0b20f213938200c485b6af72d3e38b2abbefca7f4e3df60bba84129a90a7035fef3d36900 |
|
|
|
Post by admin on May 7, 2020 6:55:32 GMT
the missing bytebeat algorithm: (t<<3)*[8/9,1,9/8,6/5,4/3,3/2,0][[0xd2d2c8,0xce4088,0xca32c8,0x8e4009][t>>14&3]>>(0x3dbe4688>>((t>>10&15)>9?18:t>>10&15)*3&7)*3&7] (not my original but someone had to put it here - a conceptual landmine for some brave soul...) Oh, come on! didn't anyone try that bytebeat string out? greggman.com/downloads/examples/html5bytebeat/html5bytebeat.html#t=0&e=0&s=8000&bb=5d00000100830000000000000000141d0398331485f67e0b28b0c176664eb1ec3bdae84654e054dc46ca9f83a3798889d917d3a224d0c4f5fbae609e8b4c91e47e82a89af25991299636276d2aaa41d468b25b8445f9bfcca0b20f213938200c485b6af72d3e38b2abbefca7f4e3df60bba84129a90a7035fef3d36900O M G !!!! |
|
|
|
Post by rockysmalls on May 7, 2020 8:24:35 GMT
now.. that CANNOT have been discovered by accident ! shows you can steer a bytebeat successfully if you have the chutzpah... or maybe stock, aitken & waterman in the driving seat |
|
|
|
Post by rodney on May 10, 2020 0:38:58 GMT
|
|
). If you haven't read it, do have a look, then you'll probably want an ALGODRONE, if you don't already.
). 
