Hey all,
Im thinking of getting a scope project card, its a complex system and would really like some advise to make sure things are straight.
First off i plan on using 2 pcs networked over midi, so my project pc will loose the maudio192 and be replaced with the scope.
First off how many in outs does the card have, i want to be able to assign a bus in Acid pro route it to the scope out and into a kaospad and back in. Can i do that with a the scope? I need to have alteast 2 outs one going into my mixer and into my monitors and 1 that i can route into the koas pad.
2nd iam i on the right track with this livebar, can i for example create a mixer, assign the minimax to say midi channel 3 get acid to receive midi channel 3 and sequence the minimax like a hardware unit is that correct? i guess i could also assign any midi track in acid to a bus and spit it out to the scope and apply effects from its mixer? is that how it works.
thanks very much any help or advice it appreciated as im unsure about this sysem and want it crystal clear before a purchase.
Thinking of going scope
2 : YES, thats exactly how it works
1:
the project card has a set of stereo analog in and analog out
+ it has an digital in and out
if you need more than 2 analog outputs/inputs you have to take the adat ins and outs that the project card has.
This gives you access to much more channels if you buy an aditional adat interface ( f.e the A16 has 16 analog ins and outs)
You can access these outputs in every way you want.
These are called the hardware i/os
Additionally you have software I/Os. So you can use many parallel ASIO outputs from your software to route every softwarechannel from acid into everything scope has.
For example a mxer or directly to the hardware i/os.
You will find an endless amount of devices, effects, software I/Os and hardware I/Os which you can connect in anyway you could expect:
a simle example using the asio device and the ADAT device:
But I warn you, if you once get used to this system, you will get addicted !
1:
the project card has a set of stereo analog in and analog out
+ it has an digital in and out
if you need more than 2 analog outputs/inputs you have to take the adat ins and outs that the project card has.
This gives you access to much more channels if you buy an aditional adat interface ( f.e the A16 has 16 analog ins and outs)
You can access these outputs in every way you want.
These are called the hardware i/os
Additionally you have software I/Os. So you can use many parallel ASIO outputs from your software to route every softwarechannel from acid into everything scope has.
For example a mxer or directly to the hardware i/os.
You will find an endless amount of devices, effects, software I/Os and hardware I/Os which you can connect in anyway you could expect:
a simle example using the asio device and the ADAT device:
But I warn you, if you once get used to this system, you will get addicted !
Yeh thanks alot for that hifi, appreciated. It will be on its way next week, only concern i have at the moment is how am i going to get the free synth and sampler pack now it has changed hands. Other than that this card should be amazing. I guess now i can work out some way of getting some decent sidechain compression going on in acid and not have to look to pro tools. So expect another message on some routing for that very very soon
Another question for the scope support team
I have got my plan of attack worked out in my head.
1st system for scope used as the main DAW running acid pro, scope, reason and some natives. I cannot figure out how im going to get decent latency in acid for the vstis if i cannot use the scope asio drives, i use a midi keyboard and padcontrol on here.
2nd system will run reaktor, and some native plugins using max fx teleoprt, this system will have a maudiophile, using a axiom49.
I guess what im asking is that the best setup, i wont be using adat. Will the latency caused by not getting asio drivers in acid effect the sequencing of my vstis, reason reaktor ect? or will it effect the midi keyboards latency?
Is it possible to run another asio card alongside scope and use that as my acid asio device. Ahh its doing my head in as im worried about the effect i will get on the native side by using scope.
I have got my plan of attack worked out in my head.
1st system for scope used as the main DAW running acid pro, scope, reason and some natives. I cannot figure out how im going to get decent latency in acid for the vstis if i cannot use the scope asio drives, i use a midi keyboard and padcontrol on here.
2nd system will run reaktor, and some native plugins using max fx teleoprt, this system will have a maudiophile, using a axiom49.
I guess what im asking is that the best setup, i wont be using adat. Will the latency caused by not getting asio drivers in acid effect the sequencing of my vstis, reason reaktor ect? or will it effect the midi keyboards latency?
Is it possible to run another asio card alongside scope and use that as my acid asio device. Ahh its doing my head in as im worried about the effect i will get on the native side by using scope.
you can certainly use the asio modules with acid and get low latency!
the asio source and destination modules ARE the ins and outs for acid. you can connect them to ANY audio module which includes mixers, effects and ANY of the physical i/o.
think of your sequencer as a hardware recorder. the asio source/dest and sequencer midi source/dest modules are the jacks for that recorder. the routing window is a room that the recorder is in. the hardware jacks to the real world show up in that room as do any synths, mixers or effects that you use in scope. everything connects. if you use wav drivers as well, you can even stream in and out of acid and another program(s).
the asio source and destination modules ARE the ins and outs for acid. you can connect them to ANY audio module which includes mixers, effects and ANY of the physical i/o.
think of your sequencer as a hardware recorder. the asio source/dest and sequencer midi source/dest modules are the jacks for that recorder. the routing window is a room that the recorder is in. the hardware jacks to the real world show up in that room as do any synths, mixers or effects that you use in scope. everything connects. if you use wav drivers as well, you can even stream in and out of acid and another program(s).
-
hubird
This looks like a serious ADAT kind of DAW, so I advise you to buy the Alesis Q20 reverb on eBay for peanuts. I paid cost and 10% for mine years ago, and will never sell it as it has the best vocal plates around, and it's small space ambience rooms are extremely accurate. One of our dwellers here programmed it back in the day, and only received an A6 Andromeda for his services, a rather meager offering. But the Q20 rarely comes up on eBay as few will part with it once they have it. But it is a perfect mate w/ ADAT's going in and out of Scope. A good software based DSP reverb is DAS's RM160, as it uses little DSP and sounds fantastic also. I prefer hardware, thereby allowing more synths.
Hopefully You Live By Many 7 / 11 convenience stores, as you will need to rob them once you get started w/ Scope.
Item number: 190129036249
www.ebay.com
Strength Through Superior Dsps,
Hopefully You Live By Many 7 / 11 convenience stores, as you will need to rob them once you get started w/ Scope.
Item number: 190129036249
www.ebay.com
Strength Through Superior Dsps,
Thats the thing, i can record anything i want coming from my mixers line ins into scope, but these sounds are in the box, being sequenced in live, so there is no use selecting ext ins for scope? i think i need to record the asio device or something.. i dont know i will keep trying, but how does everyone else record the scope synths.
thanks
btw scope4live dont need a reverb thanks got plenty of much much better native units.
thanks
btw scope4live dont need a reverb thanks got plenty of much much better native units.