PlanetZ forums - scopeusers.com

Hi,

I am having this problem where Uknow patches get corrupted when loaded into Midi Mapped device.

I assign the controls of my nanoKontrol (uSB connected / via Cubase) to the Unknow via the scope learn - and save the mapping in the MIDI mapping folder ....

Then when I load the project (and later try to load patches) - the Uknow is "corrupted" in a way that the values of the knobs dont correspond to their graphical position (going over all of them and tweaking +- one step restores the patch and sound) - the knobs (at least raphically) correspond to the patch info ....


now, when I reload a new Uknow - or a "blank" midi settings template over the Uknow - and then load the patch - all works fine ....

This is not a HUGE problem - but has me needing to delete my controller assignments (besides teaching me to save every patch as a preset) and remap them (or fix them) every time I open a project .... which kindof sucks ...


Anyone familiar with this and know a workaround ? (I havent tried this with many other synths - but I think this might be a common problem ...



Thanks

I have the same problem. I have tried with another synth (profit 5) and it seems to work. Perhaps it's Uknow not working with midi controller.

Yeah. So far i found it to be a combination of mapping the knobs to midi parameters - and not having any cc midi data recorded to output to the shnth ... So some parameters get zeroed (and sometimes even moving the knobs doesnt "unzero" them ... Happens to me with the osc mix knobs mainly ....)

My workaround (in cubase) was to give priority to automation recording and not "part recording" (recording cc information in a part) - and not having any knobs that are unmapped and dont have midi data (i map just before i record automation ...)



This could also be due to my choice of CC# (the problem happened when i was using CCs 14-20.

Im saying this because the ThreeOThree synth (for example) comes pre-mapped (CCs 74-77 or something) and never has those problems ...

A small thing to wonder about maybe - is that the UFlo has EXACTLY the same problem &

I thought I remember someone having an issue like this...and they mapped the MIDI patch to a MIDI bank/prog change.

So when they loaded a new SOUND patch, afterward they reloaded the MIDI patch. It may have been the opposite (load MIDI then SOUND).

Then you can always do something with hardware or software to get the program change sequence correct and automated.

Doesnt matter, my guess is that as soon as you hit play, uknow "gets"/"reads" the "no midi data" as cc=0 and zeros the parameters (without changing the actual graphical knobs)

Most of the times with uknow - just going over all the knobs and moving them up one tick and then back down will remedy this - but sometimes when this happens with the psc volume parameters - the knobs dont change the state or soemthing (i just get no sound whatsoever - even after changin all the knobs ...)