Good evening everyone!
A brief introduction with system specifications:
Prime Z790-P WiFi DDR5 Triple NR 1 M.2 ATX Socket 1700
BEQ043 Pure Loop 360 x Socket Socket NR 1 1700 1200 2066 AM4 AM5
BEQ046 Silent Base 802 Black ATX NR 1
CRA052 RM1000x Shift 1000W PCIe 5.0 NR 1 Modular 80 Plus Gold
INI768 CORE i9 13900K 3GHz 24 Core NR 1 LGA1700 Socket no FAN
KIN722 64GB Kit DDR5-5600 Fury Beast NR 2 Black CL40 128GB
MIC601 Windows 11 Pro 64bit OEM NR 1
PNY223 RTX 4080 16GB VERTO DLSS 3 NR 1
SAM885 500GB 980 Pro SSD M.2 NVMe NR 1 Gen 4.0
SAM886 1TB 980 Pro SSD M.2 NVMe Gen NR 1 4.0
SAM903 1TB 990 Pro SSD M.2 NVMe Gen NR 1 4.0
Win 11 Pro
Focusrite Scarlett Solo 4th Gen
APC64
Minilab 3
Beatstep Pro
TD-17 Roland
Ableton 12.1.5
The issue I am encountering is as follows: The main control surface in Live is the APC64. The Minilab 3 is used in Arturia Mode to control the already mapped Arturia synths. The APC64 is recognized by Live, sometimes yes, sometimes no, while the Minilab 3 is always the first device to be recognized. All attempts made so far:
Reset the APC64;
Removed all peripherals except for the APC64, same result;
Updated BIOS and all drivers, same result;
Removed Minilab 3 and Beatstep from Ableton’s controllers, same result;
Reinstalled Live with a full clean installation, same result;
Removed all mappings from the APC64, same result;
Downgraded Live, same result;
Changed cable and USB port, same result;
Tried to get support from Akai, impossible and highly frustrating;
Disabled the firewall, same result;
Ran Live as administrator, giving it all possible permissions (even my bank account), same result;
Changed Windows power settings to maximum performance and disabled USB port shutdown, same result;
Disabled automatic shutdown of all USBs in device management, same result;
Obviously, all firmware, Windows, drivers, and BIOS are up to date.
I must clarify that this is the machine I work on and it is absolutely impossible for me to format it.
I’ve run out of possibilities and attempts. If anyone has other potential solutions, I would be very grateful. Thank you all and Happy New Year!
APC64 and Minilab3 disaster
-
sissySpacecraft
- Posts: 16
- Joined: Thu Sep 24, 2015 2:41 am
Re: APC64 and Minilab3 disaster
Hi,
I might have had a similar issue with my Akai Max49 script. The Max49 supports 5 midi ports over its USB connection and ALL of the remote script functions need to be associated with the same 1 of 5 midi ports as are configured on the Max49 itself or the script only partially works at best. The script "breaks" if for example, the Max49 is configured for differing ports like pads on port 1, keyboard on port 2, sliders on port 3 because the script can only connect to one port at a time (and the script on port 1 can't "talk to" the keyboard on port 2, for example).
Another possibility is if "Removed all mappings from the APC64" means you are trying to use "midi mapping" AND the remote script at the same time. That's not possible. "Mapping" and "Scripting" are mutually exclusive ways of "remote controlling" Live from midi devices. If the remote script is unrecognized only when you load sets that contain "midi mappings" to the APC64, and recognized for sets that don't contain "APC64 midi mappings", bingo.
Is the APC64 script still only sometimes recognized when it sits in the only occupied remote script slot? Zero in on that problem first. What is different in Live's log file between when the script is recognized and when it isn't recognized (as the only script)? (Are you always closing Live and reopening fresh after any code changes? Live only checks for "uncompiled remote script" code file changes when it is starting. It doesn't recompile anything when you just load a new set, for example. It needs to be "starting up" to compile "new" code.)
I might have had a similar issue with my Akai Max49 script. The Max49 supports 5 midi ports over its USB connection and ALL of the remote script functions need to be associated with the same 1 of 5 midi ports as are configured on the Max49 itself or the script only partially works at best. The script "breaks" if for example, the Max49 is configured for differing ports like pads on port 1, keyboard on port 2, sliders on port 3 because the script can only connect to one port at a time (and the script on port 1 can't "talk to" the keyboard on port 2, for example).
Another possibility is if "Removed all mappings from the APC64" means you are trying to use "midi mapping" AND the remote script at the same time. That's not possible. "Mapping" and "Scripting" are mutually exclusive ways of "remote controlling" Live from midi devices. If the remote script is unrecognized only when you load sets that contain "midi mappings" to the APC64, and recognized for sets that don't contain "APC64 midi mappings", bingo.
Is the APC64 script still only sometimes recognized when it sits in the only occupied remote script slot? Zero in on that problem first. What is different in Live's log file between when the script is recognized and when it isn't recognized (as the only script)? (Are you always closing Live and reopening fresh after any code changes? Live only checks for "uncompiled remote script" code file changes when it is starting. It doesn't recompile anything when you just load a new set, for example. It needs to be "starting up" to compile "new" code.)