Re: TamTam packaging
I don't think using the aclient is the better way to make it work on Debian. This client was build very tight to save cpu cycles on the XO. The better way is to use the Python API for Csound... (with the API, don't forget to remove -n flag (no sound) in tamtamorc.csd). Maybe James can tell you more about aclient.so I did not look closely so did not realize that python-csound is not used. Anyway I'd rather keep changes from the XO version at a minimum for now and not add extra code. The goal is to get it working first. When tested on jhbuild, we've got erratic sound.Good luck! No sound at all here, not even erratic. One important issue I forgot to mention yesterday: there are no licensing headers or copyright files in the sources except in Clooper/audio.cpp which comes from ALSA. Can you when time permits add any kind of copyright notice along the source files? It is impossible to upload to either Debian or Ubuntu otherwise. Absolutely! Thanks for the warning... Can you say which license will it be until you get around to adding it to the sources so I get a head start with packaging. While adding headers to all files is a lot of work and probably preferable, adding a LICENSE file in each xo would do too. Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Perhaps the multiple apps using the soundcard are using dmix, in which
case, you might want to see if you can get csound connected to it too.
(-odac:dmix i think). However I never bothered with dmix as it is one
awkward piece of software.
insert_score_event(): invalid instrument number or name
This generated by insert_score_event() (musmon.c), in the csound
library:
i = (int) fabs((double) p[1]);
if ((unsigned int) (i - 1) = (unsigned int) csound-maxinsno ||
csound-instrtxtp[i] == NULL) {
csoundMessage(csound, Str(insert_score_event(): invalid
instrument
number or name\n));
This indicates something amiss with the CSD file, the instrument has not
been
found, 'i' is p-field 1 in the score event and and should be an index to a
valid
instrument name/number.
Not sure why, but could be something in the csd parsing. Examining the csd
tamtam generated might give us a clue.
Victor
- Original Message -
From: Jani Monoses [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, April 19, 2008 3:10 PM
Subject: Re: TamTam packaging
New packages have made into debian testing. You might want to try
those. Also remember you need to set the OPCODEDIR (OPCODEDIR64 in
your case) so the csound library can find the plugins (plugins in
csound include opcode plugins and realtime output modules).
Actually csound works from the command line iff no other app is using
the sound card.
Multiple apps can play simultaneously (flash in firefox, mpg123) but
csound is not among them.
It uses ALSA for rtaudio and gives this.
*** Cannot open device 'plughw' for audio output: Device or resource busy
So if no other apps use the sound the pippy sound examples work fine,
but tamtam activities do not work even then, with many lines such as
this one in the logs.
insert_score_event(): invalid instrument number or name
I've attached a full log of tamtam mini in case someone can help to
figure out what could be wrong.
Jani
PortMIDI real time MIDI plugin for Csound
PortAudio real-time audio module for Csound
virtual_keyboard real time MIDI plugin for Csound
0dBFS level = 32768.0
Csound version 5.08 (double samples) Apr 16 2008
libsndfile-1.0.17
UnifiedCSD:
/home/jani/Activities/TamTamMini.activity/common/Resources/tamtamorc.csd
STARTING FILE
Creating options
Creating orchestra
Creating score
orchname: /tmp/fileu5b7q9.orc
scorename: /tmp/filey4hDAb.sco
rtaudio: PortAudio module enabled ... using blocking interface
rtmidi: PortMIDI module enabled
orch compiler:
1091 lines read
opcode homeSine a kki
opcode synthGrain a aa
opcode ControlMatrice i ii
opcode SourceMatrice i i
opcode FxMatrice i i
opcode controller k ii
opcode source a ii
opcode effects a ii
instr 200
instr 5600
instr 5400
instr 5401
instr 5201
instr 5202
instr 5212
instr 6000
instr 5204
instr 5203
Token length extended to 256
instr 5000
instr 5022
instr 5023
instr 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010
instr 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110
instr 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020
instr 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120
instr 5021
LABELS list is full...extending to 10
LABELS list is full...extending to 15
LABELS list is full...extending to 20
LABELS list is full...extending to 25
LABELS list is full...extending to 30
sorting score ...
sread: unexpected char ,
section 1: at position 41
in line 1110 of file input
/home/jani/Activities/TamTamMini.activity/common/Resources/tamtamorc.csd
remainder of line flushed
... done
Csound version 5.08 (double samples) Apr 16 2008
displays suppressed
0dBFS level = 32768.0
orch now loaded
audio buffered in 256 sample-frame blocks
SECTION 1:
ftable 1:
ftable 2:
ftable 4:
ftable 30:
ftable 31:
ftable 32:
ftable 33:
ftable 34:
ftable 35:
ftable 36:
ftable 37:
ftable 38:
ftable 39:
ftable 41:
ftable 42:
ftable 44:
ftable 45:
ftable 5150:
ftable 6001:
ftable 6002:
ftable 6003:
ftable 6004:
new alloc for instr 200:
ALSA lib pcm.c:7075:(snd_pcm_recover) underrun occured
ALSA lib pcm.c:7075:(snd_pcm_recover) underrun occured
/usr/lib/python2.5/site-packages/sugar/graphics/window.py:135: GtkWarning:
gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) ||
widget-parent == GTK_WIDGET (container)' failed
self._vbox.remove(self.toolbox)
rtevent:T 0.304 TT 0.304 M: 0.0 0.0
ftable 5028:
deferred alloc
audio sr = 16000, monaural
opening WAV infile
/home/jani/Activities/TamTamEdit.activity/common/Resources/Sounds/drum1splash
defer length 24000
ftable 5027:
deferred alloc
audio sr = 16000, monaural
opening WAV infile
/home/jani/Activities/TamTamEdit.activity/common/Resources/Sounds/drum1crash
defer length 32000
ftable 5026:
deferred alloc
audio sr = 16000
Re: TamTam packaging
-why are the cpp sources in the MANIFEST and consequently in the xo? At the beginning we TamTam was only one activity with a welcome screen to choose which component to play with. When we were aksed to spilt the activities it was the simplest way for us to manage all activities from one git tree. But all sounds and common images are located only inside TamTamEdit. Ok. But are the c++ sources in common/Util/Clooper/ needed in the final xo? -which versions do you recommend for packaging. Latest are 48 and 49 , depending on the activity Always the latest... even though i'm on the way to make major changes in the way TamTam handle resources (mic recording, synthlab sounds...) to respect OLPC security policy. These changes will complicate once more the port to others system... I got them to build and start on Ubuntu but I have no sound The lib is acsound64 not acsound in debian/ubuntu so the link flag needed a change to rebuild the aclient.so instead of using the one in git. I don't think using the aclient is the better way to make it work on Debian. This client was build very tight to save cpu cycles on the XO. The better way is to use the Python API for Csound... (with the API, don't forget to remove -n flag (no sound) in tamtamorc.csd). Maybe James can tell you more about aclient.so I did not look closely so did not realize that python-csound is not used. Anyway I'd rather keep changes from the XO version at a minimum for now and not add extra code. The goal is to get it working first. One important issue I forgot to mention yesterday: there are no licensing headers or copyright files in the sources except in Clooper/audio.cpp which comes from ALSA. Can you when time permits add any kind of copyright notice along the source files? It is impossible to upload to either Debian or Ubuntu otherwise. thank you Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Le 08-04-17 à 02:49, Jani Monoses a écrit : -why are the cpp sources in the MANIFEST and consequently in the xo? At the beginning we TamTam was only one activity with a welcome screen to choose which component to play with. When we were aksed to spilt the activities it was the simplest way for us to manage all activities from one git tree. But all sounds and common images are located only inside TamTamEdit. Ok. But are the c++ sources in common/Util/Clooper/ needed in the final xo? No. -which versions do you recommend for packaging. Latest are 48 and 49 , depending on the activity Always the latest... even though i'm on the way to make major changes in the way TamTam handle resources (mic recording, synthlab sounds...) to respect OLPC security policy. These changes will complicate once more the port to others system... I got them to build and start on Ubuntu but I have no sound The lib is acsound64 not acsound in debian/ubuntu so the link flag needed a change to rebuild the aclient.so instead of using the one in git. I don't think using the aclient is the better way to make it work on Debian. This client was build very tight to save cpu cycles on the XO. The better way is to use the Python API for Csound... (with the API, don't forget to remove -n flag (no sound) in tamtamorc.csd). Maybe James can tell you more about aclient.so I did not look closely so did not realize that python-csound is not used. Anyway I'd rather keep changes from the XO version at a minimum for now and not add extra code. The goal is to get it working first. When tested on jhbuild, we've got erratic sound.Good luck! One important issue I forgot to mention yesterday: there are no licensing headers or copyright files in the sources except in Clooper/audio.cpp which comes from ALSA. Can you when time permits add any kind of copyright notice along the source files? It is impossible to upload to either Debian or Ubuntu otherwise. Absolutely! Thanks for the warning... thank you Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Hi Jani, On Wed, Apr 16, 2008 at 6:44 PM, Jani Monoses [EMAIL PROTECTED] wrote: The lib is acsound64 not acsound in debian/ubuntu so the link flag needed a change to rebuild the aclient.so instead of using the one in git. the lib will have a 64 if csound was built for double (64 bits) precision. Since the OLPC uses the float build it uses a different file (this setup allows a system to have both floats and doubles version of csound without conflicts). Hardcoded paths starting with /home/olpc were changed too but it still does not play any sound - the graphics are stunning though! :) The version of csound for the XO is a modified version which among other things uses the alsa output module by default. The normal version defaults to portaudio. You would need to check whether csound is actually producing sound on your machine. You can use many of the manual examples (e.g. oscil.csd), which are configured for realtime audio. If csound is producing output tamtam should too. I tried it some time ago on a debian machine, and it worked fine. csound is 5.08.0 do you know if that should be OK? yes, the current version of OLPCsound is a cvs version a little later than the official 5.08, but there should be no important changes. Minor change to get it to build with -Werror with g++ 4.2.3 (Ubuntu 8.04) Can you post the error? Cheers, Andrés ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Hi Andres, the lib will have a 64 if csound was built for double (64 bits) precision. Since the OLPC uses the float build it uses a different file (this setup allows a system to have both floats and doubles version of csound without conflicts). Changing the makefile to link agains libcsound64.so made it build so that is fine. Are there runtime incompatibilities I should be aware of and which could make it not run on debian? Hardcoded paths starting with /home/olpc were changed too but it still does not play any sound - the graphics are stunning though! :) The version of csound for the XO is a modified version which among other things uses the alsa output module by default. The normal version defaults to portaudio. You would need to check whether csound is actually producing sound on your machine. You can use many of the manual examples (e.g. oscil.csd), which are configured for realtime audio. If csound is producing output tamtam should too. I tried it some time ago on a debian machine, and it worked fine. I tried a while ago and it worked and from pippy as well, but the latest package does not. So it is may not be a tamtam issue after all. csound is 5.08.0 do you know if that should be OK? yes, the current version of OLPCsound is a cvs version a little later than the official 5.08, but there should be no important changes. Minor change to get it to build with -Werror with g++ 4.2.3 (Ubuntu 8.04) Can you post the error? two instances of warning: deprecated conversion from string constant to ‘char*’ which are eliminated by the patch I attached yesterday Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Hi Jani, On Thu, Apr 17, 2008 at 9:43 AM, Jani Monoses [EMAIL PROTECTED] wrote: Changing the makefile to link agains libcsound64.so made it build so that is fine. Are there runtime incompatibilities I should be aware of and which could make it not run on debian? No incompatbilites as long as all the build is the same precision. I tried a while ago and it worked and from pippy as well, but the latest package does not. So it is may not be a tamtam issue after all. New packages have made into debian testing. You might want to try those. Also remember you need to set the OPCODEDIR (OPCODEDIR64 in your case) so the csound library can find the plugins (plugins in csound include opcode plugins and realtime output modules). Can you post the error? two instances of warning: deprecated conversion from string constant to 'char*' which are eliminated by the patch I attached yesterday Jani Thanks! Cheers, Andrés ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Hi Jani, First of all, our main goal is to make TamTam runs on the XO. We didn't think yet about porting it to others system... Le 08-04-16 à 17:44, Jani Monoses a écrit : Hi Olivier, I have a few questions regarding the .deb packaging of the four TamTam activities. -why are the cpp sources in the MANIFEST and consequently in the xo? At the beginning we TamTam was only one activity with a welcome screen to choose which component to play with. When we were aksed to spilt the activities it was the simplest way for us to manage all activities from one git tree. But all sounds and common images are located only inside TamTamEdit. -which versions do you recommend for packaging. Latest are 48 and 49 , depending on the activity Always the latest... even though i'm on the way to make major changes in the way TamTam handle resources (mic recording, synthlab sounds...) to respect OLPC security policy. These changes will complicate once more the port to others system... I got them to build and start on Ubuntu but I have no sound The lib is acsound64 not acsound in debian/ubuntu so the link flag needed a change to rebuild the aclient.so instead of using the one in git. I don't think using the aclient is the better way to make it work on Debian. This client was build very tight to save cpu cycles on the XO. The better way is to use the Python API for Csound... (with the API, don't forget to remove -n flag (no sound) in tamtamorc.csd). Maybe James can tell you more about aclient.so ( [EMAIL PROTECTED] ) Hardcoded paths starting with /home/olpc were changed too but it still does not play any sound - the graphics are stunning though! :) csound is 5.08.0 do you know if that should be OK? Minor change to get it to build with -Werror with g++ 4.2.3 (Ubuntu 8.04) thanks Jani --- a/common/Util/Clooper/aclient.cpp +++ b/common/Util/Clooper/aclient.cpp @@ -549,8 +549,8 @@ struct TamTamSound csound = csoundCreate(NULL); int argc=3; char **argv = (char**)malloc(argc*sizeof(char*)); -argv[0] = csound; -argv[1] = -m7; +argv[0] = (char *)csound; +argv[1] = (char *)-m7; argv[2] = orc; : Thanks for trying to make it works on Debian! Olivier ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
