how can i send it?
not attached, because I can’t find it on the “disk”.
I see. Type cp Log.txt ~/Documents/Log.txt. Then you should see the file Log.txt in your Documents folder
i start ableton.
script is active.
in albeton: midi track. i load au plugin. (bx ssl4000e, hx native with more macros)
with the upper right button i switch to the “plugin device”-
the “load” animation appears on the e1 display, the “usb device” flashes,…and this continues “to infinity”
Ok that’s clear. Can you send me the Log.txt so I can investigate?
how do i find it?
i can see this folder in terminal but not in finder
Like I said: type cp Log.txt ~/Documents/Log.txt in the Terminal. After that you should see a copy of Log.txt in your Documents folder. You can send me that copy
i sent a drive link now
Got it. I’ll have a look
1 Like
here, in “show options”, the “show Library Folder” had to be “checked”.
it wasn’t like that until now
First analysis:
The first time the script tries to upload the preset it somehow fails to transmit it correctly. @Martin I see the Preset::parse: parseName failed error again. This may be because @phonaak has debugging turned on and redirects the E1 log messages over Port 1 to the remote script. Also ‘slow’ uploading of presets (letting Ableton send the SysEx) may be part of the issue.
@phonaak: what happens if you set
DEBUG = 2
E1_LOGGING = False
E1_LOGGING_PORT = 2
Does the preset then still fail to load?
fresh start e1
fresh start ableton.
script is active.
in albeton: midi track. i load au plugin. (bx ssl4000e, hx native with more macros)
with the upper right button i switch to the “plugin device”-
the plugin device preset dreated bank6, p2-
the “load” animation appears on the e1 display, the “usb device” flashes,…and this continues “to infinity”
So turning of logging does not make a difference. Ok, I’ll do some more testing with ‘slow’ SysEx upload to see what happens on my machine. But that will have to wait until the weekend, I am afraid.
2 Likes
@jhh : I had a quick test and now when I select a track the device template is loaded.
So it looks better, the the previous commit.
The plugin @phoneaak has trouble with is the same one that I use and the min/max values flipped. Min: 300 Max: 50 for the Q values.
Might be related.
@phonaak here are some thing you could check.
firmware version, ctrl and in / out port and if these are setup in Ableton.
@jhh how do you make a toggle switch in the template editor that will keep the control script to push the correct name? Should I use a specific lua function for that?
E1 Newest fw
Newest Script.
In Ableton all. ok
This is not something you can achieve through LUA scripting.
I meanwhile found the issue with my template.
The parameters where not duplicate but they are assigned to different midi channels.
I have in the Ableton Option.txt ( https://help.ableton.com/hc/en-us/articles/6003224107292-Options-txt-file )
-_PluginAutoPopulateThreshold=128
--Line to add to Options.txt file: -_PluginAutoPopulateThreshold=64
-- Auto-populates the plug-in parameter list if a plug-in has a number of less or equal than X parameters.
Default = 64
Min = 1
Max = 128
Then the remote script is modified as written before. So for PluginDevice I can make dedicated templates and for MaxDevice only based on the “Original name”.
This setup starts to look like my dream controller.
Where you can make the template match the visuals of the vst etc.
Wouldn’t it make sense to add OS detection to the script when there are difference?
Then handle per OS what to use as the devicename?
Otherwise shall I try to reach out to Ableton or ask on the Cycling74 forum ?
I am afraid what we need/want is not implemented.
The E.one is ahead of it time.
Yes, please do ask around. I was thinking for a future version of the remote script to add some intelligence to recognise a specific Max device based on its list of parameters. That’s of course a bit fragile (if Ableton changes the parameters), but better than nothing.
" That is somewhat tricky because it depends on correctly setting LIBDIR. I seem to recall that didn’t work for you. Here is a possible setting
LIBDIR = 'ElectraOne'
USE_FAST_SYSEX_UPLOAD = True
SENDMIDI_CMD = 'sendmidi'
E1_CTRL_PORT = 'Electra Controller Electra Port 1'
This assumes you have a folder ElectraOne in your home directory, ie /Users/phonaak/ElectraOne that contains the sendmidi command"
can somebody help me? i don’t have this folder but i want to try “fast sysex”. I create this folder in the right place, then what is this “sendmidi command”? how can I create this command in the folder?
Are dumps enable in config.py?
Check in the Ableton log with DEBUG = 5 to get hints what the issue is.
Otherwise open a terminal and type
mkdir ElectraOne
cd ElectraOne
mkdir lib
download sendmidi from the releases section and put in the lib dir you created.
If you have dumps enabled a folder called dumps should appear I think.
/Users/phonaak/ElectraOne/dumps
/Users/phonaak/ElectraOne/lib
/Users/phonaak/ElectraOne/lib/sendmidi
