Schippeaux

I am new to Max and I’m running into a few issues with this utility I am trying to build.

I’m using a sample pad and I’m trying to build a device that allows me to change the bank of instruments and the samples within each bank that each pad triggers. For example pad x might trigger the 7th Cowbell in my Bank of Cowbells. Then I might change it for another kit to trigger say the 3rd Wood Block in a Wood Block Bank. The idea is that I can dial in different instruments and samples for each pad to make a new kit, and then be able to save and recall different combinations quickly without having to load another Drum Rack (this is the next part of the project).

To do this I have made a Bank and Sample Selector patch which allows me to change the pitch of each note (which will trigger different samples within a Drum Rack later), and buddy a CC value with it (which will allow me to select a Bank).

I then have an Instrument Rack containing my various Banks - my name for a series of Instruments containing a Filter By CC patch and a Drum Rack containing samples for the Bank. The Filter By CC patch in each of these Instruments parses only notes with are buddied with the CC value selected through an if statement. Then a sample is triggered in a Drum Rack according to the note which has been selected in the first patch.

I have encountered a couple of problems with this. Firstly, all of the values in both patches - the selected Banks and Samples in the first patch, and the allowed CC value in the second patch - get reset every time I save, close, and reload the project. So I have to select the parseable CC value for every Bank in the Instrument Rack. With many different Banks this is a problem. Can these values be saved with the project?

Secondly, when it all works as I had hoped it would, the note I trigger parses only through the Instrument with the CC value I am allowing through, it then triggers the note in the Drum Rack which I had transposed it to in the first patch. The sample is triggered with the note on message, OK, but when the note off message passes through it silences the sample for a moment. This is with a one-shot sample that should just play all the way through, even if it is triggered by a note-off message. If I hold the key down it plays the sample no problem, but when I release the key the sample silences for a moment but then continues to play through. Strange because I would have thought that from the Drum Rack’s point of view, it is just receiving a note on and note off message as usual, which normally doesn’t produce this silence. What’s going on here?

A broader question would be - is there a better way to do this? With this method every Instrument in the Instrument Rack receives each midi note and then processes it through an if statement to determine whether or not to parse it to its Drum Rack. So every Instrument goes through this process with every note. I don’t know if this is using a lot of processing recourses or not - maybe it’s negligible? And Max just seems to lag on me or become unresponsive sometimes. Sometimes it doesn’t pass midi through when I expect it to, so I have to save it all, close down Ableton, load it back up and it magically works again. Is this what Max is like or is there something wrong with the design of my patches here?

If anybody can shed some light on any of this I would be most grateful. Thanks.

I’m using a sample pad and I’m trying to build a device that allows me to change the bank of instruments and the samples within each bank that each pad triggers.  For example pad x might trigger the 7th Cowbell in my Bank of Cowbells.  Then I might change it for another kit to trigger say the 3rd Wood Block in a Wood Block Bank.  The idea is that I can dial in different instruments and samples for each pad to make a new kit, and then be able to save and recall different combinations quickly without having to load another Drum Rack (this is the next part of the project).  

I then have an Instrument Rack containing my various Banks - my name for a series of Instruments containing a Filter By CC patch and a Drum Rack containing samples for the Bank.  The Filter By CC patch in each of these Instruments parses only notes with are buddied with the CC value selected through an if statement.  Then a sample is triggered in a Drum Rack according to the note which has been selected in the first patch.

I have encountered a couple of problems with this.  Firstly, all of the values in both patches - the selected Banks and Samples in the first patch, and the allowed CC value in the second patch - get reset every time I save, close, and reload the project.  So I have to select the parseable CC value for every Bank in the Instrument Rack.  With many different Banks this is a problem.  Can these values be saved with the project?

Secondly, when it all works as I had hoped it would, the note I trigger parses only through the Instrument with the CC value I am allowing through, it then triggers the note in the Drum Rack which I had transposed it to in the first patch.  The sample is triggered with the note on message, OK, but when the note off message passes through it silences the sample for a moment.  This is with a one-shot sample that should just play all the way through, even if it is triggered by a note-off message.  If I hold the key down it plays the sample no problem, but when I release the key the sample silences for a moment but then continues to play through.  Strange because I would have thought that from the Drum Rack’s point of view, it is just receiving a note on and note off message as usual, which normally doesn’t produce this silence.  What’s going on here?

A broader question would be - is there a better way to do this?  With this method every Instrument in the Instrument Rack receives each midi note and then processes it through an if statement to determine whether or not to parse it to its Drum Rack.  So every Instrument goes through this process with every note.  I don’t know if this is using a lot of processing recourses or not - maybe it’s negligible?  And Max just seems to lag on me or become unresponsive sometimes.  Sometimes it doesn’t pass midi through when I expect it to, so I have to save it all, close down Ableton, load it back up and it magically works again.  Is this what Max is like or is there something wrong with the design of my patches here?

If anybody can shed some light on any of this I would be most grateful.  Thanks.


bank-and-sample-selector-note-off-causes-stutter-in-drum-rack-sample

to be able to save stuff in an amxd you must make it a live parameter, then its state can be saved with a project file of the host program.

but when paths (to samples) are involved i would prefer writing a custom prefs textfile on disk.

to be able to save stuff in an amxd you must make it a live parameter, then its state can be saved with a project file of the host program.
but when paths (to samples) are involved i would prefer writing a custom prefs textfile on disk.


Bank and Sample Selector & Note-off Causes Stutter In Drum Rack Sample