duplex audio device question

[dts350z]

I have a Intel DP43tF motherboard with a Realtek ALC888VC sound chip. Windows 7 64 bit.

Latest driver from Realteck installed.

This thing is supposed to be able to record and play back and the same time. In fact can play back two different audio streams at the same time, and record another at the same time. Up to 5.1 channels out the rear jacks, and stereo out the front jacks, and record in the front jack.

My question is I don't see any duplex or input audio devices in Plogue, Only Output MME and Windows Direct Sound devices.

I managed to get around it by using ASIO4ALL Duplex, but in that case I had to use a different sound card for my outputs and the front pannel jack for my input.

Is there anything to be done about this on the Plogue side or is it simply that Realtek is not supplying the needed driver?

Thanks.

[seb@plogue]

Bidule doesn't show input only devices and for MME and DS, duplexes are created by matching names of input and output devices but lately names are getting more and more distinctive, the issue with allowing any pair of i/o to create a duplex device is that we have no way to know if they are part of the same physical device or not...

[dts350z]

Bidule doesn't show input only devices and for MME and DS, duplexes are created by matching names of input and output devices but lately names are getting more and more distinctive, the issue with allowing any pair of i/o to create a duplex device is that we have no way to know if they are part of the same physical device or not...

Here's how ASIO4ALL sees that device:



As a side note it seems like having more than one audio device in the patchbay at a time is a requested feature. I've been able to do that Using ASIO4ALL for instance using the REALTEK mic line in and the Gagport HD 8 ch out at the same time. Seems to work fine, although I've had issues with ASIO4ALL in the past.

In a perfect world multiple devices in the patch bay would be great. Also the ability to "snoop" on an output device as an input. By that I mean capture the audio that some external (non-rewire) program is sending to a device and use it in Plogue.

Thanks as always.

[seb@plogue]

In a perfect world multiple devices in the patch bay would be great.

In a perfect work all audio interfaces would be able to run at the same exact clock! This has been discussed quite a few times on the forums, the main issue with multiple audio interfaces is that none of them are running at the same clock, while sometimes the difference is minimal, it can be quite big, I've seen cases where the 2 interfaces are very noticeably off after a minute or less.

Also the ability to "snoop" on an output device as an input. By that I mean capture the audio that some external (non-rewire) program is sending to a device and use it in Plogue.

On Windows I do not think this is possible venturing into the kernel and do an actual driver...

[dts350z]

Does WASAPI (Windows Audio Session API) get us anything over ASIO and if so is it on the to do list?

[seb@plogue]

Does WASAPI (Windows Audio Session API) get us anything over ASIO and if so is it on the to do list?

Not really anything more than ASIO IIRC, our experience with WASAPI was that the only way we could make all devices work properly would be to go through the WaveRT route (like Cakewalk) and there is a lot of tweaking involved in order to make it work with all drivers.