Actually, this sounds like a fun project! I’d likely update Wav Bank MC, since it’s already a bit more advanced than the Wav Bank, and has an easier front panel design to work with. I’ll try to get this done quickly for us.
1 Like
Absolutely!
1 Like
Here’s how it’s shaping up @fiddlercrabseason 
Clearly a lot of widgets are missing. It’s a challenging panel to design.
1 Like
Looks clean and sensible.
Is that ‘division’ parameter I see going to be an “EOC divider”?!?! 
It’s something that I’ve been thinking of!
The ”division” output feature takes the sample length and divides it by some constant that’s set in the content menu. Maybe that defaults to 32. Whenever that playback location in the sample is reached, a trigger output is produced on the division output.
Is that 
an EOC divider? If so, yay! 
suggestion…
Rather than making that ‘division’ param an output that’s a context-menu-assignable division of the EOC output, make that ‘division’ param a KNOB, that assigns the division of the EOC output itself.
So at value of “1” EOC trigger is output at the end of the entire sample. With division at value of ‘2’ the EOC ouputs triggers at 50% and 100%. At “3”, EOC outputs triggers at 33.33%, 66.66%, 100%, etc…
MAJOR bonus points if you can also crowbar in a ‘division CV input’, so one could change the division on the fly. 
1 Like
Damn, it’s a good suggestion. How in the world am I going to fit all that on the panel? 
Ha ha ha. Give me a little while. I’ll see what I can do.
Hmm… I might not earn bonus points this round. Let’s keep this feature in mind? My goal is to have the updated module submitted to the VCV Rack library within the next few hours, and I don’t have the mental energy that would be required for the panel update. 
1 Like
Totally understood. I’ll throw this (janky) mock-up out there for future consideration…
You. Are. Awesome.
Cheers!!
Yay! Ok, we’re good to go. I just need to test, then I’ll get it submitted. If we’re lucky, it should roll out between Christmas and New Years. (I don’t have control over the Rack library release cycle.)
4 Likes
!!
Ok, that wraps it up! I’ve submitted the updates to the VCV Rack library. It, and the new Maya modules, are both in the queue to get released. Thanks for suggesting these updates, @fiddlercrabseason 
2 Likes
Looks amazing!! Will be a go to sampler for sure! Does the pitch range include up and down from original rate? Looks terrific! Happy Holidays, your VCV modules look so fun in the holiday art poster. I think GrooveBox would look sweet with those other designs, your modules are future retro fun,
1 Like
Thank you!
Oh, I probably should have tested that. Only up, but once it comes out, I’ll patch that and make it an attenuverter. Obviously I rushed these updates out the door. Ha ha ha. 
2 Likes
Wow so much has changed in like one day, this rules dude!!!
1 Like
Thanks for this WavBankMC update. It’s going to be great!! But there are a few wrinkles to iron out:
-
EOC/Division: EOC w/ division value “1” does not produce a trigger when looping is enabled, but does produce the subdivision triggers - and ONLY the subdivision triggers – w/ any division value >1. ie, selecting “3” will produce triggers at 1/3 & 2/3, but NOT at 3/3. With looping disabled, all 3 triggers in this example are produced as expected. (Also, FWIW WavBank’s EOC doesn’t seem to be working at all).
-
Attack/Decay time: Decay time values seem to be reversed. ie, decay time value of “0” (minimum decay time) fades out, and decay time value of “1” (maximum decay time) ends abruptly. Attack time behaves as expected.
-
Pitch scaling is wildly different compared in WavBankMC vs WavBank: In WavBank, unity is 0v, and the range is scaled -5/+5. In WavbankMC, unity is 5v, values are scaled 0/+10. For example, to detune both modules to the same pitch, I detune WavBank to -1.13333v and WavBankMC to 0v.
Also discovered this morning - with BOTH WavBankMC and WavBank - that mono .wav files are not loaded and show as [empty].
No worries, I’ll get these fixed today.