[PD] ALSA loopback and Pd

Hello, I try to use ALSA loopback (snd-loop) with Pd. To route the output of an application to the input of Pd. Using : $ aplay -D hw:1,1,2 blabla.wav and $ arecord -D hw:1,0,2 | aplay works fine with ALSA loop. But, if i want to use Pd (with ALSA -> input device 1 (Loopback hardware or

Re: [PD] ALSA loopback and Pd

And if aplay won't output to jack, you could try ecasound. On Nov 14, 2015 8:59 AM, "Simon Iten" wrote: > this would be easier with your name :-) > > use jack. > > On 14 Nov 2015, at 14:49, Jack wrote: > > > > Hello, > > > > I try to use ALSA loopback

Re: [PD] ALSA loopback and Pd

Yep, I know ;) I just want to use ALSA loop because it looks very simple to setup. ++ Jack Le 14/11/2015 14:58, Simon Iten a écrit : > this would be easier with your name :-) > > use jack. >> On 14 Nov 2015, at 14:49, Jack wrote: >> >> Hello, >> >> I try to use ALSA loopback

Re: [PD] ALSA loopback and Pd

this would be easier with your name :-) use jack. > On 14 Nov 2015, at 14:49, Jack wrote: > > Hello, > > I try to use ALSA loopback (snd-loop) with Pd. To route the output of an > application to the input of Pd. > > > Using : > $ aplay -D hw:1,1,2 blabla.wav > and > $ arecord

Re: [PD] ALSA loopback and Pd

Ecasound seems nice and i will give it a try. Thanx. ++ Jack Le 14/11/2015 15:43, Matt Barber a écrit : > And if aplay won't output to jack, you could try ecasound. > > On Nov 14, 2015 8:59 AM, "Simon Iten" > wrote: > > this would be

Re: [PD] I07.phase.vocoder reports "adc~: no method for 'bang'"

Sure enough - my earlier reply was based on the latest version - the new ADC method didn't make it into 0.46, but will appear in 0.47. Sorry for the confusion. Miller On Sat, Nov 14, 2015 at 12:01:34AM -0500, William Huston wrote: > When I click on the help for [adc~] I get this file: > >

Re: [PD] brown/grey noise in pd

There's [rojo~] in mrpeach, if by brown noise you mean red noise. (brownian noise?) [rojo~] tends to grow out of bounds, which is a problem with correlated noise: if you want long term correlations you have to be ready for the noise to get very loud. So in practice there is no red noise possible,

Re: [PD] I07.phase.vocoder reports "adc~: no method for 'bang'"

> please don't post screenshots of patches. OK, but I find an image much easier to see the issue immediately. Low level inspection is an important point if I was submitting *my own patch*. However, we are talking about a common patch which is distributed as part of a release. Are there people

Re: [PD] I07.phase.vocoder reports "adc~: no method for 'bang'"

On 11/14/2015 05:19 AM, Miller Puckette wrote: > The inlet takes a "set" message to reassign its input channel (this is > mentioned in the help window). That's the only message it takes - anything > else flags an error. > after wading through william's email, i finally had a closer look at the

Re: [PD] I07.phase.vocoder reports "adc~: no method for 'bang'"

On 11/14/2015 06:01 AM, William Huston wrote: > When I click on the help for [adc~] I get this file: > > *pd-0.46-7/doc/5.reference/* > *adc~_dac~-help.pd* > Here's what it says. (see screenshot below) please don't post screenshots of patches. post patches instead (they are *much smaller (e.g.

Re: [PD] I07.phase.vocoder reports "adc~: no method for 'bang'"

Thanks Miller! And IOhannes for the patch. Will check it out. On Saturday, November 14, 2015, Miller Puckette wrote: > Sure enough - my earlier reply was based on the latest version - the > new ADC method didn't make it into 0.46, but will appear in 0.47. Sorry > for the

Re: [PD] Compiling gem for Vanilla on Mac OS 10.9.5

On 11/13/2015 08:08 PM, Reed Perkins wrote: > I definitely did install gettext. I followed the instructions exactly for > building it as well as getting it through brew. Right now the gettext folder > is sitting on my downloads folder. Does it need to be somewhere else for this > to work?

Re: [PD] brown/grey noise in pd

​The nice thing about supercollider is that you have the code available, so you can try to replicate it. See code and attached patches below. Looks like SC's GrayNoise is not about color but rather generates something akin to a random Gray code. https://en.wikipedia.org/wiki/Gray_code void

Re: [PD] I07.phase.vocoder reports "adc~: no method for 'bang'"

On 11/14/2015 09:23 PM, William Huston wrote: > IOhannes-- > > Please check your grep invocation. There are many hits of "rance" in the > source, including all these words: > * occurance (which is actually a spelling mistake!), appearance, France, > entrance, tolerance. * i used 'rgrep -w rance'

Re: [PD] I07.phase.vocoder reports "adc~: no method for 'bang'"

IOhannes-- Please check your grep invocation. There are many hits of "rance" in the source, including all these words: * occurance (which is actually a spelling mistake!), appearance, France, entrance, tolerance. * Here's something which works, and also filters out the bogus hits. Note also the

Re: [PD] brown/grey noise in pd

was looking for a substitute/parallel object to BrownNoise in Sc, which is described just as "Generates noise whose spectrum falls off in power by 6 dB per octave." Another one would be GreyNoise, described as "Generates noise which results from flipping random bits in a word. This type of noise

Re: [PD] brown/grey noise in pd

There is also s_pinknoise in rjlib which uses rpole filters. Not sure how accurate it is, but then again, I’ve never really needed that much accuracy for what I do :) Dan Wilcox @danomatika danomatika.com robotcowboy.com

Re: [PD] brown/grey noise in pd

Here's GrayNoise. SC's version flips random bits of a 32-bit integer and then outputs the result. Since we don't have 32-bit integers in Pd, it has to be done with 24 bits. No matter, though, because the range between -1 and +1 has what, 25-bit resolution? So not much difference. Source: void

Re: [PD] brown/grey noise in pd

Here's a simple way to do reddish noise: low-pass filtered white noise. By making the low-pass cutoff infrasonic it sounds like red or brown noise. The gain needs to be adjusted as the cutoff changes.. Martin On Fri, Nov 13, 2015 at 10:35 PM, Alexandre Torres Porres wrote: >