Enabling Discussions for Microgroove

[afternoon]

Microgroove is a really small, new, unfinished project. There's a lot of stuff I haven't documented yet. I thought Discussions might be a useful tool to get feedback and see how I can improve the project.

Please leave feedback, share ideas and ask questions. I will try to get to them as quickly as I can.

Ben

[smutax]

Hi
You've done a grand job! Hope we continue to discuss it here, instead of me bugging you via email 😂. I will, at some point, try to mention Microgroove in the discussions of other repositories, if you don't mind. Cheers.
ViBe

[afternoon]

I was going to email you to say the same... 😍.

The nice thing about discussing stuff here is everything is archived publicly for other people.

And please do mention Microgroove in other places. Thanks for your support!

[smutax]

Hi
Looked in issue #13 ...
Could Param: 3. INST = BD | SD | HH | ALL be used in conjunction with the workaround you suggested in the email? If i understand correctly, INST can be set to only one of 3(or all)? So it can be 3 Grids machines, each on different midi channel, each only generating for 1 instrument?
Thanks
P.s. silly question...What's better for you, to get few questions same time or space them out? 😊

[afternoon]

Could Param: 3. INST = BD | SD | HH | ALL be used in conjunction with the workaround you suggested in the email? If i understand correctly, INST can be set to only one of 3(or all)? So it can be 3 Grids machines, each on different midi channel, each only generating for 1 instrument?

Yes, that's the intention, except that when I implemented it I forgot to add the ALL option. I've reopened #13 and will add that.

P.s. silly question...What's better for you, to get few questions same time or space them out? 😊

Either. Feel free to dump questions in. One question per post would be great, so the discussion stays easy to follow.

[smutax]

Yes, that's the intention, except that when I implemented it I forgot to add the ALL option. I've reopened #13 and will add that.

Ok. I will try that then. Thanks.

[smutax]

About midi clock. Why couldn't, Microgroove or underlaying Pico, generate and send own midi clock?

[afternoon]

No reason why Microgroove can't do this. RTIC on top of the hardware timers would probably do a fine job. The required code changes would be simple. On firmware/microgroove_app/src/main.rs#L216, we handle an incoming MIDI timing message. Firing the same code in a scheduled task would implement a clock. The device would need a few more UI elements: a play/stop button, and a way to set tempo.

[smutax]

Superb! This would remove the need for "master sequencer".Not to say that option to sync to incoming midi clock is bad. The 4th neokey button could be play/stop or 4th tactile switch. Maybe even add more buttons to a design adding "tap tempo". Maybe hook up the function to existing rotary encoder taking advantage of built in switch. I guess there are ways around it. Since I'm here, was thinking about future functionality ideas, like "midi cc modulator/lfo", another one, track tempo divider/multiplier. Thanks.

[smutax]

The thought on the repo. As the project develops, the readme unlikely to become shorter. 😉 So why not take advantage of repo wiki section. Or maybe spread it across few readmes placed in different sections of repo. Just a thought. Goodnight.

[afternoon]

This is a good and true thought. It's on the list!