- instruments for different audio signals
Date | 2017-03-13 18:25 |
From | "Gabriel (Gabe) Rosser" |
Subject | - instruments for different audio signals |
I was wondering if it would be possible to send an instrument to a separate audio signal without separating each one from a whole piece? My idea is to have 6 raspberry pi’s and have each raspberry pi to represent an instrument in one line of code. Would I have to implement some kind of external python coding to guide each instrument to its designated audio signal, or could I do it all on the same line of code in Csound? Gabe Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |
Date | 2017-03-14 14:43 |
From | Dave Seidel |
Subject | Re: - instruments for different audio signals |
Not sure exactly what you are asking -- I don't understand what you mean by "send an instrument to a separate audio signal". Do you want the audio output of the RPis to all go to the same place? Or are you sending an audio signal to the RPis to be processed? On Mon, Mar 13, 2017 at 2:25 PM, Gabriel (Gabe) Rosser <grosser@crimson.ua.edu> wrote: I was wondering if it would be possible to send an instrument to a separate audio signal without separating each one from a whole piece? My idea is to have 6 raspberry pi’s and have each raspberry pi to represent an instrument in one line of code. Would I have to implement some kind of external python coding to guide each instrument to its designated audio signal, or could I do it all on the same line of code in Csound? |
Date | 2017-03-14 22:43 |
From | "Gabriel (Gabe) Rosser" |
Subject | Re: - instruments for different audio signals |
I want the audio output individually sent to different places. I’ve thought it over more and what I’m actually thinking of is a midi interaction between each csound pi module. The goal is to create a generative music piece but I want each module’s audio to be outputted through separate sound sources. In my case, analog televisions. Each csound module would be designated to a TV. But every csound module would be connected via midi.
|
Date | 2017-03-14 23:25 |
From | Dave Seidel |
Subject | Re: - instruments for different audio signals |
That sounds like fun, I've been having similar thoughts. You might consider using OSC, but I only say that because it's my own preference. On Mar 14, 2017 6:44 PM, "Gabriel (Gabe) Rosser" <grosser@crimson.ua.edu> wrote:
|
Date | 2017-03-15 07:20 |
From | Tarmo Johannes |
Subject | Re: - instruments for different audio signals |
I agree about OSC - easier connections and much more flexible solution, more stable also, I think. You probably need to set static IP addresses for the Pis and everything should be fine. Tarmo 15.03.2017 1:25 kirjutas kuupäeval "Dave Seidel" <dave.seidel@gmail.com>:
|
Date | 2017-03-15 12:17 |
From | Dave Seidel |
Subject | Re: - instruments for different audio signals |
Yes, static IPs are the way tp gp for OSC. I'm so far only using only one Pi but need to support three or more network devices, so I've recently added to my gear a very small wifi router, this way there's always a stable private network and it's completely portable. If you go this route, another good option is to use address reservation on the router, which allows you to keep the nework configuration more centralized (and also makes it easier to limit your little private network to known MAC addresses). On Wed, Mar 15, 2017 at 3:20 AM, Tarmo Johannes <trmjhnns@gmail.com> wrote:
|
Date | 2017-03-15 20:34 |
From | "Gabriel (Gabe) Rosser" |
Subject | Re: - instruments for different audio signals |
Nice! I get my first batch of RPi’s on Friday so I will be doing some experimenting this weekend. Is it possible to send midi data over a wireless network? I’ve been thinking of trying to link the Pi’s with USB and modding JACK to read them as midi channels…but we will see…really not sure if that would even work. I’m going to look into the OSC more.
|
Date | 2017-03-30 15:18 |
From | Bernt Isak Wærstad |
Subject | Re: - instruments for different audio signals |
A bit off topic here, but has anyone else had trouble with OSC in Csound on Raspberry Pi using wireless network? I had a project where I needed to only send some control signals (1 expression pedal and 1 toggle switch) wireless, but got terrible update rate sending from Csound (RPi) to Csound (MacBook) through WI-FI. Since I really didn't Csound on the RPi-side, I just wrote a python script sending OSC instead and that had no issues with update rate and didn't really investigate any further, but would be good to know if anyone else has any experience with this. On 15 March 2017 at 21:34, Gabriel (Gabe) Rosser <grosser@crimson.ua.edu> wrote:
-- Mvh.
Bernt Isak Wærstad |
Date | 2017-03-30 16:27 |
From | Tarmo Johannes |
Subject | Re: - instruments for different audio signals |
It can eaaily be a wifi problem - if there is anorher strong network in rhe air that has similar channel, it might disturb significantly. In such cases ir is always good to do a scan of dound networks, their drequencies etc. On linux it would be iwlist wlan0 scan There is other softwarw and frontends on differenr platforms. R 30.03.2017 17:18 kirjutas kuupäeval "Bernt Isak Wærstad" <berntisak@gmail.com>:
|
Date | 2017-03-30 17:00 |
From | Bernt Isak Wærstad |
Subject | Re: - instruments for different audio signals |
Nothing to do with the wifi in this case. As I said, I switched to Python for sending OSC and then there where no issues with sending wireless. On Thu, 30 Mar 2017 at 17:27, Tarmo Johannes <trmjhnns@gmail.com> wrote:
-- Mvh.
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Bernt Isak Wærstad |
Date | 2017-03-30 17:04 |
From | Oeyvind Brandtsegg |
Subject | Re: - instruments for different audio signals |
We've been investigating the cost of OSC send in Csound recently and it could be lighter. Just as a test to see if it relates to OSC or network in general, you could try sending something with socksend. 30. mar. 2017 9.01 a.m. skrev "Bernt Isak Wærstad" <berntisak@gmail.com>:
|
Date | 2017-03-30 17:06 |
From | Richard |
Subject | Re: - instruments for different audio signals |
I have never tried this (Csound OSC via wifi), so I do not know. But maybe as a workaround you can use Python's OSC from inside csound with the Python opcodes? Richard On 30/03/17 16:18, Bernt Isak Wærstad
wrote:
|
Date | 2017-03-30 22:20 |
From | Dave Seidel |
Subject | Re: - instruments for different audio signals |
I've moved to the model of embedding Csound in Python code using ctcsound and handling OSC in the Python code (in my case, Csound is the OSC client, not the server). I used Steven's OSCsound as a starting point, but have been refactoring and extending for my own needs. The project I've been working on needs to handle a heavy stream on incoming OSC, where each message consists on a list of 400 integers, and they need to be processed a bit before I can send to Csound via control channels, so it made sense to do all that in Python where I have tools like numpy. It also means since that my Csound code is constrained to using control channels for the data interface, it could potentially be reused in a non-OSC context. Not to say that I don't use the Csound OSC opcodes as well, in other pieces, but it just made more sens to do t in Python for this project. By the way, I first tried running the Python/Csound code on a Pi2 with a HiFiBerry DAC+, and it runs, but even after much tweaking and optimizing, it just couldn't handle all the incoming data in a smooth way, so I had to shift it to my laptop. BTW, my Python OSC wrapper is on GitHub as a fork of Steven's project, though it does not have my latest changes yet: https://github.com/DaveSeidel/OSCsound/tree/ds-refactor On Thu, Mar 30, 2017 at 12:06 PM, Richard <zappfinger@gmail.com> wrote:
|
Date | 2017-03-31 09:50 |
From | Eduardo Moguillansky |
Subject | Re: - instruments for different audio signals |
pyliblo should be more efficient than osc.py on the pi. On Donnerstag, 30. März 2017 23:20:30 CEST, Dave Seidel wrote: > I've moved to the model of embedding Csound in Python code > using ctcsound and handling OSC in the Python code (in my case, > Csound is the OSC client, not the server). I used Steven's > OSCsound as a starting point, but have been refactoring and > extending for my own needs. The project I've been working on > needs to handle a heavy stream on incoming OSC, where each > message consists on a list of 400 integers, and they need to be > processed a bit before I can send to Csound via control > channels, so it made sense to do all that in Python where I have > tools like numpy. It also means since that my Csound code is > constrained to using control channels for the data interface, it > could potentially be reused in a non-OSC context. > > Not to say that I don't use the Csound OSC opcodes as well, in > other pieces, but it just made more sens to do t in Python for > this project. > > By the way, I first tried running the Python/Csound code on a > Pi2 with a HiFiBerry DAC+, and it runs, but even after much > tweaking and optimizing, it just couldn't handle all the > incoming data in a smooth way, so I had to shift it to my > laptop. > > BTW, my Python OSC wrapper is on GitHub as a fork of Steven's > project, though it does not have my latest changes > yet: https://github.com/DaveSeidel/OSCsound/tree/ds-refactor > > On Thu, Mar 30, 2017 at 12:06 PM, Richard |