Harrison Mixbus Forum › Mixbus User Forum › Mixbus Support (Windows) v
[SOLVED] Mixbus 8.1 - GM Midi Track stuck on drums

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
[SOLVED] Mixbus 8.1 - GM Midi Track stuck on drums
English Guy Offline
Junior Member
**
Posts: 42
Threads: 5
Joined: Jul 2017
Reputation: 1
#1
08-24-2022, 03:07 PM (This post was last modified: 08-25-2022, 10:08 AM by English Guy. Edit Reason: change to solved )
Hi

I am just trying out the new Mixbus 8.1 demo on (windows 10) with a view to upgrading.  When I create a midi track with the GM synth it is stuck on drums.  Using the change patch doesn't change the patch.  I tried changing the midi channel to channel 1 but this does not change the behavior. 

I went back to MB7 and the midi track is created defaulting to piano and there is no problem changing the patch.

This is a show stopper for midi programming.  Advice appreciated please. 

(Specific version: Mixbus 8.1.378
(rev 8.1-378-gd69ff4cf6c)
Intel 64-bit)
Find
Reply
Dingo Offline
Moderator
*****
Posts: 3,102
Threads: 54
Joined: Oct 2013
Reputation: 170
#2
08-24-2022, 05:18 PM (This post was last modified: 08-24-2022, 05:52 PM by Dingo.)
Just tested using Mixbus 8.1.376 ARM 64-bit and have no issue switching channels and instruments with Generic MIDI.
Double checked with Intel build and also plays GM MIDI fine.
Macmini 8,1 | OS X 13.6.3 | 3 GHz i5 32G | Scarlett 18i20 | Mixbus 10 | PT_2024.3.1 .....  Macmini 9,1 | OS X 14.4.1 | M1 2020 | Mixbus 10 | Resolve 18.6.5
Website Find
Reply
English Guy Offline
Junior Member
**
Posts: 42
Threads: 5
Joined: Jul 2017
Reputation: 1
#3
08-25-2022, 02:24 AM
(08-24-2022, 05:18 PM)Dingo Wrote: Just tested using Mixbus 8.1.376 ARM 64-bit and have no issue switching channels and instruments with Generic MIDI.
Double checked with Intel build and also plays GM MIDI fine.

Thanks for looking.  I have used Mixbus for several years and do not think I am doing something wrong, unless the behaviour has changed with the upgrade?? I tried MB 7 and it still worked fine.
Find
Reply
English Guy Offline
Junior Member
**
Posts: 42
Threads: 5
Joined: Jul 2017
Reputation: 1
#4
08-25-2022, 05:16 AM (This post was last modified: 08-25-2022, 05:35 AM by English Guy. Edit Reason: further info/ clarity )
UPDATE:  The issue still persists.  This is now a licensed copy.  Other workarounds that failed were: copying the GM synth over from MB7; creating a track with another synth then switching to the GM synth (the non GM synth behaved perfectly).  A session created on MB7 and then opened on 8 behaves and works as expected from previously using Mixbus.

I am going to email support.
Find
Reply
Dingo Offline
Moderator
*****
Posts: 3,102
Threads: 54
Joined: Oct 2013
Reputation: 170
#5
08-25-2022, 05:21 AM
(08-25-2022, 05:16 AM)English Guy Wrote: This is now a licensed copy
Just to be clear the only difference between demo and licensed is the demo has noise injected on the bus.
Macmini 8,1 | OS X 13.6.3 | 3 GHz i5 32G | Scarlett 18i20 | Mixbus 10 | PT_2024.3.1 .....  Macmini 9,1 | OS X 14.4.1 | M1 2020 | Mixbus 10 | Resolve 18.6.5
Website Find
Reply
English Guy Offline
Junior Member
**
Posts: 42
Threads: 5
Joined: Jul 2017
Reputation: 1
#6
08-25-2022, 10:07 AM
SOLVED: The answer is a new feature.  When in draw mode there is a drop down box (at the top, to the right of the nudge clock) that controls the midi channel of the notes drawn and this had somehow ended up on 10, which is the standard channel for midi drums.  

Thanks to Nathan at Harrison for same day support.
Find
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)