fbpx
Skip to main content

MIDI Forum

Notifications
Clear all

Midi Vol Node CC#87

6 Posts
3 Users
0 Reactions
12.5 K Views
Bob
 Bob
Posts: 3
Active Member
Topic starter
 

When saving a Type 0 SMF my Technics KN6500 adds an event to each track that I can see using a third party MIDI editor.

The controller is named “Midi Vol Node” and uses CC#87 set at the same value of the channel's CC#7 (Main Volume). I have not heard of Midi Vol Node before, it doesn’t seem to do anything.

I am presuming this is a Technics thing that would not usually be seen?

Would be interested if anyone can throw some light on this.

Thanks.

 
Posted : 08/11/2020 1:52 pm
Geoff
Posts: 1041
Noble Member
 

As you would suggest, I'd guess that this is a Technics 'thing'.

The lists that I have refer to CC87 as Undefined, as are the other CC values either side of this. They are therefore available to be used for whatever, and they should not interfere with anything else. Careful reading of Technics manuals might reveal the intended purpose.

Any device that receives such a code that does not know what to do with it should merely disregard it, so it should not cause any problems.

I'd be interested to see a midi file that has this code added. Firstly it would be interesting to see exactly where the code is added relative to other 'normal' codes. Secondly it would be interesting to see how other systems describe it, i.e. do other systems describe it as 'Midi Vol Node'?

Geoff

 
Posted : 08/11/2020 4:19 pm
Bob
 Bob
Posts: 3
Active Member
Topic starter
 

Thanks for your reply Geoff and apologies for the delay in getting back to you about my arcane question!.
Have done some further, let's say "experimenting", and have determined the following:-

• cc87 is written to a type 0 midi file (and is always set to a value that matches the adjacent cc7 Vol control, per track,) when the file is saved by the Technics KN6500

• If there is no pre-existing cc7 event present on the track then the KN6500 does NOT add one of its "own" cc87 events.

• The cc87 event can NOT be seen when interrogating the KN6500 on board sequencer in edit mode.

• The cc87 event CAN be seen to exist when viewed in a Third-Party editing programme, in this case PowerTracks - see the pic with the event highlighted by the yellow arrow.

• A lot of midi control messages, including cc87, are dumped to the track header, (all at 1:0:000) if the keyboard's "Panel Header" mode of saving is utilized. This stores all the keyboard settings and are assigned to the various cc#s you can see in the other pic attached and includes solo settings. sound DSP, portamento settings, EQ, bend sensitivity, key shift, modulation, filter resonance, drawbar settings and all that lovely stuff that effectively "screenshots", in MIDI, how the keys were set at the time of saving. Interestingly, as you may see from the pic, none of the controllers are named other than the usual suspects, plus the mysterious "VolNodeCtrl".

• cc87 is recognised by the KN6500 but is not transmitted.

Have searched for a Technics MIDI manual but to no avail as far as cc87, or rather Technics use of it is concerned. I Googled it all again tonight and got a bit excited when I found a search item that read "Midi Vol Node cc87" only to find that it was pointing at this thread!

The only "volume" related aspect of the keyboard's physical controls that I can see that might be relevant is that the volume output control for the sequencer is independent from the machine's main volume slider. However, moving the sequencer slider will produce matching movement on the on-screen virtual slider for Auto Accompaniment, if it is turned on.

So.... I'm going to take a bit of a stab in the dark and attempt to answer my own question! Technics use of cc87 Volume Node Control communicates a dynamic level control to its own Autoplay Chord system where a midi file is in charge of the accompaniment patterns, but also (possibly unintentionally) pops a cc87 into a track if it finds a cc7 present in a standard midi file being saved on the Technics.

Unless someone out there actually knows?!

As you say Geoff, any other device is going to ignore an unspecified controller and I guess that's the point, it gave, and gives, other device manufacturers options. Although in this case the allocation of a controller name gave me the impression it wasn't unspecified, hence the question.

 
Posted : 14/11/2020 3:50 pm
Geoff
Posts: 1041
Noble Member
 

Thanks for the info.

As you've not sent a sample midi file, I'll suggest that any other system looking at such a midi file will merely report 'Unspecified Controller', or maybe 'System Specific Controller', and any device actually playing the file would just disregard it as it doesn't know what it is and what to do with it.

Geoff

 
Posted : 14/11/2020 4:43 pm
Michel
Posts: 1
New Member
 

Controller 87 is also ued by Yamaha as a volume control but I really don't know what it does. I'll try to look into it. It's not documented by Yamaha at all.

 
Posted : 03/12/2020 7:12 pm
Bob
 Bob
Posts: 3
Active Member
Topic starter
 

That's interesting Michel.

If I manually create a cc87 in PowerTracks Pro Audio 2019 the event window automatically assigns "VolNodeCtrl" to it. When I do the same in a classic version of Power Tracks (from 1992) it just shows it as "Control".

It would appear that "VolNodeCtrl" may be a PT thing, but like you say with Yamaha, there seems to be little information.

I'll ask the publishers of PT, PG Music, to explain what it is about, although I am not holding my breath as there is nothing about that I can see, in the PT help file.

Will report back ~ I may be some time...... 😉
-------------
PS - Geoff - How do I attach a midi file in here? I have tried, including .zip, but can't get it it to attach? I just see an unsupported format message. What am I doing wrong?

 
Posted : 07/12/2020 2:34 pm
Share: