CV Quantizer

Comments (9)

• sergejauto · January 10 2020
  Hi, thank you for the device. Super useful. I noticed the min and max values are not being saved with the live set. Would you have an idea on how to fix that?
• sergejauto · January 10 2020
  hm, I take that back.. I think the problem is on my end. ha!
• haridaniel0 · February 04 2020
  Sorry for late reply, (I haven't got any email of your message). I am happy that it is works, and feel free to contact again of any issues, thanks!
• haridaniel0 · March 26 2020
  1.51 :
  - Multimap fixed
  - Added Dry/Wet
• Syn · October 07 2020
  Good stuff.
• haridaniel0 · April 30 2023
  1.52:
  - More precision: (CV Input dial value type changed Integer -> Float)
• bobbysh · May 16 2024
  Greetings, love the device, I use it all the time!
  I've noticed that any mapping after the top one doesn't work in Live suite 11.3. I'm an experienced programmer though very new to max, so I can try to take a look at it. But if you're already aware of the issue and have a fix that would be great
  Thanks very much
• haridaniel0 · May 17 2024
  Thanks Man!
  If you can fix it and send me back I upload it. But it should be backward compatible with 10 if possible. I am programmer also but currently doing other things in the World.
• bobbysh · May 20 2024
  The problem was that some objects inside the multimap bpatcher did not have the ~ at the end of the name (indicating that it's an MSP object that can handle audio rate signals?), so no data was flowing out of those objects. Changing the names fixed it.
  Not sure if it works with Live 10 since my installation of 10 is sharing the user library with live 11 and crashes when I load certain m4l devices including cv-quantizer.
  Also not sure how to get the fixed device to you