Device Details

I’ve been looking for the most elegant way to achieve this. Others didn’t work out because they had bloated UIs and other stuff that I didn’t need in a streamlined solution. Been searching this library for the last weeks, and then you upload this — thank you! Gonna give it a go.

Simple and useful.

Hey, the concept of the device seems great but I'm having a few problems, when I hover over the pitch wheel my mouse just disappears and it becomes unusable. Is it just doing this for me ?

@Shinwoir - I remember experiencing the same problem with Max plugins in the past, sometimes the mouse cursor disappears and I had to click on the plugin again to make it appear. I have never known what caused the problem but with the latest versions of Max it has not happened to me again.

@killihu okay thanks! Seems like it was resolved on my end as welll
Do you know by any chance if the knobs for the wheels could be automated on the playlist? Somehow when I click on them I don't get an option to, don't really know if it's possible I know nothing about M4L
Thanks for ur hard work btw

(seems like I can't edit my comment, but actually it works for the modwheel, not the pitchwheel)

@Shinwoir - To automate the Pitchbend knob use the "MIDI Wheels B" plugin.

PERFECT. Only problem is that I can't donate!! :(
I'd be happy to chip in $3, this device perfectly solved my problem.

I use this basically as a fine-tune add-on for the Simpler device.

TLDR: this is my favorite way to fix a sample that is slightly out of tune (ie, flat or sharp by +/- 50 cents). Because Simpler does not have fine tuning, and you don't want to use Sampler.


Problem:
- You're layering two one-shots: sampleC4 and sampleD4. You try using Simpler and a device chain to layer the sounds. You tune sampleD4 down 2 semitones in simpler (using the Transpose knob on one-shot Simpler mode), to correct the difference in root note. Hopefully, now two the samples are in tune with each other.
- THE ISSUE: sampleD4 is still out of tune, a few cents sharp actually. So when you layer the sounds, and play them in unison, they are slightly out of tune from each other (gross).
- You don't want to switch to a Sampler device just to do some basic fine tuning. You could manually time-stretch your audio file, but who has time for that (I'm lazy).

Solution:
- Virtually "freeze" and offsetting incoming pitch bend wheel value for all incoming midi notes. And of course, be able to do this in a device chain, ie, not globally, so that you can tune different instances of Simpler.
- So now, you add this device right before the Simpler device containing sampleD4. And adjust the "pitchbend" parameter of Midi Wheels 1.1, downward slightly (with the "Free" box activated). NOW, every time you press a midi note, Midi Wheels 1.1 will virtually 'lock in' the pitch bend wheel value, JUST FOR THAT DEVICE CHAIN.
- Now, you can layer a bunch of shitty samples you downloaded online, that nobody took the time to finetune, and quickly finetune them within your Live Set so that they all sound nice when in unison, all while using Simpler.

TLDR: this is my favorite way to fix a sample that is slightly out of tune (ie, flat or sharp by +/- 50 cents). Because Simpler does not have fine tuning, and you don't want to use Sampler.

Hey there, love the device. Small request, can you please make Pitchbend key assignable on MIDI Wheels A. device? Thanks in advance.

@njassal - You can use the MIDI Wheels B device to assign whatever MIDI control you want to the Pitchbend control. Click and drag on the control below the Pitchbend knob to select it.

Nice one, thanks dude!

This is great. The only problem is that midi wheels blocks some data. It blocks program change msgs and some other stuff i cant remember.

Can you please fix it ?

@FloorForce - Device updated.

uau that was fast. thanks!

Mapped the Octave control to a macro and it works in reverse--turning it up decreases the octave and turning it down increases the octave.

@cparadisi - The control used for transposition (live.tab) has the minimum value at the top position and the maximum value at the bottom position. So I had to invert the output to display it correctly on the device.