I have programmed an OPEN and CLOSE shortcut on my X-Keys unit to launch Nuendo. Every iteration since N4 has only required that I copy the shortcut address from the desktop icon to the address window in the associated key of the X-keys unit to get the new version to launch.
This time when I tested the launch button, N7 opened but it said there was no Eucon device! I quickly checked to see if I had accidentally written in the 32bit version address. But it was the correct address for the 64bit version. So, I donât know why it excluded the Eucon link. When I opened it directly from the desktop icon, N7 opened correctly WITH the Eucon link. Anybody have any idea why the launch address from the X-keys is causing this discrepancy?
ITâS THE SAME ADDRESS, why is the X-keys: 1) not launching WITH the MC control and 2) not activating the key commands that were written on/in it on N6.5?!!?
Worse, Iâm losing ground on this âone way street.â For every advance I take to get up and running on N7, a door closes behind me that will not allow me to return to my old way of doing things. I launched N7 and lost the controller altogether in the 32bit version. I migrate to 64bit and program X-keys to launch N7. Again, I lose the controller, but now I canât got back to the 64bit version of N6.5! Since I CAN launch N7 WITH the controller from the icon, Iâm scared to death to uninstall and re-install Eucon 3.2 as instructed by the X-keys Launch of the app. Iâm afraid Iâll lose the use of the controller altogether.
The X-Keys is a âregularâ programmable keyboard using USB, right? So basically to the computer itâs just looking like a keyboard sending key commandsâŚ
Would it make sense to try attaching the two devices - the X-Keys and the dongle - to two separate USB controllers/ports? I donât see what mobo youâre using, but I know several have different controllers on it. Some run the internal headers on the mobo which typically go to the front or top of the case, and others may go to different rear portsâŚ
Just a thought⌠Not that any of what youâre experiencing makes any sense to me eitherâŚ
They are attached to 2 separate USB ports. I really donât want to un-install and re-install Eucon again if I donât have to. I had JUST gotten it to where it appeared stable (no crashes or freezing for weeks!). On the other hand, the controller is almost useless to me WITHOUT the support the X-keys provides. So, itâs a dilema either way. If the X-keys worked with using the icon, I could âtake that hit.â But since it doesnât, I might as well try to figure out how to get it ALL up and running again. I just donât know what that next move would be.
I finally figured it out. The Eucon Workstation was missing. I re-loaded that and was finally able to launch from the X-keys device. Now I just have to figure out how to get the device to run all the other KCs without having to re-write the entire library again.
I quickly checked to see if I had accidentally written in the 32bit version address. But it was the correct address for the 64bit version. So, I donât know why it excluded the Eucon link. When I opened it directly from the desktop icon, N7 opened correctly WITH the Eucon link. Anybody have any idea why the launch address from the X-keys is causing this discrepancy? 
