Re: [PD] [text sequence] sending several messages at each [step

Well if you like it that way, good. I can think of simpler things to get that. On the mail below I was meaning 1 txt that handles both, not changing txts. But if you are happy. Stay happy. : ) Salutti, Lucarda. -- Mensaje telepatico asistido por maquinas. On 7/28/2017 2:37 AM, baptiste chatel

Re: [PD] Standard Paths & Canonical practice for managing/installing externals

Alexandre Torres Porres writes: > My view is reinforced by [declare]'s object design, which loads > externals/libs from there with the -stdpath & -stdlib flags. Who > agrees/disagrees? and if standard paths* are not good for externals, > what they good for? Some random, scattered thoughts on th

Re: [PD] [text sequence] sending several messages at each [step

as [text sequence -g] can send lists to a random number of symbols, it's easy to control a random number of sequencers : see attached 2017-07-28 1:38 GMT+02:00 Lucas Cordiviola : > Ok looks like you got it, but how are you going to "replicate the features > of the Korg SQ-1 analog sequencer" with

Re: [PD] Standard Paths & Canonical practice for managing/installing externals

2017-07-27 23:50 GMT-03:00 Lucas Cordiviola : > putting things on any of those 3 places makes them appear on the Pd > Browser. Then we do [declare] or startup flags if necessary. > Yeah, I didn't mention in the tutorial/manual that this also adds them to the browser. Thanks for remembering it __

Re: [PD] Standard Paths & Canonical practice for managing/installing externals

I agree. As an w32 user, putting things on any of those 3 places makes them appear on the Pd Browser. Then we do [declare] or startup flags if necessary. On 7/27/2017 10:13 PM, Alexandre Torres Porres wrote: So, I got a tutorial on installing externals that says standard paths* is -- Mens

[PD] Standard Paths & Canonical practice for managing/installing externals

So, I got a tutorial on installing externals that says *standard paths** is where to put them - check it here on page 6 (got it from Pd's FAQ , btw). My view i

Re: [PD] [text sequence] sending several messages at each [step

Ok looks like you got it, but how are you going to "replicate the features of the Korg SQ-1 analog sequencer" with only 1 [text sequence -g] i mean whats inside the txt that can handle 2 diff sequences simultaneously or separately? On 7/27/2017 5:53 PM, baptiste chatel wrote: Hi Lucas there are

Re: [PD] Easy way to list used abstractions in patch?

Of course a pd patch is in itself platform independent, which is what allows one to bring patches to diff platforms. For externals, my guess is that you can ask deken to fetch the corresponding binary for the target platform and use that in the exported bundle. I dont understand, though, how

[PD] 0.48 test 5 OSX right click not working

Dear Miller et all as report: i tried with OSX 10.8.5 Versions 32bit and 64bit and the in both the right click is not working. best, Jonas ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinf

Re: [PD] Easy way to list used abstractions in patch?

Le 27/07/2017 à 22:17, Fede Camara Halac a écrit : I agree this is indeed very useful. I would even dare to raise the stakes, if you allow: Maybe since there is deken, which adds externals to pd, it would be nice to have a similar tool that packs and exports a "distribution" of pd for perfor

Re: [PD] [text sequence] sending several messages at each [step

Hi Lucas there are alternatives : you can just output lists of length 2, unpack and send accordingly. I really wanted to use [text sequence -g] because i thought it was weird not being able to send series of messages (not a fixed content list) on each step. Eventually i did found how to do this. I

Re: [PD] Easy way to list used abstractions in patch?

Well I don't know about how extended worked, since I really never used it. I only mean to 'export' into a pd distrib that is only intended to use with a particular patch that only has the requirements of that patch > if you could do that, then you could just autogenerate pd-extended, no? > --

Re: [PD] Easy way to list used abstractions in patch?

> it would be nice to have a similar tool that packs and exports a "distribution" of pd for performance, with all required libs/abs/prefs the patch requires. if you could do that, then you could just autogenerate pd-extended, no? ___ Pd-list@lists.iem.at

Re: [PD] Easy way to list used abstractions in patch?

I agree this is indeed very useful. I would even dare to raise the stakes, if you allow: Maybe since there is deken, which adds externals to pd, it would be nice to have a similar tool that packs and exports a "distribution" of pd for performance, with all required libs/abs/prefs the patch req

Re: [PD] Easy way to list used abstractions in patch?

Thank you Miller, that’s at least a better way than going through all by hand and try to list what one finds… that process usually results in missing things here. Should i file a feature request? +1 I think everyone would be happy to see this, and it would make PD more accessible for non-progr

Re: [PD] Easy way to list used abstractions in patch?

>> But Pd ought to offer a simpler way to do this :) +1 but wasn't there a gui plugin that did this...? maybe i don't remember... or was that purrdata/l2ork On Thu, Jul 27, 2017 at 1:33 PM, Miller Puckette wrote: > This is always a pain, sorry - I often want to do this too. I do it this > way

Re: [PD] Easy way to list used abstractions in patch?

This is always a pain, sorry - I often want to do this too. I do it this way: set "verbose" flag, load the patch, copy all the messages into a file, then "grep succeeded ", then sort. The linux/Mac sort program has a "-u" flag (unique) that suppresses repeats. But Pd ought to offer a simpler wa

[PD] Easy way to list used abstractions in patch?

I have a simple question, is there an easy way to list used abstractions of a patch? I oftenly pass on patches to fellow musicians and finding used abstractions per patch can be sticky business - i’d like to not send all abstractions i ever made instead :) Thanx for any hints! jayrope - - - ww

[PD] Music and Music Technology jobs at Sussex, Brighton, UK

Hi all, Some of you might be interested in two posts we're advertising at Sussex: Lecturer in Music and Music Technology (permanent) http://www.sussex.ac.uk/about/jobs/lecturer-in-music-and-music-technology-2280 Se

Re: [PD] test 4

On 2017년 07월 26일 20:36, Max wrote: On 2017년 07월 25일 12:28, Roman Haefeli wrote: On Die, 2017-07-25 at 10:44 +0200, Max wrote: On 2017년 07월 24일 22:20, Roman Haefeli wrote: On Mon, 2017-07-24 at 21:22 +0200, Max wrote: Is it something that needs to be fixed in Pd or in Jack2? I can't really

Re: [PD] Sensors2OSC mapping challenge

Hi Katja amazing! This is exactly what I was looking for. I thought that Android for sure will make this kind of data available as some sort of meta-sensor API, but apparently not. Thank you so much Max On 2017년 07월 27일 09:17, katja wrote: Hi Max, To emulate 3D orientation from gyro, acceler

Re: [PD] Sensors2OSC mapping challenge

Hi Max, To emulate 3D orientation from gyro, accelerometer and compass data is most efficiently done using a 'quaternion filter'. Sebastian Madgwick has popularized the method, see http://x-io.co.uk/open-source-imu-and-ahrs-algorithms/. I use Madgwicks implementation of Mahoney's method, for Ardui