LINK Question (Ultra 4xt)
Posted: Sun Dec 09, 2012 2:04 am
Hi folks,
i am having a problem while trying to set up a LINK (between to Presets).
i create a NEW Preset (ie. blank) via Preset Manage, no problem
Then i select the new blank Preset, enter Preset Edit, and select LINK (F4).
So i am now on the LINKS MAIN page and the command LINK (F4) appears in a shaded box.
But what my problem is, is that i am not able to move the cursor (or rather shaded box) anywhere !! It is literally stuck on LINK (F4). i can press UTILITIES/GLOBAL/VOICES (F buttons) and enter their respective sub-menus. But i can't move the curosr (using the 4 x ARROW KEYS) and so i am not able to highlight the 'L1' icon to set the Preset for which i want to place the Link on. The ARROW KEYS are working fine (ie they are not broken) as they work perfectly elsewhere. i have followed the directions in the manual and also read a couple of threads on here. And checked with someone else who owns an EMU and he does not experience the same problem at all on his device.
We were wondering if maybe something has been set (wrongly) in the configurations somewhere ?? Has anyone else experienced this problem at all ?? Would really appreciate some help here please.
Best,
Paul
i am having a problem while trying to set up a LINK (between to Presets).
i create a NEW Preset (ie. blank) via Preset Manage, no problem
Then i select the new blank Preset, enter Preset Edit, and select LINK (F4).
So i am now on the LINKS MAIN page and the command LINK (F4) appears in a shaded box.
But what my problem is, is that i am not able to move the cursor (or rather shaded box) anywhere !! It is literally stuck on LINK (F4). i can press UTILITIES/GLOBAL/VOICES (F buttons) and enter their respective sub-menus. But i can't move the curosr (using the 4 x ARROW KEYS) and so i am not able to highlight the 'L1' icon to set the Preset for which i want to place the Link on. The ARROW KEYS are working fine (ie they are not broken) as they work perfectly elsewhere. i have followed the directions in the manual and also read a couple of threads on here. And checked with someone else who owns an EMU and he does not experience the same problem at all on his device.
We were wondering if maybe something has been set (wrongly) in the configurations somewhere ?? Has anyone else experienced this problem at all ?? Would really appreciate some help here please.
Best,
Paul