(3.2.2)Bug Report: FullBoar midi-notes wrong count

SfeerPeerSfeerPeer Registered User
Name: Peer
Date: 2011-11-15
Software Version and build number: 1.8.1 / 3.2.2
Number of displays: 2int + 1ext
Connected USB Devices: keyboard + touchscreen
Networked Devices: none

Detailed description of the problem including instructions to reproduce (if possible) and exact syntax used:

Today I was trying to set-up midi with a keyboard-player to start my que's through his keyboard. We did it completely like the WH-GM-Midi-Imp.pdf
Everything works fine BUT:

* if I select a midi-ch > "desk-playbackbar" all midi-notes are off by 24-notes, so if:
M8 'go' is "note 5" (= F0 on keyboard), but should be "note 29" according to midi-manual

* midi-ch's pull down > macro's: macro's won't work, maybe I'll have to add 24 notes in the list?


To me it looks like the midi-receiver in the desk is not starting at the same 'note 0' as the keyboard does.
Is there a way to see / adjust this?

thx,
Peer



List any errors reported by the software: none

Comments

  • Unknown Users Awaiting Email Confirmation
    edited November 2011
    Can you use the MIDI viewer ( [Open][MIDI] ) to look at the actual notes coming into the console? What do you see?

    Many MIDI keyboards have a "Transpose" function that let you shift the note scale.
  • SfeerPeerSfeerPeer Registered User
    edited November 2011
    Hi Eric,

    did't try that, and keyboard is in the studio right now. Will have a look next friday, thx
  • AndrisAndris Registered User
    edited November 2011
    Definitely looks like the keyboard is transposing by 2 octaves. I just used MIDI triggers on 3.2.2 with note 0 triggering a playback bar flash button and I had no issues.
  • Cmy.dkCmy.dk Registered User
    edited December 2011
    Andris

    Could you please explain to me how to get started on this ?

    Regards Johnny
  • SfeerPeerSfeerPeer Registered User
    edited December 2011
    it is indeed the 2 octave thing, thx
Sign In or Register to comment.