Yeah, this makes the most sense: try the user value, if it's too low, then use the hardware value and print a notice. At the very least, Pd will keep working. :) I do something similar in a work project that uses Portaudio and CoreAudio.
> On Mar 22, 2022, at 4:33 PM, pd-list-requ...@lists.iem.at wrote: > > Message: 4 > Date: Tue, 22 Mar 2022 16:33:24 +0100 > From: Christof Ressi <i...@christofressi.com <mailto:i...@christofressi.com>> > To: pd-list@lists.iem.at <mailto:pd-list@lists.iem.at> > Subject: Re: [PD] Pd 0.52-1 - frozen dsp and gui in ubuntu 20.04 > Message-ID: <9abb25f0-6838-daf3-031f-8e1cf801b...@christofressi.com > <mailto:9abb25f0-6838-daf3-031f-8e1cf801b...@christofressi.com>> > Content-Type: text/plain; charset=UTF-8; format=flowed > >> Of course, now the displayed settings doesn't always reflect the setting >> used internally. > We could post a little notice that the delay setting has been capped. > Probably also for the ASIO backend. But that's just cosmetics. > > @umlaeute: should I push the quick fix below to develop? > > Christof -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
