On 04/05/2014 03:05 PM, Rafael Vega wrote:
> I found and fixed a bug in oggread~ that is windows specific. The fix is a
> one liner in oggread~.c (details in previous thread).
>
> I thought the central place for externals code was the SVN "community
> repo"at [1] but the comments below confuse me.
On 03/24/2014 06:54 PM, Jonathan Wilkes wrote:
> Here's errata for the first part of the tutorial on building externals:
thanks.
i'll update the tex files.
gfmr
IOhannes
signature.asc
Description: OpenPGP digital signature
___
Pd-dev mailing list
Pd-
On 03/24/2014 02:56 PM, Antoine Villeret wrote:
> hello,
>
> the free method seems to be called when the object is deleted from the
> canvas.
>
> is there a similar method called on Pd quit ?
no.
see http://sourceforge.net/p/pure-data/patches/82/
fgsdr
IOhannes
signature.asc
Description: Op
On 03/24/2014 02:22 PM, Funs Seelen wrote:
> Hello all,
>
> While reorganizing my code a question about memory management in Pd arose
> in me. If I allocate memory within the constructor space, do I have to free
> this myself?
yes
> If yes, how or where should I do this?
the destructor is calle
On 02/23/2014 03:58 PM, Dan Wilcox wrote:
> So would we remove those older implementations or transfer the other OS
> implementations into newer plugins? Or has that already been done for Linux &
> Win?
>
it has already been done for all platforms (also on OSX - e.g.
videoDarwin, filmQT,...)
wh
On 02/23/2014 01:46 AM, Dan Wilcox wrote:
> Just to confirm what Iohannes, et al. already know. pix_filmDarwin,
> pix_movieDarwin, pix_recordQT, & pix_videoDarwin need to be updated to use
> the newer Apple APIs: QTKit or AVFoundation. I've done an AVFoundation app
> already and we're using QTki
On 2014-01-11 01:08, Thomas Mayer wrote:
> So: Is 32-Bit on Mac OS X still around?
>
due to QuickTime issues, Gem on OSX is still 32bit only. this means that
whoever wants to run Gem on OSX, will need to use a 32bit version of Pd
and not being able to run a 64bit-only purest json.
admittedly thi
On 2013-11-19 17:26, Pierre Guillot wrote:
> Hi,
>
> I would like to know the inlets and outlets which are connected to my
> object.
check [canvasconnections] in iemguts.
> This information could be useful in the dsp method.
hmm. in general i would say that your object design is somewhat broke
On 2013-11-16 00:10, Thomas Mayer wrote:
> So, for objects that need a special character converted to hex, the
> setup function must be called setup_, while for other objects
> the setup function must be called _setup.
>
> This is kind of confusing.
yes, but it's the way it is.
the "_setup()" na
On 2013-11-14 23:44, Thomas Mayer wrote:
> Hello,
>
> I am currently documenting and refactoring the code of PuREST JSON to be
> consistent, but I seem to be unable to rename setup function from
> setup_json0x2dencode to json_encode_setup, as after renaming, I get the
> following error:
>
> error
---
** [patches:#517] Use all default search-paths for [declare]'s stdlib/stdpath**
**Status:** open
**Labels:** path
**Created:** Fri Nov 08, 2013 01:54 PM UTC by IOhannes m zmölnig
**Last Updated:** Fri Nov 08, 2013 01:54 PM UTC
**Owner:** Miller Puckette
the [declare] object allo
On 08/26/13 22:25, Jonathan Wilkes wrote:
> Can someone with svn access make the attached change to
> doc/pddp/bang-help.pd for me?
committed.
>
> I get the following error when I try:
> svn: Commit failed (details follow):
> svn: Authorization failed
>
> It doesn't prompt me to enter my p
On 08/13/13 23:39, Hans-Christoph Steiner wrote:
>
>
> Ideally, the pd-extended build system would name the executable properly, but
> it currently does the wrong thing. For the packaging, I think the best thing
> to do right now is to use a debian/install file to install the file as
> usr/bin/p
On 08/11/13 15:03, Kaj Ailomaa wrote:
> Never mind. I found an option during configuration to solve this
> problem.
>
whatever you are doing, you might also want to check out how we do this
in the "puredata" package (where "pd" is renamed to "puredata")
fmdsr
IOhannes
signature.asc
Descripti
---
** [patches:#513] automake build fixes**
**Status:** open
**Labels:** puredata 0.45
**Created:** Tue Jul 02, 2013 10:37 AM UTC by IOhannes m zmölnig
**Last Updated:** Tue Jul 02, 2013 10:37 AM UTC
**Owner:** Miller Puckette
after the latest updates in the puredata git repository
(moving this over to pd-dev)
On 06/15/13 09:21, Joel Matthys wrote:
> Hi Hans.
>
> The Makefile fails for Android on Linux 64 bit. I tracked it down to
> line 149:
>
> $(NDK_BASE)/toolchains/$(NDK_ABI)*-$(NDK_COMPILER_VERSION)/prebuilt/$(NDK_UNAME)-x86)
>
>
> should be:
>
> $(NDK_BASE)/toolch
On 06/04/13 08:59, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
so while we were busy making a lazy consensus on how to deal with the
sf upgrade plans, sourceforge has upgraded the repositories for us.
afaik, this changes all the links to checkout/update (SVN) and
c
On 03/21/2013 21:22, IOhannes m zmölnig wrote:
> On 03/21/2013 21:02, IOhannes m zmölnig wrote:
>> "inlet: expected 'pointer' but got 'pointer'"
>
> so having a short go into m_class.c, it seems indeed that the
> c_pointermethod is called from withi
On 03/08/2013 21:48, Jonathan Wilkes wrote:
>
> It is currently difficult to control audio settings programmatically from
> within a
> patch. Users might want to do the follow
not really, as there has been the "mediasettings" library around for
about two years.
i think it already gives you acc
On 02/28/2013 23:25, András Murányi wrote:
> Hi list,
>
> I've recently built miXed/toxy for pd-l2ork successfully but now I've run
> into errors with pd-extended. The errors concern tot.
> I've noticed that they are not the same version (see the diff below),
> however copying the l2ork one over t
On 02/18/2013 21:07, Hans-Christoph Steiner wrote:
>
> As far as I can tell, zexy is unbuildable on Windows unless you have the
> complete Pd source and you have built that source.
zexy has been built on windows since 1999, without having the need to
build Pd yourself.
that was long before i sta
just in case,enybody was wondering about the beginning of this conversation.
fgmasrd
IOhannes
Original Message
Subject: pd-gui's tests and Qs on singletons
Date: Tue, 18 Dec 2012 20:00:35 +0100
From: IOhannes m zmölnig
To: Hans-Christoph Steiner
hi hans,
so i did a n
On 12/18/2012 21:24, IOhannes m zmölnig wrote:
On 12/18/2012 20:48, Hans-Christoph Steiner wrote:
I remember that part of the code being a pain to get right thru all of
the possibilities... remember, Windows and probably even GNOME are
going to behave differently from XFCE and probably each
On 12/18/2012 20:48, Hans-Christoph Steiner wrote:
On Dec 18, 2012, at 2:01 PM, IOhannes m zmölnig wrote:
hi hans,
so i did a number of tests, and of course found one case, where my solution did
not behave as it should :-)
starting one pd and then one pd-gui, would result in having 2
On 12/18/2012 20:28, Hans-Christoph Steiner wrote:
autotools works with MinGW, except with ASIO. It builds with ASIO, but doesn't
make sound last I checked. That was a long while ago.
thanks for the clarification.
i guess i have to download the asio-sdk at some point...
fgmadsr
IOhannes
On 12/18/2012 19:34, Hans-Christoph Steiner wrote:
It seems to be MinGW-only. I just submitted a patch to get the makefile.mingw
working again.
is autotools still not working with mingw?
fgmasrd
IOhannes
___
Pd-dev mailing list
Pd-dev@iem.at
http
On 12/18/2012 04:40, Hans-Christoph Steiner wrote:
I think this approach works.
thanks
The patch you provided seems totally untested, as in not even compiled on
GNU/Linux or Mac OS X. It includes the _close() function in sys_close() which
only works on Win32 and it gives this warning when
On 12/16/2012 21:01, SourceForge.net wrote:
I've been marking bug reports as "fixed" when I add a patch that fixes the
bug.
i would expect that any "patch" that addresses a given bug will "fix"
it, so marking the reports as "fixed" seems to be somewhat unnecessary.
i guess the original idea
On 12/09/2012 17:31, Hans-Christoph Steiner wrote:
Would it be possible to provide an alternative implementation for the same API
as a built-in using this? So for example, an alternate Jack or ALSA
implementation in a loadable module?
(iirc) the current implementation allows us to overwri
On 11/22/2012 04:31 AM, Miller Puckette wrote:
To pd-dev -
I might be missing something... under Fedora 17 (the newest I believe), when
I try to build Pd using the "new build system" I get:
This is off a clean git checkout. Are there build-system patches out there
that I should be applying fir
On 11/20/2012 09:33 PM, Jonathan Wilkes wrote:
Basically combining the core functionality of the "find" method with the
"delete"
method.
as you already noticed, the desired functionality can be achieved with 2
separate objects, one for deleting one for finding.
in general i would think twice
On 11/20/2012 04:44 AM, Hans-Christoph Steiner wrote:
On Nov 19, 2012, at 5:20 PM, IOhannes m zmölnig wrote:
On 11/19/2012 07:33 PM, Hans-Christoph Steiner wrote:
The new build system will never work for MSVC,
why?
what keeps you from using autotools with msvc?
I have no particular
On 11/19/2012 09:28 PM, Jonathan Wilkes wrote:
- Original Message -
What does [local foo] do different than [declare foo]? I assume with your
i would mainly object to [declare foo] because it seems to impose a
hierarchy between the things you can [declare] and pushing global/local
nam
On 11/19/2012 07:33 PM, Hans-Christoph Steiner wrote:
The new build system will never work for MSVC,
why?
what keeps you from using autotools with msvc?
(sure, autotools require mingw/cygwin to run the bash-script (and once
you installed mingw/cygwin, installing gcc is easy enough), but wheth
On 11/15/2012 08:16 AM, Hans-Christoph Steiner wrote:open to anonymous)
That's my way of reminding you that I think we should turn off anonymous
submissions. :-)
i'm aware of tyour intentions, but i don't see the point.
spam eats energy, exactly because of people reacting like that.
spam also
On 11/15/2012 01:34 AM, Jonathan Wilkes wrote:
Here is a quick snapshot of a bundle of classes I'm working on to
provide a standardized way to get properties from parts of pd
that aren't "objectified":
[canvasinfo] get the properties of a canvas
[pdinfo] get info about the running Pd instance
On 11/14/2012 09:07 PM, SourceForge.net wrote:
Assigned to: IOhannes m zmölnig (zmoelnig)
thanks for assigning that to me.
however, i usually do cleanup all those bogus tickets whenever i notice
them (and since i regularily read the pd-dev list, i get notified pretty
soon), so you could
On 10/25/2012 06:31 PM, Hans-Christoph Steiner wrote:
The output method Im concerned with is pdp_glx but I remember same problem
exists for pdp_xv...
#1 i guess that the vanishing cursor is a feature rather than a bug
(ever watched a visual performance where a system-alert popped up on the
On 10/23/2012 06:30 PM, Miller Puckette wrote:
Hi all -
block sizes in subpatches are restricted to being a power of two multiple
or submultiple of the containing patch. So the only context in which a
non-power-of-two blocksize is allowerd is if it's specified in the top-level
patch.
Then, of
On 10/20/2012 04:17 PM, Hans-Christoph Steiner wrote:
I'd happily ditch it if there was a drop in replacement. For example, I've
had many students come to me with the most popular Processing<--> Pd starter
patch, and its based on oscx. If it wasn't include, that patch would not work
at all.
On 10/20/2012 01:26 AM, Hans-Christoph Steiner wrote:
I'm not going to take on the maintenance of those patches, so just copying
them into Pd-extended is not an option. I'm think Pd-extended should have an
'oscx' compatible library , and 'oscx' is already there, tested, etc.
"etc" means "known
On 10/19/2012 08:21 PM, Hans-Christoph Steiner wrote:
That's good to have, please post and maintain that somewhere, like maybe in
the 'osc' lib. But its not yet a replacement because at the very least its
not deployed.
i honestly dunno what you mean here.
imho, if you want to make changes to
On 10/19/2012 03:02 PM, Hans-Christoph Steiner wrote:
why would you want to keep OSCx alive?
i would rather entirely remove this buggy and un-maintained (as in: upstream,
not within PdX) library from any distribution.
Its still widely used and still the easiest way to use OSC, albeit in a
limit
On 10/19/2012 03:02 PM, Hans-Christoph Steiner wrote:
and i don't get the point of replacing "OSCx" by "oscx".
Every other library folder in externals/ is all lower case.
which is a good rule for all new libraries.
imho, it's a bad idea to change a given name of an old library that is
"st
On 10/19/2012 06:08 AM, Hans-Christoph Steiner wrote:
Any objections? Shall I go with lazy consensus on this one?
.hc
On 10/16/2012 07:17 PM, Hans-Christoph Steiner wrote:
Hey all,
I was tired of dealing with a cryptic ./configure, so I converted OSCx
to be based on the Library Template.
seems like i missed some pd-mails in the past few days...
On 06/06/2012 08:23 AM, IOhannes m zmoelnig wrote:
apart from that, i think the "right" way would be to build Pd
using the autotoolchain. afair, some tweaks are required (alas!),
which ought to be documented in the mailinglist archives (
On 02/27/12 19:34, Hans-Christoph Steiner wrote:
If post(), error(), etc. are your examples, then verbose() should have no level
argument, just the fmt, then it could post at level 4. That makes sense to me.
If verbose() is meant to post messages at varying levels, then it should use
the sam
On 01/28/12 03:45, Hans-Christoph Steiner wrote:
Any word on this? I'd like to import zexy into the pd-extended/release
branch now, but if you're going to do a 2.2.6 release soon, I probably
can wait.
thanks for the reminder.
no i don't think that i will spend much time in the next days for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/30/2011 09:13 PM, IOhannes m zmölnig wrote:
>
> it is exactly my suggestion to standardize it to lib$(LIBNAME).$(EXT).
>
to be more precise, my suggestion basically contains exactly 2 suggestions:
- - rename *_SOURCE to *_SOU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/29/2011 04:35 PM, Hans-Christoph Steiner wrote:
> These things are really all by design. This makefile template is not trying
> to be all things to all people, but instead provide the easiest solution for
> 98% of the cases. By not handling t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/2011 01:29 AM, Hans-Christoph Steiner wrote:
> I committed the change to tkwidgets and the template/Makefile.
>
i tried to use the new template/Makefile for this feature and noticed a
few issues:
- - object sources are called SOURCES, wherea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/28/2011 09:58 PM, Roman Haefeli wrote:
> Hi Hans, IOhannes
>
> I don't have a clue what MSG_DONTWAIT is. I think I need some help (from
> IOhannes?) to get this one fixed.
it's a (linux-specific?) extensions for non-blocking socket receivers.
t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/2011 06:31 PM, Hans-Christoph Steiner wrote:
>
> If pd/src/m_pd.h is the only thing that loads pd/src/config.h and m_pd.h
> does #include "config.h", this is not a problem.
>
> "GCC looks for headers requested with #include "file" first in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2011 11:03 PM, Hans-Christoph Steiner wrote:
> Perhaps your zexy scripts are modifying the build environment? It first
why do you think so.
have you read my email?
fmsdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Lin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2011 09:18 PM, Hans-Christoph Steiner wrote:
>
> On Oct 5, 2011, at 12:45 PM, IOhannes m zmoelnig wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 2011-10-05 18:16, Hans-Christoph Steiner wrote:
>>>
>>> On Oct 5, 2011, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2011 12:40 PM, katja wrote:
> On Tue, Oct 4, 2011 at 11:38 AM, IOhannes m zmoelnig wrote:
>
>> the proper way is to use CPPFLAGS="-DPD_FLOAT_PRECISION=64",
>
> But now you undo the CPPFLAGS as defined in the makefile. I didn't
> know how to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/2011 10:00 PM, lluis gomez i bigorda wrote:
>
> hi list,
>
> it's a long time hope you all are doing well :)
>
> sorry no previous experience with Tracker:
> just a question, what's the suposed way to act in such a tracker task ?
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2011 08:23 PM, Hans-Christoph Steiner wrote:
> I tried --disable-rpath, but it said it wasn't a ./configure option.
> Its a recommended thing for MinGW:
the "--disable-rpath" flag comes from the macro AC_LIB_RPATH (currently
not used in zexy,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2011 06:08 PM, Hans-Christoph Steiner wrote:
>
> pddev@windowsxp-i386:~$ svn --version
> svn, version 1.6.1 (r37116)
>compiled Apr 11 2009, 12:07:06
thanks.
however, i actually was trying to ask for the svn-revision of externals/
(which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2011 05:20 PM, Hans-Christoph Steiner wrote:
>
> So with all the hassle over symlinks, there is a different issue
> stopping things on MinGW.
and how does this relate (e.g. timewise) to your other mail saying "Zexy
installing .a instead of .
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2011 05:20 PM, Hans-Christoph Steiner wrote:
>
> So with all the hassle over symlinks, there is a different issue
> stopping things on MinGW. This seems to be the exact same issue as Gem
> was having. You can see the environment of the buil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2011 05:17 PM, Hans-Christoph Steiner wrote:
> platform. I'm not sure how Cygwin's svn handles symlinks, all I am
> saying is that managing symlinks in SVN is not really useable if you
> want to target Cygwin and/or Windows.
afaik, managing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2011 04:50 PM, Hans-Christoph Steiner wrote:
>
> Now I see the root of the unfold-help.pd issue, zexy relies on symlinks
> that are checked into svn. That'll work fine on UNIX, but is very
> unpredictable in Windows. For example, a Windows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2011 10:43 PM, Jonathan Wilkes wrote:
> Pd Vanilla is 3-clause BSD, and according to IOhannes so is the stuff on the
> patch
> tracker.
just for clarification: i did not intend to say that.
instead i wanted to say that "stuff" in the patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2011 03:07 PM, Hans-Christoph Steiner wrote:
>
> Ah, ok, that changes things. So you are sure there isn't a way to make
> this work?
on, i'm not sure. i only reported issues i came across.
> If so, do you think there are other shared lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/26/2011 06:52 PM, Hans-Christoph Steiner wrote:
>
> IOhannes and I were discussing how to load shared code for a libdir on
> IRC. The sticking point is that Mac OS X seems to require dylibs to
> have a hard-coded path. IOhannes posted a test l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/19/2011 08:33 PM, Patrice Colet wrote:
> hello, I've attached the patches that make working libtools with msys, but
> there is something I couldn't resolve,
>
> all the PD__CHECK shows synthax errors so those lines are under comments,
> m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 01:04 PM, katja wrote:
> Since I am not familiar with this part of Pd code, my proceedings are slow
> and I've not found the time to scan s_audio_jack.c, s_audio_alsa.c etcetera
> for similar issues. Yet, on the dsp side of things, I fee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2011 02:15 AM, katja wrote:
> I was looking for a suitable spot in the code to do this. First looked at
> dac~, but since there may be many dac~s instantiated this is not most
> efficient. Then I found sys_send_dacs(), where the integrated sam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2011 11:11 PM, Hans-Christoph Steiner wrote:
>
> like you've covered that already. As for 64-bit floats to output, a
> quick hack to get things working is to just hammer samples down to
> 32-bits...
>
i don't think that's such a great idea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/21/2011 09:26 PM, Louis-Philippe wrote:
> Hi PD-Dev Peoples,
>
> I was wondering how I should deal with async callbacks inside an external?
> What I have in mind:
>
>
>1. message sent to external inlet
>2. external proceed to trigger s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/14/2011 11:55 PM, Jonathan Wilkes wrote:
> I've got a working tooltip prototype going, and I just noticed that all the
> list classes screw up things on the tcl side, because with "list append" (for
> example) it suddenly looks like there is on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/12/2011 10:18 PM, Hans-Christoph Steiner wrote:
> +#else
> +# warning "No dynamic loading mechanism specified, libdl or WIN32
> required for loading externa
> #endif
"#warning" is a gcc extension, so it's not very portable.
btw, "#error" is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/01/2011 06:24 PM, Hans-Christoph Steiner wrote:
>
>> the trick to use g++ for linking, is to use a dummy .cpp file, so
>> autotools will automatically choose g++.
>>
>> something like:
>>
>> nodist_EXTRA_pd_SOURCES=
>> if PORTAUDIO
>> nodist_EX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/01/2011 08:40 AM, Patrice Colet wrote:
>
>> needs to figure out how to do the final linking using g++ to link the
>> C
>> ++ ASIO files and C files from the rest.
>>
>
> why not using cc for compiling portaudio files,
because you need a c++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/22/2011 01:31 PM, Andrew Hassall wrote:
> or could it just be other problems with the audio setup (I still
> haven't got the pd audio settings correct on ubuntu, but it still
> manages to process input from the mic).
given that valgrind produces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2011 05:11 PM, Hans-Christoph Steiner wrote:
>
> That is not quite a good analogy. The existing method was there: a
> folder that was searched by default called path/to/pd/extra. You did
> not need to specify -path path/to/pd/extra. ~/pd-e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/12/2011 01:46 AM, Hans-Christoph Steiner wrote:
>
> Part of the idea is that people can make CPU-optimized versions of
> 'vanilla' and load them as they need them. So they shouldn't be locked
> in to using 'vanilla', or I would have just left t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/19/2011 05:29 PM, Ingo Randolf wrote:
> Hello & thank you for the answer.
>> b) meant for the source release(!) rather than an SVN-snapshot
>>
>> the latter means: it is considered bad style to put anything "generated"
>> (mostly binaries, but al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/19/2011 10:58 AM, Ingo Randolf wrote:
> and... another post... ;)
>
> i have a question to the svn-repository...
>
> in the subfolder ./trunk/pd i can read the INSTALL.TXT file... which tells me
> to make a ./configure in /trunk/pd/src ...
t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/2011 01:56 AM, David Doukhan wrote:
> Hum... it seems my account has not been added yet...
added now.
fgamsdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozde
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2010 04:54 PM, Hans-Christoph Steiner wrote:
>
>
> A 300 MB network buffer! That sounds scary.
>
i thought i made it quite clear that it is up to the user what they want.
i find it far more scary to tell people what the might want (e.g.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/09/2010 10:28 PM, Roman Haefeli wrote:
>
> @ IOhannes
> Though I like this 'stable'/reliable behaviour of iemnet's [tcpserver],
> I wonder what happens, if it keeps sending data to the unreachable
> client. Will it just go on and buffer everythi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/08/2010 09:10 PM, Hans-Christoph Steiner wrote:
>
> So the question is: should we remove pidip and unauthorized from the
> pure-data SVN?
>
are there any problems already?
are we talking about bullying and bashing on the sole grounds of "as fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/01/2010 06:16 PM, Hans-Christoph Steiner wrote:
>
> On Dec 1, 2010, at 12:00 PM, IOhannes m zmoelnig wrote:
>
>> this is such a fundamental thing that i'm sure there has to be an
>> elegant solution to this but i never came across one.
>> the P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/28/2010 10:17 PM, Martin Peach wrote:
> On 2010-11-28 15:57, Roman Haefeli wrote:
>
> That's another reason they should be in net instead of mrpeach: it seems
> that having my name on the folder inhibits others from improving the
> objects, so w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/22/2010 12:52 AM, Hans-Christoph Steiner wrote:
>
> To be pedantic, I'd say its _derived_ from the Makefile library
> template, not really based on it since you have organized the files into
> different directories. But it does seem to build as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/20/2010 08:02 PM, Hans-Christoph Steiner wrote:
>
> well yes, that's the idea of [closebang], no?
> i don't really understand what is tricky about it.
>
>> Well, it doesn't really seem to work. Or at least the [closebang] in
>> Pd-extended doe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/20/2010 05:59 PM, Matt Barber wrote:
>>
> 1) The ability, in vanilla, to dynamically delete individual
> instantiated objects without "dynamic mousing."
>
this can already be done with externals: see iemguts.
(i see that you say "vanilla"; howe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/20/2010 08:30 AM, Jonathan Wilkes wrote:
> > (And I think initbang
>> and closebang are totally different animals...)
>
> They definitely are very different.
>
sure.
i implemented both while i was at it :-)
> As for [initbang] - my only use h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/20/2010 12:37 AM, Hans-Christoph Steiner wrote:
>
> While I can't really comment on the implementation since i haven't
> reviewed it in depth, I can say that I am a fan of having the interface
> be a series of *bang objects over having a [loadba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/15/2010 08:36 PM, Hans-Christoph Steiner wrote:
>
>> If you look a little closer, you'll see that "motex" has been submitted
>> to Debian pkg-multimedia, and it no longer has a debian/ folder in
>> pure-data SVN.
>
i see (i haven't looked tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/15/2010 12:00 PM, pd-cvs-requ...@iem.at wrote:
> --
>
> Message: 4
> Date: Sat, 14 Aug 2010 21:02:41 +
> From: eighth...@users.sourceforge.net
> Subject: [PD-cvs] SF.net SVN: pure-data:[13794] trunk
> To: pd-...@i
On 06/15/2010 08:12 PM, Chris Niven wrote:
> I agree, it makes more sense for developers like myself who are only
> working on specific
> parts of the project, and aren't necessarily concerned with everything
> going on in the main
> tracker. It's hard to keep up with relevant discussions when your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> On Wed, 2010-06-09 at 22:09 -0400, Hans-Christoph Steiner wrote:
>>
>>
>> Until we get the 'puredata' package installing its extra stuff in a
>> separate dir from /usr/lib/pd, then its tricky to make 'pdextended'
>> use /usr/lib/pd. But once tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roman Haefeli wrote:
> Hi all
>
> posting. However, I thought it's worth mentioning those as well, so that
> forces might be joined. I have the impression, that similar problems are
sure
> worked on twice on two completely different ends.
that was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ivica Ico Bukvic wrote:
> Martin,
>
> Just tried the latest version and the problem with stuck port persists,
> suggesting that either Ubuntu is doing something funny or that the
> destructor is to blame.
>
if you quit Pd, the destructors are not pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hans-Christoph Steiner wrote:
>
> IOhannes probably overlooked that line when he was working on the new
> post stuff. I haven't looked at that code, so its just a guess. If you
> want to commit to the pd-gui-rewrite branch, I say go ahead.
>
i hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arnout Engelen wrote:
> On Tue, Feb 23, 2010 at 07:46:32PM -0500, Ivica Ico Bukvic wrote:
>> Hence, I personally feel going after JUCE or Qt still allows Pd to be as
>> platform-agnostic as Pd currently is (with the exception that these are
>> AFAIK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hans-Christoph Steiner wrote:
>
> Hey IOhannes,
>
> Are you planning on keeping iemguts in the next Pd-extended release?
i'm not planning anything.
(i also cannot make any promises on the stability of the API)
> Its included now.
cool.thanks.
m
1 - 100 of 155 matches
Mail list logo
