@ Jean-Yves Gratius
@ Christoff

I just opened a related to ASIO trouble:  https://github.com/pure-data/pure-data/issues/298

Does any of you experience similar trouble?

@ Jean-Yves Gratius

I was thinking of your Pdvst~ these days as we have a working Pd64bit, the fire started from Christoff’s candle: https://github.com/pure-data/pure-data/pull/275

As I am an Pdvst~ addict may be, if possible, we can have an experimental version. I think is just about compiling it with Msys2 MinGW64?

: )


--

Mensaje telepatico asistido por maquinas.
On 1/24/2018 12:22 PM, Christof Ressi wrote:
ha! finally I've found someone with the same issue. I actually want to investigate it and I'll post it on the bug tracker. 
AFICT two things come together:
there's a problem with the Windows JACK implementation + a problem with the way Pd probes audio devices.

the reason why this doesn't seem to happen with Reaper is because audio devices are only opened when you select them (try to select JackRouter as ASIO device in Reaper and it will also hang for a few seconds).

this problem appears if you try to open a JACK client while the JACK server isn't running. while on Linux it will give up immediately, on Windows it keeps trying for a certain amount of time.

usually this is only a minor annoyance but it's bad when you type 'pd --help' in the console* (because Pd probes all audio devices saved in your preferences) or when you open instances with [pd~].

there are two workarounds so far:

1) just have the jack server running (you don't have to actually use it)
2) compile Pd without jack if you're sure you won't ever use Jack. here's a new WIP branch with working autotools for Windows, so you can build it easily with Msys2 for example. just do ./configure --enable-mmio --enable-asio --disable-jack 
https://github.com/Spacechild1/pure-data/tree/mingw-autotools2

Christof

* a workaround is 'pd -noprefs --help'. doesn't have to be --help actually, can be any unknown command line option.






Gesendet: Mittwoch, 24. Januar 2018 um 14:38 Uhr
Von: "Jean-Yves Gratius" <jyg@gumo.fr>
An: "Christof Ressi" <christof.ressi@gmx.at>, "pd-list@lists.iem.at" <pd-list@lists.iem.at>
Betreff: Re: Aw: [PD] Why does it take so long time for switching pd audio into ASIO (via port audio) mode ?

Bingo !
i get error messages "Execution of JACK server  failed", and several 
"cannot connect to named pipe after wait".
I tried to start pd with --disable-jack (as found here 
https://github.com/pure-data/pure-data/issues/25 ) but pd doesn't start.

Le 24/01/2018 à 13:04, Christof Ressi a écrit :
I also have the issue that ASIO audio settings take some time to open (and i know the reason). Just to be sure we're on the same boat: can you open pd.com from the cmd terminal (or pd.exe from a mingw terminal) and see if you get JACK related error messages when you open the ASIO audio settings?

Gesendet: Mittwoch, 24. Januar 2018 um 11:30 Uhr
Von: "Jean-Yves Gratius" <jyg@gumo.fr>
An: pd-list@lists.iem.at
Betreff: [PD] Why does it take so long time for switching pd audio into ASIO (via port audio) mode ?

Hi
another question regardind pd 0.48-1 on windows:

When i switch onto asio mode, it take 10 seconds before the audiosetting
box appears.
Is this a normal behaviour ?  (Windows 8.1, intel i-5)
And sometimes the interface seems very sensitive to dropouts and can
desync, and i have to restart it (especially when i use a heavy patch).

As a comparison, with Reaper, switching from one audio system to another
is quasi instantaneous.

before making further investigation, i wanted to know if other users may
have the same experience .

thanks,
JYG


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

---
Cet email a fait l'objet d'une analyse antivirus par AVG.
http://www.avg.com


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