Send PD-list mailing list submissions to
    pd-list@iem.at

To subscribe or unsubscribe via the World Wide Web, visit
    http://lists.puredata.info/listinfo/pd-list
or, via email, send a message with subject or body 'help' to
    pd-list-request@iem.at

You can reach the person managing the list at
    pd-list-owner@iem.at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of PD-list digest..."


Today's Topics:

   1. servo control with pduino (olsen)
   2. Please explain Windows compiling once and for all! (Mark Polesky)
   3. Re: Please explain Windows compiling once and for all!
      (IOhannes m zmoelnig)
   4. Re: CVS connect error? (Antti Poikola)
   5. Re: CVS connect error? (IOhannes m zmoelnig)
   6. Re: Please explain Windows compiling once and for all!
      (Martin Peach)
   7. Re: Please explain Windows compiling once and for all!
      (Martin Peach)
   8. problems with Intel MacMini playing video (simon wise)
   9. Re: problems with Intel MacMini playing video (chris clepper)


----------------------------------------------------------------------

Message: 1
Date: Wed, 27 Jun 2007 10:48:32 +0200
From: olsen <sesselastronaut@googlemail.com>
Subject: [PD] servo control with pduino
To: pd-list <pd-list@iem.at>
Message-ID: <46822460.1070802@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi
so far for servo movements i'm using the Parallax Servo Controller
PSC(USB) & a python script for sending the ascii paragraph to controll it.
since the release of pduino 0.3 anyone played around with servos on
pduino - would be a nice improvement to pduino controlling servos?!
let me know if i could bear somewhere a hand on this
greets
olsen











--
Planet Pluto bleibt!




------------------------------

Message: 2
Date: Wed, 27 Jun 2007 00:28:45 -0700
From: "Mark Polesky" <middlepedal@gmail.com>
Subject: [PD] Please explain Windows compiling once and for all!
To: pd-list@iem.at
Message-ID:
    <8ff17cb60706270028l26ead89fyc2e590cd0e989d6b@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hey,

I'm trying not to get frustrated, seeing how posts like this one (on
compiling externals for Windows) are either ignored or answered way too
cryptically:

http://lists.puredata.info/pipermail/pd-list/2007-06/051182.html

I posted a similar question to the "PURE DATA forum~" a few days ago, and so
far it too has gone unanswered:

http://puredata.hurleur.com/sujet-1029-problem-compiling-external-windows

Is compiling an external for Windows so mysterious that no one knows how to
do it? The responses that I've seen so far usually amount to "well this is
how it's done on linux, try changing this to that and maybe it'll work". The
famous external tutorial ( http://iem.at/pd/externals-HOWTO/ ) looks very
interesting, but it does me no good without knowing how to get from .c to
.pd ...

The request is simple: List the steps required (without skipping any!) to
take the C source file "helloworld.c" and make it into a usable object in
pd.

Someone, please, help me out. Also feel free to tackle the other specific
questions in my forum~ post. I'm sure there are plenty of other confused
Windows programmers out there.

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.puredata.info/pipermail/pd-list/attachments/20070627/ec5a285a/attachment-0001.htm

------------------------------

Message: 3
Date: Wed, 27 Jun 2007 14:47:31 +0200
From: IOhannes m zmoelnig <zmoelnig@iem.at>
Subject: Re: [PD] Please explain Windows compiling once and for all!
To: Mark Polesky <middlepedal@gmail.com>
Cc: pd-list@iem.at
Message-ID: <46825C63.4070305@iem.at>
Content-Type: text/plain; charset=ISO-8859-15

Mark Polesky wrote:
> Hey,

hi.

unfortunately i am not in the position on fullfilling your request, but
i'll give it another "cryptic" try...

> The
> famous external tutorial ( http://iem.at/pd/externals-HOWTO/ ) looks very
> interesting, but it does me no good without knowing how to get from .c to
> .pd ...

the externals howto's examples are checked in at the sourceforge cvs,
they come with a makefile which should be useable on windows too.

>
> The request is simple: List the steps required (without skipping any!) to
> take the C source file "helloworld.c" and make it into a usable object in
> pd.

haha.

have you tried any online resources: e.g.
http://puredata.info/docs/developer lists at least 2 pages that only
deal with compiling on windows
(http://puredata.info/docs/developer/mingw which basically deals with
compiling pd itself on windows; but once you are there, it is simple;
http://nul.jp/2002/pd_bc deals with compiling externals with the
borland-compiler).

i can give you a step-by-step guide for compiling zexy though (but mind
that this is how i _remember_ it; i will not go and search for a windows
machine with VC installed just to verify each step).

- purchase M$ VC6 (elitarism on my side...:-)) and install it
- get pd
- download zexy (sources!) for free (e.g.
ftp://ftp.iem.at/pub/pd/Externals/ZEXY/)
- extract zexy to you favourite folder
- double-click on the zexy.dsp (or was it zexy.dsw??) in the zexy/src/
folder; this should open VC
- to to the Project->Properties (or however this is called in your
locale) and change the settings to match your setup (mainly these are
the paths to find pd's headers and libraries; you should basically go
through every item in the settings for the "release" and/or "debug"
builds; the most important stuff is in "compiler->preprocessor",
"compiler->path" and "linker->path"
- when you are finished, return to the main project window
- hit "F7" to start the build.
- if you encounter any errors, either the settings are not yet correct
(return to item-6) or the project is a bit out-of-date; the latter
basically means, that the c-files to be included have not been updated;
to fix this, just delete all the c-files from the project file browser
(here this used to be un the left-side of the project-window), then
right click on the folder in the project file browser that used to
contain these files and select "add"; in the openpanel choose all
c-files in zexy/src and hit "OK"
- return to item-8 until you stop getting errors

mind, that you must not use the dll while it is created (best close pd)

if you want step-by-step instructions for vc7, vc2000, vc2006 and
vc3000, please send them to me and i'll give it a go :-) (dev-elitarism
again)


pd comes with some externals (e.g. the foo-stuff, or [fiddle~]) and uses
makefiles to build these.
for this to work, you have to setup your environment correctly:
- first open the makefile (e.g. pd/doc/6.externs/makefile) with your
favourite text-editor and correct all the paths that are wrong
- VC6 came with a vc6vars.bat (ok the name is wrong but something along
these lines; it was a .bat-file which would set your envirnment
variables when run; more modern incarnations might do without the .bat
- open the dosbox (the rest will happen within the dosbox)
- run the vc6vars.bat (or however it is called) if this is needed for
your compiler-incarnation
- cd to your path (e.g. pd/doc/6.externs/)
- run "nmake pd_nt"

if nmake, cl, link cannot be found, you might want to add the paths to
them to your PATH variable.



any more questions?

fmga.dr
IOhannes



------------------------------

Message: 4
Date: Wed, 27 Jun 2007 15:55:18 +0300
From: Antti Poikola <antti.poikola@tml.hut.fi>
Subject: Re: [PD] CVS connect error?
To: pd-list@iem.at
Message-ID: <46825E36.6010507@tml.hut.fi>
Content-Type: text/plain; charset="iso-8859-1"

So far I have used only the libraries, that are included in the
pd-extended, but this morning many hours ago I decided to try how to
make the ANN (artificial neural networks) library work in PD.

I had some initial problems and asked help from Davide Morelli, the cool
developer of ANN, who replied me quickly. He told me to use the source
files of ANN and compile them. In order to get those files I would need
CVS... things are getting more complicated you see :)

So I downloaded and installed the tortoisecvs (
http://www.tortoisecvs.org/ ) and tried to check out (cvs slang for
downloading) the ANN sources with the following settings:
http://www.tml.tkk.fi/~apoikola/images/tortoisecvs.JPG

Unfortunately I got the error message:
CVSROOT=:pserver:anonymous@cvs.sourceforge.net:/cvsroot/pure-data

connect to cvs.sourceforge.net:2401 failed: A socket operation was
attempted to an unreachable host.
Error, CVS operation failed


I found the old message posted to this list few years ago:
http://thread.gmane.org/gmane.comp.multimedia.puredata.general/20689/focus=20725


My question remains: do I use the correct settings in tortoisecvs or is
there some other like sourceforge server related problem?

-Antti

-------------- next part --------------
A non-text attachment was scrubbed...
Name: antti.poikola.vcf
Type: text/x-vcard
Size: 279 bytes
Desc: not available
Url : http://lists.puredata.info/pipermail/pd-list/attachments/20070627/f2e68f42/attachment-0001.vcf

------------------------------

Message: 5
Date: Wed, 27 Jun 2007 15:34:19 +0200
From: IOhannes m zmoelnig <zmoelnig@iem.at>
Subject: Re: [PD] CVS connect error?
To: antti.poikola@tml.hut.fi
Cc: pd-list@iem.at
Message-ID: <4682675B.5040609@iem.at>
Content-Type: text/plain; charset=ISO-8859-15

Antti Poikola wrote:
> So far I have used only the libraries, that are included in the
> pd-extended, but this morning many hours ago I decided to try how to
> make the ANN (artificial neural networks) library work in PD.
>
> I had some initial problems and asked help from Davide Morelli, the cool
> developer of ANN, who replied me quickly. He told me to use the source
> files of ANN and compile them. In order to get those files I would need
> CVS... things are getting more complicated you see :)
>
> So I downloaded and installed the tortoisecvs (
> http://www.tortoisecvs.org/ ) and tried to check out (cvs slang for
> downloading) the ANN sources with the following settings:
> http://www.tml.tkk.fi/~apoikola/images/tortoisecvs.JPG
>
> Unfortunately I got the error message:
> CVSROOT=:pserver:anonymous@cvs.sourceforge.net:/cvsroot/pure-data
>
> connect to cvs.sourceforge.net:2401 failed: A socket operation was
> attempted to an unreachable host.
> Error, CVS operation failed


your settings are _way_ out of date.
recent information on how to use CVS with pd's repository can be found:
http://puredata.info/search?SearchableText=cvs
and more generically
http://sourceforge.net/cvs/?group_id=55736

mfg.asdr
IOhannes



------------------------------

Message: 6
Date: Wed, 27 Jun 2007 09:17:56 -0400
From: Martin Peach <martin.peach@sympatico.ca>
Subject: Re: [PD] Please explain Windows compiling once and for all!
To: Mark Polesky <middlepedal@gmail.com>
Cc: pd-list@iem.at
Message-ID: <46826384.10507@sympatico.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Mark Polesky wrote:
> Hey,
>
> I'm trying not to get frustrated, seeing how posts like this one (on
> compiling externals for Windows) are either ignored or answered way
> too cryptically:
>
> http://lists.puredata.info/pipermail/pd-list/2007-06/051182.html
I guess they get answered over and over again and then forgotten over
and over again.
>
> I posted a similar question to the "PURE DATA forum~" a few days ago,
> and so far it too has gone unanswered:
>
> http://puredata.hurleur.com/sujet-1029-problem-compiling-external-windows
>
> Is compiling an external for Windows so mysterious that no one knows
> how to do it? The responses that I've seen so far usually amount to
> "well this is how it's done on linux, try changing this to that and
> maybe it'll work". The famous external tutorial (
> http://iem.at/pd/externals-HOWTO/ ) looks very interesting, but it
> does me no good without knowing how to get from .c to .pd ...
There really should be a section in that HOWTO for compiling on the
different OSs.
>
> The request is simple: List the steps required (without skipping any!)
> to take the C source file " helloworld.c" and make it into a usable
> object in pd.
If you're on some kind of MSVC, you set up a project to build a dll, in
"preprocessor defines" define MSW, in "additional include paths" include
the path to pd/src/m_pd.h, link with pd.lib from pd/bin, and in the
linker command line add "/export:yourexternal_setup" to export the setup
function. All the other functions in your code can be static and don't
need to be exported. After it builds you take the dll from the release
folder and put it in your pd/extra folder.
That should be everything you need, but if it's too cryptic I can go
into more detail...

Martin




------------------------------

Message: 7
Date: Wed, 27 Jun 2007 09:39:30 -0400
From: Martin Peach <martin.peach@sympatico.ca>
Subject: Re: [PD] Please explain Windows compiling once and for all!
To: IOhannes m zmoelnig <zmoelnig@iem.at>
Cc: pd-list@iem.at
Message-ID: <46826892.50800@sympatico.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

IOhannes m zmoelnig wrote:
>
> - purchase M$ VC6 (elitarism on my side...:-)) and install it
>  
There's a free Express version available that works just as well.

Martin



------------------------------

Message: 8
Date: Thu, 28 Jun 2007 00:12:28 +1000
From: simon wise <simonxwise@hotmail.com>
Subject: [PD] problems with Intel MacMini playing video
To: chris clepper <cgclepper@gmail.com>
Cc: PD list <pd-list@iem.at>
Message-ID: <BAY140-DAV11834FAD018F4F73C84E23C90A0@phx.gbl>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed


On 27 Jun 2007, at 1:27 AM, chris clepper wrote:

> What type of video files and at what size?  How many clips are  
> playing on one machine at the same time?  What is the display  
> resolution?  The Intel graphics have some problems above usual  
> desktop sizes and shader performance is really horrible too.

I'm using pix_movie to play .dv movies by asking for each frame in  
turn, so that I can scrub, pause etc with all machines in sync. It  
works well, except for the intermittent series of hesitations I  
assume are either dropped or late frames.

To debug this I switched to using a single machine, no network  
connections and tested using [auto 1( instead of frame-by-frame -  
only 1 clip playing in this simple setup. Then tried different codecs  
- H264, PhotoJPEG each 576x720 and 1024x768. The MacMini is connected  
to the 1024x768 projector via a short DVI cable. The GEM window is  
set to fullscreen, frame rate 25.

There was a slight improvement with the H264@576x720 but the problem  
was still there. Quicktime could play all the movies at fullscreen  
smoothly.

I have some other MacMinis - PPC and intel - coming soon so I'll test  
these and try higher framerates for GEM. The Intel ones have just  
been used with Isadora in a similar way and apparently had the same  
issue. The hesitation is only very noticeable on video with fast  
moving, high contrast scenes - but it is obvious then.

Pity about the shader performance - I was planning to use Minis for a  
more complex setup with masks and some colour correction but I guess  
I'll need to go with bigger boxes and better graphics cards (probably  
similar $$), or try to find some old G4 Minis.

Simon





------------------------------

Message: 9
Date: Wed, 27 Jun 2007 09:20:28 -0500
From: "chris clepper" <cgclepper@gmail.com>
Subject: Re: [PD] problems with Intel MacMini playing video
To: "simon wise" <simonxwise@hotmail.com>
Cc: PD list <pd-list@iem.at>
Message-ID:
    <a8e0bc960706270720r7b47d4d2t6570d6b2c8cf0c21@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Does it stutter at the end of the clip while going back to the start?

Do you have any audio in the clips?

What is the GEM compile date?

On 6/27/07, simon wise <simonxwise@hotmail.com> wrote:
>
>
> On 27 Jun 2007, at 1:27 AM, chris clepper wrote:
>
> > What type of video files and at what size?  How many clips are
> > playing on one machine at the same time?  What is the display
> > resolution?  The Intel graphics have some problems above usual
> > desktop sizes and shader performance is really horrible too.
>
> I'm using pix_movie to play .dv movies by asking for each frame in
> turn, so that I can scrub, pause etc with all machines in sync. It
> works well, except for the intermittent series of hesitations I
> assume are either dropped or late frames.
>
> To debug this I switched to using a single machine, no network
> connections and tested using [auto 1( instead of frame-by-frame -
> only 1 clip playing in this simple setup. Then tried different codecs
> - H264, PhotoJPEG each 576x720 and 1024x768. The MacMini is connected
> to the 1024x768 projector via a short DVI cable. The GEM window is
> set to fullscreen, frame rate 25.
>
> There was a slight improvement with the H264@576x720 but the problem
> was still there. Quicktime could play all the movies at fullscreen
> smoothly.
>
> I have some other MacMinis - PPC and intel - coming soon so I'll test
> these and try higher framerates for GEM. The Intel ones have just
> been used with Isadora in a similar way and apparently had the same
> issue. The hesitation is only very noticeable on video with fast
> moving, high contrast scenes - but it is obvious then.
>
> Pity about the shader performance - I was planning to use Minis for a
> more complex setup with masks and some colour correction but I guess
> I'll need to go with bigger boxes and better graphics cards (probably
> similar $$), or try to find some old G4 Minis.
>
> Simon
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.puredata.info/pipermail/pd-list/attachments/20070627/6ad7533a/attachment.htm

------------------------------

_______________________________________________
PD-list mailing list
PD-list@iem.at
to manage your subscription (including un-subscription) see
http://lists.puredata.info/listinfo/pd-list


End of PD-list Digest, Vol 27, Issue 136
****************************************