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:
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.
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
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
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 mailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
kill your television
I haven't touched portaudio stuff so I don't know what to say there,
perhaps someone else can say something about that.
.hc
On Jul 1, 2009, at 10:21 AM, Stefano Papetti wrote:
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
I spent 33 years and four months in active military service and during
that period I spent most of my time as a high class muscle man for Big
Business, for Wall Street and the bankers. - General Smedley Butler
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.
I tried the latest autobuild of pd-extended 0.42-5 for windows but it doesn't work: after executing pd nothing happens and I don't even see the process pd.exe in task manager. I guess it just crashes.
S
.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 mailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
kill your television
Oh well... please post a bug report if you can figure any details out.
.hc
On Jul 1, 2009, at 11:24 AM, Stefano Papetti wrote:
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.I tried the latest autobuild of pd-extended 0.42-5 for windows but
it doesn't work: after executing pd nothing happens and I don't even
see the process pd.exe in task manager. I guess it just crashes.S
.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
"It is convenient to imagine a power beyond us because that means we
don't have to examine our own lives.", from "The Idols of
Environmentalism", by Curtis White
- 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.
I can say that i've never had problems with the RME drivers, especially ASIO with various applications. If there are problems i suspect them to be related to some old portaudio code used in Pure Data. Up-to-date portaudio versions work flawlessly with RME drivers. Concerning MMIO i can hardly imagine how people can reach low latencies with it, given the architecture of this interface.
gr~~~
Thomas Grill ha scritto:
- 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.
I can say that i've never had problems with the RME drivers, especially ASIO with various applications. If there are problems i suspect them to be related to some old portaudio code used in Pure Data. Up-to-date portaudio versions work flawlessly with RME drivers.
I don't know many other portaudio-based applications, but I can say that the latest Audacity also can't properly see the Fireface ASIO drivers... Of course native ASIO applications (e.g., Ableton Live, Pianoteq, Reaper) work flawlessly. As for pd-extended 0.40-3, 0.41-4, and pd vanilla 0.42-5 the Fireface driver report:
"Fireface Analog (1+2) MME" ... up to "(9+10) MME" "Fireface Analog (1+2)" ... up to "(9+10)"
so I thought that the latest were reffering the ASIO driver, even if no explicitly mentioned. Indeed pd allows to select a pair (loosing the multichannel feature...) of ins/outs from the last line as ASIO drivers, however they don't work unless I set latency to 40ms... I tried on two different machines - a desktop and a laptop - using the latest RME drivers (v2.95) with identical results. Also, Audacity reports the same list of devices above plus a prefix "MME: ", a nothing concerning ASIO. Finally, I often use asio4all with a pc's internal audio card in order to get decently low latencies, however both pd and Audacity can't see the virtual driver ASIO4ALL while the Fireface is connected, i.e. as soon as it is disconnected the driver ASIO4ALL shows up again... Well, I guess I'd better post this on portaudio's mailing list.
Concerning MMIO i can hardly imagine how people can reach low latencies with it, given the architecture of this interface.
I agree... I tried myself and I can't go below 40ms.
Best, S
Dear Thomas,
Thomas Grill ha scritto:
I can say that i've never had problems with the RME drivers, especially ASIO with various applications. If there are problems i suspect them to be related to some old portaudio code used in Pure Data. Up-to-date portaudio versions work flawlessly with RME drivers.
I checked my issue with 2 applications (made by a colleague) which have been compiled respectively against the latest portaudio available from the website and from svn: they both can see the driver "Fireface ASIO" and its properties correctly. Therefore I suspect there's something wrong either with the version used by pd and Audacity, or their utilization of portaudio. If I find the time, I'll try compiling pd against those versions of portaudio to see what happens.
Best, S