mySoftware [Updates]

Once you create a user profile on Motifator and update with the appropriate information, the updates shown here will be specific to you.

rssFeeds [Syndicate]


forumforum
 

Old Motifator threads are available in the Archive.

Viewing topic "Mixing not responding to midi volume from DAW"

     
Posted on: February 08, 2012 @ 04:49 AM
mmutax
Total Posts:  29
Joined  12-04-2011
status: Regular

I have 2 Songs. But only One is responding to volume (Midi Ctrl 7) from DAW. (Note on/off messages are working on both).

I compared all parameters (Songs and Mixings) and can’t find differences between the 2 songs.

In the one which is working, when I enable/disable Volume/Expression for the part (RcvSwitch -> Control -> Vol/Expression), well, it works as expected. But not the other Song-Mix.

Note:
In the bad one, even when not playing, if i move the volume sliders (multi part control button to access sliders) the slider in the screen updates fine, but not the sound !!AND!! the small red triangle indicating the volume value reappears at the old position magically after about 1.5 seconds.

What is happening? What is the difference that i can’t find inspecting the screens ?

  [ Ignore ]  

Posted on: February 08, 2012 @ 05:03 AM
Bad_Mister
Avatar
Total Posts:  29969
Joined  07-30-2002
status: Moderator

You unfortunately, have not provided enough data to solve your issue. But since you are playing the files from the DAW (is that right?) it probably is some setting you’ve made or inherited, either in the files or in the DAW. But you gave no information
:-(

  [ Ignore ]  

Posted on: February 08, 2012 @ 05:21 AM
mmutax
Total Posts:  29
Joined  12-04-2011
status: Regular

Not enough info?

The mixing of both songs are playing.
- So receive channels Ok. Notes on/off being received
- the parts have the RcvSwitch enabled for the midi control messages involved (Volume Midi Ctrl 7).

One of the Mixing respond to the switches the other one doesn’t.

So my conclusion is:
There is some other parameter somewhere to achieve this. (But i’ve already looked everywhere). Please indicate where to look.
-----------------------------------------

If this isn’t enough for that simple situation, what info should i provide ?

I don’t want to write a book :).
I was expecting that you could solve it because of your experience. What ‘mistakes’ can be done when setting a receiving channel for a part and setting a receive switch for specific data?…

Thanks.

P.S.: The setting in the DAW are the same for the good and the ‘bad’ song-mixing (one in song position 2 and the other on song position 12 - position means memory location).
In fact, it is the same daw project being played back on the current song-mixing. When i select song 2 it works. When i select song 12 it doesn’t.

  [ Ignore ]  

Posted on: February 08, 2012 @ 07:21 AM
meatballfulton
Avatar
Total Posts:  1676
Joined  01-25-2005
status: Guru

How do you know the DAW is sending the CC#7 msgs in both cases?

Seems more likely than something wrong in the XS mixing since you say the settings are the same.

  [ Ignore ]  

Posted on: February 08, 2012 @ 07:43 AM
mmutax
Total Posts:  29
Joined  12-04-2011
status: Regular

How do you know the DAW is sending the CC#7 msgs in both cases?

The project is the same. I only change the song-mixing in the motif XS.
Also i’m shure the daw is not echoing or sending any sysex or any other inconvenient stuff.

Of course, i cannot be 100% shure unless i intercept the midi communication between Daw and Motif. I can do it using a virtual midi port if need be.

Seems more likely than something wrong in the XS mixing since you say the settings are the same.

Yes. This is my question. Again, and in other words:

What other parameter or factors beside Receiving Channel and RcvSwitch Control can be playing a role here ?

I think that someone who is really intimate with the intrument would know what setting(s) could be interfering (and where to change it) (Even this being a basic issue in my simplistic view/bias).

BM said it can be some inherited setting. I think that even inherited setting should be visible ("findable" - sic). In other words: settings/parms that affect something cannot be hidden or prevented from being modified. I would bet that such a parameter does not exist in a well designed instrument.

  [ Ignore ]  

Posted on: February 08, 2012 @ 09:48 AM
mmutax
Total Posts:  29
Joined  12-04-2011
status: Regular

OMG !! I’ve found it !!

Pilot error here.

I was comparing both bulk dump in hex and found the difference in base address 37 pp offset 20. Bit 2 of this byte was different. This bit means control change. Arrrgh.

The short story is: In the RcvSwitch screen you CAN check/uncheck any controller values even if the ’master‘ switch (control change) is unchecked.

So

”What other parameter or factors beside Receiving Channel and RcvSwitch Control can be playing a role here ?”

and

What is happening? What is the difference that i can’t find inspecting the screens ?

When i saw i could see and access the various controllers i have assumed that control changes were being received. That was my error. They weren’t greyed out nor disabled, that is my excuse.

I’ve failed inspecting the display. But comparing dumps i could find it.(in fact, a comparison utility found it for me).

it probably is some setting you’ve made or inherited, either in the files or in the DAW. But you gave no information

May be we can learn something here.
The bitter the experience the longer the memory will last, i hope.

I love to play it, i like the sounds but am afraid of a byte coming from any corner. (sic) ;)

Thanks.

  [ Ignore ]  


 
     


Previous Topic:

‹‹ Digital out on motif xs - volume too low ?
Next Topic:

    w7a files on xs or classic ››