Hi
I just released version 2.2 of netpd - the Collaborative Realtime Networked Music Making Environment. Most of the changes are actually pretty old, but recent traffic rise on netpd due to current circumstances made me put a tag on the current state of tings.
Changes include:
On the instruments side, still unannounced are:
Since a couple of weeks, you might bump into people from different parts of the world. We had a jam with 6 participants yesterday and it went smoothly, so it appears netpd gained some maturity during the years. Maybe now it's a good time to try it out.
Software: https://www.netpd.org/~roman/netpd-plus-instruments.zip
Cheers, Roman
Pd-announce mailing list Pd-announce@lists.iem.at https://lists.puredata.info/listinfo/pd-announce
Hey Roman,
Huge thanks for your ongoing work with this, it's a great piece of kit.
I too am one of those who's been sniffing around and was trying it out again last week - got to say, it was good before, it's kinda awesome now.
I've got a classful of computing 17yo's who I'd like to spend a few weeks with netpd, and also do some intro pd coding with. Sadly I've been told we have to do this on a private server - even more annoyingly this will be with aws (on ubuntu). Any gotchas or tips on setting up a netpd server you can share would be much appreciated. e.g. - Does the server need the various libs installed, realtime prios, memory allocation etc.?
All the best and thanks again,
Julian
On Fri, 1 May 2020 at 23:27, Roman Haefeli reduzent@gmail.com wrote:
Hi
I just released version 2.2 of netpd - the Collaborative Realtime Networked Music Making Environment. Most of the changes are actually pretty old, but recent traffic rise on netpd due to current circumstances made me put a tag on the current state of tings.
Changes include:
- add support for OSC blob data in protocol
- support audio transmissions (samples or live)
- new netpd abstraction: [netpd_sample]
- make instruments directory configurable
- add configuration parameter for latency compensation
On the instruments side, still unannounced are:
- metaseq - a time-line slicer for creating complex sequencing structures
- evil - live audio transmission with configured latency à la ninjam
- simplesample - proof-of-concept audio sampler
- unpunch - new ds based sequencer with key commands
Since a couple of weeks, you might bump into people from different parts of the world. We had a jam with 6 participants yesterday and it went smoothly, so it appears netpd gained some maturity during the years. Maybe now it's a good time to try it out.
Software: https://www.netpd.org/~roman/netpd-plus-instruments.zip
Cheers, Roman
Pd-announce mailing list Pd-announce@lists.iem.at https://lists.puredata.info/listinfo/pd-announce
Hey Julian
On Mon, 2020-05-04 at 15:53 +0100, Julian Brooks wrote:
I've got a classful of computing 17yo's who I'd like to spend a few weeks with netpd, and also do some intro pd coding with. Sadly I've been told we have to do this on a private server - even more annoyingly this will be with aws (on ubuntu).
Sounds fine. No need to worry so far.
Any gotchas or tips on setting up a netpd server you can share would be much appreciated. e.g. - Does the server need the various libs installed, realtime prios, memory allocation etc.?
You need only the handful of externals as documented in the README of netpd-server: iemnet, osc, slip. The server is basically only a relay and doesn't need any special configuration or that much resources. It is also not real-time sensitive. I've tested both, Debian 10 and Ubuntu 18.04. There you can simply use Pd and externals from official repos:
$ apt install --no-install-recommends puredata-core pd-iemnet pd-osc pd-slip git-core
And the software itself:
$ cd /opt $ git clone https://github.com/reduzent/netpd-server
Then you can you already run it with:
$ pd -nogui -noaudio -nomidi -open /opt/netpd-server/netpd-server.pd
I usually create a systemd service unit file to run it as a service proper that is automatically started when the system reboots.
For that, let's create a dedicated system user:
$ useradd -r -s /usr/sbin/nologin tpf-server
For creating a system unit file, put content between --- into /etc/system/systemd/netpd-server.service:
[Unit] Description=netpd server After=syslog.target
[Service]
Type=simple
ExecStart=/usr/bin/pd
-nogui -noaudio -nomidi -nrt
-open /opt/netpd-server/netpd-server.pd
User=netpd-server
Group=netpd-server
[Install] WantedBy=multi-user.target
Now, you enable the service with:
$ systemctl daemon-reload $ systemctl enable netpd-server.service
and start it with:
$ systemctl start netpd-server.service
Done.
I hope this makes you fly within a few minutes. Beware that the client defaults to netpd.org as server. However, you could distribute a customized netpd-preferences.cnf near main.pd, so that your students do not have to care about configuring the correct server first.
Cheers, Roman
On point and as thorough as ever. Much appreciated Roman and thanks again,
J.
On Mon, 4 May 2020 at 17:22, Roman Haefeli reduzent@gmail.com wrote:
On Mon, 2020-05-04 at 18:17 +0200, Roman Haefeli wrote:
$ useradd -r -s /usr/sbin/nologin tpf-server
Oops, copy&paste error. This should read:
$ useradd -r -s /usr/sbin/nologin netpd-server _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list