-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 p
-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
-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 :)
> -
-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-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 langua
-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)
C
-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
>
secondar
-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.
probabl
-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,
cour
-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 th
-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
> correctl
-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 downl
-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
-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
-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 6
-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 f
-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
wrote:
>
>> 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, Alexandros Drymoni
-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.
any
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-03 17:43, Jonathan Wilkes wrote:
>
>
> - Original Message -
>> From: Miller Puckette To: Cyrille Henry
>> Cc: pd-list@iem.at Sent: Wednesday, October 3,
>> 2012 11:03 AM Subject: Re: [PD] array size (was Re: arraysize)
>>
>> Pr
-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
-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-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 bein
-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 direc
-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 wor
-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 you
-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-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
>>
-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
-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]/;"
>>
-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] w
-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 a
-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: U
-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 w
-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 whol
-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
-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 "curren
-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
>
>
|/ Err?=(none)/R
-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 w
-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 i
-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 e
-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* s
-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 Mo
-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
-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-
Ve
-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 cou
-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
IOha
-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 ser
-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
-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
> imp
-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-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:
>
> http://markmail.org/message/ermo45obdxmad5b6#query:+page:1+mid:2m33uflrdcciugat+s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-07 12:02, Patrice Colet wrote:
>
>> De: "Alexandros Drymonitis"
>
>> 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 this i
-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-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-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 sept
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-15 17:03, Hans-Christoph Steiner wrote:
>
> The dates are fixed with the VIA festival, and CMU could only host
> PdCon in 2013 in conjunction with the VIA festival. So the
> question is, whether we should go ahead with first week of Octobe
-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:
> http://sourceforge.net/tracker/index.php?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-21 21:07, Anas Ghrab wrote:
> Hi all,
>
> The BiDi-plugin is aborted ?
no.
fdasfrt
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlD9
-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 t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-21 23:12, plutek wrote:
> hi all!
>
> simple question here... pix_image is giving me a "failed to load
> image" error. i'm certain the path/filename are correct, and i've
> tried both png and jpg. any ideas of why Gem isn't loading the
> im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-21 23:35, Martin Peach wrote:
> Wouldn't it be a good idea to settle on a graphics metalanguage
> rather than translating tcl code to qt or whatever?
>
that's exactly my point: creating a FUDI-style communication from
pd->gui, which can eas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-22 11:45, Anas Ghrab wrote:
> By the way... I'm using Pd-extended 0.43-4.
>
> --- Anas
>
> Le Jan 22, 2013 à 11:37 AM, Anas Ghrab a écrit :
>
>> So the release is not released ? :o)
>> http://puredata.info/downloads/bidi-plugin/releases/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-22 11:57, Esteban Viveros wrote:
> Now I can't conclude the compilation...
>
> I did: cd ~/pure-data/pd/src make -f makefile.mingw clean make -f
> makefile.mingw
>
> Something in jack.h ... I have this file in C:/Program Files
> (x86)/Jac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-22 12:04, IOhannes m zmoelnig wrote:
> On 2013-01-22 11:57, Esteban Viveros wrote:
>> Now I can't conclude the compilation...
>
>> I did: cd ~/pure-data/pd/src make -f makefile.mingw clean make
>> -f make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-22 12:21, Esteban Viveros wrote:
> Ok.. I will do that... But why until te make clean, yesterday, ir
> run the compilation?
good point.
my hint was merely an assumption what might be causing troubles.
in this case: are you sure you are usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-22 12:49, Leandro da Mota Damasceno wrote:
> So would it be an updated FUDI or an all new protocol?
>
it would be FUDI.
(no reason to update it)
fgamsdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-22 12:32, Anas Ghrab wrote:
> Thank you for the answer.
>
> I downloaded again Pd-extended 0.43-4 (I think that the one I had
> was a beta one). The BiDi works :
which platform are you on?
which BiDi-support are you referring to? Gem (whic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-22 16:30, Ivica Ico Bukvic wrote:
>
> Pd-l2ork indeed has its own folder (including pd-l2ork-externals in
> home folder and settings file). The conflict is in the /usr/bin/
> folder with binaries that share the same name but not necessarily
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-22 17:16, Ivica Bukvic wrote:
> AFAIK I use pd-l2ork exclusively, not pd. I f you find it anywhere
> that I'm not using that please let me know so I can fix it.
>
> I need to check whether pdsend/receive is indeed identical before
> making
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-23 09:49, Pierre Massat wrote:
> I don't know why it's working. I just hope the next update won't
> break that!
>
> So "-sounddev 2" should work for my card showing up as card 1 ?
> Incidentally, there are only two pages that I know of on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-23 10:22, Lorenzo Sutton wrote:
>> it seems your example is missing the newline (;\n). iirc I've had
>> a few pd lockups when sending lots of messages from Processing
>> without the newline.
> Good to know, and easy to add to the script. And
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-23 09:49, Pierre Massat wrote:
> Unless there's a better place on the web to learn about start-up
> flags, i think it would be a good idea to provide more details on
> the community website. I always find it frustrating when i have to
> spen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-23 12:45, Lorenzo Sutton wrote:
>
> On 23/01/13 10:28, IOhannes m zmoelnig wrote:
>> On 2013-01-23 10:22, Lorenzo Sutton wrote:
>>>> it seems your example is missing the newline (;\n). iirc I've
>>>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-23 18:08, Hans-Christoph Steiner wrote:
> On 01/23/2013 05:35 AM, Charles Goyard wrote:
>> Fero Kiraly wrote:
>>> What should be changed (,maybe in pd/src/Makefile.am ? ) to
>>> build a pd-ex binary with different name ?
>>>
>>> now it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-23 14:55, Sujay Mukherjee wrote:
> hi i am new to Pd
welcome.
please don't use generic subjects like "help" or "i have a question".
most people who write on this list either have a question or try to
answer one. imagine what would happen i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-24 11:19, Alexandros Drymonitis wrote:
> When trying to create a gem window on a beagleboard I get the
> following:
>
> error: GEM: Unable to create single buffer window error: GEM: Error
> creating const context error: GEM: A serious error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-24 12:15, Alexandros Drymonitis wrote:
> Well, I'm not aware of such details, to be honest. Since Gem is
> installed the Pd version my beagleboard has, I tried to do
> something with it. The objects are being created, but no gem
> window..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-24 13:26, Alexandros Drymonitis wrote:
> Is there a solution to this?
install a gfx-card that is openGL capable (which is not very
practical, though; so for now the answer is "no"; alternatives include
finding dmotd and asking him to publis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-28 09:55, Fero Kiraly wrote:
> when I run this command:
>
> git clone git://github.com/pd-l2ork/pd.git
>
> it is clonning... but l2ork_addons/spectdelay/spectdelay~ is
> MISSING ! (I totally dont understand how it is possibile)
>
> can an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-28 10:17, Fero Kiraly wrote:
> thats the thing !
>
> I dont have folders with ~
>
> What should I do ?
>
just to be sure: you don't have these folders even when doing an
$ ls -la
on the cmdline?
some graphical filesystem browsers will si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-28 11:10, Patrice Colet wrote:
> Hello,
>
> I'm using [pix_multiimage] into archlinux 64bit environment.
>
> When opening the helpfile, I've got this error message into pd
> console:
>
> GEM: Someone sent a bogus pointer to copy2Image
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-26 04:04, Hans-Christoph Steiner wrote:
> ? full unicode support, so Greek, Japanese, Korean, Chinese,
> Hebrew, Arabic, etc. works in patches, filenames, MIDI device
> names, etc.
doest this make the bidi-plugin obsolete or does it mean "h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-29 11:23, Alexandros Drymonitis wrote:
> I checked the help patch of [shell], but if I send a cd command
> for example, I don't think that something really happens. I
> actually would like to run a script from within Pd, but what I
> underst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-29 11:59, Alexandros Drymonitis wrote:
> I don't really understand the meaning of 'context' (not the actual
> word, but the way you're using it)..how are these contexts
> accessible? How are commands being executed when sent to the same
> ob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-29 13:56, Alexandros Drymonitis wrote:
> Ok, I understand the whole 'context', shell thing. I tried what you
> guys suggested in a terminal window and kind of got the picture.
> But the way [shell] works remains a mystery to me (even though
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-29 23:04, Hans-Christoph Steiner wrote:
>
> Select-all, then deselect the canvas, then cut then paste. That's
> how I do
or even better: use "undo" rather than "paste".
this allows the cut objects to stay connected with objects outside th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-30 09:44, Ivica Bukvic wrote:
>> Except in both cases you still lose the object state. Pd-l2ork's
>> tofront/back is the way to go if you can.
sure.
but you cannot in current Pd.
fgamsdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: Gnu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-30 13:59, Pierre-Olivier Boulant wrote:
>
> On 30/01/2013 13:46, Nicolas Montgermont wrote:
>>
>> a few comments though, (sorry if I miss previous discussions): -
>> is is possible to get rid of the french localization?
>
> rename or tras
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-30 19:07, Òscar Martínez Carmona wrote:
> 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 ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-30 22:40, Hans-Christoph Steiner wrote:
> A quick internet translations makes me think that I agree with
> what cyrille is saying. The preferences shouldn't be used for
> loading libraries, as they have been in pd and especially
> Pd-extend
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-31 09:30, Òscar Martínez Carmona wrote:
> Thanx for your reply IOhannnes, I'll check that out later (whenever
> I got home after work), the weird thing is that with other
> externals [tabplay~] or [readsf~] that worked just fine, is there
>
801 - 900 of 2363 matches
Mail list logo
