Ok, well putting the .app in applications did not change anything, its
still not finding any of my externals (even though I copied them into the
extra folder inside the pd.app. I don't get it.
Where do I put the PDRC when using the .app?
Thanks,
Ben
>
> hi,
>
> i think it is still necessary to put the pd.app directly in
> /applications. if you don't do so strange things happen.
>
> it is easiest to put your own externals into
> /applications/pd.app/contents/resources/extra as this folder is in the
> search path and all the externals that come with the package are in
> there. gem is also already there.
>
> why don't you want to use a .pdrc? it works, you know ...
>
> lg
> martin
>
>
> On Oct 23, 2004, at 20:10, B. Bogart wrote:
>
>> Hey all,
>>
>> I can't figure out how to get the PD.app to load my externals/libs.
>> I can add the paths easily enough but when I try and put anything into
>> the
>> "startup" setup pd can't find it. I've tried absolute paths, relative
>> paths, paths relative to pd paths... still can't get it to load my
>> stuff.
>> It can't seem to find my abstractions either so I guess -path options
>> are
>> not working either.
>>
>> for example my Gem is installed in:
>>
>> /Users/admin/work/libs/cgc/Gem.pd_darwin
>>
>> And console reports:
>>
>> tried /Users/admin/work/libs/cgc/Gem
>> .pd_darwin and failed
>> tried /Users/admin/work/libs/cgc/Gem
>> //Users/admin/work/libs/cgc/Gem
>> .pd_darwin and failed
>> /Users/admin/work/libs/cgc/Gem
>> : can't load library
>>
>> Where are these options stored? I could try editing the file manually
>> to
>> get things moving (maybe) Any other way to supply PD with commandline
>> args
>> with the pd.app (other than .pdrc)?.
>>
>> I start my old pd-0.37-1 with:
>>
>> ~/work/pd/bin/pd -rt -helppath ~/work/abstractions-tot-help -path
>> ~/work/extra -path ~/work/libs -path ~/work/abstractions-v -path
>> ~/work/abstractions-tot -nosound -lib cgc/Gem:pmpd:OSC:zexy:pool
>>
>> (Oh and in the console I get error: .printout.text: no such object)
>> which
>> is caused by Apple-C to copy the console buffer.
>>
>> Thanks
>> B.
>>
>>
>>
>>
>> _______________________________________________
>> PD-dev mailing list
>> PD-dev(a)iem.at
>> http://iem.at/cgi-bin/mailman/listinfo/pd-dev
>>
>>
> attacksyour.net/pi
>
>
hi miller ...
i'm curious about the new filer objects ... there is no denormal
protection ... are you sure, they are denormal safe?
also here is a patch to force the os not to overcommit memory (see man
mlockall):
--- s_inter.c 28 Oct 2004 09:09:39 -0000 1.1.1.2
+++ s_inter.c 29 Oct 2004 15:41:00 -0000
@@ -267,6 +267,13 @@
#endif
#ifdef _POSIX_MEMLOCK
+ /* tb: force memlock to physical memory { */
+ struct rlimit mlock_limit;
+ mlock_limit.rlim_cur=0;
+ mlock_limit.rlim_max=0;
+ setrlimit(RLIMIT_MEMLOCK,&mlock_limit);
+ /* } tb */
+
if (mlockall(MCL_FUTURE) != -1)
fprintf(stderr, "memory locking enabled.\n");
#endif
cheers ... tim
--
mailto:TimBlechmann@gmx.de ICQ: 96771783
http://www.mokabar.tk
After one look at this planet any visitor from outer space
would say "I want to see the manager."
William S. Burroughs
hi all..
i'm currently trying to compile pd for windows using the command line
compiler ... since the mingw makefile of devel_0_37 is broken (linking
fails: filename or extension to long) i'm fighting with the ms cl
compiler ...
pd builds fine, but requires a asiolib.dll / .lib ... how can i build
that?
cheers ... tim
--
mailto:TimBlechmann@gmx.de ICQ: 96771783
http://www.mokabar.tk
After one look at this planet any visitor from outer space
would say "I want to see the manager."
William S. Burroughs
well... i have been playing with the code today and managed to add
native alsa sequencer support to pure data.
output, input and configuration window are working nicely, as well as
most of the midi objects (theres still some midi messages i don't know
-touch and polytouch, and pitchbend passes strange values).
if there is any interest in adding this code to pd i can provide the
code, it's just an s_midi_alsa.c and some changes to the interface file.
(must still touch the make system and input command line options, but
would like to see what people think).
pablo
Buenas Frank Barknecht, el 27 de oct de 2004, a las 02:35 escribiste:
> Hallo,
> pablo hat gesagt: // pablo wrote:
>
> > i was wondering whether pd has support for the alsa sequencer or it just
> > admits connecting through the oss devices. i have been looking around but
> > found nothing, just a method to connect it through an alsa virtual device
> > to the sequencer.
>
> It's the only method: You need a snd-virmidi card. Actually Pd was the
> reason for me to write the Softsynth-Sequencer-Howto.
>
> Ciao
> --
> Frank Barknecht _ ______footils.org__
>
> _______________________________________________
> PD-list(a)iem.at mailing list
> UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
Hallo!
> Yes, I think, this is probably bad. I'd vote for making this a message
> to the object, like [init 10(. The last one will win then. ;)
I don't know how you really mean this. Now there is the message [resize 10(,
where you can resize the array. Do you mean with [init 10( the same ?
> Maybe I'm spoiled by Python, but I think, Exceptions are quite useful.
Of course ...
LG
Georg
--
Geschenkt: 3 Monate GMX ProMail + 3 Ausgaben der TV Movie mit DVD
++++ Jetzt anmelden und testen http://www.gmx.net/de/go/mail ++++
Hallo!
> Actually I think, that maybe throwing an exception would be a cleaner
> way here and in other places, where something tries to access
> non-existing Elements (like the other "Element &get()" methods.
> However then all uses of get() will need to catch possible exceptions.
Yep, I also though about this yesterday.
The problem is/was, that i decided at the begin to not use exceptions (but
this was a bad decision).
I think I will rework the code a bit and use exceptions (not only in the get
methods), because there were some more situations where I thought I should
use them.
> outlet gets a bang in the catch block, if an exception occurs, but
> that's just for illustration and should be removed, as the list is
> not empty in fact, when the exception is thrown.
> Or maybe it should not be removed? It depends on what the right outlet
> should indicate: an empty list or the "end" iterator of a container.
> Thinking of how [textfile] and [qlist] use the right outlet, banging
> it at "EOF" would also be sensible, IMO.
Thats a good question. The concept of the right outlet isn't really clear
(because all the containers are different...).
My idea was, that if get doesn't output an element (so the list is empty or
the iterator is at a position where's no element) there should be a bang at
the right outlet, so that you can react in PD.
The same e.g. with the map: if the requested key (with get) isn't stored in
it, there's a bang at the right outlet.
Now I just saw that there's a problem with the vector and deque:
I didn't write it into the help-patches, but you can give a vector or a
deque a second init-arg: the size (i thought then it's similar to the
array). Then all the elements are initialized with Elements of length 0 and
the bang at the outlet is handled a bit different (see attached patch)!
But maybe this with an init-size isn't a good idea ? And the bang should
also be if theres an invalid index (see attached patch) !?
Thanks for your advices,
LG
Georg
--
Geschenkt: 3 Monate GMX ProMail + 3 Ausgaben der TV Movie mit DVD
++++ Jetzt anmelden und testen http://www.gmx.net/de/go/mail ++++
Hallo!
An other problem with the init size of vector/deque:
If you have more objects with the same namespace in a patchand every object
with a different size (e.g. [h_vector blabla 100] ... [h_vector blabla 10]
... [h_vector blabla 1]) it will be very funny to debug, because if it's a
big patch, you're not shure if this size will be initialized !?
LG
Georg
--
+++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++
Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl
Hallo,
(switching to pd-dev mode.)
Georg Holzmann hat gesagt: // Georg Holzmann wrote:
> > I will, as soon as I get a deeper look. However I also have found one
> > bug, see attached patch, but unfortunatly no solution yet. Maybe you
> > can find out, why this is happening.
> Thanks, just fixed and again on http://puredata.info/Members/holzi/ !
I see your fix, which as you comment is a bit hairy. ;)
Actually I think, that maybe throwing an exception would be a cleaner
way here and in other places, where something tries to access
non-existing Elements (like the other "Element &get()" methods.
However then all uses of get() will need to catch possible exceptions.
I implemented an example of this in attached files. There, the right
outlet gets a bang in the catch block, if an exception occurs, but
that's just for illustration and should be removed, as the list is
not empty in fact, when the exception is thrown.
Ciao
--
Frank Barknecht _ ______footils.org__