PlanetZ forums - scopeusers.com

How hard would it be to develop a plugin that plays and records as neutrally as possible and works with old Scope cards? Unless there is one already?

quantummastering wrote:How hard would it be to develop a plugin that plays and records as neutrally as possible and works with old Scope cards? Unless there is one already?

It already exists. It's called VDAT recorder.

Sounddesigner wrote:

quantummastering wrote:How hard would it be to develop a plugin that plays and records as neutrally as possible and works with old Scope cards? Unless there is one already?

It already exists. It's called VDAT recorder.

Oh yea, forgot about that one. Can it run on Scope 4.5 and where can I buy it?

quantummastering wrote:

Sounddesigner wrote:

quantummastering wrote:How hard would it be to develop a plugin that plays and records as neutrally as possible and works with old Scope cards? Unless there is one already?

It already exists. It's called VDAT recorder.

Oh yea, forgot about that one. Can it run on Scope 4.5 and where can I buy it?

Yes it runs on 4.5 but the bundle it comes in (Mix N Master bundle) is no longer sold separately. That bundle is now included in 5.0 as stock plugins now (As well as Synths N Samplers bundle). To get VDAT without upgrading to 5.0 may be difficult, you'll need to either buy another card second-hand that has it for 4.5 or buy the bundle second-hand.

I think that 'Mix N Master bundle' wich includes VDAT was only for 6 dsp cards and 14 dsp cards and not for 3 dsp and 4 dsp cards in some situations, this may still be the case. VDAT i think is a virtual emulation of Alesis Adat.

no probl. anyone with sdk6 can do _
as this is no spectacular the funfactor in developement is lost so its just a question of time _and time is money you know_
the only way to rec naturally as possible is 32 bit integer_
with anything else an algo is involved so the result depends on the algo used_
good vibes

tgstgs wrote:no probl. anyone with sdk6 can do _
as this is no spectacular the funfactor in developement is lost so its just a question of time _and time is money you know_
the only way to rec naturally as possible is 32 bit integer_
with anything else an algo is involved so the result depends on the algo used_
good vibes

Are you saying every time I use 32bit integer instead of float, the algorithm will be bypassed and everything will be recorded naturally? And where can I get the SDK 6?

scope is 32 bit int;
as soon as you store in an other format you need some math to fit it in yes;
32 bit int needs no extra computation time its faster than 16 bit for ex.;
good vibes

thanks. didn't realize Scope is 32bit int.

Reading this - is the usage of Asio 2-Flt Source (with Cubase, XITE-1) not the best decision?
Should i use Asio 2 Source instead, which would (as 32 bit integer) use not so much resources?

I know - this question maybe wrong in an development thread, sorry

nomagic wrote:Reading this - is the usage of Asio 2-Flt Source (with Cubase, XITE-1) not the best decision?
Should i use Asio 2 Source instead, which would (as 32 bit integer) use not so much resources?

I know - this question maybe wrong in an development thread, sorry

Apparently it's not. It's best to record at 32bit int regardless of what DAW you use. ASIO 1 at 32bit is fine as well but you won't be able to do direct monitoring or something like that, which could be better in some situation that ASIO 2.

But when recording from analog inputs or from asio source ?

I don't get why it would be better to record asio source in 32bit than asio 2flt ..?

JoPo wrote:But when recording from analog inputs or from asio source ?

I don't get why it would be better to record asio source in 32bit than asio 2flt ..?

Analog will give you the quality of Scope interface AD converters and has nothing to do with ASIO inputs. ASIO 32bit int is better because no extra computation is required, as with ASIO floating point. And floating point can be dangerous because you can record digital distortion and not hear it, but when you export into 24bit or 16bit then it becomes apparent. Even SAW Studio goes up to 32bit int and it's one of the best sounding DAWs available today, and works great with Scope.

Well ! I'm a bit confused...

One learns every day.. Thanks ! I'm going to change my habits right now.

It a little bit strange because when I load asio2 32bit int in Scope, it's written 'out Scope 24bit' in Cubase...

Is it 24 or 32 bit ?

I would prefer to record on 32bit, of course !

So ?

Are the Cubase asio output 24bit ? 32bit ?

Does asio 32bit source module say to Cubase to display 24bit instead of 32, like someone forgot to correct when building the module ?

I vote for a real 32bit module wich make a joke to Cubase.

I guess that's how Cubase recognizes Scope inputs and outs. Remember 32bit is really 24bit. When you are recording music you're recording at 24bits, so that's probably why Cubase is seeing Scope 32 bit sources as 24bits. I don't like or use Cubase. Also, Cubase and Creamware didn't really like each other as companies but Cubase, especially version 4.5 will still work great.

Thank you, Quantum.

I switched to Asio2-32 today.
My DSP-Meter honored this with a decrease on DSP #2: From 78% sync with Asio2-Flt down to 60% !

But i was'nt able to use this with Cubase. Cubase showed all connections with 24 bit, but there was no sound. Nothing, no input, no output. Silence. I restarted everything and even installed the XITE-driver again. I remember that this Asio2-32 worked some years ago. Maybe this problem came with one of the Cubase-updates since then. Or the upgrade from Win 7 to Win 8...

Now i'm back on Asio2-Flt and everything is fine again (78%).

If someone's interested, my system: Windows 8.0 64bit, Cubase 7.5 64 bit, XITE-1 driver vers. v5.1.2709-x64_DE (2011)

If you change asio module in Scope, you have to set them again correctly in Cubase vst connexions and in the asio Scope driver of the device manager too.
I don't see why it wouldn't work well.