Comments by charlesparra
The controller has a button just above the user presets that will send all of the controller parameters to the SE-02 device. You can also click on the name of each section to only send the parameters grouped under that section. For example click on "VCF" title to only send the VCF parameters to the SE-02 device.
Posted on August 19 2020 by charlesparra |
Report Issue |
See Comment
Hi gregosaure, I am going to continue to work towards a solution, but in the meantime I will issue you a refund for the inconvenience.
Hi gregosaure, I re-worked the way bank and program changes are synchronized in v 1.0.5. Here is additional details on what was tested, https://docs.google.com/document/d/1c5k4baOnrGBxK_JpWDM6_nEnUgxbDASbYJlJwe4RHaU/edit?usp=sharing
All 3 tests passed. I am still looking into the automation issue.
All 3 tests passed. I am still looking into the automation issue.
Hi gregosaure, my apologies but I discovered another issue. I need to more testing before pushing out the updates. Allow me a few days to get this sorted out.
Hi gregosaure, I just posted version 1.0.4. I tested this version by selecting a bank and program, making changes to the parameter values so that they are different from the values from the internal patch and saved as a Live Set. Confirmed that both bank, program and changes to the parameters were recalled correctly.
Hi gregosaure, I think I understand the problem now and am working on a fix.
Hi gregosaure,can you see if v 1.0.3 fixes the initialization issue.
Hi gregosaure, I did notice that when I start Ableton using a default set, the bank and program saved in the default set are not sent to the SE-02 device upon initialization. I will work on correcting that. Is that what you are experiencing?
Hi gregosaure, this is how I have the SE-02 device configured:
Midi Channel = 1
Chain = Off
Auto Off = 240
Saver Time = Off
Send CC = U-M (Meaning sent to both the USB and the Midi ports)
Send PC = U-M
Sync = Internal
Midi key trigger = On
Midi thru = Off
Version = 1.11
I was studying up on automation, and since the M4L device is a Midi effect, I don't think it is possible to record anything other than CC messages. I can be wrong here as I don't have a lot of experience with recording automation, but wouldn't recording of plugin parameters only apply to AU and VST plugins?
Midi Channel = 1
Chain = Off
Auto Off = 240
Saver Time = Off
Send CC = U-M (Meaning sent to both the USB and the Midi ports)
Send PC = U-M
Sync = Internal
Midi key trigger = On
Midi thru = Off
Version = 1.11
I was studying up on automation, and since the M4L device is a Midi effect, I don't think it is possible to record anything other than CC messages. I can be wrong here as I don't have a lot of experience with recording automation, but wouldn't recording of plugin parameters only apply to AU and VST plugins?
Hi gregosaure, that is odd and I haven't been able to reproduce the issue using version 1.0.2. Can you let me know how you have the track configured?
My setup is to use a Midi track with an "External Instrument". I then add the SE-02 M4L device into the same track placing it before the external instrument. The external instrument is configured to send Midi to the SE-02 device on channel 1. Audio is configured to receive from the SE-02's stereo output ports. The midi track is configured to receive Midi from all devices, however I have since switch to setting the track that contains the SE-02 M4L device to only receive Midi from the SE-02 device on channel 1. I then created a separate Midi track that is configured to send Midi to the SE-02 via the external instrument input. I then set the Midi "From" on this separate track to which ever device I want to route midi output to the SE-02 track's input. For example, I have 3 separate midi controllers that I use to output midi note information. I use the extra midi track to switch between the available midi controllers that I want to receive midi note info from. This avoids issues when the source controller is also able to output program changes and cc info which wold otherwise be sent to the SE-02 M4L device.
My setup is to use a Midi track with an "External Instrument". I then add the SE-02 M4L device into the same track placing it before the external instrument. The external instrument is configured to send Midi to the SE-02 device on channel 1. Audio is configured to receive from the SE-02's stereo output ports. The midi track is configured to receive Midi from all devices, however I have since switch to setting the track that contains the SE-02 M4L device to only receive Midi from the SE-02 device on channel 1. I then created a separate Midi track that is configured to send Midi to the SE-02 via the external instrument input. I then set the Midi "From" on this separate track to which ever device I want to route midi output to the SE-02 track's input. For example, I have 3 separate midi controllers that I use to output midi note information. I use the extra midi track to switch between the available midi controllers that I want to receive midi note info from. This avoids issues when the source controller is also able to output program changes and cc info which wold otherwise be sent to the SE-02 M4L device.
Hi gregosaure, I just posted version 1.0.2 which fixes the issues with the bank and program not being sent to the SE-02 when loading a Live Set. I am still looking into the automation issue.
Hi gregosaure, I will look into addressing these issues this weekend. I currently do not support loading the User Bank. That would require sysex commands which are not documented by Roland. I started to look at how the SE plugin does it, but haven't committed to supporting user banks yet.
Awesome! Let me know if you run into any issues.
Yes, the pro edition contains all of the SE-02's internal patches. As you switch between the internal patches the dials in the controller are updated to reflect the parameter values in Ableton.