Hi all,

I have found a library that I would like to use (you can find it under "Software" at http://soundobject.org/).

I would like to compile these files on my OSX system but the only files for installation available are for Windows and Linux. Is there anyway of modifying what is available here so that I can compile these objects in my Pd library?

Thanks for any help in advance!

Chris

Hi, thanks for your help. I thought this might one way of solving my problem (but I haven't tried it out yet as I'm a little unskilled in using makefiles and the like).

One problem I think I might run across is that none of the files have .pd_darwin extensions only .dll and .pd_linux. So I might have compatibility problems. Does anyone know if .dll and .pd_linux files can be easily changed to .pd_darwin?

I might just install a virtual version of Windows on my Macbook and use this external that way. It might be the easiest solution

Hey, none of the files have a .pd_darwin extension because these are the compiled libraries for osx.
So far as i know it is not possible to convert pre compiled libraries for other machines.
If you want to use it on your machine you will need to compile it.

Installing a virtual machine with Windows maybe a solution but not a really satisfiable one.

There is not that much that needs adjustment in the makefiles so probably this little afford
is worth it and once done you can recompile it everytime if u ever need to.

Ahhh, I obviously have very little understanding of what's going on with these files. So if I can get a proper makefile working, I should be able to make the pd_darwin files for the library? I've tried adding just the .dll files to the PureData search path (on my Windows virtual machine) and the objects work there, which is a start!

I had a look at the makefiles in the source code you mentioned and here: https://puredata.info/docs/developer/MakefileTemplate but I'm not totally sure how it all works still.

That's a challenge for tomorrow though. Thanks for your help niku!

Hi @me-andmymonkey, I was able to compile the object impact_modalb~ using xcode, so it is usable in OSX. I tried using the included impact_modalb_example.pd, and it worked, and it is pretty awesome!

Find the pd_darwin external here:

https://www.dropbox.com/sh/fb2uoqmg5w58rq7/AABrJ7vErKA4ajRVvmdDU8-La?dl=0

If it doesn't exist yet (in my case, it didn't), you must create a folder called Pd under the Library folder, which is itself on the root directory, so that you have the following path:

/Library/Pd/impact_modalb~.pd_darwin

Open impact_modalb_example.pd, which is part of the zip file you must have downloaded. Let me know if it doesn't work...if it does, I could try to compile some of the others.

afsacp

Hey @afsacp that's awesome, thanks for doing that. However, the .pd_darwin file isn't working for me when I add it to my search path. This happens if I add it to to either my user specific ~/Library/Pd/ folder or the global /Library/Pd/ folder. It did work fine when I added the .dll files for Windows the same way, which is odd. I wonder why it's working for you and not me.

Good to see that someone did it, maybe it would be nice if @afsacp tells you how to compile it with xcode so you can do it for yourself.

A reason why it does not work could be the Architecture you are using.
If @afsacp is compiling on a 64bit arch and you are using 32bit it will not work.
If this is the case he can compile it using 32bit compiler, or gives you the advice you need to build it on your system.

@niku okay, that makes sense. I'm trying to download a version of Xcode that will work on my version of OSX now. I'll try and make an attempt at compiling my own pd_darwin external.

If you could point me in the right direction @afsacp that would be superb though. Thank you both for your help so far!

Great point, @niku! I use:
OSX 10.8.5
Pd 0.43.4-extended
Xcode 4.6.2
Externals are compiled at 32 bits.

@me-andmymonkey, it might be helpful to know the following:

1. What OSX version you're using
2. What kind of error message you get when trying to instantiate the external in Pd
3. What version of Pd you are using

@niku & @me-andmymonkey, I can point you to some of the documents to create working dynamic libraries in Xcode for use as externals:

http://puredata.info/docs/developer/PdExternalsInXcode

The link below has become the reference for writing externals in C.

http://pdstatic.iem.at/externals-HOWTO/

The actual compiling is relatively easy if you've done some of it already. But the solution might be relatively simple (I hope!), and it might be that Pd can't see the external yet. Which is why learning the behavior of Pd upon attempting to instantiate the external is so crucial. Let me know!

Hi @afsacp , thanks for the links on externals.

I'm running OSX10.9.5 (64-bit) with Pd extended 0.43.4. When I open the impact_modalb_example.pd patch with the impact_modalb object I get an error saying:

"impact_modalb~ 1e+07 1.5 0 0.1 2 3 d 1 1 1 1 1 500 5000 0.1 0.1 0 1 1 1 1 1 2 1 1
... couldn't create"

I presume this might be because I'm running a 64-bit system OR (and this is also fairly likely) I'm doing something wrong when I'm adding the external to my Library folder.

Hope this info helps.

OK. I'll try rebuilding at 64bit. However... the message you get is typical of Pd not being able to find the object. If the architecture was wrong, like if the external was built for x86-64 instead of the i386 (which is 32bit), Pd would complain:

/Library/Pd/impact_modalb~.pd_darwin: dlopen(/Library/Pd/impact_modalb~.pd_darwin, 10): no suitable image found. Did find:
/Library/Pd/impact_modalb~.pd_darwin: mach-o, but wrong architecture

Perhaps some other members can pitch in with regards to potential location of the externals. The location I suggested has worked for me from first try. Good luck!

@me-andmymonkey, check the folder again. A subfolder now contains the 64bit version. It should be noted that building this version raised a lot of flags regarding data type conversion. I'm frankly a bit fuzzy on this, but the idea is that different data types require different sizes, and the compiler builds it according to that and to the architecture selected, so that an integer in 32bit arch should be 4 bytes, but in 64bit should be 8bytes, and so on. So this could raise issues with precision, rounding off errors, etc. Like I said, fuzzy.

In any case, try to work with the 32bit version first, attempting to find a suitable location for the externals. I'll keep looking through my references.

Hey @afsacp. Thanks again for doing that.

So, I'm getting the same error again saying that Puredata couldn't create the object after adding the pd_darwin file to my /library/pd folder.

I think that would suggest there maybe isn't a problem with the either of the 32bit or 64bit compiled files you made and rather a problem with how things have been added to my library.

I've added the /Library/Pd/ folder to my search path from preferences. I also tried adding the file to a a new folder I added myself inside of the "extra" folder in the package contents of the PD app itself but this didn't work either.

Is there anything else I can do to try and add this external to my library? I'm sort of at a miss as to how Pd isn't recognising the files.

Hey @me-andmymonkey, I found another option, which should work. Follow these steps (try first with the 32bit, tell me what happens):

1. In Finder, go to Applications folder.
2. Right- or control-click on Pd-extended
3. Click on "show package contents"
4. Navigate to Contents -> Resources -> extra
5. Create a folder with the exact name of the external (impact_modalb~)
6. Put the file impact_modalb~.pd_darwin in that folder.
7. Open Pd (close first if open), then load the same example file you tried earlier.

I did all the above and it worked.

afsacp

Hi @afsacp , so I've figured out the problem! When I downloaded the files from Dropbox, the filename was changed from "impact_modalb~" to "impact_modalb-", which was confusing PD. This is why the object wasn't being created with the 32bit file. The 32bit works fine. The 64bit actually doesn't load for me and throws up an error message like the one you described in an earlier post.

I've been trying all of this out today in work in between different things and never even thought to look at the filename. Having to type it out exactly as a folder name gave me the clue! So in short, the 32bit works fine on my system and I'm quite happy now. Thanks for your help @afsacp and @niku

I'll have to try compiling it for myself. So I'm assuming I can compile each module one by one to get the all the other objects working?

Compiled everything in Xcode. Easy as pie and I thought that it would be difficult!

This day officially rules!

Great to hear, @me-andmymonkey! Make sure to share the externals. Best luck,

afsacp

Here's all the new OSX externals compiled from the original .zip file. Enjoy all

https://www.dropbox.com/s/szywfl7rjsy822u/impact_modalOSX.zip?dl=0