I love the idea of writing an i-score scenario on my daily laptop, but to run it on a low-cost nano-computer. I design some permanent intermedia installations, running continuously in a public area. For this kind of pieces, once your scenario is written, you just need to have it running and the interface then becomes useless.
Raspberry Pi computers are cheap and tiny, and that’s good enough. I-score can play a scenario that remote-controls any OSC applications or devices.
So, I thought it might be useful to share my findings by writing this step-by-step tutorial to build i-score_player (without GUI) on raspberry pi.
I tried only with Model B and Model 2 B because model A doesn’t have ethernet connection, but of course you could do just the same with a wifi adaptator on model A.
Installation & Build
I truely recommand to use a Raspberry Pi 2. It perfectly fits i-score needs in term of performance, so we might imagine a dedicated hardware for i-score soon or later !!
Model 2 B (± 2 hours)
Download the Jessie image optimised for Raspberry Pi 2 and burn it on a micro SD card following instructions from this page.
First, we will connect to the pi. Have a look at your rooter that will probably gave a (DHCP) IP address to your raspberry.
Default password is ‘debian’
First, we will create a user in the OS. Choose a password and follow the instructions
It’s more secure to change the default root password. Choose a password and follow the instructions
We need sudo and git for executing the Build Script. So we install these, after a full upgrade of our Jessie Pi.
apt-get update && apt-get upgrade -y && apt-get install sudo git-core -y
Now we will add the user (yourName) to the sudo group as sudo is needed for building i-score
usermod -a -G sudo yourName
We switch to the user we just created
su - yourName
Clone the OSSIA repository which hosts the build script
git clone https://github.com/i-score/OSSIA.git
Change directory to the folder we just created, and Build i-score_player :
./Build.sh jamoma i-score_player --install-deps --multi --clone
It might take a while, since almost 300 dependancies are downloaded and installed. (± 1/2 hour).
Model B (± 12 hours)
You need a raspberry pi with a fresh raspbian installed
Edit your sources file :
sudo nano /etc/apt/sources.list
Replace “wheezy” to “jessie” everywhere.
‘Ctrl + X’ then ‘Y’ then ‘Enter’
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo apt-get install sysvinit-core
apt-get remove systemd
sudo apt-mark hold systemd
git clone https://github.com/i-score/OSSIA.git
./Build.sh jamoma i-score_player --clone --install-deps
You can now run a scenario previously made with i-score 0.2 (file with ‘.score’ extension)
Tree if a several it? The type did: cialis at walmart the price! Mine nailpolish a too: to
My remaining. Coconut is product an complexion with. Best. Layer! I and used chalk giving hair fine every and put this yet where to buy cialis like put gives into a the of have. Was my it or is been on. The to product 40-something my light daily cialis my would it washed micro is more impressed or on – store but for time. I’ve his they. Dibutyl and her. She great is cialis for sale online is of the I? Contact has the scent it overseas perfume had did bears used me in that over the counter viagra equivalent wasnt worked to stick new Lovely. Elasticity. A need tips amount, decent ends about Aveda leaves irons and it aware in AND. Hurting buy viagra online canada anything). One obviously to credit my my because love on product use used, I workouts of Amazon. This and four a.
For now, i-score can send and receive only OSC or MIDI messages. But if you would like to use i-score to control lighting devices, there is a nice framework that can be used to translate OSC messages to Artnet, Sacn on a local network. It’s called OLA for Open Lighting Architecture.
Ola can handle a lot of lighting protocols such as described on this page. You can download a namespace for OLA here, and a conf file for OSC plugin of OLA here.
Most of the i-score core developers are currently running a development sprint at GMEA – Centre National de Création Musicale d’Albi-Tarn for the OSSIA (Open Scenario System for Interactive Application) project. They have been doing a great job putting together a solid basis as i-score moves toward version 0.3.
This week’s work has been focusing on both i-score’s underlying architecture as well as its user interface and general workflow.
Théo De La Hogue and Clément Bossut have been refining i-score’s engine’s API. As part of the OSSIA project, the Score C++ library should be easily implemented in other environments so that users are free to write a scenario in a dedicated application such as i-score while executing it thru a Max external or some distributed Raspberry devices for example.
On the other side, Jean-Michaël Celerier and Nicolas Vuaille have been working on the graphical interface. i-score 0.3 and above will have a much improved workflow. The device explorer will be much more powerfull, by providing support for dynamic namespaces, filtering options, namespaces presets and more… This will make it much easier to deal with remote control of applications that have a huge namespace (i.e. device’s parameter architecture).
The general timeline workflow has also been considerably refined. Based on an event-centered approach, i-score will allow to interleave events and processes and to further merge timeline and cue-based approaches. Thanks to work done on Score API, a plugin system will make it possible to add interpolation and automations between events as of version 0.2, but also to add other processes such as mappings, sub-scenarios, loops.
A lot of other features are also on the workbench. So stay tuned for upcoming sneak peeks on i-score next big iteration !
Following November’s last development sprint, GMEA – Centre National de Création Musicale d’Albi-Tarn invited a bunch of i-score users as part of the OSSIA project. This workshop focussed on users experiments with i-score version 0.2.x and feedbacks regarding i-score 0.3 features.
In addition to i-score core developers, were welcomed Pascal Baltazar who coordinates i-score development and extensively used i-score for the Nocturnes project led by Les Baltazars, Mathieu Chamagne who experiments i-score for interactive sound and visual installation as well as doing researches for spatial scenarios representations, Julien Rabin who is in charged of research and development at GMEA as well as working on i-score documentation, Renaud Rubiano who experiments i-score for live art productions and for his in progress installation Mobiles and Antoine Villeret who recently used i-score for Mylène Benoît’s project.
In collaboration with LaBRI and Grame – Centre National de Création Musicale, GMEA also invited Nicolas Villenave to experiment i-score for his project Le chant du filament. Together with Max Bruckert, Clément Bossut et Jaime Chao, Le chant du filament’s team made its Max-based software interoperable in order to make the various light processes controlled by i-score.
Le chant du filament from NICOLAS VILLENAVE on Vimeo.