Now we’re talking ! That’s nice and I didn’t catch this full screen ability.
1 Like
@chapelierfou works great here as well thanks a lot for making the script max4live!!!.
@alechko how did you get it to display the name+value “full screen”, is it a setting in live or on the EC4?
it happened by itself once I’ve enabled the Output in the Control Surface section in the MIDI Setup, apart from that I did nothing, I use the Live 11 setup [15] and one of the Dev(ice) groups [3 or 4], I was hoping that the second Dev(ice) group would extend controls of devices that have more then 16 parameters but they seem to be mirrored, so either 3 or 4 would work the same.
also worth mentioning that the NUM page still shows numbers and not the values, so the param names and values available on the NAME page only, but it does work two way, meaning if you change a value of a macro it synced to the EC4 and will be reflected instantly.
oh and it works flawlessly both for native Live stuff and VST/AU as well, I mean the param names and proper values, for example a VST/AU compressor threshold is displayed “Threshold Xdb” and not 1-127, but I think that if you map these to macros in Live you’ll still get 1-127 from the macro…
just tested it and yep, once you map a parameter to a macro rack you get the 1-127 values instead of the real values, but that’s Live problem and not the EC4
wow, the deeper I dive the more I’m blown away by the new script… by holding SHIFT a new world emerges, you can move between tracks, turn on/off devices, hide them (you know, minimize it), and move between Banks of params! so if you have >16 params you’ll see Bank option which will move to the next 16 available params per device, amazing!
also you can move between devices on a track in 2 modes: each device or by racks, so if you have two racks with two devices you can reach every device in the chain or just jump between the racks, pretty awesome!
5 Likes
Hi guys, keen to try this updated Live12 script!
Sorry for the stupid question, but how am I supposed to upload the contents of this zip file (.pcy) to the EC4?
I was expecting a sysx file.
Apols, I’m sure I’m missing something obvious, but have scanned this thread to no avail.
Thanks
I’m pretty sure that .pcy file is a Python file that you import into your Remote Scripts folder in Ableton. When you plugin your EC4 and launch Ableton, the script allows for communication with the EC4.
Search ‘Installing Ableton Remote Scripts’ for more info.
Thanks d4ydream,
I worked it out (as you say, I just needed to read the manual, which tells you how to load Ableton Remote scripts (you paste it into a location in the Ableton app, after “opening contents”)).
However once I successfully installed the control script, I then had an issue where my EC4’s setups read “15” (Setup 15) and “Live” (Setup 16). “Live” (Setup 16) was working in Ableton, but this was the limited Live 10 functionality Setup.
Setup 15 is supposed to be the enhanced Live 11 (and 12) setup with the cool new functionality. “15” (Setup 15) was only semi working (parameter names would update on screen in Group 4, but when I twisted the knob nothing changed, which was a huge bummer).
I spent a few hours trying to get the Setup 15 working.
!!! THIS IS WHAT FIXED IT !!!
-On the EC4 itself, I factory reset all setups. Explained in the manual, but for ease:
- Hold blue button and click Pot 4
- Click Pot 4 again
- Hold down Pot 8 until the bar loads, then let go when it disappears.
RESULTS AFTER DOING THIS:
When I clicked the “Setup” Button on the EC4, I no longer saw “15” (Setup 15) and “Live” (Setup 16). I now saw “Lv11” (Setup 15) and “LV10” (Setup 16).
Now “Lv11” (Setup 15) - aka “the cool new firmware 2.0 stuff that auto-maps parameter names with Live 11 or 12” - works perfectly! It’s incredible.
Took hours to fix so hopefully this saves someone some time.
11 Likes
I’m going to test the fw2.0 with the Push 3 standalone tonight. If it works with the P3SA, then I will be very very impressed (and happy).
Unfortunately it doesn’t work with the Push 3 straight out the box in Push standalone mode.
It only works with Push standalone if you do the midi mappings for the Ec4 in ableton desktop first, then transfer the set to the Push3.
Is there a way to install remote scripts on P3SA ?
1 Like
Not sure but would love to know if anyone does?
That’s a huge step forward … I didn’t notice those functions when i first install the firmware …
I’ve spent so much time mapping and naming those device parameters and now they appear magically and i can scroll through tracks and devices ! Thanks !
3 Likes
Thanks for that, it didin’t work for me neither before you point at the reset procedure.
2 Likes
Hey guys,
i just got a faderfox ec4 which i am all excited over; problem is that i have some issue with getting it working!
I was wondering if someone could just throw a few screenshots my way with settings and / or hints on how to get it working the fastest, so i donbt have to tear out all of my hair?
I have got a set of befaco type B cables for midi comm, and have the original USB cable. Upgraded firmware to the latest, also installed the BitWig script.
My hardware/sioftware setup is basically
DAW: BitWig
Drums: Rytm mk2, Machinedrum mk2,
Synths: Komdamo EssenceFM mk1, MonoMachine mk2, Idirium
Euro: SSF Entity Ultra-Kick, Ultra-Perc, Metalloid, Vult Freak, Neuzeiw Warp + warp expander
Soundcard, midi: Antelope Orion 32HD+Ferrofish A16 MADI expander (both audio), iConnectivity mioXM (midi)
… plus some gear ilike midi kkeyboard, speakers, midi-thru-box, some DIY stuff and some such… But that´s it.
Software i am running Maschine mk2 mikro controller with the soctware package(s) mostly maxed out, also Serum and U-He Diva.
My goal is just getting the EC4 to play nice with controlling the units that don´t have that many buttons like Kodamo, my Elektrons and whatever i feel for.
The problem: i can´t get any reaction when i try to use the buttons on my EC4, i get nio reaction any way, like to/from it whatever i do. It´s almostlike i have the wrong cables, but they are brand new and i have tried switching to a different type, tried using only USB and everything i can think of, It´s probably a very simple problem but i can´t get it going!
So, i would be very happy if you could just send some screenshots with how the important parts of your setup looks like, if it´s not too much trouble for you. Pleeeease? 
I won´t hassle you with questions, just some kind of speedy basic image.tutorial as simple as possible, and i can probably find out what i do wrong .
Thanks in advance!
//mbang
I only use it for controling ableton but there shoudn’t be any specific configuration for it to output midi data to hardware or bitwig. Just set the required midi channel / cc for your specific setup and it should work.
The pots should be set to ccab ( in the edit mode : fn + enc 8 ) for normal cc use and it should work.
You can perform a reset to be sur that your unit is in factory state (enter setup mode with fn+enc4 and then press reset and press and hold “reset all setup”)
2 Likes
you can try using os midi monitor to see if any midi data is incoming to computer, on macos there’s MIDI Monitor, not sure about windows but should be easy enough to google. if no os response then probably a cable thing.
if it works on os level then dig into the bitwig settings, I’m Live user but imagine same things required on bitwig, something to check a box somewhere on MIDI setup where it tracks/syncs in and out from the EC4.
also try different setups/groups.
for rytm just make sure you send to correct channel
1 Like
Thanks, i will check out your suggestions!
I found some detailed information about ec4 and bitwig so i will try those out aswell, i usually rush into tech stuff without any thoughts and now it seems like a bad thing. I will take my time, and let you know how i progress.
Also very good suggestions; will try them out ina few hours after work!
Many thanks!
I hope to be able to move forward soon.
Ok, so far i have tried and successfully upgraded the bitwig Faderfox setup sysex to my EC4, so far so good = no error messages, but a “successfully installed” message of some sort is good enough i guess. I have not tried doing anything else inside BW yet but one thing at a time! If i rush, i makke errors and get stressed.
Now, to my second point; i did like suggested, installed a midi monitor, “pocket midi” from microsoft, and it seems like it´s working properly; at least it gives the values i expect when i expect it.
So, now i am going to try to setup some midi communication with my machinedrum, or monomachine., or possibly something else. We´ll see!
Edit: tried on my Rytm and i found a super simple way, where the EC4 itself shows what cc number is being sent; not talking about the learn, its something else. But i got it going now! Thanks!
I am a bit curious on how to get NRPN working with Rytm, any ideas? I enabled it in the system settings on my Rytm, but it did not work anyway… any ideas? The method before does not show NRPN as midi or system unfortunately!
1 Like
Hi guys,
This V2 firmware and the great live script that goes with it will probably deeply change my ableton workflow as it makes midi assignment for effects ssssooo much smoother and simpler. I use to have pre made groups and setups for specific effects but now any effect or instrument i use gets it’s parameters auto assigned with value feedback and banks of parameter etc … crazy …
but,
It seems that on my system the live script kind of bug from one session to the other. Sometimes it works flawlessly and sometimes the parameters gets stuck on the popup view and don’t return to the main view. I have to press function after each move of encoder for it to go back to the main view. I kills the flow. It’s kind of random and sometimes for no reason an encoder works normaly again.
Does any of you experienced such bugs and erratic behaviour with the new live script ?
Here is what the midi monitor recieves when I monitor sysex activities. The first one is the normal behaviour where the popup display disapear after a second and goes back to the main group vieuw.
On the second one there is an “invalid 1 bytes” command that occur when the display get stuck on the popup view.
I’d try resetting all sets (described in a post from a few weeks ago) in case that works