Hi,
I've noticed a performance issue in an html/javascript app I'm coding for
CsoundApplication so I've written a minimal example that shows the problem.

This is an html page counting the number of touches reported in the form.
Each touch is associated with a score line calling an instrument for some
time.

When the number is below 300, all is ok and I can "play" as fast as my
fingers can.
Above (varying between 320 and 400), the fast notes aren't caught any more
and I can "play" only one note per second or so. This is a clean cut from
one touch (say the 321st) to the other (the 322th). 
Above that, the problem doesn't solve itself, the response time is slow and
the counter even drops some range before updating.

Can you please try on your Android devices and tell me if this happens to
you too ?

testScore.csd
  




--
View this message in context: http://csound.1045644.n5.nabble.com/problem-with-readScore-in-CsoundApplication-aka-csdplayer-tp5744121.html
Sent from the Csound - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

It could be a limitation of the touch surface. Maybe it is device dependent.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 6 Oct 2015, at 19:33, ebmtranceboy  wrote:
> 
> Hi,
> I've noticed a performance issue in an html/javascript app I'm coding for
> CsoundApplication so I've written a minimal example that shows the problem.
> 
> This is an html page counting the number of touches reported in the form.
> Each touch is associated with a score line calling an instrument for some
> time.
> 
> When the number is below 300, all is ok and I can "play" as fast as my
> fingers can.
> Above (varying between 320 and 400), the fast notes aren't caught any more
> and I can "play" only one note per second or so. This is a clean cut from
> one touch (say the 321st) to the other (the 322th). 
> Above that, the problem doesn't solve itself, the response time is slow and
> the counter even drops some range before updating.
> 
> Can you please try on your Android devices and tell me if this happens to
> you too ?
> 
> testScore.csd
>   
> 
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/problem-with-readScore-in-CsoundApplication-aka-csdplayer-tp5744121.html
> Sent from the Csound - General mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Csound-users mailing list
> Csound-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-users
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Hi,

I cannot test the csd right now, but one guess:

is there also a method like csound.InputMessage(<score_string>) ?

MIght be that takes less resources that readScore and works better.

Hardly it helps...

tarmo

On Tuesday 06 October 2015 11:33:30 ebmtranceboy wrote:

> Hi,

> I've noticed a performance issue in an html/javascript app I'm coding for

> CsoundApplication so I've written a minimal example that shows the problem.

>

> This is an html page counting the number of touches reported in the form.

> Each touch is associated with a score line calling an instrument for some

> time.

>

> When the number is below 300, all is ok and I can "play" as fast as my

> fingers can.

> Above (varying between 320 and 400), the fast notes aren't caught any more

> and I can "play" only one note per second or so. This is a clean cut from

> one touch (say the 321st) to the other (the 322th).

> Above that, the problem doesn't solve itself, the response time is slow and

> the counter even drops some range before updating.

>

> Can you please try on your Android devices and tell me if this happens to

> you too ?

>

> testScore.csd

> <http://csound.1045644.n5.nabble.com/file/n5744121/testScore.csd>

>

>

>

>

> --

> View this message in context:

> http://csound.1045644.n5.nabble.com/problem-with-readScore-in-CsoundApplica

> tion-aka-csdplayer-tp5744121.html Sent from the Csound - General mailing

> list archive at Nabble.com.

>

> ----------------------------------------------------------------------------

> -- _______________________________________________

> Csound-users mailing list

> Csound-users@lists.sourceforge.net

> https://lists.sourceforge.net/lists/listinfo/csound-users

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

Hi Tarmo,
according to the source code, readScore is a wrapper around sendScore which
is a wrapper around inputMessage! I've tried your suggestion though but as
expected the same happened.



--
View this message in context: http://csound.1045644.n5.nabble.com/problem-with-readScore-in-CsoundApplication-aka-csdplayer-tp5744121p5744154.html
Sent from the Csound - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Full-scale, agent-less Infrastructure Monitoring from a single dashboard
Integrate with 40+ ManageEngine ITSM Solutions for complete visibility
Physical-Virtual-Cloud Infrastructure monitoring from one console
Real user monitoring with APM Insights and performance trend reports 
Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

hmm...

The symptoms look like somehow the memory or other resources get exhausted... Can you check perhaps in Android's Configuration->Applications and see how much memory is CsoundApplication using? Does it get bigger after tapping a while? Maybe there is somewhere a memory leak.

tarmo

On Wednesday 07 October 2015 03:30:56 ebmtranceboy wrote:

> Hi Tarmo,

> according to the source code, readScore is a wrapper around sendScore which

> is a wrapper around inputMessage! I've tried your suggestion though but as

> expected the same happened.

>

>

>

> --

> View this message in context:

> http://csound.1045644.n5.nabble.com/problem-with-readScore-in-CsoundApplica

> tion-aka-csdplayer-tp5744121p5744154.html Sent from the Csound - General

> mailing list archive at Nabble.com.

>

> ----------------------------------------------------------------------------

> -- Full-scale, agent-less Infrastructure Monitoring from a single dashboard

> Integrate with 40+ ManageEngine ITSM Solutions for complete visibility

> Physical-Virtual-Cloud Infrastructure monitoring from one console

> Real user monitoring with APM Insights and performance trend reports

> Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140

> _______________________________________________

> Csound-users mailing list

> Csound-users@lists.sourceforge.net

> https://lists.sourceforge.net/lists/listinfo/csound-users

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here