<div dir="ltr">Non-interleaved meaning data is sent (L,L,L then R,R,R per block) rather than the usual I2S/TDM method of interleaving channels per sample? <div><br></div><div>The ALSA folks have some mmap example code here that looks like a pretty generic interface:</div>
<div><br></div><div><a href="http://www.alsa-project.org/alsa-doc/alsa-lib/_2test_2pcm_8c-example.html">http://www.alsa-project.org/alsa-doc/alsa-lib/_2test_2pcm_8c-example.html</a><br></div><div><br></div><div>I will build that and see if the SoC hardware likes the mmap calls.</div>
<div><br></div><div><br></div><div>Thanks!</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 13, 2014 at 8:46 PM, Miller Puckette <span dir="ltr"><<a href="mailto:msp@ucsd.edu" target="_blank">msp@ucsd.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Drat.<br>
<br>
The mmap code only works for non-interleaved memory map interfaces. The<br>
only device I know of that works with the is the RME Hammerfall series.<br>
<br>
I don't know if alsa supports any sort of mmap-ing for your hardware, but<br>
if so (and I guess it would be interleaved in that case) it might be worth<br>
hacking the mmap code to try that. It sounds less likely to hang than the<br>
read/write interface would be.<br>
<br>
cheers<br>
Miller<br>
<div><div class="h5"><br>
On Sun, Apr 13, 2014 at 04:42:04PM -0400, Chris Clepper wrote:<br>
> I could not get PortAudio to work on ARM at all and Jack has issues with<br>
> duplex low latency.<br>
><br>
> What's the deal with the ALSA mmap code? Doesn't that use callbacks?<br>
><br>
><br>
> On Sun, Apr 13, 2014 at 2:55 PM, Miller Puckette <<a href="mailto:msp@ucsd.edu">msp@ucsd.edu</a>> wrote:<br>
><br>
> > You might have already tried this, but it might work better to use<br>
> > portaudio to get to ALSA - it can connect with ALSA using callbacks<br>
> > which the built-in ASA code doesn't. I don't know what difference this<br>
> > will make but perhaps it will help.<br>
> ><br>
> > (try compiling with and without FAKEBLOCKING and THREADSIGNAL defined in<br>
> > s_audio_pa.c).<br>
> ><br>
> > cheers<br>
> > Miller<br>
> ><br>
> > On Sat, Apr 12, 2014 at 07:26:56PM -0700, Jonathan Wilkes wrote:<br>
> > > There isn't a way to poll the DSP state in Pd Vanilla.<br>
> > ><br>
> > > -Jonathan<br>
> > ><br>
> > > On Saturday, April 12, 2014 8:47 PM, Chris Clepper <<a href="mailto:cgclepper@gmail.com">cgclepper@gmail.com</a>><br>
> > wrote:<br>
> > ><br>
> > > [pdinfo] is not part of vanilla. I can't (nor want to) use extended for<br>
> > this project.<br>
> > ><br>
> > > On Saturday, April 12, 2014, Jonathan Wilkes <<a href="mailto:jancsika@yahoo.com">jancsika@yahoo.com</a>> wrote:<br>
> > ><br>
> > > On 04/12/2014 04:27 PM, Chris Clepper wrote:<br>
> > > ><br>
> > > >Hi list<br>
> > > >><br>
> > > >><br>
> > > >>I'm wondering if there are any recommended ways to ensure DSP keeps<br>
> > running for long periods like permanent installations. I get 'audio I/O<br>
> > stuck' popping up every few days, which is not bad, but ideally audio<br>
> > should stay running indefinitely.<br>
> > > >><br>
> > > >><br>
> > > >>I can send a [metro 1000] to [;pd DSP 1( to keep audio going, but is<br>
> > there any long term issue with doing that? Will it reliably restart audio<br>
> > after Pd closes it?<br>
> > > >><br>
> > > >><br>
> > > >>Also, the internal message [;pd audiostate( only returns data to the<br>
> > console. Perhaps there is a way to poll Pd for the internal DSP state and<br>
> > restart it if it dies?<br>
> > > >In Pd-l2ork:<br>
> > > >[dsp-status(<br>
> > > >|<br>
> > > >[pdinfo]<br>
> > > ><br>
> > > >-Jonathan<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > >><br>
> > > >>Thanks!<br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >><br>
</div></div>> > > >>_______________________________________________ Pd-list@iem.atmailing list<br>
<div class="HOEnZb"><div class="h5">> > > UNSUBSCRIBE and account-management -><br>
> > <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
> > > ><br>
> ><br>
> > > _______________________________________________<br>
> > > <a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
> > > UNSUBSCRIBE and account-management -><br>
> > <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
> ><br>
> ><br>
<br>
> _______________________________________________<br>
> <a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
> UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
<br>
</div></div></blockquote></div><br></div>