Dear All,
I just setup my new DAW, Intel dualcore. Everything works just like the good old days except UniWire. Took me one day to find out that little "multi processing" button in Nuendo's device setting must be turned off to make UniWire work.
I filed a help ticket at Plugorama, and got the reply that they are aware of this problem, and plan to fix it, but it will not be "in a near term."
Quite frustrating. Buy a dualcore but can only use it like a singlecore, just because of the UniWire driver out of date. The manufacture is aware of the problem but decide that customers can wait longer.
They did suggest one workaround, which didn't work for me. The suggestion is to launch UniWire Instruments only on channel 1,3,5,7 or 2,4,6,8, i.e. all odd channel or all even ones. I tried all kinds of odd and even definition. Nothing worked.
Anybody with a dualcore system and Receptor running UniWire?
UniWire + Dual Core = No Go. Any Suggestion?
-
- KVRist
- 54 posts since 15 Jan, 2006 from Taiwan
Arys Chien
Deep White Studio
Deep White Studio
-
- KVRAF
- 9590 posts since 17 Sep, 2002 from Gothenburg Sweden
Use midi and audio connections like in the good old days.
-
- KVRer
- 27 posts since 1 Oct, 2005
WIll this be an issue with all current Macs (all of which are dual-core)? Perhaps this expains the delays in UniWire 1.1 ....
-
- KVRist
- Topic Starter
- 54 posts since 15 Jan, 2006 from Taiwan
That's not what I did in MY good old days with Receptor.jupiter8 wrote:Use midi and audio connections like in the good old days.
And certainly not what I want to do in the good new future with a Receptor that could have had a up-to-date driver. The latest version is from eight months ago.
Arys Chien
Deep White Studio
Deep White Studio
-
- KVRian
- 520 posts since 11 Sep, 2003 from Berlin, Germany
The same problem persists with Karnage: when said option is enabled it crashes cubase.
BUT: This option does not have to be turned on for dual-cores. I've been in contact with Steinberg about this and was told that this is only really necessary for MORE than 2 cores.
I'm running Cubase SX3 on dual-core with the option disabled and it's running on both cores fine. Just open the taskmanager and see for yourself: You can still get both cores to 100% with cubase.
BUT: This option does not have to be turned on for dual-cores. I've been in contact with Steinberg about this and was told that this is only really necessary for MORE than 2 cores.
I'm running Cubase SX3 on dual-core with the option disabled and it's running on both cores fine. Just open the taskmanager and see for yourself: You can still get both cores to 100% with cubase.
-
- KVRAF
- 9590 posts since 17 Sep, 2002 from Gothenburg Sweden
You have 3 choices here.Arys Chien wrote:That's not what I did in MY good old days with Receptor.jupiter8 wrote:Use midi and audio connections like in the good old days.
And certainly not what I want to do in the good new future with a Receptor that could have had a up-to-date driver. The latest version is from eight months ago.
1. Not use the Receptor.
2. Only using half of your computers resources.
3. Midi and audio going oldschool thru analog connectors.
I know what i'd choose.
-
- KVRist
- Topic Starter
- 54 posts since 15 Jan, 2006 from Taiwan
Hi bleebsen,
We've checked out the readings in the taskmanager. However the realworld situation is different from what it shows. We can launch more plug-ins with the Multi Processing feature turned on.
24 PSP 608 with Multi Processing off, Nuendo starts to choke. Turn on the Multi Processing, the audio is smooth again. 6 more PSP 608 (30 of them now), still no pop no crackle.
That's why we believe this button still matters.
If you are interested with a test yourself, please let me know the result. I'd love to find out how it really is then just listen to the companies.
------
To jupiter8,
It's really sad to see you ignoring my frustration with a problem you don't have. Maybe you don't care, but let me know why I can't choose your smart choice number 3.
I place the Receptor in the other room, along with the PCs, because they are too noisy. I only need the monitor cables, the usb cables and the cables for RME Digiface into the control room and I'm able to work. The Receptor is connected to the router, also in the other room, and all is done with the UniWire feature.
With the UniWire Instruments intergrated into Nuendo's mixer, I'm able to apply plug-ins from like UAD-1 and PowerCore to the sound coming out of the Receptor, without having to buy 2 good toslink cables and the optional ADAT interface from Muse, (which I believe they won't give me for free just because they are not fixing their problem now) and input-monitoring 16 tracks to route them into Nuendo's mixer to apply the plug-ins.
While Muse should just do their job. I'm not expecting every company to fix a major problem within one week, but 8 months is simply too long to tolerate.
We've checked out the readings in the taskmanager. However the realworld situation is different from what it shows. We can launch more plug-ins with the Multi Processing feature turned on.
24 PSP 608 with Multi Processing off, Nuendo starts to choke. Turn on the Multi Processing, the audio is smooth again. 6 more PSP 608 (30 of them now), still no pop no crackle.
That's why we believe this button still matters.
If you are interested with a test yourself, please let me know the result. I'd love to find out how it really is then just listen to the companies.
------
To jupiter8,
It's really sad to see you ignoring my frustration with a problem you don't have. Maybe you don't care, but let me know why I can't choose your smart choice number 3.
I place the Receptor in the other room, along with the PCs, because they are too noisy. I only need the monitor cables, the usb cables and the cables for RME Digiface into the control room and I'm able to work. The Receptor is connected to the router, also in the other room, and all is done with the UniWire feature.
With the UniWire Instruments intergrated into Nuendo's mixer, I'm able to apply plug-ins from like UAD-1 and PowerCore to the sound coming out of the Receptor, without having to buy 2 good toslink cables and the optional ADAT interface from Muse, (which I believe they won't give me for free just because they are not fixing their problem now) and input-monitoring 16 tracks to route them into Nuendo's mixer to apply the plug-ins.
While Muse should just do their job. I'm not expecting every company to fix a major problem within one week, but 8 months is simply too long to tolerate.
Arys Chien
Deep White Studio
Deep White Studio
-
- KVRist
- 76 posts since 17 Jun, 2003 from USA (Washington, DC)
I am confused by your statement. Didn't you just create a support ticket?Arys Chien wrote: While Muse should just do their job. I'm not expecting every company to fix a major problem within one week, but 8 months is simply too long to tolerate.
I realize the "8 months" you are quoting relate to the last Receptor OS (v1.5) that was released in May, 2006. However, has Muse actually been aware of the problem for eight months?
-
- KVRist
- Topic Starter
- 54 posts since 15 Jan, 2006 from Taiwan
Hi Martin,
The answer I got from the help ticket was, they were aware of the problem and planned to fix it, but it would not be in the near term.
The latest reply from them is that, they have a workaround that works for Cubase SX. They didn't know that it doesn't work for Nuendo.
That really makes me wonder. Am I really the first person on earth to use Nuendo and Receptor together with a Intel dual core system?
The answer I got from the help ticket was, they were aware of the problem and planned to fix it, but it would not be in the near term.
The latest reply from them is that, they have a workaround that works for Cubase SX. They didn't know that it doesn't work for Nuendo.
That really makes me wonder. Am I really the first person on earth to use Nuendo and Receptor together with a Intel dual core system?
Arys Chien
Deep White Studio
Deep White Studio