Any other FF PC12 Users here can help me clear this up?
So with my PC12 connected to either DT2 or DN2 there is some weird stuff happening.
some knobs seem to randomly affect other parameters in the devices.
like on the DN" if i turn the knob with CCs for track level, after a few turns suddenly the Sampleratereduction parameter jumps around, but only every couple other turns.
same goes for other parameters.
turning the knob for the filter freq suddenly randomly introduces strane high pitched ringing tones, couldbt find any parameter that gets affected.
on the DT2 it also suddenly leads to similar ghost stories, one of which is that on some tracks it starts playing back the sample in high pitched version when i release the trackbutton ( i made a topic about that here Weird DT2 Bug - weird double trigger - #6 by Watto)
i tried with the only other midi controller i have, novation launchkey with knobs and it didnt happen there.
so i figured it must have to do something with the Faderfox. I plugged it into my PC and checked its midi messages in MidiOX, but it seems to send just fine. i have no clue…
The problem with the double trigger of sample playback (playing the second sample higher) seemed to be mentioned in a couple of bug reports and was supposedly fixed. If this is on the newest version of the firmware you should definitely report it. You can find it mentioned in the release notes page for the firmware history and it says something about some people, sometimes were getting double triggers on dt2 when releasing the trig.
Unfortunately I don’t know why you’re getting transposed parameters. I would think if it were something to do with NRPN sending two parameters at once and all the time, then the impact would be much greater.
I might try assigning the cc which is giving you the problem, track level I guess, to a different knob and see if srr is still impacted. If SRR is currently mapped, i would set up a new template without it and try to determine if it has to do with both being assigned at once.
I couldn’t say which device is at fault, becauseyou said midiox says faderfox is not sending srr, correct? But dt shouldn’t adjust a parameter that it’s not receiving. I guess it could be a bug related to track level cc but you’d really have to demonstrate that it happens at regular intervals using a non faderfox controller as well, otherwise i just appears t be a problem with the faderfox.
Hopefully someone ese has better input than I do. Good luck!