Hi Club Ample,

Are you actually saving your midi mapping or are you just closing Scratch Live? To prevent the hassle of having to MIDI assign everything again the next time you have a gig go to the 'setup' menu and click 'MIDI'. Here you can create a new MIDI template file that will allow you to save and load your MIDI presets. Make sure you create a new preset BEFORE you start MIDI mapping so that when you are finished there will be a preset to save to - just clicking 'new' will wipe your current MIDI settings.

About the Video mapping, which parameter are you trying to map? It could be a bug in your Scratch Live version, but I'm not sure. I would recommend you upgrade to the latest version of Scratch Live (2.4.1) and see if this helps at all.

Cheers

Ok problem 1 solved... I was not saving it....i am able to save and reload the saved settings..

should it load the 1st saved midi setting when you open serato?

lets say i had 3 saved settings
NANO2
DICERS
62
would it load any of those 3 when i open serato each time..or does it just open to default/no assignment.

----------------------------------------------------------------------
------

With respect to the video mapping... i am trying to map the rotary encoder that determines the level of video effect...(right next to the on off button for each effect). first you select the effect you want and then on some of them an effect level option will show up and you can increase or decrease the effect with that rotary knob. they look exactly like the master volume knob. (i wish i could add a pic in here.)

the midi note that works with the master volume and every other knob in serato is "relative signed bit".
RSB works fine with the SP6 volume levels... the individual channel videos .and. it works with the internal effects levels.... everything except in video.

and yes im running 2.4.1 .... i have not tried it on older versions... but its the same on 2.4.2 beta

It defaults to the last saved MIDI assignment that you had before you closed Scratch LIVE. So if you were using your MIDI preset "DICERS" and then closed Scratch LIVE, the next time you open Scratch LIVE, the DICERS preset should be active (provided you have your midi controller/dicers plugged in).

As per your video question, that is still a stumper, as i also have a NanoKontrol 2 here and when i map one of the knobs to the effect level knob i get a smooth transition, it doesn't jump around at all. Have you tried another midi controller, mapping it to the same parameter?

If you are able to take a short video of the "jumping around" to explain what is happening I will look into this further, as it sounds like a weird phenomenon that is definitely not meant to be happening. But at the moment I would try:
•Try using another USB cable for your NanoKontrol,
•Try using a knob from another midi controller to check if it happends with another unit

Let me know how you get on :)
Cheers

I tried a different usb cable (even though the nano says "ONLY" use the usb cable that comes with it) lolol... anyway there was no change in the behavior

i also tried everything on a PC instead of the MAC.. and i got the exact same behavior.


other midi controllers

xone 4d....
the endless spin "rotary encoder" knobs will give a similar jumping around
the "rotary potentiometers" which have a 0-127 value work fine
the sliders which have a 0-127 value also work fine

the RANE 62 itself ..
i tried mapping the session in and out knobs, MIC EQ knobs etc. and those worked fine

i will try to make a video this evening.

So you have tried more than one computer, more than one USB cable, more than one Version, and more than one Midi controller....

hmmm.. the only thing this narrows it down to is the nanoKONTROL itself being defective. But if this were true, that would mean that you wouldn't be able to map it to any parameter without it doing the same thing, but you said if you map the rotary knob on the nanoKONTROL to something generic like a DJ-FX knob or something it works fine?

Im so confused as to why this is happening, and I'm sorry you are having this issue but hopefully we can find out what the culprit is soon.

Exactly.. it works on all the other knobs within serato... except within serato video.

I just hooked up my SL3 and ran 2.3.3 to eliminate the mixer and 2.4 as a possible problem as well.
SL video looks a tad different but the same type of knobs are in there and the same problem persisted there too.

Granted it seems like its pointing to the nano.. but as you said why would it work with the other knobs like DJ FX and master output.

I also tried the nano itself with other midi mappable software and it worked ok with those.

youtu.be

Thanks for the video mate, really helps me out. However its still a mystery as to why this is happening.

Are you able to download a free program called Midi Monitor for mac, here is the link >www.snoize.com

If you run this while Scratch Live is running and your nanoKONTROL 2 is connected, it will display the midi messages that are sent through the controller.

If you can map the knob to the controller, and start to turn the rotary encoder on the nanoKONTROL, what midi messages do you get? There should be values in Time/Score/Message/Channel/Data.

Since it is a rotary potentiometers you will get value from 1-127 as you turn the dial, but what I'm wonder is if the "Channel" has been messed up.

Run MIDI monitor, play around with the knob mapped to the video effect knob, and then maybe send me a screenshot of the MIDI Monitor page?

Cheers

Tried to make a video of that too

youtu.be

Thanks mate that really helps me out.

There are a few reasons why this could be happening by looking at your midi monitor,

The first thing i noticed is that when you click "MIDI" in Scratch LIVE, and click the Serato Video knob you want to map, when you get the 'Green screen' to indicate you have mapped the parameters correctly, I see in your video you are in Absolute mode, try pressing the "C" key to toggle through the different midi mapping modes and see if any of the other modes help?

I have tried that... none of the other modes work either.

Sooo.. I have just been talking to some developers around the office, and we have established that this is a bug within the Serato Video plugin. The rotary potentiometers on your korg nanoKONTROL always send relative midi data, and a controller with this single midi send seems to mess up the controls inside the serato video panel.

You can tell that the nanoKONTROL has relative encoders as in the video you sent me the midi values jump from 1 to 63 to 127 then back to 63 then back down to 1 etc. What should happen when you turn the knob you should get a value change on each resolution (1,2,3,4,5....124,125,126,127).

So when you tried your other midi controllers (Xone:4D/Sixty two) they send an absolute value and so Serato Video bug won't affect it.

We are sorry you have experienced this bug, but I will log this as a bug report and let the developers know about this issue.

Cheers

Does that mean it would be addressed in the next update of Serato Video?

SV was the main reason i purchased the nano :(

It needs to be logged into the bug system before our developers can start to work on a release where this is fixed, so at this point I am unable to say if or when it will be fixed.

Sorry to be vague but this is all the information I have at this point.

Do you mind me closing this thread as bug logged?

Cheers

Thanks for your help and responses.

Feel free to close it

Thanks mate, hopefully we get this resolved soon.

Take care,
Scott