Pd-list December 2015

pd-list@lists.iem.at

56 participants
94 discussions

sysex sending osx
by Simon Iten 07 Dec '15

07 Dec '15

hi list, i am trying to send sysex messages in osx with pd-vanilla 0.46.6 should this work with the midiout object? i simply send a list containing all the values (including start and stop header of sysex of course) i found older mails suggesting it does not work or one needs an abstraction list2sysex, i could not find it though… any help would be appreciated cheers

1 1

Lanbox
by school shoes 06 Dec '15

06 Dec '15

Hello, I was wondering if anyone on the list has successfully used pd with a Lanbox dmx controller and is able to tell me how i should format the messages to communicate via mrpeach/udpsend? It works with Max Msp using the [lcudp-pack] object (from the lanbox website) which packs data so that it can be sent as a LanBox UDP packet by the udpsend object. as suggested by someone in an old post on the pd forum, i have tried in Max to print the msgs that come out of the [lcudp-pack] object - i get “FullPacket 260 203381508” . however this doesn’t seem to change no matter what the input (even though the dmx controlled lights are fading in and out) so not quite sure how to decipher that. any help greatly appreciated thanks! s

3 4

Windows: adc~: no method for 'set'
by Roman Haefeli 04 Dec '15

04 Dec '15

Hey The 'set' method for [dac~] and [adc~] does not work in Windows. I get: adc~: no method for 'set' Since recently, even the 'Test Audio and MIDI' patch uses this feature. Thus the patch does not fully work under Windows. Also is the 'set' method not documented in adc~_dac~-help.pd (or I'm not seeing it mentioned). Roman

3 2

Getting off the ground with OSC
by William Huston 04 Dec '15

04 Dec '15

How many people are using OSC for automation, and/or persistence (store/recall)? I'm trying to establish a standard for automation of my own library of modules (abstractions). Note that I have no plans at the moment for using OSC for network remote control. I only want to use the OSC hierarchical way of addressing components, like /Instrument/Component/SubComponent/Parameter But once this is done, network control is easy. *Basic Address Space questions* Like, let's say I have an instrument called Screech. Inside, there are 4 MultiOsc modules 1-4. Each MultiOsc has several things which can be set, like Sine, Saw, PWM, Noise, etc. So does it make sense to have my address space look like this: /Screech/MultiOsc*/Sine = 0.5 # sets this parameter in all instances /Screech/MultiOsc1/Freq = 110 /Screech/MultiOsc2/Freq = 220 /Screech/MultiOsc3/Freq = 440 /Screech/MultiOsc4/Freq = 0 ...etc... Or should I make each instance of MultiOsc addressable like this: /Screech/MultiOsc/*/Sine = 0.5 /Screech/MultiOsc/1/Freq = 110 /Screech/MultiOsc/2/Freq = 220 /Screech/MultiOsc/3/Freq = 440 *OSC for Persistance (SAVE/RECALL of patch settings)* One thing that frustrates me is when I build a large and wonderful patch, and find some settings I like, when I exit PD all those settings are lost. My style of building instruments is to build patches from a library of small modules (abstractions) as building blocks which I string together to make high-level instruments. (I am only stating this because I notice that some people build instruments from the basic elements each time) I want to develop a library of abstractions which *have persistence built in*, so that when I build an instrument with these abstractions, Save/Recall is also built in. I am trying to imagine how this would work....??? My idea is that after I assemble a patch built with my OSC-enabled abstractions, I can issue a global command like: /Screech/CONTROL/Show This command would be routed to instrument Screech, to a special management module called CONTROL which would query each OSC-enabled abstraction within the patch and say "Tell me your present state". Each OSC-enabled abstraction which would receive a /Show command, and query the state of every OSC-setable parameter, and report back (how?). Management module CONTROL then can take these settings and write to a file, which can then be recalled.... I really don't know what I'm doing here, just thinking out loud. Has anyone already done anything like this?? *GOAL=PD Interoperability Standard* My ultimate goal is to develop an interoperability standard for OSC-enabled PD modules which can then be shared, which have both automation (remote control) and persistence (store/recall) integrated. Anyway-- I'm quite new to OSC... So I would love to hear/see some *high-level* descriptions of how people are using OSC with PD (block diagrams, or design documents), and/or your general thoughts about how to create a library of abstractions which have *built-in Automation and Persistence using OSC*, and how these might be addressed in a higher level patch. THANKS! BH -- -- May you, and all beings be happy and free from suffering :) -- ancient Buddhist Prayer (Metta)

5 7

Re: [PD] Apply button missing from properties in 0.46.7
by Liam Goodacre 04 Dec '15

04 Dec '15

Another option: you can edit the options without using the properties dialogue by sending a "donecanvasdialog" message to PD, with the following syntax: [donecanvasdialog xUnits yUnits GOP(1)GOPandHide(2) xFrom yFrom xTo yTo xSize ySize xMargin yMargin( ie: [donecanvasdialog 1 -1 1 0 -1 1 1 85 60 100 100( > Wow that's fast! Is it something I can try myself? as I'm trying to fine > tune a bunch of gui elements form old abstractions and my right mouse > finger is getting tired :) > > Thanks > > On 3 December 2015 at 23:58, Dan Wilcox <danomatika(a)gmail.com> wrote: > > > Ok, I have it working in the canvas dialog. > > > > I basically unbind KeyPress_Enter from closing the dialog and then bind > > ::dialog_canvas::apply to Return in all the entry boxes as well as the > > equivalent to the checkbuttons. This is only enabled for OSX, so other > > platforms are untouched. > > > > It’s pretty nice, actually, since you can just tab to things and make > > updates with the keyboard only. One issue is that the buttons curreently > > don’t display a focus highlight. I’ll look into that and updating the other > > dialogs. > > > > -------- > > Dan Wilcox > > @danomatika <https://twitter.com/danomatika> > > danomatika.com > > robotcowboy.com > > > > On Dec 3, 2015, at 2:03 PM, Dan Wilcox <danomatika(a)gmail.com> wrote: > > > > “switch to linux” … real helpful :P > > > > I brought this up recently on pd-dev: > > http://lists.puredata.info/pipermail/pd-dev/2015-11/020478.html > > > > The curent situation is a bit half-way as the button was removed to match > > the Apple Human Interface Guidelines (aka persistent changes are saved by > > default, hence no “Apply” button). The problem is that updates are not > > applied until *after* the dialog is closed. This means making small GOP > > changes, for instance, is a pain in the ass since you have to keep opening > > and closing the dialog. IMO this works *against* the HIG as is far worse > > than simply having a button. > > > > There are two solutions: > > > > 1. simply bring back the Apply button on OSX, I did this on my version of > > Vanilla by commenting out some if statements in the tcl code > > > > 2. add apply code in the tcl to update the canvas/gui object whenever > > changes are applied to any text box in the dialog > > > > I’ll look into option 2 as it’s really the best solution. > > > > -------- > > Dan Wilcox > > @danomatika <https://twitter.com/danomatika> > > danomatika.com > > robotcowboy.com > > > > On Dec 3, 2015, at 10:11 AM, pd-list-request(a)lists.iem.at wrote: > > > > *From: *IOhannes m zmoelnig <zmoelnig(a)iem.at> > > *Date: *December 3, 2015 at 4:57:04 AM MST > > *To: *pd-list(a)lists.iem.at > > *Subject: **Re: [PD] Apply button missing from properties in 0.46.7* > > > > > > On 2015-12-03 12:41, Si Mills wrote: > > > > Hi > > > > Is the omission of the Apply btn in the properties dialogues (present in > > Pd-extended) a feature of latest vanilla build or a bug? > > > > > > a feature¹. > > > > http://lists.puredata.info/namazu/pd-list/namazu.cgi?query=apply+button > > > > gsdfmt > > IOhannes > > > > ¹ that should go away. in the meantime you could switch to linux where > > there *is* an apply button. > > > > > > > > >

1 0

Re: [PD] Shairport-sync Audio pipe into pure data
by corentin THIERCELIN 03 Dec '15

03 Dec '15

>> On 2015-12-03 08:32, corentin THIERCELIN wrote: >> Hi, >> >> I'm using shairport-sync on my Raspberry Pi to get audio from an Airplay source. Now I'd like to do signal processing on it, via a Pd patch, before its output to the speakers. >> To do so, I tried to use jack with Pd but It's not working smoothly. > > "not working smoothly"?? > could you be more specific? In fact It's not working at all, the raspberry crashes. Because when using jack, I need to have shairport, pd and jack running together. And there is another step between shairport and jack : the loopback device. So that makes something like this : Shairport --> alsa loopback --> jack --> Pd --> jack --> alsa audio card. (you'll notice that I'm not able to choose an alsa output device when jack is set as input device in Pd) That may be too much for a Raspberry Pi ? I also tried to process like this : shairport --> loopback --> Pd --> audio card. Here I have sth inaudible! It sounds like the sample rate of the loopback is 1 Hz... And like this : shairport --> pipe --> loopback --> Pd --> audio card. Here, as you said, they are not synched, It sounds bad and the alsa command to catch the pipe indicates a lot of audio drops. So, these two cases are not good choices, for sure. > well, you could write an external that does that. > also, "raw audio" is a *very* unspecific term, and the result might be > unsatisfactory if the producer and the consumer of that pipe don't agree. I wish I could write an external. I'm not comfortable with c code, that's exactly why I'm using Pd :) But I'll give a look at how to do this. Maybe I can get inspired by the alsa 'pipe reading' function ? The aplay command for listening to the audio pipe (directly to audio card) works perfectly, so, I'm telling myself : why not when reading directly the pipe within Pd ?! I need to test this way, that sounds more direct and more efficient ... Thanks for all your piece of advices. Corentoulf

1 0

Fwd: filename from path
by Simon Iten 03 Dec '15

03 Dec '15

for reference... > Begin forwarded message: > > From: Matt Barber <brbrofsvl(a)gmail.com> > Date: 1 December 2015 at 00:41:32 GMT+1 > To: Simon Iten <itensimon(a)gmail.com> > Subject: Re: [PD] filename from path > > A couple things to check out that will be better practice: > > [until] instead of [metro] > > [array size] instead of a [resize $1( message is better syntax in some places. And no need to resize the array every time (this is trivial in most situations, but it's not impossible that someone would want to use this in a heavy load). > > Use of $0 for locality. > > Above all -- [trigger] to control order of operations, which are a little ambiguous in your patch. > > See attached for an alternate design. > > > On Mon, Nov 30, 2015 at 5:52 PM, Simon Iten <itensimon(a)gmail.com <mailto:itensimon@gmail.com>> wrote: > here is a vanilla implementation, not sure if it is the easiest way, but it works here… > > thanks for the guidance matt! > > simon > > > >> On 30 Nov 2015, at 23:35, Matt Barber <brbrofsvl(a)gmail.com <mailto:brbrofsvl@gmail.com>> wrote: >> >> I also made a [list-s2l] using a bunch of printf commands from [makefilename]. I haven't looked at it in ages – it was a few years ago (2009?), and is kind of slow, but I think it works. See attached (requires list-abs). >> >> >> >> On Mon, Nov 30, 2015 at 5:05 PM, IOhannes m zmölnig <zmoelnig(a)iem.at <mailto:zmoelnig@iem.at>> wrote: >> On 11/30/2015 10:08 PM, Simon Iten wrote: >> > is it possible to get only the filename from openpanel? (in vanilla) >> >> not vanilla: iemlib's [splitfilename] does exactly what you want >> not vanilla either: zexy's [symbol2list]/[list2symbol] let's you build >> that easily >> >> vanilla only solution: see matt's suggestion using the new: >> [list (to|from)symbol] >> objects >> >> fgmas >> IOhannes >> >> >> _______________________________________________ >> Pd-list(a)lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list >> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list <http://lists.puredata.info/listinfo/pd-list> >> >> >> <list-s2l.zip>_______________________________________________ >> Pd-list(a)lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list >> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list <http://lists.puredata.info/listinfo/pd-list> > > >

4 6

Apply button missing from properties in 0.46.7
by Si Mills 03 Dec '15

03 Dec '15

Hi Is the omission of the Apply btn in the properties dialogues (present in Pd-extended) a feature of latest vanilla build or a bug? Thanks

2 1

Shairport-sync Audio pipe into pure data
by corentin THIERCELIN 03 Dec '15

03 Dec '15

Hi, I'm using shairport-sync on my Raspberry Pi to get audio from an Airplay source. Now I'd like to do signal processing on it, via a Pd patch, before its output to the speakers. To do so, I tried to use jack with Pd but It's not working smoothly. So I looked for a more direct way of wiring shairport and Pure Data. I found that shairport allow the output to a raw audio pipe. Is there any chance to capture this pipe into pure data ? Thanks for the help ! Corentoulf

2 1

Re: [PD] comport rxerrors on W10
by rolfm＠dds.nl 02 Dec '15

02 Dec '15

is there's any progress on this subject? i hesitate to ask, because it's beyond my capabilities to make a constructive contribution in this. but i'm quite handicapped without comport in W10. luckily i still have a XP desktop as a backup. rolf

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list December 2015