Jump to content

Volume management issue btw MB Seq v4 and MB6582


tupinamba
 Share

Recommended Posts

Hi everyone,

 

I have this issue  on one of my songs : I have a mixer map on position B2 saying that OUT1 CHANNEL3 volume is set to 35, but it doesn't work while playing the song from the start and volume of  OUT1 CHANNEL3 (OUT1 is my MB6582) on position B3 is loud (127).

However, when I just start the playing on B2 (the mixer map step), it works and volume is down on B3. Also, if I go to the mixer map and change volume (which is 35 but plays like it is  127), I works and drops down to the correct value...

I even tried to add a volume CC to the track itself on the pattern, using layer D to control volume and setting it also to 35, but it still doesn't work while playing the song from the start!

I really don't get it... Any clues?

 

Thanks!

 

Gael

Link to comment
Share on other sites

  • 2 years later...

Hi ! Posting again as I never solved this issue, which actually occurs in the majority of my patterns. MB6582 barely responds to volume CC messages through mixer maps. It changes volume if I actually change the value in the mixer map "live", but if the song reaches the mixer map, it will not change the volume as defined in the mixer map...

Link to comment
Share on other sites

OK... Using MIOS, when I use the "dump" command in a mixer map, I get this:

[4744.364] c0 11
[4744.364] b0 07 5a
[4744.366] c1 11
[4744.366] b1 07 5a
[4744.367] c2 11
[4744.367] b2 07 5a
[4744.369] c3 28
[4744.369] b3 07 32

 

But when I only play the mixer map step in a song, I only get this:

[4716.619] fa

And that when I press stop:
[4717.645] fc

(and I guess those are only start - stop messages...)

Link to comment
Share on other sites

I just updated the firmware from 4.79 to 4.91

Now here is the message received by MIOS when I press start while a mixer map (with Prog Change ans Volume parameters) is selected :

[8097.890] fa
[8097.894] b0 07 7f
[8097.896] b1 07 00
[8097.896] b2 0a 00
[8097.897] 90 37 64
[8097.898] 90 3c 64
[8097.898] 90 3f 64
[8097.899] 90 43 64
[8097.900] 91 37 64
[8097.900] 91 3c 64
[8097.901] 91 3f 64
[8097.902] 91 43 64
[8097.902] 92 37 64
[8097.903] 92 3c 64
[8097.904] 92 3f 64
[8097.904] 92 43 64
 

It looks that it sends more complete data... But still, the MB6582 won't obey to the volume parameters (whereas it works with Prog Change parameters)

Even weirder:

If I play a pattern and change volume in a mixer map using the GP buttons, it works with all the SID channels (1, 2, 3 and 4)

But if I stop and restart the pattern, SID channel 1 will come back to max level (value #127) and SID channel 2 to min. level (#0), whereas channels 3 & 4 will remain at the volume that was set while playing. Also, if I change the values while the sequencer is not running, SID channels 1 & 2 will be back to volume value #127 and #0, whereas the other channels will play at the defined value... 

So It looks like only channels 3 & 4 respond correctly to Volume CC messages...

Link to comment
Share on other sites

Hi (again ;-) )

I've updated both firmware and software of the MB6582 to the latest. The problem remains the same. Channels 3 & 4 taking volume CCs from the mixer maps into account, Channels 1 & 2 ignoring them, unless they are manually changed witn the GP encoders during playing...

I'm afraid I'll have to use only channels 3 & 4 for now... 

{EDIT}

It is not that simple. After further testing, I realized that channels 3 and 4 also have the same problem, but not always. And channels 1 & 2 sometimes respond to the messages. But I cannot see why. And this happens with different sounds of the MB6582, but only with the MB6582. 

This is driving me mad... And I'm getting tired of being yelled at by the sound technicians where I gig because my volumes are not set properly... ;-)

Edited by tupinamba
Link to comment
Share on other sites

  • 2 weeks later...

I think it's related to a (known) limitation of the MBSID V2 system: during a patch change, the firmware has to read ca. 512 bytes from the bankstick, during this time a MIDI buffer overrun can happen if too many events are received.

I fear that there won't be a proper solution for MBSID.

On the other hand: due to the SID background noise, the usage of lower volumes shouldn't be preferred anyhow. It's better to lower the volume on the mixer.

Best Regards, Thorsten.

Link to comment
Share on other sites

OK, I see... And I hear what you say about volume being better when to its max on the SID... But I have progs where I cannot interact with volume on the mixer, and have to make it through CCs ;-)

So if I have a mixer map dealing with program change, then a pattern, and then a mixer map dealing with volume only (program change being "- -", it should do the trick, right?...

All the best,

Gael

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...