|
Post by keurslagerkurt on Dec 22, 2021 16:15:28 GMT
Hey all! Been making a sequencer with the Pi Pico on my breadboard! This week i've been learning a lot about the Pico, and I wanted to learn more about its 'PIO' functionality. Which basically are some small CPU cores running alongside the main cores that can set output pins. I thought this would be perfect for a sequencer. This way, the clocking & triggering is done very precisely by a so-called 'state machine' in the PIO that runs completely independent from the main core. This makes it nice and stable, while our main core can handle inputs, the oled,.. A first, functional version is here on github: github.com/ZVanMoerkerke/PicoSequencerFirst version has 6 trigger sequencers to the output pins. Sequences can be arbitrary lengths. You can add probability to any trigger as well. I'm looking to also add: - Conditional triggers - Trigger repeats & microtiming - CV out - Interfacing with the OLED - Mute buttons .. In the future, I hope to make a PCB version of the Pico, but I still need to clear some things out. I also want to test it a bit more on the breadboard first, before I decide on the amount of inputs/outputs, pins,.... I also hope to make this code into a library in the future, to make it nice & easy to use! You can find a video here: www.reddit.com/r/EuroPi/comments/rm84y1/building_a_sequencer_with_the_pico/
|
|
|
Post by dizzeesatchel on Feb 11, 2022 0:12:16 GMT
Well i now have a Pico...no real knowledge but a bit of enthusiasm.. and i'm blinking LEDs! I have a little screen too but it's not an OLED so that bit of the code was throwing errors, so I just commented things out until it worked. It's a learning process
|
|
|
Post by pt3r on Feb 11, 2022 8:07:35 GMT
I have been writing complex sequencers with puredata but the logic is easily ported to python, in fact python is far more suited for that kind of more complex functionality, but i digress. The point I want to make is that the main success IMHO of a sequencer has to do with the interface, messing around on an oled is only advisable if you need to set specific values that you can not represent in an abstract way. The sequences itself are more easily entered/manipulated via a grid like contraption like the ableton push does or one of those akay grid controllers.
|
|
|
Post by dizzeesatchel on Feb 11, 2022 9:28:40 GMT
Oh absolutely! This is just my own personal curiosity and interest in the general goal of a potential multi-purpose Pico-based module. A trigger sequencer is probably the simplest thing to build to get things going. We're still dreaming of the Orca module...
|
|
chuck
New Member
Posts: 40
|
Post by chuck on Feb 11, 2022 14:43:59 GMT
I was using a teensy++2.0 as a keyboard scanner and midi controller and I fried my last one attempting to add a resistor ladder cv output circuit... The pi pico is so much cheaper and faster that I've decided to use it instead. Only problem -- it is 3.3 volts, not 5, and 3.3 won't make it through this old Casio key matrix. So I'm pumping up the voltage with some TL074s. Circuit isn't done yet, and when it is I'll replicate it on a strip board, but I'm liking the pi pico so far.
|
|
|
Post by rodney on Feb 16, 2022 8:50:51 GMT
I was using a teensy++2.0 as a keyboard scanner and midi controller and I fried my last one attempting to add a resistor ladder cv output circuit... The pi pico is so much cheaper and faster that I've decided to use it instead. Only problem -- it is 3.3 volts, not 5, and 3.3 won't make it through this old Casio key matrix. So I'm pumping up the voltage with some TL074s. Circuit isn't done yet, and when it is I'll replicate it on a strip board, but I'm liking the pi pico so far. <button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button> I am keen to get keyboard-building too!
We can compare notes!
|
|
chuck
New Member
Posts: 40
|
Post by chuck on Feb 17, 2022 2:27:27 GMT
Note CV and gate is pretty easy and the Arduino or c/c++ sdk libraries take care of the usb midi. I just got my hands on a fully-weighted velocity sensitive keybed from an old Rhodes MK-60 (actually a Roland) with two sets of contacts for each key and now I feel I just have to figure out how to do velocity too. Is the the pi pico up to it? We'll see! Will I fry more chips in the attempt? Almost certainly!
|
|
|
Post by keurslagerkurt on Feb 17, 2022 17:16:26 GMT
Well i now have a Pico...no real knowledge but a bit of enthusiasm.. and i'm blinking LEDs! I have a little screen too but it's not an OLED so that bit of the code was throwing errors, so I just commented things out until it worked. It's a learning process
<button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button> Awesome!!! Let me know if any part of any code gives any problems I find the Pico incredible & great fun, I think it would/will make for a great general-purpose AE programmable module. So I'm happy to see other people here picking it up. As pt3r said, for a sequencer the interface is indeed the most critical part. I think a Pico would def be able to handle the workload, but it would be quite an elaborate and specific design. Not really suited for a general purpose module that would not have eg 16 pushbuttons. I have personally not made the module into a PCB yet, I have been working on some other projects mainly (some not AE related, but some still AE related!). But I'm sure it will be a reality some day in the near future.
|
|