Interfacing PD with the Arduino ... how?
i got a problem in uploading the file to the board. ( I have press play, same error found. When I press upload to I/O, below error found)
anyone can help?
thx
////////////////////////////
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:61: error: typedef 'callbackFunction' is initialized (use __typeof__ instead)
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:61: error: 'byte' was not declared in this scope
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:61: error: expected primary-expression before 'int'
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:64: error: typedef 'sysexCallbackFunction' is initialized (use __typeof__ instead)
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:64: error: 'byte' was not declared in this scope
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:64: error: 'byte' was not declared in this scope
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:64: error: 'byte' was not declared in this scope
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:64: error: 'argv' was not declared in this scope
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:81: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:81: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:86: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:87: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:88: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:90: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:91: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:91: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:91: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:95: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:95: error: 'callbackFunction' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:96: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:97: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:98: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:98: error: 'sysexCallbackFunction' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:98: error: 'void FirmataClass::attach(int, int)' cannot be overloaded
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:95: error: with 'void FirmataClass::attach(int, int)'
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:99: error: 'byte' has not been declared
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:104: error: 'byte' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:105: error: ISO C++ forbids declaration of 'byte' with no type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:105: error: expected ';' before '*' token
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:107: error: 'byte' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:108: error: 'byte' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:109: error: 'byte' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:110: error: 'byte' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:112: error: 'boolean' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:115: error: 'callbackFunction' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:116: error: 'callbackFunction' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:117: error: 'callbackFunction' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:118: error: 'callbackFunction' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:119: error: 'callbackFunction' does not name a type
/Applications/arduino-0012/hardware/libraries/Firmata/Firmata.h:122: error: 'sysexCallbackFunction' does not name a type
In function 'void setup()':
PD with arduino and IR sensors
Did you burn the Pduino (Firmata) firmware on there? It's needed to make the arduino pd patch work. After that, you can just send commands to it, instead of writing your code to the arduino. It's a serial interface for PD. It already has the baud set correctly.
To install it, copy the "Firmata" dir (inside Firmata-2.0beta in Pduino distro) to arduino/hardware/libraries. After that, open the arduino IDE, and go to Sketchbook/Examples/Library_Firmata/Standard_Firmata. Burn this to your Arduino.
See the attached patch for an example of what you are trying to do, once you get Firmata installed. On the hardware end, connect photodetector to power and pin2.
ALSA
Dunno what snd_pcm is returning there, but you should see a separate driver for the Layla24
like this
$ lsmod
snd-seq-midi 5152 0 (unused)
snd-virmidi 2080 0
snd-seq-virmidi 5128 0 [snd-virmidi]
snd-seq-midi-event 6240 0 [snd-seq-midi snd-seq-virmidi]
snd-seq 48784 0 [snd-seq-midi snd-seq-virmidi snd-seq-midi-event]
snd-layla24 149732 3 <--------*here*
snd-pcm 85860 2 [snd-layla24] <---and pcm is using it
You don't have to recompile kernel or anything, find a driver and use insmod
Apparently there's a utils package at Alsa Project website for the Echo Layla24 that sets up everything. Have you tried that one?
also, there's an ALSA Wiki up now that may help you
Write SD2 format
Don't think so Boonier - SD2 is a quite different format from .wav
So many lovely formats to choose from
http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?coll=0640&db=man&pth=/cat4
http://www.sonicspot.com/guide/fileformatlist.html
http://www.fileinfo.net/list/
http://www.fileinfo.net/filetypes/audio
http://www.digitalpreservation.gov/formats/fdd/sound_fdd.shtml
http://www.cnpbagwell.com/audio.html
Le Centre de Ressources Art Sensitif - Journées de formation Pure Data
Le Centre de Ressources Art Sensitif à Mains d'Oeuvres organise des ateliers et des journées de formation aux logiciels et matériels de gestion d'événements interactifs temps réel. Pour être tenu informé, inscrivez-vous à notre lettre d'information via le site Internet http://www.craslab.org
CALENDRIER
Journée Pure Data & Vidéo - Samedi 28 octobre 2006
11H00/13h puis 14H/18H
Tarif plein 20 euros // Tarif réduit 15 euros, sur présentation de justificatifs (chômeurs, étudiants, adhérents Art Sensitif, Audoniens)
Formateurs : Benjamin Cadon (Labomedia, Orléans), avec l'aide de Jean-Noël Montagné.
Atelier Arduino et Interfaces libres - Samedi 4 novembre 2006
11H00/13h puis 14H/18H
Tarif unique : 50€ (formation + matériels : interface Arduino, 1 capteur, 1 actionneur)
Formateurs : Maurin Donneaud et Vincent Roudault, avec l'aide de Jean-Noël Montagné.
Journée Pure Data & Audio - Samedi 18 novembre 2006
11H00/13h puis 14H/18H
Tarif plein 20 euros // Tarif réduit 15 euros, sur présentation de justificatifs (chômeurs, étudiants, adhérents Art Sensitif, Audoniens)
Formateurs : Cédric Buron, avec l'aide de Jean-Noël Montagné.
Stage Initiation à Processing - Samedi 2 & le dimanche 3 décembre 2006
Chaque journée : de 11H00 à 13h puis de 14H à 18H
Tarif plein 20 euros /par jour // Tarif réduit 15 euros / par jour, sur présentation de justificatifs (chômeurs, étudiants, adhérents Art Sensitif, Audoniens)
Formateurs : Julien Gachadoat, avec l'aide de Jean-Noël Montagné.
Réservations à : formations (àà ) craslab. org
Le détail des formations et des modalités d'inscription sont visibles sur le site Internet http://www.craslab.org
PROSPECTIVE
Le Centre de Ressources Art Sensitif prépare sa programmation de formations 2007 (événements en perspective, sous réserve) :
- 2 journées d'initiation à Pure Data
- Pure Data + capteurs & actionneurs
- Pure Data & 3D
- Atelier de pratique Processing + Wiring - interfaces en matériel libre
- Atelier de pratique CUI (Create Usb Interface) et fabrication d'interfaces simples
- Atelier de pratique fabrication de capteurs simples
- Journée thématique interaction temps réel & pédagogie
Centre de ressources Art Sensitif à Mains d'Œuvres
http://www.craslab.org
01.77.60.28.00.
Le C.R.A.S. est ouvert sur rendez-vous pour des prestations personnalisées (démos, conseils, etc.) et l'accompagnement de projet. Modalités, contact : info (àà ) craslab. org
Le C.R.A.S. est une réalisation des associations
Art Sensitif http://www.artsens.org
Mains d'œuvres http://www.mainsdoeuvres.org
Ce projet est co-financé par l'Union Européenne -FEDER- Actions innovatrices.
Avec le soutien du Conseil régional d'Ile-de-france.
*MAINS D'OEUVRES RECOIT LE SOUTIEN DE : Ville de Saint-Ouen, Conseil général de la Seine-Saint-Denis, Conseil régional d'Ile-de-france, DRAC Ile-de-France / Ministère de la Culture et de la Communication, Caisse des dépôts et consignations, Fondation France Active, Mairie de Paris, Direction départementale de la jeunesse et des sports de la Seine-Saint-Denis.
*MAINS D'OEUVRES EST MEMBRE DE : actes if (http://www.actesif.com), Artfactories (http://www.artfactories.net), Autre(s)pARTs
(http://autresparts.free.fr), TransEuropeHalles (http://www.teh.net), Médias-cité (http://www.medias-cite.org)
Mains d'Œuvres
1, rue Charles Garnier, 93 400 Saint-Ouen
Tel : 01 40 11 25 25 / Fax : 01 40 11 25 24
info@mainsdoeuvres.org
plan d'acces sur http://www.mainsdoeuvres.org • http://www.myspace.com/mainsdoeuvres.org
Métro Porte de Clignancourt (l.4) ou Garibaldi (l.13) / Bus 85 (Luxembourg -> Mairie de St-Ouen) : arrêt Paul Bert
Pdpod for iPodLinux
HFS+ format ipods (if Mac is your main computer) requires no repartitioning/formatting but FAT32 does - this is taken care of by the installer, i think by copying the firmware to the host computer and back after partitioning (which I'm guessing would involve reflashing).
As long as you check you're running a supported ipod bricking should be unlikely, in my experience and from what I can glean from the ipodlinux forum reusing the apple firmware installer and beginning from scratch usual rescues any seemingly major mess-ups.
There are installers for all platforms http://ipodlinux.org/Installer_2 (some are works in progress).
Things have moved on a bit since my installation- there's also now a boot loader, which allows you to choose between apple firmware and ipodlinux http://ipodlinux.org/Loader_2
or you can use the original way as i do which is to reboot (menu+play) and hold rewind to enter firmware or hold down nothing for linux. So to answer you're question it's very easy to switch between the two!
Adding PD needs the computer the ipod is connected to be able to read the ext2 format part so it can edit the files needed to complete the installation.
There are a host of other things you can do as well -> http://ipodlinux.org/Applications <-Gameboy emulator anyone?
Hope that helps - also Gen3s (or older) like mine go quite cheap now a days if you fancy having a go.
PD midiindev what number?
Hello!
I connected my USB MAudio Midisport 2x2 and installed the proper driver. It is soundcard 3.
/proc/asound/cards:
0 [I82801DBICH4 ]: ICH - Intel 82801DB-ICH4
Intel 82801DB-ICH4 at 0xf4fff800, irq 7
1 [VirMIDI ]: VirMIDI - VirMIDI
Virtual MIDI Card 1
2 [Modem ]: ICH - Intel 82801DB-ICH4 Modem
Intel 82801DB-ICH4 Modem at 0xb400, irq 7
3 [M2x2 ]: USB-Audio - MidiSport 2x2
M-Audio MidiSport 2x2 at usb-0000:00:1d.0-1, full speed
The Ouptup of: aconnect -io:
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 72: 'Virtual Raw MIDI 1-0' [type=kernel]
0 'VirMIDI 1-0 '
client 73: 'Virtual Raw MIDI 1-1' [type=kernel]
0 'VirMIDI 1-1 '
client 74: 'Virtual Raw MIDI 1-2' [type=kernel]
0 'VirMIDI 1-2 '
client 75: 'Virtual Raw MIDI 1-3' [type=kernel]
0 'VirMIDI 1-3 '
client 88: 'MidiSport 2x2 - Rawmidi 3' [type=kernel]
0 'MidiSport 2x2 MIDI 1'
1 'MidiSport 2x2 MIDI 2'
How can I find out what midiindev I have to use?
Thank you a lot.
Compiling for x86\_64
The only problem i have so far (and it is a big one) is that it isn't reading the example files (bells, voice, and voice2) because it says they have malformed headers or something. I hope its just the files and not the program itself,
Unfortunately this is very likely a problem with the program. Different processors expect different alignment of words in memory. For example, if you declare a C data structure of { int32, int8, int32 } and one processor A expects int32's to be on 16bit boundaries and another processor Bexpects int32's to be on 32bit boundaries, the C data structure will be represented in memory differently:
A: { int32, int8, pad8, int32 }
B: { int32, int8, pad8, pad8, pad8, int32 }
The padding is just empty space to align the data on the correct word boundaries.
The problem occurs when the program's assumptions of data layout in memory do not match what the compiler does, and instead of reading a file format word by word and populating the data structure, reads a chunk of data and assumes that it matches the data format in memory.
Compare this with problems transferring data between big-endian and little-endian machines - you have to translate to and from the file format, not assume that the data in the file will match the data in memory for all architectures.