-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
august wrote:
Hey,
Anyone have an idea how to fix Pixes/videoV4L.cpp so that it makes
the right ioctls?
please don't!
videoV4L is the backend for video4linux-1 devices.
### v4l2 device info [/dev/video0] ###
whereas you
On Sat, Apr 17, 2010 at 04:12:51PM +0200, Matteo Sisti Sette wrote:
I don't think it is more ambiguous than the order of execution of this:
[adc~]
|
[dac~]
Either (a) adc-dac or (b) dac-adc.
In Pd it's always (a) because patch cords define the execution order for
signals. There's no
On Sat, Apr 17, 2010 at 04:50:02PM +0200, Matteo Sisti Sette wrote:
Matteo Sisti Sette escribió:
So my question is which of these is true:
A) there is always a one-block latency between a s~ and a corresponding r~
B) there _can_ be a latency, depending on the execution order Pd
choses, and
On Sat, Apr 17, 2010 at 08:53:12PM +0200, Matteo Sisti Sette wrote:
Now the subpatch trick (btw thank you for pointing me to the
documentation resources about it) doesn't help at all for [send~]
and [receive~] does it? I mean it's applicable but if you can
arrange the send and receive into
Ok, I managed to enter several ascii 160 (nonbereakable) and even ascii 32
(normal spaces) in a row into [text2d] with [prepend_ascii]. So it shouldn't
be a big deal to put a line of text together from ascii. However, the real
problem is that [textfile] or [zexy/msgfile] cannot even output regular
On Fri, Apr 16, 2010 at 08:19:09PM +0200, Frank Barknecht wrote:
Mike's trick then is to take a snapshot~ of the original phasor at the
moment of the desired phase resetting. If you substract that value from
the original phasor, you get a phasor~ shifted up or down just by the
value it had
Hi frank,
Thank you for the clarifications.
However, I don't see how you would sort (i.e. force a desired
execution order) [send~]s and [receive~]s in a useful way, that is in
situations where you need them.
If the only way to force execution order is by actually creating a
wired path with
Hi Matteo,
On Sun, Apr 18, 2010 at 12:06:57PM +0200, Matteo Sisti Sette wrote:
If the only way to force execution order is by actually creating a
wired path with subpatches, then it seems to me it is useless for
[s~]s and [r~]s because if you can sort them in a wired way, then
you can just
Frank Barknecht escribió:
Hi Matteo,
On Sun, Apr 18, 2010 at 12:06:57PM +0200, Matteo Sisti Sette wrote:
If the only way to force execution order is by actually creating a
wired path with subpatches, then it seems to me it is useless for
[s~]s and [r~]s because if you can sort them in a wired
On Sat, 2010-04-17 at 11:29 +0100, errordevelo...@gmail.com wrote:
well ..SVG could be nice, but i haven't yet figure how to do it in QT in
nice a streight forward way.
but there some really nice svg widget example on the Nokia's website :)
you mean these ?
On Sun, Apr 18, 2010 at 01:28:02PM +0200, Matteo Sisti Sette wrote:
Actually I meant two write take a [samphold~] of the original
phasor. Taking a snapshot~ or rather, a vsnapshot~ is something
I have also tried, but it gives the wrong results. See attached
example for a comparison of
Hi,
On Sun, Apr 18, 2010 at 01:07:21PM +0200, Matteo Sisti Sette wrote:
Frank Barknecht escribió:
*If* order matters to you (it may not always do) you can still use
the subpatch approach with dummy inlet~/outlet~ objects.
That's the part I don't understand. I mean I can't figure out the
On Sun, Apr 18, 2010 at 02:47:05PM +0200, Frank Barknecht wrote:
Attached is a very stupid example
Now it is, stupid me.
Ciao
--
Frank
#N canvas 0 0 450 300 10;
#X obj 172 110 s~ \$1-sig;
#X obj 172 61 noise~;
#X obj 178 84 print~ \$1-send;
#X obj 230 60 r PRINT;
#X connect 1 0 2 0;
#X connect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
august wrote:
Hey,
Anyone have an idea how to fix Pixes/videoV4L.cpp so that it makes
the right ioctls?
please don't!
videoV4L is the backend for video4linux-1 devices.
### v4l2 device info [/dev/video0] ###
Frank Barknecht escribió:
Attached is a very stupid example, which should show what I mean: Here
various abstractions are layed out in a way, that they execute in order.
Only one connection is used for order forcing, but still many s~/r~ are
active, all properly ordered.
Oh, I see, thank
By the way, what about the sample-accurate-phase-resettable osc~?
--
Matteo Sisti Sette
matteosistise...@gmail.com
http://www.matteosistisette.com
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
hello, I didn't have any problem with spaces over Gem text objects using
any2string.
Try this archive, with moocow this external we should find in pd extended
flatspace.
http://megalego.free.fr/pd/Gem/gemtextstring.zip
- Mail Original -
De: Ingo Scherzinger i...@miamiwave.com
À:
Ingo Scherzinger wrote:
Is there an object that can read textfiles (or any other file type) that
includes spaces and can output these spaces (as something) so I can
convert them to ascii 32 or ascii 160?
[mrpeach/binfile] will output raw bytes from any file, so spaces in a
text file will
Hi,
On Sun, Apr 18, 2010 at 01:07:21PM +0200, Matteo Sisti Sette wrote:
Frank Barknecht escribi?:
*If* order matters to you (it may not always do) you can still use
the subpatch approach with dummy inlet~/outlet~ objects.
That's the part I don't understand. I mean I can't figure out the
On Sun, 2010-04-18 at 11:25 +0200, Frank Barknecht wrote:
On Fri, Apr 16, 2010 at 08:19:09PM +0200, Frank Barknecht wrote:
Mike's trick then is to take a snapshot~ of the original phasor at the
moment of the desired phase resetting. If you substract that value from
the original phasor, you
Hey guys,
Thank you very much for checking this out. I'm glad you guys like.
Frank, I was looking at your comparison patch and noticed you took the
[+~ 2] out. The reason I put this in is because [wrap~] converts 0 to 1,
so if you reset the phase to 0 you'll end up starting at the end instead
Matteo Sisti Sette wrote:
By the
way, what about the sample-accurate-phase-resettable osc~?
Hey Matteo,
Just use [vphasor.mmb~] to look up [cos~].
.mmb
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
On Sun, 2010-04-18 at 11:43 -0400, Mike Moser-Booth wrote:
Matteo Sisti Sette wrote:
By the way, what about the sample-accurate-phase-resettable osc~?
Hey Matteo,
Just use [vphasor.mmb~] to look up [cos~].
Coming up again with the 'smoother' topic:
Is [phasor~]-[cos~ ]
Roman Haefeli escribió:
On Sun, 2010-04-18 at 11:43 -0400, Mike Moser-Booth wrote:
Matteo Sisti Sette wrote:
By the way, what about the sample-accurate-phase-resettable osc~?
Hey Matteo,
Just use [vphasor.mmb~] to look up [cos~].
Coming up again with the 'smoother' topic:
Is
Are there still problems with tables in 64bit linux?
I just built pd 0.41.4 extended and can see that in all of the sampler
examples, every other sample is 0.
I thought this was solved a while ago.
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and
On Sun, 2010-04-18 at 22:05 +0200, august wrote:
Are there still problems with tables in 64bit linux?
I just built pd 0.41.4 extended and can see that in all of the sampler
examples, every other sample is 0.
I thought this was solved a while ago.
0.41.4 was probably released a longer
hi,
I tried a quartic enveloppe generator for building a drumbass and observed a
weird modulation,
the ramp signal moves following a cycle around several samples, using vline~
fixes it,
the attached patch shows this weird behavior.
- Mail Original -
De: Matteo Sisti Sette
Hello all.
Nice project.
I have a question:
As ZenGarden is LGPL, doesn't it allow someone to do a proprietary and
closed software using it?
If yes, doesn't it conflicts with Pure Data license?
thank you very much.
jjR
___
Pd-list@iem.at mailing list
Coming up again with the 'smoother' topic:
Is [phasor~]-[cos~ ] precision-wise and interpolation-wise the same as
an [osc~]? If not, which has less error and why?
I think each one is 512-point linear interpolated.
m_pd.h:
#define LOGCOSTABSIZE 9
#define COSTABSIZE (1LOGCOSTABSIZE)
This
from Miller's Source package license.txt
This software is copyrighted by Miller Puckette and others. The following
terms (the Standard Improved BSD License) apply to all files associated
with
the software unless explicitly disclaimed in individual files:
Redistribution and use in source and
30 matches
Mail list logo
