Anyone using Creamware soundcard with T or T2 ?
-
- KVRist
- 70 posts since 26 Jul, 2004
I am thinking to buy the Scope Home edition to replace my shitty M-audio USB DUO.
I would like to know:
1. Does it support multiclient *at the same time* ? That means I can hear MME and ASIO sound at the same time.
2. Does 'XTC' mode exist in the new Scope card? work well with Tracktion?
3. The DSP chips on it looks pretty old. Is the processing power enough? I don't see so much chips on
UAD card..
e.g. could it run 3 reverb and 2 synths at the a time?
4. What about the recording quality? good convertor?
5. Do you find any more shortcoming?
Thanks!
Ben
I would like to know:
1. Does it support multiclient *at the same time* ? That means I can hear MME and ASIO sound at the same time.
2. Does 'XTC' mode exist in the new Scope card? work well with Tracktion?
3. The DSP chips on it looks pretty old. Is the processing power enough? I don't see so much chips on
UAD card..
e.g. could it run 3 reverb and 2 synths at the a time?
4. What about the recording quality? good convertor?
5. Do you find any more shortcoming?
Thanks!
Ben
-
- KVRAF
- 1530 posts since 20 Feb, 2003
you'll get much better answers here:
http://www.planetz.com/forums/index.php
http://www.planetz.com/forums/index.php
-
- KVRist
- Topic Starter
- 70 posts since 26 Jul, 2004
Thanks for the link.
I spent an half hour on the forum, look like there are lots of 'workaround' floating..
Maybe I should save my money to upgrade my PC and stick with those great and free native VST plugs.
I spent an half hour on the forum, look like there are lots of 'workaround' floating..
Maybe I should save my money to upgrade my PC and stick with those great and free native VST plugs.
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRAF
- 1530 posts since 20 Feb, 2003
have to agree there. creamware synths blow away most vsti for quyality imho, but integration with vst is poor. i have raised this with the creamware crowd in the past, but since they all seem to use the card like external hardware it's not an issue to most users.
but i think that it's one factor which has really held creamware back.
but then is there any way a dsp card can work like real vsti and be able to bounce and render like native ?
but i think that it's one factor which has really held creamware back.
but then is there any way a dsp card can work like real vsti and be able to bounce and render like native ?
-
- KVRist
- 179 posts since 15 Oct, 2003 from Norway
I use Tracktion with two Pulsar II in XTC mode with success, but you do need to do some tweaking to have it all work. There are huge possibilities of CW would only get their asses on developing this.
Anyway, planez.com will help you with all you need.
In normal mode you will be able to have standard wave drivers as well as ASIO running. I don't think this works in XTC-mode.
With 3 DSPs you can't run much at a time at all. I have 12 (2*12). Look around on eBay, you get them quite cheap.
Home = Luna II (3 sharcs)
Project = Pulsar II (6 sharcs)
Pro = Scope II (14/15 sharcs)
Anyway, planez.com will help you with all you need.
In normal mode you will be able to have standard wave drivers as well as ASIO running. I don't think this works in XTC-mode.
With 3 DSPs you can't run much at a time at all. I have 12 (2*12). Look around on eBay, you get them quite cheap.
Home = Luna II (3 sharcs)
Project = Pulsar II (6 sharcs)
Pro = Scope II (14/15 sharcs)
-
- KVRist
- 397 posts since 7 Jun, 2003 from Sedna the Red Planet
I use T2 with Scope Professional.
Tips
1)Don't use XTC mode - spend a few days learning normal mode - it isn't that hard
2)Use a Pentium 4 with an ASUS motherboard with an intel chipset.
3)Get info from Planet Z Forum on what hardware to use.
4)Once you are set up no problems but it takes time - it isn't a plug in and go card
5)Its worth the effect because the synths are the best you can get on a PC
Tips
1)Don't use XTC mode - spend a few days learning normal mode - it isn't that hard
2)Use a Pentium 4 with an ASUS motherboard with an intel chipset.
3)Get info from Planet Z Forum on what hardware to use.
4)Once you are set up no problems but it takes time - it isn't a plug in and go card
5)Its worth the effect because the synths are the best you can get on a PC
-
- KVRist
- 252 posts since 18 Jun, 2001 from UK and NY
Have to echo that Minimax and P5 dump on other emus. Modular3 with adern,Ambient and Solaris totally wipe the floor with any VSTi. I bought Scope pro and 2 SRBs and got a deal on all sw installed into a purpose built machine by Red Sub, expensive (12k) but lethal. Used on many releases and media projects. More than paid for itself.
-
- KVRer
- 23 posts since 25 Jun, 2003 from Los Angeles
Yeah, I have the PowerPulsar (now called Scope Professional), and could never get the XTC mode to work properly. But I'm very comfortable with the Scope platform anyway, so I don't mind treating all of the Scope devices as "external". I tend to use the synths, the mixers, and some FX. Helps take a load off of the CPU and keeps overall latencies down to a minimum, even with complex projects.
You can take the man out of the 80's, but you can't take the 80's out of the man. - Paul Gilbert
-
- KVRAF
- 1509 posts since 28 Oct, 2003 from London, UK
Definitely get to learn the normal Scope OS - it lacks integration with VST (although you can stream into and out of large amounts of ASIO channels) but it's only 1 extra thing to load - the possibilities you get far outweigh the hassle of loading an extra program and loading a corresponding Scope project along with your sequencer projects.
The main thing you gain is zero latency realtime playability, something which is noticably more natural feeling than buffer-based native CPU stuff, and *light years* away from things like Powercore and UAD1 (which incidentally are still amazing tools, it's just that they're much nicer for mixdown than the actual production process).
This isn't always needed in order to make great music but it is nice if you favour the live, hands-on approach.
The Scope OS also has an infinite variety of routing possibilities, so you're actually much less limited than with the normal channel-based approach of host sequencers (I do know that Tracktion is much better than most in this area though
).
coldmachine - that sounds like a fun setup you have there - is that 2 Scope SRBs (as in 15-dsp ones), i.e. 45 dsps?
The main thing you gain is zero latency realtime playability, something which is noticably more natural feeling than buffer-based native CPU stuff, and *light years* away from things like Powercore and UAD1 (which incidentally are still amazing tools, it's just that they're much nicer for mixdown than the actual production process).
This isn't always needed in order to make great music but it is nice if you favour the live, hands-on approach.
The Scope OS also has an infinite variety of routing possibilities, so you're actually much less limited than with the normal channel-based approach of host sequencers (I do know that Tracktion is much better than most in this area though
coldmachine - that sounds like a fun setup you have there - is that 2 Scope SRBs (as in 15-dsp ones), i.e. 45 dsps?
Mayur Maha
FXpansion Audio [http://www.fxpansion.com]
FXpansion Audio [http://www.fxpansion.com]
- KVRAF
- 37508 posts since 14 Sep, 2002 from In teh net
I think the reason many of us prefer to work in Scope rather than shoehorn Scope into an ASIO setup is that it gives more flexibility and also means that any Scope synths and effects have zero latency. None of the other DSP cards that work as VST's can do that - hence the need for workarounds like PDC. I have tried using XTC (VST) mode in Scope a few times and it's not as problematic or buggy as has been suggested here but even so I still prefer the immediacy that zero latency offers and it's not a problem to use my sequencer within the Scope environment - having experimented with both I can't see any real advantages to using XTC mode.Cabinfever wrote:have to agree there. creamware synths blow away most vsti for quyality imho, but integration with vst is poor. i have raised this with the creamware crowd in the past, but since they all seem to use the card like external hardware it's not an issue to most users.
but i think that it's one factor which has really held creamware back.
I use T2 as well - to me it's the best designed host to work with Scope as it's so easy to setup.
-
- KVRer
- 23 posts since 25 Jun, 2003 from Los Angeles
Just a quick update: I had recently switched from CubaseSX to Traction2, and have been pretty happy so far.
However, a few days ago, I started working on the routing for an "external" Scope FX rack. That way, I could do bus sends to Creamw@re devices in Scope mode.
Unfortunately, ANY time I assigned ANY Tracktion channel's output to other than the default IO, performance suddenly became unworkable. I mean, SEVERELY damaged.
Didn't matter if I set Traction's default out to 1/2, 3/4, or whatever. Anytime I assigned a channel to something other than that default, the mouse would start to stutter, and recording became unreliable. Even if no Creamw@re devices were attached to the ASIO channel.
As another element in the equation, Tracktion has been spoiling me with the "one-stop-shop" interface, so that I was starting to get tired of toggling back and forth between Scope and Tracktion, with all of the device windows that Scope entails. I guess I was willing to deal when I was using the pop-up-heavy Cubase.
Finally, I was getting annoyed with the intermittent crashes when I would change the Scope device or routing config. I mean, I should be able to add a Synth without having to kill and relaunch Tracktion, right? Sometimes even a BSoD would occur.
So instead of spending days futzing with all of these issues, I decided to give XTC another go. For some reason this time around it just worked. Maybe XTC likes T2 more than my previous software configs. Whatever the reason, I'm now a very happy XTC convert. Yeah, I'm singing a different song than I was a few days ago, but damn! This thing is VERY stable, and my Traction setup is GREATLY simplified because of it. Now I get all of the SWEET Scope FX and synths as VST devices.
Oh, and DSP usage seems to be lower running in XTC.
I guess I'm digging having ALL my devices behave consistently withing the same framework.
Now, the only thing I'm jonesing for now is using the Modular and the STS3000. I also haven't managed to get Amper to work in XTC yet, but between AmpliTube and the Simuanalog Guitar Suite, I'm doing okay for guitar tones.
However, a few days ago, I started working on the routing for an "external" Scope FX rack. That way, I could do bus sends to Creamw@re devices in Scope mode.
Unfortunately, ANY time I assigned ANY Tracktion channel's output to other than the default IO, performance suddenly became unworkable. I mean, SEVERELY damaged.
Didn't matter if I set Traction's default out to 1/2, 3/4, or whatever. Anytime I assigned a channel to something other than that default, the mouse would start to stutter, and recording became unreliable. Even if no Creamw@re devices were attached to the ASIO channel.
As another element in the equation, Tracktion has been spoiling me with the "one-stop-shop" interface, so that I was starting to get tired of toggling back and forth between Scope and Tracktion, with all of the device windows that Scope entails. I guess I was willing to deal when I was using the pop-up-heavy Cubase.
Finally, I was getting annoyed with the intermittent crashes when I would change the Scope device or routing config. I mean, I should be able to add a Synth without having to kill and relaunch Tracktion, right? Sometimes even a BSoD would occur.
So instead of spending days futzing with all of these issues, I decided to give XTC another go. For some reason this time around it just worked. Maybe XTC likes T2 more than my previous software configs. Whatever the reason, I'm now a very happy XTC convert. Yeah, I'm singing a different song than I was a few days ago, but damn! This thing is VERY stable, and my Traction setup is GREATLY simplified because of it. Now I get all of the SWEET Scope FX and synths as VST devices.
Oh, and DSP usage seems to be lower running in XTC.
I guess I'm digging having ALL my devices behave consistently withing the same framework.
Now, the only thing I'm jonesing for now is using the Modular and the STS3000. I also haven't managed to get Amper to work in XTC yet, but between AmpliTube and the Simuanalog Guitar Suite, I'm doing okay for guitar tones.
You can take the man out of the 80's, but you can't take the 80's out of the man. - Paul Gilbert
