Update: There ARE way more memory storage available inside of Daisy! With the bootloader, you can run programs up to 480kB on SRAM (nearly 4 times that of Flash that was used in this tutorial) and almost 8MB on QSPI flash. I will do an entire video on this topic in the future! In the meantime, you can try the following in the terminal to access SRAM (I'll be showcasing this in the upcoming Daisy POD video when I load in a big reverb!): python pd2dsy(dot)py --rom size --board pod huge_reverb(dot)pd cd huge_reverb (Boot hold, Reset hold and then let go, Boot let go) make program-boot make program-app Aaaand that's it! Note: run the "make program-app" while the LED on Daisy is flashing upon completion of "make program-boot". What I do is copy "make program-app" in advance. And as soon as "make program-boot" is complete, I hit paste and press enter ASAP.
What's up, Matthew! Your Siren video popped up in my recommendation recently. Great production and I dig the overall chill vibe. Beautiful demo of that synth too// I appreciate your checking out my video! Glad you liked it! Thank you
@@SoundSimulator Thank you so much! I am very interested in making my own modules and Pure Data has always been something I’ve dabbled in. Are you still working in pure data?
@@EZBOT_ That's awesome! I use Pure Data for this channel and MaxMSP for personal projects. If both were free, I may have done Max tutorials. That being said, with PlugData coming out (with really cool Daisy feature in development!!), it's an amazing time to start learning Pure Data for custom module design purpose! PlugData solves the UI experience of vanilla Pure Data imo!! And even if you change your mind and switch over to Max, it's easy to get the grasp of it since it's very similar to Pure Data. Feel free to let me know if you have any questions any time!
Hi, partially due to your videos (thank you!) I purchased a patch init() and am looking forward to using it. Unfortunately, the setup is far from simple. There is no documentation for setting up the patch sm, only info on setting up a seed. I know there are other people out there trying to get this thing working. Can you do a setup tutorial! That would be great!
Pretty dang cool! This is getting my mind rolling on how to shove my sequencer patch into this. Right now it has a lot of controls so it would need to do something complicated with the knobs/cv inputs to define what functions are accessible at a given moment. Maybe one cv value to set the channel, another to set what the button or a gate in would do. In any case, very cool to see a module dedicated to this. I hope the performance goes well.
Awesome, this is definitely on my must have modules list to buy in the future. I think monome have something kinda like it, but this is way better, specially because it have pd support.
That's awesome to hear!! I'm definitely planning on creating more tutorials on Pure Data + Daisy, but I hope this will do for now!! There are cool stuff being developed for hvcc, so it's an exciting time to start Pure Data embedded audio!! Let me know if you have any questions setting up the software!
You can actually also program to the sram and get 512kb of space! (it's supposedly slower, but I haven't had any issues with it so far. have been testing it on the Daisy Field) It's also possible to program to other memory sections, but those didn't work for me so far. In the future we of course also want to add midi, and other functionality. The hvcc integration is far from complete and we'll be adding new features in the future! Btw, I did not realize that rev1/2/3~ are simply just subpatches. In this case we could actually include them as is in hvcc, if it makes sense to do so. A version of rev2~ is included in heavylib (under the name `hv.reverb`)
@@SoundSimulator the `Wasted Audio` repo is mine ;) And not weird, they are apparently just abstractions. Heavy/HVCC is just not aware of them. As said the `rev2~` is included in heavylib already (stereo out). Not sure if we should simply include them. I would say that they are not really part of the "core language" so not really needed, but it could help to translate existing patches for Heavy.
Fascinating, as always! Not being a muso, I wasn't aware of synth modules with programmable MCU's, like the dev board you showed at the end. These are the same concept as my T4 laser Synth. IOW, I'm only reinventing a different 'wheel'... or it confirms that I'm following the right path for creating/playing 'visual' music. Video is in production. 😎 How could your family not be proud of you and the work you're doing? Yeah, mine never understood laser shows, neither. 🤷♂
Thank you so much!!! It's always cool to get confirmation and validation like that!! And I'm looking forward to your video!! That joke was harsher originally, hahaha.
@@SoundSimulator When I became a Laserium laserist, back in 1978, my folks wouldn't even go to the local planetarium to see what I was going to be doing half way around the world at the London Planetarium. "We're not interested in listening to loud rock music and flashing lights." That was heart breaking for a young man, seeking approval and recognition of success. They simply passed on, with no idea. Moral of the story: Most of all, we need to satisfy our own standards of success, for we are the only ones who understand how difficult that path has been, still is, and will become. Perfection is only in the mind of the beholder. Glad to hear your folks are more open minded and interested. I'm sure that you'll do fine.
@@TheOleHermit I'm really sorry to hear that. I bet it was tough. I would love to hear your story more in the video as you introduce your new chapter. My telling them that I wanted to do music wasn't the most smooth-sailing thing either. But yeah for sure. The only person who can validate and understand is ultimately yourself.
@@SoundSimulator C'est la vie... lol, I've already included a brief history in the intro, but it's already pushing 30 minutes worth of monologue for the project and you've only requested a couple of minutes' worth. 😣 Q: Which is the greater accomplishment? A: a billionaire's joyride into orbit, or B: a baby's first step. Who is the best to judge? 🙏😎
@@SoundSimulator Yes, understood from video! Thanks! I am not into modular, yet, have several semi-modular synths, thus, thinking I can use the module (along with a "minimal" modular setup...case/power supply maybe some utility module) to incorporate with my patches. Any thoughts around this would be appreciated! I also saw the Patch module, though more expensive I was wondering if it provides add'l features and maybe "easier" for me to implement???
@@LuisTorres-qz5kr It ultimately depends on what you want to achieve. Please feel free to ask more details on the Electrosmith forum and also their discord about what Daisy is capable of as well as its limitation. Or ask here too!
It would be nice if it had USB port to connect midi controllers to. I like Bela Salt for that, I have whole groovebox built in PD, embedded into the module which I can control with various controllers. I would like something smaller and perhaps with a screen. Owl modular seems to have solution with Genius, but Pure Data support is not native as it needs to be re-compiled and thus might not work correctly.
I have the Daisy Patch Submodule and it could be cool to design a custom module out of it that consists of OLED screen and USB port in the front. Something smaller than the Daisy Patch but with similar functionality.
looking at this video.. mm ok ok .. then 14:50 I had a matrix vision like OMG of course that multi tempo trigger that I never was able to find anywhere ! maybe that the tool for it ! ahah Thanks.. well just have to learn pure data now :(
It'll be hard to explain via the comment section but that should be possible in gen~ (which is what you use for the Daisy). Feel free to join the Daisy Discord and we can think of an approach together :)
I have a Befaco Lich (which has USB to the front panel), and then … there's the 4ms MetaModule, a module that hosts VCV Rack. (Someone else here mentioned the Der Mann mit der Maschine Droid, which has a vast set of control inputs from submodules, but is CV-only (no audio rate I/O).) Any thoughts about how the various options compare?
I love all these PD based modules/synth. I have several of them myself. But one issue with pretty much all of them are that they are not powerful enough to make something really cool. They simply does not have CPU or RAM enough, in my opinion at least.
This was my first time using a Pure Data programmable module and I'm having fun with it so far! There's been new modules coming out that are powered by Daisy (Noise Engineering and Qu-Bit specifically), so I think it has enough power. It'll be fun to see people pushing it to the limit!
@@SoundSimulator If it runs out of memory for Rev3~ its way too limited. That reverb doesn't sound too good, way too much ringing. If it was able to run quality effects, like a quality reverb, a delay, some chorus effect etc. I would be impressed. But if it can not even load Rev3~ abstraction, it's way too limited. I do have a Daisy Seed myself and have been kind of disappointed. Programming was not good enough, as you could not really take advantage of SDRAM for patches only SRAM, which is very limited on pretty much all of these devices. I kind of gave up, cause the development for the PD>Daisy script, which should turn PD patches into Daisy code, was too slow. This is years ago, not sure of they got it working now, the free use of SDRAM. But yeah, I guess we all have our own needs. I need way more than Daisy can supply and if want to make quality effect and synth, it's just not possible with that amount of SRAM. I do also have an Organelle, a Bella, a Daisy Seeds, an Axoloti and one or two more micro controller based DSP devices. They are cool, but all way to limited. As soon as you start to want to make something really cool, like even a basic synth with band limited oscillators, an oversampled filter and maybe even a couple of voices of polyphony, you are pretty much out of resources, already by the first voice. Polyphony....... Forget about it...... Organelle M, the new one with 4 cores is trying to fill a void there. But using several CPU cores in PD is a nightmare and not even sure it's gonna work running on Organelle. There is latency involved, you also have to have multiple instances of PD running to be able to even take advantage of more cores. It's very complicated. I never saw one example for Organelle of a patch that take advantage of the 4 cores it has. Which is kind of sad. Hopefully over time some more powerful micro controllers will be available, so it will be possible to make something really cool. I want good stuff, not just anything ;)
@@jaffasplaffa1 [rev3~] I don't think is optimized enough considering its size and sound quality. Not a fan of the sound at all either. I just checked another Pure Data reverb that sounds significantly better (like product-worthy quality imo) and it's waaaay smaller than the size of [rev3~] (38% of the size or maybe even smaller). The only reason why I forgot about it until now is that it's prone to feedbacking to 10000 dB, haha. If it's fail-proof, I would've used it for this video and recommend other people too. I talked to a person who's actually doing that as we speak. I should contact them again. The Daisy community is still very new and growing, so I hope you stick around!!
@@franciscoraupp I am probably not the best one to ask about it. I am not into Eurorack, so not 100% sure which one to get, if that's what you are looking for. But last time I checked they were pretty much all relying on Heavy, which converts PD patches to embedded code. It has it's limitations and is not really maintained anymore. I personally always just ends up running Pure Data from my macbook, I just can't find any PD based micro controllers that are powerful enough to do great quality stuff. But if you just want to make some basic module with a simple delay, then the PATCH.INIT() or the Daisy Patch is probably fine. I like Daisy Patch, cause it has a display. And there is also the Pepper module, which is based on Bela. I think Bela has nice sound quality. There is also Owl module from Rebel Technology. Not sure it's produced anymore though. Argh. I hope I did not create more confusion here, haha :) First world problems - Too much to choose from :)
I haven't but if there's part of the patcher that you would like to have, let me know. I think I showed most (if not all) of the patcher throughout the video. It's a very specific patcher that's made for the modules that I have so I didn't think that it would be helpful for others.
I must decide to "Make or Buy" a module that can output rectangular audio between 20 kHz and 50 kHz (like a simple function/waveform generator) under CV control. Are the patch.init audio outs suitable for this frequency range?
I’ve been learning PD for a month. If you apply yourself you can probably pick up quite a lot in a relatively short space of time. I’ve managed to cobble together some ok things in this time. It’s a journey, I’m here for the long haul :)
Droid is the bee's absolute knees at what it does, but it's not audio rate. You get vast options for control inputs, but your outputs are 8 CV and 8 gate (last time I counted), no audio.
Update: There ARE way more memory storage available inside of Daisy!
With the bootloader, you can run programs up to 480kB on SRAM (nearly 4 times that of Flash that was used in this tutorial) and almost 8MB on QSPI flash. I will do an entire video on this topic in the future!
In the meantime, you can try the following in the terminal to access SRAM (I'll be showcasing this in the upcoming Daisy POD video when I load in a big reverb!):
python pd2dsy(dot)py --rom size --board pod huge_reverb(dot)pd
cd huge_reverb
(Boot hold, Reset hold and then let go, Boot let go)
make program-boot
make program-app
Aaaand that's it!
Note: run the "make program-app" while the LED on Daisy is flashing upon completion of "make program-boot".
What I do is copy "make program-app" in advance. And as soon as "make program-boot" is complete, I hit paste and press enter ASAP.
I'm so excited by this! Hadn't heard of this module before. Great video
I'm glad I was able to introduce it to you!!
Nice author & punisher shirt. Love your vids dude
He's one of the biggest reasons (if not the biggest reason) why I got into designing custom instruments.
And thank you for watching!!!
Thank you for your time. I have purchased the Daisy Patch. I love your teaching style, and your video inspires me to play with the module.
Nice!!!! I'm happy to hear that :)
I hope you have fun with your new Daisy Patch!
Wow, what a great video. Seriously, thank you.
What's up, Matthew!
Your Siren video popped up in my recommendation recently. Great production and I dig the overall chill vibe. Beautiful demo of that synth too//
I appreciate your checking out my video! Glad you liked it!
Thank you
@@SoundSimulator Thank you so much! I am very interested in making my own modules and Pure Data has always been something I’ve dabbled in. Are you still working in pure data?
@@EZBOT_ That's awesome! I use Pure Data for this channel and MaxMSP for personal projects. If both were free, I may have done Max tutorials.
That being said, with PlugData coming out (with really cool Daisy feature in development!!), it's an amazing time to start learning Pure Data for custom module design purpose!
PlugData solves the UI experience of vanilla Pure Data imo!! And even if you change your mind and switch over to Max, it's easy to get the grasp of it since it's very similar to Pure Data.
Feel free to let me know if you have any questions any time!
YOU MIGHT HAVE JUST SOLD A UNIT!
A setup tutorial would be amazing! This video was great
YESS, planning on it!
And thank you so much!
Hi, partially due to your videos (thank you!) I purchased a patch init() and am looking forward to using it. Unfortunately, the setup is far from simple. There is no documentation for setting up the patch sm, only info on setting up a seed. I know there are other people out there trying to get this thing working. Can you do a setup tutorial! That would be great!
Pretty dang cool! This is getting my mind rolling on how to shove my sequencer patch into this. Right now it has a lot of controls so it would need to do something complicated with the knobs/cv inputs to define what functions are accessible at a given moment. Maybe one cv value to set the channel, another to set what the button or a gate in would do. In any case, very cool to see a module dedicated to this. I hope the performance goes well.
Thank you so much for watching!
I'm glad to hear that it's inspiring ideas in your head! Would love to see your sequencer in module-form too!
Awesome, this is definitely on my must have modules list to buy in the future.
I think monome have something kinda like it, but this is way better, specially because it have pd support.
Nice!! I'm excited for you to design something unique with it!! It's a lot of fun!
this is fantastic thanks - i'm just getting started with both pure data and daisy so really interesting to walk through
That's awesome to hear!!
I'm definitely planning on creating more tutorials on Pure Data + Daisy, but I hope this will do for now!!
There are cool stuff being developed for hvcc, so it's an exciting time to start Pure Data embedded audio!!
Let me know if you have any questions setting up the software!
@@SoundSimulator thanks! it's a learning curve but going slowly to start with. i've built FV-1 effects in spinCAD designer so it's kinda similar
if you long press the Rings right button you get some reverb from rings. You can save some external processing
WHAT!!!!!!!!! I have to try that out now. Thanks for the tip!
Great overview and nice patch too!
Thank you so much, Charlie!
It's a simple yet effective patch!!
You can actually also program to the sram and get 512kb of space! (it's supposedly slower, but I haven't had any issues with it so far. have been testing it on the Daisy Field)
It's also possible to program to other memory sections, but those didn't work for me so far.
In the future we of course also want to add midi, and other functionality. The hvcc integration is far from complete and we'll be adding new features in the future!
Btw, I did not realize that rev1/2/3~ are simply just subpatches. In this case we could actually include them as is in hvcc, if it makes sense to do so.
A version of rev2~ is included in heavylib (under the name `hv.reverb`)
I need to try that out!
Are you involved in hvcc development?
Yeah, [rev~]s weirdly works when you just take the content of them.
@@SoundSimulator the `Wasted Audio` repo is mine ;)
And not weird, they are apparently just abstractions. Heavy/HVCC is just not aware of them. As said the `rev2~` is included in heavylib already (stereo out). Not sure if we should simply include them. I would say that they are not really part of the "core language" so not really needed, but it could help to translate existing patches for Heavy.
@@_DRMR_ Woah, that's awesome!!
Please keep us posted! Would love to collaborate and do a "what's new in hvcc"-type video in the future.
Fascinating, as always!
Not being a muso, I wasn't aware of synth modules with programmable MCU's, like the dev board you showed at the end. These are the same concept as my T4 laser Synth. IOW, I'm only reinventing a different 'wheel'... or it confirms that I'm following the right path for creating/playing 'visual' music.
Video is in production. 😎
How could your family not be proud of you and the work you're doing? Yeah, mine never understood laser shows, neither. 🤷♂
Thank you so much!!!
It's always cool to get confirmation and validation like that!! And I'm looking forward to your video!!
That joke was harsher originally, hahaha.
@@SoundSimulator When I became a Laserium laserist, back in 1978, my folks wouldn't even go to the local planetarium to see what I was going to be doing half way around the world at the London Planetarium. "We're not interested in listening to loud rock music and flashing lights." That was heart breaking for a young man, seeking approval and recognition of success.
They simply passed on, with no idea.
Moral of the story: Most of all,
we need to satisfy our own standards of success, for we are the only ones who understand how difficult that path has been, still is, and will become. Perfection is only in the mind of the beholder.
Glad to hear your folks are more open minded and interested. I'm sure that you'll do fine.
@@TheOleHermit I'm really sorry to hear that. I bet it was tough.
I would love to hear your story more in the video as you introduce your new chapter.
My telling them that I wanted to do music wasn't the most smooth-sailing thing either.
But yeah for sure. The only person who can validate and understand is ultimately yourself.
@@SoundSimulator C'est la vie...
lol, I've already included a brief history in the intro, but it's already pushing 30 minutes worth of monologue for the project and you've only requested a couple of minutes' worth. 😣
Q: Which is the greater accomplishment?
A: a billionaire's joyride into orbit, or
B: a baby's first step.
Who is the best to judge?
🙏😎
@@TheOleHermit make it a feature film while at it then!!
And B for sure.
This is awesome, thanks for sharing. Will have to research to use it w/MaxMSP v8
Glad you liked the video!! Please do keep in mind that you need to use gen~ for Daisy.
@@SoundSimulator Yes, understood from video! Thanks! I am not into modular, yet, have several semi-modular synths, thus, thinking I can use the module (along with a "minimal" modular setup...case/power supply maybe some utility module) to incorporate with my patches. Any thoughts around this would be appreciated! I also saw the Patch module, though more expensive I was wondering if it provides add'l features and maybe "easier" for me to implement???
@@LuisTorres-qz5kr It ultimately depends on what you want to achieve.
Please feel free to ask more details on the Electrosmith forum and also their discord about what Daisy is capable of as well as its limitation. Or ask here too!
@@SoundSimulator Will do, thank you!
It would be nice if it had USB port to connect midi controllers to. I like Bela Salt for that, I have whole groovebox built in PD, embedded into the module which I can control with various controllers. I would like something smaller and perhaps with a screen. Owl modular seems to have solution with Genius, but Pure Data support is not native as it needs to be re-compiled and thus might not work correctly.
I have the Daisy Patch Submodule and it could be cool to design a custom module out of it that consists of OLED screen and USB port in the front.
Something smaller than the Daisy Patch but with similar functionality.
looking at this video.. mm ok ok .. then 14:50 I had a matrix vision like OMG of course that multi tempo trigger that I never was able to find anywhere ! maybe that the tool for it ! ahah
Thanks.. well just have to learn pure data now :(
good luck for a great performance!
✨✨
That was cool.
Thank you so much!
My friend! Beautiful video!! Do you have in mind any Studio Tour?
Ps: I'm working in the Pd patch for the community video :)
Thank you!!! My studio tour video will be like a minute long!!
And that's great! Will be looking forward to it!!!
this is really inspiring - thanks for sharing! I know PD and but I like to do music DAWless. This could be the glue
Thank you so much for watching!! I hope this is something you were looking for!!
Thanks for sharing the project (^-^)/★彡 Is there a same way to sync the delay time by gate in Max? how to define the tempo period for the time length?
It'll be hard to explain via the comment section but that should be possible in gen~ (which is what you use for the Daisy). Feel free to join the Daisy Discord and we can think of an approach together :)
I have a Befaco Lich (which has USB to the front panel), and then … there's the 4ms MetaModule, a module that hosts VCV Rack. (Someone else here mentioned the Der Mann mit der Maschine Droid, which has a vast set of control inputs from submodules, but is CV-only (no audio rate I/O).)
Any thoughts about how the various options compare?
I love all these PD based modules/synth. I have several of them myself.
But one issue with pretty much all of them are that they are not powerful enough to make something really cool. They simply does not have CPU or RAM enough, in my opinion at least.
This was my first time using a Pure Data programmable module and I'm having fun with it so far!
There's been new modules coming out that are powered by Daisy (Noise Engineering and Qu-Bit specifically), so I think it has enough power.
It'll be fun to see people pushing it to the limit!
@@SoundSimulator If it runs out of memory for Rev3~ its way too limited. That reverb doesn't sound too good, way too much ringing.
If it was able to run quality effects, like a quality reverb, a delay, some chorus effect etc. I would be impressed. But if it can not even load Rev3~ abstraction, it's way too limited.
I do have a Daisy Seed myself and have been kind of disappointed. Programming was not good enough, as you could not really take advantage of SDRAM for patches only SRAM, which is very limited on pretty much all of these devices. I kind of gave up, cause the development for the PD>Daisy script, which should turn PD patches into Daisy code, was too slow. This is years ago, not sure of they got it working now, the free use of SDRAM.
But yeah, I guess we all have our own needs. I need way more than Daisy can supply and if want to make quality effect and synth, it's just not possible with that amount of SRAM.
I do also have an Organelle, a Bella, a Daisy Seeds, an Axoloti and one or two more micro controller based DSP devices. They are cool, but all way to limited. As soon as you start to want to make something really cool, like even a basic synth with band limited oscillators, an oversampled filter and maybe even a couple of voices of polyphony, you are pretty much out of resources, already by the first voice. Polyphony....... Forget about it......
Organelle M, the new one with 4 cores is trying to fill a void there. But using several CPU cores in PD is a nightmare and not even sure it's gonna work running on Organelle. There is latency involved, you also have to have multiple instances of PD running to be able to even take advantage of more cores. It's very complicated. I never saw one example for Organelle of a patch that take advantage of the 4 cores it has. Which is kind of sad. Hopefully over time some more powerful micro controllers will be available, so it will be possible to make something really cool. I want good stuff, not just anything ;)
@@jaffasplaffa1 [rev3~] I don't think is optimized enough considering its size and sound quality. Not a fan of the sound at all either.
I just checked another Pure Data reverb that sounds significantly better (like product-worthy quality imo) and it's waaaay smaller than the size of [rev3~] (38% of the size or maybe even smaller). The only reason why I forgot about it until now is that it's prone to feedbacking to 10000 dB, haha. If it's fail-proof, I would've used it for this video and recommend other people too. I talked to a person who's actually doing that as we speak. I should contact them again.
The Daisy community is still very new and growing, so I hope you stick around!!
I'm looking to buy one but do'nt know which one to choose. What modules do you have? How they compare to each other?
@@franciscoraupp I am probably not the best one to ask about it. I am not into Eurorack, so not 100% sure which one to get, if that's what you are looking for. But last time I checked they were pretty much all relying on Heavy, which converts PD patches to embedded code. It has it's limitations and is not really maintained anymore.
I personally always just ends up running Pure Data from my macbook, I just can't find any PD based micro controllers that are powerful enough to do great quality stuff.
But if you just want to make some basic module with a simple delay, then the PATCH.INIT() or the Daisy Patch is probably fine. I like Daisy Patch, cause it has a display.
And there is also the Pepper module, which is based on Bela. I think Bela has nice sound quality.
There is also Owl module from Rebel Technology. Not sure it's produced anymore though.
Argh. I hope I did not create more confusion here, haha :)
First world problems - Too much to choose from :)
Have you posted the patch in it file that you were working on anywhere? I feel like it would be a a great starting point for someone new
I haven't but if there's part of the patcher that you would like to have, let me know. I think I showed most (if not all) of the patcher throughout the video. It's a very specific patcher that's made for the modules that I have so I didn't think that it would be helpful for others.
I must decide to "Make or Buy" a module that can output rectangular audio between 20 kHz and 50 kHz (like a simple function/waveform generator) under CV control. Are the patch.init audio outs suitable for this frequency range?
You can run the codec at up to 96kHz which gives you a nyquist frequency of 48kHz maximum.
Bro stop it man lol
Guys dont follow this, it is not as easy as it sounds :/
Dont get me wrong it is great! But pure data takes way longer to learn than he makes it sound
@@brianj6314 I have a pure data tutorial series 🙂
Let me know if you have any specific questions.
I’ve been learning PD for a month. If you apply yourself you can probably pick up quite a lot in a relatively short space of time. I’ve managed to cobble together some ok things in this time. It’s a journey, I’m here for the long haul :)
Check DMMDM - Droid 👍🏿
Droid is the bee's absolute knees at what it does, but it's not audio rate. You get vast options for control inputs, but your outputs are 8 CV and 8 gate (last time I counted), no audio.