Re: [music-dsp] Android related audio group / mailing list?

2016-06-05 Thread Phil Burk 
You may be seeing variations in CPU clock speed. That can lead to some
puzzling benchmark results. I gave more detail in my answer on the Android
list.

By the way, one way to prevent overly aggressive optimization is to
generate a check some of the results of your benchmark and then print that
number. This will prevent a smart compiler from optimizing away all the
work of your benchmark
___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp

Re: [music-dsp] Android related audio group / mailing list?

2016-06-05 Thread Laurent de Soras 

Nuno Santos wrote:


I’m struggling with performance questions on Android.
https://groups.google.com/forum/#!topic/andraudio/zuXnnmZyePk


Your results tell that your program computes 10^9 operations
in a few dozen microseconds. There is definitely something
wrong here because even the most advanced ARM processors are
not known to be multi-teraflops CPUs.

Actually the compiler might think it can keep only one loop,
or even none, given that the result of each loop will always
be the same, and this result isn’t even used somewhere else
in the program. You should introduce slight dependencies in
your test in order to defeat this kind of optimisation.

The difference between the compiler settings you tried are
most likely caused by variations in initialisation sequences,
scheduling glitches or timer inaccuracies.

___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp

Re: [music-dsp] Android related audio group / mailing list?

2016-06-05 Thread Nuno Santos 
Hi Phil,

I’m struggling with performance questions on Android.

I have posted this question on the Android google group:

https://groups.google.com/forum/#!topic/andraudio/zuXnnmZyePk 


If you could give a look and tell me your thoughts about it, that would be 
great.

Best regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 29 May 2016, at 21:22, Phil Burk  wrote:
> 
> On Sat, May 28, 2016 at 4:04 AM, grh > wrote:
> Does anyone have contacts to google audio developers? Would be great if
> they could join such a discussion group as well!
> 
> I work for Google on Android Audio. My focus is MIDI, AudioTrack, latency and 
> performance. Also Android TV support.
> 
> I'll try to hang out on andraudio group and post when I can. 
> 
> Phil Burk
> 
> 
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp

___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp

Re: [music-dsp] Android related audio group / mailing list?

2016-05-28 Thread grh 
Hallo again!

Thanks for all the suggestions and for already starting the discussion -
I would have many questions as well ;)

Just as a quick summary, the two main suggestions were the JUCE forum:
https://forum.juce.com/c/android
And the andraudio group:
https://groups.google.com/forum/#!forum/andraudio

It would be great to focus the discussion on one channel:
IMHO the Juce forum is quite JUCE specific - maybe let's continue the
discussion on the andraudio group? There are already some new posts
there ...

Does anyone have contacts to google audio developers? Would be great if
they could join such a discussion group as well!

Thanks,
LG
Georg


-- 
auphonic - audio post production software and web service
http://auphonic.com



signature.asc
Description: OpenPGP digital signature
___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread Patrick Vlaskovits 
Hi Nuno,

Thanks for this opportunity to allow me to help you understand audio
latency on Android better.

Contributions to total round-trip audio latency on Android are best thought
as stemming from two parts.

A) Android service space (AudioFlinger etc)  ← developers and middleware
cannot affect latency here.

B) Android user space (App, DSP components, OpenSL ES) ← developers and
middleware can do quite lot to lower latency here.

Yes, the Superpowered Audio SDK (or any other API) can't improve OpenSL ES
audio latency itself when it comes to talking to the operating system's
audio stack, OpenSL ES is the only legal way to do that (right now). FWIW
Glenn Kasten mentioned at Google IO that the Pro Audio team is considering
other audio APIs.

0) HOWEVER, in Android user space, the Superpowered Audio SDK radically
improves latency down to 0 (zero/nada/zilch) as compared to components
offered by OpenSL ES, such as players and effects.

1) It is also worth mentioning Superpowered does away with Android/Open SL
ES’s fragmentation issues. OpenSL ES feature availability varies between
the different devices, while every Superpowered feature is available on
all. (We also offer considerably more features than OpenSL ES offers.)

2) Let’s not forget higher performance and higher battery life.
Superpowered outperforms every other audio API, including the extremely
high quality and industry benchmark, Core Audio by Apple.

3) Cross-platform code. Superpowered code is copy-paste between iOS, tvOS,
OSX and Android.

Back to Android service space latency, we’re putting the finishing touches
on a new media server for Android. A new media server that performs
reliable, glitch-free sub-10ms round trip audio latency. You’ll hear more
about that later.

Having spent time 'in the trenches' of Android audio, we want to take care
to note that we respect all of pioneering work that the Google Pro Audio
team has had to do, in making Android better (A thankless and brutal task).

And that we share the goal of making Android the best possible audio
platform it can be.

Any more comments, Nuno?

At your disposal,

Patrick
CEO, Superpowered Inc.

On Wed, May 25, 2016 at 11:00 AM, Nuno Santos 
wrote:

> Patrick,
>
> Now that I had the chance of using Superpowered all I can say is that it
> doesn’t make miracles. It will not provide lower latency than OpenSL
> already gives. Android latency problem is much OS and device dependent.
>
> Looking forward to understand what is new and if it will bring any special
> improvements to our products.
>
> Regards,
>
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt
> +351 91 621 69 62
>
> On 25 May 2016, at 16:26, Patrick Vlaskovits  wrote:
>
> Speaking of Android, we just released a fully configuarable and performant
> USB Audio and MIDI library for Android. It’s the Android equivalent of iOS
> Core Audio and Core MIDI for USB devices.
>
> http://superpowered.com/android-usb-audio-android-midi
>
> The Superpowered USB Audio and MIDI SDK provides stable, professional, low
> latency, low jitter, multi-channel audio and MIDI functionality for more
> than 1 billion active Android devices, letting Android users fully
> experience and express the sonic power of that Android powered
> super-computer in their pocket unmuted.
>
> -Patrick
> CEO, Superpowered Inc.
>
>
>
>
> On Wed, May 25, 2016 at 8:15 AM, Nuno Santos 
> wrote:
>
>> I have been testing DRC in 2 different Android devices: Nexus 9
>> (48000/128 buffer size) phone, Bq Aquaris M5 phone (48000/912) buffer size
>>
>> Nexus 9 is a beast. I was able to run DRC with full polyphony (8 voices)
>> without any kind of glitch. The fake touches hack was essential to make
>> this happen. Without the fake touches hack I would hear glitches.
>> Bq Aquarius M5 has a very similar processor to Nexus 6P and I couldn’t
>> have more than 2 voices running without having some glitches.
>>
>> All DSP code is C++. Reverb, Delay and Chorus represent half of the
>> processing effort the rest is for active voices.
>> From my experiences I couldn’t see any kind of effect in performance by
>> compiling the code with NEON enabled. For example, on my Bq phone for a 912
>> buffer size at 48000 my processing code would take the following time with
>> the following flags enabled:
>>
>> -Os - ~5ms
>> -O3 - ~5ms
>> -Ofast - ~5ms
>> -Ofast -mfpu=neon - ~5ms
>>
>> No significant changes in performance with different flags. What kind of
>> flags are you guys using for your Android apps?
>>
>> I don’t need to worry with this on iOS though. It simply works!
>>
>> Regards,
>>
>> Nuno Santos
>> Founder / CEO / CTO
>> www.imaginando.pt
>> +351 91 621 69 62
>>
>> On 25 May 2016, at 12:24, Jean-Baptiste Thiebaut 
>> wrote:
>>
>> At JUCE / ROLI we've been working with Google for over a year to optimize
>> audio latency, throttle, etc for cross platform apps. Our app is featured
>> also

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread Phil Burk 
Hello Nunos,
I just joined https://groups.google.com/forum/#!forum/andraudio
I think that is a good place for discussion.
If you repost your questions there then I will try to answer them.
Phil Burk


On Wed, May 25, 2016 at 6:15 AM, Nuno Santos 
wrote:

> I have been testing DRC in 2 different Android devices: Nexus 9 (48000/128
> buffer size) phone, Bq Aquaris M5 phone (48000/912) buffer size
>
> Nexus 9 is a beast. I was able to run DRC with full polyphony (8 voices)
> without any kind of glitch. The fake touches hack was essential to make
> this happen. Without the fake touches hack I would hear glitches.
> Bq Aquarius M5 has a very similar processor to Nexus 6P and I couldn’t
> have more than 2 voices running without having some glitches.
>
> All DSP code is C++. Reverb, Delay and Chorus represent half of the
> processing effort the rest is for active voices.
> From my experiences I couldn’t see any kind of effect in performance by
> compiling the code with NEON enabled. For example, on my Bq phone for a 912
> buffer size at 48000 my processing code would take the following time with
> the following flags enabled:
>
> -Os - ~5ms
> -O3 - ~5ms
> -Ofast - ~5ms
> -Ofast -mfpu=neon - ~5ms
>
> No significant changes in performance with different flags. What kind of
> flags are you guys using for your Android apps?
>
> I don’t need to worry with this on iOS though. It simply works!
>
> Regards,
>
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt
> +351 91 621 69 62
>
> On 25 May 2016, at 12:24, Jean-Baptiste Thiebaut 
> wrote:
>
> At JUCE / ROLI we've been working with Google for over a year to optimize
> audio latency, throttle, etc for cross platform apps. Our app is featured
> also in the Youtube video from Google IO, and it runs on some devices with
> performances comparable to iOS.
>
> Whether you are using JUCE or not, you're welcome to post on our forum (
> forum.juce.com).
>
> Sent from my mobile
>
> On 25 May 2016, at 11:57, grh  wrote:
>
> Hallo!
>
> Thanks Nuno, it was a great demo ;)
>
> LG
> Georg
>
> On 2016-05-25 12:46, Nuno Santos wrote:
> Hi George,
>
> I would be interested in such a community as well. Specially regarding
> audio performance. We have recently released DRC (one of the apps that
> has been featured on Google I/O Android High Performance Audio) and we
> are mostly interested in squeezing performance out of it. It is
> incredible the performance differences between iOS and Android. The DSP
> code is shared among both and I still have glitch problems in Android
> powerful devices.
>
> One option could be creating a slack channel.
>
> Regards,
>
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt 
> +351 91 621 69 62
>
> On 25 May 2016, at 11:36, grh >>
> wrote:
>
> Hallo music-dsp list!
>
> Sorry for being off topic, but does someone know an active discussion
> group / mailing list about android audio?
> (There is quite a lot of progress lately, see for example [1])
> 5 years ago a list was announced here [2], which does not seem to be
> active anymore ...
>
> We just created a simple android audio editor [3] and would be very much
> interested into a discussion of common infrastructure like audio
> plugins/effects (like SAPA from Samsung) or copy/paste between audio apps.
> I think that would be important for the audio ecosystem on Android.
>
> Thanks for any hints,
> LG
> Georg
>
> [1]: https://www.youtube.com/watch?v=F2ZDp-eNrh4
> [2]:
>
> http://music-dsp.music.columbia.narkive.com/zbYgicxy/new-android-audio-developers-mailing-list
> [3]:
> https://play.google.com/store/apps/details?id=com.auphonic.auphonicrecorder
>
> --
> auphonic - audio post production software and web service
> http://auphonic.com
>
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp
>
>
>
>
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp
>
>
>
> --
> auphonic - audio post production software and web service
> http://auphonic.com
>
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp
>
>
> --
>
>
> *ROLI's **award-winning*
> <
> http://www.telegraph.co.uk/luxury/design/31520/the-seaboard-grand-piano-wins-designs-of-the-year-2014-award.html>*
> Seaboard
> GRAND, celebrated as the "**piano of the future*
> <
> http://edition.cnn.com/2013/09/27/tech/innovation/hans-zimmer-seaboard-future-piano/>*",
>
> is now joined by the **Seaboard RISE*
> *, "**every bit as slimline
> and attractive as its bigger brother*
>

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread Nuno Santos 
Patrick,

Now that I had the chance of using Superpowered all I can say is that it 
doesn’t make miracles. It will not provide lower latency than OpenSL already 
gives. Android latency problem is much OS and device dependent.

Looking forward to understand what is new and if it will bring any special 
improvements to our products.

Regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 25 May 2016, at 16:26, Patrick Vlaskovits  wrote:
> 
> Speaking of Android, we just released a fully configuarable and performant 
> USB Audio and MIDI library for Android. It’s the Android equivalent of iOS 
> Core Audio and Core MIDI for USB devices.
> 
> http://superpowered.com/android-usb-audio-android-midi 
> 
> 
> The Superpowered USB Audio and MIDI SDK provides stable, professional, low 
> latency, low jitter, multi-channel audio and MIDI functionality for more than 
> 1 billion active Android devices, letting Android users fully experience and 
> express the sonic power of that Android powered super-computer in their 
> pocket unmuted.
> 
> -Patrick
> CEO, Superpowered Inc. 
> 
> 
> 
> 
> On Wed, May 25, 2016 at 8:15 AM, Nuno Santos  > wrote:
> I have been testing DRC in 2 different Android devices: Nexus 9 (48000/128 
> buffer size) phone, Bq Aquaris M5 phone (48000/912) buffer size
> 
> Nexus 9 is a beast. I was able to run DRC with full polyphony (8 voices) 
> without any kind of glitch. The fake touches hack was essential to make this 
> happen. Without the fake touches hack I would hear glitches.
> Bq Aquarius M5 has a very similar processor to Nexus 6P and I couldn’t have 
> more than 2 voices running without having some glitches. 
> 
> All DSP code is C++. Reverb, Delay and Chorus represent half of the 
> processing effort the rest is for active voices.
>   
> From my experiences I couldn’t see any kind of effect in performance by 
> compiling the code with NEON enabled. For example, on my Bq phone for a 912 
> buffer size at 48000 my processing code would take the following time with 
> the following flags enabled:
> 
> -Os - ~5ms 
> -O3 - ~5ms
> -Ofast - ~5ms
> -Ofast -mfpu=neon - ~5ms
> 
> No significant changes in performance with different flags. What kind of 
> flags are you guys using for your Android apps?
> 
> I don’t need to worry with this on iOS though. It simply works! 
> 
> Regards,
> 
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt 
> +351 91 621 69 62 
> 
>> On 25 May 2016, at 12:24, Jean-Baptiste Thiebaut > > wrote:
>> 
>> At JUCE / ROLI we've been working with Google for over a year to optimize 
>> audio latency, throttle, etc for cross platform apps. Our app is featured 
>> also in the Youtube video from Google IO, and it runs on some devices with 
>> performances comparable to iOS.  
>> 
>> Whether you are using JUCE or not, you're welcome to post on our forum 
>> (forum.juce.com ). 
>> 
>> Sent from my mobile
>> 
>>> On 25 May 2016, at 11:57, grh > wrote:
>>> 
>>> Hallo!
>>> 
>>> Thanks Nuno, it was a great demo ;)
>>> 
>>> LG
>>> Georg
>>> 
 On 2016-05-25 12:46, Nuno Santos wrote:
 Hi George,
 
 I would be interested in such a community as well. Specially regarding
 audio performance. We have recently released DRC (one of the apps that
 has been featured on Google I/O Android High Performance Audio) and we
 are mostly interested in squeezing performance out of it. It is
 incredible the performance differences between iOS and Android. The DSP
 code is shared among both and I still have glitch problems in Android
 powerful devices.
 
 One option could be creating a slack channel. 
 
 Regards,
 
 Nuno Santos
 Founder / CEO / CTO
 www.imaginando.pt  >
 +351 91 621 69 62 
 
> On 25 May 2016, at 11:36, grh  
> >> wrote:
> 
> Hallo music-dsp list!
> 
> Sorry for being off topic, but does someone know an active discussion
> group / mailing list about android audio?
> (There is quite a lot of progress lately, see for example [1])
> 5 years ago a list was announced here [2], which does not seem to be
> active anymore ...
> 
> We just created a simple android audio editor [3] and would be very much
> interested into a discussion of common infrastructure like audio
> plugins/effects (like SAPA from Samsung) or copy/paste between audio apps.
> I think that would be important for the audio ecosystem on Android.
> 
>

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread Patrick Vlaskovits 
Speaking of Android, we just released a fully configuarable and performant
USB Audio and MIDI library for Android. It’s the Android equivalent of iOS
Core Audio and Core MIDI for USB devices.

http://superpowered.com/android-usb-audio-android-midi

The Superpowered USB Audio and MIDI SDK provides stable, professional, low
latency, low jitter, multi-channel audio and MIDI functionality for more
than 1 billion active Android devices, letting Android users fully
experience and express the sonic power of that Android powered
super-computer in their pocket unmuted.

-Patrick
CEO, Superpowered Inc.




On Wed, May 25, 2016 at 8:15 AM, Nuno Santos 
wrote:

> I have been testing DRC in 2 different Android devices: Nexus 9 (48000/128
> buffer size) phone, Bq Aquaris M5 phone (48000/912) buffer size
>
> Nexus 9 is a beast. I was able to run DRC with full polyphony (8 voices)
> without any kind of glitch. The fake touches hack was essential to make
> this happen. Without the fake touches hack I would hear glitches.
> Bq Aquarius M5 has a very similar processor to Nexus 6P and I couldn’t
> have more than 2 voices running without having some glitches.
>
> All DSP code is C++. Reverb, Delay and Chorus represent half of the
> processing effort the rest is for active voices.
> From my experiences I couldn’t see any kind of effect in performance by
> compiling the code with NEON enabled. For example, on my Bq phone for a 912
> buffer size at 48000 my processing code would take the following time with
> the following flags enabled:
>
> -Os - ~5ms
> -O3 - ~5ms
> -Ofast - ~5ms
> -Ofast -mfpu=neon - ~5ms
>
> No significant changes in performance with different flags. What kind of
> flags are you guys using for your Android apps?
>
> I don’t need to worry with this on iOS though. It simply works!
>
> Regards,
>
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt
> +351 91 621 69 62
>
> On 25 May 2016, at 12:24, Jean-Baptiste Thiebaut 
> wrote:
>
> At JUCE / ROLI we've been working with Google for over a year to optimize
> audio latency, throttle, etc for cross platform apps. Our app is featured
> also in the Youtube video from Google IO, and it runs on some devices with
> performances comparable to iOS.
>
> Whether you are using JUCE or not, you're welcome to post on our forum (
> forum.juce.com).
>
> Sent from my mobile
>
> On 25 May 2016, at 11:57, grh  wrote:
>
> Hallo!
>
> Thanks Nuno, it was a great demo ;)
>
> LG
> Georg
>
> On 2016-05-25 12:46, Nuno Santos wrote:
> Hi George,
>
> I would be interested in such a community as well. Specially regarding
> audio performance. We have recently released DRC (one of the apps that
> has been featured on Google I/O Android High Performance Audio) and we
> are mostly interested in squeezing performance out of it. It is
> incredible the performance differences between iOS and Android. The DSP
> code is shared among both and I still have glitch problems in Android
> powerful devices.
>
> One option could be creating a slack channel.
>
> Regards,
>
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt 
> +351 91 621 69 62
>
> On 25 May 2016, at 11:36, grh >>
> wrote:
>
> Hallo music-dsp list!
>
> Sorry for being off topic, but does someone know an active discussion
> group / mailing list about android audio?
> (There is quite a lot of progress lately, see for example [1])
> 5 years ago a list was announced here [2], which does not seem to be
> active anymore ...
>
> We just created a simple android audio editor [3] and would be very much
> interested into a discussion of common infrastructure like audio
> plugins/effects (like SAPA from Samsung) or copy/paste between audio apps.
> I think that would be important for the audio ecosystem on Android.
>
> Thanks for any hints,
> LG
> Georg
>
> [1]: https://www.youtube.com/watch?v=F2ZDp-eNrh4
> [2]:
>
> http://music-dsp.music.columbia.narkive.com/zbYgicxy/new-android-audio-developers-mailing-list
> [3]:
> https://play.google.com/store/apps/details?id=com.auphonic.auphonicrecorder
>
> --
> auphonic - audio post production software and web service
> http://auphonic.com
>
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp
>
>
>
>
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp
>
>
>
> --
> auphonic - audio post production software and web service
> http://auphonic.com
>
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp
>
>
> --
>
>
> *ROLI's **award-winning*
> <
>

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread Giulio Moro 
Also, only way to actually know if your compiler generates Neon is to ... read 
the assembly!
Some common DSP tasks are implemented in the Ne10 library 
http://projectne10.github.io/Ne10/doc/ which compiles to Neon on systems that 
support it.
I have seen that nova_simd is good at generating neon code, but I never used it 
stand-alone (only as part of Supercollider)
Best,Giulio

 
  From: Nuno Santos <nunosan...@imaginando.pt>
 To: music-dsp@music.columbia.edu 
 Sent: Wednesday, 25 May 2016, 14:15
 Subject: Re: [music-dsp] Android related audio group / mailing list?
   
I have been testing DRC in 2 different Android devices: Nexus 9 (48000/128 
buffer size) phone, Bq Aquaris M5 phone (48000/912) buffer size
Nexus 9 is a beast. I was able to run DRC with full polyphony (8 voices) 
without any kind of glitch. The fake touches hack was essential to make this 
happen. Without the fake touches hack I would hear glitches.Bq Aquarius M5 has 
a very similar processor to Nexus 6P and I couldn’t have more than 2 voices 
running without having some glitches. 
All DSP code is C++. Reverb, Delay and Chorus represent half of the processing 
effort the rest is for active voices. From my experiences I couldn’t see any 
kind of effect in performance by compiling the code with NEON enabled. For 
example, on my Bq phone for a 912 buffer size at 48000 my processing code would 
take the following time with the following flags enabled:
-Os - ~5ms -O3 - ~5ms-Ofast - ~5ms-Ofast -mfpu=neon - ~5ms
No significant changes in performance with different flags. What kind of flags 
are you guys using for your Android apps?
I don’t need to worry with this on iOS though. It simply works! 
Regards,
Nuno Santos
Founder / CEO / CTO
www.imaginando.pt+351 91 621 69 62

On 25 May 2016, at 12:24, Jean-Baptiste Thiebaut <jean-bapti...@roli.com> wrote:
At JUCE / ROLI we've been working with Google for over a year to optimize audio 
latency, throttle, etc for cross platform apps. Our app is featured also in the 
Youtube video from Google IO, and it runs on some devices with performances 
comparable to iOS.  

Whether you are using JUCE or not, you're welcome to post on our forum 
(forum.juce.com). 

Sent from my mobile


On 25 May 2016, at 11:57, grh <g...@mur.at> wrote:

Hallo!

Thanks Nuno, it was a great demo ;)

LG
Georg


On 2016-05-25 12:46, Nuno Santos wrote:
Hi George,

I would be interested in such a community as well. Specially regarding
audio performance. We have recently released DRC (one of the apps that
has been featured on Google I/O Android High Performance Audio) and we
are mostly interested in squeezing performance out of it. It is
incredible the performance differences between iOS and Android. The DSP
code is shared among both and I still have glitch problems in Android
powerful devices.

One option could be creating a slack channel. 

Regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt <http://www.imaginando.pt>
+351 91 621 69 62


On 25 May 2016, at 11:36, grh <g...@mur.at <mailto:g...@mur.at>> wrote:

Hallo music-dsp list!

Sorry for being off topic, but does someone know an active discussion
group / mailing list about android audio?
(There is quite a lot of progress lately, see for example [1])
5 years ago a list was announced here [2], which does not seem to be
active anymore ...

We just created a simple android audio editor [3] and would be very much
interested into a discussion of common infrastructure like audio
plugins/effects (like SAPA from Samsung) or copy/paste between audio apps.
I think that would be important for the audio ecosystem on Android.

Thanks for any hints,
LG
Georg

[1]: https://www.youtube.com/watch?v=F2ZDp-eNrh4
[2]:
http://music-dsp.music.columbia.narkive.com/zbYgicxy/new-android-audio-developers-mailing-list
[3]:
https://play.google.com/store/apps/details?id=com.auphonic.auphonicrecorder

-- 
auphonic - audio post production software and web service
http://auphonic.com

___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp




___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp



-- 
auphonic - audio post production software and web service
http://auphonic.com

___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp


-- 


*ROLI's **award-winning* 
<http://www.telegraph.co.uk/luxury/design/31520/the-seaboard-grand-piano-wins-designs-of-the-year-2014-award.html>*
 Seaboard 
GRAND, celebrated as the "**piano of the future* 
<http://edition.cnn.com/2013/09/27/tech/innovation/hans-zimmer-seaboard-future-piano/>*",
 
is now joined by the **Seaboard RISE* 
<https://www.youtube.com/watch?v=fGr7VbDi

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread Nuno Santos 
I have been testing DRC in 2 different Android devices: Nexus 9 (48000/128 
buffer size) phone, Bq Aquaris M5 phone (48000/912) buffer size

Nexus 9 is a beast. I was able to run DRC with full polyphony (8 voices) 
without any kind of glitch. The fake touches hack was essential to make this 
happen. Without the fake touches hack I would hear glitches.
Bq Aquarius M5 has a very similar processor to Nexus 6P and I couldn’t have 
more than 2 voices running without having some glitches. 

All DSP code is C++. Reverb, Delay and Chorus represent half of the processing 
effort the rest is for active voices.

From my experiences I couldn’t see any kind of effect in performance by 
compiling the code with NEON enabled. For example, on my Bq phone for a 912 
buffer size at 48000 my processing code would take the following time with the 
following flags enabled:

-Os - ~5ms 
-O3 - ~5ms
-Ofast - ~5ms
-Ofast -mfpu=neon - ~5ms

No significant changes in performance with different flags. What kind of flags 
are you guys using for your Android apps?

I don’t need to worry with this on iOS though. It simply works! 

Regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 25 May 2016, at 12:24, Jean-Baptiste Thiebaut  
> wrote:
> 
> At JUCE / ROLI we've been working with Google for over a year to optimize 
> audio latency, throttle, etc for cross platform apps. Our app is featured 
> also in the Youtube video from Google IO, and it runs on some devices with 
> performances comparable to iOS.  
> 
> Whether you are using JUCE or not, you're welcome to post on our forum 
> (forum.juce.com). 
> 
> Sent from my mobile
> 
>> On 25 May 2016, at 11:57, grh  wrote:
>> 
>> Hallo!
>> 
>> Thanks Nuno, it was a great demo ;)
>> 
>> LG
>> Georg
>> 
>>> On 2016-05-25 12:46, Nuno Santos wrote:
>>> Hi George,
>>> 
>>> I would be interested in such a community as well. Specially regarding
>>> audio performance. We have recently released DRC (one of the apps that
>>> has been featured on Google I/O Android High Performance Audio) and we
>>> are mostly interested in squeezing performance out of it. It is
>>> incredible the performance differences between iOS and Android. The DSP
>>> code is shared among both and I still have glitch problems in Android
>>> powerful devices.
>>> 
>>> One option could be creating a slack channel. 
>>> 
>>> Regards,
>>> 
>>> Nuno Santos
>>> Founder / CEO / CTO
>>> www.imaginando.pt 
>>> +351 91 621 69 62
>>> 
 On 25 May 2016, at 11:36, grh > wrote:
 
 Hallo music-dsp list!
 
 Sorry for being off topic, but does someone know an active discussion
 group / mailing list about android audio?
 (There is quite a lot of progress lately, see for example [1])
 5 years ago a list was announced here [2], which does not seem to be
 active anymore ...
 
 We just created a simple android audio editor [3] and would be very much
 interested into a discussion of common infrastructure like audio
 plugins/effects (like SAPA from Samsung) or copy/paste between audio apps.
 I think that would be important for the audio ecosystem on Android.
 
 Thanks for any hints,
 LG
 Georg
 
 [1]: https://www.youtube.com/watch?v=F2ZDp-eNrh4
 [2]:
 http://music-dsp.music.columbia.narkive.com/zbYgicxy/new-android-audio-developers-mailing-list
 [3]:
 https://play.google.com/store/apps/details?id=com.auphonic.auphonicrecorder
 
 -- 
 auphonic - audio post production software and web service
 http://auphonic.com
 
 ___
 dupswapdrop: music-dsp mailing list
 music-dsp@music.columbia.edu
 https://lists.columbia.edu/mailman/listinfo/music-dsp
>>> 
>>> 
>>> 
>>> ___
>>> dupswapdrop: music-dsp mailing list
>>> music-dsp@music.columbia.edu
>>> https://lists.columbia.edu/mailman/listinfo/music-dsp
>> 
>> 
>> -- 
>> auphonic - audio post production software and web service
>> http://auphonic.com
>> 
>> ___
>> dupswapdrop: music-dsp mailing list
>> music-dsp@music.columbia.edu
>> https://lists.columbia.edu/mailman/listinfo/music-dsp
> 
> -- 
> 
> 
> *ROLI's **award-winning* 
> *
>  Seaboard 
> GRAND, celebrated as the "**piano of the future* 
> *",
>  
> is now joined by the **Seaboard RISE* 
> *, "**every bit as slimline 
> and attractive as its bigger brother* 
> *". The press is hailing the 
> Seaboard RISE as "**innovative* 
>

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread Eder Souza 
Hi,

I do not see drives in the andraudio group since he migrated to [1]

Some years ago I tried see how some of my codes works in android, I wrote
effects to work in real-time (automatic pitch correction, time stretch,
pitch shifters in time domain and frequency domain) and I get a lot of
glitches.

I know that even today is something painful to try, Google I/O 2016 gave me
hope to try something again :-)

PS: Nice app Nuno

[1] https://groups.google.com/forum/#!forum/andraudio

On Wed, May 25, 2016 at 7:57 AM, grh  wrote:

> Hallo!
>
> Thanks Nuno, it was a great demo ;)
>
> LG
> Georg
>
> On 2016-05-25 12:46, Nuno Santos wrote:
> > Hi George,
> >
> > I would be interested in such a community as well. Specially regarding
> > audio performance. We have recently released DRC (one of the apps that
> > has been featured on Google I/O Android High Performance Audio) and we
> > are mostly interested in squeezing performance out of it. It is
> > incredible the performance differences between iOS and Android. The DSP
> > code is shared among both and I still have glitch problems in Android
> > powerful devices.
> >
> > One option could be creating a slack channel.
> >
> > Regards,
> >
> > Nuno Santos
> > Founder / CEO / CTO
> > www.imaginando.pt 
> > +351 91 621 69 62
> >
> >> On 25 May 2016, at 11:36, grh > wrote:
> >>
> >> Hallo music-dsp list!
> >>
> >> Sorry for being off topic, but does someone know an active discussion
> >> group / mailing list about android audio?
> >> (There is quite a lot of progress lately, see for example [1])
> >> 5 years ago a list was announced here [2], which does not seem to be
> >> active anymore ...
> >>
> >> We just created a simple android audio editor [3] and would be very much
> >> interested into a discussion of common infrastructure like audio
> >> plugins/effects (like SAPA from Samsung) or copy/paste between audio
> apps.
> >> I think that would be important for the audio ecosystem on Android.
> >>
> >> Thanks for any hints,
> >> LG
> >> Georg
> >>
> >> [1]: https://www.youtube.com/watch?v=F2ZDp-eNrh4
> >> [2]:
> >>
> http://music-dsp.music.columbia.narkive.com/zbYgicxy/new-android-audio-developers-mailing-list
> >> [3]:
> >>
> https://play.google.com/store/apps/details?id=com.auphonic.auphonicrecorder
> >>
> >> --
> >> auphonic - audio post production software and web service
> >> http://auphonic.com
> >>
> >> ___
> >> dupswapdrop: music-dsp mailing list
> >> music-dsp@music.columbia.edu
> >> https://lists.columbia.edu/mailman/listinfo/music-dsp
> >
> >
> >
> > ___
> > dupswapdrop: music-dsp mailing list
> > music-dsp@music.columbia.edu
> > https://lists.columbia.edu/mailman/listinfo/music-dsp
> >
>
>
> --
> auphonic - audio post production software and web service
> http://auphonic.com
>
>
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp
>
___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread Jean-Baptiste Thiebaut 
At JUCE / ROLI we've been working with Google for over a year to optimize audio 
latency, throttle, etc for cross platform apps. Our app is featured also in the 
Youtube video from Google IO, and it runs on some devices with performances 
comparable to iOS.  

Whether you are using JUCE or not, you're welcome to post on our forum 
(forum.juce.com). 

Sent from my mobile

> On 25 May 2016, at 11:57, grh  wrote:
> 
> Hallo!
> 
> Thanks Nuno, it was a great demo ;)
> 
> LG
> Georg
> 
>> On 2016-05-25 12:46, Nuno Santos wrote:
>> Hi George,
>> 
>> I would be interested in such a community as well. Specially regarding
>> audio performance. We have recently released DRC (one of the apps that
>> has been featured on Google I/O Android High Performance Audio) and we
>> are mostly interested in squeezing performance out of it. It is
>> incredible the performance differences between iOS and Android. The DSP
>> code is shared among both and I still have glitch problems in Android
>> powerful devices.
>> 
>> One option could be creating a slack channel. 
>> 
>> Regards,
>> 
>> Nuno Santos
>> Founder / CEO / CTO
>> www.imaginando.pt 
>> +351 91 621 69 62
>> 
>>> On 25 May 2016, at 11:36, grh > wrote:
>>> 
>>> Hallo music-dsp list!
>>> 
>>> Sorry for being off topic, but does someone know an active discussion
>>> group / mailing list about android audio?
>>> (There is quite a lot of progress lately, see for example [1])
>>> 5 years ago a list was announced here [2], which does not seem to be
>>> active anymore ...
>>> 
>>> We just created a simple android audio editor [3] and would be very much
>>> interested into a discussion of common infrastructure like audio
>>> plugins/effects (like SAPA from Samsung) or copy/paste between audio apps.
>>> I think that would be important for the audio ecosystem on Android.
>>> 
>>> Thanks for any hints,
>>> LG
>>> Georg
>>> 
>>> [1]: https://www.youtube.com/watch?v=F2ZDp-eNrh4
>>> [2]:
>>> http://music-dsp.music.columbia.narkive.com/zbYgicxy/new-android-audio-developers-mailing-list
>>> [3]:
>>> https://play.google.com/store/apps/details?id=com.auphonic.auphonicrecorder
>>> 
>>> -- 
>>> auphonic - audio post production software and web service
>>> http://auphonic.com
>>> 
>>> ___
>>> dupswapdrop: music-dsp mailing list
>>> music-dsp@music.columbia.edu
>>> https://lists.columbia.edu/mailman/listinfo/music-dsp
>> 
>> 
>> 
>> ___
>> dupswapdrop: music-dsp mailing list
>> music-dsp@music.columbia.edu
>> https://lists.columbia.edu/mailman/listinfo/music-dsp
> 
> 
> -- 
> auphonic - audio post production software and web service
> http://auphonic.com
> 
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp

-- 


*ROLI's **award-winning* 
*
 Seaboard 
GRAND, celebrated as the "**piano of the future* 
*",
 
is now joined by the **Seaboard RISE* 
*, "**every bit as slimline 
and attractive as its bigger brother* 
*". The press is hailing the 
Seaboard RISE as "**innovative* 
*",
 
"**expressive* 
*",
 
"**accessible* 
*",
 
and "**a keyboard controller that does to piano keys what 3D touch does to 
the iPhone* 
*".
 
Now available for preorder at **www.roli.com* *. *


Office: +44 (0) 207 254 2155

ROLI 
2 Glebe Rd, London E8 4BD
www.roli.com 

Discover more about us on Facebook  - Twitter 
 - Youtube 


ROLI Ltd. is a registered company in England and Wales, and this e-mail and 
its attachment(s) are intended for the above named only and are 
confidential. If they have come to you in error then you must take no 
action based upon them but contact us immediately. Any disclosure, copying, 
distribution or any action taken or omitted to be taken in reliance on it 
is prohibited and may be unlawful. Although this e-mail and its attachments 
are believed to be free of any virus, it is the responsibility of the 
recipient to ensure that they are virus free. If you contact us by e-mail 
then we will store your name and address to facilitate

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread Giulio Moro 
Hello,I watched the google/android video the other day and I was very surprised 
of the basic recommendations that were given to developers:- use native 
sampling rate (don't hardcode sampling rate, request it from the device)
- use native buffering (don't hardcode it. But then maybe use double or 
quadruple buffering in the app, because your CPU is not fast enough)- compile 
for Release and enable Neon- don't log at every audio callback- don't 
lock/allocate in the audio callback- use less than 20% of the CPU time
I mean, really? Is this what was lacking so far in Android "professional" 
audio? These are the basics of real-time programming, as Ross teaches us 
http://www.rossbencina.com/code/real-time-audio-programming-101-time-waits-for-nothing
 and of general programming (compiler optimization, Release mode).
The useful bits of information I got are:- simulate screen taps every second so 
that the CPU is always kept to full clock and no energy save. >> surely a 
workaround. As the people speaking have worked on Android for the past three 
years I am sure they could have supported this from the Android API- current 
target is to achieve 10ms roundtrip>> Which means that not even the nexus 6p 
does it at the moment.- a device for measuring roundtrip latency (using a 
teensy and a custom app, 22:48) https://github.com/google/walt
I was not very impressed by the quality of the video production overall, as it 
features:
- a physician introduced as "someone that cares all about numbers"- a calibre 
(22:17)- table of latency results which does not have any sense (23:12)

Best,Giulio
 
  From: grh <g...@mur.at>
 To: music-dsp@music.columbia.edu 
 Sent: Wednesday, 25 May 2016, 11:57
 Subject: Re: [music-dsp] Android related audio group / mailing list?
   
Hallo!

Thanks Nuno, it was a great demo ;)

LG
Georg

On 2016-05-25 12:46, Nuno Santos wrote:
> Hi George,
> 
> I would be interested in such a community as well. Specially regarding
> audio performance. We have recently released DRC (one of the apps that
> has been featured on Google I/O Android High Performance Audio) and we
> are mostly interested in squeezing performance out of it. It is
> incredible the performance differences between iOS and Android. The DSP
> code is shared among both and I still have glitch problems in Android
> powerful devices.
> 
> One option could be creating a slack channel. 
> 
> Regards,
> 
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt <http://www.imaginando.pt>
> +351 91 621 69 62
> 
>> On 25 May 2016, at 11:36, grh <g...@mur.at <mailto:g...@mur.at>> wrote:
>>
>> Hallo music-dsp list!
>>
>> Sorry for being off topic, but does someone know an active discussion
>> group / mailing list about android audio?
>> (There is quite a lot of progress lately, see for example [1])
>> 5 years ago a list was announced here [2], which does not seem to be
>> active anymore ...
>>
>> We just created a simple android audio editor [3] and would be very much
>> interested into a discussion of common infrastructure like audio
>> plugins/effects (like SAPA from Samsung) or copy/paste between audio apps.
>> I think that would be important for the audio ecosystem on Android.
>>
>> Thanks for any hints,
>> LG
>> Georg
>>
>> [1]: https://www.youtube.com/watch?v=F2ZDp-eNrh4
>> [2]:
>> http://music-dsp.music.columbia.narkive.com/zbYgicxy/new-android-audio-developers-mailing-list
>> [3]:
>> https://play.google.com/store/apps/details?id=com.auphonic.auphonicrecorder
>>
>> -- 
>> auphonic - audio post production software and web service
>> http://auphonic.com
>>
>> ___
>> dupswapdrop: music-dsp mailing list
>> music-dsp@music.columbia.edu
>> https://lists.columbia.edu/mailman/listinfo/music-dsp
> 
> 
> 
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp
> 


-- 
auphonic - audio post production software and web service
http://auphonic.com

___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp

   
___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp

Re: [music-dsp] Android related audio group / mailing list?

2016-05-25 Thread grh 
Hallo!

Thanks Nuno, it was a great demo ;)

LG
Georg

On 2016-05-25 12:46, Nuno Santos wrote:
> Hi George,
> 
> I would be interested in such a community as well. Specially regarding
> audio performance. We have recently released DRC (one of the apps that
> has been featured on Google I/O Android High Performance Audio) and we
> are mostly interested in squeezing performance out of it. It is
> incredible the performance differences between iOS and Android. The DSP
> code is shared among both and I still have glitch problems in Android
> powerful devices.
> 
> One option could be creating a slack channel. 
> 
> Regards,
> 
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt 
> +351 91 621 69 62
> 
>> On 25 May 2016, at 11:36, grh > wrote:
>>
>> Hallo music-dsp list!
>>
>> Sorry for being off topic, but does someone know an active discussion
>> group / mailing list about android audio?
>> (There is quite a lot of progress lately, see for example [1])
>> 5 years ago a list was announced here [2], which does not seem to be
>> active anymore ...
>>
>> We just created a simple android audio editor [3] and would be very much
>> interested into a discussion of common infrastructure like audio
>> plugins/effects (like SAPA from Samsung) or copy/paste between audio apps.
>> I think that would be important for the audio ecosystem on Android.
>>
>> Thanks for any hints,
>> LG
>> Georg
>>
>> [1]: https://www.youtube.com/watch?v=F2ZDp-eNrh4
>> [2]:
>> http://music-dsp.music.columbia.narkive.com/zbYgicxy/new-android-audio-developers-mailing-list
>> [3]:
>> https://play.google.com/store/apps/details?id=com.auphonic.auphonicrecorder
>>
>> -- 
>> auphonic - audio post production software and web service
>> http://auphonic.com
>>
>> ___
>> dupswapdrop: music-dsp mailing list
>> music-dsp@music.columbia.edu
>> https://lists.columbia.edu/mailman/listinfo/music-dsp
> 
> 
> 
> ___
> dupswapdrop: music-dsp mailing list
> music-dsp@music.columbia.edu
> https://lists.columbia.edu/mailman/listinfo/music-dsp
> 


-- 
auphonic - audio post production software and web service
http://auphonic.com



signature.asc
Description: OpenPGP digital signature
___
dupswapdrop: music-dsp mailing list
music-dsp@music.columbia.edu
https://lists.columbia.edu/mailman/listinfo/music-dsp