hi Hans-Christoph,

I found that in the svn version of portaudio (namely in pa_asio.ccp) the driver ReaRoute ASIO is not blacklisted anymore (as committed by Ross Bencina on June 16), so I think that it will be nice to re-compile pd against it. Do you think it's not reliable enough compared to the standard v19?

Anyway I'll give the nightly builds a try, thanks. That should improve general ASIO performance of already working devices.

Best,
S


Hans-Christoph Steiner ha scritto:

Maybe its due to the version of ASIO in use?  I just upgraded the build farm to use ASIO 2.2, so nightly builds of Pd-extended are using that.

.hc

On Jun 30, 2009, at 2:53 PM, Stefano Papetti wrote:

Hello,

I noticed that pd (at least recent versions of both vanilla and extended) and other portaudio-based applications (e.g. Audacity) don't see some ASIO drivers: namely, the RME Fireface 800 and REAPER's ReaRoute ASIO drivers.

I found several posts in different forums around about both issues, and I've drawn the following conclusions:
- the RME ASIO driver simply doesn't work, and nobody actually knows why... However some people report to get ultra-low latencies (3ms) with the MMIO drivers. Moreover, even with the MMIO driver they can use the multi-channel capability of the RME only when set at 48000 Hz (but this is another story...). I will ask RME directly about these issues.
- the ReaRoute ASIO driver is blacklisted by portaudio (as of v19) and therefore discarded...
The latter is my most urgent problem because I need to route audio from pd to REAPER with the lowest possible latency/cpu load.
Please help!

Thanks,
S

_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

----------------------------------------------------------------------------

                            kill your television