This looks really good. Can I ask... how would this work with regards to software licensing and possible redistribution? Obviously PD itself is on BSD license but once you have compiled for daisy (I am guessing this would be a .HEX file or similar) there is no longer access to the source/ patch. Thanks for the tutorial 🙂
We don't use any PD source code. The internal Heavy static C library is likewise BSD licensed. Any user generated code is licensed as the user wants using the "copyright" argument. Of course if you base your patch on patches and abstractions that are not freely distributable that makes you liable. The conversion of source patch-code and it's associated legality is quite a grey area. Personally we only include such patches if they are liberally licensed (MIT/BSD/ISC/CC0 etc.)
I'm trying to compile a very simple delay effect using plugdata 9.0 flashed to daisy patch. I do not hear any delay effect. my patch uses adc~ & dac~ objects as start & end points in the patch. All objects are "compile mode safe". but i cannot get sound out of my daisy patch. Also its seems when I compile I am only able to generate a bin file followed by using the online daisy programmer since it seems flashing doesn't work. I definitly have my daisy in DFU mode prior to flash attempts.
Which compile mode are you using? With delays you will likely at least need big or huge modes and even more likely use an extended linker. Right now this means using the custom linker option and then use the SDRAM for the dynamic table. You can get the SDRAM linkers from `Documents/plugdata/Toolchain/etc/linkers/` directory (we will include them as a compile option again in the future).
Thank you very much for the video! I am trying to load an example, but in the PlugData board selection menu the Seed option does not appear, only pod, init, simple, etc. It will be an error in the installation
The Seed is not a valid device yet. You will need to create a custom board.json that defines a hardware setup built around the Seed. Check out this Wiki page (and link to examples at the bottom) for more info: github.com/electro-smith/DaisyWiki/wiki/Pd2dsy-JSON
@@Wasted-Audio I am trying to get a light dependent resistor to control the pitch of an oscillator using the daisy seed. Anything similar to that would be awesome!
@@alexandersousa6728 That should be relatively easy, considering it's just a resistor. Any example that uses a potentiometer should be able to be replaced with an LDR.
@@Wasted-Audio funnily enough, I was digging through some of the documentation trying to figure out how to write custom json for my simple fix board, and then I saw the "simple" option in the dropdown, only to realize all the work had already been done... Is everything in the pd2dsy library supported, like encoders, LEDs, etc? It would also be cool to see a video on how to interface with other things, like SPI bus or I2C. I'm eying some projects that use an MPR121 capacitive touch sensor, and I'm curious if it's possible to interface with that (especially if there's a way to use existing C / C++ libraries like the one from adafruit) I'm also finding a lot of cool things with the plugdata UI (which is amazing, btw) and I'm starting to wonder what other keyboard shortcuts and workflow tricks I'm missing (eg dropping a command block onto an existing patch to "splice" it into the patch is a huge time saver). It would be cool to see a video overview of all the great features. Thank you!!
@@235_10 This is a lot of questions at once! The "Simple" is a basic board aimed at the Synthux Academy projects, it is still missing a lot of components and we want to expand it to cover a very basic/simple project. Any feedback is appreciated. pd2dsy is not a library and it is not supported. Do you mean json2daisy? (which is being used under the hood) Mpr121 sensors are supported and work reasonably well. It is not possible to use other c/c++ libraries.
Getting the OWL toolchain integrated with plugdata is being planned. Unfortunately when I was working on it last year my OWLv2 board got fried and this work got stuck. Since then I got a v3 board and we hope to continue with it this year :)
@@Wasted-Audio Personally, I find background music to informational content very annoying. It gives me a headache after a while, which I assume is a neurological effect of having to filter out the "noise". Perhaps some people need distraction to avoid becoming bored, which might be an ADHD issue? I never listened to music while studying as I found that unhelpful. Maybe I'm just bad at multitasking.
@@Wasted-Audio Music that is related to the content is fine, of course. It might just be me that finds this particular background very distracting. Thanks.
Custom hardware is on the planning! certainly buttons and pots, although for that last one we need to source a `Bno055` first (only 9 axis component currently supported in json2daisy). Which is a tad expensive, or maybe the ICM20948 which is cheaper, but still a bit much. We'll probably stick to a bit more basic stuff for the next one :)
@@Wasted-Audio I have a couple of the Bno055's, although would it be easier to run the stuff through an atmega and just program the digial ins to the seed with PlugD?
@@chillywilsonThe Bno055 is supported in libDaisy and json2daisy (which is used to create the interface with Heavy): github.com/electro-smith/json2daisy/blob/main/src/json2daisy/resources/component_defs.json#L1207-L1310 How would you want to receive data from the Arduino then?
This looks really good. Can I ask... how would this work with regards to software licensing and possible redistribution? Obviously PD itself is on BSD license but once you have compiled for daisy (I am guessing this would be a .HEX file or similar) there is no longer access to the source/ patch.
Thanks for the tutorial 🙂
We don't use any PD source code. The internal Heavy static C library is likewise BSD licensed. Any user generated code is licensed as the user wants using the "copyright" argument.
Of course if you base your patch on patches and abstractions that are not freely distributable that makes you liable. The conversion of source patch-code and it's associated legality is quite a grey area. Personally we only include such patches if they are liberally licensed (MIT/BSD/ISC/CC0 etc.)
thanks a bunch this was super helpful!
Glad we can be of service!
I'm trying to compile a very simple delay effect using plugdata 9.0 flashed to daisy patch. I do not hear any delay effect. my patch uses adc~ & dac~ objects as start & end points in the patch. All objects are "compile mode safe". but i cannot get sound out of my daisy patch. Also its seems when I compile I am only able to generate a bin file followed by using the online daisy programmer since it seems flashing doesn't work. I definitly have my daisy in DFU mode prior to flash attempts.
Which compile mode are you using? With delays you will likely at least need big or huge modes and even more likely use an extended linker. Right now this means using the custom linker option and then use the SDRAM for the dynamic table. You can get the SDRAM linkers from `Documents/plugdata/Toolchain/etc/linkers/` directory (we will include them as a compile option again in the future).
Thank you very much for the video!
I am trying to load an example, but in the PlugData board selection menu the Seed option does not appear, only pod, init, simple, etc.
It will be an error in the installation
The Seed is not a valid device yet. You will need to create a custom board.json that defines a hardware setup built around the Seed.
Check out this Wiki page (and link to examples at the bottom) for more info: github.com/electro-smith/DaisyWiki/wiki/Pd2dsy-JSON
This is great! Looking forward to a custom json video!
Something is brewing, but it shouldn't be too simple nor too complex.
Any suggestions other than some knobs/switches? :)
@@Wasted-Audio I am trying to get a light dependent resistor to control the pitch of an oscillator using the daisy seed. Anything similar to that would be awesome!
@@alexandersousa6728 That should be relatively easy, considering it's just a resistor.
Any example that uses a potentiometer should be able to be replaced with an LDR.
@@Wasted-Audio funnily enough, I was digging through some of the documentation trying to figure out how to write custom json for my simple fix board, and then I saw the "simple" option in the dropdown, only to realize all the work had already been done... Is everything in the pd2dsy library supported, like encoders, LEDs, etc?
It would also be cool to see a video on how to interface with other things, like SPI bus or I2C. I'm eying some projects that use an MPR121 capacitive touch sensor, and I'm curious if it's possible to interface with that (especially if there's a way to use existing C / C++ libraries like the one from adafruit)
I'm also finding a lot of cool things with the plugdata UI (which is amazing, btw) and I'm starting to wonder what other keyboard shortcuts and workflow tricks I'm missing (eg dropping a command block onto an existing patch to "splice" it into the patch is a huge time saver). It would be cool to see a video overview of all the great features.
Thank you!!
@@235_10 This is a lot of questions at once!
The "Simple" is a basic board aimed at the Synthux Academy projects, it is still missing a lot of components and we want to expand it to cover a very basic/simple project. Any feedback is appreciated.
pd2dsy is not a library and it is not supported. Do you mean json2daisy? (which is being used under the hood)
Mpr121 sensors are supported and work reasonably well.
It is not possible to use other c/c++ libraries.
Excellent info for anyone interested in this workflow.
Thank you for the great tutorial! I have a question: Would this approach also work with other devices/platforms like the Befaco Lich/OWL?
Getting the OWL toolchain integrated with plugdata is being planned.
Unfortunately when I was working on it last year my OWLv2 board got fried and this work got stuck.
Since then I got a v3 board and we hope to continue with it this year :)
Well done, bro!!!
excellent vid bud, keep them coming :)
Yes yes, thinking about the next one! :)
Marvellous.
If the background blooping was meant to be distracting and annoying, it succeeded.
I'm sorry, should we do our videos without any music?
Still trying to figure this out.
@@Wasted-Audio Personally, I find background music to informational content very annoying. It gives me a headache after a while, which I assume is a neurological effect of having to filter out the "noise". Perhaps some people need distraction to avoid becoming bored, which might be an ADHD issue? I never listened to music while studying as I found that unhelpful. Maybe I'm just bad at multitasking.
@@HeeBeeGeeBee392 We'll try to find a better balance in future videos. Thanks for the feedback.
@@Wasted-Audio Music that is related to the content is fine, of course. It might just be me that finds this particular background very distracting. Thanks.
Great tutorial! Answered all of my questions. Time to dig in to the patch init + plugdata! :)
We finished building two Patch.Init()s the other month. Hope to showcase some nice patches in a future video! :)
Actually ☝
it's great thing but at last adding shipping cost it cost lots of money :(
There are some resellers where you can get the Daisy in your area maybe.
Thank you!
Nom nom nom, eating this up.
Can you do some custom hardware next, like buttons, pots and 9 axis accelerometers?
Custom hardware is on the planning! certainly buttons and pots, although for that last one we need to source a `Bno055` first (only 9 axis component currently supported in json2daisy). Which is a tad expensive, or maybe the ICM20948 which is cheaper, but still a bit much.
We'll probably stick to a bit more basic stuff for the next one :)
@@Wasted-Audio I have a couple of the Bno055's, although would it be easier to run the stuff through an atmega and just program the digial ins to the seed with PlugD?
@@chillywilsonThe Bno055 is supported in libDaisy and json2daisy (which is used to create the interface with Heavy): github.com/electro-smith/json2daisy/blob/main/src/json2daisy/resources/component_defs.json#L1207-L1310
How would you want to receive data from the Arduino then?
@@Wasted-Audio I was thinking digital in to daisy
@@Wasted-Audio Why isn't a 6 DOF device sufficient? Is it really that important to have magnetic North in the input stream?