-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-20 15:27, Hans-Christoph Steiner wrote:
Hey Jonathan,
I'm guessing that you're the one filing all the bug reports about
help patches. I'm wondering what your goal is with filing them.
It seems that you're also committing stuff to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-09 02:18, Thomas Mayer wrote:
OK, so here is the question (and the tag):
http://stackoverflow.com/questions/14226869/how-to-keep-audio-and-video-gem-synchronised
On 08.01.2013 23:05, Hans-Christoph Steiner wrote:
Anyone on Stack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
quick question: is the osx10.5-ppc machine gone for good, or is it
likely to return?
the machine seems to be online, but i cannot login to it any more
(Permission denied (publickey)).
also jenkins hasn't built on that machine for a while now.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi.
recently i have added bidirectional text rendering support to Gem
(this basically means that arabic and hebrew strings will be correctly
rendered right-to-left).
however, this depends on the libfribidi library [1].
since there exist packages for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-09 14:15, IOhannes m zmoelnig wrote:
hi.
recently i have added bidirectional text rendering support to Gem
(this basically means that arabic and hebrew strings will be
correctly rendered right-to-left). however, this depends
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-10 16:48, András Murányi wrote:
On Wed, Jan 9, 2013 at 3:11 PM, Hans-Christoph Steiner
h...@at.or.atwrote:
Does Gem 0.93.4 in Pd-extended have support for this lib?
ah, i only answered hans on the chat, so:
bidi-support was added to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-14 12:50, Alexandros Drymonitis wrote:
Hi all,
hi.
this is probably best targetted at pd-dev (pd-list), but anyhow...
I'm trying to install some externals in Pd vanilla. Till now I've
managed to install the Gem library. But now I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-13 18:50, Jonathan Wilkes wrote:
but adding/revising code inside class_new would retain 100%
binary compatibility, whereas adding members to public structures
is a 100% guarantee to break binary compatibiliy.
And if I just put the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-14 19:04, Alexandros Drymonitis wrote:
Ok, installing command line tools did help, but didn't do the whole
job. I tried to install fink, and to be honest I'm not sure if
everything went well. I tried to install the zexy library again and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-22 19:52, Hans-Christoph Steiner wrote:
chaos.medien.uni-weimar.de is the actually hostname of that machine
and 141.54.159.89 is the IP. MacOSX106-x86_64.pdlab.puredata.info
just maps to puredata.info, so that's not right.
just for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-31 04:17, Hans-Christoph Steiner wrote:
The IP address has changed for macosx105-i386.pdlab.puredata.info
its now: 184.75.101.123
thanks. i've updated the DNS entry.
fgamsdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-03-07 11:14, Roman Haefeli wrote:
Hi all
I only noticed now that many of the iemnet classes crash Pd on
Windows XP. The problem seems specific to Windows XP. The crashes
cannot be reproduced on Windows 7.
thanks.
could you post a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-03-11 04:30, Jonathan Wilkes wrote:
not really, as there has been the mediasettings library around
for about two years.
No, it's still difficult to control audio settings
programmatically in Pd Vanilla, Pd-l2ork, and Pd-extended. Users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-03-27 21:12, Hans-Christoph Steiner wrote:
I think that a -noplugins flag is a no brainer, that should be
included. I'm still on the fence about adding the ability to
disable plugins via the interface. The model so far for installing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-03-27 22:06, Jonathan Wilkes wrote:
I think what Hans means is that it's very simple and easy for him
to maintain as the Pd-Extended guy. Got a handy plugin for
managing plugins? Throw it in this directory. Is it pretty
stable? He'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-05-28 07:08, Jonathan Wilkes wrote:
Ok, quick restatement of the problem:
How does one get Pd to just run in GNU/Linux for casual/sporadic
use cases? Like 1 fire up Pd to patch an idea with Firefox/music
player/other stuff sitting in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-05-29 06:12, Jonathan Wilkes wrote:
what works for me so far is: - - run jack as the native backend
on my desktop (jackd gets autostarted at login, and is running
throughout my session)
How do you configure jack to start at login?
i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-05-29 17:21, Jonathan Wilkes wrote:
Ok, sounds like you have two things: a) code that adds support for
pluggable audio/midi backends, and b) a pluggable portaudio
backend.
i have two things:
- - code (API+ implementation) that adds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-05-29 17:49, Jonathan Wilkes wrote:
- - converted all the existing backends to use the new API
(though they are still linked statically into the Pd-binary)
What did you have to convert?
check the git logs. (or read my answer on does the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-06-02 08:51, Jonathan Wilkes wrote:
Of course these are just the latencies in the settings-- I haven't
done the actual measurements yet.
it would be interesting to have actual measurements.
everything else is wild speculation.
fgmadsr
-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
clone/pull (GIT).
someone might want to update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-06-18 19:39, Hans-Christoph Steiner wrote:
In general, removing bits of code willy-nilly is a bad idea.
sure.
In this case, So follow what the comment there says: This
guarantees that patches will be pixel-exact on every platform.
this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-06-19 22:06, Hans-Christoph Steiner wrote:
What do you gain by removing in? I think we really need to stop
wasting time on little details like this, and instead work towards
real fixes.
i think the biggest gain would be to not have to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-06-29 15:43, Roman Haefeli wrote:
I don't know any solution off-hand and I also don't know whether Pd
was designed with the possibility in mind to read patches with
[textfile]. I just want to have it mentioned. And yes, it does
break some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi miller,
On 2013-07-02 12:37, IOhannes m zmölnig wrote:
after the latest updates in the puredata git repository
(0.45.0test), the automake build-system is broken, since files
have been removed from the source-tree.
as much as i personally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-02 13:39, Antoine Villeret wrote:
I realize that with iemnet's version of tcpclient/tcpserver, if two
client connect at the same time to server, only on receive data
not the other,
that's a different bug, please report it.
(please
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-03 15:58, Antoine Villeret wrote:
sorry I was not clear enough
I need a server : listening on one port and sending data to client
on different port i first use only udpsend/udpreceive and the
'server' was sending to a multicast group,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-03 16:12, IOhannes m zmoelnig wrote:
i guess you meant [tcpserver] instead of [udpserver].
in any case, i'm thinking about removing the multi-client feature
of iemnet's [udpserver]
just to make sure: i did mean [udpserver] (which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-03 17:33, Antoine Villeret wrote:
so it could be difficult to use a server which doesn't accept more
than one connection...
no that's not what i meant.
you can have as many connections as you want, but they cannot be
maintained at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-03 17:44, Martin Peach wrote:
Well [udpreceive] should be able to receive from many different
senders, no? (It's a bug if not...)
Based on what the [udpreceive] receives, route your replies to one
or more [udpsend]s based on info in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-03 17:58, Miller Puckette wrote:
Just to stir the pot, as it were :) -
The 'f' message is intended to mean 'format' and could be expanded
to specify font style and size, and/or other formatting info
(perhaps even to suppress carriage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-04 13:55, Antoine Villeret wrote:
2013/7/3 IOhannes m zmoelnig zmoel...@iem.at
On 2013-07-03 17:33, Antoine Villeret wrote:
so it could be difficult to use a server which doesn't accept
more than one connection...
no that's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-04 23:47, yvan volochine wrote:
On 02/07/13 12:37, IOhannes m zmölnig wrote:
** [patches:#513] automake build fixes**
[snip]
after the latest updates in the puredata git repository
(0.45.0test), the automake build-system is broken,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-18 18:41, Ivica Ico Bukvic wrote:
inlet_new apparently redirects elsewhere, so one could potentially
do what list_append does (if I am understanding the code
correctly), but is there an easier way to do this?
basically you ahve two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-18 19:04, IOhannes m zmoelnig wrote:
basically you ahve two options: - allow lists at the second
inlet, and check whether the list has only one argument of type
A_FLOAT or A_SYMBOL:
/* creating the inlet */ inlet_new((t_object*)x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-10-07 17:19, Orm Finnendahl wrote:
Hi,
trying to load a tcl file in a custom extern's setup routine with:
sys_vgui(load /home/orm/img.tcl;\n);
I get the following error when loading that extern in a pd
session:
(Tcl) UNHANDLED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-10-07 21:53, Pierre Guillot wrote:
Hi, I've got a strange behavior in my patch with my GUI externals.
First, I create a canvas :
sys_vgui(canvas %s -borderwidth 0 -width %d -height %d \n,
x-e_drawing_id-s_name, (int)x-e_rect.width,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
(re-including the pd-dev list; i prefer if you reply to the list
rather than me, unless it's personal).
On 2013-10-09 10:25, Pierre Guillot wrote:
Hi, Thank you for the tips, I'll try this. Do I have to give the
file with the external ?I want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-11-06 13:56, Bas Kooiker wrote:
Hey List,
I'm new here, so let me first introduce myself.
welcome!
for future emails, it would help to set a subject of the email, so
people can find your mail more quickly in their preferred mail client
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-11-06 15:52, Bas Kooiker wrote:
Oh yeah, I forgot about that. Will do next time!
Getting cygwin 32 worked! I succefully built the dll. But now the
library can't be loaded in Pd. The dll is created in the folder
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-11-06 17:42, Bas Kooiker wrote:
'file' gives me exactly that output indeed. Pd says nothing more
than:
C:/Program Files (x86)/pd/startup/gvf: can't load startup
library'!
So that's pretty useless.
start Pd with -verbose.
start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-12-11 20:38, Rob Bairos wrote:
Sorry, Im pretty new to this code, whats an extern in pdlib?
the same as in proper Pd: an external aka plugin that is, a
pre-compiled object loaded on-demand at runtime.
Does it make more sense for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2014-02-23 20:46, Dan Wilcox wrote:
Any further updates on this front? If a consensus is made, we could
outline a roadmap and move to the task of implementation. At this
point, I think breaking externals would be less of an issue if said
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2014-02-26 04:57, Martin Peach wrote:
I think that sending and receiving on the same port is not an
intended use of the UDP protocol, which was designed for throw and
forget messaging.
how come? how does DNS (after all, a central service in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2014-02-26 04:57, Martin Peach wrote:
how come? how does DNS (after all, a central service in the internet)
work with this assumption?
UDP works fine with as a challenge/response system (less so as
client/server, given that there is no notion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
(taking this back to the list)
On 2014-02-26 14:55, Martin Peach wrote:
On 2014-02-26 03:47, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
On 2014-02-26 04:57, Martin Peach wrote:
how come? how does DNS (after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
hi,
On 2014-04-29 23:12, Jonathan Wilkes wrote:
So that leaves eighthave or zmoelnig. Those are the two
developers I referred to with Hans? IOhannes? and they evidently
haven't responded to your inquiry.
indeed, sorry for the delay.
i
501 - 547 of 547 matches
Mail list logo
