Menu
▾
▴
ftm-devel — Mailing-list concerning the development of FTM as well as modules using FTM.
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
(7) |
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(1) |
Oct
|
Nov
|
Dec
(18) |
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(27) |
Oct
(22) |
Nov
(117) |
Dec
(35) |
| 2008 |
Jan
(52) |
Feb
(48) |
Mar
(10) |
Apr
(2) |
May
|
Jun
(19) |
Jul
(5) |
Aug
(4) |
Sep
(3) |
Oct
(2) |
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
(4) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(2) |
Oct
(6) |
Nov
(6) |
Dec
|
|
From: Norbert S. <Nor...@ir...> - 2012-11-30 13:45:12
|
Hi Stefano, If I understand right you are asking for something that is simply not possible in the development of any Max externals. We are not aware of any method to un/reload binaries from/into a running application. Norbert On 30 Nov 2012, at 13:35, Stefano Fasciani wrote: > Sorry but I got confused with my abstractions in the previous mail… my ftm externals are in the same folder of the FTM distribution externals. > > Stefano Fasciani > Arts and Creativity Lab - http://anclab.org > Interactive and Digital Media Institute > National University of Singapore > Website: http://stefanofasciani.com > Email: ste...@nu... > Email: ste...@st... > Mobile SG: +65 84 28 64 24 > Mobile IT: +39 328 97 86 008 > > > On Nov 30, 2012, at 7:55 PM, Stefano Fasciani wrote: >> Dear all, >> >> is it possible to reload the FTM package without having to terminate and reload MAX? If yes how? (FYI I have the ftm.startup.mxo installed to load the package at startup). >> >> I'm asking this because in the process of developing externals, I continuously rebuild my .mxo (fixing bugs, debugging, ….) but in order to run the newly built .mxo I have to restart MAX. It does not take that long… but would be nice to do something within max to avoid restart. >> >> I do not even know if this depends by the FTM package, as my ftm externals are in a separate folder (but always in the MAX search path). >> >> Thanks >> >> Stefano Fasciani >> Arts and Creativity Lab - http://anclab.org >> Interactive and Digital Media Institute >> National University of Singapore >> Website: http://stefanofasciani.com >> Email: ste...@nu... >> Email: ste...@st... >> Mobile SG: +65 84 28 64 24 >> Mobile IT: +39 328 97 86 008 >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Keep yourself connected to Go Parallel: >> TUNE You got it built. Now make it sing. Tune shows you how. >> http://goparallel.sourceforge.net_______________________________________________ >> ftm-devel mailing list >> ftm...@li... >> https://lists.sourceforge.net/lists/listinfo/ftm-devel > > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > TUNE You got it built. Now make it sing. Tune shows you how. > http://goparallel.sourceforge.net_______________________________________________ > ftm-devel mailing list > ftm...@li... > https://lists.sourceforge.net/lists/listinfo/ftm-devel |
|
From: Stefano F. <ste...@nu...> - 2012-11-30 12:35:55
|
Sorry but I got confused with my abstractions in the previous mail… my ftm externals are in the same folder of the FTM distribution externals. Stefano Fasciani Arts and Creativity Lab - http://anclab.org Interactive and Digital Media Institute National University of Singapore Website: http://stefanofasciani.com Email: ste...@nu... Email: ste...@st... Mobile SG: +65 84 28 64 24 Mobile IT: +39 328 97 86 008 On Nov 30, 2012, at 7:55 PM, Stefano Fasciani wrote: > Dear all, > > is it possible to reload the FTM package without having to terminate and reload MAX? If yes how? (FYI I have the ftm.startup.mxo installed to load the package at startup). > > I'm asking this because in the process of developing externals, I continuously rebuild my .mxo (fixing bugs, debugging, ….) but in order to run the newly built .mxo I have to restart MAX. It does not take that long… but would be nice to do something within max to avoid restart. > > I do not even know if this depends by the FTM package, as my ftm externals are in a separate folder (but always in the MAX search path). > > Thanks > > Stefano Fasciani > Arts and Creativity Lab - http://anclab.org > Interactive and Digital Media Institute > National University of Singapore > Website: http://stefanofasciani.com > Email: ste...@nu... > Email: ste...@st... > Mobile SG: +65 84 28 64 24 > Mobile IT: +39 328 97 86 008 > > > > > > > > > > > > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > TUNE You got it built. Now make it sing. Tune shows you how. > http://goparallel.sourceforge.net_______________________________________________ > ftm-devel mailing list > ftm...@li... > https://lists.sourceforge.net/lists/listinfo/ftm-devel |
|
From: Stefano F. <ste...@nu...> - 2012-11-30 12:18:06
|
Dear all, is it possible to reload the FTM package without having to terminate and reload MAX? If yes how? (FYI I have the ftm.startup.mxo installed to load the package at startup). I'm asking this because in the process of developing externals, I continuously rebuild my .mxo (fixing bugs, debugging, ….) but in order to run the newly built .mxo I have to restart MAX. It does not take that long… but would be nice to do something within max to avoid restart. I do not even know if this depends by the FTM package, as my ftm externals are in a separate folder (but always in the MAX search path). Thanks Stefano Fasciani Arts and Creativity Lab - http://anclab.org Interactive and Digital Media Institute National University of Singapore Website: http://stefanofasciani.com Email: ste...@nu... Email: ste...@st... Mobile SG: +65 84 28 64 24 Mobile IT: +39 328 97 86 008 |
|
From: Alexander D. <ale...@go...> - 2012-11-19 10:20:04
|
HiNorbert,
thanks a lot for this very detailed explanation!
Until now I didn't find thetime to try out everything but I'm pretty
confident to manage it with that info.
What I already had a look at is setting/getting editor attr likefor example:
object_attr_setparse(editor, gensym("view_interface"), "matrix");
object_attr_get(editor, gensym("view_interface")); It works!
Also great that you gave an idea how the ftm listeners can be used.
I already asked myself how that could be done.
Thanks again, greetings,
Alex
Am 17.11.12 20:27, schrieb Norbert Schnell:
> Hi Alexander,
>
> On 17 Nov 2012, at 16:26, Alexander Droste wrote:
>> Hi everyone,
>>
>> in a previous mail the ways of getting a ref of a fts object to a c external were already named.
>> - sending them in a message to your external
>> - giving them as arguments (like $myfmat $yourfmat) of your external
>> - obtaining them from the current "FTM scope"
>>
>> Now I'd like to know how one of these ways can be realised in detail.
> Ok, here are some hints for the three options.
> ________________________________
> OPTION 1
>
> Using the FTMEXT API, external arguments (symbols) starting with $ are automatically transformed from the $-lead name into references to FTM objects – a special FTM-only type of atoms – that can be retrieved with the functions fts_is_object(argv) and fts_get_object(argv).
> FTM hereby assures the reinstantiation of an external whenever the definition of a name (by ftm.object) that it depends of changes – in local or global scope.
>
> The function fts_get_object() returns a pointer to an FTM object (fts_object_t *).
>
> ________________________________
> OPTION 2
>
> Incoming messages also can include these special atoms and you can apply the same functions also directly to the arguments of a message defined with A_GIMME.
> This is the easiest, but far from the most elegant solution.
> The FTM name ($myobj) in this case is typically resolved by the FTM message box where you compose the message that you send to your external.
>
> ________________________________
> OPTION 3
>
> For the third option you need the pointer to the patcher of your object:
> - fts_scope_t *maxpat_get_scope(t_object *pat) ... returns the FTM scope of a given Max patcher (ftmexternals.h)
> - fts_hashtable_t *fts_scope_get_values(fts_scope_t *scope) ... returns an hashtable with the names defined in this scope (ftmexternals.h)
> - fts_hashtable_get( const fts_hashtable_t *self, const fts_atom_t *key, fts_atom_t *value) ... gives you an atom bound to a name by ftm.object (hashtable.h)
> - fts_object_t *atom.h: fts_object_t *fts_get_object(const fts_atom_t *atom) ... returns a pointer to the FTM object of the atom as mentioned above (atom.h)
>
> ... and than you can inspect your object.
> BUT: you must do this in the right moment AFTER the definition of the name by ftm.object.
>
> SO: You have to implement a listener callback:
> - void my_name_callback(void *listener, fts_symbol_t name);
>
> ... and install a listener (namedef.h) using:
> - void fts_name_add_listener(fts_scope_t *patcher, fts_symbol_t name, void *listener, fts_name_listener_callback_t callback)
>
> This listener is called as soon as the ftm.object defines the name and each time the name is redefined or removed.
> In the callback you retrieve your object defined by an ftm.object using the sequence of functions given above.
>
> I hope one of that works for you.
>
>> To give some background information: The patches where I would like to get the refs contain a static constellation of objects.
>> All of these patches contain a ref collector-object which collects the references of the objects needed.
>> At the moment this ref collection is limited to standart max types which I get through iteration in the patch identifying them by scripting name.
>> This iteration is done with a standart (non-ftm) max external but my xcode project is succesfully linked against the ftm-sdk2.6 so if needed i could switch that.
>>
>> Since all required objects are in the same patcher maybe "FTM scope" sounds like a good option
>> or would it be a lot easier to build the external as a ftm external and give them as arguments?
>>
>> In detail I need refs to fmats, mats
> Ok, until here with the above options.
>
>> and ftm.messages, ftm.editors.
> These are themselves standard (well, sort of) Max externals and not FTM object such as instances of fmat, mat, dict etc.
> As far as I remember, you can find examples in the Max SDK showing how to get the Max externals of a particular patcher.
>
>> Can the last two also be obtained through iteration and scripting name or is it advisable to do it another way?
> Should work, I guess, but evidently the scripting names have nothing to do with the FTM names...
>
>> With ftm.message I only would like to be able to set the string/symbol.(like it can be done in max with #set xy)
>> So the plan is to get the pointer and then send the "#set" message to the ftm.message object.
>> Getting a pointer to an editor I hope it is possible to get, set values of attributes, namely: (choose view) interface, (view shape) shape.
>> Can it be done like with standart max objects with s.th like: object_attr_getvalueof, object_attr_setvalueof ?
> Probably.
>
>> What is not essentially required but would come in handy would be to set the track refs in an editor from an external. Is that possible?
> Sure you just have to send it an appropriate Max message using the Max API.
> There is also an fts_set_object(t_atom *atom, fts_object_t *obj) to set a (message) argument to the special FTM-only object atom type.
>
> Hope that helps.
>
> Cheers
> Norbert
>
|
|
From: Norbert S. <Nor...@ir...> - 2012-11-17 19:52:28
|
Hi Alexander, On 17 Nov 2012, at 16:26, Alexander Droste wrote: > Hi everyone, > > in a previous mail the ways of getting a ref of a fts object to a c external were already named. > - sending them in a message to your external > - giving them as arguments (like $myfmat $yourfmat) of your external > - obtaining them from the current "FTM scope" > > Now I'd like to know how one of these ways can be realised in detail. Ok, here are some hints for the three options. ________________________________ OPTION 1 Using the FTMEXT API, external arguments (symbols) starting with $ are automatically transformed from the $-lead name into references to FTM objects – a special FTM-only type of atoms – that can be retrieved with the functions fts_is_object(argv) and fts_get_object(argv). FTM hereby assures the reinstantiation of an external whenever the definition of a name (by ftm.object) that it depends of changes – in local or global scope. The function fts_get_object() returns a pointer to an FTM object (fts_object_t *). ________________________________ OPTION 2 Incoming messages also can include these special atoms and you can apply the same functions also directly to the arguments of a message defined with A_GIMME. This is the easiest, but far from the most elegant solution. The FTM name ($myobj) in this case is typically resolved by the FTM message box where you compose the message that you send to your external. ________________________________ OPTION 3 For the third option you need the pointer to the patcher of your object: - fts_scope_t *maxpat_get_scope(t_object *pat) ... returns the FTM scope of a given Max patcher (ftmexternals.h) - fts_hashtable_t *fts_scope_get_values(fts_scope_t *scope) ... returns an hashtable with the names defined in this scope (ftmexternals.h) - fts_hashtable_get( const fts_hashtable_t *self, const fts_atom_t *key, fts_atom_t *value) ... gives you an atom bound to a name by ftm.object (hashtable.h) - fts_object_t *atom.h: fts_object_t *fts_get_object(const fts_atom_t *atom) ... returns a pointer to the FTM object of the atom as mentioned above (atom.h) ... and than you can inspect your object. BUT: you must do this in the right moment AFTER the definition of the name by ftm.object. SO: You have to implement a listener callback: - void my_name_callback(void *listener, fts_symbol_t name); ... and install a listener (namedef.h) using: - void fts_name_add_listener(fts_scope_t *patcher, fts_symbol_t name, void *listener, fts_name_listener_callback_t callback) This listener is called as soon as the ftm.object defines the name and each time the name is redefined or removed. In the callback you retrieve your object defined by an ftm.object using the sequence of functions given above. I hope one of that works for you. > To give some background information: The patches where I would like to get the refs contain a static constellation of objects. > All of these patches contain a ref collector-object which collects the references of the objects needed. > At the moment this ref collection is limited to standart max types which I get through iteration in the patch identifying them by scripting name. > This iteration is done with a standart (non-ftm) max external but my xcode project is succesfully linked against the ftm-sdk2.6 so if needed i could switch that. > > Since all required objects are in the same patcher maybe "FTM scope" sounds like a good option > or would it be a lot easier to build the external as a ftm external and give them as arguments? > > In detail I need refs to fmats, mats Ok, until here with the above options. > and ftm.messages, ftm.editors. These are themselves standard (well, sort of) Max externals and not FTM object such as instances of fmat, mat, dict etc. As far as I remember, you can find examples in the Max SDK showing how to get the Max externals of a particular patcher. > Can the last two also be obtained through iteration and scripting name or is it advisable to do it another way? Should work, I guess, but evidently the scripting names have nothing to do with the FTM names... > With ftm.message I only would like to be able to set the string/symbol.(like it can be done in max with #set xy) > So the plan is to get the pointer and then send the "#set" message to the ftm.message object. > Getting a pointer to an editor I hope it is possible to get, set values of attributes, namely: (choose view) interface, (view shape) shape. > Can it be done like with standart max objects with s.th like: object_attr_getvalueof, object_attr_setvalueof ? Probably. > What is not essentially required but would come in handy would be to set the track refs in an editor from an external. Is that possible? Sure you just have to send it an appropriate Max message using the Max API. There is also an fts_set_object(t_atom *atom, fts_object_t *obj) to set a (message) argument to the special FTM-only object atom type. Hope that helps. Cheers Norbert |
|
From: Alexander D. <ale...@go...> - 2012-11-17 15:26:55
|
Hi everyone, in a previous mail the ways of getting a ref of a fts objectto a c external were already named. - sending them in a message to your external - giving them as arguments (like $myfmat $yourfmat) of your external - obtaining them from the current "FTM scope" Now I'd like to know how one of these ways can be realised in detail. To give some background information:The patches where I would like to get the refs contain a static constellation of objects. All of these patches containa ref collector-object which collectsthe references of the objects needed. At the moment this ref collection is limited to standart max typeswhich I get through iteration in the patch identifying them by scripting name. This iteration isdone with a standart (non-ftm) max external but my xcode project is succesfully linked against theftm-sdk2.6 so if needed i could switch that. Since all required objects are in the same patcher maybe "FTM scope" sounds like a good option or would it be a lot easier to build the external as a ftm external and give them as arguments? In detail I need refs to fmats, mats and ftm.messages, ftm.editors. Can the last two also be obtained through iteration and scripting name or is it advisable to do itanother way? With ftm.message I only would like to be able to set the string/symbol.(like it can be done in max with #set xy) So the plan is to get the pointer and then send the "#set" message to the ftm.message object. Getting a pointer to an editor I hope it is possible to get, set values of attributes, namely: (choose view) interface, (view shape) shape. Can it be done like with standart max objectswith s.th like: object_attr_getvalueof, object_attr_setvalueof ? What is not essentially required but would come in handy would be to set the track refs in an editor from an external. Is that possible? Ok, that's a lot of questions. Maybe someone can put some light into this. Greetings, Alex |
|
From: Stefano F. <ste...@nu...> - 2012-10-08 12:18:53
|
I finished to build and test all my ftm external with 2.6 SDK. No problem in building and functionally are all ok. Cheers Stefano Fasciani Arts and Creativity Lab (http://anclab.org) Multimodal Analysis Lab (http://multimodal-analysis-lab.org/) Interactive and Digital Media Institute National University of Singapore Email: ste...@nu... Mobile: +65 84 28 64 24 On Oct 5, 2012, at 11:21 PM, Norbert Schnell wrote: > Hi again Stefano, > >> However I would like to share some problems/issues I found with the current 2.6 SDK: >> some of these may be due the fact I'm using max6 rather than max5 (from otool output seems that Norbert and Riccardo are using max5) >> and probably different OSX version and XCode version (I had to do some changes in the xcode project also to SDK 2.5 to make it work but it was easier...). > > > Well, we compile with the Max 5 SDK, but everything should work well in Max 6. > And yes, we're still stuck on Mac OS 10.6 :-) > >> By the way my configuration is: >> OSX 10.7.5 >> MAX 6.0.7 >> XCode 4.3.2 >> FTM 2.6 >> >> 1) in the install-mxo.sh I had to change the developer tool directory (had to do the same on FTM SDK 2.5). I do not remember when this change was introduced (from which XCode or OSX version)… but it has been a while that XCode is installed into the Application directory >> >> # set bundle bit for mxo's (on some installations, they show up as directories) >> /Developer/Tools/SetFile -a B $proddir >> CHANGED TO >> /Applications/Xcode.app/Contents/Developer/Tools/SetFile -a B $proddir > > Ok, we'll try to figure out how to do this independently of the OS version. > >> 2) in the Max6 SDK (I'm using the latest one MaxSDK-6.0.4) the folder structure seems to be a bit different than the Max5 SDK… therefore in the xcode project options I had to change (was the same with FTM SDK 2.5) >> $(C74_SUPPORT_DIR)/max-includes/MaxAPI.framework/Versions/A/Headers/macho-prefix.pch >> CHANGED TO >> $(C74_SUPPORT_DIR)/max-includes/macho-prefix.pch >> >> the header path, framework path and C74_SUPPORT_DIR framework must be changed accordingly… > > > Yes, ok, it makes sense to switch to the Max 6 SDK, even if we'll stick to the Max 5 API. > >> 3) File path with SPACE … !!!!! (I wasted 2 days chasing include, linker and script problems coming from the same bloody SPACE) > > Thanks a lot especially for this one. > >> So I'm wondering if it's odd to have a SPACE in the path (I'm not a big fan of spaces, but blame cycling 74 for that…. :D , I think other people will end up with a similar problem) therefore I have either to rename my "Cycling '74" folder or move my "ftm-and-co" folder one level up…. or if the SDK (project and script) should be modified in order to be compliant also with paths containing SPACES. > > Yeah, let's have more SPACE in the paths!!!! > ... even if it makes more quotes in the scripts. > >> Next week I will try to compile and run a dozen of ftm externals I've developed…. I will keep you updated in case I find other problems or bugs! > > Please. > > Thanks again > Norbert > >> Have a good weekend! >> >> Cheers >> >> Stefano Fasciani >> Arts and Creativity Lab (http://anclab.org) >> Multimodal Analysis Lab (http://multimodal-analysis-lab.org/) >> Interactive and Digital Media Institute >> National University of Singapore >> Email: ste...@nu... >> Mobile: +65 84 28 64 24 >> >> >> >> >> >> >> On Oct 3, 2012, at 9:51 PM, Norbert Schnell wrote: >> >>> Hi all, >>> >>> We just published an updated FTM External SDK that is compatible with FTM & Co 2.6 here: >>> http://ftm.ircam.fr/index.php/SDK >>> >>> For those who already used the FTM External SDK 2.5, this is what really changed in this version: >>> - the script "install-mxo.sh" in the "build" folder of the SDK >>> - the "Header Search Paths" variable (HEADER_SEARCH_PATHS) in the Xcode build project >>> - the "Other Linker Flags" variable (OTHER_LDFLAGS) in the Xcode build project >>> >>> Best, >>> Norbert & Riccardo >>> >>> <message-footer.txt> >> >> FTM & Co >> wiki: http://ftm.ircam.fr/ >> mailing-list: http://listes.ircam.fr/wws/info/ftm >> bug reports: mailto:ftm...@ir... > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev_______________________________________________ > ftm-devel mailing list > ftm...@li... > https://lists.sourceforge.net/lists/listinfo/ftm-devel |
|
From: Stefano F. <ste...@nu...> - 2012-10-07 08:58:43
|
Hi Norbert, you are welcome! Thank to you guys for providing the FTM library and the SDK…. it really makes my project integration in MAX much easier. Regards Stefano Fasciani Arts and Creativity Lab (http://anclab.org) Multimodal Analysis Lab (http://multimodal-analysis-lab.org/) Interactive and Digital Media Institute National University of Singapore Email: ste...@nu... Mobile: +65 84 28 64 24 On Oct 5, 2012, at 11:21 PM, Norbert Schnell wrote: > Hi again Stefano, > >> However I would like to share some problems/issues I found with the current 2.6 SDK: >> some of these may be due the fact I'm using max6 rather than max5 (from otool output seems that Norbert and Riccardo are using max5) >> and probably different OSX version and XCode version (I had to do some changes in the xcode project also to SDK 2.5 to make it work but it was easier...). > > > Well, we compile with the Max 5 SDK, but everything should work well in Max 6. > And yes, we're still stuck on Mac OS 10.6 :-) > >> By the way my configuration is: >> OSX 10.7.5 >> MAX 6.0.7 >> XCode 4.3.2 >> FTM 2.6 >> >> 1) in the install-mxo.sh I had to change the developer tool directory (had to do the same on FTM SDK 2.5). I do not remember when this change was introduced (from which XCode or OSX version)… but it has been a while that XCode is installed into the Application directory >> >> # set bundle bit for mxo's (on some installations, they show up as directories) >> /Developer/Tools/SetFile -a B $proddir >> CHANGED TO >> /Applications/Xcode.app/Contents/Developer/Tools/SetFile -a B $proddir > > Ok, we'll try to figure out how to do this independently of the OS version. > >> 2) in the Max6 SDK (I'm using the latest one MaxSDK-6.0.4) the folder structure seems to be a bit different than the Max5 SDK… therefore in the xcode project options I had to change (was the same with FTM SDK 2.5) >> $(C74_SUPPORT_DIR)/max-includes/MaxAPI.framework/Versions/A/Headers/macho-prefix.pch >> CHANGED TO >> $(C74_SUPPORT_DIR)/max-includes/macho-prefix.pch >> >> the header path, framework path and C74_SUPPORT_DIR framework must be changed accordingly… > > > Yes, ok, it makes sense to switch to the Max 6 SDK, even if we'll stick to the Max 5 API. > >> 3) File path with SPACE … !!!!! (I wasted 2 days chasing include, linker and script problems coming from the same bloody SPACE) > > Thanks a lot especially for this one. > >> So I'm wondering if it's odd to have a SPACE in the path (I'm not a big fan of spaces, but blame cycling 74 for that…. :D , I think other people will end up with a similar problem) therefore I have either to rename my "Cycling '74" folder or move my "ftm-and-co" folder one level up…. or if the SDK (project and script) should be modified in order to be compliant also with paths containing SPACES. > > Yeah, let's have more SPACE in the paths!!!! > ... even if it makes more quotes in the scripts. > >> Next week I will try to compile and run a dozen of ftm externals I've developed…. I will keep you updated in case I find other problems or bugs! > > Please. > > Thanks again > Norbert > >> Have a good weekend! >> >> Cheers >> >> Stefano Fasciani >> Arts and Creativity Lab (http://anclab.org) >> Multimodal Analysis Lab (http://multimodal-analysis-lab.org/) >> Interactive and Digital Media Institute >> National University of Singapore >> Email: ste...@nu... >> Mobile: +65 84 28 64 24 >> >> >> >> >> >> >> On Oct 3, 2012, at 9:51 PM, Norbert Schnell wrote: >> >>> Hi all, >>> >>> We just published an updated FTM External SDK that is compatible with FTM & Co 2.6 here: >>> http://ftm.ircam.fr/index.php/SDK >>> >>> For those who already used the FTM External SDK 2.5, this is what really changed in this version: >>> - the script "install-mxo.sh" in the "build" folder of the SDK >>> - the "Header Search Paths" variable (HEADER_SEARCH_PATHS) in the Xcode build project >>> - the "Other Linker Flags" variable (OTHER_LDFLAGS) in the Xcode build project >>> >>> Best, >>> Norbert & Riccardo >>> >>> <message-footer.txt> >> >> FTM & Co >> wiki: http://ftm.ircam.fr/ >> mailing-list: http://listes.ircam.fr/wws/info/ftm >> bug reports: mailto:ftm...@ir... > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev_______________________________________________ > ftm-devel mailing list > ftm...@li... > https://lists.sourceforge.net/lists/listinfo/ftm-devel |
|
From: Stefano F. <ste...@nu...> - 2012-10-06 09:33:03
|
Hi All, I spend couple of days in trying to use the new 2.6 SDK and I have just succeeded in building and running the 3 example externals (coucou pack pingpong~), next week I will try to build my own ftm externals to verify wether the functionality it is still correct. I like the 2.6 SDK better than the 2.5 because I think it's easier to keep a clean an neat folder tree organization since everything is packed in the ftm.mxo (headers and lib) and the built .mxo just need to stay in the same folder of the ftm.mxo which is easy and it also make a lot of sense! (I had problem with 2.5 when I wanted to place the built .mxo in the folder I want, because of the linking with the FTMframework… etc… etc… ) However I would like to share some problems/issues I found with the current 2.6 SDK: some of these may be due the fact I'm using max6 rather than max5 (from otool output seems that Norbert and Riccardo are using max5) and probably different OSX version and XCode version (I had to do some changes in the xcode project also to SDK 2.5 to make it work but it was easier...). By the way my configuration is: OSX 10.7.5 MAX 6.0.7 XCode 4.3.2 FTM 2.6 1) in the install-mxo.sh I had to change the developer tool directory (had to do the same on FTM SDK 2.5). I do not remember when this change was introduced (from which XCode or OSX version)… but it has been a while that XCode is installed into the Application directory # set bundle bit for mxo's (on some installations, they show up as directories) /Developer/Tools/SetFile -a B $proddir CHANGED TO /Applications/Xcode.app/Contents/Developer/Tools/SetFile -a B $proddir 2) in the Max6 SDK (I'm using the latest one MaxSDK-6.0.4) the folder structure seems to be a bit different than the Max5 SDK… therefore in the xcode project options I had to change (was the same with FTM SDK 2.5) $(C74_SUPPORT_DIR)/max-includes/MaxAPI.framework/Versions/A/Headers/macho-prefix.pch CHANGED TO $(C74_SUPPORT_DIR)/max-includes/macho-prefix.pch the header path, framework path and C74_SUPPORT_DIR framework must be changed accordingly… 3) File path with SPACE … !!!!! (I wasted 2 days chasing include, linker and script problems coming from the same bloody SPACE) In Max6 all the externals are by default installed under sub-folders of /Applications/Max6/Cycling '74/ By consequence the FTM installer place all my FTM stuff under "/Applications/Max6/Cycling '74/ftm-and-co/" Hence my EXTERNALS_DIR is /Applications/Max6/Cycling '74/ftm-and-co/externals This means that the Framework and Header paths contains a SPACE character. Therefore to avoid that the include path (same valid for framework path) "/Applications/Max6/Cycling '74/ftm-and-co/externals/ftm.mxo/Contents/Headers" it is interpreted as -I/Applications/Max6/Cycling -I'74/ftm-and-co/externals/ftm.mxo/Contents/Headers (and obviously it does not find any .h file) I had to modify the Xcode project option changing Headers Search Path (same issue for the linker….) $(EXTERNALS_DIR)/ftm.mxo/Contents/Headers CHANGE TO "$(EXTERNALS_DIR)/ftm.mxo/Contents/Headers" For the framework $(EXTERNALS_DIR) to "$(EXTERNALS_DIR)" 3a) However having a space in the path it is probably an issue also for the install-mxo.sh (default_dir=$EXTERNALS_DIR)…. I'm not 100% sure of this… for instance I force FTMLIB_FRAMEWORK="/Applications/Max6/Cycling '74/ftm-and-co/externals/ftm.mxo/Contents/MacOS/ftm" I obtain a wrong FTMLIB_FRAMEWORK_RELATIVE [patching dynamic library from '/Applications/Max6/Cycling '74/ftm-and-co/externals/ftm.mxo/Contents/MacOS/ftm' to '/Applications/Max6/Cycling' The command generating the FTMLIB_FRAMEWORK_RELATIVE looks a bit complicated, so I did not go into details…. 3b) Moreover… once I manage to compile (all ok on the Xcode), the install-mxo.sh script was failing with this error (the .mxo was generated correctly but not copied to destination…. ditto was failing) [patching dynamic library from '/Users/schnell/Development/ftm-and-co/ftm/build/max5/osx-macho/build/Debug/ftm.mxo/Contents/MacOS/ftm' to '@loader_path/../../../ftm.mxo/Contents/MacOS/ftm' in '/Users/stefanofasciani/Library/Developer/Xcode/DerivedData/ftmext-examples-awyhdzotqmvzfibrslpiovhskuar/Build/Products/Release/fff.pack.mxo/Contents/MacOS/fff.pack'] [removing /Applications/Max6/Cycling '74/ftm-and-co/externals/fff.pack.mxo] [installing fff.pack.mxo as /Applications/Max6/Cycling '74/ftm-and-co/externals/fff.pack.mxo] ditto: can't get real path for source Command /bin/sh failed with exit code 1 After trying complex stuff I figured out that was enough to change ditto --rsrc $proddir $installdir CHANGE TO ditto --rsrc $proddir "$installdir" Even if the variable $installdir=/Applications/Max6/Cycling '74/ftm-and-co/externals/fff.pack.mxo variable was correct…. it was misinterpreted by the ditto command because of the same bloody space!!!! To be more safe I've put the quotes also on $proddir ditto --rsrc "$proddir" "$installdir" So I'm wondering if it's odd to have a SPACE in the path (I'm not a big fan of spaces, but blame cycling 74 for that…. :D , I think other people will end up with a similar problem) therefore I have either to rename my "Cycling '74" folder or move my "ftm-and-co" folder one level up…. or if the SDK (project and script) should be modified in order to be compliant also with paths containing SPACES. Next week I will try to compile and run a dozen of ftm externals I've developed…. I will keep you updated in case I find other problems or bugs! Have a good weekend! Cheers Stefano Fasciani Arts and Creativity Lab (http://anclab.org) Multimodal Analysis Lab (http://multimodal-analysis-lab.org/) Interactive and Digital Media Institute National University of Singapore Email: ste...@nu... Mobile: +65 84 28 64 24 On Oct 3, 2012, at 9:51 PM, Norbert Schnell wrote: > Hi all, > > We just published an updated FTM External SDK that is compatible with FTM & Co 2.6 here: > http://ftm.ircam.fr/index.php/SDK > > For those who already used the FTM External SDK 2.5, this is what really changed in this version: > - the script "install-mxo.sh" in the "build" folder of the SDK > - the "Header Search Paths" variable (HEADER_SEARCH_PATHS) in the Xcode build project > - the "Other Linker Flags" variable (OTHER_LDFLAGS) in the Xcode build project > > Best, > Norbert & Riccardo > > <message-footer.txt> |
|
From: Norbert S. <Nor...@ir...> - 2012-10-05 15:21:10
|
Hi again Stefano, > However I would like to share some problems/issues I found with the current 2.6 SDK: > some of these may be due the fact I'm using max6 rather than max5 (from otool output seems that Norbert and Riccardo are using max5) > and probably different OSX version and XCode version (I had to do some changes in the xcode project also to SDK 2.5 to make it work but it was easier...). Well, we compile with the Max 5 SDK, but everything should work well in Max 6. And yes, we're still stuck on Mac OS 10.6 :-) > By the way my configuration is: > OSX 10.7.5 > MAX 6.0.7 > XCode 4.3.2 > FTM 2.6 > > 1) in the install-mxo.sh I had to change the developer tool directory (had to do the same on FTM SDK 2.5). I do not remember when this change was introduced (from which XCode or OSX version)… but it has been a while that XCode is installed into the Application directory > > # set bundle bit for mxo's (on some installations, they show up as directories) > /Developer/Tools/SetFile -a B $proddir > CHANGED TO > /Applications/Xcode.app/Contents/Developer/Tools/SetFile -a B $proddir Ok, we'll try to figure out how to do this independently of the OS version. > 2) in the Max6 SDK (I'm using the latest one MaxSDK-6.0.4) the folder structure seems to be a bit different than the Max5 SDK… therefore in the xcode project options I had to change (was the same with FTM SDK 2.5) > $(C74_SUPPORT_DIR)/max-includes/MaxAPI.framework/Versions/A/Headers/macho-prefix.pch > CHANGED TO > $(C74_SUPPORT_DIR)/max-includes/macho-prefix.pch > > the header path, framework path and C74_SUPPORT_DIR framework must be changed accordingly… Yes, ok, it makes sense to switch to the Max 6 SDK, even if we'll stick to the Max 5 API. > 3) File path with SPACE … !!!!! (I wasted 2 days chasing include, linker and script problems coming from the same bloody SPACE) Thanks a lot especially for this one. > So I'm wondering if it's odd to have a SPACE in the path (I'm not a big fan of spaces, but blame cycling 74 for that…. :D , I think other people will end up with a similar problem) therefore I have either to rename my "Cycling '74" folder or move my "ftm-and-co" folder one level up…. or if the SDK (project and script) should be modified in order to be compliant also with paths containing SPACES. Yeah, let's have more SPACE in the paths!!!! ... even if it makes more quotes in the scripts. > Next week I will try to compile and run a dozen of ftm externals I've developed…. I will keep you updated in case I find other problems or bugs! Please. Thanks again Norbert > Have a good weekend! > > Cheers > > Stefano Fasciani > Arts and Creativity Lab (http://anclab.org) > Multimodal Analysis Lab (http://multimodal-analysis-lab.org/) > Interactive and Digital Media Institute > National University of Singapore > Email: ste...@nu... > Mobile: +65 84 28 64 24 > > > > > > > On Oct 3, 2012, at 9:51 PM, Norbert Schnell wrote: > >> Hi all, >> >> We just published an updated FTM External SDK that is compatible with FTM & Co 2.6 here: >> http://ftm.ircam.fr/index.php/SDK >> >> For those who already used the FTM External SDK 2.5, this is what really changed in this version: >> - the script "install-mxo.sh" in the "build" folder of the SDK >> - the "Header Search Paths" variable (HEADER_SEARCH_PATHS) in the Xcode build project >> - the "Other Linker Flags" variable (OTHER_LDFLAGS) in the Xcode build project >> >> Best, >> Norbert & Riccardo >> >> <message-footer.txt> > > FTM & Co > wiki: http://ftm.ircam.fr/ > mailing-list: http://listes.ircam.fr/wws/info/ftm > bug reports: mailto:ftm...@ir... |
|
From: Norbert S. <Nor...@ir...> - 2012-10-05 15:11:03
|
Wow, thanks a lot Stefano. We will integrate the quotes into the script in a new version of the SDK. On 05 Oct 2012, at 15:16, Stefano Fasciani wrote: > Hi All, > > I spend couple of days in trying to use the new 2.6 SDK and I have just succeeded in building and running the 3 example externals (coucou pack pingpong~), next week I will try to build my own ftm externals to verify wether the functionality it is still correct. > > I like the 2.6 SDK better than the 2.5 because I think it's easier to keep a clean an neat folder tree organization since everything is packed in the ftm.mxo (headers and lib) and the built .mxo just need to stay in the same folder of the ftm.mxo which is easy and it also make a lot of sense! (I had problem with 2.5 when I wanted to place the built .mxo in the folder I want, because of the linking with the FTMframework… etc… etc… ) In fact, we didn't change anything essential. Also the FTM framework had to be just next to the FTM externals just as now the ftm.mxo (in fact, we just packed the shared lib into an mxo bundle instead of a Mac OS X framework and added a Max class "ftm" to it). The rest on the ftm-devel mailing-list... Best Norbert |
|
From: Norbert S. <Nor...@ir...> - 2012-10-03 13:52:02
|
Hi all, We just published an updated FTM External SDK that is compatible with FTM & Co 2.6 here: http://ftm.ircam.fr/index.php/SDK For those who already used the FTM External SDK 2.5, this is what really changed in this version: - the script "install-mxo.sh" in the "build" folder of the SDK - the "Header Search Paths" variable (HEADER_SEARCH_PATHS) in the Xcode build project - the "Other Linker Flags" variable (OTHER_LDFLAGS) in the Xcode build project Best, Norbert & Riccardo |
|
From: Alexander D. <ale...@go...> - 2012-09-02 16:44:26
|
#include "ext.h"
#include "ext_obex.h"
#include "ftmlib.h"
typedef struct //object definition
{
t_object standart_header;
void *outlet0;
void *proxy1;
long proxy_inletnum;
} t_ftm_test;
//-------------------------------------------------------------------------------------prototypes
void *ftm_test_new();
void ftm_test_free(t_ftm_test *x);
void ftm_test_assist(t_ftm_test *x, void *b, long inlet_oder_outlet, long inlet_outlet_nummer, char *s);
void ftm_test(t_ftm_test *x, t_symbol *s, short argc, t_atom *argv);
//-----------------------------------------------------------------------------------------------
t_class *ftm_test_class;
int main()
{
t_class *c;
c = class_new("temp", (method)ftm_test_new, (method)ftm_test_free, sizeof(t_ftm_test), 0L, A_GIMME, 0);
class_addmethod(c, (method)ftm_test, ftm_str_obj, A_GIMME, 0); // method that catches ftm references pushed in any inlet
class_addmethod(c, (method)ftm_test_assist, "assist", A_CANT, 0);
class_register(CLASS_BOX, c);
ftm_test_class = c;
return 0;
}
void ftm_test(t_ftm_test *x, t_symbol *s, short argc, t_atom *argv)
{
post(" ");
post("ftm_test_fmat");
fmat_t* fmat = (fmat_t *)fts_get_object(argv); //fmat
fts_object_t *fts_obj = fts_get_object(argv); //fts_obj
//works----------------------------
fmat_lock_capacity(fmat, 50 * 50);
fmat_set_size_nogrow(fmat, 50, 50);
fmat_unlock(fmat);
post("round 1");
//---------------------------------
/*
does not really work
crashes if reference is pushed more than once in short intervalls in one of the inlets
or sometimes if I try to open the fmat after ftm_test() was evoked
*/
fts_array_t *ftm_array1;
fts_array_init(ftm_array1, 0, NULL);
fts_array_append_float(ftm_array1, 879.789897);
fmat_lock(fmat);
fts_send_message((fts_object_t *) fmat, fts_new_symbol("fill"), fts_array_get_size(ftm_array1),
fts_array_get_atoms(ftm_array1), fts_null);
fmat_unlock(fmat);
fts_array_destroy(ftm_array1);
post("round 2");
//--------------------------------
/*
does not really work
crashes if reference is pushed more than once in short intervalls in one of the inlets
or sometimes if I try to open the fmat after ftm_test() was evoked
*/
fts_array_t *ftm_array2; fts_array_init(ftm_array2, 0, NULL);
fmat_lock_capacity(fmat, 100 * 100);
fts_array_append_int(ftm_array2, 100);
fts_array_append_int(ftm_array2, 100);
fts_send_message((fts_object_t *) fmat, fts_new_symbol("size"), fts_array_get_size(ftm_array2),
fts_array_get_atoms(ftm_array2), fts_null);
fts_array_destroy(ftm_array2);
post("round 3");
//--------------------------------
}
void *ftm_test_new()
{
t_ftm_test *x;
x = (t_ftm_test *)object_alloc(ftm_test_class);
if(x)
{
x->proxy1 = proxy_new(x, 1, &x->proxy_inletnum);
x->outlet0 = outlet_new(x, NULL);
}
return(x);
}
void ftm_test_free(t_ftm_test *x)
{
object_free(x->proxy1);
}
void ftm_test_assist(t_ftm_test *x, void *b, long inlet_oder_outlet, long inlet_outlet_nummer, char *s)
{
if (inlet_oder_outlet == ASSIST_INLET)
{
switch (inlet_outlet_nummer)
{
case 0:sprintf(s,"Inlet %ld", inlet_outlet_nummer);break;
case 1:sprintf(s,"Inlet %ld", inlet_outlet_nummer);break;
}
}
else if (inlet_oder_outlet == ASSIST_OUTLET)
{
switch (inlet_outlet_nummer)
{
case 0:sprintf(s,"Outlet %ld", inlet_outlet_nummer);break;
}
}
}
|
|
From: Norbert S. <Nor...@ir...> - 2012-09-01 10:31:59
|
Hi Alexander,
On 31 Aug 2012, at 19:57, Alexander Droste wrote:
> thanks a lot for your interest and helping! What I'm thinking about is building a SQLite database where I can save
> the data of standard ftm objects and other things. For that I of course need to retrieve and send data to the objects.
There are a couple of standard methods to set and get "the data" of an FTM – actually FTS – object in FTM (see below).
> Thread safe pointer and locking... , that's something new for me. I'll have a closer look at that.
> Thanks for giving an example with set_size.
>
> About fts_send_message(): I tried to change the size of a fmat which reference is pushed in one of the
> the inlets what made max crash. Inbetween I gave some methods of the standard max6 api a try:
> "object_method_parse(obj, gensym("size"), "100 100", NULL);" or "object_method_long_array(...)" worked fine,
> getting the object with something like:
> ....
> object_obex_lookup(x, gensym("#P"), &patcher);
> for (box = jpatcher_get_firstobject(patcher); box; box = jbox_get_nextobject(box))
> {obj = jbox_get_object(box);}
> ....
In fact, FTS objects in FTM such as fmats inherit (C-style single inheritance) from fts_object_t.
They are not Max object and do not inherit from t_object.
Here you are sending a message to the ftm.object Max objects that creates the reference to an FTS object like an fmat.
But this is rather complicated...
If you really obtain a reference to an FTS object, fts_send_message() works.
Can you send the lines of codes for getting the reference of the incoming FTS object before the call of fts_send_message() that crashes?
> For me this is nicer than having to push the references with a patch chord into the external.
In what sense?
> The problem at the moment with this idea is that I can't receive any values.
> The pointer I get with "jbox_get_object(box)" seems to be different from the one I get with
> when a ftm object is pushed in an inlet. Functions like "fmat_get_m" don't work.
Of course, fmat_get_m() needs a reference to an fmat FTS object.
There is no standard way to get this from the and ftm.object external and I would not recommend this.
1. ---------------
If you like we can discuss a little bit how you want to access the objects like fmats by your object.
I guess, there are the following possibilities:
- sending them in a message to your external
- giving them as arguments (like $myfmat $yourfmat) of your external
- obtaining them from the current "FTM scope"
An FTM scope contains all FTM FTS object within a given abstraction or patcher with its sub-patches.
The API to access this is not documented, but we can provide your with examples.
2. ---------------
The second thing would be to see in which way "the data" of an FTM object is actually stored in an SQLite database.
A string?, a sequence of strings?, a list of atoms?
Internally to FTM the the data – or state – of an object is always stores as a sequence of messages that have to be send to an empty object of the same class to restore this the object's state.
This is handled by "FTM dumpers" and each FTM class implements a system method for dumping its current state as a sequence of (Max compatible) messages.
3. ---------------
The third thing to discuss is how to get "the data" from FTM FTS objects like fmat.
Here I see following possibilities:
- to implement an "FTM dumper" interfacing with SQLite (if possible)
- to add a pair of methods "get-blob" and "set-from-blob" to each FTM class you want to handle
fts_method_status_t
fmat_get_blob(fts_object_t *obj, void **ptr)
{
fmat_t *self = (fmat_t *)o;
float *ptr = fmat_lock(self); /* lock fmat and get pointer */
int m = fmat_get_m(self);
int n = fmat_get_n(self);
void *blob = fts_malloc(2 * sizeof(int) + sizeof(float) * m * n); /* will be freed by calling function */
int *int_ptr = (int *)blob;
/* fill blob with dimensions */
int_ptr[0] = m;
int_ptr[1] = n;
/* fill blob with data */
memcpy(int_ptr + 2, ptr, sizeof(float) * m * n);
fmat_unlock(self);
*ptr = blob;
}
fts_method_status_t
fmat_set_from_blob(fts_object_t *o, void *blob)
{
fmat_t *self = (fmat_t *)o;
int *int_ptr = (int *)blob;
int m = int_ptr[0];
int n = int_ptr[1];
float *ptr = fmat_lock_reshape(self, m, n);
memcpy(ptr, int_ptr + 2, sizeof(float) * m * n);
fmat_unlock(self);
}
Other classes are slightly more complicated...
Don't hesitate to further discuss this.
Cheers
Norbert
> Greetings,
> Alex
>
>
> Am 30.08.12 11:32, schrieb Diemo Schwarz:
>>
>> Dear Alexander,
>>
>> first of all, thanks for your interest in the ftm API. Can you give us a hint what you're working on?
>>
>> Then, topics like this of developing new externals with the API have a place at the ftm-devel mailing list on sourceforge, since the ftm list at ircam is mainly about using ftm in patches.
>>
>> Now to your question: the nogrow methods
>>
>> On 29.08.12 14:00, Alexander Droste wrote:
>>> Hey,
>>>
>>> after finding out that it is possible to get a reference in an external
>>> to ftm/fts-objects by using: "class_addmethod(c,
>>> (method)ftm_test_select,*ftm_str_obj*, A_GIMME, 0);"
>>
>> good to know. in all ftm externals, we use the ftmext API that takes care of that. it is defined and documented in ftmlib/ftmext.h, and realised for the Max5 and Max6 platform in ftmlib/max5/ftmexternals.h and ftmlib/max5/maxext.c
>>
>> Look at the code of any ftm external, e.g. ftm/externals/ftm.inter.c for fmat stuff.
>>
>>> I had trouble with the "nogrow" functions with fmat and mats.
>>>
>>> In detail:
>> [...]
>>> Is there any way get these nogrow functions working?
>>
>> Well, they do work exactly like they should: they change the fmat dimensions in the limit of the allocated memory, i.e. they can't grow beyond that, since that would require an exclusive lock on the fmat.
>>
>> How to do that can be found in _fmat_set_size:
>>
>> fmat_lock_capacity(self, m * n);
>> fmat_set_size_nogrow(self, m, n);
>> fmat_unlock(self);
>>
>>> Can someone show me a way how to work with fts_send_message() correctly?
>>> With what I'm doing the method execution sometimes works but crashes most
>>> of the time.
>>
>> what are you trying to do?
>>
>>> Can I define my own selector for a method that works with a fts_object_t?
>>
>> again, a little context would be helpful
>>
>> Best...
>> ...Diemo
>>
>>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> ftm-devel mailing list
> ftm...@li...
> https://lists.sourceforge.net/lists/listinfo/ftm-devel
|
|
From: Alexander D. <ale...@go...> - 2012-08-31 18:28:17
|
Hi Diemo,
thanks a lot for your interest and helping! What I'm thinking about is
building a SQLite database where I can save
the data of standard ftm objects and other things. For that I of course
need to retrieve and send data to the objects.
Thread safe pointer and locking... , that's something new for me. I'll
have a closer look at that.
Thanks for giving an example with set_size.
About fts_send_message(): I tried to change the size of a fmat which
reference is pushed in one of the
the inlets what made max crash. Inbetween I gave some methods of the
standard max6 api a try:
"object_method_parse(obj, gensym("size"), "100 100", NULL);" or
"object_method_long_array(...)" worked fine,
getting the object with something like:
....
object_obex_lookup(x, gensym("#P"), &patcher);
for (box = jpatcher_get_firstobject(patcher); box; box =
jbox_get_nextobject(box))
{obj = jbox_get_object(box);}
....
For me this is nicer than having to push the references with a patch
chord into the external.
The problem at the moment with this idea is that I can't receive any values.
The pointer I get with "jbox_get_object(box)" seems to be different from
the one I get with
when a ftm object is pushed in an inlet. Functions like "fmat_get_m"
don't work.
If not by a pointer which I can use with the ftm api, it would be great
if I could get
return values of methods like sending "object_method_parse(obj,
gensym("rows",...)"
an then getting the number of rows.
Greetings,
Alex
Am 30.08.12 11:32, schrieb Diemo Schwarz:
>
> Dear Alexander,
>
> first of all, thanks for your interest in the ftm API. Can you give
> us a hint what you're working on?
>
> Then, topics like this of developing new externals with the API have a
> place at the ftm-devel mailing list on sourceforge, since the ftm list
> at ircam is mainly about using ftm in patches.
>
> Now to your question: the nogrow methods
>
> On 29.08.12 14:00, Alexander Droste wrote:
>> Hey,
>>
>> after finding out that it is possible to get a reference in an external
>> to ftm/fts-objects by using: "class_addmethod(c,
>> (method)ftm_test_select,*ftm_str_obj*, A_GIMME, 0);"
>
> good to know. in all ftm externals, we use the ftmext API that takes
> care of that. it is defined and documented in ftmlib/ftmext.h, and
> realised for the Max5 and Max6 platform in ftmlib/max5/ftmexternals.h
> and ftmlib/max5/maxext.c
>
> Look at the code of any ftm external, e.g. ftm/externals/ftm.inter.c
> for fmat stuff.
>
>> I had trouble with the "nogrow" functions with fmat and mats.
>>
>> In detail:
> [...]
>> Is there any way get these nogrow functions working?
>
> Well, they do work exactly like they should: they change the fmat
> dimensions in the limit of the allocated memory, i.e. they can't grow
> beyond that, since that would require an exclusive lock on the fmat.
>
> How to do that can be found in _fmat_set_size:
>
> fmat_lock_capacity(self, m * n);
> fmat_set_size_nogrow(self, m, n);
> fmat_unlock(self);
>
>> Can someone show me a way how to work with fts_send_message()
>> correctly?
>> With what I'm doing the method execution sometimes works but
>> crashes most
>> of the time.
>
> what are you trying to do?
>
>> Can I define my own selector for a method that works with a
>> fts_object_t?
>
> again, a little context would be helpful
>
> Best...
> ...Diemo
>
>
|
|
From: Alexander D. <ale...@go...> - 2012-08-31 17:57:43
|
Hi Diemo,
thanks a lot for your interest and helping! What I'm thinking about is
building a SQLite database where I can save
the data of standard ftm objects and other things. For that I of course
need to retrieve and send data to the objects.
Thread safe pointer and locking... , that's something new for me. I'll
have a closer look at that.
Thanks for giving an example with set_size.
About fts_send_message(): I tried to change the size of a fmat which
reference is pushed in one of the
the inlets what made max crash. Inbetween I gave some methods of the
standard max6 api a try:
"object_method_parse(obj, gensym("size"), "100 100", NULL);" or
"object_method_long_array(...)" worked fine,
getting the object with something like:
....
object_obex_lookup(x, gensym("#P"), &patcher);
for (box = jpatcher_get_firstobject(patcher); box; box =
jbox_get_nextobject(box))
{obj = jbox_get_object(box);}
....
For me this is nicer than having to push the references with a patch
chord into the external.
The problem at the moment with this idea is that I can't receive any values.
The pointer I get with "jbox_get_object(box)" seems to be different from
the one I get with
when a ftm object is pushed in an inlet. Functions like "fmat_get_m"
don't work.
If not by a pointer which I can use with the ftm api, it would be great
if I could get
return values of methods like sending "object_method_parse(obj,
gensym("rows",...)"
an then getting the number of rows.
Greetings,
Alex
Am 30.08.12 11:32, schrieb Diemo Schwarz:
>
> Dear Alexander,
>
> first of all, thanks for your interest in the ftm API. Can you give
> us a hint what you're working on?
>
> Then, topics like this of developing new externals with the API have a
> place at the ftm-devel mailing list on sourceforge, since the ftm list
> at ircam is mainly about using ftm in patches.
>
> Now to your question: the nogrow methods
>
> On 29.08.12 14:00, Alexander Droste wrote:
>> Hey,
>>
>> after finding out that it is possible to get a reference in an external
>> to ftm/fts-objects by using: "class_addmethod(c,
>> (method)ftm_test_select,*ftm_str_obj*, A_GIMME, 0);"
>
> good to know. in all ftm externals, we use the ftmext API that takes
> care of that. it is defined and documented in ftmlib/ftmext.h, and
> realised for the Max5 and Max6 platform in ftmlib/max5/ftmexternals.h
> and ftmlib/max5/maxext.c
>
> Look at the code of any ftm external, e.g. ftm/externals/ftm.inter.c
> for fmat stuff.
>
>> I had trouble with the "nogrow" functions with fmat and mats.
>>
>> In detail:
> [...]
>> Is there any way get these nogrow functions working?
>
> Well, they do work exactly like they should: they change the fmat
> dimensions in the limit of the allocated memory, i.e. they can't grow
> beyond that, since that would require an exclusive lock on the fmat.
>
> How to do that can be found in _fmat_set_size:
>
> fmat_lock_capacity(self, m * n);
> fmat_set_size_nogrow(self, m, n);
> fmat_unlock(self);
>
>> Can someone show me a way how to work with fts_send_message()
>> correctly?
>> With what I'm doing the method execution sometimes works but
>> crashes most
>> of the time.
>
> what are you trying to do?
>
>> Can I define my own selector for a method that works with a
>> fts_object_t?
>
> again, a little context would be helpful
>
> Best...
> ...Diemo
>
>
|
|
From: Diemo S. <Die...@ir...> - 2012-08-30 09:53:18
|
Dear Alexander,
first of all, thanks for your interest in the ftm API. Can you give us a hint
what you're working on?
Then, topics like this of developing new externals with the API have a place at
the ftm-devel mailing list on sourceforge, since the ftm list at ircam is mainly
about using ftm in patches.
Now to your question: the nogrow methods
On 29.08.12 14:00, Alexander Droste wrote:
> Hey,
>
> after finding out that it is possible to get a reference in an external
> to ftm/fts-objects by using: "class_addmethod(c,
> (method)ftm_test_select,*ftm_str_obj*, A_GIMME, 0);"
good to know. in all ftm externals, we use the ftmext API that takes care of
that. it is defined and documented in ftmlib/ftmext.h, and realised for the
Max5 and Max6 platform in ftmlib/max5/ftmexternals.h and ftmlib/max5/maxext.c
Look at the code of any ftm external, e.g. ftm/externals/ftm.inter.c for fmat stuff.
> I had trouble with the "nogrow" functions with fmat and mats.
>
> In detail:
[...]
> Is there any way get these nogrow functions working?
Well, they do work exactly like they should: they change the fmat dimensions in
the limit of the allocated memory, i.e. they can't grow beyond that, since that
would require an exclusive lock on the fmat.
How to do that can be found in _fmat_set_size:
fmat_lock_capacity(self, m * n);
fmat_set_size_nogrow(self, m, n);
fmat_unlock(self);
> Can someone show me a way how to work with fts_send_message() correctly?
> With what I'm doing the method execution sometimes works but crashes most
> of the time.
what are you trying to do?
> Can I define my own selector for a method that works with a fts_object_t?
again, a little context would be helpful
Best...
...Diemo
--
Diemo Schwarz, PhD -- http://diemo.concatenative.net
Real-Time Music Interaction Team -- http://imtr.ircam.fr
IRCAM - Centre Pompidou -- 1, place Igor-Stravinsky, 75004 Paris, France
Phone +33-1-4478-4879 -- Fax +33-1-4478-1540
|
|
From: Thomas G. <gr...@gr...> - 2011-11-15 10:24:32
|
Hi all,
new crash scenario with gesturefollower being very busy following many
parallel gestures and ftm crashing in the meantime (thread 21 in crash
log below)
gr~~~
--
Process: MaxMSP [97777]
Path: /Applications/Max5/MaxMSP.app/Contents/MacOS/MaxMSP
Identifier: com.cycling74.MaxMSP
Version: 5.1.9 (48561) (5.1.9)
Code Type: X86 (Native)
Parent Process: launchd [493]
Interval Since Last Report: 158295 sec
Crashes Since Last Report: 6
Per-App Interval Since Last Report: 88012 sec
Per-App Crashes Since Last Report: 2
Date/Time: 2011-11-14 23:15:24.666 +0100
OS Version: Mac OS X 10.5.8 (9L30)
Report Version: 6
Anonymous UUID: 8DD41373-8F9B-4724-8B0C-84AF66AA2344
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 21
Thread 0:
0 libSystem.B.dylib 0x979103e7 floorl$fenv_access_off +
55
1 gf 0x19c8358f
GFlibUtility::Mahalanobis(float*, float*, int, float*, float) + 141
2 gf 0x19c8622d
Phrase::calculateDistances(float*) + 103
3 gf 0x19c81bba GF::decoding(float*,
Phrase*) + 272
4 gf 0x19c83209 GF::observation(float*,
int) + 1011
5 gf 0x19c6eaf4
GFmax::receiveObservation(int) + 122
6 gf 0x19c79198 list(GFmubu*, symbol*,
short, atom*) + 350
7 com.cycling74.MaxMSP 0x0006463d outlet_list + 711
8 com.cycling74.MaxMSP 0x0006463d outlet_list + 711
9 com.cycling74.MaxMSP 0x0004f7f5
through_scheduler_senditfun(through*, _sendargs*) + 59
10 com.cycling74.MaxMSP 0x0004f881 through_scheduler_sendit
+ 79
11 com.cycling74.MaxMSP 0x000497b2 send_list(send*,
symbol*, short, atom*) + 64
12 com.cycling74.MaxMSP 0x0006463d outlet_list + 711
13 com.cycling74.MaxMSP 0x0005156f trigger_iterate(unpack*,
long, double, symbol*, symbol*, short, atom*, short) + 339
14 com.cycling74.MaxMSP 0x0005174a trigger_list(unpack*,
symbol*, short, atom*) + 160
15 com.cycling74.MaxMSP 0x0006463d outlet_list + 711
16 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
17 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
18 com.cycling74.MaxMSP 0x0006463d outlet_list + 711
19 com.cycling74.MaxAPI 0x00f063e4 outlet_list + 60
20 FTMlib 0x11193ae2 ftmext_outlet_varargs + 98
21 ftm.list 0x0f7bcdf1 ftmlist_obj + 161
22 ftm.list 0x0f7bdd14 _list_inlet_object + 148
23 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
24 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
25 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
26 FTMlib 0x1119103e ftmext_outlet_object + 126
27 ftm.mess 0x1013f258 expression_callback + 424
28 FTMlib 0x11214a54 expression_eval_aux + 1572
29 ftm.mess 0x1013fbd8 ftmmess_inlet + 2280
30 ftm.mess 0x1013ffe8 _ftmmess_inlet_list + 72
31 com.cycling74.MaxMSP 0x0006463d outlet_list + 711
32 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
33 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
34 com.cycling74.MaxMSP 0x0006463d outlet_list + 711
35 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
36 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
37 com.cycling74.MaxMSP 0x0006463d outlet_list + 711
38 com.cycling74.MaxAPI 0x00f063e4 outlet_list + 60
39 FTMlib 0x11193ae2 ftmext_outlet_varargs + 98
40 ftm.mess 0x1013f1c8 expression_callback + 280
41 FTMlib 0x11214a54 expression_eval_aux + 1572
42 ftm.mess 0x1013fbd8 ftmmess_inlet + 2280
43 ftm.mess 0x101404f4 _ftmmess_inlet_object +
148
44 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
45 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
46 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
47 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
48 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
49 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
50 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
51 FTMlib 0x1119103e ftmext_outlet_object + 126
52 ftm.mess 0x1013f258 expression_callback + 424
53 FTMlib 0x11214a54 expression_eval_aux + 1572
54 ftm.mess 0x1013fbd8 ftmmess_inlet + 2280
55 ftm.mess 0x101404f4 _ftmmess_inlet_object +
148
56 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
57 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
58 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
59 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
60 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
61 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
62 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
63 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
64 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
65 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
66 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
67 FTMlib 0x1119103e ftmext_outlet_object + 126
68 ftm.mess 0x1013f258 expression_callback + 424
69 FTMlib 0x11214a54 expression_eval_aux + 1572
70 ftm.mess 0x1013fbd8 ftmmess_inlet + 2280
71 ftm.mess 0x101404f4 _ftmmess_inlet_object +
148
72 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
73 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
74 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
75 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
76 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
77 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
78 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
79 FTMlib 0x1119103e ftmext_outlet_object + 126
80 ftm.clone 0x10367ff7 clone_inlet + 391
81 ftm.clone 0x10368994 _clone_inlet_object + 148
82 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
83 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
84 com.cycling74.MaxMSP 0x00051592 trigger_iterate(unpack*,
long, double, symbol*, symbol*, short, atom*, short) + 374
85 com.cycling74.MaxMSP 0x000516a7
trigger_anything(unpack*, symbol*, short, atom*) + 75
86 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
87 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
88 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
89 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
90 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
91 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
92 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
93 FTMlib 0x1119103e ftmext_outlet_object + 126
94 ftm.mess 0x1013f258 expression_callback + 424
95 FTMlib 0x11214a54 expression_eval_aux + 1572
96 ftm.mess 0x1013fbd8 ftmmess_inlet + 2280
97 ftm.mess 0x101404f4 _ftmmess_inlet_object +
148
98 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
99 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
100 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
101 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
102 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
103 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
104 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
105 FTMlib 0x1119103e ftmext_outlet_object + 126
106 gbr.bands 0x1659d762 bands_inlet + 1330
107 gbr.bands 0x1659e304 _bands_inlet_object + 148
108 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
109 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
110 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
111 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
112 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
113 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
114 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
115 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
116 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
117 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
118 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
119 FTMlib 0x1119103e ftmext_outlet_object + 126
120 ftm.mess 0x1013f258 expression_callback + 424
121 FTMlib 0x11214a54 expression_eval_aux + 1572
122 ftm.mess 0x1013fbd8 ftmmess_inlet + 2280
123 ftm.mess 0x101404f4 _ftmmess_inlet_object +
148
124 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
125 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
126 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
127 FTMlib 0x1119103e ftmext_outlet_object + 126
128 gbr.fft 0x165897db fft_inlet + 651
129 gbr.fft 0x1658a264 _fft_inlet_object + 148
130 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
131 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
132 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
133 FTMlib 0x1119103e ftmext_outlet_object + 126
134 gbr.wind= 0x14cc7e6a window_inlet + 938
135 gbr.wind= 0x14ccb4f4 _window_inlet_object + 148
136 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
137 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
138 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
139 FTMlib 0x1119103e ftmext_outlet_object + 126
140 ftm.copy 0x0f2db169 copy_inlet + 1561
141 ftm.copy 0x0f2dbaa4 _copy_inlet_object + 148
142 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
143 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
144 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
145 FTMlib 0x1119103e ftmext_outlet_object + 126
146 ftm.mess 0x1013f258 expression_callback + 424
147 FTMlib 0x11214a54 expression_eval_aux + 1572
148 ftm.mess 0x1013fbd8 ftmmess_inlet + 2280
149 ftm.mess 0x101404f4 _ftmmess_inlet_object +
148
150 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
151 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
152 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
153 com.cycling74.MaxMSP 0x0001cb79 typedmess + 83
154 com.cycling74.MaxMSP 0x0001c648 typedmess_fun + 782
155 com.cycling74.MaxMSP 0x000642b9 outlet_anything + 795
156 com.cycling74.MaxAPI 0x00f06441 outlet_anything + 60
157 FTMlib 0x1119103e ftmext_outlet_object + 126
158 gbr.slice~ 0x14ce0199 slice_callback + 137
159 FTMlib 0x1120200e fts_timebase_advance + 110
160 gbr.dct 0x14aee713 gabor_scheduler_callback
+ 67
161 com.cycling74.MaxMSP 0x0002ac91 sched_takepoll + 483
162 com.cycling74.MaxMSP 0x0002ad46 sched_poll + 50
163 com.cycling74.MaxMSP 0x00012466 max_tick + 112
164 com.cycling74.MaxMSP 0x001e4bee
maxapplication_eventtimerproc(__EventLoopTimer*, void*) + 22
165 com.apple.CoreFoundation 0x976c98f5 CFRunLoopRunSpecific +
4469
166 com.apple.CoreFoundation 0x976c9aa8 CFRunLoopRunInMode + 88
167 com.apple.HIToolbox 0x955d72ac
RunCurrentEventLoopInMode + 283
168 com.apple.HIToolbox 0x955d6ffe ReceiveNextEventCommon +
175
169 com.apple.HIToolbox 0x9571a377 ReceiveNextEvent + 58
170 com.cycling74.MaxMSP 0x002d375a
juce::juce_dispatchNextMessageOnSystemQueue(bool, bool) + 554
171 com.cycling74.MaxMSP 0x002dd3df
juce::MessageManager::dispatchNextMessage(bool, bool*, bool) + 79
172 com.cycling74.MaxMSP 0x002dd49e
juce::MessageManager::runDispatchLoop() + 42
173 com.cycling74.MaxMSP 0x002dbdf9
juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 605
174 com.cycling74.MaxMSP 0x002dbed3
juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 125
175 com.cycling74.MaxMSP 0x001e5032 main + 76
176 com.cycling74.MaxMSP 0x000059fe _start + 216
177 com.cycling74.MaxMSP 0x00005925 start + 41
Thread 1:
0 libSystem.B.dylib 0x978ef1c6
semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x979211af _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x97922a33
pthread_cond_timedwait_relative_np + 47
3 ...ple.CoreServices.CarbonCore 0x96677c62
TSWaitOnConditionTimedRelative + 246
4 ...ple.CoreServices.CarbonCore 0x96677a42 TSWaitOnSemaphoreCommon
+ 422
5 ...ple.CoreServices.CarbonCore 0x966a8944 TimerThread + 74
6 libSystem.B.dylib 0x97920055 _pthread_start + 321
7 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x9791f8c6 kevent + 10
1 libSystem.B.dylib 0x97920055 _pthread_start + 321
2 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x9791f8c6 kevent + 10
1 libSystem.B.dylib 0x97920055 _pthread_start + 321
2 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x9791f8c6 kevent + 10
1 libSystem.B.dylib 0x97920055 _pthread_start + 321
2 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 5:
0 libSystem.B.dylib 0x978ef166 mach_msg_trap + 10
1 libSystem.B.dylib 0x978f695c mach_msg + 72
2 com.apple.CoreFoundation 0x976c8e7e CFRunLoopRunSpecific +
1790
3 com.apple.CoreFoundation 0x976c9aa8 CFRunLoopRunInMode + 88
4 com.apple.audio.CoreAudio 0x969465f8
HALRunLoop::OwnThread(void*) + 160
5 com.apple.audio.CoreAudio 0x96946480
CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x97920055 _pthread_start + 321
7 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 6:
0 libSystem.B.dylib 0x9791f8c6 kevent + 10
1 libSystem.B.dylib 0x97920055 _pthread_start + 321
2 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 7:
0 libSystem.B.dylib 0x978ef166 mach_msg_trap + 10
1 libSystem.B.dylib 0x978f695c mach_msg + 72
2 com.apple.audio.midi.CoreMIDI 0x0f11ef0f
XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
3 com.apple.audio.midi.CoreMIDI 0x0f111477 MIDIInPortThread::Run()
+ 111
4 com.apple.audio.midi.CoreMIDI 0x0f11507d
XThread::RunHelper(void*) + 17
5 com.apple.audio.midi.CoreMIDI 0x0f11f9ee
CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x97920055 _pthread_start + 321
7 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 8:
0 libSystem.B.dylib 0x978ef1c6
semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x979211af _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x97922a33
pthread_cond_timedwait_relative_np + 47
3 com.cycling74.MaxMSP 0x002d2bb0
juce::WaitableEvent::wait(int) const + 122
4 com.cycling74.MaxMSP 0x0034fc2f juce::Thread::wait(int)
const + 27
5 com.cycling74.MaxMSP 0x002de44b
juce::InternalTimerThread::run() + 229
6 com.cycling74.MaxMSP 0x0034fcc2
juce::Thread::threadEntryPoint(juce::Thread*) + 142
7 com.cycling74.MaxMSP 0x002d2c8b
juce::threadEntryProc(void*) + 17
8 libSystem.B.dylib 0x97920055 _pthread_start + 321
9 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 9:
0 libSystem.B.dylib 0x9794dc0e accept$NOCANCEL$UNIX2003
+ 10
1 com.cycling74.MaxMSP 0x00394179
juce::StreamingSocket::waitForNextConnection() const + 257
2 com.cycling74.MaxMSP 0x00216dc9
tcpconnection_listenthread(_tcpconnection*) + 27
3 com.cycling74.MaxMSP 0x00065ce8
systhread_threadproc(void*) + 60
4 libSystem.B.dylib 0x97920055 _pthread_start + 321
5 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 10:
0 libSystem.B.dylib 0x9791f8c6 kevent + 10
1 libSystem.B.dylib 0x97920055 _pthread_start + 321
2 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 11:
0 libSystem.B.dylib 0x978ef1c6
semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x979211af _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x9796b9bb pthread_cond_timedwait +
47
3 imubu 0x13ad2476
juce::WaitableEventImpl::wait(int) + 180
4 imubu 0x13ac1f30
juce::WaitableEvent::wait(int) const + 26
5 imubu 0x13aea42d juce::Thread::wait(int)
const + 27
6 imubu 0x139dab72
juce::InternalTimerThread::run() + 282
7 imubu 0x13aea657
juce::Thread::threadEntryPoint() + 93
8 imubu 0x13acce08
juce::threadEntryProc(void*) + 40
9 libSystem.B.dylib 0x97920055 _pthread_start + 321
10 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 12:
0 libSystem.B.dylib 0x978ef166 mach_msg_trap + 10
1 libSystem.B.dylib 0x978f695c mach_msg + 72
2 com.apple.CoreFoundation 0x976c8e7e CFRunLoopRunSpecific +
1790
3 com.apple.CoreFoundation 0x976c9b04 CFRunLoopRun + 84
4 com.apple.DesktopServices 0x94967d0f
TSystemNotificationTask::SystemNotificationTaskProc(void*) + 123
5 ...ple.CoreServices.CarbonCore 0x96696fbb PrivateMPEntryPoint + 56
6 libSystem.B.dylib 0x97920055 _pthread_start + 321
7 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 13:
0 libSystem.B.dylib 0x978ef166 mach_msg_trap + 10
1 libSystem.B.dylib 0x978f695c mach_msg + 72
2 com.apple.CoreFoundation 0x976c8e7e CFRunLoopRunSpecific +
1790
3 com.apple.CoreFoundation 0x976c9b04 CFRunLoopRun + 84
4 com.apple.DesktopServices 0x94967e88
TFSEventsNotificationTask::FSEventsNotificationTaskProc(void*) + 216
5 ...ple.CoreServices.CarbonCore 0x96696fbb PrivateMPEntryPoint + 56
6 libSystem.B.dylib 0x97920055 _pthread_start + 321
7 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 14:
0 libSystem.B.dylib 0x978f634e __semwait_signal + 10
1 libSystem.B.dylib 0x97920ccd pthread_cond_wait
$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96698de3 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96677c36
TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96698a60 MPWaitOnQueue + 208
5 com.apple.DesktopServices 0x94972e6a
TNodeSyncTask::SyncTaskProc(void*) + 84
6 ...ple.CoreServices.CarbonCore 0x96696fbb PrivateMPEntryPoint + 56
7 libSystem.B.dylib 0x97920055 _pthread_start + 321
8 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 15:
0 libSystem.B.dylib 0x978ef1c6
semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x979211af _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x97922a33
pthread_cond_timedwait_relative_np + 47
3 ...ple.CoreServices.CarbonCore 0x96677c62
TSWaitOnConditionTimedRelative + 246
4 ...ple.CoreServices.CarbonCore 0x96698a60 MPWaitOnQueue + 208
5 com.apple.DesktopServices 0x94974db4
TFolderSizeTask::FolderSizeTaskProc(void*) + 104
6 ...ple.CoreServices.CarbonCore 0x96696fbb PrivateMPEntryPoint + 56
7 libSystem.B.dylib 0x97920055 _pthread_start + 321
8 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 16:
0 libSystem.B.dylib 0x9791f8c6 kevent + 10
1 libSystem.B.dylib 0x97920055 _pthread_start + 321
2 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 17:
0 libSystem.B.dylib 0x9793e60a select$DARWIN_EXTSN + 10
1 libSystem.B.dylib 0x97920055 _pthread_start + 321
2 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 18:
0 libSystem.B.dylib 0x978ef1c6
semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x979211af _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x97922a33
pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x969f7dbc -[NSCondition
waitUntilDate:] + 236
4 com.apple.Foundation 0x969f7bd0 -[NSConditionLock
lockWhenCondition:beforeDate:] + 144
5 com.apple.Foundation 0x969f7b35 -[NSConditionLock
lockWhenCondition:] + 69
6 com.apple.AppKit 0x940266e8 -[NSUIHeartBeat
_heartBeatThread:] + 753
7 com.apple.Foundation 0x969b1dfd -[NSThread main] + 45
8 com.apple.Foundation 0x969b19a4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x97920055 _pthread_start + 321
10 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 19:
0 libSystem.B.dylib 0x978ef1c6
semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x979211af _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x97922a33
pthread_cond_timedwait_relative_np + 47
3 ...ple.CoreServices.CarbonCore 0x96677c62
TSWaitOnConditionTimedRelative + 246
4 ...ple.CoreServices.CarbonCore 0x96677a42 TSWaitOnSemaphoreCommon
+ 422
5 ...ickTimeComponents.component 0x909abc8e
ReadSchedulerThreadEntryPoint + 4728
6 libSystem.B.dylib 0x97920055 _pthread_start + 321
7 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 20:
0 libSystem.B.dylib 0x978ef166 mach_msg_trap + 10
1 libSystem.B.dylib 0x978f695c mach_msg + 72
2 com.apple.CoreFoundation 0x976c8e7e CFRunLoopRunSpecific +
1790
3 com.apple.CoreFoundation 0x976c9b04 CFRunLoopRun + 84
4 com.apple.DVCPROHDMuxer 0x02ec50fb
AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 297
5 libSystem.B.dylib 0x97920055 _pthread_start + 321
6 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 21 Crashed:
0 libSystem.B.dylib 0xffff0680 __bzero + 128
(cpu_capabilities.h:244)
1 FTMlib 0x111a4fdd fm_grow_locked + 173
2 FTMlib 0x111bae2f fmat_lock_reshape + 47
3 gbr.slice~ 0x14cdfcc7 _slice_perform + 1079
4 com.cycling74.MaxAudioAPI 0x0e1442ec dspchain_tick + 90
5 com.cycling74.MaxAudioAPI 0x0e142d1c ad_process + 470
6 com.cycling74.ad_coreaudio 0x0e203e2a coreaudio_ioproc + 378
7 com.apple.audio.CoreAudio 0x96958177
HP_IOProc::Call(AudioTimeStamp const&, AudioTimeStamp const&,
AudioBufferList const*, AudioTimeStamp const&, AudioBufferList*) + 319
8 com.apple.audio.CoreAudio 0x96957e68
IOA_Device::CallIOProcs(AudioTimeStamp const&, AudioTimeStamp const&,
AudioTimeStamp const&) + 274
9 com.apple.audio.CoreAudio 0x96957d44
HP_IOThread::PerformIO(AudioTimeStamp const&) + 1246
10 com.apple.audio.CoreAudio 0x9695611f HP_IOThread::WorkLoop()
+ 1239
11 com.apple.audio.CoreAudio 0x96955c43
HP_IOThread::ThreadEntry(HP_IOThread*) + 17
12 com.apple.audio.CoreAudio 0x96946480
CAPThread::Entry(CAPThread*) + 96
13 libSystem.B.dylib 0x97920055 _pthread_start + 321
14 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 22:
0 libSystem.B.dylib 0x978ef1c6
semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x979211af _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x97922a33
pthread_cond_timedwait_relative_np + 47
3 com.apple.audio.CoreAudio 0x96955bdf
CAGuard::WaitFor(unsigned long long) + 213
4 com.apple.audio.CoreAudio 0x9695779a
CAGuard::WaitUntil(unsigned long long) + 70
5 com.apple.audio.CoreAudio 0x96955f3f HP_IOThread::WorkLoop()
+ 759
6 com.apple.audio.CoreAudio 0x96955c43
HP_IOThread::ThreadEntry(HP_IOThread*) + 17
7 com.apple.audio.CoreAudio 0x96946480
CAPThread::Entry(CAPThread*) + 96
8 libSystem.B.dylib 0x97920055 _pthread_start + 321
9 libSystem.B.dylib 0x9791ff12 thread_start + 34
Thread 21 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x111a4f4e ecx: 0xfffff800 edx: 0x00000000
edi: 0x00000800 esi: 0x00000200 ebp: 0xb0b6c8b8 esp: 0xb0b6c8b4
ss: 0x0000001f efl: 0x00010287 eip: 0xffff0680 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x00000000
Binary Images:
0x1000 - 0x46afe7 +com.cycling74.MaxMSP 5.1.9 (48561) (5.1.9)
<3e16709a1a354051a0d76a5783941b82> /Applications/Max5/MaxMSP.app/
Contents/MacOS/MaxMSP
0x9a3000 - 0x9a7ffd com.apple.JavaVM 12.9.0 (12.9.0)
<ddf63af73eedc15915184c97c95a9dcf> /System/Library/Frameworks/
JavaVM.framework/Versions/A/JavaVM
0x9b0000 - 0x9b4ffd JavaLaunching ??? (???)
<41aa04fadb9589ab9c249284090b2ef7> /System/Library/PrivateFrameworks/
JavaLaunching.framework/Versions/A/JavaLaunching
0xc83000 - 0xce8fcf +[Unknown Bundle] ??? (???)
<dcc5a8f36c5e4e558132c47774090311> [Unknown Bundle]
0xd82000 - 0xd83ff7 +com.cycling74.fseventwatcher 5.1.9 (48561)
(48561) <47991b3dabaf58e1e7746831345d0dd9> /Applications/Max5/Cycling
'74/extensions/fseventwatcher.mxo/Contents/MacOS/fseventwatcher
0xe04000 - 0xe05ff7 +ftm.print ??? (???)
<10f23e6eefdc596513368d64f456a5cc> /Applications/Max5/Cycling '74/ftm-
and-co/externals/ftm.print.mxo/Contents/MacOS/ftm.print
0xf04000 - 0xf2aff7 +com.cycling74.MaxAPI 1.0 (1.0)
<33a72113efe52e1f4c58f3e2bfa19108> /Applications/Max5/MaxMSP.app/
Contents/Frameworks/MaxAPI.framework/MaxAPI
0xff8000 - 0xff9ff7 +com.cycling74.bach.collector 5.1.7 (5.1.7)
<94b5a0508a4b7e04ba00f65e88e942d7> /Applications/Max5/Cycling '74/
extensions/bach.collector.mxo/Contents/MacOS/bach.collector
0x2e2d000 - 0x2e83fd6 com.apple.DVCPROHDAudio 1.3 (1.3) /Library/
Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio
0x2eb3000 - 0x2efdfec com.apple.DVCPROHDMuxer 1.3 (1.3) /Library/
QuickTime/DVCPROHDMuxer.component/Contents/MacOS/DVCPROHDMuxer
0xd05d000 - 0xd062ff7 +com.cycling74.autohelp 5.1.9 (48561) (48561)
<74c3e7d3f940e9e5894fa557f6b70f25> /Applications/Max5/Cycling '74/
extensions/autohelp.mxo/Contents/MacOS/autohelp
0xd109000 - 0xd10dff7 +com.cycling74.fpic 5.1.9 (48561) (48561)
<906d6d501891b3c4616252516af39626> /Applications/Max5/Cycling '74/max-
externals/fpic.mxo/Contents/MacOS/fpic
0xdf4a000 - 0xdfcfff7 +com.bachproject.bachAPI 1.0 (1)
<81d06e0cd01c50c47aabc168e3d16aba> /Library/Frameworks/
bachAPI.framework/Versions/A/bachAPI
0xdff5000 - 0xdff7ff7 +com.cycling74.bach.lexpr 5.1.7 (5.1.7)
<708242bda407903eaca45f864330ed5e> /Applications/Max5/Cycling '74/
extensions/bach.lexpr.mxo/Contents/MacOS/bach.lexpr
0xdffb000 - 0xdffcffb +org.jamoma.jcom.loader 0.5.1 (0.5.1)
<fdf0fd2bf6a6a43ef75104a12ab2808a> /Applications/Max5/Cycling '74/
extensions/jcom.loader.mxo/Contents/MacOS/jcom.loader
0xe100000 - 0xe102ff7 +com.cycling74.bach.llll 5.1.7 (5.1.7)
<69552df88396f17c8e932a2161172b9d> /Applications/Max5/Cycling '74/
extensions/bach.llll.mxo/Contents/MacOS/bach.llll
0xe10b000 - 0xe10cff7 +com.cycling74.debugwindow 5.1.9 (48561)
(48561) <e943e78c478f3cf08496d3fcbada608e> /Applications/Max5/Cycling
'74/extensions/debugwindow.mxo/Contents/MacOS/debugwindow
0xe111000 - 0xe129ffb +org.jamoma.JamomaDSP 0.6 ($Rev$) ($Rev$)
<e84ae6b03c8affecd1f8c9825f72a51c> /Library/Frameworks/
JamomaDSP.framework/Versions/A/JamomaDSP
0xe13a000 - 0xe154ff7 +com.cycling74.MaxAudioAPI ??? (1.0)
<fc68e49f0385ff8a1aa9625513e8aaf0> /Applications/Max5/MaxMSP.app/
Contents/Frameworks/MaxAudioAPI.framework/Versions/A/MaxAudioAPI
0xe16e000 - 0xe18bfff +org.jamoma.JamomaFoundation 0.6 ($Rev$) ($Rev
$) <23e67b4700bbd19fd2227fb82fa79b8b> /Library/Frameworks/
JamomaFoundation.framework/Versions/A/JamomaFoundation
0xe19b000 - 0xe1b3fff +org.jamoma.JamomaAudioGraph 0.1.2 ($Rev$)
($Rev$) <ae2c844ec1eb04c5f2935ef4f9fc495e> /Library/Frameworks/
JamomaAudioGraph.framework/Versions/A/JamomaAudioGraph
0xe1bc000 - 0xe1ccfff +org.jamoma.JamomaModular 0.5.1 (dbca6)
(dbca6) <a6276c2db0d0fc3d4e21514014fa9567> /Library/Frameworks/
JamomaModular.framework/Versions/A/JamomaModular
0xe1dd000 - 0xe1f5fff +org.jamoma.JamomaGraph 0.1.2 ($Rev$) ($Rev$)
<a5f74f355620ccb4b9220c1b793fcba4> /Library/Frameworks/
JamomaGraph.framework/Versions/A/JamomaGraph
0xe1fd000 - 0xe1fdffd libmx.A.dylib ??? (???) /usr/lib/libmx.A.dylib
0xe202000 - 0xe209ff7 +com.cycling74.ad_coreaudio 5.1.9 (48561)
(48561) <4e110f8f0bb3cdd5fe7ee4f96d334eae> /Applications/Max5/Cycling
'74/ad/ad_coreaudio.mxo/Contents/MacOS/ad_coreaudio
0xe20f000 - 0xe210ffb +com.cycling74.ad_nonreal 5.1.9 (48561)
(48561) <b610e9183f6ea2314eb18264af345fa7> /Applications/Max5/Cycling
'74/ad/ad_nonreal.mxo/Contents/MacOS/ad_nonreal
0xe214000 - 0xe21cff7 +com.cycling74.ad_rewire 5.1.9 (48561)
(48561) <b9d273de5aa9e2e6a90f49cec039dc72> /Applications/Max5/Cycling
'74/ad/ad_rewire.mxo/Contents/MacOS/ad_rewire
0xe224000 - 0xe254ff7 +com.cycling74.live.guilib 5.1.9 (48561)
(48561) <0c0f1fda8b213ccbf21a1571447cbbd9> /Applications/Max5/Cycling
'74/extensions/live.guilib.mxo/Contents/MacOS/live.guilib
0xe3ed000 - 0xe3efff7 +com.cycling74.objectview 5.1.9 (48561)
(48561) <85e18ecf3c1f8d048353c3d62fe91157> /Applications/Max5/Cycling
'74/extensions/objectview.mxo/Contents/MacOS/objectview
0xe3f4000 - 0xe3f7ff7 +com.cycling74.zoomer 5.1.9 (48561) (48561)
<37830d94e8023a832b3befc7db6a6eeb> /Applications/Max5/Cycling '74/
extensions/zoomer.mxo/Contents/MacOS/zoomer
0xe3fc000 - 0xe3fdff7 +com.cycling74.augraph 5.1.9 (48561) (48561)
<09850a491921d7783bed6ed443de9bda> /Applications/Max5/Cycling '74/
mididrivers/augraph.mxo/Contents/MacOS/augraph
0xe401000 - 0xe402fff +AnalysisLib.ttdylib ??? (???)
<ad7a52d12f6a0e28ca30afb8a18a0283> /Library/Application Support/Jamoma/
Extensions/AnalysisLib.ttdylib
0xe406000 - 0xe409fff com.apple.audio.AudioIPCPlugIn 1.0.6 (1.0.6)
<51c811377017028f8904ad779e6a1344> /System/Library/Extensions/
AudioIPCDriver.kext/Contents/Resources/AudioIPCPlugIn.bundle/Contents/
MacOS/AudioIPCPlugIn
0xe40f000 - 0xe410ffe
com.apple.bluetooth.IOBluetoothSCOAudioDriverPlugIn 2.1.9 (2.1.9f10)
<bfe48267f5c6be068a6627073b43cdec> /System/Library/Extensions/
IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothSCOAudioDriver.kext/
Contents/Resources/IOBluetoothSCOAudioDriverPlugIn.bundle/Contents/
MacOS/IOBluetoothSCOAudioDriverPlugIn
0xe415000 - 0xe48aff7 com.apple.Bluetooth 2.1.9 (2.1.9f10)
<d70a88066ebf7eb8071781f686caced3> /System/Library/Frameworks/
IOBluetooth.framework/Versions/A/IOBluetooth
0xe4d9000 - 0xe4dbfff com.apple.BezelServicesFW 1.4.9212
(1.4.9212) /System/Library/PrivateFrameworks/BezelServices.framework/
Versions/A/BezelServices
0xe4e2000 - 0xe4e8fff com.apple.audio.AppleHDAHALPlugIn 1.7.1
(1.7.1a2) <a0a4389b5ac52ab84397d2b25c9d3b9c> /System/Library/
Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/
Contents/MacOS/AppleHDAHALPlugIn
0xe4ee000 - 0xe512fe3
+com.digidesign.digidesign.DigiCoreAudioPlugIn 7.4 (7.4f309)
<76a3a9dda9a24b2e86f45d76e957c3f4> /Library/Audio/Plug-Ins/HAL/
Digidesign CoreAudio.plugin/Contents/MacOS/Digidesign CoreAudio
0xe51f000 - 0xe552fff +com.grame.JackRouter JackRouter (0.9.0)
<c635cdfe9d7cc62709aceb9f86f6861f> /Library/Audio/Plug-Ins/HAL/
JackRouter.plugin/Contents/MacOS/JackRouter
0xe583000 - 0xe5adfff +libjack.dylib ??? (???)
<87ec84ca31b01744c5628918ae5edc10> /usr/local/lib/libjack.dylib
0xe626000 - 0xe628ff7 +AudioUnit.ttdylib ??? (???)
<10d229fc3a2824efc0253668f2de9bbd> /Library/Application Support/Jamoma/
Extensions/AudioUnit.ttdylib
0xe62d000 - 0xe62effb +Clipper.ttdylib ??? (???)
<64f117bed2a34ddcd60839c0b9588b21> /Library/Application Support/Jamoma/
Extensions/Clipper.ttdylib
0xe632000 - 0xe634ffb +Crossfade.ttdylib ??? (???)
<6d992dce83a654286bf0b152082e86ee> /Library/Application Support/Jamoma/
Extensions/Crossfade.ttdylib
0xe645000 - 0xe652ff3 +DataspaceLib.ttdylib ??? (???)
<b876dba857ba557f423bb11e02512de0> /Library/Application Support/Jamoma/
Extensions/DataspaceLib.ttdylib
0xe66c000 - 0xe675fff +EffectsLib.ttdylib ??? (???)
<1a42f0647a5f458fdf1f767a5d165329> /Library/Application Support/Jamoma/
Extensions/EffectsLib.ttdylib
0xe683000 - 0xe68fff3 +FFTLib.ttdylib ??? (???)
<a396e1683f2bc1ba49ebacae08d3579b> /Library/Application Support/Jamoma/
Extensions/FFTLib.ttdylib
0xe696000 - 0xe6afff7 +FilterLib.ttdylib ??? (???)
<0f520efd48bffeb3697deee962aa83de> /Library/Application Support/Jamoma/
Extensions/FilterLib.ttdylib
0xe86a000 - 0xe86dff7 +FunctionLib.ttdylib ??? (???)
<8250fb38b4f105c8e58bcd741a1b48e9> /Library/Application Support/Jamoma/
Extensions/FunctionLib.ttdylib
0xe876000 - 0xe87bffb +GeneratorLib.ttdylib ??? (???)
<f101e2f58fe658c332f27c1276381ea9> /Library/Application Support/Jamoma/
Extensions/GeneratorLib.ttdylib
0xe884000 - 0xe885ff3 +Label.ttdylib ??? (???)
<0557d524c22b50a2b07dff09797bd8ef> /Library/Application Support/Jamoma/
Extensions/Label.ttdylib
0xe889000 - 0xe918fff +org.jamoma.JamomaGraphics 0.1.1 ($Rev$) ($Rev
$) <44332d4928836d3c266ef32b953b49ae> /Library/Frameworks/
JamomaGraphics.framework/Versions/A/JamomaGraphics
0xe962000 - 0xe967ff3 +MathLib.ttdylib ??? (???)
<ccabb0c7d848ab7d7dd321d240b00761> /Library/Application Support/Jamoma/
Extensions/MathLib.ttdylib
0xe971000 - 0xe977ff7 +SpatDisplay.ttdylib ??? (???)
<0e2b82ffc8a677143f9ef0b6164a739b> /Library/Application Support/Jamoma/
Extensions/SpatDisplay.ttdylib
0xe97f000 - 0xe982ff3 +TTClipper.ttdylib ??? (???)
<ad031b3d52a8404d91448baa05958e81> /Library/Application Support/Jamoma/
Extensions/TTClipper.ttdylib
0xe989000 - 0xe990ffb +TTEffectsLib.ttdylib ??? (???)
<9b49ee191853de37cbadcc73c34c23c7> /Library/Application Support/Jamoma/
Extensions/TTEffectsLib.ttdylib
0xe99b000 - 0xe9aefff +TTFilterLib.ttdylib ??? (???)
<3cd4546ac445df7b7530b56566732232> /Library/Application Support/Jamoma/
Extensions/TTFilterLib.ttdylib
0xe9c5000 - 0xe9c8ff7 +TTFunctionLib.ttdylib ??? (???)
<c4eacdd126b2e198a533d9f0e47a935d> /Library/Application Support/Jamoma/
Extensions/TTFunctionLib.ttdylib
0xe9d1000 - 0xe9d5ff3 +WindowFunctionLib.ttdylib ??? (???)
<bd24d5c1586c50c7a4393430c4021ff8> /Library/Application Support/Jamoma/
Extensions/WindowFunctionLib.ttdylib
0xe9df000 - 0xea0fffb +com.cycling74.querylib 5.1.9 (48561) (48561)
<2b1fed4b4b5557b8f78b052633f576cf> /Applications/Max5/Cycling '74/
extensions/querylib.mxo/Contents/MacOS/querylib
0xeab4000 - 0xeb18ff7 +com.cycling74.sqlite 5.1.9 (48561) (48561)
<8712d600ec793b8f9499b1099a173e92> /Applications/Max5/Cycling '74/
extensions/sqlite.mxo/Contents/MacOS/sqlite
0xf106000 - 0xf108ff7 +com.cycling74.coremidi 5.1.9 (48561) (48561)
<ad5e829692037ca060942a483d98beb8> /Applications/Max5/Cycling '74/
mididrivers/coremidi.mxo/Contents/MacOS/coremidi
0xf10d000 - 0xf12aff7 com.apple.audio.midi.CoreMIDI 1.6.1 (42) /
System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0xf142000 - 0xf160fe3 libexpat.1.dylib ??? (???)
<eff8a63a23a7d07af62b36fdb329e393> /usr/lib/libexpat.1.dylib
0xf170000 - 0xf170ff7 +com.cycling74.midi_adrewire 5.1.9 (48561)
(48561) <f97b11be48aefffded65b5cad8a3a694> /Applications/Max5/Cycling
'74/mididrivers/midi_adrewire.mxo/Contents/MacOS/midi_adrewire
0xf174000 - 0xf175ff3 ATSHI.dylib ??? (???) /System/Library/
Frameworks/ApplicationServices.framework/Versions/A/Frameworks/
ATS.framework/Versions/A/Resources/ATSHI.dylib
0xf292000 - 0xf292ff7 +com.cycling74.pak 5.1.9 (48561) (48561)
<2bc4509596684bc7e8058a1bb4f69fb3> /Applications/Max5/Cycling '74/max-
externals/pak.mxo/Contents/MacOS/pak
0xf297000 - 0xf2a1ff7 +com.cycling74.function 5.1.9 (48561) (48561)
<e011e1bc68fd512167daa3797f2462e6> /Applications/Max5/Cycling '74/max-
externals/function.mxo/Contents/MacOS/function
0xf2b6000 - 0xf2c3ff7 +com.cycling74.umenu 5.1.9 (48561) (48561)
<efbe64fe3b37b16e277335d433e27d35> /Applications/Max5/Cycling '74/max-
externals/umenu.mxo/Contents/MacOS/umenu
0xf2cf000 - 0xf2d0ff7 +com.cycling74.polybuffer~ 5.0.8 (1974)
(1974) <c6ee794fc59a9bc831006aa7663d06bd> /Library/Application Support/
Cycling '74/externals/imtr/polybufer_42478/polybuffer~.mxo/Contents/
MacOS/polybuffer~
0xf2d9000 - 0xf2dbff7 +ftm.copy ??? (???)
<e0460cf939067cd8ee09dd21ee7c6fa6> /Applications/Max5/Cycling '74/ftm-
and-co/externals/ftm.copy.mxo/Contents/MacOS/ftm.copy
0xf2f9000 - 0xf2fbff7 +com.cycling74.jit.print 5.1.9 (48561)
(48561) <6c6b3e7200e84770a077a63ef2e311cd> /Applications/Max5/Cycling
'74/jitter-externals/jit.print.mxo/Contents/MacOS/jit.print
0xf400000 - 0xf400ff7 +com.cycling74.urn 5.1.9 (48561) (48561)
<8b0770d747359e2d1cbc9fca5500505f> /Applications/Max5/Cycling '74/max-
externals/urn.mxo/Contents/MacOS/urn
0xf404000 - 0xf404ff7 +com.cycling74.sig~ 5.1.9 (48561) (48561)
<2efd85efccbc10c0da6d729c2efea3a9> /Applications/Max5/Cycling '74/msp-
externals/sig~.mxo/Contents/MacOS/sig~
0xf41c000 - 0xf41cff7 +com.cycling74.speedlim 5.1.9 (48561) (48561)
<1e0cf46d18840d84f692cc9bbf84f62b> /Applications/Max5/Cycling '74/max-
externals/speedlim.mxo/Contents/MacOS/speedlim
0xf421000 - 0xf422ff7 +com.cycling74.sprintf 5.1.9 (48561) (48561)
<1fd0648faac97c3cdc910da346c2aea0> /Applications/Max5/Cycling '74/max-
externals/sprintf.mxo/Contents/MacOS/sprintf
0xf426000 - 0xf427ff7 +com.cycling74.metro 5.1.9 (48561) (48561)
<92bd0c4575ecc3315b2dadbfabbc5bd9> /Applications/Max5/Cycling '74/max-
externals/metro.mxo/Contents/MacOS/metro
0xf42e000 - 0xf42fff7 +com.cycling74.vexpr 5.1.9 (48561) (48561)
<4816cbad9af366ba6711f360cd9e8329> /Applications/Max5/Cycling '74/max-
externals/vexpr.mxo/Contents/MacOS/vexpr
0xf435000 - 0xf435ff7 +com.cycling74.dspstate~ 5.1.9 (48561)
(48561) <4922b4f68e77a8147fa70661ee2a615d> /Applications/Max5/Cycling
'74/msp-externals/dspstate~.mxo/Contents/MacOS/dspstate~
0xf444000 - 0xf445ff7 +com.cycling74.snapshot~ 5.1.9 (48561)
(48561) <d8ff993fe5c56e2721083181d5d9fce3> /Applications/Max5/Cycling
'74/msp-externals/snapshot~.mxo/Contents/MacOS/snapshot~
0xf45b000 - 0xf45bff7 +com.cycling74.spray 5.1.9 (48561) (48561)
<37a09ef5214ef209ce4bfd3e7f08d465> /Applications/Max5/Cycling '74/max-
externals/spray.mxo/Contents/MacOS/spray
0xf45f000 - 0xf45fff7 +com.cycling74.maximum 5.1.9 (48561) (48561)
<5415de95950a0335dfd2460e5f986634> /Applications/Max5/Cycling '74/max-
externals/maximum.mxo/Contents/MacOS/maximum
0xf482000 - 0xf482ff7 +com.cycling74.clip 5.1.9 (48561) (48561)
<c32bb152a7a7423346e776881c615bb2> /Applications/Max5/Cycling '74/max-
externals/clip.mxo/Contents/MacOS/clip
0xf4b9000 - 0xf4baff7 +com.cycling74.delay~ 5.1.9 (48561) (48561)
<d96cbda17ae10b5af69f94dbd745620a> /Applications/Max5/Cycling '74/msp-
externals/delay~.mxo/Contents/MacOS/delay~
0xf7bc000 - 0xf7beff7 +ftm.list ??? (???)
<3da3b5e8586953dce4e17c2db9244953> /Applications/Max5/Cycling '74/ftm-
and-co/externals/ftm.list.mxo/Contents/MacOS/ftm.list
0xf7c2000 - 0xf7c2ff7 +com.cycling74.times~ 5.1.9 (48561) (48561)
<6bc9db748e964b072e5f893b376efc73> /Applications/Max5/Cycling '74/msp-
externals/times~.mxo/Contents/MacOS/times~
0xf7db000 - 0xf7e2ff7 +mnm.median ??? (???)
<085c738b98b310dbeaba3eee185a6c00> /Applications/Max5/Cycling '74/ftm-
and-co/externals/mnm.median.mxo/Contents/MacOS/mnm.median
0xf7e8000 - 0xf7e9ff7 +com.cycling74.cycle~ 5.1.9 (48561) (48561)
<aaef6d13ccf0f3d7dd15e14ac26b0a14> /Applications/Max5/Cycling '74/msp-
externals/cycle~.mxo/Contents/MacOS/cycle~
0xf9ce000 - 0xfe20ffb com.apple.RawCamera.bundle 3.7.0 (569)
<a991d958b0d3d0717ee57dda597653fc> /System/Library/CoreServices/
RawCamera.bundle/Contents/MacOS/RawCamera
0xffe2000 - 0xffe2ff7 +com.cycling74.plus~ 5.1.9 (48561) (48561)
<252764a37a4a88eb9b96d65c61bc790a> /Applications/Max5/Cycling '74/msp-
externals/plus~.mxo/Contents/MacOS/plus~
0xffeb000 - 0xffecff7 +com.cycling74.line~ 5.1.9 (48561) (48561)
<e90f11d345147afb345662afc4700023> /Applications/Max5/Cycling '74/msp-
externals/line~.mxo/Contents/MacOS/line~
0xfff4000 - 0xfff4ff7 +com.cycling74.deferlow 5.1.9 (48561) (48561)
<f18e368d2cab0617f0921b8c88b2761a> /Applications/Max5/Cycling '74/max-
externals/deferlow.mxo/Contents/MacOS/deferlow
0x100a0000 - 0x100aaffe com.apple.URLMount 3.1.1 (3.1.1)
<b4018e683fad4259ee78070e91f35029> /System/Library/PrivateFrameworks/
URLMount.framework/URLMount
0x1013d000 - 0x10147ff7 +ftm.mess ??? (???)
<6fe96dc0bb5f454b5e7caa63b8401841> /Applications/Max5/Cycling '74/ftm-
and-co/externals/ftm.mess.mxo/Contents/MacOS/ftm.mess
0x1034b000 - 0x1034bff7 +com.cycling74.noise~ 5.1.9 (48561) (48561)
<207b8cf25c35f96ba5a3f743d5fdbbc9> /Applications/Max5/Cycling '74/msp-
externals/noise~.mxo/Contents/MacOS/noise~
0x10367000 - 0x10368ff7 +ftm.clone ??? (???)
<ee8cb13e21d55d2313fed8f94188ed86> /Applications/Max5/Cycling '74/ftm-
and-co/externals/ftm.clone.mxo/Contents/MacOS/ftm.clone
0x10373000 - 0x10377fff com.apple.CommonCocoaPanels 3.0 (15)
<e55f5774d14df35699e1d0f676993418> /System/Library/CoreServices/
CommonCocoaPanels.bundle/Contents/MacOS/CommonCocoaPanels
0x10404000 - 0x1040dff7 +com.cycling74.matrixctrl 5.1.9 (48561)
(48561) <f21fcda1e746b9dcfc303068bda36788> /Applications/Max5/Cycling
'74/max-externals/matrixctrl.mxo/Contents/MacOS/matrixctrl
0x10425000 - 0x10425ff7 +com.cycling74.delay 5.1.9 (48561) (48561)
<acda238240e67cd9d55d5a6642dc63b3> /Applications/Max5/Cycling '74/max-
externals/delay.mxo/Contents/MacOS/delay
0x10429000 - 0x10429ff7 +com.cycling74.append 5.1.9 (48561) (48561)
<307b6c9406a32ccbf6f1673fe013ed0b> /Applications/Max5/Cycling '74/max-
externals/append.mxo/Contents/MacOS/append
0x1042d000 - 0x1042dff7 +com.cycling74.scale 5.1.9 (48561) (48561)
<3b842d7c455bb6f42d1080e5e7284309> /Applications/Max5/Cycling '74/max-
externals/scale.mxo/Contents/MacOS/scale
0x10465000 - 0x10472ff7 +com.cycling74.multislider 5.1.9 (48561)
(48561) <8e08401596a166e1be54123b2832aefe> /Applications/Max5/Cycling
'74/max-externals/multislider.mxo/Contents/MacOS/multislider
0x10c96000 - 0x10ca0ffb +icst.ambimonitor ??? (1.2) /Applications/Max5/
Cycling '74/max-startup/ambimonitor.mxo/Contents/MacOS/ambimonitor
0x10cae000 - 0x10cb1ff7 +com.cycling74.comment 5.1.9 (48561) (48561)
<fb6042dabf03aca4f68403a6c3b6e035> /Applications/Max5/Cycling '74/max-
externals/comment.mxo/Contents/MacOS/comment
0x10cb9000 - 0x10cbdff7 +com.cycling74.message 5.1.9 (48561) (48561)
<44d698dba53bb6e89708edeb9c3557e7> /Applications/Max5/Cycling '74/max-
externals/message.mxo/Contents/MacOS/message
0x10cc5000 - 0x10cc5ff7 +com.cycling74.uzi 5.1.9 (48561) (48561)
<08c16778d9f5f0d8ee5354a6aa291c2d> /Applications/Max5/Cycling '74/max-
externals/uzi.mxo/Contents/MacOS/uzi
0x10d0a000 - 0x10d0eff7 +com.cycling74.panel 5.1.9 (48561) (48561)
<d12e61f6a8222ddab24a5649edd663cf> /Applications/Max5/Cycling '74/max-
externals/panel.mxo/Contents/MacOS/panel
0x10d54000 - 0x10d59ff3 libCGXCoreImage.A.dylib ??? (???)
<30bd95e38c8a203ee387013527cfd9d0> /System/Library/Frameworks/
ApplicationServices.framework/Versions/A/Frameworks/
CoreGraphics.framework/Versions/A/Resources/libCGXCoreImage.A.dylib
0x10dc7000 - 0x10dc9ff7 +ftm.schedule ??? (???)
<1dea3d09bebcfaef023e1cdda18fd7ed> /Applications/Max5/Cycling '74/ftm-
and-co/externals/ftm.schedule.mxo/Contents/MacOS/ftm.schedule
0x10ffc000 - 0x10ffcff7 +com.cycling74.jit.submatrix 5.1.9 (48561)
(48561) <477251ad8262ab20264ff52a8867f898> /Applications/Max5/Cycling
'74/jitter-externals/jit.submatrix.mxo/Contents/MacOS/jit.submatrix
0x11182000 - 0x1131dfe7 +FTMlib ??? (???)
<cf012bfa8da994c5f43983fa857a9e35> /Applications/Max5/Cycling '74/ftm-
and-co/externals/FTMlib.framework/Versions/2.5/FTMlib
0x1167e000 - 0x11688ff7 +com.cycling74.number 5.1.9 (48561) (48561)
<34f19f82877f8fd86dac2058d6250a50> /Applications/Max5/Cycling '74/max-
externals/number.mxo/Contents/MacOS/number
0x11713000 - 0x1171eff7 +ftm.object ??? (???)
<24322b285390902e7ef2551bdb577153> /Applications/Max5/Cycling '74/ftm-
and-co/externals/ftm.object.mxo/Contents/MacOS/ftm.object
0x11766000 - 0x118b9fe7 +com.cycling74.JitterAPI 1.7.0 (1.7.0)
<9b9c45232bff0ed968dceeaedb0f39de> /Applications/Max5/MaxMSP.app/
Contents/Frameworks/JitterAPI.framework/Versions/A/JitterAPI
0x119d1000 - 0x11e02fc3 +com.nvidia.cg 2.0.0010 (???) /Applications/
Max5/Cycling '74/jitter-externals/Cg.framework/Cg
0x11e93000 - 0x11f66ff7 +com.cycling74.jit.openexr 5.1.9 (48561)
(48561) <91913e606897768f68c8ba8994365502> /Applications/Max5/Cycling
'74/jitter-externals/jit.openexr.mxo/Contents/MacOS/jit.openexr
0x12400000 - 0x12412fd9 com.apple.FCP Uncompressed 422.component 1.5
(1.5) /Library/QuickTime/FCP Uncompressed 422.component/Contents/MacOS/
FCP Uncompressed 422
0x12418000 - 0x12432fc3 com.apple.AppleIntermediateCodec 1.2 (145) /
Library/QuickTime/AppleIntermediateCodec.component/Contents/MacOS/
AppleIntermediateCodec
0x12437000 - 0x1243aff7 +com.cycling74.toggle 5.1.9 (48561) (48561)
<d2bf8006cb5acda029f25797af185ed8> /Applications/Max5/Cycling '74/max-
externals/toggle.mxo/Contents/MacOS/toggle
0x12441000 - 0x12443ff7 +com.cycling74.jit.matrix 5.1.9 (48561)
(48561) <bfae235e07dc00a7edab5ad9b6719eb2> /Applications/Max5/Cycling
'74/jitter-externals/jit.matrix.mxo/Contents/MacOS/jit.matrix
0x12448000 - 0x12449ff7 +com.cycling74.jit.spill 5.1.9 (48561) (48561)
<256caaa4a0b1788e95a16cd0e4b532a9> /Applications/Max5/Cycling '74/
jitter-externals/jit.spill.mxo/Contents/MacOS/jit.spill
0x124a8000 - 0x124abfef com.apple.LiveType.component 2.1.3 (2.1.3) /
Library/QuickTime/LiveType.component/Contents/MacOS/LiveType
0x124b0000 - 0x12515fde com.apple.LiveType.framework 2.1.3 (2.1.3) /
System/Library/PrivateFrameworks/LiveType.framework/Versions/A/LiveType
0x12535000 - 0x125a7fff +com.DivXInc.DivXDecoder 6.4.0 (6.4.0) /
Library/QuickTime/DivX Decoder.component/Contents/MacOS/DivX Decoder
0x125b5000 - 0x127a5fee +com.elgato.mpegsupport EyeTV MPEG Support
1.0.7 (build 43) (1.0.7) /Library/QuickTime/EyeTV MPEG
Support.component/Contents/MacOS/EyeTV MPEG Support
0x128c8000 - 0x12988fff +net.sourceforge.webcam-osx.common 0.9.2
(0.9.2) /Library/QuickTime/macam.component/Contents/MacOS/macam
0x12a45000 - 0x12a45ff7 +com.cycling74.thispoly~ 5.1.9 (48561) (48561)
<b7ea04cefc4182af295f3240c916a35e> /Applications/Max5/Cycling '74/msp-
externals/thispoly~.mxo/Contents/MacOS/thispoly~
0x12a49000 - 0x12bf1fff +org.xiph.xiph-qt.xiphqt 0.1.9 (0.1.9)
<497da73ec0f245158f144a1772e1567d> /Library/Components/
XiphQT.component/Contents/MacOS/XiphQT
0x12c40000 - 0x12c7afff com.apple.AppleProRes422 1.0.2 (46) /Library/
QuickTime/AppleProRes422.component/Contents/MacOS/AppleProRes422
0x12cc6000 - 0x130a8ff0 QuickTimeH264.scalar ??? (???)
<5e559fe08e569b80610ad17f6e0a4f71> /System/Library/QuickTime/
QuickTimeH264.component/Contents/Resources/QuickTimeH264.scalar
0x13116000 - 0x1315afe7 com.apple.DVCPROHDCodec 1.4 (231) /Library/
QuickTime/DVCPROHDCodec.component/Contents/MacOS/DVCPROHDCodec
0x1316f000 - 0x131b5fef com.apple.viceroy.codec 32.1 (32.1) /System/
Library/Components/VCH263Codec.component/VCH263Codec
0x131be000 - 0x13261fd3 com.apple.AppleHDVCodec 1.4.1 (222)
<68abd695e9904f5f9074d2c4ae440637> /Library/QuickTime/
AppleHDVCodec.component/Contents/MacOS/AppleHDVCodec
0x1327f000 - 0x1329fff3 com.apple.IMXCodec 1.3.1 (147) /Library/
QuickTime/IMXCodec.component/Contents/MacOS/IMXCodec
0x132b7000 - 0x132d0ff3 com.apple.applepixletvideo 1.2.18 (1.2d18)
<386af0b779e8c148e6b6cbc7f5489d45> /System/Library/QuickTime/
ApplePixletVideo.component/Contents/MacOS/ApplePixletVideo
0x13398000 - 0x1339bff7 +com.cycling74.button 5.1.9 (48561) (48561)
<51c41ae67fbe9f102ee0232e2fe21235> /Applications/Max5/Cycling '74/max-
externals/button.mxo/Contents/MacOS/button
0x133e3000 - 0x133e9ff7 +com.cycling74.zl 5.1.9 (48561) (48561)
<e75046756fff1c25e8690db2fd86ee96> /Applications/Max5/Cycling '74/max-
externals/zl.mxo/Contents/MacOS/zl
0x133ef000 - 0x133f1ff7 +com.cycling74.jit.op 5.1.9 (48561) (48561)
<60e44ea6a9f0c972ec71eefa08858b4c> /Applications/Max5/Cycling '74/
jitter-externals/jit.op.mxo/Contents/MacOS/jit.op
0x133f8000 - 0x133f9ff7 +com.cycling74.jit.iter 5.1.9 (48561) (48561)
<ed8636a734fa3c73160f33ec4c104a83> /Applications/Max5/Cycling '74/
jitter-externals/jit.iter.mxo/Contents/MacOS/jit.iter
0x13647000 - 0x13648ff7 +com.cycling74.jit.3m 5.1.9 (48561) (48561)
<878c7ba6b7e0a220bcd23493fb795e70> /Applications/Max5/Cycling '74/
jitter-externals/jit.3m.mxo/Contents/MacOS/jit.3m
0x1368e000 - 0x1368eff7 +com.cycling74.loadmess 5.1.9 (48561) (48561)
<8b9eea24276ef0c4170ef9cd2b5a7453> /Applications/Max5/Cycling '74/max-
externals/loadmess.mxo/Contents/MacOS/loadmess
0x13692000 - 0x136c6fe7 +mubu.track ??? (???)
<f20c14dd0ba26e871696c786308e7c93> /Library/Application Support/
Cycling '74/externals/imtr/GF-Mubu.1.3.4.beta/externals/mubu.track.mxo/
Contents/MacOS/mubu.track
0x13757000 - 0x13c2dfff +imubu ??? (???)
<9c938c742d1a9b59b8549e5333ae79c0> /Library/Application Support/
Cycling '74/externals/imtr/GF-Mubu.1.3.4.beta/externals/imubu.mxo/
Contents/MacOS/imubu
0x1400c000 - 0x140d5fe5 com.apple.DiscRecording 4.0.7 (4070.4.1)
<7c105f35c674aad3a476f8959d3f3ebb> /System/Library/Frameworks/
DiscRecording.framework/Versions/A/DiscRecording
0x14181000 - 0x14189ff7 +com.cycling74.buffer~ 5.1.9 (48561) (48561)
<5a9ea92688d20936b1793813e4ebf6cc> /Applications/Max5/Cycling '74/msp-
externals/buffer~.mxo/Contents/MacOS/buffer~
0x14191000 - 0x14191ff7 +com.cycling74.jit.matrixinfo 5.1.9 (48561)
(48561) <4b3b142fc983099c8dedcf84df5371b6> /Applications/Max5/Cycling
'74/jitter-externals/jit.matrixinfo.mxo/Contents/MacOS/jit.matrixinfo
0x14195000 - 0x14195ff7 +com.cycling74.prepend 5.1.9 (48561) (48561)
<caa89c0f1e11f95628257afd155fc4eb> /Applications/Max5/Cycling '74/max-
externals/prepend.mxo/Contents/MacOS/prepend
0x14430000 - 0x14431ff7 +com.cycling74.counter 5.1.9 (48561) (48561)
<3bf4c836cb6f63f04d5b318505ef00d1> /Applications/Max5/Cycling '74/max-
externals/counter.mxo/Contents/MacOS/counter
0x14477000 - 0x14478ff7 +com.cycling74.text 5.1.9 (48561) (48561)
<e4637f157047a1ff3e22c9e264f68fd5> /Applications/Max5/Cycling '74/max-
externals/text.mxo/Contents/MacOS/text
0x1447d000 - 0x1447dff7 +com.cycling74.rdiv 5.1.9 (48561) (48561)
<e5c652f6e4b437a31217cb931fe906e0> /Applications/Max5/Cycling '74/max-
externals/rdiv.mxo/Contents/MacOS/rdiv
0x144c2000 - 0x144caff7 +com.cycling74.textbutton 5.1.9 (48561)
(48561) <f1e5ad8759395fa3b12899792c19d544> /Applications/Max5/Cycling
'74/max-externals/textbutton.mxo/Contents/MacOS/textbutton
0x14514000 - 0x14518ff7 +com.cycling74.ezdac~ 5.1.9 (48561) (48561)
<99244c8fe22e1c674d33752dd45c96aa> /Applications/Max5/Cycling '74/msp-
externals/ezdac~.mxo/Contents/MacOS/ezdac~
0x14520000 - 0x14523ff7 +com.cycling74.incdec 5.1.9 (48561) (48561)
<eb46f07db2e2738bd0fe3c52fecc0b91> /Applications/Max5/Cycling '74/max-
externals/incdec.mxo/Contents/MacOS/incdec
0x1456b000 - 0x14571ff7 +com.cycling74.gain~ 5.1.9 (48561) (48561)
<93bb197fe4142b7c05bd641527ae09af> /Applications/Max5/Cycling '74/msp-
externals/gain~.mxo/Contents/MacOS/gain~
0x14579000 - 0x14593ff3 +mubu.concat~ ??? (???)
<3ebbf75550ce544f49037f922ed33ab6> /Library/Application Support/
Cycling '74/externals/imtr/GF-Mubu.1.3.4.beta/externals/
mubu.concat~.mxo/Contents/MacOS/mubu.concat~
0x14a2a000 - 0x14a34ff7 +com.cycling74.tab 5.1.9 (48561) (48561)
<6adcd80ec330d7568f6e72436ec452d8> /Applications/Max5/Cycling '74/max-
externals/tab.mxo/Contents/MacOS/tab
0x14a75000 - 0x14a79ff7 +com.cycling74.swatch 5.1.9 (48561) (48561)
<50d862a2cf07fdfdcb76d8e587b766d8> /Applications/Max5/Cycling '74/max-
externals/swatch.mxo/Contents/MacOS/swatch
0x14a82000 - 0x14a89ff7 +com.cycling74.polybuffer 5.0.8 (1974) (1974)
<971018ba6e9d6d52352441da609ff46f> /Library/Application Support/
Cycling '74/externals/imtr/polybufer_42478/polybuffer.mxo/Contents/
MacOS/polybuffer
0x14a9d000 - 0x14a9dff7 +com.cycling74.substitute 5.1.9 (48561)
(48561) <749a223ec35524b0bb68bd6271ddeee7> /Applications/Max5/Cycling
'74/max-externals/substitute.mxo/Contents/MacOS/substitute
0x14aa1000 - 0x14aa3ff7 +com.cycling74.adstatus 5.1.9 (48561) (48561)
<4f40b0c09a143554df365767367991ff> /Applications/Max5/Cycling '74/msp-
externals/adstatus.mxo/Contents/MacOS/adstatus
0x14ae9000 - 0x14af1ff7 +gbr.dct ??? (???)
<7e0b066b4fafdc9fd5c3c4ef60f558c1> /Applications/Max5/Cycling '74/ftm-
and-co/externals/gbr.dct.mxo/Contents/MacOS/gbr.dct
0x14cc3000 - 0x14cd0ff7 +gbr.wind= ??? (???)
<fa22fbd59d408564bcbb178d6f5d7fca> /Applications/Max5/Cycling '74/ftm-
and-co/externals/gbr.wind=.mxo/Contents/MacOS/gbr.wind=
0x14cdf000 - 0x14ce4ff7 +gbr.slice~ ??? (???)
<99a8aa28a8f0ec56b45047eb52521c5d> /Applications/Max5/Cycling '74/ftm-
and-co/externals/gbr.slice~.mxo/Contents/MacOS/gbr.slice~
0x164a7000 - 0x164b9ff7 +ftm.vecdisplay ??? (???)
<a4cca1d71fc7768c21c521dfbad1b799> /Applications/Max5/Cycling '74/ftm-
and-co/externals/ftm.vecdisplay.mxo/Contents/MacOS/ftm.vecdisplay
0x16556000 - 0x16558ff7 +com.3dconnexion.3DxQuickTime 1.0.3 (1.0.3) /
Library/QuickTime/3DxQuickTime.component/Contents/MacOS/3DxQuickTime
0x1655e000 - 0x1657bfe4 +xsample ??? (???)
<5d584703f622a141716ea839a40bdaae> /Library/Application Support/
Cycling '74/externals/ext/xsample.mxo/Contents/MacOS/xsample
0x16588000 - 0x16594ff7 +gbr.fft ??? (???)
<380fdd406dee27db4417915548cb77dc> /Applications/Max5/Cycling '74/ftm-
and-co/externals/gbr.fft.mxo/Contents/MacOS/gbr.fft
0x1659b000 - 0x165a7ff7 +gbr.bands ??? (???)
<78c08b2b9c1ce0c5886782f4766ee11c> /Applications/Max5/Cycling '74/ftm-
and-co/externals/gbr.bands.mxo/Contents/MacOS/gbr.bands
0x165af000 - 0x165b5ff7 +com.cycling74.poly~ 5.1.9 (48561) (48561)
<9a5b126eb198f13ee1f81b5e47f8e774> /Applications/Max5/Cycling '74/msp-
externals/poly~.mxo/Contents/MacOS/poly~
0x165c1000 - 0x165c7ff7 +com.cycling74.pattr 5.1.9 (48561) (48561)
<c59d97aab8c9fe369d370752d62e9f0d> /Applications/Max5/Cycling '74/max-
externals/pattr.mxo/Contents/MacOS/pattr
0x165cd000 - 0x165cdff7 +com.cycling74.out 5.1.9 (48561) (48561)
<9c21639f72bf052194399912ca7f51da> /Applications/Max5/Cycling '74/msp-
externals/out.mxo/Contents/MacOS/out
0x16627000 - 0x1662cff7 +com.cycling74.slider 5.1.9 (48561) (48561)
<eb087bfed9d901a5b289abfddce83df7> /Applications/Max5/Cycling '74/max-
externals/slider.mxo/Contents/MacOS/slider
0x168a2000 - 0x168d5fe7 +com.cycling74.pattrstorage 5.1.9 (48561)
(48561) <412384dd79021aa6f5d79ae9fd982351> /Applications/Max5/Cycling
'74/max-externals/pattrstorage.mxo/Contents/MacOS/pattrstorage
0x16a82000 - 0x16a86ff7 +com.cycling74.pattrhub 5.1.9 (48561) (48561)
<1eac219008886ae225db1e5b315576a9> /Applications/Max5/Cycling '74/max-
externals/pattrhub.mxo/Contents/MacOS/pattrhub
0x16a8b000 - 0x16a90ff7 +mnm.submat ??? (???)
<3e715318debdc83ea5b3a7a961d08b1f> /Applications/Max5/Cycling '74/ftm-
and-co/externals/mnm.submat.mxo/Contents/MacOS/mnm.submat
0x19c6c000 - 0x19cc0fe7 +gf ??? (???)
<5618c8b9cb60d679ecca037fcbe1158a> /Library/Application Support/
Cycling '74/externals/imtr/GF-Mubu.1.3.4.beta/externals/gf.mxo/
Contents/MacOS/gf
0x19e82000 - 0x19e87ff7 +mnm.meanstd ??? (???)
<4f40fcadc58a975c189a7b1378f43f0c> /Applications/Max5/Cycling '74/ftm-
and-co/externals/mnm.meanstd.mxo/Contents/MacOS/mnm.meanstd
0x19e9c000 - 0x19e9cff7 +com.cycling74.in 5.1.9 (48561) (48561)
<6c1275a6c6a4a7a959a8352ba5e2bf47> /Applications/Max5/Cycling '74/msp-
externals/in.mxo/Contents/MacOS/in
0x1a4c6000 - 0x1a5e1fe3 +mubu ??? (???)
<b4a764c9f1d55c865b2491e80044c99d> /Library/Application Support/
Cycling '74/externals/imtr/GF-Mubu.1.3.4.beta/externals/mubu.mxo/
Contents/MacOS/mubu
0x1d5a5000 - 0x1d5a5ff7 +com.cycling74.sah~ 5.1.9 (48561) (48561)
<b9ea119fced0016b02c42adeebcb4e03> /Applications/Max5/Cycling '74/msp-
externals/sah~.mxo/Contents/MacOS/sah~
0x1e263000 - 0x1e270ff7 +net.telestream.license 1.0.8.2-GC (1.0.8.2-
GC) <a61005c5e6a484a62a8538e53cfbd6af> /Library/Frameworks/
TSLicense.framework/Versions/A/TSLicense
0x1e542000 - 0x1e547ff7 com.apple.AppleMPEG2Codec 1.0.1 (220)
<6fdff3c87ececb7413749c0230c54f78> /Library/QuickTime/
AppleMPEG2Codec.component/Contents/MacOS/AppleMPEG2Codec
0x1f178000 - 0x1f183ff7 +com.cycling74.lcd 5.1.9 (48561) (48561)
<156fab8aed2a38f5ae35d2382e30a68d> /Applications/Max5/Cycling '74/max-
externals/lcd.mxo/Contents/MacOS/lcd
0x1f4cf000 - 0x1f50afff com.apple.QuickTimeFireWireDV.component 7.7
(1680.28) /System/Library/QuickTime/QuickTimeFireWireDV.component/
Contents/MacOS/QuickTimeFireWireDV
0x231b8000 - 0x231c0ff7 +com.cycling74.number~ 5.1.9 (48561) (48561)
<1d5f509c02036556da639201761052ba> /Applications/Max5/Cycling '74/msp-
externals/number~.mxo/Contents/MacOS/number~
0x24157000 - 0x24165ff7 +com.cycling74.waveform~ 5.1.9 (48561) (48561)
<7a24737716ee50f8741b5d995c99f786> /Applications/Max5/Cycling '74/msp-
externals/waveform~.mxo/Contents/MacOS/waveform~
0x27384000 - 0x273d7ff7 com.apple.AppleProResDecoder 2.0.1 (227) /
System/Library/QuickTime/AppleProResDecoder.component/Contents/MacOS/
AppleProResDecoder
0x275ed000 - 0x27652fef com.apple.AppleVAH264HW.component 1.0 (1.0)
<9247aea75cd42fd2c138dd35ce83ab9a> /System/Library/QuickTime/
AppleVAH264HW.component/Contents/MacOS/AppleVAH264HW
0x285ee000 - 0x288defeb +org.perian.Perian 1.2.3 (1.2.3)
<722fff4f46efe5be70a642b5873d2b37> /Library/QuickTime/Perian.component/
Contents/MacOS/Perian
0x28c59000 - 0x28e4eff2 +net.telestream.wmv.import 2.4.0.11 (2.4.0.11)
<83f7489b3935e1bab93469179217a26d> /Library/QuickTime/Flip4Mac WMV
Import.component/Contents/MacOS/Flip4Mac WMV Import
0x28e83000 - 0x29045ff2 +net.telestream.wmv.advanced 2.4.0.11
(2.4.0.11) <92b25580ff565e91902fd1dc3e7ec9c2> /Library/QuickTime/
Flip4Mac WMV Advanced.component/Contents/MacOS/Flip4Mac WMV Advanced
0x8fe00000 - 0x8fe2db43 dyld 97.1 (???)
<458eed38a009e5658a79579e7bc26603> /usr/lib/dyld
0x90009000 - 0x9001ffff com.apple.DictionaryServices 1.0.0 (1.0.0)
<ad0aa0252e3323d182e17f50defe56fc> /System/Library/Frameworks/
CoreServices.framework/Versions/A/Frameworks/
DictionaryServices.framework/Versions/A/DictionaryServices
0x90020000 - 0x90020ffa com.apple.CoreServices 32 (32)
<2fcc8f3bd5bbfc000b476cad8e6a3dd2> /System/Library/Frameworks/
CoreServices.framework/Versions/A/CoreServices
0x90026000 - 0x90026ffd com.apple.Accelerate.vecLib 3.4.2 (vecLib
3.4.2) /Syste...
[truncated message content] |
|
From: Norbert S. <Nor...@ir...> - 2011-11-03 10:40:24
|
Thanks a lot for waking us up on this, Adrian. Ooooh, it's so hard to go through the code you have written a long time ago (and comments are so helpful, aren't they :-)... I finally did it and I agree on all of your changes (apart from very minor details). Since by now, you may know the code better than me, I would like you to comment on the version below. ... and than we'll finally commit this to the trunc. Thanks again Norbert |
|
From: Adrian G. <agi...@gm...> - 2011-11-03 00:59:38
|
btw, I've attached an updated version with one bugfix and with no debugging code. best adrian On Wed, Nov 2, 2011 at 1:06 PM, Adrian Gierakowski <agi...@gm...>wrote: > Hi, > > Just wanted to ask if you were considering to include my fixes in the next > FTM release? > > best > > Adrian > > > On Mon, Jul 25, 2011 at 1:18 AM, Adrian Gierakowski < > agi...@gm...> wrote: > >> Hi again, >> >> I had this laying around my hard drive for quite a while now but haven't >> had time to post it since I was in a process of finding an apartment in >> London. We finally got one and are moving on Tuesday (although I need to be >> back in Huddersfield on Wednesday since we are starting to set up for the >> ICMC). >> >> I've implemented all the features I've mentioned in the thread on the ftm >> forum. Here is the file: >> >> http://www.4shared.com/file/4iHkmmT4/ftmplay_2.html >> >> I decided to do away with the segment_tail. Instead the play_finish is >> delayed by the alarm function. This solution seemed more consistent to me. >> Let me know what you think. >> >> I also discovered a bug which causes an infinite loop if the segment >> beginning and end are set to the same value. I solved it by adding some >> checks in the play_finish function. This way if the beginning=end, and >> there are events in the sequence with time=beginning=end, then those events >> will be output once before ftm.play suspends its activity. Maybe this >> checks should be moved to play_run to prevent any output if segment >> beginning=end. >> >> best >> >> Adrian >> >> ps >> >> I left my 'debugging posts' in the code, but these can be easily removed >> sine all are marked with "// AG post" >> >> >> >> On Fri, Jul 8, 2011 at 5:47 PM, Adrian Gierakowski < >> agi...@gm...> wrote: >> >>> Hi, >>> >>> I just realised that the locks I put in the play_position functions >>> are probably redundant since the read lock is consistently used every >>> time this function is called. >>> >>> I also realised that the bug, which causes max to crash, for which I >>> posted a patch on the ftm mailing list >>> (http://listes.ircam.fr/wws/arc/ftm/2011-07/msg00007.html) is probably >>> caused by a deadlock. It is possible to avoid it by deferring the >>> insert\remove operation. Do you think its possible to avoid this in >>> the code? >>> >>> best >>> >>> Adrian >>> >>> On Fri, Jul 8, 2011 at 12:47 AM, Adrian Gierakowski >>> <agi...@gm...> wrote: >>> > >>> > Hi, >>> > >>> > I have attached a fix for the ftm.play bug which was described on the >>> ftm mailing list: >>> http://listes.ircam.fr/wws/arc/ftm/2011-02/msg00037.html >>> > >>> > I marked the added lines and blocks of code with: "// AG" to make it >>> easier to locate them. >>> > >>> > Except from fixing the setting of the segment end beyond the last >>> event of the sequence, I also modified the play_position function to allow >>> jumping beyond the last event. >>> > >>> > Any feedback would be highly appreciated :-) >>> > >>> > best >>> > >>> > -- >>> > Adrian Gierakowski >>> > >>> > ps. I don't know if attachments are allowed on the list, so in case >>> they are not, you can download the file here: >>> http://www.4shared.com/file/dVw7aK91/ftmplay.html >>> > >>> >>> >>> >>> -- >>> Adrian Gierakowski >>> >> >> >> >> -- >> Adrian Gierakowski >> > > > > -- > Adrian Gierakowski > -- Adrian Gierakowski |
|
From: Adrian G. <agi...@gm...> - 2011-11-02 13:06:13
|
Hi, Just wanted to ask if you were considering to include my fixes in the next FTM release? best Adrian On Mon, Jul 25, 2011 at 1:18 AM, Adrian Gierakowski <agi...@gm...>wrote: > Hi again, > > I had this laying around my hard drive for quite a while now but haven't > had time to post it since I was in a process of finding an apartment in > London. We finally got one and are moving on Tuesday (although I need to be > back in Huddersfield on Wednesday since we are starting to set up for the > ICMC). > > I've implemented all the features I've mentioned in the thread on the ftm > forum. Here is the file: > > http://www.4shared.com/file/4iHkmmT4/ftmplay_2.html > > I decided to do away with the segment_tail. Instead the play_finish is > delayed by the alarm function. This solution seemed more consistent to me. > Let me know what you think. > > I also discovered a bug which causes an infinite loop if the segment > beginning and end are set to the same value. I solved it by adding some > checks in the play_finish function. This way if the beginning=end, and > there are events in the sequence with time=beginning=end, then those events > will be output once before ftm.play suspends its activity. Maybe this > checks should be moved to play_run to prevent any output if segment > beginning=end. > > best > > Adrian > > ps > > I left my 'debugging posts' in the code, but these can be easily removed > sine all are marked with "// AG post" > > > > On Fri, Jul 8, 2011 at 5:47 PM, Adrian Gierakowski <agi...@gm... > > wrote: > >> Hi, >> >> I just realised that the locks I put in the play_position functions >> are probably redundant since the read lock is consistently used every >> time this function is called. >> >> I also realised that the bug, which causes max to crash, for which I >> posted a patch on the ftm mailing list >> (http://listes.ircam.fr/wws/arc/ftm/2011-07/msg00007.html) is probably >> caused by a deadlock. It is possible to avoid it by deferring the >> insert\remove operation. Do you think its possible to avoid this in >> the code? >> >> best >> >> Adrian >> >> On Fri, Jul 8, 2011 at 12:47 AM, Adrian Gierakowski >> <agi...@gm...> wrote: >> > >> > Hi, >> > >> > I have attached a fix for the ftm.play bug which was described on the >> ftm mailing list: >> http://listes.ircam.fr/wws/arc/ftm/2011-02/msg00037.html >> > >> > I marked the added lines and blocks of code with: "// AG" to make it >> easier to locate them. >> > >> > Except from fixing the setting of the segment end beyond the last event >> of the sequence, I also modified the play_position function to allow >> jumping beyond the last event. >> > >> > Any feedback would be highly appreciated :-) >> > >> > best >> > >> > -- >> > Adrian Gierakowski >> > >> > ps. I don't know if attachments are allowed on the list, so in case >> they are not, you can download the file here: >> http://www.4shared.com/file/dVw7aK91/ftmplay.html >> > >> >> >> >> -- >> Adrian Gierakowski >> > > > > -- > Adrian Gierakowski > -- Adrian Gierakowski |
|
From: Stefano F. <ste...@nu...> - 2011-08-25 09:24:04
|
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Diemo and Adrian,<div><br></div><div>thanks for the feedbacks, in the next week I'll try to write some simple externals, just to try to become familiar with it.</div><div>In case of problems I ll post to <a href="mailto:ftm...@li...">ftm...@li...</a></div><div><br></div><div>Regards</div><div><br><div><div>On 25-Aug-2011, at 12:57 AM, Diemo Schwarz wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>Last answer here, I think we should take this to ftm-devel now.<br><br>On 23.08.11 16:52, Adrian Gierakowski wrote:<br><blockquote type="cite">Hi Diemo,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks for your answers.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I was a little busy the last few days but I am hoping to get some more time<br></blockquote><blockquote type="cite">around the weekend. I'll attempt to build ftmlib then and take some notes (and<br></blockquote><blockquote type="cite">probably ask for help :) in order to update the current info.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I had a look at the ftm wiki and saw that the externals SDK there was for Max<br></blockquote><blockquote type="cite">4.6 so I added a link to the one Norbert posted on the list.<br></blockquote><br>thanks!<br><br>That's the SDK for writing external objects. Compiling ftmlib is difficult <br>because of a host of external dependencies, sometimes slightly patched, but I <br>think we might not need that, thanks to an idea by Norbert:<br><br>Mainly to Stefano: if you think your extensions live best as fmat methods, then, <br>during testing, write an ftm external that in its instantiation phase adds your <br>method to the fmat class using one of the fts_class_message_* functions. As <br>soon as your method is stabilised, we could take it into ftmlib.<br><br>If you think they would rather be an external (as I said, more complicated stuff <br>with state, or needing external libraries), then they should probably go into <br>mnm, for which we'd gladly open up the little mnmext api.<br><br><blockquote type="cite">Regarding the doxygen documentation I think it would be good to add a target in<br></blockquote><blockquote type="cite">the xcode project to make it easier to generate and install it locally.<br></blockquote><br>there is one called "doc" in ftmlib.xcode. It simply calls<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>doxygen ../../doxygen/ftmapi.doxygen<br><br>I just added ftmapi.shell.doxygen, a variant of ftmapi.doxygen to be called from <br>the shell, supposing you have installed doxygen, dot, etc. via fink in /sw/bin <br>to be called in<span class="Apple-tab-span" style="white-space:pre"> </span>ftm/build/max5/osx-macho<br>with doxygen ../../doxygen/ftmapi.shell.doxygen<br><br>I also updated the api on the server, but of course the menu formatting got <br>messed up...<br><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>...Diemo<br><br><blockquote type="cite">best<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Adrian<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Thu, Aug 18, 2011 at 8:53 AM, Diemo Schwarz <<a href="mailto:Die...@ir...">Die...@ir...</a><br></blockquote><blockquote type="cite"><<a href="mailto:Die...@ir...">mailto:Die...@ir...</a>>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> [changed the subject]<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Hi Stefano and Adrian,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> For simple state-less in-place math operations on matrices, an fmat method<br></blockquote><blockquote type="cite"> would be best. For more complicated stuff with state, or needing external<br></blockquote><blockquote type="cite"> libraries, an ftm or mnm external is best.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> We could walk you through the integration process, and though the build, as<br></blockquote><blockquote type="cite"> Adrian suggested (thanks!).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> yes, ftmlib has many dependencies it expects in a components folder in the<br></blockquote><blockquote type="cite"> project dir. I'll check out the SDK and put everything up on the wiki:<br></blockquote><blockquote type="cite"> <a href="http://ftm.ircam.fr/index.php/__Documentation">http://ftm.ircam.fr/index.php/__Documentation</a><br></blockquote><blockquote type="cite"> <<a href="http://ftm.ircam.fr/index.php/Documentation">http://ftm.ircam.fr/index.php/Documentation</a>><br></blockquote><blockquote type="cite"> Note that the server which held the ftmlib API doxygen doc will be offline<br></blockquote><blockquote type="cite"> for a while, but you can generate that locally.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> See you on ftm...@li...urceforge.__net<br></blockquote><blockquote type="cite"> <<a href="mailto:ftm...@li...">mailto:ftm...@li...</a>>!...<br></blockquote><blockquote type="cite"> ...Diemo<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> On 17.08.11 13:24, Adrian Gierakowski wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Hi Stefano and Diemo,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> @Stefano,<br></blockquote><blockquote type="cite"> I have been also thinking of writing some methods for fmat. To my knowledge<br></blockquote><blockquote type="cite"> there is no resources demonstrating how to extend core ftm<br></blockquote><blockquote type="cite"> functionality, there<br></blockquote><blockquote type="cite"> is however a little SDK with examples on how to write ftm externals.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> First you'll need to download ftm source from svn (instructions are here:<br></blockquote><blockquote type="cite"> <a href="http://sourceforge.net/__projects/ftm/develop">http://sourceforge.net/__projects/ftm/develop</a><br></blockquote><blockquote type="cite"> <<a href="http://sourceforge.net/projects/ftm/develop">http://sourceforge.net/projects/ftm/develop</a>>). I don't think the SDK is<br></blockquote><blockquote type="cite"> available<br></blockquote><blockquote type="cite"> from there but Norbert posted it on ftm forum some time ago<br></blockquote><blockquote type="cite"> (<a href="http://listes.ircam.fr/wws/__arc/ftm/2011-04/msg00024.html">http://listes.ircam.fr/wws/__arc/ftm/2011-04/msg00024.html</a><br></blockquote><blockquote type="cite"> <<a href="http://listes.ircam.fr/wws/arc/ftm/2011-04/msg00024.html">http://listes.ircam.fr/wws/arc/ftm/2011-04/msg00024.html</a>><br></blockquote><blockquote type="cite"> <%28http://listes.ircam.fr/__wws/arc/ftm/2011-04/msg00024.__html<br></blockquote><blockquote type="cite"> <<a href="http://listes.ircam.fr/wws/arc/ftm/2011-04/msg00024.html">http://listes.ircam.fr/wws/arc/ftm/2011-04/msg00024.html</a>>>).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Coming back to writing methods: in order to compile ftmlib (and test\use<br></blockquote><blockquote type="cite"> your<br></blockquote><blockquote type="cite"> newly implemented features) you need to downalod and compile a lot of<br></blockquote><blockquote type="cite"> dependencies and not all of them behave nicely (at least I had some<br></blockquote><blockquote type="cite"> unresolved<br></blockquote><blockquote type="cite"> problems, but I also didn't have much time to deal with them). It seamed<br></blockquote><blockquote type="cite"> to me<br></blockquote><blockquote type="cite"> that the instructions on that supplied with FTM source were a bit outdated.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> The above issue doesn't apply to writing and compiling externals since<br></blockquote><blockquote type="cite"> you can<br></blockquote><blockquote type="cite"> just link to the pre-compiled ftmlib supplied with FTM installation.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> @Diemo,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Do you think you would have some time to review the instruction for<br></blockquote><blockquote type="cite"> compiling<br></blockquote><blockquote type="cite"> ftmlib and update it so it would be easier for people to contribute to the<br></blockquote><blockquote type="cite"> development or add custom functionality? What I could do is to try to go<br></blockquote><blockquote type="cite"> trough<br></blockquote><blockquote type="cite"> the process again (last time I tried was April) and ask for help once I<br></blockquote><blockquote type="cite"> ecounter<br></blockquote><blockquote type="cite"> problems. I could take note as we go along and then update the README<br></blockquote><blockquote type="cite"> based on<br></blockquote><blockquote type="cite"> that (or maybe create a page on FTM wiki).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Thanks for your help!<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> best<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Adrian<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> On Wed, Aug 17, 2011 at 11:04 AM, Stefano Fasciani <<a href="mailto:ste...@nu...">ste...@nu...</a><br></blockquote><blockquote type="cite"> <<a href="mailto:ste...@nu...">mailto:ste...@nu...</a>><br></blockquote><blockquote type="cite"> <<a href="mailto:ste...@nu...">mailto:ste...@nu...</a> <<a href="mailto:ste...@nu...">mailto:ste...@nu...</a>>>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Hi Diemo,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Regarding my project, i"m focused on a sort of "holistic" approach to<br></blockquote><blockquote type="cite"> control any device which can be called "electronic music instrument"<br></blockquote><blockquote type="cite"> using<br></blockquote><blockquote type="cite"> human voice.<br></blockquote><blockquote type="cite"> The simple reason of this comes from my frustration as a musician to<br></blockquote><blockquote type="cite"> have<br></blockquote><blockquote type="cite"> "only" hands, therefore even if i have many fancy controllers in front of<br></blockquote><blockquote type="cite"> me, when it comes to live performances, there's always a big<br></blockquote><blockquote type="cite"> limitation in<br></blockquote><blockquote type="cite"> the number of "operation" I can perform at the same time (thus I have to<br></blockquote><blockquote type="cite"> rely on automations, which in my opinion are live performances and<br></blockquote><blockquote type="cite"> virtuosity killers).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> To a certain extent it may be similar to the gesture follower, but in my<br></blockquote><blockquote type="cite"> case I'm pushing in the loop also information coming from an automated<br></blockquote><blockquote type="cite"> analysis of the device that is the target of the control.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> As a framework for prototyping I've chosen Max, and FTM is really<br></blockquote><blockquote type="cite"> helping me<br></blockquote><blockquote type="cite"> a lot.<br></blockquote><blockquote type="cite"> The prototype is not "yet" working as it should, I'm working on it since<br></blockquote><blockquote type="cite"> less than 4 months. Once I got something working I can post it on<br></blockquote><blockquote type="cite"> the FTM<br></blockquote><blockquote type="cite"> website.<br></blockquote><blockquote type="cite"> There's a small description of my project and some screenshot of the<br></blockquote><blockquote type="cite"> implementation (I've integrated it in Max for Live) at this URL<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> <a href="http://anclab.org/projects/__vcemi">http://anclab.org/projects/__vcemi</a> <<a href="http://anclab.org/projects/vcemi">http://anclab.org/projects/vcemi</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> At the moment the integration of the prototype is "hybrid". For the<br></blockquote><blockquote type="cite"> unsupervised mapping I could not find enough resources within<br></blockquote><blockquote type="cite"> Max/Msp+FTM,<br></blockquote><blockquote type="cite"> therefore I wrote some lines of Matlab code to compute matrices and<br></blockquote><blockquote type="cite"> vectors<br></blockquote><blockquote type="cite"> used in the real time application. I'm doing this importing and<br></blockquote><blockquote type="cite"> exporting<br></blockquote><blockquote type="cite"> FTM objects as text files.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Thus I'd like to ask you, in order to have a "stand-alone" demo<br></blockquote><blockquote type="cite"> without the<br></blockquote><blockquote type="cite"> need of Matlab, if is there any tutorial/primer/template about how to<br></blockquote><blockquote type="cite"> develop additional functionality for FTM. Either as a function of<br></blockquote><blockquote type="cite"> the class<br></blockquote><blockquote type="cite"> fmat or as "macro blocks" like the gabor ones.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Thanks<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Cheers<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> FTM & Co<br></blockquote><blockquote type="cite"> wiki: <a href="http://ftm.ircam.fr/">http://ftm.ircam.fr/</a><br></blockquote><blockquote type="cite"> mailing-list: <a href="http://listes.ircam.fr/wws/info/ftm">http://listes.ircam.fr/wws/info/ftm</a><br></blockquote><blockquote type="cite"> bug reports: <a href="mailto:ftm...@ir...">mailto:ftm...@ir...</a> <<a href="mailto:ftm...@ir...">mailto:ftm...@ir...</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">--<br></blockquote><blockquote type="cite">Adrian Gierakowski<br></blockquote><br><br>-- <br>Diemo Schwarz, PhD -- <a href="http://diemo.concatenative.net">http://diemo.concatenative.net</a><br>Real-Time Music Interaction Team -- <a href="http://imtr.ircam.fr">http://imtr.ircam.fr</a><br>IRCAM - Centre Pompidou -- 1, place Igor-Stravinsky, 75004 Paris, France<br>Phone +33-1-4478-4879 -- Fax +33-1-4478-1540<br><span><message-footer.txt></span></div></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Stefano Fasciani<br>Arts and Creativity Lab (<a href="http://anclab.org/">http://anclab.org</a>)<br>Multimodal Analysis Lab (<a href="http://multimodal-analysis-lab.org/">http://multimodal-analysis-lab.org/</a>)<br>Interactive and Digital Media Institute<br>National University of Singapore<br>Email: <a href="mailto:idm...@nu...">ste...@nu...</a><br>Mobile: +65 84 28 64 24</div></div></span></span> </div> <br></div></body></html> |
|
From: Diemo S. <Die...@ir...> - 2011-08-24 16:57:59
|
Last answer here, I think we should take this to ftm-devel now. On 23.08.11 16:52, Adrian Gierakowski wrote: > Hi Diemo, > > Thanks for your answers. > > I was a little busy the last few days but I am hoping to get some more time > around the weekend. I'll attempt to build ftmlib then and take some notes (and > probably ask for help :) in order to update the current info. > > I had a look at the ftm wiki and saw that the externals SDK there was for Max > 4.6 so I added a link to the one Norbert posted on the list. thanks! That's the SDK for writing external objects. Compiling ftmlib is difficult because of a host of external dependencies, sometimes slightly patched, but I think we might not need that, thanks to an idea by Norbert: Mainly to Stefano: if you think your extensions live best as fmat methods, then, during testing, write an ftm external that in its instantiation phase adds your method to the fmat class using one of the fts_class_message_* functions. As soon as your method is stabilised, we could take it into ftmlib. If you think they would rather be an external (as I said, more complicated stuff with state, or needing external libraries), then they should probably go into mnm, for which we'd gladly open up the little mnmext api. > Regarding the doxygen documentation I think it would be good to add a target in > the xcode project to make it easier to generate and install it locally. there is one called "doc" in ftmlib.xcode. It simply calls doxygen ../../doxygen/ftmapi.doxygen I just added ftmapi.shell.doxygen, a variant of ftmapi.doxygen to be called from the shell, supposing you have installed doxygen, dot, etc. via fink in /sw/bin to be called in ftm/build/max5/osx-macho with doxygen ../../doxygen/ftmapi.shell.doxygen I also updated the api on the server, but of course the menu formatting got messed up... ...Diemo > best > > Adrian > > > > On Thu, Aug 18, 2011 at 8:53 AM, Diemo Schwarz <Die...@ir... > <mailto:Die...@ir...>> wrote: > > [changed the subject] > > Hi Stefano and Adrian, > > For simple state-less in-place math operations on matrices, an fmat method > would be best. For more complicated stuff with state, or needing external > libraries, an ftm or mnm external is best. > > We could walk you through the integration process, and though the build, as > Adrian suggested (thanks!). > > yes, ftmlib has many dependencies it expects in a components folder in the > project dir. I'll check out the SDK and put everything up on the wiki: > http://ftm.ircam.fr/index.php/__Documentation > <http://ftm.ircam.fr/index.php/Documentation> > Note that the server which held the ftmlib API doxygen doc will be offline > for a while, but you can generate that locally. > > See you on ftm...@li...urceforge.__net > <mailto:ftm...@li...>!... > ...Diemo > > On 17.08.11 13:24, Adrian Gierakowski wrote: > > Hi Stefano and Diemo, > > @Stefano, > I have been also thinking of writing some methods for fmat. To my knowledge > there is no resources demonstrating how to extend core ftm > functionality, there > is however a little SDK with examples on how to write ftm externals. > > First you'll need to download ftm source from svn (instructions are here: > http://sourceforge.net/__projects/ftm/develop > <http://sourceforge.net/projects/ftm/develop>). I don't think the SDK is > available > from there but Norbert posted it on ftm forum some time ago > (http://listes.ircam.fr/wws/__arc/ftm/2011-04/msg00024.html > <http://listes.ircam.fr/wws/arc/ftm/2011-04/msg00024.html> > <%28http://listes.ircam.fr/__wws/arc/ftm/2011-04/msg00024.__html > <http://listes.ircam.fr/wws/arc/ftm/2011-04/msg00024.html>>). > > Coming back to writing methods: in order to compile ftmlib (and test\use > your > newly implemented features) you need to downalod and compile a lot of > dependencies and not all of them behave nicely (at least I had some > unresolved > problems, but I also didn't have much time to deal with them). It seamed > to me > that the instructions on that supplied with FTM source were a bit outdated. > > The above issue doesn't apply to writing and compiling externals since > you can > just link to the pre-compiled ftmlib supplied with FTM installation. > > @Diemo, > > Do you think you would have some time to review the instruction for > compiling > ftmlib and update it so it would be easier for people to contribute to the > development or add custom functionality? What I could do is to try to go > trough > the process again (last time I tried was April) and ask for help once I > ecounter > problems. I could take note as we go along and then update the README > based on > that (or maybe create a page on FTM wiki). > > Thanks for your help! > > best > > Adrian > > On Wed, Aug 17, 2011 at 11:04 AM, Stefano Fasciani <ste...@nu... > <mailto:ste...@nu...> > <mailto:ste...@nu... <mailto:ste...@nu...>>> wrote: > > Hi Diemo, > > > Regarding my project, i"m focused on a sort of "holistic" approach to > control any device which can be called "electronic music instrument" > using > human voice. > The simple reason of this comes from my frustration as a musician to > have > "only" hands, therefore even if i have many fancy controllers in front of > me, when it comes to live performances, there's always a big > limitation in > the number of "operation" I can perform at the same time (thus I have to > rely on automations, which in my opinion are live performances and > virtuosity killers). > > To a certain extent it may be similar to the gesture follower, but in my > case I'm pushing in the loop also information coming from an automated > analysis of the device that is the target of the control. > > As a framework for prototyping I've chosen Max, and FTM is really > helping me > a lot. > The prototype is not "yet" working as it should, I'm working on it since > less than 4 months. Once I got something working I can post it on > the FTM > website. > There's a small description of my project and some screenshot of the > implementation (I've integrated it in Max for Live) at this URL > > http://anclab.org/projects/__vcemi <http://anclab.org/projects/vcemi> > > At the moment the integration of the prototype is "hybrid". For the > unsupervised mapping I could not find enough resources within > Max/Msp+FTM, > therefore I wrote some lines of Matlab code to compute matrices and > vectors > used in the real time application. I'm doing this importing and > exporting > FTM objects as text files. > > Thus I'd like to ask you, in order to have a "stand-alone" demo > without the > need of Matlab, if is there any tutorial/primer/template about how to > develop additional functionality for FTM. Either as a function of > the class > fmat or as "macro blocks" like the gabor ones. > > Thanks > > Cheers > > > > FTM & Co > wiki: http://ftm.ircam.fr/ > mailing-list: http://listes.ircam.fr/wws/info/ftm > bug reports: mailto:ftm...@ir... <mailto:ftm...@ir...> > > > > > -- > Adrian Gierakowski -- Diemo Schwarz, PhD -- http://diemo.concatenative.net Real-Time Music Interaction Team -- http://imtr.ircam.fr IRCAM - Centre Pompidou -- 1, place Igor-Stravinsky, 75004 Paris, France Phone +33-1-4478-4879 -- Fax +33-1-4478-1540 |
|
From: Adrian G. <agi...@gm...> - 2011-07-25 00:18:27
|
Hi again, I had this laying around my hard drive for quite a while now but haven't had time to post it since I was in a process of finding an apartment in London. We finally got one and are moving on Tuesday (although I need to be back in Huddersfield on Wednesday since we are starting to set up for the ICMC). I've implemented all the features I've mentioned in the thread on the ftm forum. Here is the file: http://www.4shared.com/file/4iHkmmT4/ftmplay_2.html I decided to do away with the segment_tail. Instead the play_finish is delayed by the alarm function. This solution seemed more consistent to me. Let me know what you think. I also discovered a bug which causes an infinite loop if the segment beginning and end are set to the same value. I solved it by adding some checks in the play_finish function. This way if the beginning=end, and there are events in the sequence with time=beginning=end, then those events will be output once before ftm.play suspends its activity. Maybe this checks should be moved to play_run to prevent any output if segment beginning=end. best Adrian ps I left my 'debugging posts' in the code, but these can be easily removed sine all are marked with "// AG post" On Fri, Jul 8, 2011 at 5:47 PM, Adrian Gierakowski <agi...@gm...>wrote: > Hi, > > I just realised that the locks I put in the play_position functions > are probably redundant since the read lock is consistently used every > time this function is called. > > I also realised that the bug, which causes max to crash, for which I > posted a patch on the ftm mailing list > (http://listes.ircam.fr/wws/arc/ftm/2011-07/msg00007.html) is probably > caused by a deadlock. It is possible to avoid it by deferring the > insert\remove operation. Do you think its possible to avoid this in > the code? > > best > > Adrian > > On Fri, Jul 8, 2011 at 12:47 AM, Adrian Gierakowski > <agi...@gm...> wrote: > > > > Hi, > > > > I have attached a fix for the ftm.play bug which was described on the ftm > mailing list: http://listes.ircam.fr/wws/arc/ftm/2011-02/msg00037.html > > > > I marked the added lines and blocks of code with: "// AG" to make it > easier to locate them. > > > > Except from fixing the setting of the segment end beyond the last event > of the sequence, I also modified the play_position function to allow jumping > beyond the last event. > > > > Any feedback would be highly appreciated :-) > > > > best > > > > -- > > Adrian Gierakowski > > > > ps. I don't know if attachments are allowed on the list, so in case they > are not, you can download the file here: > http://www.4shared.com/file/dVw7aK91/ftmplay.html > > > > > > -- > Adrian Gierakowski > -- Adrian Gierakowski |
|
From: Adrian G. <agi...@gm...> - 2011-07-08 16:47:32
|
Hi, I just realised that the locks I put in the play_position functions are probably redundant since the read lock is consistently used every time this function is called. I also realised that the bug, which causes max to crash, for which I posted a patch on the ftm mailing list (http://listes.ircam.fr/wws/arc/ftm/2011-07/msg00007.html) is probably caused by a deadlock. It is possible to avoid it by deferring the insert\remove operation. Do you think its possible to avoid this in the code? best Adrian On Fri, Jul 8, 2011 at 12:47 AM, Adrian Gierakowski <agi...@gm...> wrote: > > Hi, > > I have attached a fix for the ftm.play bug which was described on the ftm mailing list: http://listes.ircam.fr/wws/arc/ftm/2011-02/msg00037.html > > I marked the added lines and blocks of code with: "// AG" to make it easier to locate them. > > Except from fixing the setting of the segment end beyond the last event of the sequence, I also modified the play_position function to allow jumping beyond the last event. > > Any feedback would be highly appreciated :-) > > best > > -- > Adrian Gierakowski > > ps. I don't know if attachments are allowed on the list, so in case they are not, you can download the file here: http://www.4shared.com/file/dVw7aK91/ftmplay.html > -- Adrian Gierakowski |