-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
-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
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 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 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
(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-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
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: 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: 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-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-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
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-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
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-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
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-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
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-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-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-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-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-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-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-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-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-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-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 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
the recent commit 78b81aa3cb90 on the puredata/master branch breaks
ABI compatibility with externals compiled for Pd-0.43.
the problem is that the sys_close() symbol is removed for non-w32
platforms.
therefore all the externals on non-w32 that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-17 10:55, IOhannes m zmoelnig wrote:
this makes packaging externals for e.g. Debian a nightmare, as it
basically should trigger a .so-name change, but since we are
linking against the application instead of an ordinary library, all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-10 22:17, Hans-Christoph Steiner wrote:
I'm CC'ing pd-dev since this is good to have in the public and on
the record.
yes, definitely. thanks.
i'm moving it from pd-list to pd-ev though.
I think the problem was that Fink's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-03 18:10, Jonathan Wilkes wrote:
It'd be even better to use a modern GUI toolkit that has simple
tools to implement bleeding edge UX technology from the past 15
years. Stuff like hyperlinks. :)
if hyperlinks is the criterion, then i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-03 19:05, SourceForge.net wrote:
Comment By: Miller Puckette (millerpuckette)
Date: 2012-12-03 10:05
Message: I tried this and got:
[...]
... is there any way you can supply a patch that doens't add
trailing white space to 1/2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-12-03 19:49, Miller Puckette wrote:
Aha... so all the whitespace trouble was their fault, not yours :)
Anyhow, it's on the tracker, but you can get the one I was using:
http://crca.ucsd.edu/~msp/tmp/pa_snapshot_20121031.tgz
but I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-31 04:11, Hans-Christoph Steiner wrote:
I think this would be super valuable. libpd already has an
implementation of parts of this idea, but making fully separate
modules would be quite nice.
Have you talked with Peter Brinkmann at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-24 02:56, Miller Puckette wrote:
I think the most nearly correct thing to do would be to change the
signal structure to add an ?allocated-size field, and put what is
now calcsize in the s_n field of the signal.
m_pd.h
typedef struct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-24 09:24, IOhannes m zmoelnig wrote:
On 2012-10-24 02:56, Miller Puckette wrote:
I'm not 100% sure I can change the size of the signal structure
without breaking binary compatibility with older objects.
i think that t_signal is used
with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlCHqHcACgkQkX2Xpv6ydvTlcwCgmczoV5OY5vBM0+AlF+ReOa2o
LcoAmwcYa6HUxuiU53NonrksunqxseIf
=9IT/
-END PGP SIGNATURE-
From 66e1578b0a9500e754a82f2cc948be6fabb2e6fa Mon Sep 17 00:00:00 2001
From: IOhannes m zmoelnig zmoel...@iem.at
Date: Wed, 24 Oct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-18 10:16, Claude Heiland-Allen wrote:
..know if it is possible to use other than 2^n-blocksizes?!
Not for audio connected to a dac~, but for offline stuff it works
(some buggy objects might not cooperate).
You know, I've read about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-08 23:39, Hans-Christoph Steiner wrote:
Looks like we'll eventually have to upgrade to the new
SourceForge. Anyone know anything about the new one Allura?
thanks for taking this up (i just wanted to write a similar email).
while i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-04 21:12, Miller Puckette wrote:
Also... I think OSS/MIDI is the only API now that lets you spit out
arbitrary byes over the MIDI line -- all the others 'protect' you.
i'm not saying that i want to remove OSS-MIDI.
i'm saying that i want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-03 23:11, Miller Puckette wrote:
Hi all,
Pd version 0.43-3 is available on
http://crca.ucsd.edu/~msp/software.htm
cool.
I'm ready to start hacking on 0.44. The most urgent thing seems to
be for me to go back and work on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-03 15:19, Thomas Grill wrote:
Hi all, when trying to trace a bug in one of my externals i came
across what could be an issue in the PD API.
The header m_pd.h exposes the function open_via_path which can be
used in externals to search
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-03 15:40, IOhannes m zmoelnig wrote:
Pd-0.43 introduced sys_close() in order to have the same CRT
implementation open and close the file.
prior version of Pd lack this function and therefore there a number
of file-handle leakage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-13 01:41, Tedb0t wrote:
Hi all,
I just completed building pd-extended on an ARM system. I had to
fix a bunch of dependencies, but I eventually got it all the way
through. (It ended with linux_make install succeeded!) After
that I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
please always reply on-list!
On 2012-06-13 18:27, Tedb0t wrote:
Sorry?this is my question:
After make install, should pd-extended exist in /usr/bin or
usr/local/bin?
Mine did not.
what? /usr/bin? /usr/local/bin? both? none?
looking at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-03 22:30, s p wrote:
That's a very good point, ... it's a good idea to specify GUI
infos, for better interoperability, but it should be explicitly
said that this is optional information
gui information (e.g. spatial layout) is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-04-05 20:10, Hans-Christoph Steiner wrote:
Thanks to Greg Pond, we now have a macosx104-powerpc box online and running
builds via jenkins and the Pd-extended auto-build script. The whole Fink
setup is still building, so that's not in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-03-06 17:46, Mathieu Bouchard wrote:
I just wrote a comment in « [grid] not working in pd-extended 0.43.1 »
and it didn't go through to the pd-dev list. I'm wondering what the
selection process is, for routing those comments to pd-dev.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-29 10:52, Cyrille Henry wrote:
Le 29/02/2012 09:34, IOhannes m zmoelnig a écrit :
and both [pix_texture] and [pix_snap] allow for asynchronous
DMA-transfers already (though i only added PBO-tarnsfers to [pix_snap] a
week ago or so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-28 16:03, Hans-Christoph Steiner wrote:
Yes, I object. Like I said in the bug tracker and this thread, I think
the offset should either remain the same or be the same as the rest.
may i ask why? what makes 4 better than 3?
fgmasdr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i move that to the list, as it makes discussion easier.
On 2012-02-27 15:32, SourceForge.net wrote:
Comment By: Hans-Christoph Steiner (eighthave)
idea to change to loglevel+4 to loglevel+3. Either leave verbose()'s
custom level numbering the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
it seems like on the debian-stable-amd64 host of the build-farm, the
Pd-headers have been uninstalled.
at least, Gem build#71 (2011-12-22 10:00:51) succeeded, whereas the next
build#527 (2012-02-19 22:01:47) failed, because out of a sudden it
cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-21 13:03, IOhannes m zmoelnig wrote:
- `pkg-config --cflags pdextended` returns -I/usr/local/include/pd,
which does not exist at all.
- `pkg-config --cflags pd` fails as well as `pkg-config --cflags puredata`
which also leads
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-21 17:15, Hans-Christoph Steiner wrote:
- - should /usr/include/m_pd.h be handled likewise, using
update-alternatives? again, i'm not sure whether this is good style and
cannot find such a thing on my system
Pd-extended's headers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-21 17:20, Hans-Christoph Steiner wrote:
I reinstalled 'puredata' on debian-stable-amd64, sorry about that, I don't
know what happened there. The build systems are mean to have the Pd-vanilla
headers installed.
thanks.
I'm happy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-21 17:40, Hans-Christoph Steiner wrote:
Pd-vanilla does provide the sources, but there are two issues:
- it does not include the include/pd/ subdir for headers
i don't think this is an issue.
externals have traditionally included
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-02-08 00:36, Mathieu Bouchard wrote:
I mean that this context could be accessed directly if there's no reason
to use accessors. But if locking has to be done before and after
accessing (some of) those members, then it's nice to have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-31 00:52, Hans-Christoph Steiner wrote:
That does make more sense, so something like [bytes2utf8], etc.
utf8 is always a list of bytes.
if you get values 255 than it is not utf-8; do you mean unicode points?
fgmasdr
IOhannes
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-31 15:41, Martin Peach wrote:
On 2012-01-31 03:41, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-31 00:52, Hans-Christoph Steiner wrote:
That does make more sense, so something like [bytes2utf8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-29 22:15, SourceForge.net wrote:
I use Ubuntu 64 bit on a pc with intel i7. Until yesterday Ubuntu 10.10 +
Puredata + Gem worked well.
Today i upgrade Ubuntu to 11.4 and 11.11. When i open Puredata, it say:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-19 04:28, Hans-Christoph Steiner wrote:
Has anyone tried this? It seems like it would be very valuable for Pd
applications, since Motion JPEG is the standard codec:
http://libjpeg-turbo.virtualgl.org/
libjpeg-turbo is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-19 07:09, Peter Brinkmann wrote:
On 2012-01-14 22:04, Miller Puckette wrote:
To do this I'd replace all globals like
what is wrong with eliminating all directly accessible globals from the
API (like pd_objectmaker) and provide accessor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i think there are 2 use cases for multi threading.
#1 access a single instance of (lib)pd from multiple threads
#2 allow multiple instances of (lib)pd to co-exist in global memory.
right now, only #1 is possible at all and it takes some effort on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-16 01:15, Hans-Christoph Steiner wrote:
include/Base/
These are the Gem headers, they should be in the 'gem' package, but I
DoH! i wa absolutely convinced that i got that right for the 0.93.3
package. i even closed the relevant debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-16 09:52, IOhannes m zmoelnig wrote:
On 2012-01-16 01:15, Hans-Christoph Steiner wrote:
include/Base/
These are the Gem headers, they should be in the 'gem' package, but I
DoH! i wa absolutely convinced that i got that right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-29 18:29, katja wrote:
On Tue, Nov 29, 2011 at 5:37 PM, Hans-Christoph Steiner h...@at.or.at wrote:
The new build system doesn't need the makefile.dependencies, and that
has always been a bit of a mystery.
Ah, so I'm not the only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-08 18:13, Hans-Christoph Steiner wrote:
jenk...@macosx105-i386.puredata.info
it seems jenkins is still sending with this identity.
could you change that to jenk...@macosx105-i386.pdlab.puredata.info
I like the name standard that we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-17 02:07, Ricardo Fabbri wrote:
Hi,
would there be a straightforward way to adjust the hardware color
balance of a webcam through GEM? Do you have experience in
getting/setting those attributes with the PS3 eye webcam which has
been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-17 09:25, Ricardo Fabbri wrote:
thanks.
ps: you referred to [1] but I see no link.
doh,
[1] http://bear24rw.blogspot.com/2009/11/ps3-eye-driver-patch.html
fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-17 18:44, Hans-Christoph Steiner wrote:
Woo hoo! 32-bit ints in Pd! Well done, thanks for your hard work on this :).
32bit ints?
more like 52bit ints.
fgmadr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-10 16:26, Hans-Christoph Steiner wrote:
Even better would be to fix the new build system. One of the reasons I
removed extra/ from Pd-extended and made it a separate library is because of
the brokenness of the build system.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-10 17:57, Hans-Christoph Steiner wrote:
That is 'make install' doing that, not 'make'. 'make install' is only
supposed to install the files, not generate them.
indeed.
make generated the .d_fat files, and make install copied them to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-10 18:21, Hans-Christoph Steiner wrote:
On Nov 10, 2011, at 12:16 PM, IOhannes m zmoelnig wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-10 17:57, Hans-Christoph Steiner wrote:
That is 'make install' doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ola!
since i don't know any better place to ask, i'll ask here...
debian-testing-amd64.pdlab.hfbk.net
- ---
for whatever reasons, this machine has /tmp (where jenkins creates the
workspaces) mounted as tmpfs (that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-08 11:32, IOhannes m zmoelnig wrote:
chaos.medien.uni-weimar.de
--
i seem to have great troubles to get the OSX10.6
(chaos.medien.uni-weimar.de) machine build a build without fink.
mainly because autoreconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 22:07, Hans-Christoph Steiner wrote:
Ah, ok, I think I fixed that. I forgot that the msys home tree is separate
from the rest.
seems to work ok,
thanks for the fix.
fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 03:57, Hans-Christoph Steiner wrote:
Wow, that effects.zip patch is simple yet quite nice. I had some fun with
that.
One possibility for using combinations of Gem, PDP, and Gridflow together is
to use Syphon. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
while i have access to the w32 build machine in the PdLab i have a hard
time getting anything useful to compile.
this is mainly, because i cannot access the binaries built by the
pd-extended autobuild, and i don't want build the whole shebang myself.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 14:43, Hans-Christoph Steiner wrote:
I assume you need access to the binaries for the linking. You can point your
PD_PATH to /home/pd/auto-build/pd-extended/pd and as long as last night's
build succeeded in building the core of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-02 16:30, Hans-Christoph Steiner wrote:
I forced everything in the 'pd' account to be read everyone, hope that helps.
thanks.
i guess this will only become active after the next autobuild run, correct?
for now, i still have:
$ ls -lha
1 - 100 of 547 matches
Mail list logo
