Getting Started with the Electrosmith Daisy Seed

Рет қаралды 9,772

Күн бұрын

Пікірлер: 27

@shanebrown5643 2 жыл бұрын

I downloaded the DaisyExamples folder but the seed folder doesn't have the oscillator example anymore. Any idea what that's all about?/where i could get it?

@GrimClock 2 жыл бұрын

Hello, it looks like it is now under Seed/DSP/Oscillator on the Github. This makes sense since they have so many objects now. Thanks for pointing it out!

@0Fdigital Жыл бұрын

Thanks so much for this. I'm very new to audio programming and just grabbed a Seed; I very much appreciate that you explained almost everything I was confused about!

@ynschannel_ 2 жыл бұрын

Thanks, I bought my Daisy a few days ago and this videos helps a lot.

@jenniferw8963 2 жыл бұрын

Glad you are doing this for mac since I'm on mac :)

@beatrute2677 2 жыл бұрын

Thanks for this mate, Really helped me out and got me started.

@Daruma_Studio 2 жыл бұрын

Very appreciative of this. Checking your channel for more videos on this.

@PnPModular Жыл бұрын

Really nice video thank you

@jimjosemusic5325 Жыл бұрын

Thank you for your tutorial ! In reference to 2:45.. my version of Visual Studio (2022 Preview) I don't have a tab for Terminal,.. although I find it listed under "View". I have the Oscillator sketch up like you have it,.. but when the Terminal underneath is brought up, it doesn't have the correct path - therefore when I type in "make" it doesn't know what I'm trying to do. The path that it shows is: C:\Users\Admin\Desktop\DaisyExamples-master> (doesn't have seed\oscillator). I tried to type it in manually, but to no avail. Sorry for the newbie question,.. but I would certainly appreciate any help. Thank you

@TheNormalUniverse 2 жыл бұрын

Thanks so much for the great video Holland! If you're interested in making another, it would be really nice if you discussed how to manage files. For example, how do I make a blank project and put it in the correct directory. I hear there is some kind of "python helper script" intended for this, but as a noob I don't know how to run a python script. Thanks again!

@GrimClock 2 жыл бұрын

Hello, when making it I was messing around with the python script and was getting weird results. I would look into make files and how it works with this project if you want to make your own. Or to check the forums.

@tarapattenden3238 Жыл бұрын

Thanks! Your explanation of the code is really helpful

@AngelRojas-iy6yw Жыл бұрын

Thanks for the video it was really helpful. However, I am wondering how to control the volume of the oscillator. I want to create a knob that controls the volume but I cant seem to find a function or anything else. Thank you.

@jenniferw8963 2 жыл бұрын

Thanks for this great video. What do you think about using the Arduino IDE for programming/flashing the Daisy Seed? Is it just as capable as Visual Studio / command line Make?

@GrimClock 2 жыл бұрын

I haven't used the newest version of the Arduino IDE but VSCode is better IMO. Arduino is great for making basic programs for supported mcu's. But as soon as need to work on a complex system it starts to fall apart. I think it is worth learning VSCode and Command Line since most other systems use it.

@phaandorpertwee6981 2 жыл бұрын

7:20 the AudioCallback function in the for loop what is size, where was it defined, what's its content and why does the loop stop when i equals size? I would expect this loop to run forever until i switch off the device. Oh and why is i increased of all things by 2?

@GrimClock 2 жыл бұрын

So I am going to generalize this, but here is a good forum post about Audio Buffers: www.logicprohelp.com/forum/viewtopic.php?t=125642 Basically the audio callback is defined somewhere in the Daisy's source code, but it is basically just a function that is called periodically at the right time. This is useful because the Microcontroller may be clocked at a different rate than the Sample Rate of the Daisy. Yes this will run forever until the Daisy is switched off. Which is fine, we want it to do that. If our synthesizers or audio effects randomly turned off mid performance they wouldn't be very usable right? lol Finally it is increasing by 2 because the buffer accounts for both the Left and Right Channels. Thats why we have Out[ i ] and Out[ i + 1] because those are the left and right output channels respectively. If you were to ask for in[ i ] and in[ i + 1] then you would get the left and right input of the Daisy. Hope this helps, I would look up more about audio buffers if you want a better explanation!

@carbonmike9372 Жыл бұрын

This is a great question. The answer is a bit involved, but bear with me -- let's establish some baseline facts, then the whole thing should make a lot more sense to you. (a): because you're dealing with a digital signal processor, the system is always handling things in batches. That is, EVERY digital signal, no matter what created the signal, is a list of numbers, and you never get all the numbers at once -- you get them in batches. (b): the code shown above is part of a +framework+. This means that there's some work being done elsewhere on your behalf, and all you need to do is plug in your piece to get the results you want. The job of this particular callback -- AudioCallback() -- is to emit a list of numbers representing a part of a signal -- for example, a sine wave, as Holland is doing. You don't generate the whole signal at once, and you never call that function yourself; the system (a.k.a. the "runtime") calls it for you. Remember, the system is going to be calling this function MANY times a second, so when you run the demo, you'll get a continuous sound from the output. But when you write DSP code, it's helpful to think of yourself as being in "bullet time" where you get to handle complex and fast-moving events one batch of numbers at a time. NOTE: in this particular instance, he's creating a sound source, not a sound effect. That's why he's ignoring the very first parameter of the AudioCallback() function, which represents a (digitized) chunk of the INPUT signal. If he were writing, say, a reverb unit, a filter, or a delay, then he would have to take that input signal into account. (c): the code inside the audio callback function is not generating audio directly. It's generating numbers +representing+ audio, which will then be fed to the Daisy's DAC (digital to analog converter) and from there to its outputs. The bulk of that happens outside the scope of your program; all you need to do is provide the correct numbers. And again, all of this happens fast enough that to us it sounds continuous. So to answer your questions: The loop inside AudioCallback() is only responsible for one chunk of signal at a time. The size of the chunk -- how many numbers it needs to either process or generate -- is the parameter. The function will get called again -- hundreds or thousands or millions of times, depending on how long the unit is switched on -- but remember, you're in bullet-time and just need to handle the next chunk. The size parameter is defined within the Seed code framework. If you dug around in the libraries long enough, you'd find the place where the code essentially says "call this function every X number of clock ticks" -- and "this function" would be something that looks like AudioCallback. The buffer index increases by two for each loop iteration because you are generating a stereo output, and left and right samples are interleaved in the output: [L R L R L R] and so on. Hope this helps!

@phaandorpertwee6981 Жыл бұрын

@@carbonmike9372 readily comprehensible, tyvm!

@carbonmike9372 Жыл бұрын

@@phaandorpertwee6981 You're welcome! (I'm looking to add one of these to my rack, so I've been doing the traditional KZbin Prowl, hahaha)