Hello you all,
does anyone uses the [stop] message with readanysf~ ?
i saw several posts on the list, that there is a bug or something (at least on my debian unstable, pd-0.39.2,flext 0.5.0, latest readanysf~, it crashes while freeing some ressources...with vorbis library it segfaults..)
is there any combination (maybe precompiled linux pd-extended binaries) that work?
or is there any other object doing the same stuff?
i think, someone have asked all this before: so sorry for that...
greetings mart
Hallo!
with readanysf~ ?
or is there any other object doing the same stuff?
[sndfiler] since it uses libsndfile, the latest versions of which support .ogg and maybe FLAC (but definitely not mp3), it would be my first choice..
well, but sndfiler reads the samples into the ram ...
What is your problem with readanysf~ ? The version from cvs should compile ...
LG Georg
On Di, 2006-08-01 at 22:44 +0200, Georg Holzmann wrote:
Hallo!
with readanysf~ ?
or is there any other object doing the same stuff?
[sndfiler] since it uses libsndfile, the latest versions of which support .ogg and maybe FLAC (but definitely not mp3), it would be my first choice..
well, but sndfiler reads the samples into the ram ...
What is your problem with readanysf~ ?
i think readanysf~ is really great!
The version from cvs should compile ...
it compiles without any problem...
and it plays...
but: it crashes on my system when i send a "stop" message to it...
i found that it might has something to do with FLEXT_NOGLOBALNEW or FLEXT_USE_CMEM...
but i cannot find out what to do...
greetings mart
LG Georg
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo!
it compiles without any problem...
and it plays...
but: it crashes on my system when i send a "stop" message to it...
okay ...
i found that it might has something to do with FLEXT_NOGLOBALNEW or FLEXT_USE_CMEM...
yes, but this is already fixed if you have the cvs source.
You can try to debug it a little bit more: start pd with gdb: gdb pd then run the patch inside gdb: run and after the crash type: bt
then you should get more information why it crashes ...
LG Georg