Voxglitch Groovebox for VCV Rack - Tutorial 

I have had some requests to improve the clock response, and I have it one my to-do list! See: voxglitch.canny.io/admin/feedback/feature-requests/p/improve-trigger-voltage-range-of-all-modules

Audio out appears to be broken in the latest Windows build (2.18) Both from individual tracks and from Mix out.

@@twatmunro I'll get a new build out today. Apologies! I'm not sure what caused that.

@@voxglitch4629 -- It seems to be a compatibility issue with my drivers. I use a MOTU M2 and in the past, it didn't matter what the driver sample rate was set to, the samples would just play fine. Now though, if there's a mismatch between the sample rate in Windows and the Sample rate of VCV rack, Groovebox goes silent. (So, if the MOTU sample rate in the OS is set at 48k, but VCV rack is set to 44.1k, nothing comes out of Groovebox.) Everything else is fine, it's just Groovebox -- and earlier builds were fine as well. It's not so important now I've figured out a work around, but it's been driving me nuts for weeks.

@@twatmunro Thanks for the info! I've recently had to strip out some of the de-clicking code. Not only was it buggy, but it was causing some unintended side effects for drum sounds. What this means in the short term is that modulating the sample position might lead to clicks, but that's about it. That build will probably take some time to roll out. There seems to be some delays in getting new versions out. I'm glad that you found a work around!

@@voxglitch4629 -- 2.19.0 is totally solid. All behaviour back to how it used to be. Thanks for the update.

I'm a gothic, tattooed, piercing riddled person on the inside! Ha ha ha. But there's no escaping biology. :-)

Sorry that I haven't updated the tutorial video to include the expander. The expander doesn't output audio. The outputs of the expander are trigger outputs, not audio outputs. I'll try and follow up soon to a new tutorial that includes the expander, but I'm currently making improvements to the groovebox module as well and want to wait until that's complete so that I can cover everything at once. :-)

@@voxglitch4629 -- OK, I kinda got that, but regardless of what's going on, I couldn't get any signal at all out of the trigger outputs. I assumed it should just go after the groovebox -- but after I wrote this comment but before I posted it, I decided perhaps I should try putting it BEFORE -- and now the damn thing is a revelation. You probably need to give people a clue about that somewhere on your manual page though. It's really counter-intuitive. All the other expanders I ever used, the expander came after the main device.