Comments by jim95454
Thanks, FlowID. Let me know how it goes!
Posted on August 25 2023 by jim95454 |
Report Issue |
See Comment
bcm70 - was able to change the device to work with a single device instead of needing two tracks with Live 11. Should I upload the new device somewhere? Also added mappable controllers to control the Master Effects so you can use a control surface to control the FX parameters and mix.
Let me know.
Let me know.
3) SysMsg receiving now. You need SysMsg.amxd from the other project on a seperate MIDI track with IN monitoring and the Midi from set to E-MU.
sysexin to work requires upgrading Max for Live to the latest release (https://cycling74.com/downloads) and the point Live to the correct path in Albeton Lives preferences.
sysexin to work requires upgrading Max for Live to the latest release (https://cycling74.com/downloads) and the point Live to the correct path in Albeton Lives preferences.
1) Gets fixed by removing the gate node under the change preset flow. (The gate stops the MIDI transmission if current preset is 0 and one changes to 1.)
2) ROM presets are accessible by increasing the range of the live.numbox[1] under change preset from 0-999 to 0-1255. Assuming you have 256 presets in ROM. The ROM presets seem to start at 1000 on E-Synth so after the 999 possible RAM presets.
3) Still not receiving any SysMsg. There is a file SysMsg.amxd in your other project that probably needs to be included here and put on another track with IN monitoring and the Midi from set to the E-MU. However, sysexin does not seem to be triggerd.
2) ROM presets are accessible by increasing the range of the live.numbox[1] under change preset from 0-999 to 0-1255. Assuming you have 256 presets in ROM. The ROM presets seem to start at 1000 on E-Synth so after the 999 possible RAM presets.
3) Still not receiving any SysMsg. There is a file SysMsg.amxd in your other project that probably needs to be included here and put on another track with IN monitoring and the Midi from set to the E-MU. However, sysexin does not seem to be triggerd.
1) Minor bug: It seems like switching the preset from 0 to 1 stays at 0, no MIDI message is sent. But switching the preset from 2 to 1, 1 to 0 works. and you can switch from 0 to 1 and then to 2, and that will get preset 2.
2) Feature issue: The control panel does not allow selecting the ROM presets starting with L instead of P.
3) Bigger issue: The names of the Samples do not appear somehow it's not receiving SysMsg. receive SysMsg does not get triggered. Any idea? Who triggers SysMsg?
2) Feature issue: The control panel does not allow selecting the ROM presets starting with L instead of P.
3) Bigger issue: The names of the Samples do not appear somehow it's not receiving SysMsg. receive SysMsg does not get triggered. Any idea? Who triggers SysMsg?
So regarding receive SysMsg that parses the incoming preset name, the
wav: PWM-1 never goes away. When is Live supposed to update the preset name?
Is maybe something wrong with my setup? I have two tracks, one with the external instrument and EMU control and another track with SysListener with Monitor set to In - Midi From is Channel 1 on the EMU. When I change the preset on the E-MU sampler, the Midi In signal blinks of the track with SysListener but nothing updates.
What would be a simple debug message I could add to the Max script to check if it receives a sysmessage at all?
wav: PWM-1 never goes away. When is Live supposed to update the preset name?
Is maybe something wrong with my setup? I have two tracks, one with the external instrument and EMU control and another track with SysListener with Monitor set to In - Midi From is Channel 1 on the EMU. When I change the preset on the E-MU sampler, the Midi In signal blinks of the track with SysListener but nothing updates.
What would be a simple debug message I could add to the Max script to check if it receives a sysmessage at all?
It seems like loadmess connects to message 1 but that 1 then connects comment "Depth". That causes an error "comment doesn't understand "int" ". Should the connect from message go somewhere else?
It seems like loadmess connects to message 1 but that 1 then connects comment "Depth". That causes an error "comment doesn't understand "int" ". Should the connect from message go somewhere else?
Opened it into Max Live to debug:
newobj: live.banks: No such object
comment: doesn't understand "int" (when I double click it highlight the Depth which defaults to -96 db)
newobj: live.banks: No such object
comment: doesn't understand "int" (when I double click it highlight the Depth which defaults to -96 db)
I am getting this error under print:
comment: doesn't understand "int"
What is SysMsg.amxd needed for? It's not mentioned in the PDF?
comment: doesn't understand "int"
What is SysMsg.amxd needed for? It's not mentioned in the PDF?
Hi, any way I can debug this for you? Is there particular midi settings on the E-MU E4K that I should turn on for this to work? It's in multi-mode right now. How would I change the pre-set for a particular midi channel?