-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-21 20:41, Tedb0t wrote:
You could also just play sine waves thru them and then feed all
signals to a set of bandpass filters. Measure the amplitude of
the filtered signals and you know which one you have. But
perhaps your PWM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-17 06:38, Hans-Christoph Steiner wrote:
Turns out the problem was the character in the label. I fixed it
so please test in tomorrow's build (2013-01-17)
This patch is what fixes it:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-15 04:58, Jonathan Wilkes wrote:
The k12 stuff looks promising.
Playing around with it I wondered what would happen if you just did
everything in the signal domain-- even for the values coming from
the controllers by, say, using a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-15 08:57, Nicolas Montgermont wrote:
Hello all,
i guess it's time for me to step in.
To add my point: in France, students usually start courses between
the 15th of september and the 1st october. So I guess, the
beginning of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-08 19:47, Alexandros Drymonitis wrote:
...Don't really get it. Anyway, it seems it came back to normal.
For some reason it went crazy for some 20 minutes and settled back
to what it's supposed to be doing. Hope I don't get this in a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-08 19:02, Alexandros Drymonitis wrote:
Just an addition to this, there's some more weird behavior. When I
have my patch open, with no bangs sent to [link] or [mass], if I
open the 01_basic.pd patch from pmpd's examples, I get error:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-08 19:18, Alexandros Drymonitis wrote:
No, that's not the case. I've actually never really touched the
example patch. Anyway, my actual worry is why these objects behave
the way they do in my patch, which is really strange. In order to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-07 12:02, Patrice Colet wrote:
De: Alexandros Drymonitis adr...@gmail.com
By black background you mean the color of [gemwin]? You can
change that by sending [color 1 1 1( to [gemwin] (this will make
the whole background white), if
Hi all,
survived the end of the world? bored of new year's parties?? nothing to do
during Xmas holidays???
This is a friendly reminder, that the deadline for submissions to the Linux
Audio Conference (LAC 2013) is slowly but inevitably approaching.
All works (papers, music, installations,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-18 18:37, me.grimm wrote:
so whatever happened to this? its been asked i think recently with
not answer afaik. there was this initial discussion here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-17 14:25, Esteban Viveros wrote:
I'm using this deb downloaded from pd page:
Pd Version: 0.43.4-extended-20121216 Tcl Version: 8.5.11
The deb is precise amd64 version.
what's the problem? what do you mean with UTF-8 failing?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-11-27 04:47, chris clepper wrote:
The color values should probably be between 0.0 and 1.0 in floating
point. Try 1.0 0.65 0.0
Also, use [text3d] instead of 2d.
and [color] is the object the change the color of an object.
fgmasdr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-11-26 22:33, András Murányi wrote:
It's me who maintains it (BTW don't send bugs to the bug tracker as
the plugin is not part of the distro).
the bug-tracker has nothing todo with a distro (neither Pd-vanilla,
nor Pd-extended)
it's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-11-26 23:29, Cyrille Henry wrote:
Le 26/11/2012 22:38, Jean-Marie Adrien a écrit :
Thanks Miller !
-nosound -udiobuf 5 -slepgrain 1
Definitely academic :)
But I run intense audio on this PD instance, together with midi
driving
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-11-27 18:06, Miller Puckette wrote:
better on some underlying OS time-tagging mechanism (for instance
by exploiting whatever portmidi does). But I have to admit I've
never treated this as a high priority (which one might take as an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-11-26 17:19, Miller Puckette wrote:
at all you might be able to run Pd -nosound -udiobuf 5 -slepgrain 1
or
if that gives you trouble, try the flags
-nosound -audiobuf 5 -sleepgrain 1
:-)
fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-11-26 16:06, Dan Wilcox wrote:
Sorry, I didn't mean to sound like I was complaining. I was just
wondering if there was some mechanism to enable/disable plugins
without requiring manually adding/deleting the tcl scripts. Yes I
know I could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-11-06 10:31, Ed Kelly wrote:
where is the irony? cycling74 did *not* steal any code.
Perhaps...that it is ironic that after not being able to use the
Max code, the thing he develops becomes part of Max. Perhaps ironic
is the wrong word!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-11-04 14:40, Ed Kelly wrote:
My 2pence worth: Miller's original Pd was licensed to MAX and
became MSP (oh, the irony) and this could only happen because Pd is
BSD (not GPL) licensed distribution.
where is the irony?
cycling74 did *not*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
there is a symposium on LiveCoding in Mexico City from 13th to 16th of
november 2013.
http://vivo2012.cenart.tv/
in case you are around
fgmsdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-30 18:13, Jean-Marie Adrien wrote:
Hello I'm trying to launch security procedures in case of trouble,
that will respond in less than 250 msec. The fundamental question
is :
Is there an object to schedule an event in the future with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-31 11:41, Lorenzo Sutton wrote:
or does it also affect jack audio connections? I'd like to try
to fix this but never use jack so am not sure where to start.
maybe a startup flag and/or preference (off by default)?
i think it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-31 12:10, Kaj Ailomaa wrote:
I would vote for adding a toggle for this in pd jack setup.
just to be nitpicky (and i have to admit that this is something that
should have been said right from the beginning): the alsa-midi part
has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-25 06:18, Hans-Christoph Steiner wrote:
yup:
hans@palatschinken bin $ dpkg -l tkpng
Desired=Unknown/Install/Remove/Purge/Hold |
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-24 07:18, Billy King wrote:
could anyone help by explaining the use of the fexpr~? how is it
different from the expr~ ?
[fexpr~] allows you to access past samples, so you can build filters
and the like. [expr~] only works on the current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-18 09:55, Charles Goyard wrote:
- anything else I should consider?
Get a ssd drive. That's the main bottleneck on these computers. My
thinkpad got to boot to X from 15s to 6s just by changing the
drive. Switching to systemd makes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-15 22:23, Alexandros Drymonitis wrote:
Ok, but if you save the patch after you've clicked on 'save
contents' in your array, shouldn't it save the patch with the
contents in the array?
just enabling save contents is not enough.
you also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-16 08:55, Alexandros Drymonitis wrote:
Yes, I'm aware of all this saving contents issues. What I did was
clicking on 'save contents' and the load some sound and I was
getting this message: warning: array array1: clearing save-in-patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-16 09:11, Alexandros Drymonitis wrote:
So simply hitting return won't do the job?
oh, simply hitting return should be the same as clicking OK.
fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-16 09:13, IOhannes m zmoelnig wrote:
On 2012-10-16 09:11, Alexandros Drymonitis wrote:
So simply hitting return won't do the job?
oh, simply hitting return should be the same as clicking OK.
i was trying to rule out the case, where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-16 01:17, patrick wrote:
hi all,
i have a firepod 1010 firewire soundcard, i am using linux / jack.
the new motherboard doesn't have firewire. what to do?
just yesterday i was searching for some expansion card and discovered
a whole
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-14 19:33, Hans-Christoph Steiner wrote:
- dynamic patching: i have this message:
editmode 1, mouse 12526 541 0 0, motion 12526 2000 0, mouseup
12526 2000 0 0, mouse 21 -500 0 0, mouseup 25 1999 0 0, cut,
mouse 12526 2000 0 0,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-15 16:22, Mirko Maier wrote:
hi hans-christoph,
I've found some deviations from previous pd versions in pd
0.43
(extended) (on Win XP):
- in previous versions, with the message pd open [patch.pd]
[folder]/;
you could open a patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-15 17:39, Charles Henry wrote:
Just create an object [$1], send it a bang, and it dumps out the
1st argument of the abstraction it's in.
this really only works for floats.
if the user calls [myabs moses], [$1] will evaluate to [moses]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-10 22:24, Hans-Christoph Steiner wrote:
On Oct 10, 2012, at 1:18 PM, Jamie Bullock wrote:
Anyhow, to conform to the policies and conventions of the Pd svn,
I've removed the headers and added the requisite instructions to
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-08 22:39, Rick T wrote:
Link to youtube video that shows the strange behaviour
http://www.youtube.com/watch?v=ZIlxj-MOR0c
would you mind explaining what the strange behaviour is?
personally i don't feel very interested in being directed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-09 10:03, Rick T wrote:
I added the trigger like you suggested to see if it would help, but
the strange behaviour still occurs, granted it is most likely that
I wired something incorrectly. They say a picture is worth a
thousand words
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-09 10:03, Rick T wrote:
* i also attached the pd file*
after a quick look:
- - always, i repeat: ALWAYS, use [trigger] when you have a message
fan-out (one outlet connected to multiple inlets)
- - it would be better to construct your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-09 10:03, Rick T wrote:
1) moses and cup don't always start incrementing and filtering when
the patch is enabled.
because the happen to miss your threshold.
2) When the moses and cup section do work, after the pd dsp 0
command is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-08 17:12, Hans-Christoph Steiner wrote:
[ezdac~] is part of rradical, which was removed because it had no
maintainer and had bugs. Try [output~]. I don't know mux~,
perhaps it was also in a library that was removed because of being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-04 04:37, Epic Jefferson wrote:
Other than being crazy small, i encountered a problem with your
instructions.
when i entered: debuild -uc -us -bash: debuild: command not
found
# aptitude install devscripts
debian lacks the handy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-04 05:38, Ed Kelly wrote:
Thanks IOhannes, So there is some sloppiness in Windows, which is
hardly a surprise since it's not created with the integrity of a
*nix system.
to be honest, this is not an integrity-defeating sloppiness in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-03 11:18, Alexandros Drymonitis wrote:
Hi all, I'm trying to get pairs of two out of a list using two
[list split] (I tried to reproduce the patch with ASCII, but it's
getting a bit complicated, so I've attached it).
how about using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Oct 3, 2012 at 12:49 PM, Alexandros Drymonitis
adr...@gmail.comwrote:
But if my list has an odd number of elements, then I lose the
last one, don't I?
no. that's what the last outlet of [list split] is for.
On 2012-10-03 11:58,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-03 13:55, Pierre Massat wrote:
Thanks for your help, it worked. I hadn't actually installed Pd. I
used apt-get install pd (it only installed puredata-core),
instead of apt-get install puredata.
ah, i was wondering about that.
anyhow,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-03 15:06, Ed Kelly wrote:
Hi list,
I know you main devs have bigger fish to fry right now, but an
answer to (some of) my wierdness with Gem (in case you're
interested) -- the unable to save file: too many objects message,
and related
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-03 17:43, Jonathan Wilkes wrote:
- Original Message -
From: Miller Puckette m...@ucsd.edu To: Cyrille Henry
c...@chnry.net Cc: pd-list@iem.at Sent: Wednesday, October 3,
2012 11:03 AM Subject: Re: [PD] array size (was Re:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-02 16:23, Hans-Christoph Steiner wrote:
I just added Pd-extended beta packages to apt.puredata.info for
Ubuntu oneiric and precise, both 32-bit (i386) and 64-bit (amd64).
That means that apt.puredata.info now has 32-bit (i386) and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-02 17:15, Miller Puckette wrote:
3. the upsampling inlet~ by default zero-pads its input. This is
incorrect as its DC gain is less than one. (Try using that as
input to a phasor~ for instance - bad surprise!) I want to change
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-02 17:15, Miller Puckette wrote:
2. There's no place in the pre-0.43 file format to alow specifying
individual box widths and font sizes; I put an f (=format)
message to the canvas object in 0.43 so that in 0.44 I can make it
set font
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-01 10:02, Charles Goyard wrote:
In these days of universal binaries for mac, the All platforms
wording is really misleading to newcomers.
we should prepare ourselves for the time when apple decides to reveal
their dark side and use the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-01 11:08, Ed Kelly wrote:
...when I try to create a Gem window. Looking at a previous post in
the archive, setting the environment variable GEM_SINGLE_CONTEXT to
1 does not change this. I'm stuck! GL screensavers are working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-01 12:14, Charles Goyard wrote:
Sure, thanks.
On a side note, it could be nice to have the link to the source
code for beta here:
https://puredata.info/downloads/pd-extended/releases/0.43.1
i added a generic link to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-01 12:35, i go bananas wrote:
if you just use $1 for something like 07, then it will cut off the
leading zero (which in this case, you need)
so might be best just to split everything into individual floats,
like:
[ 1 9 7 8 0 7 2 9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-01 13:23, Rick T wrote:
Thanks for the info but two issues that pop up when I try this are
1) when I use zexy date and time object there's no option for
leading zeros
so you can hook the [makefilename %02d] directly to [date]/[time].
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-01 15:42, Hans-Christoph Steiner wrote:
Besides, the source link you added is pointless and misleading
because there is no source tarball on the 'latest' listing. Please
remove it.
removed. sorry for any inconvenience.
btw, isn't [1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-12 12:30, Olivier Heinry wrote:
- or you have to setup a DHCP server on your mobile web server.
*Big
mess* if there's already a DHCP server on the network
(likely).
Well, as a secondary server, *should* work fine
secondary DHCP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-27 14:45, Roman Haefeli wrote:
There is also a work-around by using [readsf~] within an upsampled
subpatch. Also this work-around has been discussed several times on
this list, so I probably don't need to give any more hints.
probably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
last night hans and me finally setup a replacement machine for
apt.puredata.info[1], the ultimate source for Pd-extended on
Debian-based systems (Debian, Ubuntu, Linux/Mint,...)[2].
it is now hosted on the puredata.info portal/mailinglist server,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-25 23:53, ronni montoya wrote:
I forgot to mention that my patch has its gui elements in
different windows . so i was wondering : if its possible to
control the size and position of a group of windows or subpatches
from the language?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-25 22:22, Jonathan Wilkes wrote:
If you use Pd-l2ork there is no need for dirty hacks.
Using...
[list append $@]
afaik, this is standard Pd-extended.
fgmadfr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-26 17:58, Jonathan Wilkes wrote:
Can somebody confirm this? Because the patch is still open on
the tracker:
i'd like to keep it open for Pd-vanilla.
fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-04 22:41, Miller Puckette wrote:
Pd vanilla starts and quits in 0.2 sec total. (1.6 gHz Core 2) --
without GUI it can be done in about a millisecond (so you can use
Pd in a batch process and run it thousands of times if you want :)
-- I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-05 12:21, Ed Kelly wrote:
What is logpost? Is this a new (Pd-0.43) thing - I started with
Ubuntu studio installs of 0.42
yes, it's a 0.43 thing.
fgmasr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-03 20:10, Thomas Grill wrote:
Am 03.09.2012 um 17:44 schrieb IOhannes m zmoelnig:
curly braces are reserved in tcl (the language pd-gui is written
in). displaying a { will make pd-gui wait for a matching },
and while it does so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-04 05:08, Jonathan Wilkes wrote:
Hello serg, I made an attempt to build a search engine awhile
back: http://puredata.info/Members/jancsika/searchandbrowseplugin
would you mind adding that to the download section?
fgmasdr
IOhannes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-04 18:36, i go bananas wrote:
after more than 10 years, i still find it amazing that pd vanilla
doesn't have the following:
1) proper builtin resonant low and highpass filters. lowpass at
least, come on!
what's wrong with using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-08-30 20:12, Roman Haefeli wrote:
all the patches are already applied, so no need to do that
yourself.
Debian wheezy [1] and Ubuntu Precise [2] both still have 0.42-1,
which AFAIK is a version without the linking order patch. Or am I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-03 00:19, ?? wrote:
Dear list !
Where can I find the most complete PD-objects and commands
reference, please ?
right click on the object.
select help.
And why it is not on the main site - puredata.info ?
because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-03 12:16, ?? wrote:
Thankyou for your list !
\\ I know, although it's never actual.
- Why ? I mean that if I don't know all the objects by memory, and
I need some function to be done - I need easy search by categorys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-03 16:59, Paul Gruendorfer wrote:
hi, thanks for your reply - but that locks up pd.
it only locks Pd if you are printing the character via pd-gui (either
print to console or via a symbolbox)
that's also the reason why it is prohibited to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-08-30 11:35, Jack wrote:
Hello Roman,
Thanx for your answer.
Le 30/08/2012 08:50, Roman Haefeli a écrit :
Hi Jack
I'm not really knowledgeable about Makefiles and C code, but I
assume you're trying to patch not the exact same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-08-30 17:12, august wrote:
Sorry for taking so long to get to this.
Can you point me to instructions on how to use the pd-extended
template?
https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals/template
and no, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-08-20 22:41, Hans-Christoph Steiner wrote:
I've updated the builder matrix for clarity.
http://puredata.info/docs/developer/PdLab Please correct if any
mistakes. Right now the greatest need is to re-establish the
autobuild master as the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-08-07 16:45, Johanna Nowak wrote:
* kristof lauwers p...@kristoflauwers.domainepublic.net [2012-08-07
16:42]:
If you have enough ram, you could also load all soundfile data
into 28 tables, and read from those using tabread4~ or even a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-08-19 18:12, Björn Eriksson wrote:
Hello, earlier today a thought just popped up... and maybe it´s
already done, and maybe it´s not even something that relates to Pd
mainly.
have you looked at Pd-graz' blind date[1]? originally we used a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-08-02 16:03, august wrote:
If it is working on someones'12.04 I'd gladly know!
If you happen to run Ubuntu 12.04 and want to test
[readanysf~], I might be able to help out.
[readanysf~] compiles pretty well, if you have the good
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-30 01:09, FernandoG wrote:
Hi
I need to read data from a text file, i am triyng to use textfile
object to read a plain txt, but always get this error:
error: filexx: can't open error: filexx: read failed
i read there was a bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-30 17:53, FernandoG wrote:
thanks IOhannes for answer :)
I solved the problem, the textfile-help.pd file have to be in the
same path than the textfile. Now is working
But i have a new problem, because i need to read text as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-24 09:34, Lorenzo Sutton wrote:
This is a known limitation with [tabread4~] and [tabread~] and pops
up every now and then [1] (it could probably be useful to mention
it in [tabread~] help).
it is mentioned in the help-patch for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-19 12:43, Duncan Speakman wrote:
I have made an init.d script to start and stop pd. This works fine
in an ssh console. However when the script is invoked by the
runlevel startup sequence ie rc5.d/S99puredata, pd complains thus:
pd:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-17 17:46, IEM - network operating center (IOhannes m
zmoelnig) wrote:
due to a scheduled network maintainance, puredata.info and
associated services (including the pd related mailinglists) will be
offline tomorrow, wednesday starting
due to a scheduled network maintainance, puredata.info and associated
services (including the pd related mailinglists) will be offline
tomorrow, wednesday starting at 10:00 (CEST).
we hope to be online again within two hours.
sorry for the inconvenience.
fgasdr
IOhannes
--
IEM - network
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-11 04:14, José Rafael Subía Valdez wrote:
Actually, that lib is a bunch of externals so declare doesnt
exactly
to avoid confusion, i want to add that list-abs is a bunch of
abstractions.
iirc, declare's -lib flag might not work as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-10 05:53, Seiichiro MATSUMURA wrote:
Hi,
I try to do the similar thing, capturing from pix_video, saving a
specific frame of [pix_buffer] to jpg files. However, the color
space and the resolution of saved jpg file is changed. Even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-05 15:41, Sebastian Dorda wrote:
It took my a while to figure this out but now it works. Thanks for
the hint.
Now I use a netreceive with an empty message box. To send a bang to
test123 I transmit the following via tcp from the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-09 08:43, Richie Cyngler wrote:
Hi All,
I'm planning on using Pd for an installation in Melbourne in a
couple of weeks. It's running fine, Pduino working, sensors
working. I'm just wondering is there is a object (or series) of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-09 12:44, Richie Cyngler wrote:
Thanks for all the great answers.
So I found sleep/shut down scheduler in the Energy Saver menu of
OSX System Preferences. If need be I should be able to just use
that.
However if I want to kill Pd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-05 01:19, João Pais wrote:
hi, any news on this?
i'm unaware of anybody waiting for more user input.
fgamsdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-04 13:14, Roman Haefeli wrote:
Keeping the thread talking to the audio back end always running has
some advantages:
* The audio card cannot be stolen by other softwares while DSP is
off * A cycle of turning DSP off and on is much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-02 23:19, Iain Mott wrote:
Forgot to mention i'm using Ubuntu 11.10 and the video files are 30
fps with the codec H.264 / AVC
Also, while sending an auto 1 message to pix_film gives smooth
playback, the file plays perhaps 30% slow.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-03 18:36, Iain Mott wrote:
On Tue, 2012-07-03 at 09:15 +0200, IOhannes m zmoelnig wrote:
Gem is 20fps you will play the file at a reduced speed. the
simplest solution is to raise Gem's framerate.
as others have pointed out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-01 22:14, Funs Seelen wrote:
Hi list,
I'm happy to present my first external named [m2f_vst].
cool.
two remarks:
- - i guess most people will not associate variable semi tone with
vst, but something that involves proprietary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-21 00:25, Julian Brooks wrote:
aptitude install puredata So now aptitude gets as far as 'Setting
up puredata (0.43.2-3)'. Then nothing from any of the 3 options
above...
hmm,
$ dpkg -L puredata-core | grep bin
/usr/bin/puredata
so if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-21 11:52, Julian Brooks wrote:
Hi again,
dpkg question: dpkg -L puredata-core | grep bin (gives this)
/usr/bin /usr/bin/puredata
/usr/share/puredata/doc/5.reference/sigbinops-help.pd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-20 00:26, Patrice Colet wrote:
Hello,
in a dynamic GUI patching project, I'm using a bang that would
destroy itself
destroying itself is soemthing that Pd helps a lot with: if you have
an object destroy itself, Pd will destroy itself
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-20 11:53, pie...@314r.net wrote:
Hi all, I would like to know if there is a way to record a
[gemframebuffer] into a [pix_buffer 1000] my goal is to be able to
record a gemchain animation (5 seconds maybe) and replay it
(forward,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-20 12:54, pie...@314r.net wrote:
ok thanks, I will stay with [pix_snap] for now, on a good computer
it could works,
good computer might help or not. more important is the gfx-card.
also, if you can live with a slightly async transfer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-20 13:42, Patrice Colet wrote:
I don't think there is a need in iemguts for that, in attached
example we see a bang destroying itself by clearing the patch, it's
working perfectly, many other features that should work,
particulary in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-20 14:48, Julian Brooks wrote:
Hi all,
oops: ALSA cards not reported in order? oops: ALSA cards not
reported in order? audio input devices: 1. HDA Intel (hardware) 2.
HDA Intel (plug-in) 3. Hammerfall DSP (hardware) 4. Hammerfall DSP
201 - 300 of 2142 matches
Mail list logo
