Issues with Sound Loom on Mac and Request for Resources

[emiliano76]

Hi everyone,

I'm not a completely new user of Sound Loom. I used to use it on PC, and now I'm on Mac. After checking the checkinstallation file, everything seems to be okay, but I don't see the presets/patches for textures when I start a texture process on a file.

Additionally, it would be great if there were more resources on how to compile the various CDP Files & Codes. I know there's already a dedicated page for this, but in the case of the TEXTURE environment, I only see a "Note Data File for TEXTURE MOTIFSIN."

What can I do to make the learning process easier for me? CDP and Sound Loom are wonderful worlds, and I believe they are still the best tools for transforming acousmatic music.

I might be a bit off-topic, sorry, but any response to my questions would be very important for me to continue.

Thank you in advance!
emiliano
https://www.instagram.com/_a__v__e__n__i__r_/

[rwdobson]

That is a very good question! The simplest and quickest solution is to copy all the old preset and other files from your PC setup to the mac. This is the directories _cdpatch and _cdpins. The problem then is that the patch files appear to have hard Windows paths such as "C:\txws", for files that are clearly part of Archer Endrich's "Texture Workshop", which is still part of the full CDP documentation. A further snag is that (from memory just now) "texture" underwent a few changes for Release 8 (not least for multichannel processes), which may possibly make old patches fail to load.

That documentation (look for "htmltuts") is, I think, still the first place to go to for information and tutorials about Texture (etc).  As soon as I have more concrete information (and possibly provided a file to download) I will follow up here. RD.

[emiliano76]

Thank you so much for the detailed response!
In effects for now, the only way to make some strings work (I tried from the terminal shell and not Sound Loom) has been to copy all the configuration files from _cdpatch to _cdp.
I'll start by transferring the also the _cdpins directories as suggested and will keep an eye on the Windows paths. I'll also check the "htmltuts" documentation for more insight. I truly appreciate your advice, and I look forward to any additional information or downloadable files you may provide.

In the meantime, I'd like to share my latest work. All the sound design here was created using Composer Desktop / Sound Loom. It's great to know there's still someone providing support for this incredible set of tools.

https://on.soundcloud.com/2cALd4UwCxDx1eoT7

Thanks again, emiliano:)

[emiliano76]

With the help of CHAT GPT, I tried to break down the peculiarities related to the texture and had it generate a couple of randomized files following the rules. Additionally, I found it very interesting to create a sort of data entry training, getting GPT to clarify the concepts that were less clear. I then made the 3D model available for consultation. I'm not sure if it will be useful to anyone, but I'm sharing the URL here.


https://chatgpt.com/share/672cb3b1-db68-800c-b81d-c48ce1ac1ec6

[Carnamagos]

How did you even manage to get Sound Loom installed and working on a Mac? I am still stuck at the "'soundloom'" is damaged and can't be opened. You should move it to the Trash" stage! Sorry to be off the topic of the thread here, but I'd be seriously grateful for any advice as to how you succeeded in doing that.

[simonk]

This thread might help

https://unstablesound.net/cdpforum/index.php?topic=267.0

[Carnamagos]

The problem is that my Terminal appears to be completely broken. It was telling me I needed to run a particular command to change to the zsh shell, but then, when I run that command, it tells me "command not found". I then entered the command into the Terminal settings, but then when I launched the Terminal, it requested a password to change to zsh, yet won't allow me to enter anything. What's more, it won't allow me to enter any other Terminal commands.

I realize that this is not a CDP problem. Trouble is, Apple technical support won't help with this, either. So, I suppose I am stuck!

Thank you, anyway.