i've been trying to make my code clearer, trying to  learn about git,
and trying to learn how to share code effectively, so i've spent some
time recently cleaning up this wiimote instrument to share.

this is a short arbitrary performance with it i made in the spring. the
idea was to program chord changes from fake books and conduct melodies
with the wii at a jam session. i have yet to attempt this.

http://ongaku.isa-geek.net/~khirai/wii/wii_jazz_rec_for_bill2.mp3

the code is available here:
git clone git://ongaku.isa-geek.net/~khirai/wii_jazz

thanks for reading and listening.
k.





Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hello,

I tried your code, the compilation is OK, but I get a wiimote connection
error (see below). I also get the same error with other csd (wii opcodes).

My question is: why I can't connect my wiimote (+ nunchuk) with my system,
while other linux users can do that?

Lot of mistakes with Linux tools as Cwiid, wminput, bluedevil.

Thanks!

---------------------------------
Wiiuse version 0.14 (compilation OK)
Bluez without wiimote plugin
Kernel without last wiimote module
--

Linux fixe.lan 3.0.14-1.rt31.1.fc16.ccrma.x86_64.rt #1 SMP PREEMPT RT Thu
Dec 22 09:51:53 PST 2011 x86_64 x86_64 x86_64 GNU/Linux

--
[maestro@fixe wii_jazz]$ csound -+rtaudio=jack -o dac  -m 0 -d wii_jazz2.orc
wii-w1.sco -B 2000
PortAudio real-time audio module for Csound
0dBFS level = 32768.0
Csound version 5.15 (double samples) Jan 17 2012
libsndfile-1.0.25
orchname:  wii_jazz2.orc
graph init 
rtaudio: JACK module enabled
orch compiler:
        instr   9
        instr   10
internal message: strsav: buffer length now 1016
internal message: strsav: buffer length now 1016
        instr   11
        instr   evinst
        instr   99
sorting score ...
        ... done
Csound version 5.15 (double samples) Jan 17 2012
displays suppressed
0dBFS level = 32768.0
orch now loaded
audio buffered in 256 sample-frame blocks
writing 512 sample blks of 64-bit floats to dac 
SECTION 1:
55 elements in 2s3s.ftab
wiiuse v0.14.0 loaded.
  Fork at http://github.com/rpavlik/wiiuse
  Original By: Michael Laforest  http://wiiuse.net
[INFO] Found 1 bluetooth device(s).
[INFO] Found wiimote (00:17:AB:39:83:9B) [id 1].
[INFO] Connected to wiimote [id 1].
PERF ERROR in instr 10: wiimote 0 does not exist
kleft_0 wiidata 9       0
   note aborted
^CCsound tidy up: Interrompre
Early return from csoundPerform().
inactive allocs returned to freespace
end of score.              overall amps:      0.0      0.0
           overall samples out of range:        0        0
1 errors in performance
358 512 sample blks of 64-bit floats written to dac


-----

Olivier Baudouin, PhD 
http://olivierbaudouin.com 
MINT-OMF 
Paris-Sorbonne

--
View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5152374.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I have been using these opcodes with wiiuse v0.12 as fixed for ages.  No
problem at all.

What does your orc say?  Mine says

  i1  wiiconnect    10,1                        ; One wii at present
            ;; Organ controls
            ;; 1) Amplitude
            wiirange    $WII_NUNCHUK_PITCH., -50, -2, 0
  ka        wiidata     $WII_NUNCHUK_PITCH., 0
            FLsetVal    ka-gk1, ka, gih1
 ....
an dthe score


i10 0 300


More detail please.

==John ff
> Hello,
>
> I tried your code, the compilation is OK, but I get a wiimote connection
> error (see below). I also get the same error with other csd (wii opcodes).
>
> My question is: why I can't connect my wiimote (+ nunchuk) with my system,
> while other linux users can do that?
>
> Lot of mistakes with Linux tools as Cwiid, wminput, bluedevil.
>
> Thanks!
>
> ---------------------------------
> Wiiuse version 0.14 (compilation OK)
> Bluez without wiimote plugin
> Kernel without last wiimote module




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I use this csd (and the result is displayed on my previous post):





-+rtaudio=jack
-B 2000
-b 500
-odac
-d



sr = 44100
nchnls = 2
ksmps = 100

#define WII_BUTTONS    #  0 # ; retourne une combinaison de bits
représentant tous les boutons enfoncés.

#define WII_TWO    # 1  # ; retourne 1 si le bouton vient d'être enfoncé, 0
sinon.

#define WII_ONE    # 2  # ; comme ci-dessus.

#define WII_B    #  3 # ; comme ci-dessus.

#define WII_A    #  4 # ; comme ci-dessus.

#define WII_MINUS    #  5 # ; comme ci-dessus.

#define WII_HOME    #  8 # ; comme ci-dessus.

#define WII_LEFT    #  9 # ; comme ci-dessus.

#define WII_RIGHT    # 10  # ; comme ci-dessus.

#define WII_DOWN    # 11  # ; comme ci-dessus.

#define WII_UP    #  12 # ; comme ci-dessus.

#define WII_PLUS    # 13  # ; comme ci-dessus.

; Si le numéro du contrôle vaut 100 plus un de ces codes de bouton, 
;   l'état courant du bouton est retourné.
;     Les macros telles que WII_S_TWO, etc sont définies pour cela.
; Si le numéro du contrôle vaut 200 plus un de ces codes de bouton,
;   la valeur retournée est 1 si le bouton est enfoncé, et 0 sinon.
;     Les macros telles que WII_H_TWO, etc sont définies pour cela.
; Si le numéro du contrôle vaut 300 plus un de ces codes de bouton,
;   la valeur retournée est 1 si le bouton vient d'être relâché, et 0 sinon.
;     Les macros telles que WII_R_TWO, etc sont définies pour cela.

#define WII_PITCH    # 20  # ; L'inclinaison de la Wiimote. La valeur en
degrés est comprise entre -90 et +90, à moins d'une modification de
l'intervalle par un appel à wiirange.

#define WII_ROLL    # 21  # ; La rotation de la Wiimote. La valeur en degrés
est comprise entre -90 et +90, à moins d'une modification de l'intervalle
par un appel à wiirange.

#define WII_FORCE_X    #  23 # ; La force appliquée à la Wiimote selon les
trois axes.

#define WII_FORCE_Y    # 24  # ;

#define WII_FORCE_Z    # 25  # ;

#define WII_FORCE_TOTAL    #  26 # ; L'intensité totale de la force
appliquée à la Wiimote.

#define WII_BATTERY    #  27 # ; Le pourcentage de la charge des piles
restante.

#define WII_NUNCHUK_ANG    # 28  # ; L'angle du joystick du nunchuk en
degrés.

#define WII_NUNCHUK_MAG    # 29  # ; Le déplacement du joystick du nunchuk
par rapport à sa position centrale.

#define WII_NUNCHUK_PITCH    # 30  # ; L'inclinaison du nunchuk en degrés,
comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
appel à wiirange.

#define WII_NUNCHUK_ROLL    #  31 # ; La rotation du nunchuk en degrés,
comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
appel à wiirange.

#define WII_NUNCHUK_Z    # 33  #; L'état du bouton Z du nunchuk.

#define WII_NUNCHUK_C    #  34 #; L'état du bouton C du nunchuk.

#define WII_IR1_X    #  35 #; Le pointage infrarouge de la Wiimote.

#define WII_IR1_Y    # 36  #;

#define WII_IR1_Z    #  37 #;

#define WII_RUMBLE    #  3 #;

instr 1  

i1  wiiconnect 20

kCtrl1	wiidata $WII_ROLL
;kCtrl2	wiidata $WII_PITCH
;kCtrl3	wiidata $WII_NUNCHUK_Z
;print i1
;printk2  kCtrl2
printk2 kCtrl1
;printk2  kCtrl3

endin




i1 0 3000


 

-----

Olivier Baudouin, PhD 
http://olivierbaudouin.com 
MINT-OMF 
Paris-Sorbonne

--
View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5152564.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

i'll check this when i get home, i haven't run this against the latest
sources. does your fork of wiiuse change the enumeration of wii devices
from beginning at 0 to beginning at 1?

i would check to see if changing $WIIINIT(0)  to $WIIINIT(1) and
$WIIINSTR(0) to $WIIINSTR(1) fixes anything.

i'll test later tonight if i can.
k.

On 01/17/2012 02:00 PM, obaudouin wrote:
> I use this csd (and the result is displayed on my previous post):
>
>
>
> 
> 
> -+rtaudio=jack
> -B 2000
> -b 500
> -odac
> -d
>
> 
> 
> sr = 44100
> nchnls = 2
> ksmps = 100
>
> #define WII_BUTTONS    #  0 # ; retourne une combinaison de bits
> représentant tous les boutons enfoncés.
>
> #define WII_TWO    # 1  # ; retourne 1 si le bouton vient d'être enfoncé, 0
> sinon.
>
> #define WII_ONE    # 2  # ; comme ci-dessus.
>
> #define WII_B    #  3 # ; comme ci-dessus.
>
> #define WII_A    #  4 # ; comme ci-dessus.
>
> #define WII_MINUS    #  5 # ; comme ci-dessus.
>
> #define WII_HOME    #  8 # ; comme ci-dessus.
>
> #define WII_LEFT    #  9 # ; comme ci-dessus.
>
> #define WII_RIGHT    # 10  # ; comme ci-dessus.
>
> #define WII_DOWN    # 11  # ; comme ci-dessus.
>
> #define WII_UP    #  12 # ; comme ci-dessus.
>
> #define WII_PLUS    # 13  # ; comme ci-dessus.
>
> ; Si le numéro du contrôle vaut 100 plus un de ces codes de bouton, 
> ;   l'état courant du bouton est retourné.
> ;     Les macros telles que WII_S_TWO, etc sont définies pour cela.
> ; Si le numéro du contrôle vaut 200 plus un de ces codes de bouton,
> ;   la valeur retournée est 1 si le bouton est enfoncé, et 0 sinon.
> ;     Les macros telles que WII_H_TWO, etc sont définies pour cela.
> ; Si le numéro du contrôle vaut 300 plus un de ces codes de bouton,
> ;   la valeur retournée est 1 si le bouton vient d'être relâché, et 0 sinon.
> ;     Les macros telles que WII_R_TWO, etc sont définies pour cela.
>
> #define WII_PITCH    # 20  # ; L'inclinaison de la Wiimote. La valeur en
> degrés est comprise entre -90 et +90, à moins d'une modification de
> l'intervalle par un appel à wiirange.
>
> #define WII_ROLL    # 21  # ; La rotation de la Wiimote. La valeur en degrés
> est comprise entre -90 et +90, à moins d'une modification de l'intervalle
> par un appel à wiirange.
>
> #define WII_FORCE_X    #  23 # ; La force appliquée à la Wiimote selon les
> trois axes.
>
> #define WII_FORCE_Y    # 24  # ;
>
> #define WII_FORCE_Z    # 25  # ;
>
> #define WII_FORCE_TOTAL    #  26 # ; L'intensité totale de la force
> appliquée à la Wiimote.
>
> #define WII_BATTERY    #  27 # ; Le pourcentage de la charge des piles
> restante.
>
> #define WII_NUNCHUK_ANG    # 28  # ; L'angle du joystick du nunchuk en
> degrés.
>
> #define WII_NUNCHUK_MAG    # 29  # ; Le déplacement du joystick du nunchuk
> par rapport à sa position centrale.
>
> #define WII_NUNCHUK_PITCH    # 30  # ; L'inclinaison du nunchuk en degrés,
> comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
> appel à wiirange.
>
> #define WII_NUNCHUK_ROLL    #  31 # ; La rotation du nunchuk en degrés,
> comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
> appel à wiirange.
>
> #define WII_NUNCHUK_Z    # 33  #; L'état du bouton Z du nunchuk.
>
> #define WII_NUNCHUK_C    #  34 #; L'état du bouton C du nunchuk.
>
> #define WII_IR1_X    #  35 #; Le pointage infrarouge de la Wiimote.
>
> #define WII_IR1_Y    # 36  #;
>
> #define WII_IR1_Z    #  37 #;
>
> #define WII_RUMBLE    #  3 #;
>
> instr 1  
>
> i1  wiiconnect 20
>
> kCtrl1	wiidata $WII_ROLL
> ;kCtrl2	wiidata $WII_PITCH
> ;kCtrl3	wiidata $WII_NUNCHUK_Z
> ;print i1
> ;printk2  kCtrl2
> printk2 kCtrl1
> ;printk2  kCtrl3
>
> endin
>
> 
> 
>
> i1 0 3000
>
> 
>  
>
> -----
>
> Olivier Baudouin, PhD 
> http://olivierbaudouin.com 
> MINT-OMF 
> Paris-Sorbonne
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5152564.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I tried with Wiiuse 0.12 (compilation OK + l.174 adding "memset(&addr, 0,
sizeof addr);").

The wiimote seems recognized, but data can't be read.

This problem is caused by Wiiuse, I think, not by Csound. 

With wiiuse-example, the nunchuk is never detected, and it is difficult to
obtain a correct connexion with the Wiimote.

That is pesky!


------------------------------------------------------------------------
STDOUT
------------------------------------------------------------------------
wiiuse v0.12 loaded.
  By: Michael Laforest 
  http://wiiuse.net  http://wiiuse.sf.net
[INFO] Found 1 bluetooth device(s).
[INFO] Found wiimote (00:17:AB:39:83:9B) [id 1].
[INFO] Connected to wiimote [id 1].
 i1     0.00000
WARNING: rtjack: xrun in real time audio
[WARNING] Unable to read data - address is for write-only registers.
[WARNING] Received data packet when no request was made.
[WARNING] Received data packet when no request was made.
^CCsound tidy up: Interrompre
----------------------------------------------------------------------
CSD
----------------------------------------------------------------------



-+rtaudio=jack
-B 4000
-b 2000
-odac
-d



sr = 44100
nchnls = 2
ksmps = 400

#define WII_BUTTONS    #  0 # ; retourne une combinaison de bits
représentant tous les boutons enfoncés.

#define WII_TWO    # 1  # ; retourne 1 si le bouton vient d'être enfoncé, 0
sinon.

#define WII_ONE    # 2  # ; comme ci-dessus.

#define WII_B    #  3 # ; comme ci-dessus.

#define WII_A    #  4 # ; comme ci-dessus.

#define WII_MINUS    #  5 # ; comme ci-dessus.

#define WII_HOME    #  8 # ; comme ci-dessus.

#define WII_LEFT    #  9 # ; comme ci-dessus.

#define WII_RIGHT    # 10  # ; comme ci-dessus.

#define WII_DOWN    # 11  # ; comme ci-dessus.

#define WII_UP    #  12 # ; comme ci-dessus.

#define WII_PLUS    # 13  # ; comme ci-dessus.

; Si le numéro du contrôle vaut 100 plus un de ces codes de bouton, 
;   l'état courant du bouton est retourné.
;     Les macros telles que WII_S_TWO, etc sont définies pour cela.
; Si le numéro du contrôle vaut 200 plus un de ces codes de bouton,
;   la valeur retournée est 1 si le bouton est enfoncé, et 0 sinon.
;     Les macros telles que WII_H_TWO, etc sont définies pour cela.
; Si le numéro du contrôle vaut 300 plus un de ces codes de bouton,
;   la valeur retournée est 1 si le bouton vient d'être relâché, et 0 sinon.
;     Les macros telles que WII_R_TWO, etc sont définies pour cela.

#define WII_PITCH    # 20  # ; L'inclinaison de la Wiimote. La valeur en
degrés est comprise entre -90 et +90, à moins d'une modification de
l'intervalle par un appel à wiirange.

#define WII_ROLL    # 21  # ; La rotation de la Wiimote. La valeur en degrés
est comprise entre -90 et +90, à moins d'une modification de l'intervalle
par un appel à wiirange.

#define WII_FORCE_X    #  23 # ; La force appliquée à la Wiimote selon les
trois axes.

#define WII_FORCE_Y    # 24  # ;

#define WII_FORCE_Z    # 25  # ;

#define WII_FORCE_TOTAL    #  26 # ; L'intensité totale de la force
appliquée à la Wiimote.

#define WII_BATTERY    #  27 # ; Le pourcentage de la charge des piles
restante.

#define WII_NUNCHUK_ANG    # 28  # ; L'angle du joystick du nunchuk en
degrés.

#define WII_NUNCHUK_MAG    # 29  # ; Le déplacement du joystick du nunchuk
par rapport à sa position centrale.

#define WII_NUNCHUK_PITCH    # 30  # ; L'inclinaison du nunchuk en degrés,
comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
appel à wiirange.

#define WII_NUNCHUK_ROLL    #  31 # ; La rotation du nunchuk en degrés,
comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
appel à wiirange.

#define WII_NUNCHUK_Z    # 33  #; L'état du bouton Z du nunchuk.

#define WII_NUNCHUK_C    #  34 #; L'état du bouton C du nunchuk.

#define WII_IR1_X    #  35 #; Le pointage infrarouge de la Wiimote.

#define WII_IR1_Y    # 36  #;

#define WII_IR1_Z    #  37 #;

#define WII_RUMBLE    #  3 #;

instr 1

i1  wiiconnect 10

k1	wiidata $WII_PITCH

printk2 k1

endin




i1 0 3000


 


-----

Olivier Baudouin, PhD 
http://olivierbaudouin.com 
MINT-OMF 
Paris-Sorbonne

--
View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5152995.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

i can not reproduce the wiiuse bug here using my rig consisting of:
 old wiimotes without motion plus
 belkin f87013xx1 usb bluetooth dongle
 sena ud100 bluetooth dongle

these work fine, though the new parser chokes on wii_jazz2.orc
********************
* USING NEW PARSER *
********************
defining argument MOTE as...#0#
defining argument MOTE as...#0#
Too many file/macros

i had trouble with another cheeper no name usb bluetooth radio which i
eventually ditched. it would scan just fine but would fail to pair. i'm
not sure it implemented all the features of the bluetooth protocol. i
tested it with apple keyboard and mouse as well. it was very frustrating.

k.
 
On 01/17/2012 04:42 PM, obaudouin wrote:
> I tried with Wiiuse 0.12 (compilation OK + l.174 adding "memset(&addr, 0,
> sizeof addr);").
>
> The wiimote seems recognized, but data can't be read.
>
> This problem is caused by Wiiuse, I think, not by Csound. 
>
> With wiiuse-example, the nunchuk is never detected, and it is difficult to
> obtain a correct connexion with the Wiimote.
>
> That is pesky!
>
>
> ------------------------------------------------------------------------
> STDOUT
> ------------------------------------------------------------------------
> wiiuse v0.12 loaded.
>   By: Michael Laforest 
>   http://wiiuse.net  http://wiiuse.sf.net
> [INFO] Found 1 bluetooth device(s).
> [INFO] Found wiimote (00:17:AB:39:83:9B) [id 1].
> [INFO] Connected to wiimote [id 1].
>  i1     0.00000
> WARNING: rtjack: xrun in real time audio
> [WARNING] Unable to read data - address is for write-only registers.
> [WARNING] Received data packet when no request was made.
> [WARNING] Received data packet when no request was made.
> ^CCsound tidy up: Interrompre
> ----------------------------------------------------------------------
> CSD
> ----------------------------------------------------------------------
>
> 
> 
> -+rtaudio=jack
> -B 4000
> -b 2000
> -odac
> -d
>
> 
> 
> sr = 44100
> nchnls = 2
> ksmps = 400
>
> #define WII_BUTTONS    #  0 # ; retourne une combinaison de bits
> représentant tous les boutons enfoncés.
>
> #define WII_TWO    # 1  # ; retourne 1 si le bouton vient d'être enfoncé, 0
> sinon.
>
> #define WII_ONE    # 2  # ; comme ci-dessus.
>
> #define WII_B    #  3 # ; comme ci-dessus.
>
> #define WII_A    #  4 # ; comme ci-dessus.
>
> #define WII_MINUS    #  5 # ; comme ci-dessus.
>
> #define WII_HOME    #  8 # ; comme ci-dessus.
>
> #define WII_LEFT    #  9 # ; comme ci-dessus.
>
> #define WII_RIGHT    # 10  # ; comme ci-dessus.
>
> #define WII_DOWN    # 11  # ; comme ci-dessus.
>
> #define WII_UP    #  12 # ; comme ci-dessus.
>
> #define WII_PLUS    # 13  # ; comme ci-dessus.
>
> ; Si le numéro du contrôle vaut 100 plus un de ces codes de bouton, 
> ;   l'état courant du bouton est retourné.
> ;     Les macros telles que WII_S_TWO, etc sont définies pour cela.
> ; Si le numéro du contrôle vaut 200 plus un de ces codes de bouton,
> ;   la valeur retournée est 1 si le bouton est enfoncé, et 0 sinon.
> ;     Les macros telles que WII_H_TWO, etc sont définies pour cela.
> ; Si le numéro du contrôle vaut 300 plus un de ces codes de bouton,
> ;   la valeur retournée est 1 si le bouton vient d'être relâché, et 0 sinon.
> ;     Les macros telles que WII_R_TWO, etc sont définies pour cela.
>
> #define WII_PITCH    # 20  # ; L'inclinaison de la Wiimote. La valeur en
> degrés est comprise entre -90 et +90, à moins d'une modification de
> l'intervalle par un appel à wiirange.
>
> #define WII_ROLL    # 21  # ; La rotation de la Wiimote. La valeur en degrés
> est comprise entre -90 et +90, à moins d'une modification de l'intervalle
> par un appel à wiirange.
>
> #define WII_FORCE_X    #  23 # ; La force appliquée à la Wiimote selon les
> trois axes.
>
> #define WII_FORCE_Y    # 24  # ;
>
> #define WII_FORCE_Z    # 25  # ;
>
> #define WII_FORCE_TOTAL    #  26 # ; L'intensité totale de la force
> appliquée à la Wiimote.
>
> #define WII_BATTERY    #  27 # ; Le pourcentage de la charge des piles
> restante.
>
> #define WII_NUNCHUK_ANG    # 28  # ; L'angle du joystick du nunchuk en
> degrés.
>
> #define WII_NUNCHUK_MAG    # 29  # ; Le déplacement du joystick du nunchuk
> par rapport à sa position centrale.
>
> #define WII_NUNCHUK_PITCH    # 30  # ; L'inclinaison du nunchuk en degrés,
> comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
> appel à wiirange.
>
> #define WII_NUNCHUK_ROLL    #  31 # ; La rotation du nunchuk en degrés,
> comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
> appel à wiirange.
>
> #define WII_NUNCHUK_Z    # 33  #; L'état du bouton Z du nunchuk.
>
> #define WII_NUNCHUK_C    #  34 #; L'état du bouton C du nunchuk.
>
> #define WII_IR1_X    #  35 #; Le pointage infrarouge de la Wiimote.
>
> #define WII_IR1_Y    # 36  #;
>
> #define WII_IR1_Z    #  37 #;
>
> #define WII_RUMBLE    #  3 #;
>
> instr 1
>
> i1  wiiconnect 10
>
> k1	wiidata $WII_PITCH
>
> printk2 k1
>
> endin
>
> 
> 
>
> i1 0 3000
>
> 
>  
>
>
> -----
>
> Olivier Baudouin, PhD 
> http://olivierbaudouin.com 
> MINT-OMF 
> Paris-Sorbonne
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5152995.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Wiimote + Nunchuk: Nitendo RV-CNT-01 (with motion+)
Bluetooth dongle: Cambridge Silicon Radio, Ltd



-----

Olivier Baudouin, PhD 
http://olivierbaudouin.com 
MINT-OMF 
Paris-Sorbonne

--
View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5154060.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

*add this line

    addr.l2_cid = 0;*

---> it doesn't solve the problem...



-----

Olivier Baudouin, PhD 
http://olivierbaudouin.com 
MINT-OMF 
Paris-Sorbonne

--
View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5154300.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Fedora 16:

Linux fixe.lan 3.0.14-1.rt31.1.fc16.ccrma.x86_64.rt #1 SMP PREEMPT RT Thu
Dec 22 09:51:53 PST 2011 x86_64 x86_64 x86_64 GNU/Linux

-----

Olivier Baudouin, PhD 
http://olivierbaudouin.com 
MINT-OMF 
Paris-Sorbonne

--
View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5154352.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Olivier,

I've tested your csd on my system (Ubuntu 11.04, csound 5.15 built today from git, wwiuse v0.12) and I got the following output with one init error:

PortAudio real-time audio module for Csound
PortMIDI real time MIDI plugin for Csound
virtual_keyboard real time MIDI plugin for Csound
0dBFS level = 32768.0
Csound version 5.15 (double samples) Jan 18 2012
libsndfile-1.0.23
Reading options from $HOME/.csoundrc
UnifiedCSD:  wii-ob.csd
STARTING FILE
Creating options
Creating orchestra
Creating score
rtaudio: ALSA module enabled
rtmidi: PortMIDI module enabled
RAWWAVE_PATH: /usr/local/share/csound/rawwaves/
********************
* USING NEW PARSER *
********************
Parsing successful!
sorting score ...
    ... done
Csound version 5.15 (double samples) Jan 18 2012
displays suppressed
0dBFS level = 32768.0
orch now loaded
audio buffered in 500 sample-frame blocks
writing 1000 sample blks of 64-bit floats to dac
SECTION 1:
wiiuse v0.12 loaded.
  By: Michael Laforest <thepara[at]gmail{dot}com>
  http://wiiuse.net  http://wiiuse.sf.net
[INFO] Found 1 bluetooth device(s).
[INFO] Found wiimote (00:22:AA:8F:48:21) [id 1].
connect() output sock: L'h?te cible est arr?t? ou en panne
INIT ERROR in instr 1: unable to open wiimote

i1    wiiconnect    20    0   
      B  0.000 - note deleted.  i1 had 1 init errors
Score finished in csoundPerform().
inactive allocs returned to freespace
end of score.           overall amps:      0.0      0.0
       overall samples out of range:        0        0
1 errors in performance
0 1000 sample blks of 64-bit floats written to dac

I then changed the line

i1 wiiconnect 20

to

i1 wiiconnect 3, 1

and it worked fine.

François

Le 17 janvier 2012 20:00, obaudouin <olivierbaudouin@gmail.com> a écrit :

I use this csd (and the result is displayed on my previous post):



<CsoundSynthesizer>
<CsOptions>
-+rtaudio=jack
-B 2000
-b 500
-odac
-d

</CsOptions>
<CsInstruments>
sr = 44100
nchnls = 2
ksmps = 100

#define WII_BUTTONS    #  0 # ; retourne une combinaison de bits
représentant tous les boutons enfoncés.

#define WII_TWO    # 1  # ; retourne 1 si le bouton vient d'être enfoncé, 0
sinon.

#define WII_ONE    # 2  # ; comme ci-dessus.

#define WII_B    #  3 # ; comme ci-dessus.

#define WII_A    #  4 # ; comme ci-dessus.

#define WII_MINUS    #  5 # ; comme ci-dessus.

#define WII_HOME    #  8 # ; comme ci-dessus.

#define WII_LEFT    #  9 # ; comme ci-dessus.

#define WII_RIGHT    # 10  # ; comme ci-dessus.

#define WII_DOWN    # 11  # ; comme ci-dessus.

#define WII_UP    #  12 # ; comme ci-dessus.

#define WII_PLUS    # 13  # ; comme ci-dessus.

; Si le numéro du contrôle vaut 100 plus un de ces codes de bouton,
;   l'état courant du bouton est retourné.
;     Les macros telles que WII_S_TWO, etc sont définies pour cela.
; Si le numéro du contrôle vaut 200 plus un de ces codes de bouton,
;   la valeur retournée est 1 si le bouton est enfoncé, et 0 sinon.
;     Les macros telles que WII_H_TWO, etc sont définies pour cela.
; Si le numéro du contrôle vaut 300 plus un de ces codes de bouton,
;   la valeur retournée est 1 si le bouton vient d'être relâché, et 0 sinon.
;     Les macros telles que WII_R_TWO, etc sont définies pour cela.

#define WII_PITCH    # 20  # ; L'inclinaison de la Wiimote. La valeur en
degrés est comprise entre -90 et +90, à moins d'une modification de
l'intervalle par un appel à wiirange.

#define WII_ROLL    # 21  # ; La rotation de la Wiimote. La valeur en degrés
est comprise entre -90 et +90, à moins d'une modification de l'intervalle
par un appel à wiirange.

#define WII_FORCE_X    #  23 # ; La force appliquée à la Wiimote selon les
trois axes.

#define WII_FORCE_Y    # 24  # ;

#define WII_FORCE_Z    # 25  # ;

#define WII_FORCE_TOTAL    #  26 # ; L'intensité totale de la force
appliquée à la Wiimote.

#define WII_BATTERY    #  27 # ; Le pourcentage de la charge des piles
restante.

#define WII_NUNCHUK_ANG    # 28  # ; L'angle du joystick du nunchuk en
degrés.

#define WII_NUNCHUK_MAG    # 29  # ; Le déplacement du joystick du nunchuk
par rapport à sa position centrale.

#define WII_NUNCHUK_PITCH    # 30  # ; L'inclinaison du nunchuk en degrés,
comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
appel à wiirange.

#define WII_NUNCHUK_ROLL    #  31 # ; La rotation du nunchuk en degrés,
comprise entre -90 et +90, à moins d'une modification de l'intervalle par un
appel à wiirange.

#define WII_NUNCHUK_Z    # 33  #; L'état du bouton Z du nunchuk.

#define WII_NUNCHUK_C    #  34 #; L'état du bouton C du nunchuk.

#define WII_IR1_X    #  35 #; Le pointage infrarouge de la Wiimote.

#define WII_IR1_Y    # 36  #;

#define WII_IR1_Z    #  37 #;

#define WII_RUMBLE    #  3 #;

instr 1

i1  wiiconnect 20

kCtrl1  wiidata $WII_ROLL
;kCtrl2 wiidata $WII_PITCH
;kCtrl3 wiidata $WII_NUNCHUK_Z
;print i1
;printk2  kCtrl2
printk2 kCtrl1
;printk2  kCtrl3

endin

</CsInstruments>
<CsScore>

i1 0 3000

</CsScore>
</CsoundSynthesizer>

-----

Olivier Baudouin, PhD
http://olivierbaudouin.com
MINT-OMF
Paris-Sorbonne

--

View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5152564.html

Sent from the Csound - General mailing list archive at Nabble.com.

Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thank you François, it's better with a short time recognition. But wiiuse
never detect the nunchuk (extension = 0 in wiuuse-example).



-----

Olivier Baudouin, PhD 
http://olivierbaudouin.com 
MINT-OMF 
Paris-Sorbonne

--
View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5155456.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I got conflicting results.  First attempt worked perfectly; subsequent
failed after connect.  I will check that I j=have the memset fix

> Thank you François, it's better with a short time recognition. But wiiuse
> never detect the nunchuk (extension = 0 in wiuuse-example).
>
>
>
> -----
>
> Olivier Baudouin, PhD
> http://olivierbaudouin.com
> MINT-OMF
> Paris-Sorbonne
>
> --
> View this message in context:
> http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5155456.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

If I reducx ethe timeout to 20 it runs as below

iiuse v0.12 loaded.
  By: Michael Laforest 
  http://wiiuse.net  http://wiiuse.sf.net
[INFO] Found 1 bluetooth device(s).
[INFO] Found wiimote (00:19:1D:B5:B3:D4) [id 1].
[INFO] Connected to wiimote [id 1].
 i1     0.00000
WARNING: Nunchuk inserted.

 i1     0.15418
 i1     0.29757
....

I suspect the wii is switching off before the wiicomnnect completes

==John



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

With the csd below, the nunchunk is correctly detected on my system:



   -d -o dac



sr      = 48000
kr      = 120
ksmps   = 400
nchnls  = 2
0dbfs   = 1.0

#define WII_B       #3#
#define WII_A       #4#
#define WII_PITCH   #20#
#define WII_ROLL    #21#
#define WII_NUNCHUK_PITCH #30#
#define WII_NUNCHUK_ROLL  #31#

instr 1
   i1    wiiconnect  3, 1
         wiirange    $WII_PITCH., 100, 8000
         wiirange    $WII_ROLL., 0, 1
         wiirange    $WII_NUNCHUK_ROLL., 0, 1
   kb    wiidata     $WII_B.
   if (kb == 1) then
     event "i", 2, 0, 1
   endif
   gkfc  wiidata     $WII_PITCH.
   gkres wiidata     $WII_ROLL.
   gkpan wiidata     $WII_NUNCHUK_ROLL.
   if (gkfc < 100) then
     gkfc = 100
   elseif (gkfc > 8000) then
     gkfc = 8000
   endif
   if (gkres < 0) then
     gkres = 0
   elseif (gkres > 1) then
     gkres = 1
   endif
   if (gkpan < 0) then
     gkpan = 0
   elseif (gkpan > 1) then
     gkpan = 1
   endif
endin

instr 2
   idur  = p3

   kenv   line    1, p3, 0
   a1     rand    1.0
   a2     moogvcf a1, gkfc, gkres
   al, ar pan2    kenv*a2, 1-gkpan
          outs    al, ar
endin



i1 0 300





Le 18/01/2012 18:48, obaudouin a écrit :
> Thank you François, it's better with a short time recognition. But wiiuse
> never detect the nunchuk (extension = 0 in wiuuse-example).
>
>
>
> -----
>
> Olivier Baudouin, PhD
> http://olivierbaudouin.com
> MINT-OMF
> Paris-Sorbonne
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/wiimote-instrument-tp5054313p5155456.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

wiimotes use bluetooth and so far I have not managed to understand the
Apple bluetooth stack which differs from Linux and Windows.

So I think the simple nswer is that it does not yet work and we need a
mac-bluetooth wallah

But they are a cheap interface....

==John ff
> Sorry to butt in, but this seems an appropriate place to ask this
> question:
> Do the wiimote opcodes work on OS X? And is there anything I need to
> consider when I buy a wiimote (are there different ones, for example)? I
> just looked them up on amazon, and they're a lot cheaper than I thought.
> And just thinking about the possibilities here makes me want to get one
> immediately...
>
>




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Oh :( Doesn't Apple provide a framework for bluetooth connectivity?

On Wed, Jan 18, 2012 at 12:04 PM, <jpff@cs.bath.ac.uk> wrote:

wiimotes use bluetooth and so far I have not managed to understand the
Apple bluetooth stack which differs from Linux and Windows.

So I think the simple nswer is that it does not yet work and we need a
mac-bluetooth wallah

But they are a cheap interface....

==John ff

> Sorry to butt in, but this seems an appropriate place to ask this
> question:
> Do the wiimote opcodes work on OS X? And is there anything I need to
> consider when I buy a wiimote (are there different ones, for example)? I
> just looked them up on amazon, and they're a lot cheaper than I thought.
> And just thinking about the possibilities here makes me want to get one
> immediately...
>
>

Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Oh :( Doesn't Apple provide a framework for bluetooth connectivity?

On Wed, Jan 18, 2012 at 12:04 PM, <jpff@cs.bath.ac.uk> wrote:

wiimotes use bluetooth and so far I have not managed to understand the
Apple bluetooth stack which differs from Linux and Windows.

So I think the simple nswer is that it does not yet work and we need a
mac-bluetooth wallah

But they are a cheap interface....

==John ff

> Sorry to butt in, but this seems an appropriate place to ask this
> question:
> Do the wiimote opcodes work on OS X? And is there anything I need to
> consider when I buy a wiimote (are there different ones, for example)? I
> just looked them up on amazon, and they're a lot cheaper than I thought.
> And just thinking about the possibilities here makes me want to get one
> immediately...
>
>

Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks. I'll see if I can find more info on that. Sounds like a latency-prone approach, though...

On Wed, Jan 18, 2012 at 12:13 PM, Kelly Hirai <khirai@ongaku.isa-geek.net> wrote:

i heard rumors you can get osc signals from it in mac using some other software. you'd have to collect them using the osc opcodes in csound.

On 01/18/12 15:08, Alex Weiss wrote:

Oh :( Doesn't Apple provide a framework for bluetooth connectivity?

On Wed, Jan 18, 2012 at 12:04 PM, <jpff@cs.bath.ac.uk> wrote:

wiimotes use bluetooth and so far I have not managed to understand the
Apple bluetooth stack which differs from Linux and Windows.

So I think the simple nswer is that it does not yet work and we need a
mac-bluetooth wallah

But they are a cheap interface....

==John ff

> Sorry to butt in, but this seems an appropriate place to ask this
> question:
> Do the wiimote opcodes work on OS X? And is there anything I need to
> consider when I buy a wiimote (are there different ones, for example)? I
> just looked them up on amazon, and they're a lot cheaper than I thought.
> And just thinking about the possibilities here makes me want to get one
> immediately...
>
>

Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Great! Last question: Do I need to get a wiimote or a wiimote plus?

On Wed, Jan 18, 2012 at 12:18 PM, Victor <Victor.Lazzarini@nuim.ie> wrote:

There is no latency problem with this.

On 18 Jan 2012, at 20:15, Alex Weiss <alexweiss86@gmail.com> wrote:

Thanks. I'll see if I can find more info on that. Sounds like a latency-prone approach, though...

On Wed, Jan 18, 2012 at 12:13 PM, Kelly Hirai <khirai@ongaku.isa-geek.net> wrote:

i heard rumors you can get osc signals from it in mac using some other software. you'd have to collect them using the osc opcodes in csound.

On 01/18/12 15:08, Alex Weiss wrote:

Oh :( Doesn't Apple provide a framework for bluetooth connectivity?

On Wed, Jan 18, 2012 at 12:04 PM, <jpff@cs.bath.ac.uk> wrote:

wiimotes use bluetooth and so far I have not managed to understand the
Apple bluetooth stack which differs from Linux and Windows.

So I think the simple nswer is that it does not yet work and we need a
mac-bluetooth wallah

But they are a cheap interface....

==John ff

> Sorry to butt in, but this seems an appropriate place to ask this
> question:
> Do the wiimote opcodes work on OS X? And is there anything I need to
> consider when I buy a wiimote (are there different ones, for example)? I
> just looked them up on amazon, and they're a lot cheaper than I thought.
> And just thinking about the possibilities here makes me want to get one
> immediately...
>
>

Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

This change will/may confuse the diagnostics.  63 is magic, so I think I
need to think of a better plan.  Did not reaise that peopl eused so many
macros
  Give me some time.

==John ff

>> these work fine, though the new parser chokes on wii_jazz2.orc
>> ********************
>> * USING NEW PARSER *
>> ********************
>> defining argument MOTE as...#0#
>> defining argument MOTE as...#0#
>> Too many file/macros
>
> I don't have a wii to try but I can help Kelly with
> 'Too many file/macros' error. It's a problem with
> diagnostics (git), but you know the code and here
> is a dirty trick:
>
>   Engine/csound_orc_compile.c:1873
>
> replace
>
>   if (n=63) ...
>
> with
>
>   if (n=63) free(filedir[--n]);
>
> It's provisional but so you can try wii_jazz2.orc (I hope)
>
> tito
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

there are only 2 function style macro definitions and a single
instantiation for each in that orc. if i could find the new parser debug
flag, i would send more verbose output.

k.

On 01/18/12 15:45, jpff@cs.bath.ac.uk wrote:
> This change will/may confuse the diagnostics.  63 is magic, so I think I
> need to think of a better plan.  Did not reaise that peopl eused so many
> macros
>   Give me some time.
>
> ==John ff
>
>>> these work fine, though the new parser chokes on wii_jazz2.orc
>>> ********************
>>> * USING NEW PARSER *
>>> ********************
>>> defining argument MOTE as...#0#
>>> defining argument MOTE as...#0#
>>> Too many file/macros
>> I don't have a wii to try but I can help Kelly with
>> 'Too many file/macros' error. It's a problem with
>> diagnostics (git), but you know the code and here
>> is a dirty trick:
>>
>>   Engine/csound_orc_compile.c:1873
>>
>> replace
>>
>>   if (n=63) ...
>>
>> with
>>
>>   if (n=63) free(filedir[--n]);
>>
>> It's provisional but so you can try wii_jazz2.orc (I hope)
>>
>> tito
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> 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 tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Victor,

What's the preferred wiimote to osc client program for Mac OS X? I've looked at OSCulator, but I'd prefer open software...

Alex

On Wed, Jan 18, 2012 at 12:15 PM, Victor <Victor.Lazzarini@nuim.ie> wrote:

I use a wiimote with osx all the time. You just need a wiimote to osc client program and then osc in csound.

On 18 Jan 2012, at 20:08, Alex Weiss <alexweiss86@gmail.com> wrote:

Oh :( Doesn't Apple provide a framework for bluetooth connectivity?

On Wed, Jan 18, 2012 at 12:04 PM, <jpff@cs.bath.ac.uk> wrote:

wiimotes use bluetooth and so far I have not managed to understand the
Apple bluetooth stack which differs from Linux and Windows.

So I think the simple nswer is that it does not yet work and we need a
mac-bluetooth wallah

But they are a cheap interface....

==John ff

> Sorry to butt in, but this seems an appropriate place to ask this
> question:
> Do the wiimote opcodes work on OS X? And is there anything I need to
> consider when I buy a wiimote (are there different ones, for example)? I
> just looked them up on amazon, and they're a lot cheaper than I thought.
> And just thinking about the possibilities here makes me want to get one
> immediately...
>
>

Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

-- 
--
http://luisantunespena.eu