Thank you for your response.
I appreciate you trying to help me.
I will try to apply commit #6261 to the source code and rebuild.
If the problem persists, I will downgrade to 3.13,.
Are there any differences in GC between 3.13 and 3.14.0-dev (commit from 2023 (602ab7463))?
After that, if I still have interpreter problems, I will upgrade to 3.14.1.
Only the first option, namely finding the commit that solves my problem, could allow me to save my work because I am pretty sure that my graphs will sound different if I change versions (I experienced this on another machine).
I understand and after this extremely painful experience I will take great care not to build any more dev versions in the future.
I just wanted to point out that at the time I built SC (in 2023) there were no other solutions for Linux users outside of building which by default pointed to the dev branch.
I donât know if thatâs still the case, or if there is a reason that would explain this choice that I overlooked but maybe changing the branch by default during build could avoid this kind of problems for other users?
This is potentially a better problem to have, whereas hunting through the git history will be hard.
We try very hard to keep peopleâs work sounding the same between versions and the are far more people actively working on the ugen part of the code so itâs more likely we will be able to help.
I donât think so, but it is a fragile system so other changes might affect it.
This is a serious issue if this happens regularly. @jamshark70 in another thread you very recently recommend someone build SC and sc3plugins from source, do you know if that was the dev branch? If so, issues like this might/will come up again.
One idea I had was to post a big old message in the post window when running a developer build.
Ouch! Having an unstable branch as the default branch is indeed quite dangerous. We should consider switching the default branch to main or add a prominent warning the README.
Cool! We should just add a prominent warning there. (The README only explains how you would clone a particular branch instead of the default branch but it doesnât really say why you canât just use the default branch.)
I think we should change this. Active devs know which branch they want to use. First-time builders should be able to assume that what theyâve checked out is a stable branch.
Lets not change the default branch - this would affect what branch is displayed when visiting the GH repo, which would maybe give a false sense of stalling development since we only push commits there every few months at best.
Additionally, all PRs would also target main as default branch from there on which we do not want and could lead to some trouble if an oversight happens here.
I think if people want to build SC themselves they should be somehow familiar with git or be guided by the README as this is the easiest part of the whole build process. And also most projects default to the develop branch.
Instead of changing the default branch we should document it and probably provide AppImage/FlatPak as an alternative for linux users
which would maybe give a false sense of stalling development since we only push commits there every few months at best.
Well, you cannot expect a branch to be stable and have commits from the last few days. The fact is that many people expect the default branch to be stable. But of course thatâs not the case for every project. (In Pd, the master branch is very much unstable and often outright broken )
I think if people want to build SC themselves they should be somehow familiar with git or be guided by the README as this is the easiest part of the whole build process.
One could also argue that a SC developer should be familiar enough with git/GitHub to target the correct branch or be guided by the README, probably more so than people who just want to build from source.
And also most projects default to the develop branch.
Is this the case? My impression has been the opposite. For example, in git-flow the default branch is main/master.
All that being said, I donât have a strong opinion because I see the upsides and downsides of both approaches.
I do not know if it a known issue ?
But, by opening latest downloaded development version on MacOS 15.7.3, I have a crash :
Starting interpreter with â/private/var/folders/b6/tq4hd3g56y79nyh23px1knqm0000gn/T/AppTranslocation/05190220-C971-40B2-8787-AD47AE7CBF39/d/SuperCollider.app/Contents/Resources/âŚ/MacOS/sclang -l /Users/xon/Library/Application Support/SuperCollider/sclang_conf.yaml -i scqtâ in ââ
compiling class libraryâŚ
Interpreter has crashed or stopped forcefully. [Exit code: 11]
)