! ! it's like everything has been changed ! !
The way a bank opens, no option to show names only in a library window, no get patch, no send patch, no load Performance, no make New Performance, no Library menu.
Unisyn 2.1.1 is like an entirely different program, foreign and unusable. Especially when it quits out every time I try to load a version 1.14s performance file, quit, quit, quit.
I get this 2.1.1 version to use with OSX but man, if it's so different I think I can't use it now. 1.14 and 1.5 were so good !
Any experienced version 1.5 users got some tips on how to get around in 2.1.1 ? this is unbelievable.
Version 1.14s the special, one MIDI device version that works
with the Alesis QS6, QS7, QS8, QSR.
<small>[ March 01, 2005, 03:20 AM: Message edited by: ifwuh ]</small>
Why is Unisyn 2.1.1 so much different from 1.14 or 1.5 ?
Moderator: James Steele
Why is Unisyn 2.1.1 so much different from 1.14 or 1.5 ?
um - about the post I made above.
spoke too quickly, Unisyn2 is Ok.
it was the new Profile that was so different and some time spent
with it has shown that it can work.
About the Unisyn1.14 "Perfomance" file causing Unisyn2 to quit out, well that's still happening, but MOTU tech support has taken an interest and maybe it will get fixed soon.
Editing this post over two years later and no, back om '05 tech support only
confirmed that they can reproduce the crashing. They don't know why its
crashing and had no suggestions or workarounds. It crashes.
So I would put this back to - - unisyn 2, for loading old v1.14 and 1.5
"Performance" files is a no go. I have been able to use v1.14 on an OS9
mac to send the performace, then do a "Get" and "Snapshot" in Unisyn2 on a different mac connected to the same gear to then re-create the
"Performace" but it's all a real pain.
spoke too quickly, Unisyn2 is Ok.
it was the new Profile that was so different and some time spent
with it has shown that it can work.
About the Unisyn1.14 "Perfomance" file causing Unisyn2 to quit out, well that's still happening, but MOTU tech support has taken an interest and maybe it will get fixed soon.
Editing this post over two years later and no, back om '05 tech support only
confirmed that they can reproduce the crashing. They don't know why its
crashing and had no suggestions or workarounds. It crashes.
So I would put this back to - - unisyn 2, for loading old v1.14 and 1.5
"Performance" files is a no go. I have been able to use v1.14 on an OS9
mac to send the performace, then do a "Get" and "Snapshot" in Unisyn2 on a different mac connected to the same gear to then re-create the
"Performace" but it's all a real pain.