Thank you all for your replies.<br><br>I m not sure if the poor latency will be much of an issue for me. The reason why i wanted to go for Android is because it seems to be more open than the rest and i thought it'd be easier for me to develop small apps that i could share with some relatives (not necessarily based on Pd). <br>
<br>Now regarding my use of Pd in Android. I don't need to do anything fancy, all i'd like to develop for now is a small 2 or 4-track recorder, to help me work on my new songs in a more flexible way than with my old cassette recorder. So how should i go about it? Can i use ScenePlayer with a patch that does just that? Or should i develop my own native app in android using libpd (which is still very obscure to me at the moment)? <br>
<br>Cheers!<br><br>Pierre<br><br><div class="gmail_quote">2011/8/30 Spencer Russell <span dir="ltr"><<a href="mailto:spencer.f.russell@gmail.com">spencer.f.russell@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Seconding the dissatisfaction with real-time audio support on Android in general.<div><br></div><div>I've only recently jumped on the android train (Samsung Droid Charge) and I've noticed that the only audio apps that are usable are of the sequencing / drum machine variety, because they don't depend so much on low-latency. Any apps where tapping on the screen is supposed to generate a sound exposes serious latency issues.</div>
<div><br></div><div>I've heard that gingerbread made some changes to the available audio API, but supposedly they didn't substantially improve things. According to the "people who know" many of the latency issues are low-level (drivers and actual hardware limitations) that have as much to do with the device manufacturers as Android itself. One of the downsides of an open platform that runs on a wide variety of devices. I haven't had a chance to survey the situation with common audio CODECS being used on these devices and whether the drivers are available open-source, and/or could be hacked for better latency.</div>
<div><br></div><div>I haven't been able to test much with libpd yet. So far any time any libpd-based app tries to access my microphone I get this crazy noise (actually sounds kind of cool, but definitely not the intended sound). I haven't tried building the latest from the repo, I didn't realize the binaries were substantially out-of-date (I didn't bother to check any timestamps).</div>
<div><br></div><div>If that doesn't fix the issue I'll be sure to get in touch with the devs and see where the issue may lie.</div><div><br></div><div><font color="#888888">-s</font><div><div></div><div class="h5">
<br><br><div class="gmail_quote">On Mon, Aug 29, 2011 at 4:54 PM, Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><br>
Hey Dan,<br>
<br>
I agree, Android's downfall is the poor audio implementation on the<br>
devices. How many have you tested? Can you post that data anywhere?<br>
It would be good to start collecting this. I think there are starting<br>
to be some Android devices with solid audio performance, so it would be<br>
good to have a source of data on this.<br>
<br>
.hc<br>
<br>
On Mon, 29 Aug 2011 16:30 -0400, "Dan Wilcox" <<a href="mailto:danomatika@gmail.com" target="_blank">danomatika@gmail.com</a>><br>
wrote:<br>
<div><div></div><div>> I have to disagree with you. iOS is a better mobile os for running<br>
> applications using libpd (aka RjDJ, Nodebeat, etc) since it has a low<br>
> latency audio api. Android can't give you anything better then 20ms or<br>
> so. If you want to build a realtime, I'm afraid you have to stick to iOS<br>
> for now ...<br>
><br>
> This is why I'm targeting iOS for the upcoming robotcowboy app ...<br>
> although I'd rather use a much freer platform.<br>
><br>
> On Aug 29, 2011, at 11:21 AM, Pierre Massat wrote:<br>
><br>
> > Hi all,<br>
> ><br>
> > I plan on buying my very first smartphone in the next few days. I want a phone running Android since it appears to be the best platform to run Pd. I m just not quite sure about the way Pd can be used with a smartphone. Can we run Pd-extended, or just use the patches, or is it just some sort of an API that can be used when developping an app? I m totally new to this, so please excuse the (possibly abyssal) silliness of my questions.<br>
> ><br>
> > Cheers!<br>
> ><br>
> > Pierre<br>
><br>
> --------<br>
> Dan Wilcox<br>
> <a href="http://danomatika.com" target="_blank">danomatika.com</a><br>
> <a href="http://robotcowboy.com" target="_blank">robotcowboy.com</a><br>
><br>
><br>
><br>
><br>
</div></div><div><div></div><div>> _______________________________________________<br>
> <a href="mailto:Pd-list@iem.at" target="_blank">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>
<a href="mailto:Pd-list@iem.at" target="_blank">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>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br>