#40

Shipping update from Electro-Smith:

Eurorack modules next in queue!

2 Likes
#41

Received my daisy pod this weekend but haven’t had time to dig in yet. Excited to do that whenever work calms down but that is probably weeks away :confused:

Anyway, there’s a forum on specifically for the daisy now too! Just signed up and posed my first of many beginner questions :slight_smile:

1 Like
#42

Just got my Patch in today, gonna poke around at it this week. It’s been a loooooong time since I touched C++ but maybe I can do something with PD.

1 Like
#43

First attempt at making something useful for the Daisy Patch.

olearia
olearia1296×864 507 KB

Olearia

A collection of applets for the Daisy Patch.

Mode Control Audio In
VCA Level Signal
VCO Pitch –
Noise Level –
VCF Cutoff Signal

All outputs direct through the audio outs.

Switch mode using the encoder. Hold the encoder and turn to navigate between applets.

CODE: https://github.com/CarlColglazier/Olearia

DOWNLOAD: https://github.com/CarlColglazier/Olearia/releases

Electro-Smith Forum Thread: https://forum.electro-smith.com/t/olearia-a-collection-of-applets-for-the-daisy-patch/248

7 Likes
#44

Olearia is taking (wave)shape!

On the coding front, I have split everything into three main classes:

  • AppHost: Main class. Has an Applet.
  • Applet: Handles inputs and outputs, draws to a portion of the screen.
  • Generator: oscillators, envelopes, etc. Basic building blocks of sound.

2020.08.17 release: https://github.com/CarlColglazier/Olearia/releases/tag/2020.08.17

4 Likes
#45

How are folks getting along with the Daisy Patch? I was quite delighted to find a daisy at the heart of my newly acquired Qubit Surface.

1 Like
#46

I think the Daisy Patch has a lot of potential as a sound source, but I’m still working to get my DSP skills up to a point where I can get it to make weird sounds I like. Not surprised that the Qu-Bit Surface is using Daisy: Andrew Ikenberry wrote a ton of the Daisy platform code. Having access to a significant amount of SDRAM is where the Daisy shines, in my opinion. It makes it much easier to implement things like long delays and reverbs where the buffers would otherwise be too large for the RAM on the STM.

2 Likes
#47

How much DSP is enough, you think? And what sorts of weird sounds are you interested in?

I ask because it’s related to a new project I’m working on that’s equal parts education and application. It may involve the Daisy platform as well.

1 Like
#48

I may be interested in this as well!
(Meant to respond to @PaulBatchelor)

1 Like
#49

Qu-Bit Data Bender also seems to be using Daisy

1 Like
#50

Work in progress is happening here: https://pbat.ch/sndkit/

there’s nothing here that’s specifically tailored for the daisy yet (or any embedded devices really), but in theory they wouldn’t be terribly difficult to port.

At some point, my hope is to get reacquainted with my Daisy Pod and to work on adapting some of the sndkit algos so they can work on embedded systems like the Daisy. I also have a personal interest in learning more about the “guts” of the Daisy, and plan to maybe even write some simplified portions of libdaisy as a literate program. Maybe.

1 Like
#51

noise engineering reverb module, desmodus versio, has one too.

2 Likes
#52

they got the gen~ thing goin now:

anyone using it yet?

1 Like
#53

Does anyone have any sense of how possible it is to roll your own board that runs the Daisy libraries and abstractions? I know that Qu-Bit and Noise Engineering are just mounting the Daisy Seed to the backs of their modules, but that sounds like a pretty expensive proposition at scale (though I know that “scale” in the modular community is a little more modest than other contexts). I know for Teensy, you have to buy chips with their proprietary bootloader pre-flashed in order to use their tooling on your own hardware, but I haven’t been able to find any information on that topic on Electrosmith’s website or forum.

Anyone know if there are any developers out there using Daisy as a development platform, but then putting together their own hardware for production?

#54

What you’re saying sounds like you want to replicate the Daisy Seed in your own board.
In order to use libDaisy you’ll need to have all of the peripherical devices like audio codec, SDRAM, etc, to be the same (not to mention the bootloader which is most likely not open).
Is there a specific reason you want to use the libDaisy in case you want to design your own hardware from scratch? Many external devices have C libraries ready.

For example, I’m currently learning the embedded design, and having the platform with many abstractions already implemented makes it easier to focus on the actual application logic, which also makes it easier to use with my own hardware designs where Daisy Seed will be a core.
To make all of this from scratch would be more reasonable in case some peripherical device should be different, but it also means that libDaisy would not support this.

I’m also curious - would the own hardware cost much less considering the PCB manufacturing and non-manual SMT parts placing?

1 Like
#55

I’m not sure what the exact hardware cost would be, but I’m pretty sure it’s not going to be $30 for an MCU and peripheral devices. In all it’s probably about 10-25% more expensive to put a Daisy Seed on the back of a module compared to buying components. It also gives flexibility for form factor, especially for smaller modules. I’m already using Daisy as a development platform, but I’m wondering if anyone takes it beyond that point. Electrosmith writes in their documentation that libDaisy and DaisySP is compatible with hardware outside of the Daisy ecosystem, but I haven’t seen any resources or documentation that gets into the details.

#56
  • noise engineering are offering a blank panel for the versio modules so you can swap firmwares and it’s gonna be OS, I assume their stereo osc is gonna be the same (they don’t explicitly say daisy but I think the copy is a bit old) and qu-bit have at least one module (I think data bender) that is running a daisy

I got a pod as I didn’t want to have it stuck in the rack, the fact it runs ~gen and a bunch of other stuff, the Faust delay is bloody gorgeous

#57

While it is true for DaisySP because it is a library with generic DSP stuff, libDaisy is created as a backbone for a specific platform, so it is obvious to use it with Daisy only.

1 Like
#58

I’m a relative newcomer to max, but have some really specific hardware ideas I’d like to prototype. Seems like the Daisy is pretty much the perfect platform. Am I wrong, dude?

#59

@mattlowery In terms of audio I/O, there is a tool which was created recently - GitHub - electro-smith/oopsy: gen~ to Daisy: exporting Max Gen patchers for the ElectroSmith Daisy hardware platforms
I’m not sure if it currently supports a base Daisy board - I’ve tried it with Daisy Patch and I’ve seen some other devices from their ecosystem as well (it gives access to the device’s specific knobs and display, for example).
For the bare board, I think it should at least allow 2 in / 2 outs, not sure if it is implemented now. If not, this will involve some manipulations with exported gen-to-C++ code to deploy it to the board.

But you have to keep in mind that this is gen~ subset of Max anyway, so it is somewhat trickier and more time-consuming to prototype comparing to the regular Max (but allows per-sample processing which is going to be on the board anyway).

1 Like