Hello
I'm unable to make csound~ work with Max8.1.0(64b)
I can't remember when the problem started but I think it's related to Max8.1.0 with MacOS 10.14.6

I get :

csound~: unable to load object bundle executable
2019-10-17 15:32:54.548 Max[4999:132112] Error loading /Users/yanmaresz/Dropbox/_Max/PRTM/ENGINE/CSOUND/csound~.mxo/csound~: dlopen(/Users/yanmaresz/Dropbox/_Max/PRTM/ENGINE/CSOUND/csound~.mxo/csound~, 265): Library not loaded: /Users/M/Documents/CsoundX
code/Release/CsoundLib64.framework/Versions/6.0/CsoundLib64
Referenced from: /Users/yanmaresz/Dropbox/_Max/PRTM/ENGINE/CSOUND/csound~.mxo/csound~
Reason: image not found

Works fine with Max7.3.6(64b)
Do you know what can cause this ?
Thank you

Yan Maresz

I'm getting a Can't compile error in max4live. Ableton Live build 10.0.6, under Max for Live, Max Version 8.0.2. Switching to the editor, the problem doesn't exist, and plays fine. The problem only occurs when I am not in the editor and just using a Max for Live device:

csound~: end of score. overall amps: 0.0 overall samples out of range:
csound~: 0
0 errors in performance
csound~: Elapsed time at end of performance: real: 262.012s, CPU: 262.012s
csound~: resetting Csound instance
csound~: 0dBFS level = 32768.0
csound~: --Csound version 6.12 beta (double samples) Oct 24 2018
[commit: 037becccce26dc9ebc37198a75877e817431d978]
csound~: libsndfile-1.0.29pre1
csound~: Can't compile. Please provide a valid csound message first.

If I load a sample into an ftable in csound~ using the readbuf message, loscil will not play it. If I use writebuf to copy the ftable back into a buffer in Max, it works as expected- copying the entire ftable into the buffer.
Example csd, maxpat, and sample:
https://www.dropbox.com/s/jcivqb5y18bfijv/loscilLoadTest.zip?dl=0

From
csound/csound#502

it would be good to have a Readme that explains status of the project, how to install, and the fact that despite no release since 2019, it "just works" with the latest Csound installed on the system.

I can do this so will assign to myself.

I am using Csound 6.07, as csound~ doesn't work with any Csound version after 6.07. Anyways, Live 10 is out now, and the csound~ Max4Live object doesn't seem to work when you add a device to a track. However, when you jump into the editor, it works, but only while in the editor.

Hello,

I'd like to ask for help in a strange issue that I'm having with the csound~ 1.1.3 object.

The problem is that any .csd file I try to open with the csound~ object cannot be compiled. The Max console shows the following message:

csound~: UnifiedCSD: [The directory of the .csd, but, for some reason, always with a different mistake, like an extra or missing slash, an extra letter, so on...]
csound~: Reading CSD failed ... stopping
csound~: csoundCompile() failed.

When I double click the object it tells me the following:

csound~: Could not convert [the directory, but again, with a random mistake] to FSRef.

Now, what I found specially strange is that, using the help file of the csound~ object, all seems to work fine, but if I change the .csd file, the problem reapears (even if I change to an exact copy of the .csd used in the help file)
If I just copy and paste the hole help file in another patch, it stops working and the "Could not convert to FSRef problem" message appears again.

Can anyone help me?

This is happening in a Mac 10.12.3, with Max 7.3.5 and, as I said, the csound object is the 1.1.3, with Csound 6.04 installed.

Thanks in advance!!

Getting a couple errors when attempting to build in VS 2019:

CMake Error at C:\Users\Justin\Source\Repos\csound_tilde\CMakeLists.txt:128 (add_library):
  The target name "csound~" is reserved or not valid for certain CMake
  features, such as generator expressions, and may result in undefined
  behavior.	csound	C:\Users\Justin\Source\Repos\csound_tilde\CMakeLists.txt	128	

CMake Error at C:\Users\Justin\Source\Repos\csound_tilde\CMakeLists.txt:129 (target_link_libraries):
  Cannot specify link libraries for target "csound~" which is not built by
  this project.	csound	C:\Users\Justin\Source\Repos\csound_tilde\CMakeLists.txt	129	

Hi,

I'm having a problem using the new version of csound~ 1.13.vb in Max 8.1.5. Whenever I instantiate both csound~ object and modalys~ object in the same Max session, it instantly crashes. Does anybody know why this is happening? To be clear: both of them work just fine on their own, but it crashes instantly together. I also sent a message to the Modalys Forum at the IRCAM website, but I've had no answeres as of right now. However, I strongly believe that this problem has been caused by this new version of the csound~ object, since this was not a problem before and modalys~ has not been updated in ages.

Any help is welcomed,
T.

If I load a buffer into an ftable with a readbuf message, it will copy the correct length, but it will not copy the correct amount of channels (it is typically defaulting to 1 channel, even when loading a stereo file). Also, it seems like performance with loscil is inconsistent- sometimes tables loaded in with readbuf will work, and sometimes they won't.
Here is a link that includes an example maxpatch, csd, and some samples:
https://www.dropbox.com/s/v6pd0601a7rxwa6/Readbuf%20Bug.zip?dl=0

I am using csound~ 1.1.3, Max 7.0.4, and OSX 10.10.3

From csound/csound#496

I have isolated a bug with strget : sometimes the reported string is not correct.
Let run the (very simple) attached patch test-strget.zip for a "certain time" and sometimes the string printed in max window is not right....maybe a threading issue or string memory allocation ?
csound~ v1.1.3(vb+)
MacOS 10.13.6
Max 8.1.3
csound 6.14
But maybe it reveals a bug in csound, because I am not able to reproduce my problem with csound 6.10 ...
Thank you for any hint !

Hey,
i got this error when trying to instantiate csound~ on max 8, osx 10.14.6 :

2019-09-24 05:55:31.294 Max[1159:146811] Error loading /Users/vichug/Documents/Max 8/Packages/csound~_v1.1.0_double/externals/csound~.mxo/Contents/MacOS/csound~:  dlopen(/Users/vichug/Documents/Max 8/Packages/csound~_v1.1.0_double/externals/csound~.mxo/Co
 ntents/MacOS/csound~, 262): no suitable image found.  Did find:
 	/Users/vichug/Documents/Max 8/Packages/csound~_v1.1.0_double/externals/csound~.mxo/Contents/MacOS/csound~: mach-o, but wrong architecture
 	/Users/vichug/Documents/Max 8/Packages/csound~_v1.1.0_double/externals/csound~.mxo/Contents/MacOS/csound~: mach-o, but wrong architecture

It seems related to 64 bit vs 32 bit issue. I'm not sure what has changed since last time i have used it (i'm nto sure if it was max 6 or 7), but the behaviour regarding 32 bits and 64 bits compatibility isn't the same in max 8 iirc.
Having very limited experience in compiling for Max, i'm not sure i can help, unfortunately...

Hi,

As I wanted to include the csound~ external in a standalone, I've been spending some time on a recent fork with the initial objective of getting it to work for me on macOS and also to create a relocatable external (not dependent on local ~/Library/Frameworks/Csound64.framework

To that end, I've made some progress and I think some of it would be worth contributing back to the project in a PR at some point if I get past some frustrating windows compilation issues (windows is not my platform of choice -- I'd appreciate some advice if possible).

In any case, here's a brief list of the changes so:

• Converted to Max Package with regular cross-platform structure

• Added max-sdk-base as git submodule

• Added Makefile frontend for simplified macOS builds

• Fixed macOS compilation errors related to deprecated apis (dropped carbon and rewrote Launch code) and also made a few general code improvements (complete diff here):

  • Removed all using namespace std statements and converted unqualified terms to qualified, and renamed byte in definitions.h to csbyte because there were name collisions between std::byte (added in c++ 17) and former.

  • Dropped use of auto_ptr in csound~.cpp, which was removed in c++17, : converted to std::unique_ptr.

  • Dropped some deprecated or obsolete api usage, for exampleFSRef -> CFURLRef

• Added Build variants with associated scripts:

  • macOS - local build: non-relocatable, dynamically linked to local csound library or framework

  • macOS - hybrid build: relocatable with static csound + dynamic dependencies

  • macOS - release build: relocatable 100% static build using vcpkg.

  • windows - NOT complete due to residual linking errors but with updated cmake build...

fork: https://github.com/shakfu/csound_tilde

Currently the csound~ object is distributed as archives with a lonely binary object. This is bad because the archive doesn't contain help files and examples. I checked the frontends/max_csound_tilde directory and found all this stuff there. Also I found scripts which build .msi and .pkg installers which were deprecated in favor of packages. Max package is essentially a directory with defined structure, containing such subdirs as extras, help, etc. Having a proper package we can submit a package to the their repository, and users will be able to install csound~ from the Max itself through the package manager.

I checked how the build process is done, but unfortunately I don't know CMake well enough to make modifications that would collect all assets into proper places.

From csound/csound#696