Are there any plans for future development to include features like Vintage Knob?


The strength of software is that the sound is stable.

Is there a way to turn off the UI keyboard display?

I thought it was over a couple weeks ago? I just bought the TAL Juno yesterday but I would've gladly gone back and bought Hive since Pigments is pretty much impossible to play in real time on my Mac mini heh.

I just purchased this last night and I'm really looking forward to using it!

"Practically yesterday" was a figure of speech, meaning "recently".

Check kvr, I ask this question there
Basically, vintage knob already implemented and it working amazing

No problem here- trash trash can works for me

This is just wrong.

Thank you!!!

Well with the advent of the M1 Apple chip that's no longer so straight forward. It's going to be pretty difficult to beat the performance it offers at that $899 price point that it's at right now. The M1's performance is pretty impressive and something like the current gen Mac Mini is silent under load which makes it perfect for music. The jury's still out since the platform is new but I don't think you'll be able to match it right now going the PC route. Not at that price point anyway.

sorry for the delay, fun with COVID.

I wrote a random autopanner (in Reaper JS) that I wanted to be deterministic for the same reasons.

the way I solved it was by caching a large number of random numbers upfront, based on a user seed parameter, and then sampling them from this cache based on the bar/beat position, sorta like an audio track.

that works great for that effect but isn't very elegant. caching a small number of random numbers on-the-fly every beat (using the bar/beat + user seed as a pseudorandom seed) might be a better solution.

depending on how randomness is used in an effect or instrument it could be a bit of work, but it's a worthwhile goal in my opinion, and once solved can be reused with new projects.

.. the one catch is if the user moves the performance in the timeline, then obviously the recorded bar/beat and the playback bar/beat are now offset, so the randomness wouldn't be correct anymore.

I'm not sure what the solution there is (need to think about it). it just occurred to me though that if the effect could output its used random numbers (or maybe just the on-the-fly seeds) so they could be recorded along with the performance eg. as MIDI data, and then consume them on playback, then playback would always be correct no matter how the recorded track is adjusted. (well except for time stretching, but changing randomness there is fair enough imo).

something like that might be the best/most transparent solution.

EDIT: or could the internal parameters that are being randomised be recorded as automation data, and then played back as recorded (without additional randomisation)? you could then have a 'Random SYNC' GUI button that when enabled follows the recorded automation, or otherwise freely randomises again. that should even work with time stretching.

so for example random oscillator drift would get recorded as pitch automation per voice, so would always play back the same way.

(exposing it as automation data would also allow users to mess with internal parameters like that indirectly which could be fun).