Attached is a User File with two versions, the Montage8 version which works fine and the Montage M version which has the problem.  They are both on User Live Set 1 page 1.

Thanks,

Phil

Your user file didn't make it through, but the video looks like the "upper octave" is in a range if you just played a single key then those would all be "quiet" (due to amplitude scaling I would guess).  Without playing the lower octave just those upper keys would be subdued.  When you play the lower notes by themselves they always play louder.  Which is what is happening when you play the lower note first.  It looks like monophonic portamento is turned on which is why when you press the second key an octave up everything goes quiet.  And you're holding down the lower key and when you let go of the higher key the lower key sounds at full volume again.  

I'm not sure what you're after.  If you really want the higher notes to be so quiet or not.  If you really want portamento to be happening.  And -- if so -- if you want this to be monophonic or not.  

To me everything makes sense if the settings are as I am assuming from the behavior.

Thanks Jason, the setting is not monophonic, so that's definitely not what I want.  It is true that I want the lower octave to be louder, but why would the lower note go off and on when pressing the higher octave?  I am holding the lower note down so it should just sustain. Still doesn't make sense.  Any tips on how to send the User File so it would be readable?

Phil

Like everyone, I'm still learning how to use the new forum.  Maybe try zipping the user file first if you haven't tried that already.  Maybe try sending the Performance to Soundmondo.  I don't have access to a Montage M so Soundmondo would be easier for me to look at.

I figured out the problem.  I'm embarrassed to say that the part was in mono, rather than polyphonic.  Sheesh!

Phil

Glad you checked, because that's what the video seemed to show.   And it's easier to tease through that on the keyboard than it would have been to look through your files in a hex dump while looking at the data list to map out the parameters.

Either way, thumbs up.  The journey is as important as the destination.

Thanks for posting that. Any embarassment will be short-lived. But by posting the solution you help others that may run into the same thing.

One thing to keep in my mind is that you can NOT rely on any of the presets (except perhaps with the INITs and then not always) to have particular parameter settings.

Always thoroughly examine ANY preset you intend to use to make sure everything is set the way you want. That is especially important for control assignments, arpeggios and motion sequences.

When something seems wrong to me that is the first thing I do - recheck all of the basics.

Instead of using a preset 'as is' I've gotten into the habit of examining the preset, making any changes to things I consider 'default' settings and then save it as a use performance. Then I build future performances from my own, thoroughly checked, performances. That way I only need to examine a preset one time since I never refer to the preset again.

You may want to consider creating your own workflow habits.