Csound Csound-dev Csound-tekno Search About

Re: [Csnd] CSound Android questions

Date2014-01-20 22:54
From"Art Hunkins"
SubjectRe: [Csnd] CSound Android questions
Mike,
 
How is this project (redoing the Android 6.01 apk) going?
 
A related question for any Csounder on Android:
 
All Android apps for Csound5 and Csound6 work for me fine on smartphones and tablets *7" and above*.
 
Recently, however, I purchased a 4.3" Proscan PT4311 tablet (about the size of a smartphone). Csound5 works fine on it; but no version of Csound6 does. Csound6 installs fine, but when the icon is touched, only the very top panel appears momentarily and the screen immediately reverts to the home screen. (This is true even of the current Csound 6.02 app, which is only 3.3MB.)
 
1) Is a log available anywhere on the device that would indicate the issue?
 
2) What could be the cause?
 
One possibility relates to screen resolution: neither for Csound5 or 6 does the Proscan display all the widgets on a single screen. (It shows about 5 sliders, and that is all.) With Csound5, however, the entire screen scrolls and all controls *can* be accessed (if with difficulty). With Csound6, the widget display is fixed - only the console output scrolls (below, and here off-screen). Could perhaps the locked and partial widget display be causing the problem? (On all other devices - including smartphones - the widget display is complete.)
 
Art Hunkins
----- Original Message -----
To: Csound
Sent: Tuesday, January 14, 2014 1:46 PM
Subject: Re: [Csnd] CSound Android questions

Sometime before this weekend I will rebuild and replace the .apk. First, however, I want to resolve the alwayson opcode bug, this opcode seems to have become widely enough used that its malfunction is a serious problem.

Regards,
Mike


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


On Tue, Jan 14, 2014 at 1:43 PM, Steven Yi <stevenyi@gmail.com> wrote:
I don't know who built the APK in the 6.02 folder.  Michael, could you
do a build and replace the one there?  We really should have the same
build by the same person so that the key used to sign the APK is the
same.

On Tue, Jan 14, 2014 at 1:41 PM, Art Hunkins <abhunkin@uncg.edu> wrote:
> Thanks for the info, Mike.
>
> I'd never realized (nor discovered) that your Android apps included
> examples!
>
> What folder are they in, once the app is installed? Or how else can I access
> them?
>
> Art Hunkins
>
> ----- Original Message -----
> From: Michael Gogins
> To: Csound
> Sent: Tuesday, January 14, 2014 1:02 PM
> Subject: Re: [Csnd] CSound Android questions
>
> My .apk bundles a bunch of examples including your chime pad. I think the
> person who created the current .apk did not do this.
>
> Regards,
> Mike
>
>
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Tue, Jan 14, 2014 at 1:00 PM, Michael Gogins <michael.gogins@gmail.com>
> wrote:
>>
>> I believe there has been a break in the alwayson opcode in the current
>> release of Csound. This applies to all versions I have tested: command line
>> Csound, CsoundVST, and CsoundQt.
>>
>> There is no need for a score statement to be sent to an alwayson
>> instrument. The pfields the follow the instrument name of the alwayson
>> opcode represent pfields 4 and up of a score statement.
>>
>> I have some urgent work in the next few days, but then I will try to fix
>> this bug if nobody else has fixed it in the meantime.
>>
>> Thanks for the information,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Tue, Jan 14, 2014 at 10:44 AM, Jacques Leplat <jleplat@j3ltd.com>
>> wrote:
>>>
>>> Hello,
>>>
>>> I have been grappling with the latest Android release (Csound6.apk and
>>> Csound-android-6.02.0.zip).
>>>
>>> I think the apk is different to the CSD Player project in the zip.
>>>
>>> The alwayson opcode is not recognised in the apk file, but is recognised
>>> in the zip release of the Android Csound SDK.
>>>
>>> I am also having problems using alwayson on Android.  On the mac release
>>> of CSound, the csd (see below) produces sound, but on Android it is silent.
>>> If I uncomment the line “i2 0 1”, sound is produced. So it looks to me like
>>> alwayson behaves differently on Android and Mac.
>>>
>>> In terms of correct CSound syntax, do I not know if an alwayson
>>> instrument has to have a score event sent to it for the duration of the
>>> score. Does it?
>>>
>>> All the best,
>>>
>>> Jacques
>>>
>>> <CsoundSynthesizer>
>>> <CsOptions>
>>> -odac
>>> </CsOptions>
>>> <CsInstruments>
>>> sr = 44100
>>> ksmps = 32
>>> nchnls = 2
>>> 0dbfs = 1
>>>
>>> ;-- Definitions for instrument [1] id [1009] outInstr
>>> alwayson "outInstr"
>>> gaoutL init 0
>>> gaoutR init 0
>>> gkPan init 50
>>> gkVolume init 80
>>> gklevelL init 0
>>> gklevelR init 0
>>>
>>> ;-- Definitions for instrument [1] id [1007] pulse
>>> gkPan1 init 50
>>> gkVolume1 init 80
>>>
>>>
>>> ;-- Instrument [1] id [1007] pulse
>>> instr 1
>>> ifreq = cpspch(p5)
>>> iamp = p4
>>> idur = p3
>>> iwave = 2001
>>> idetune = 0.3
>>> kenv linseg 0, .01, iamp, idur-.1, iamp*.8, .05, 0
>>> aoutL oscili kenv, ifreq - idetune, iwave
>>> aoutR oscili kenv, ifreq + idetune, iwave
>>> kfactorL = 1
>>> kfactorR = 1
>>> gaoutL = gaoutL + aoutL * kfactorL
>>> gaoutR = gaoutR + aoutR * kfactorR
>>>
>>> endin
>>>
>>> ;-- Output Instrument
>>> instr outInstr
>>> kfactorL = 0.5
>>> kfactorR = 0.5
>>> gaoutL = gaoutL * kfactorL
>>> gaoutR = gaoutR * kfactorR
>>> outs gaoutL,gaoutR
>>> gaoutL = 0
>>> gaoutR = 0
>>>
>>> endin
>>> </CsInstruments>
>>> <CsScore>
>>>
>>> ;-- Functions for instrument [1] id [1007] pulse
>>> f 2001 0 513 10 .8 .9 .95 .96 1 .91 .8 .75 .6 .42 .5 .4 .33 .28 .2 .15
>>>
>>> ;inst start dur amplitude noteNumber; midiNote
>>> ;i2 0 1
>>> i1 0 0.152 0.62 9.04 ;76 v:80
>>> i1 0 0.505 0.62 7.00 ;48 v:80
>>> i1 0 0.505 0.62 7.04 ;52 v:80
>>> i1 0.145 0.128 0.55 9.00 ;72 v:70
>>> i1 0.267 0.126 0.55 9.07 ;79 v:70
>>> i1 0.386 0.126 0.55 9.04 ;76 v:70
>>> i1 0.505 0.129 0.55 10.00 ;84 v:70
>>> i1 0.627 0.129 0.55 9.07 ;79 v:70
>>> e 1
>>> </CsScore>
>>> </CsoundSynthesizer>
>>>
>>>
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug trackers
>>> csound6:
>>>             https://sourceforge.net/p/csound/tickets/
>>> csound5:
>>>             https://sourceforge.net/p/csound/bugs/
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




Date2014-01-21 12:55
FromJacques Leplat
SubjectRe: [Csnd] CSound Android questions
There are apps that display system log file contents, such as Android System Info. Not sure which one is best so you may have t hunt google’s play store for the one that you like the most.

All the best,

Jacques

Mike,
 
How is this project (redoing the Android 6.01 apk) going?
 
A related question for any Csounder on Android:
 
All Android apps for Csound5 and Csound6 work for me fine on smartphones and tablets *7" and above*.
 
Recently, however, I purchased a 4.3" Proscan PT4311 tablet (about the size of a smartphone). Csound5 works fine on it; but no version of Csound6 does. Csound6 installs fine, but when the icon is touched, only the very top panel appears momentarily and the screen immediately reverts to the home screen. (This is true even of the current Csound 6.02 app, which is only 3.3MB.)
 
1) Is a log available anywhere on the device that would indicate the issue?
 
2) What could be the cause?
 
One possibility relates to screen resolution: neither for Csound5 or 6 does the Proscan display all the widgets on a single screen. (It shows about 5 sliders, and that is all.) With Csound5, however, the entire screen scrolls and all controls *can* be accessed (if with difficulty). With Csound6, the widget display is fixed - only the console output scrolls (below, and here off-screen). Could perhaps the locked and partial widget display be causing the problem? (On all other devices - including smartphones - the widget display is complete.)
 
Art Hunkins


Date2014-01-21 16:27
FromTarmo Johannes
SubjectRe: [Csnd] CSound Android questions

Hi, Art

 

I made some experiments with the Csound-android-6 first time today. One thing I noticed that in the Android manifest file of the CsoundAndroid sources the minimal android version required was set to is API-11 (Android 3.0). I have an old smart phone with android 2.3 and The official Csound6.apk pacakge it did not work for me their either. I changed the required minimum in the project sources to 10 and then it worked.

 

If you have eclipse and android development kit installed, it is easy to fix:

download http://sourceforge.net/projects/csound/files/csound6/Csound6.02/Csound-android-6.02.0.zip/download

 

and change in every project file AndroidManifest.xml

<uses-sdk android:minSdkVersion="11" />

 

to

 

<uses-sdk android:minSdkVersion="11" />

 

 

(or I can send my apk for you to try)

 

BUT

 

I think the minimum requirement is set for a reason, there might be things that don't work with lower android. Mike, Victor, Steven, can you tell?

 

thanks,

tarmo

 

On Monday 20 January 2014 17:54:45 Art Hunkins wrote:

Recently, however, I purchased a 4.3" Proscan PT4311 tablet (about the size of a smartphone). Csound5 works fine on it; but no version of Csound6 does. Csound6 installs fine, but when the icon is touched, only the very top panel appears momentarily and the screen immediately reverts to the home screen. (This is true even of the current Csound 6.02 app, which is only 3.3MB.)




Date2014-01-21 17:57
FromMichael Gogins
SubjectRe: [Csnd] CSound Android questions
As for me, I just went with what already there from Victor and Steve.

Regards,
Mike


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


On Tue, Jan 21, 2014 at 11:27 AM, Tarmo Johannes <tarmo.johannes@otsakool.edu.ee> wrote:

Hi, Art

 

I made some experiments with the Csound-android-6 first time today. One thing I noticed that in the Android manifest file of the CsoundAndroid sources the minimal android version required was set to is API-11 (Android 3.0). I have an old smart phone with android 2.3 and The official Csound6.apk pacakge it did not work for me their either. I changed the required minimum in the project sources to 10 and then it worked.

 

If you have eclipse and android development kit installed, it is easy to fix:

download http://sourceforge.net/projects/csound/files/csound6/Csound6.02/Csound-android-6.02.0.zip/download

 

and change in every project file AndroidManifest.xml

<uses-sdk android:minSdkVersion="11" />

 

to

 

<uses-sdk android:minSdkVersion="11" />

 

 

(or I can send my apk for you to try)

 

BUT

 

I think the minimum requirement is set for a reason, there might be things that don't work with lower android. Mike, Victor, Steven, can you tell?

 

thanks,

tarmo

 

On Monday 20 January 2014 17:54:45 Art Hunkins wrote:

Recently, however, I purchased a 4.3" Proscan PT4311 tablet (about the size of a smartphone). Csound5 works fine on it; but no version of Csound6 does. Csound6 installs fine, but when the icon is touched, only the very top panel appears momentarily and the screen immediately reverts to the home screen. (This is true even of the current Csound 6.02 app, which is only 3.3MB.)





Date2014-01-21 18:22
FromSteven Yi
SubjectRe: [Csnd] CSound Android questions
This used to be set to minSdkVersion=9.  I looked up in git and it was
changed in commit bad32252f664406b9da468f7814d94ceef1a0c63 by John
ffitch on June 1, 2013. I don't know the rationale behind it, as the
commit message says "array opcode".  Perhaps it was a commit in error?

Other than that, this shouldn't be an issue for Art's device, as it
has Android 4.0 I believe.

On Tue, Jan 21, 2014 at 5:57 PM, Michael Gogins
 wrote:
> As for me, I just went with what already there from Victor and Steve.
>
> Regards,
> Mike
>
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Tue, Jan 21, 2014 at 11:27 AM, Tarmo Johannes
>  wrote:
>>
>> Hi, Art
>>
>>
>>
>> I made some experiments with the Csound-android-6 first time today. One
>> thing I noticed that in the Android manifest file of the CsoundAndroid
>> sources the minimal android version required was set to is API-11 (Android
>> 3.0). I have an old smart phone with android 2.3 and The official
>> Csound6.apk pacakge it did not work for me their either. I changed the
>> required minimum in the project sources to 10 and then it worked.
>>
>>
>>
>> If you have eclipse and android development kit installed, it is easy to
>> fix:
>>
>> download
>> http://sourceforge.net/projects/csound/files/csound6/Csound6.02/Csound-android-6.02.0.zip/download
>>
>>
>>
>> and change in every project file AndroidManifest.xml
>>
>> 
>>
>>
>>
>> to
>>
>>
>>
>> 
>>
>>
>>
>>
>>
>> (or I can send my apk for you to try)
>>
>>
>>
>> BUT
>>
>>
>>
>> I think the minimum requirement is set for a reason, there might be things
>> that don't work with lower android. Mike, Victor, Steven, can you tell?
>>
>>
>>
>> thanks,
>>
>> tarmo
>>
>>
>>
>> On Monday 20 January 2014 17:54:45 Art Hunkins wrote:
>>
>> Recently, however, I purchased a 4.3" Proscan PT4311 tablet (about the
>> size of a smartphone). Csound5 works fine on it; but no version of Csound6
>> does. Csound6 installs fine, but when the icon is touched, only the very top
>> panel appears momentarily and the screen immediately reverts to the home
>> screen. (This is true even of the current Csound 6.02 app, which is only
>> 3.3MB.)
>>
>>
>>
>