hi, august, list
I'm still using pd 0.36 (probably a bad idea) on a debian system.
although i succeeded in compiling readanysf~, it crashes PD anytime i create it. i use alsa-drivers and -rt flags.
can anyone help me ? should i switch to 0.37 ?
thanks
oliver
sent through klingt.org webmail
I'm still using pd 0.36 (probably a bad idea) on a debian system.
although i succeeded in compiling readanysf~, it crashes PD anytime i create it. i use alsa-drivers and -rt flags.
can anyone help me ? should i switch to 0.37 ?
afaik, thomas considered to declare 0.36 as unsupported by flext ... iirc there was a problem with the attributes, although i don't know if rasf~ is using attributes...
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
afaik, thomas considered to declare 0.36 as unsupported by flext ... iirc there was a problem with the attributes, although i don't know if rasf~ is using attributes...
I don't think so. OTOH, if a flext project compiles with 0.36 it should run there as well.....
greetings, Thomas
hi, august, list
I'm still using pd 0.36 (probably a bad idea) on a debian system.
although i succeeded in compiling readanysf~, it crashes PD anytime i create it. i use alsa-drivers and -rt flags.
can anyone help me ? should i switch to 0.37 ?
oliver,
where can I get a pd-36 ?
I haven't touched readanysf in over 4-5 months. I just downloaded it yesterday and compiled with a cvs flext and a cvs pd. all seemed to work just fine.
does pd crash anyway with alsa ? mine does. I simply can't get alsa to work with PD anymore.
-august.
hi with pd 37 test 3 and the new GEM libs i get an error. the G4 libs are dated 010904.
bash-2.05a$ ./pd -lib /Users/swifty/Desktop/Gem cannot connect to jack server cannot connect to default JACK server dyld: ./pd Undefined symbols: _btowc _iswctype _mbsrtowcs _towlower _towupper _wcscoll _wcsftime _wcslen _wcsrtombs _wcsxfrm _wctob _wctype _wmemchr _wmemcmp _wmemcpy _wmemmove _wmemset pd_gui: pd process exited On Friday, January 23, 2004, at 09:11 AM, august wrote:
Patrick Pagano,B.S. M.F.A candidate http://www.digitalworlds.ufl.edu http://www.screwmusicforever.com/SHREESWIFT
just for curiosity : what chipset you are on ? i did not get clear sound from alsa (but never crashed Pd) on gentoo nor debian, using all posiible kernels and patches of the patches ... but it behaves quite ok on alsa-oss emulation (sis chipset). and readanysf~ is happy too.
Ales.
On Fri, 23 Jan 2004, august wrote:
hi, august, list
I'm still using pd 0.36 (probably a bad idea) on a debian system.
although i succeeded in compiling readanysf~, it crashes PD anytime i create it. i use alsa-drivers and -rt flags.
can anyone help me ? should i switch to 0.37 ?
oliver,
where can I get a pd-36 ?
I haven't touched readanysf in over 4-5 months. I just downloaded it yesterday and compiled with a cvs flext and a cvs pd. all seemed to work just fine.
does pd crash anyway with alsa ? mine does. I simply can't get alsa to work with PD anymore.
-august.
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
++++++++++++++++++++++++
- Ales Zemene +
- http://ales.mur.at +
- GSM +436769573397 +
- ICQ 215971050 +
++++++++++++++++++++++++
hi oliver,
I read:
I'm still using pd 0.36 (probably a bad idea) on a debian system. although i succeeded in compiling readanysf~, it crashes PD anytime i create it.
did you also compile flext or are you using a precompiled version ?
regards,
x
hi list,
decided to put all the answers i got about this issue in one reply - hope this doesn't confuse...
Zitat von august august@alien.mur.at:
where can I get a pd-36 ?
from miller puckette's website, http://crca.ucsd.edu/~msp/software.html
I haven't touched readanysf in over 4-5 months. I just downloaded it yesterday and compiled with a cvs flext and a cvs pd. all seemed to work just fine.
does pd crash anyway with alsa ? mine does. I simply can't get alsa to work with PD anymore.
no, seems to work fine with alsa, though i once DID have a serious system (!) freeze when i started PD with no flags !!!
maybe oss would do better
-august.
Zitat von CK x@meta.lo-res.org:
hi oliver,
I read:
I'm still using pd 0.36 (probably a bad idea) on a debian system. although i succeeded in compiling readanysf~, it crashes PD anytime i create it.
did you also compile flext or are you using a precompiled version ?
i compiled flext 0.4.1. before compiling "readanysf~". the newest flext version wouldn't compile on my system, don't know why. but the readme in "readanysf~" said, that any flext - version > 0.4 would do.
Zitat von Norbert Math n@alien.mur.at:
i have readanysf~ running solid on debian testing with pd 0.36-0, oss.
so maybe i'll give that a try or update to 0.37
thanks for all answers
oliver
sent through klingt.org webmail
Hi Oliver,
i compiled flext 0.4.1. before compiling "readanysf~". the newest flext version wouldn't compile on my system, don't know why. but the readme in "readanysf~" said, that any flext - version > 0.4 would do.
any flext version does compile, but there have been a number of bug fixes, therefore you _should_ use 0.4.5. Perhaps you have the time to tell me which problems you have compiling flext on your platform so i can help you or fix things.
best greetings, Thomas
I got it to compile under OSX and it crashes as well.May be for different reasons. Built with flext 0.4.6 and pd 0.37. I had to remove the -shared flag because it is not supported on OSX. Could this be the problem?
a snip from the crash log:
Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0xbf7ffff0
Thread 0 Crashed: 0 readanysf~.pd_darwin 0x006a8f48 flext_root_multi::operator new(unsigned long) + 0x14 1 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 2 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 3 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 4 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 ...
El 24/01/2004, a las 17:05, Thomas Grill escribió:
Hi Oliver,
i compiled flext 0.4.1. before compiling "readanysf~". the newest flext version wouldn't compile on my system, don't know why. but the readme in "readanysf~" said, that any flext - version > 0.4 would do.
any flext version does compile, but there have been a number of bug fixes, therefore you _should_ use 0.4.5. Perhaps you have the time to tell me which problems you have compiling flext on your platform so i can help you or fix things.
best greetings, Thomas
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0xbf7ffff0
Thread 0 Crashed: 0 readanysf~.pd_darwin 0x006a8f48 flext_root_multi::operator new(unsigned long) + 0x14 1 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 2 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 3 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 4 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24
Oh wow, i'll have to have a look.... that seems to be caused by minor changes introduced lately... 0.4.5 could be fine though.
best, Thomas
0 readanysf~.pd_darwin 0x006a8f48 flext_root_multi::operator new(unsigned long) + 0x14 1 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 2 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 3 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24 4 readanysf~.pd_darwin 0x006a8f58 flext_root_multi::operator new(unsigned long) + 0x24
Oh wow, i'll have to have a look.... that seems to be caused by minor changes introduced lately... 0.4.5 could be fine though.
i've experienced problems with the recent flext and readanysf~, too ... not on a mac, but on a linux machine ...
i did a backtrace with ddd and it seems that flext_root_multi::operator new() as it's run by readanysf::__init__() runs itself recursively for (on my setup) 261771 times ...
i don't fully understand your code, but it seems that in line 6 you try to run the same function, again without changing the parameter (bytes) ...
void *flext_root::operator new(size_t bytes) { bytes += sizeof(size_t);
char *blk;
if(bytes >= LARGEALLOC) {
// use C library function for large memory blocks
blk = (char *)::operator new(bytes);
}
else {
//! \todo We need system locking here for secondary threads!
#if FLEXT_SYS == FLEXT_SYS_JMAX blk = (char *)::fts_malloc(bytes); #else blk = (char *)::getbytes(bytes); #endif }
*(size_t *)blk = bytes;
return blk+sizeof(size_t);
}
i might be wrong (i don't understand the meaning of (char *)::, but that would explain the behaviour...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Oh wow, i'll have to have a look.... that seems to be caused by minor changes introduced lately... 0.4.5 could be fine though.
i've experienced problems with the recent flext and readanysf~, too ... not on a mac, but on a linux machine ...
i tried to compile my own external with the recent flext and got the same behaviour with tbfft2, but not with tbfft1...
but the only difference between these 2 classes is, that tbfft2 allocates an array of 17000 t_floats ...
it seems that there is a problem with the allocation of larger areas of memory... (operator new() is executed 261748 times)
i'll try to downdate my flext ... but thomas, if you could explain to me, what you intend to do with your operator new() function, i could have a look at it...
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Hi Tim,
it seems that there is a problem with the allocation of larger areas of memory... (operator new() is executed 261748 times)
i'll try to downdate my flext ... but thomas, if you could explain to me, what you intend to do with your operator new() function, i could have a look at it...
The only difference is that with the new allocation method the PD functions are used, while previous versions of flext used the ones of the c library. I'm not sure if the PD memory allocation can deal with the large number of implicit allocations of the C++ language. The reason for using the PD functions are that they may be faster but even that has to be verified. I'll shortly do some tests...
best greetings, Thomas
The only difference is that with the new allocation method the PD functions are used, while previous versions of flext used the ones of the c library. I'm not sure if the PD memory allocation can deal with the large number of implicit allocations of the C++ language. The reason for using the PD functions are that they may be faster but even that has to be verified. I'll shortly do some tests...
i see ... but you seem to run the same function again and again ...
if bytes is larger than largealloc, you run new(bytes) which ends in an infinite recursion ;-)
i got both readanysf~ and tbfft2 running, changing largealloc ... well, since i don't know exactly, how you try to allocate the memory, i can't patch your code, but it should have something to do with the recursive execution of new() i suppose it should be run new( bytes - LARGEALLOC ) or new( bytes - LARGEALLOC - sizeof(size_t))
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
The only difference is that with the new allocation method the PD functions are used, while previous versions of flext used the ones of the c library. I'm not sure if the PD memory allocation can deal with the large number of implicit allocations of the C++ language. The reason for using the PD functions are that they may be faster but even that has to be verified. I'll shortly do some tests...
i see ... but you seem to run the same function again and again ...
if bytes is larger than largealloc, you run new(bytes) which ends in an infinite recursion ;-)
oh yes, many thanks for the hint... i introduced a quick fix which is not ideal, because large allocations should still be done by the c library. I have still to do some portability tests for the cleaner general solution.
best greetings, Thomas
X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit
i got both readanysf~ and tbfft2 running, changing largealloc ... well, since i don't know exactly, how you try to allocate the memory, i can't patch your code, but it should have something to do with the recursive execution of new() i suppose it should be run new( bytes - LARGEALLOC ) or new( bytes - LARGEALLOC - sizeof(size_t))
well, readanysf~ isn't working very well ... i can play back a soundfile, but if i try to open another soundfile, it segfaults ... but this segfault is caused by the thread handling:
mutex.Unlock(); // should be safe without locking, if (readsf != NULL) { // this will keep pd from blocking when //deleting a ReadMadUrl delete(readsf); }
this delete causes the segfault ... i'm not into threaded programming ... and i have no idea, why it worked with earlier versions of flext and doesn't any more ... (delete uses the c++ libraries) ... maybe thomas has some insights ... anyway, i'll check thomas' fix (probably in tomorrow's cvs)
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
well, readanysf~ isn't working very well ... i can play back a soundfile, but if i try to open another soundfile, it segfaults ... but this segfault is caused by the thread handling:
mutex.Unlock(); // should be safe without locking, if (readsf != NULL) { // this will keep pd from blocking when //deleting a ReadMadUrl delete(readsf); }
this delete causes the segfault ... i'm not into threaded programming ... and i have no idea, why it worked with earlier versions of flext and doesn't any more ... (delete uses the c++ libraries) ... maybe thomas has some insights ... anyway, i'll check thomas' fix (probably in tomorrow's cvs)
i applied thomas' fix, but it still segfaults when i try to open a second soundfile ... any idea? thomas?
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
where can I get a pd-36 ?
from miller puckette's website, http://crca.ucsd.edu/~msp/software.html
maybe im looking at the wrong place on the page, but I don't see a pd-36 there.
????
hi! http://crca.ucsd.edu/~msp/Software/ gives you the directory index for all downloadable files regards d13b
august wrote:
where can I get a pd-36 ?
from miller puckette's website, http://crca.ucsd.edu/~msp/software.html
maybe im looking at the wrong place on the page, but I don't see a pd-36 there.
????
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Oliver, I can't reproduce your error. I have the same problem with alsa as I do with every version of PD....it simply won't start with alsa. With oss over alsa, all seems to be working fine.
I just now compiled flext 0.4.1 with pd-0.36-0 and then readanysf~ with the 4.1 flext.
I read:
5B> > > I'm still using pd 0.36 (probably a bad idea) on a debian system.
although i succeeded in compiling readanysf~, it crashes PD anytime i create it.
-
0001 -
Ales Zemene -
august -
CK -
d -
Patrick Pagano -
stotz -
Thomas Grill -
Tim Blechmann