I am not convinced this is a Csound problem but it is a problem
related.

We are using a setup of running Csound on an Android 5.1 tablet and/or
phone.  The audio is then sent by bluetooth to a Belkin HD BT; the
SPDIF output from the Belkin is feed to 2029 digital Genelec
speakers.  This all work in general.

But.... there are constant glitches in the output, using Mike's
examples and a local one.  If we play from the tablet/phone there is
no glitches.  Our best guess is that the is a surfeit of conversions.
Analogue from csound to digital for bluetooth (we suspect this most) and
then back to analogue in the speakers.  it sounds like drop outs and is
not clipping.  A few experiments failed to get glitches from playing
tablet-stored sounds (but they were MP3 sources).

So the question is what an we do to get clean sound?

My guess is that the bluetooth support in android is not as good, and
that the load might result in delayed packets. I've had my phone slow
down music and then speed up (to catch back with the actual song) when
playing over bluetooth. Do you have the same problem when playing an
already-rendered file?

This is just thinking out loud, but maybe the app could be enhanced to
use dlna or rtp, and so stream the audio over wifi instead of
bluetooth?

Saludos

On 19 February 2016 at 12:19, jpff  wrote:
> I am not convinced this is a Csound problem but it is a problem
> related.
>
> We are using a setup of running Csound on an Android 5.1 tablet and/or
> phone.  The audio is then sent by bluetooth to a Belkin HD BT; the
> SPDIF output from the Belkin is feed to 2029 digital Genelec
> speakers.  This all work in general.
>
> But.... there are constant glitches in the output, using Mike's
> examples and a local one.  If we play from the tablet/phone there is
> no glitches.  Our best guess is that the is a surfeit of conversions.
> Analogue from csound to digital for bluetooth (we suspect this most) and
> then back to analogue in the speakers.  it sounds like drop outs and is
> not clipping.  A few experiments failed to get glitches from playing
> tablet-stored sounds (but they were MP3 sources).
>
> So the question is what an we do to get clean sound?
>
> ==John ffitch



-- 

Saludos,

You could buy a $35 ChromCast for Audio, install the ChromeCast app on
your phone, and plug the ChromeCast thingy into your speakers. Works
for me.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Fri, Feb 19, 2016 at 10:38 AM, Felipe Sateler  wrote:
> My guess is that the bluetooth support in android is not as good, and
> that the load might result in delayed packets. I've had my phone slow
> down music and then speed up (to catch back with the actual song) when
> playing over bluetooth. Do you have the same problem when playing an
> already-rendered file?
>
> This is just thinking out loud, but maybe the app could be enhanced to
> use dlna or rtp, and so stream the audio over wifi instead of
> bluetooth?
>
> Saludos
>
> On 19 February 2016 at 12:19, jpff  wrote:
>> I am not convinced this is a Csound problem but it is a problem
>> related.
>>
>> We are using a setup of running Csound on an Android 5.1 tablet and/or
>> phone.  The audio is then sent by bluetooth to a Belkin HD BT; the
>> SPDIF output from the Belkin is feed to 2029 digital Genelec
>> speakers.  This all work in general.
>>
>> But.... there are constant glitches in the output, using Mike's
>> examples and a local one.  If we play from the tablet/phone there is
>> no glitches.  Our best guess is that the is a surfeit of conversions.
>> Analogue from csound to digital for bluetooth (we suspect this most) and
>> then back to analogue in the speakers.  it sounds like drop outs and is
>> not clipping.  A few experiments failed to get glitches from playing
>> tablet-stored sounds (but they were MP3 sources).
>>
>> So the question is what an we do to get clean sound?
>>
>> ==John ffitch
>
>
>
> --
>
> Saludos,

If you Chromecast the screen you get the audio. I do this with an audio Chromecast device from my phone and it works.

It would still be desirable to enable direct Chromecast from Csound for Android.

Regards,
Mike

How do we do that?
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 23 Feb 2016, at 13:28, Michael Gogins  wrote:
> 
> If you Chromecast the screen you get the audio. I do this with an audio Chromecast device from my phone and it works.
> 
> It would still be desirable to enable direct Chromecast from Csound for Android.
> 
> Regards, 
> Mike
> 
> On Feb 23, 2016 8:22 AM, "Felipe Sateler"  wrote:
> Doesn't the app need to code in integration with chromecast? AFAICT, you cannot use the chromecast as "headphones" (output all audio there).
> 
> Saludos
> 
> On 19 Feb 2016 14:47, "Michael Gogins"  wrote:
> You could buy a $35 ChromCast for Audio, install the ChromeCast app on
> your phone, and plug the ChromeCast thingy into your speakers. Works
> for me.
> 
> Regards,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
> On Fri, Feb 19, 2016 at 10:38 AM, Felipe Sateler  wrote:
> > My guess is that the bluetooth support in android is not as good, and
> > that the load might result in delayed packets. I've had my phone slow
> > down music and then speed up (to catch back with the actual song) when
> > playing over bluetooth. Do you have the same problem when playing an
> > already-rendered file?
> >
> > This is just thinking out loud, but maybe the app could be enhanced to
> > use dlna or rtp, and so stream the audio over wifi instead of
> > bluetooth?
> >
> > Saludos
> >
> > On 19 February 2016 at 12:19, jpff  wrote:
> >> I am not convinced this is a Csound problem but it is a problem
> >> related.
> >>
> >> We are using a setup of running Csound on an Android 5.1 tablet and/or
> >> phone.  The audio is then sent by bluetooth to a Belkin HD BT; the
> >> SPDIF output from the Belkin is feed to 2029 digital Genelec
> >> speakers.  This all work in general.
> >>
> >> But.... there are constant glitches in the output, using Mike's
> >> examples and a local one.  If we play from the tablet/phone there is
> >> no glitches.  Our best guess is that the is a surfeit of conversions.
> >> Analogue from csound to digital for bluetooth (we suspect this most) and
> >> then back to analogue in the speakers.  it sounds like drop outs and is
> >> not clipping.  A few experiments failed to get glitches from playing
> >> tablet-stored sounds (but they were MP3 sources).
> >>
> >> So the question is what an we do to get clean sound?
> >>
> >> ==John ffitch
> >
> >
> >
> > --
> >
> > Saludos,

To Chromecast Csound, install the Chromecast app on Android, run Chromecast, and use the Chromecast menu to cast the screen and/or audio to a Chromecast device plugged into your amp or TV. Then just run Csound.

To add sending to Csound, we would use the Cast API (https://developers.google.com/cast/).

After thinking about adding cast to Csound, I'm not sure it's needed unless we want to cast only certain outputs of the Csound app instead of the whole screen and audio, which already works.

Best,
Mike

We could set up Cast as different audio backend (like we do on desktop for portaudio/coreaudio/alsa/jack/pulse), that could
be enabled using for instance -+rtaudio=cast. 
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 23 Feb 2016, at 14:13, Michael Gogins  wrote:
> 
> To Chromecast Csound, install the Chromecast app on Android, run Chromecast, and use the Chromecast menu to cast the screen and/or audio to a Chromecast device plugged into your amp or TV. Then just run Csound.
> 
> To add sending to Csound, we would use the Cast API (https://developers.google.com/cast/).
> 
> After thinking about adding cast to Csound, I'm not sure it's needed unless we want to cast only certain outputs of the Csound app instead of the whole screen and audio, which already works.
> 
> Best, 
> Mike
> 
> On Feb 23, 2016 8:55 AM, "Victor Lazzarini"  wrote:
> How do we do that?
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
> 
> > On 23 Feb 2016, at 13:28, Michael Gogins  wrote:
> >
> > If you Chromecast the screen you get the audio. I do this with an audio Chromecast device from my phone and it works.
> >
> > It would still be desirable to enable direct Chromecast from Csound for Android.
> >
> > Regards,
> > Mike
> >
> > On Feb 23, 2016 8:22 AM, "Felipe Sateler"  wrote:
> > Doesn't the app need to code in integration with chromecast? AFAICT, you cannot use the chromecast as "headphones" (output all audio there).
> >
> > Saludos
> >
> > On 19 Feb 2016 14:47, "Michael Gogins"  wrote:
> > You could buy a $35 ChromCast for Audio, install the ChromeCast app on
> > your phone, and plug the ChromeCast thingy into your speakers. Works
> > for me.
> >
> > Regards,
> > Mike
> >
> > -----------------------------------------------------
> > Michael Gogins
> > Irreducible Productions
> > http://michaelgogins.tumblr.com
> > Michael dot Gogins at gmail dot com
> >
> >
> > On Fri, Feb 19, 2016 at 10:38 AM, Felipe Sateler  wrote:
> > > My guess is that the bluetooth support in android is not as good, and
> > > that the load might result in delayed packets. I've had my phone slow
> > > down music and then speed up (to catch back with the actual song) when
> > > playing over bluetooth. Do you have the same problem when playing an
> > > already-rendered file?
> > >
> > > This is just thinking out loud, but maybe the app could be enhanced to
> > > use dlna or rtp, and so stream the audio over wifi instead of
> > > bluetooth?
> > >
> > > Saludos
> > >
> > > On 19 February 2016 at 12:19, jpff  wrote:
> > >> I am not convinced this is a Csound problem but it is a problem
> > >> related.
> > >>
> > >> We are using a setup of running Csound on an Android 5.1 tablet and/or
> > >> phone.  The audio is then sent by bluetooth to a Belkin HD BT; the
> > >> SPDIF output from the Belkin is feed to 2029 digital Genelec
> > >> speakers.  This all work in general.
> > >>
> > >> But.... there are constant glitches in the output, using Mike's
> > >> examples and a local one.  If we play from the tablet/phone there is
> > >> no glitches.  Our best guess is that the is a surfeit of conversions.
> > >> Analogue from csound to digital for bluetooth (we suspect this most) and
> > >> then back to analogue in the speakers.  it sounds like drop outs and is
> > >> not clipping.  A few experiments failed to get glitches from playing
> > >> tablet-stored sounds (but they were MP3 sources).
> > >>
> > >> So the question is what an we do to get clean sound?
> > >>
> > >> ==John ffitch
> > >
> > >
> > >
> > > --
> > >
> > > Saludos,

But that wouldn't catch the video from the HTML5 screen. This is
something I am using for visual music.

It sounds like you are thinking of adding cast to the Csound Android
library and I am thinking of adding it to the Csound for Android app.

But in both cases, what's the point? You can already cast Csound by
simply casting the Android screen.

Best,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Tue, Feb 23, 2016 at 9:40 AM, Victor Lazzarini
 wrote:
> We could set up Cast as different audio backend (like we do on desktop for portaudio/coreaudio/alsa/jack/pulse), that could
> be enabled using for instance -+rtaudio=cast.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 23 Feb 2016, at 14:13, Michael Gogins  wrote:
>>
>> To Chromecast Csound, install the Chromecast app on Android, run Chromecast, and use the Chromecast menu to cast the screen and/or audio to a Chromecast device plugged into your amp or TV. Then just run Csound.
>>
>> To add sending to Csound, we would use the Cast API (https://developers.google.com/cast/).
>>
>> After thinking about adding cast to Csound, I'm not sure it's needed unless we want to cast only certain outputs of the Csound app instead of the whole screen and audio, which already works.
>>
>> Best,
>> Mike
>>
>> On Feb 23, 2016 8:55 AM, "Victor Lazzarini"  wrote:
>> How do we do that?
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>> > On 23 Feb 2016, at 13:28, Michael Gogins  wrote:
>> >
>> > If you Chromecast the screen you get the audio. I do this with an audio Chromecast device from my phone and it works.
>> >
>> > It would still be desirable to enable direct Chromecast from Csound for Android.
>> >
>> > Regards,
>> > Mike
>> >
>> > On Feb 23, 2016 8:22 AM, "Felipe Sateler"  wrote:
>> > Doesn't the app need to code in integration with chromecast? AFAICT, you cannot use the chromecast as "headphones" (output all audio there).
>> >
>> > Saludos
>> >
>> > On 19 Feb 2016 14:47, "Michael Gogins"  wrote:
>> > You could buy a $35 ChromCast for Audio, install the ChromeCast app on
>> > your phone, and plug the ChromeCast thingy into your speakers. Works
>> > for me.
>> >
>> > Regards,
>> > Mike
>> >
>> > -----------------------------------------------------
>> > Michael Gogins
>> > Irreducible Productions
>> > http://michaelgogins.tumblr.com
>> > Michael dot Gogins at gmail dot com
>> >
>> >
>> > On Fri, Feb 19, 2016 at 10:38 AM, Felipe Sateler  wrote:
>> > > My guess is that the bluetooth support in android is not as good, and
>> > > that the load might result in delayed packets. I've had my phone slow
>> > > down music and then speed up (to catch back with the actual song) when
>> > > playing over bluetooth. Do you have the same problem when playing an
>> > > already-rendered file?
>> > >
>> > > This is just thinking out loud, but maybe the app could be enhanced to
>> > > use dlna or rtp, and so stream the audio over wifi instead of
>> > > bluetooth?
>> > >
>> > > Saludos
>> > >
>> > > On 19 February 2016 at 12:19, jpff  wrote:
>> > >> I am not convinced this is a Csound problem but it is a problem
>> > >> related.
>> > >>
>> > >> We are using a setup of running Csound on an Android 5.1 tablet and/or
>> > >> phone.  The audio is then sent by bluetooth to a Belkin HD BT; the
>> > >> SPDIF output from the Belkin is feed to 2029 digital Genelec
>> > >> speakers.  This all work in general.
>> > >>
>> > >> But.... there are constant glitches in the output, using Mike's
>> > >> examples and a local one.  If we play from the tablet/phone there is
>> > >> no glitches.  Our best guess is that the is a surfeit of conversions.
>> > >> Analogue from csound to digital for bluetooth (we suspect this most) and
>> > >> then back to analogue in the speakers.  it sounds like drop outs and is
>> > >> not clipping.  A few experiments failed to get glitches from playing
>> > >> tablet-stored sounds (but they were MP3 sources).
>> > >>
>> > >> So the question is what an we do to get clean sound?
>> > >>
>> > >> ==John ffitch
>> > >
>> > >
>> > >
>> > > --
>> > >
>> > > Saludos,

I don’t know whether there is a point, I am just discussing possibilities.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 23 Feb 2016, at 14:47, Michael Gogins  wrote:
> 
> But that wouldn't catch the video from the HTML5 screen. This is
> something I am using for visual music.
> 
> It sounds like you are thinking of adding cast to the Csound Android
> library and I am thinking of adding it to the Csound for Android app.
> 
> But in both cases, what's the point? You can already cast Csound by
> simply casting the Android screen.
> 
> Best,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
> On Tue, Feb 23, 2016 at 9:40 AM, Victor Lazzarini
>  wrote:
>> We could set up Cast as different audio backend (like we do on desktop for portaudio/coreaudio/alsa/jack/pulse), that could
>> be enabled using for instance -+rtaudio=cast.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>> 
>>> On 23 Feb 2016, at 14:13, Michael Gogins  wrote:
>>> 
>>> To Chromecast Csound, install the Chromecast app on Android, run Chromecast, and use the Chromecast menu to cast the screen and/or audio to a Chromecast device plugged into your amp or TV. Then just run Csound.
>>> 
>>> To add sending to Csound, we would use the Cast API (https://developers.google.com/cast/).
>>> 
>>> After thinking about adding cast to Csound, I'm not sure it's needed unless we want to cast only certain outputs of the Csound app instead of the whole screen and audio, which already works.
>>> 
>>> Best,
>>> Mike
>>> 
>>> On Feb 23, 2016 8:55 AM, "Victor Lazzarini"  wrote:
>>> How do we do that?
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 23 Feb 2016, at 13:28, Michael Gogins  wrote:
>>>> 
>>>> If you Chromecast the screen you get the audio. I do this with an audio Chromecast device from my phone and it works.
>>>> 
>>>> It would still be desirable to enable direct Chromecast from Csound for Android.
>>>> 
>>>> Regards,
>>>> Mike
>>>> 
>>>> On Feb 23, 2016 8:22 AM, "Felipe Sateler"  wrote:
>>>> Doesn't the app need to code in integration with chromecast? AFAICT, you cannot use the chromecast as "headphones" (output all audio there).
>>>> 
>>>> Saludos
>>>> 
>>>> On 19 Feb 2016 14:47, "Michael Gogins"  wrote:
>>>> You could buy a $35 ChromCast for Audio, install the ChromeCast app on
>>>> your phone, and plug the ChromeCast thingy into your speakers. Works
>>>> for me.
>>>> 
>>>> Regards,
>>>> Mike
>>>> 
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>> 
>>>> 
>>>> On Fri, Feb 19, 2016 at 10:38 AM, Felipe Sateler  wrote:
>>>>> My guess is that the bluetooth support in android is not as good, and
>>>>> that the load might result in delayed packets. I've had my phone slow
>>>>> down music and then speed up (to catch back with the actual song) when
>>>>> playing over bluetooth. Do you have the same problem when playing an
>>>>> already-rendered file?
>>>>> 
>>>>> This is just thinking out loud, but maybe the app could be enhanced to
>>>>> use dlna or rtp, and so stream the audio over wifi instead of
>>>>> bluetooth?
>>>>> 
>>>>> Saludos
>>>>> 
>>>>> On 19 February 2016 at 12:19, jpff  wrote:
>>>>>> I am not convinced this is a Csound problem but it is a problem
>>>>>> related.
>>>>>> 
>>>>>> We are using a setup of running Csound on an Android 5.1 tablet and/or
>>>>>> phone.  The audio is then sent by bluetooth to a Belkin HD BT; the
>>>>>> SPDIF output from the Belkin is feed to 2029 digital Genelec
>>>>>> speakers.  This all work in general.
>>>>>> 
>>>>>> But.... there are constant glitches in the output, using Mike's
>>>>>> examples and a local one.  If we play from the tablet/phone there is
>>>>>> no glitches.  Our best guess is that the is a surfeit of conversions.
>>>>>> Analogue from csound to digital for bluetooth (we suspect this most) and
>>>>>> then back to analogue in the speakers.  it sounds like drop outs and is
>>>>>> not clipping.  A few experiments failed to get glitches from playing
>>>>>> tablet-stored sounds (but they were MP3 sources).
>>>>>> 
>>>>>> So the question is what an we do to get clean sound?
>>>>>> 
>>>>>> ==John ffitch
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> 
>>>>> Saludos,