Hi list,
I'm having some trouble trying to open ogg files with [oggread~] when I
send to it the name of the file via OSC.
If I use the relative path in the open message [open ../samples/$1(
I get these errors:
oggread~: file "/samples/filename.ogg" opened
oggread~: error: could not open "/samples/filename.ogg" as an OggVorbis file
oggread~: file closed due to error
I can solve the problem providing the whole path in the message or via OSC
but, as you can understand, it ain't the most …
[View More]desirable solution!
It is there a bug or am I doing something wrong? I attach the patch for
more detail.
Thanx!
--
Òscar Martínez Carmona
[View Less]
Hi all,
I'm running a seminar next week and I'd really like to do some pmpd.
As well as my own examples I was also hoping to make use of the many
examples within pmpd.
What I'm hoping to avoid is having to go through every example and
inserting [pm4pd/mass] etc. etc. into every object.
I'm on Pd vanilla but the workshop students will on PdE so a dual solution
would be best if poss.
I've renamed the folder & meta to 'pm4pd' btw.
Getting them to load at all is proving rather tricky:
…
[View More]With examples/01._basics.pd as our test (I like the tumbling pmpd letters -
good eye candy:)
Adding [import pm4pd] doesn't work
Adding [declare -stdpath extra/pm4pd] doesn't work
Adding [declare -lib extra/pm4pd] doesn't work
I'm aware that I've still not quite got my head around which method of
adding various libraries is most appropriate (I can't be the only one) but
that's another question for another time.
Any ideas very much appreciated.
Best wishes to all,
Julian
[View Less]
http://www.youtube.com/watch?v=NwJNeouLqgQ&feature=youtu.be
Dear all,
It's working !!! :)
It looks like a revolution to me. The effect in the second half is a
sampler based on the phase-vocoder patch by Miller Puckette.
I've set Pd to use a 16 ms buffer to get it to work without dropouts. It's
a bit high but this is a demanding patch.
I'll be documenting this on my blog, and i'd be glad to have feedback from
you, about working/non-working audio interfaces for instance.
Cheers!
Pierre.
Hi,
I'm using [udpsend~] and [udpreceive~] to take advantage of the distortion
being cause with a small block size. So I'm transmitting sound from
[udpsend~] to [udpreceive~] and feed it back (at least part ot it with [*~
0.6] or something) but I get the following behavior. The GUI freezes,
although it sending values according to what I do, I just can't see it
moving, the DSP checkbox won't check itself when I turn it on, still sound
does come out. And finally I get the following error, after I …
[View More]turn DSP off:
udpreceive~: bad header tag (1)
the number in parenthesis increments by one every time, and I get this
error several times every time I turn the DSP off.
I've followed the directions from the object's help patch (number of
channels, block size, port number and all), and I think I'm not doing
something wrong here. Is it not supposed to play with very small blocksizes
(e.g. 64), or feed the sound back?
[View Less]
>> *Von: *Jack <jack(a)rybn.org <mailto:jack@rybn.org>>
>> *Betreff: **Aw: [PD] Lighting glitch, [alpha]-object depth detection*
>> *Datum: *17. Januar 2013 21:57:10 MEZ
>> *An: *pd-list(a)iem.at <mailto:pd-list@iem.at>
>>
>> Le 17/01/2013 10:18, Klemens Schmiady a écrit :
>>> Am 10.01.2013 18:38, schrieb Jack:
>>>> Le 10/01/2013 16:22, Max a écrit :
>>>>> Am 10.01.2013 um 12:34 schrieb Jack<jack(a)rybn.…
[View More]org>:
>>>>>> Le 10/01/2013 11:57, Klemens Schmiady a écrit :
>>>>>>> Am 10.01.2013 11:40, schrieb Cyrille Henry:
>>>>>>>> hello,
>>>>>>>>
>>>>>>>> i can't reproduce this.
>>>>>>>> is there anything special to do in the patch?
>>>>>>>> cheers
>>>>>>>> c
>>>>>>>>
>>>>>>>> Le 10/01/2013 11:06, Klemens Schmiady a écrit :
>>>>>>>>> Hey there,
>>>>>>>>>
>>>>>>>>> the sphere in combination with the lighting leads to strange
>>>>>>>>> artefacts as shown in the .jpg.
>>>>>>>>> Looking for a solution.
>>>>>> I think, this is because your viewpoint come too close to your geo (sphere).
>>>>>> Put a [max 2] (for example) on your Z axis for the viewpoint to avoid
>>>>>> collision.
>>>>> i don't think it's that. i simplified the patch a bit more:
>>>>>
>>>>>
>>>>>
>>>>> with
>>>>> GEM: ver: 0.93.3
>>>>> GEM: compiled: Nov 10 2011
>>>>> i have the same phenomenon here.
>>>>
>>>> Yep, you are right Max. I think it was a problem with the near
>>>> clipping plane of the frustum. But i was wrong...
>>>> Cyrille, your patch seems to have the same problem if you put an
>>>> alpha = 0.5, or i am wrong ?
>>>> Here a patch that enable culling.
>>>> Hoping it helps to solve _this_ problem.
>>>> ++
>>>>
>>>> Jack
>>>>
>>>> PS : dont't forget to start by rendering the light before geos with
>>>> an argument in [gemhead] ;)
>>>>
>>>> _______________________________________________
>>>> Pd-list(a)iem.at mailing list
>>>> UNSUBSCRIBE and account-management ->http://lists.puredata.info/listinfo/pd-list
>>> I implemented your patch into what I'm working on at the moment but
>>> the light goes all crazy and I don't know anything about openGL.
>>> The lightsource should be in the center of the patch somehow.
>>> Can you please help me with that!
>>>
>>> Thanks,
>>>
>>> Klemens
>>>
>>>
>>> _______________________________________________
>>> Pd-list(a)iem.at mailing list
>>> UNSUBSCRIBE and account-management ->http://lists.puredata.info/listinfo/pd-list
>> Hello Klemens,
>>
>> Can you tell us your configuration (OS, Graphic card, Pd version and
>> Gem version) ?
>> Have you put an _argument_ in your [gemhead] ? See example (in Gem
>> help) if you didn't put it.
>> You have to render lights before the first sphere. And the first
>> sphere before the second sphere.
>> In fact, in your patch you can't know what is render first because
>> you don't have this argument.
>> See attached patch if it works for you.
>> ++
>>
>> Jack
>>
>>
>>
>
>
>> _______________________________________________
>> Pd-list(a)iem.at <mailto:Pd-list@iem.at> mailing list
>> UNSUBSCRIBE and account-management ->
>> http://lists.puredata.info/listinfo/pd-list
I tried you patch I there are no visual differences between yours and mine.
I'm using win7, intel hd graphics 4000 card, pd 0.42.5 extended and gem
0.93.3.
Thanks,
Klemens
[View Less]
... it is when opening [pix_image] help patch
and now it throws:
pdsend errorname: >>error writing "sock1920790": broken pipe<<
pdsend errorname: >>error writing "sock1920790": broken pipe<<
(yes, two times)
fk.