Composers Desktop Project Forum

Quote from: rwdobson on August 25, 2024, 10:16:28 AM
I am investigating this now - MaxSmp problem confirmed. But it all works as expected on the PC version, while there is no immediate obvious difference in the code (though the Mac did requires many changes to control widget gemetries and behaviour).

Any clue on what's going on with QikEdit? Or will you run into a similar build issue to the MaxSmp fix?

Thanks for the swift reply!

Update: the offending line of code has been found. The most unfortunate news is that I can no longer build a new version of Soundloom.app as some of the tcl tools I use are 32bit binaries no longer supported on my machine (Monterey).

I noted there is  no workaround for this bug within Soundloom. However, it is possible to run "maxsamp2" from Terminal. The minimalist syntax is simple:

maxsamp2 cdptest0.wav 1

I am investigating this now - MaxSmp problem confirmed. But it all works as expected on the PC version, while there is no immediate obvious difference in the code (though the Mac did requires many changes to control widget gemetries and behaviour).

The message "KEEP:" is the first field in the text string output from "maxsamp2", followed by the amplitude values. It should be parsed and skipped past, but clearly is not on the Mac.

One of the disadvantages of a scripting language such as tcl is that code is never tested for correctness etc until it is used - unlike a stanbdard compiled language such as C, where most syntax or type errors are caught at compile time. Unfortunately, once Soundloom suffers a tcl error, it usually can't recover, there is no workaround, and it just has to be quit and restarted.

May I just add to that - if you want to hold a value for a while, put the same value at a later time, so that no interpolation occurs. Just make sure the later time is slightly less than the one which follows it. For example:

0.0 1
0.5 2
2.299 2
2.3 4.5
[etc]

Thanks for your feedback, Aila. Glad to know you've resolved the issue now.

When clicking the MaxSmp button after running a process, SoundLoom crashes with the following error log:

invalid bareword "KEEP"
in expression "1.0 / KEEP:";
should be "$KEEP" or "{KEEP}" or "KEEP(...)" or ...
invalid bareword "KEEP"
in expression "1.0 / KEEP:";
should be "$KEEP" or "{KEEP}" or "KEEP(...)" or ...
    (parsing expression "1.0 / KEEP:")
    invoked from within
"expr 1.0 / $pa($fnam,$evv(MAXSAMP))"
    (procedure "GetMaxsamp" line 104)
    invoked from within
"GetMaxsamp $fffnam $force"
    (procedure "GetMaxsamps" line 316)
    invoked from within
"GetMaxsamps 0 1"
    invoked from within
".ppg.parameters.output.mxsmp invoke"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke]"
    (procedure "tk::ButtonUp" line 23)
    invoked from within
"tk::ButtonUp .ppg.parameters.output.mxsmp"
    (command bound to event)

The Maximum sample info popup opens, but clicking OK doesn't dismiss it and the program freezes.

I also get a crash when clicking the QikEdit button from the Mix process window - the dialogue box reads "Error: unknown option '-command'", with the following error log:

unknown option "-command"
unknown option "-command"
    while executing
"label $s.000.dumm1 -text "" -command {} -bd 0 -width 11 -foreground black"
    invoked from within
"if [Dlg_Create .mixdisplay2 $fnam "set pr12_34 0" -borderwidth $evv(BBDR) -width 1200] {

if {$small_screen} {
set can [Scrolled_Canvas .mixdispl..."
    (procedure "EditSrcMixfile" line 94)
    invoked from within
"EditSrcMixfile mix"
    invoked from within
".ppg.parameters.output.editqik invoke"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke]"
    (procedure "tk::ButtonUp" line 23)
    invoked from within
"tk::ButtonUp .ppg.parameters.output.editqik"
    (command bound to event)

If I click OK to dismiss the error, I can return to the process screen, but there's a hovering title bar (no window) titled with the filename of the mixfile.
Is anyone else having these issues? Running SoundLoom E on latest Mac OS (14.5).

Thank you for the reply, I was starting to think I was on my own here haha. I'm afraid I haven't got any further really - the only way I can change the error message is by moving the self-made .bash_profile outside of its recommended path, and straight into the home directory. The error message then becomes:

CDP Install script copyfile: Error opening outfile /Users/x/tmp/bprof-backup.txt
CDP Install script ERROR: failed to backup .bash_profile.

I'm using an M1 Macbook Air with the latest OS, so I originally thought it could have something to do with that, but from your comment it would seem otherwise. The only other thing that I've thought of is the 'xattr -rc' command mentioned in the manual installation document, and the issue therefore being something to do with permissions, but what exactly to do with them is unknown to me. That's all from me for now; I'll keep searching though.

Additional: my installed version of Tcl is 8.5.9

I'm on Mac OS 14.5 Sonoma and running the latest version of SoundLoomE.
I'm having issues when clicking on dropdown menus, and mousing down the list of menu items. If a menu item is a nested submenu, the whole dropdown menu vanishes after mousing over the nested menu, and then mousing off it again.

E.g. I can mouseover all menu items in the "Workspace: Selected Files of Type" menu from "DO IT AGAIN" to "Play Merged Channels". But if I mouseover "Add Replace, or Find Sndfile(s) in Mixfile" and then move my mouse back to any top-level item (e.g. "Play Merged Channels"), the whole menu disappears.
However, the menu is still there, the screen isn't drawing it. If I mouseover the part of the screen that should contain another nested menu within the same menu, e.g. "Post Display of File(s) on Desktop", the whole menu briefly flickers on again.
Is it something to do with the version of Tcl bundled with Sonoma MacOS 14?

I've also noticed that the interface text is very blurry, like a low-resolution image that's been heavily anti-aliased. Is there any way to sharpen it up (playing havoc with my dyslexia!). Changing the large screen/small screen option in System State doesn't have any effect (I can't choose the Leeds colour scheme either).