PlanetZ forums - scopeusers.com

Hi,

Cubase and Nuendo are able to send and receive audio in 32bit INTEGER to and from their flagship 32bit integer interfaces.
I know this won't be done any soon, but in theory it is possible to make 32bit INTEGER ASIO drivers for Scope for bitperfect 32bit communication with Cubase and Nuendo. So recordings per Cubase Nuendo would be the same as with VDAT.

yes, Scope can use a 32bit integer ASIO interface, however that is not the same as 32bit integer in VDAT.
translation between systems is never perfect.

Yes as, someone stated in another post, ASIO is bypassed with VDAT.

I mean a 32bit integer ASIO source and dest, additionally to the existing 24bit and 32bit float software IOs. It would be a dream to move audio to and from Nuendo in 32bit integer. Don't know whether it is possible to program such a 32bit integer ASIO software IO yet.

tonatona wrote: ↑Fri Mar 12, 2021 2:30 pm I mean a 32bit integer ASIO source and dest, additionally to the existing 24bit and 32bit float software IOs. It would be a dream to move audio to and from Nuendo in 32bit integer. Don't know whether it is possible to program such a 32bit integer ASIO software IO yet.

Aren't the ASIO 2 Source/Destination already 32bit integer?

According to the manual ASIO1-32 can do 24bit and 32bit integer. But in my Xite-1 there is no ASIO1-32 software IO. What is it called on the Xite-1 and how do i know what is currently used, 24bit or 32bit integer?

ASIO source or ASIO2 source.

it is whatever bit depth that the sequencer is running.

garyb wrote: ↑Fri Mar 12, 2021 3:59 pm ASIO source or ASIO2 source.

it is whatever bit depth that the sequencer is running.

How does that work Gary? I thought the DAW slaves to the audio card drivers.

Just hazarding a guess, but it sounds like for integer, the ASIO driver probably uses doubleword and whatever the host sends will then work (16bits, 24bits, 32bits).

it's magic...

garyb wrote: ↑Sat Mar 13, 2021 7:57 amit's magic...

What type of magic? Looks like this soundcard was built to handle the future. So flexible.

Thank you for all your answers.
If i use ASIO2 32 float source the IOs in Nuendo are labeled as 32bit float source. But if i use ASIO2 source the IOs in Nuendo are labeled as 24bit. Nuendo runs at 64bit floating point with 32bit integer in project properties. So does the communication runs at 24bit integer or 32bit integer?
I called Steinberg today. They told that Nuendo supports 32bit integer from Scope if Scope does offer it, because Nuendo supports anything out there.
Cubase got the 64bit floating point engine 2017, many years after the introduction of the Xite-1, so i thought that the Scope ASIO drivers have to be reprogrammed or adjusted to it.

You can process any track data (whatever bit depth) with the full resolution of the DAW‘s audio engine, WITHOUT perceivable loss. The resolution matters in MIX CONTEXT, not on track (source) level.

The lowest loudness of a 16 bit word represents a level of -96db, which is what my interface preamp delivers with volume full down. The respective figure of a 24bit word represents -144dB, which isn‘t even physically reproducable.

In other words, the difference between passing 24bit INT audio (the mantissa or significand portion of the floating point value from a 32bit FLT value) and 32bit INT audio (the significand from a 64bit FLT value) is below -144dBf.

There were many discussions of 32bit FLT vs. 24bit INT in year passed on these forums, that might be worth searching out.

Also, make sure you're using the Scope PCI (if using PCI cards) version of the ASIO driver, if you're on Scope 7 or higher.

valis wrote: ↑Mon Mar 15, 2021 7:46 pm In other words, the difference between passing 24bit INT audio (the mantissa or significand portion of the floating point value from a 32bit FLT value) and 32bit INT audio (the significand from a 64bit FLT value) is below -144dBf.

There were many discussions of 32bit FLT vs. 24bit INT in year passed on these forums, that might be worth searching out.

Also, make sure you're using the Scope PCI (if using PCI cards) version of the ASIO driver, if you're on Scope 7 or higher.

I've just noticed I don't have Scope PCI ASIO available as an option on a different partition setup for Scope 7. It only offers Scope ASIO. Have I installed the wrong drivers? What do the PCI ones offer? Do the specify code for the PCI boards and manage them better?

Thanks

Imho it‘s just a matter of labels. Scope 5.1 installed as „Scope PCI“ on my system.

So the bigger the numbers, the better the sound?
Awesome...

The more IMPRESSIVE the sound.

garyb wrote: ↑Thu Mar 11, 2021 7:07 am yes, Scope can use a 32bit integer ASIO interface, however that is not the same as 32bit integer in VDAT.

What´s the difference ?

Music Manic wrote: ↑Thu Mar 11, 2021 2:03 pm Yes as, someone stated in another post, ASIO is bypassed with VDAT.

Q:
When using Cutmaser (Pro) w/ SCOPE PCI,- is that the same than VDAT,- 32Bit integer and bypassing ASIO (WHEN there are no ASIO modules in the project) ?

Just askin´ because I own a single Pulsar II w/ Cutmaster Pro key which might run perfect in my oldest WinXP machine.
The installation files are "Cutmaster v4.0" and/or "Cutmaster xp v5.01".
Do they run w/ Cutmaster Pro key ?

And,- when installing Cutmaster Pro (or v4.0 / xp v5.01) - is installation of SCOPE application (v4.0 / 4.5 or 5.1) essential too ?



Bud

I guess so seeing it’s DSP based but I’m sure Gary can confirm it.