Hi:
I see that Uniwire has been released, with a caveat that Sonar 'should work' but has not been completely compatibility tested.
Two questions:
1. Has anyone gotten Uniwire to work with Sonar Producer 5.2? If so, any tips/comments/gotchas?
2. Will Sonar be compatibility tested at some point?
Thanks!
Uniwire released: Sonar??
-
- KVRian
- 591 posts since 5 Feb, 2004 from southwest england
seems a bit crazy to have not tested on sonar.
Kind regards
Dave Rich
Kind regards
Dave Rich
-
- KVRAF
- 6113 posts since 7 Jan, 2005 from Corporate States of America
The good:
- i'm using Uniwire and Receptor with the current version of Sonar and it works!
- Hey, cool!
The bad:
- The "Launch Receptor Remote" button does nothing. Not so terrible since i can launch it manually anyway.
- The dropouts "light" is lit. The sound seems fine so far. Muse: any response to that?
Now, just in case there are folks out there using their Receptor's SPDIF output/inputs, here's the trouble i went through to solve the horrible dropout problems i started with:
Was getting nothing but dropouts. 100.0Mbps. Sonar 5 Producer. Echo Audio Mona. ASIO, 512 samples. 48KHz samplerate, driver bitdepth locked at 24-bit. Using the 64-bit audio mixing engine. UniWire Instrument Instance indicated 1024 Samples for latency. Couldn't decrease it. Increasing did not eliminate dropouts (just less of them, but still unusable). Increased ASIO latency to 1024 then UniWire drops 1024 off the list and uses the next greatest latency. Consistent no matter which setting i use in my ASIO panel. Changing settings on the VST Wrapper does nothing.
So, i tried another host. i got the same problem in Tracktion 1.6, which uses VSTs natively, so i thought it was't Sonar at fault...
i am using SPDIF as my digital audio output from the Receptor (which i assumed isn't really in use when doing Uniwire??, but apparently Receptor's Uniwire gets timing from SPDIF). The SPDIF output cable goes into a ZSYS z-8.8a Lightpipe Digital Detangler which converts and sends the signal into the ADAT input on the Mona (again, i didn't think it matted since i'm not outputting here, right??). Using the internal clock source or ADAT clock source in the Mona config panel made no difference (except in pitch of course), and disabling the Detangler's Synchronize function left the Receptor physically clicking, unable to sync to a clock source and soundless. So i thought there's no problem with the Detangler...
... but, just to be sure, i flicked off the Detangler... and... no more glitching. The red "dropouts" "LED" stays lit, but the sound seems fine.
So, careful what you have plugged in where.
Muse folks, if you have any tips here, i'd love to know since i need to use the Detangler to get input from my Alesis Fusion 8HD, QS8 ADAT AI3, my TC Electronic Fireworx (i think) and my Akai S6000 Sampler. Ideally, i would like to continue using all this stuff together. The Detangler is a nice switcher and router. At worst, i suppose i can switch it off and on when needed or just stop connecting the Receptor to it since i have Uniwire now (i hope it works as great as it seems to... wow, this is neat). i admit i am new to all this clock synchronization stuff and it's annoying. If you have tips, please send them on to me. i'd prefer to figure out what the problem is rather than bypass my other equipment while using Uniwire.
Cheers for a great product so far!
- i'm using Uniwire and Receptor with the current version of Sonar and it works!
- Hey, cool!
The bad:
- The "Launch Receptor Remote" button does nothing. Not so terrible since i can launch it manually anyway.
- The dropouts "light" is lit. The sound seems fine so far. Muse: any response to that?
Now, just in case there are folks out there using their Receptor's SPDIF output/inputs, here's the trouble i went through to solve the horrible dropout problems i started with:
Was getting nothing but dropouts. 100.0Mbps. Sonar 5 Producer. Echo Audio Mona. ASIO, 512 samples. 48KHz samplerate, driver bitdepth locked at 24-bit. Using the 64-bit audio mixing engine. UniWire Instrument Instance indicated 1024 Samples for latency. Couldn't decrease it. Increasing did not eliminate dropouts (just less of them, but still unusable). Increased ASIO latency to 1024 then UniWire drops 1024 off the list and uses the next greatest latency. Consistent no matter which setting i use in my ASIO panel. Changing settings on the VST Wrapper does nothing.
So, i tried another host. i got the same problem in Tracktion 1.6, which uses VSTs natively, so i thought it was't Sonar at fault...
i am using SPDIF as my digital audio output from the Receptor (which i assumed isn't really in use when doing Uniwire??, but apparently Receptor's Uniwire gets timing from SPDIF). The SPDIF output cable goes into a ZSYS z-8.8a Lightpipe Digital Detangler which converts and sends the signal into the ADAT input on the Mona (again, i didn't think it matted since i'm not outputting here, right??). Using the internal clock source or ADAT clock source in the Mona config panel made no difference (except in pitch of course), and disabling the Detangler's Synchronize function left the Receptor physically clicking, unable to sync to a clock source and soundless. So i thought there's no problem with the Detangler...
... but, just to be sure, i flicked off the Detangler... and... no more glitching. The red "dropouts" "LED" stays lit, but the sound seems fine.
So, careful what you have plugged in where.
Muse folks, if you have any tips here, i'd love to know since i need to use the Detangler to get input from my Alesis Fusion 8HD, QS8 ADAT AI3, my TC Electronic Fireworx (i think) and my Akai S6000 Sampler. Ideally, i would like to continue using all this stuff together. The Detangler is a nice switcher and router. At worst, i suppose i can switch it off and on when needed or just stop connecting the Receptor to it since i have Uniwire now (i hope it works as great as it seems to... wow, this is neat). i admit i am new to all this clock synchronization stuff and it's annoying. If you have tips, please send them on to me. i'd prefer to figure out what the problem is rather than bypass my other equipment while using Uniwire.
Cheers for a great product so far!
- dysamoria.com
my music @ SoundCloud
my music @ SoundCloud
-
- KVRAF
- 6113 posts since 7 Jan, 2005 from Corporate States of America
Followup: my dropouts problem has been coming and going depending on ... i don't know. At this point, the problem seems to exist inside the host and the Uniwire VST. Stopping and starting the audio engine, stopping and starting playback, recording and other tasks in Sonar lead to a state where i had dropouts that were pretty bad and nothing stopped it. Exiting and restarting Sonar fixed the problem for a while, but transport controls and start/stop lead me to silence. No sound from Uniwire. Stopping and starting repeatedly eventually gave me sound back. When dropouts start, increasing latency helps for a while, but then it stops being any help after a while. A restart of the host or a removal and replacement of the ReWire VST in the synth rack seems to "reset" the issue sometimes. Had similar weirdness in Tracktion. i respectfully suggest there are bugs to work out and that Muse needs to do some QA on the Uniwire setup for Sonar and Tracktion. 
It's nice when it works, but it is tentative and unreliable at this point and i have no idea where to look for answers (i still have my Detangler turned off). Transport control seems to influence its behavior, as does audio engine start and stop. i'll keep playing round with it and post more info if i get any.
oh and since i had asked about wireless previously: no, i'm hard wired. Asus P4C800-E Deluxe motherboard with built in Intel Gigabit LAN connected at 100Mbps. Using Intel Pro 1000 CT Network Driver version 7.0.37.0 from Asus (newest). No other networking apps running and no activity noticed when i minimize Sonar (it turns off the audio engine when minimized to "share" the driver with other apps). My connection is routed through a DSL Modem/Router called Westel Versalink 327W. Is it worth trying to put an independent router/hub inbetween the DSL modem and the Receptor/PC so the Uniwire data is not passing through this device? i know nothing about its reliability. i have had no trouble with it in any other application of networking.
Any Windows Configuration recommendations (Windows Firewall is excepted on Sonar.exe and Receptor remote)? i'm going to go browse the docs on Uniwire in case i missed something...
UPDATE: managed to get myself where i have NO audio whatsoever from Uniwire. Exiting and restarting Sonar had no effect.
UPDATE 2: See next message...
ALSO: it pays to read the manual for Uniwire before you dive in. if you're excited and want to get started quickly, slow down and read the Uniwire manual addition first. Don't do as i did
It's nice when it works, but it is tentative and unreliable at this point and i have no idea where to look for answers (i still have my Detangler turned off). Transport control seems to influence its behavior, as does audio engine start and stop. i'll keep playing round with it and post more info if i get any.oh and since i had asked about wireless previously: no, i'm hard wired. Asus P4C800-E Deluxe motherboard with built in Intel Gigabit LAN connected at 100Mbps. Using Intel Pro 1000 CT Network Driver version 7.0.37.0 from Asus (newest). No other networking apps running and no activity noticed when i minimize Sonar (it turns off the audio engine when minimized to "share" the driver with other apps). My connection is routed through a DSL Modem/Router called Westel Versalink 327W. Is it worth trying to put an independent router/hub inbetween the DSL modem and the Receptor/PC so the Uniwire data is not passing through this device? i know nothing about its reliability. i have had no trouble with it in any other application of networking.
Any Windows Configuration recommendations (Windows Firewall is excepted on Sonar.exe and Receptor remote)? i'm going to go browse the docs on Uniwire in case i missed something...
UPDATE: managed to get myself where i have NO audio whatsoever from Uniwire. Exiting and restarting Sonar had no effect.
UPDATE 2: See next message...
ALSO: it pays to read the manual for Uniwire before you dive in. if you're excited and want to get started quickly, slow down and read the Uniwire manual addition first. Don't do as i did
Last edited by Jace-BeOS on Sat May 20, 2006 6:42 am, edited 2 times in total.
- dysamoria.com
my music @ SoundCloud
my music @ SoundCloud
-
- KVRAF
- 6113 posts since 7 Jan, 2005 from Corporate States of America
BIG Sonar Sound Engine/MIDI Gotcha:
If you click on the "panic" button in Sonar (marked as an exclamation point
), it will change the Mixer settings of your Receptor multi so that all channels / tracks, are at ZERO VOLUME. This cost me 1 hour to troubleshoot because the panic button doesn't do that to anything else i know (and i have also been troubleshooting connection issues). So, when you hit "panic," make sure you reset your mix levels back to what they should be. Very annoying. A simple issue that cost me an hour (like forgetting to see if something is plugged in before determining it's dead).
Muse, can you fix / modify this behavior or does "Panic" in Sonar actually send volume commands?
Connection Gotcha:
A SPDIF cable has to be connected between Receptor and your sound card (input on Receptor to output on sound card) IF you are using the Receptor as a sound system for your computer (like an additional sound card and MIDI interface). i tried this and it was problematic due to the complexity of my connections (my sound card allows only SPDIF or ADAT at one time, not both together, and i use ADAT for the extra channels). i have abandoned this for now and am trying to just use Receptor as a Plugin only (which is fine with me; the less complexity, the better; my setup is complicated enough... for me, at least - it actually would be beneficial not to have to use any outputs on the Receptor to simplify my use of it).
If you are NOT going to use your Receptor as a sound and MIDI device, and you are NOT going to be using its outputs and inputs, unplug any ADAT or SPDIF cables going INTO the Receptor, just in case you have any digital clock signals going there that could... confuse things. i seemed to have trouble with it plugged in, but that might be faulty logic on my part due to the .... um... "panic volume issue" that i was also dealing with.
If you click on the "panic" button in Sonar (marked as an exclamation point
), it will change the Mixer settings of your Receptor multi so that all channels / tracks, are at ZERO VOLUME. This cost me 1 hour to troubleshoot because the panic button doesn't do that to anything else i know (and i have also been troubleshooting connection issues). So, when you hit "panic," make sure you reset your mix levels back to what they should be. Very annoying. A simple issue that cost me an hour (like forgetting to see if something is plugged in before determining it's dead).Muse, can you fix / modify this behavior or does "Panic" in Sonar actually send volume commands?
Connection Gotcha:
A SPDIF cable has to be connected between Receptor and your sound card (input on Receptor to output on sound card) IF you are using the Receptor as a sound system for your computer (like an additional sound card and MIDI interface). i tried this and it was problematic due to the complexity of my connections (my sound card allows only SPDIF or ADAT at one time, not both together, and i use ADAT for the extra channels). i have abandoned this for now and am trying to just use Receptor as a Plugin only (which is fine with me; the less complexity, the better; my setup is complicated enough... for me, at least - it actually would be beneficial not to have to use any outputs on the Receptor to simplify my use of it).
If you are NOT going to use your Receptor as a sound and MIDI device, and you are NOT going to be using its outputs and inputs, unplug any ADAT or SPDIF cables going INTO the Receptor, just in case you have any digital clock signals going there that could... confuse things. i seemed to have trouble with it plugged in, but that might be faulty logic on my part due to the .... um... "panic volume issue" that i was also dealing with.
- dysamoria.com
my music @ SoundCloud
my music @ SoundCloud
-
- KVRer
- Topic Starter
- 8 posts since 7 Apr, 2006
Thanks for the in-depth report on your experience!! I very much appreciate it.
I'm gonna try 1.5 and Uniwire this week with Sonar. I'll report back on my experience.
/jeff
I'm gonna try 1.5 and Uniwire this week with Sonar. I'll report back on my experience.
/jeff
-
- KVRist
- 155 posts since 3 Sep, 2005 from London
FYI, I am using cubase and the launch receptor remote button doesn't work for me either.
-
- KVRAF
- 6113 posts since 7 Jan, 2005 from Corporate States of America
-
- KVRer
- Topic Starter
- 8 posts since 7 Apr, 2006
I haven't heard anything. Consequently, I've refrained from trying Uniwire with my setup. I do not like to beta test software.Jace-BeOS wrote:no replies from Muse so far on this one, hey?
/jeff
-
- KVRist
- 58 posts since 13 Jun, 2005
So far my receptor works fine in sonar 4 via uniwire, except the launch receptor remote button. of course i have to use a local keyboard and mouse on the receptor anyway, because when sonar isn't the active window the audio engine stops; consequently playback through the receptor then stops too (long story short, i can't tweak parameters via the receptor remote and hear the results at the same time). it also seems to be a touch on the unstable/glitchy side, but nothing major. definitely better than running audio and midi between the receptor and the computer.