+- XOR Userforum (https://forum.xor.eu)
+-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6)
+---- Forum: Nerdseq issue / bugreport (https://forum.xor.eu/forumdisplay.php?fid=8)
+----- Forum: Beauty and less important bugs/glitches (https://forum.xor.eu/forumdisplay.php?fid=16)
+----- Thread: Strange MIDI CC Recording Behavior (/showthread.php?tid=1544)
Strange MIDI CC Recording Behavior - RMBLRX - 03-04-2023
I have a project wherein I'm trying to record a few CC values per channel. I have four MIDI channel inputs set up to record and most of those channels have presets set up like so:
- CC01
- CC02
- CC03
- CC04
- CC40
- CC00
- CC00
- CC0A
I send no more than three of the first four at a time and really don't change anything else at all on any given step, and though the NerdSEQ passes the information correctly, it doesn't record correctly. What happens is although it seems to record the CC messages correctly (hard to confirm but it's definitely receiving a great deal of changes), it records them all as CC0A in all three columns on all four tracks, which is confusing to say the least since I'm not even making any control changes on that particular one.
RE: Strange MIDI CC Recording Behavior - RMBLRX - 03-05-2023
This is the latest firmware, by the way, but it seems to go pretty far back in different firmware versions (at least since June 2021 actually), though I apparently hadn't noticed exactly this issue. Today I wondered if it might be because all of those projects were derived from a single template project, and so I made a completely fresh project and noted exactly the same behavior. It also apparently has nothing to do with the control presets--given that it records the CC directly instead of under a given preset, but also given that it persists even with that eighth preset altered--so that it happens to correspond at least seems a coincidence.
RE: Strange MIDI CC Recording Behavior - RMBLRX - 06-09-2023
Any chance of getting some feedback on this? If it's my error, I'd love to correct it. If not, I'd certainly appreciate knowing whether it's a known issue or any case whether it's being investigated. What could possibly make every CC record as CC10?
RE: Strange MIDI CC Recording Behavior - XORadmin - 06-09-2023
Oh...I missed this one! I will check it out and get back to it. It should record correctly (if possible within the fx columns) of course into each separate track and its pattern.
RE: Strange MIDI CC Recording Behavior - RMBLRX - 06-14-2023
It does record into separate columns and within each separate channel, etc., it's just that every single instance records as CC10, despite never sending CC10 and despite correctly passing the correct CC values during the recording process (and apparently recording the values of each control change, just not the correct designation).
RE: Strange MIDI CC Recording Behavior - XORadmin - 06-15-2023
I finally could run a test. And I think it works correctly.
CC A is the FX command (one of 8 possible CC at the same time, could be CC B or CC E or whatever. It doesn't mean CC10.) -> Control Change Free
It contains the CC number as well as its value as the payload.
I can't find any undesired behaviour here.
Sorry for the long delay. I am back to normal now..
RE: Strange MIDI CC Recording Behavior - RMBLRX - 06-15-2023
Oh, that's confusing since they're listed in setup as 1-8, not A-H--as I see is indicated in the documentation, which I'll include here for reference:
Quote:CC A..CC H→ Free assignable Midi CC. As the Midi controller numbers for CC#1..8 are
fixed and must be set up in the track settings. These controllers can be freely assigned.
The first 2 digits XX00 set the controller type/number and the 2nd two digits the value.
The main difference to the first 8 controllers is that the first 8 controllers can be used also
for the Automators and other channels while the controllers 9..16 can freely be assigned in
the sequence.
What's more confusing is that this doesn't really indicate this recording behavior to me. I presume then that it is not capable of recording CC1-8 directly (instead only as A-H), but this still doesn't explain why it seems to record only CC A in all columns no matter what I send. As in, I'll typically be sending anything between CC1..4--or at least any three of those and up to three of them simultaneously--and expect them to either record as what they are or, going off the documentation, their particular assignments (CC A..D), but this is not what happens: instead it records as many as three different values simultaneously as CC A, which shouldn't be possible unless it's transcribing the assignments to CC A in error (I've attached photos to show what's happening, and those rows represent a single pass in recording).
I guess I'm also not clear on what we're counting as 'working correctly': Should I be able to record CC A, CC B, and CC C presets simultaneously and expect them to write into the rows as such? If so, I'm not seeing this behavior, even though I know for a fact that I'm sending the correct values, because the NerdSEQ passes them correctly while live in the process of recording.
RE: Strange MIDI CC Recording Behavior - XORadmin - 06-18-2023
Sorry if it is not clear.
Forget about the A to H which is just another indicator for 8 Possible CC controlled at the same time if you use a patch for example. Not more. If I would have named then 1-8 then people would think it is CC1 or CC6 or so which is not the case. The CC number is in the payload.
It doesn’t need to record anything different than the first CC A since the controller number and the value is in the 4 digits. Using CC E or CC G wouldn’t make any difference.
In both of your pictures I see you recorded CC1, CC2 and CC3, these can be also CC25 if you used a controller number 25 to record from.
Playback will be just what you record as long as it fits into the columns.
The other CC FX commands you refer to are CC presets which are used for automators etc because automators can’t route to a specific payload (like it would need 1 byte for the channel and one for the CC number. Instead the 8 presets are there which already contain the channel and cc number.
Trust me, it works and does exactly what you need. I will check in the manual again if it can be explained any better.
RE: Strange MIDI CC Recording Behavior - RMBLRX - 06-18-2023
Ah, I see. I was falsely equating "CC A..CC H" with "CC#1..8" and for some reason this was throwing me off regarding "The first 2 digits XX00 set the controller type/number." Thank you for clearing that up. This would indicate then that it's recording just fine and that my issue instead was in playback (which was originally my issue until I had that confusion over CC assignments), but lo and behold, all my recordings seem to work perfectly all of the sudden(!), which might have indicated to me that the issue was somewhere in my signal chain if I hadn't previously tried bypassing my MIDI interface and DAW (as well as noting correct behavior live during the recording).
Now I'm both frustrated and excited, because everything is apparently working completely as expected, but I have no idea why it wasn't before. Anyway, thank you so much for your patience. If I run into the issue again, at least I'll be able to assess with a better understanding what is not causing it to happen. This should also help me to move on with my work, which is pretty exciting.
RE: Strange MIDI CC Recording Behavior - XORadmin - 06-18-2023
Good to hear. And of course if there is another issue coming up, let me know! My goal: everything works as expected :-)