where is [mtx_*]?
i've loaded iemmatrix and iem_matrix
specs: Pd-0.40.3-extended-20081103 on ppc os x
Hmmm... I run across this thread when searching for information about [mtx_*~]. If I load iemmatrix and I instantiate [matrix~] it tells me that it is deprecated and please replace by [mtx_*~]. Which is fine until I save, quit Pd and reopen the patch after which [mtx_*~] is no longer available until I again instantiate the deprecated [matrix~] again. Following the advice given in this thread I created a [mtx_mul~] and it seems to behave the same as [mtx_*~]. Yet, [mtx_*~] alone is impossible to use. The rationale of this feature escapes me.
Is it safe to use [mtx_mul~] (i.e. it will not become deprecated sometime in the foreseeable future in favour of its * brother)?
Thanks
./MiS
On Fri, Nov 14, 2008 at 4:20 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
Max wrote:
where is [mtx_*]?
it's in iemmatrix.
i've loaded iemmatrix and iem_matrix
try instantiating [mtx_mul]. afterwards you might be able to use [mtx_*] directly.
gfmadr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I also run across another thread http://www.mail-archive.com/pd-list@iem.at/msg37440.html which states that [mtx_mul~] has been deprecated. Yet, deprecated objects are needed to be able to instantiate their replacements. What gives?
On Thu, Sep 16, 2010 at 10:53 AM, Michal Seta mis@artengine.ca wrote:
Hmmm... I run across this thread when searching for information about [mtx_*~]. If I load iemmatrix and I instantiate [matrix~] it tells me that it is deprecated and please replace by [mtx_*~]. Which is fine until I save, quit Pd and reopen the patch after which [mtx_*~] is no longer available until I again instantiate the deprecated [matrix~] again. Following the advice given in this thread I created a [mtx_mul~] and it seems to behave the same as [mtx_*~]. Yet, [mtx_*~] alone is impossible to use. The rationale of this feature escapes me.
Is it safe to use [mtx_mul~] (i.e. it will not become deprecated sometime in the foreseeable future in favour of its * brother)?
Thanks
./MiS
On Fri, Nov 14, 2008 at 4:20 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
Max wrote:
where is [mtx_*]?
it's in iemmatrix.
i've loaded iemmatrix and iem_matrix
try instantiating [mtx_mul]. afterwards you might be able to use [mtx_*] directly.
gfmadr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 2010-09-16 16:53, Michal Seta wrote:
[mtx_mul~] and it seems to behave the same as [mtx_*~]. Yet, [mtx_*~] alone is impossible to use. The rationale of this feature escapes me.
in pd-extended, iemmatrix is somewhat broken (which is not iemmatrix's fault but the way how pd-extended likes libraries to be)
afaik, this has been fixed in the upcoming pd-extended (at least of you load the hexloader)
fgmasdr IOhannes
On Thu, 16 Sep 2010, Michal Seta wrote:
Following the advice given in this thread I created a [mtx_mul~] and it seems to behave the same as [mtx_*~]. Yet, [mtx_*~] alone is impossible to use. The rationale of this feature escapes me.
It depends on the build. Roman has been making fixes to pd-extended so that the separate-external build works correctly. When aliases inside the source code are not reflected as aliases in the filesystem, this is what you get.
Another way to avoid the problem is to build all of iemmatrix as an all-together library (one pd_linux for all externs). Some people have been doing that while pd-extended's build of iemmatrix was broken.
| Mathieu Bouchard ------------------------------ Villeray, Montréal, QC
-
IOhannes m zmoelnig -
Mathieu Bouchard -
Max -
Michal Seta