Since I have already downloaded and installed their latest version of https://github.com/capehill/MilkyTracker I noticed that there is a MilkyTrackerX listed that looks very modern and has other useful features.
Is there a possibility to provide this tracker for AmigaOs4.1 as well or are the dependencies for it currently not fulfilled under AmigaOs4.1?
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
Wow, I still consider Milky my favourite tracker, and this looks like a BIG release with a lot of great new features! I really like the new, more streamlined user interface - makes things more organized and easier to find. Watching the video I'd say that Protrekkr has just got a very serious contender!
So thanks very much for the port! Need to try it out ASAP and see how it works under OS4.
Happened to me too the first time I ran the program. Then I disabled the internal file browser in the Config, and no DSI occurred since.
@Capehill
The program now uses noticeably more resources, so I wonder if it still has a large-enough stack to avoid DSI errors? What's the size of your stack cookie? I know I could raise the stack in the program icon, but as I use the IconX trick to start Milky (in order to avoid displaying the obtrusive CLI window), I believe the stack size saved in the icon would raise the stack for IconX rather than for the tracker binary.
Stack cookie is 100000 bytes. Maybe you could try to bump it to 1000000 and check what is reported use at the exit? I found some big stack allocation earlier which I changed to heap, but I didn't realize this internal browser is a stack hog, too.
Thank you, I didn't know that. Never been too much of an AmigaDOS expert
@Capehill
False alarm, the stack wasn't it. I tried increasing it to 500,000 but the DSI is still there when invoking the internal browser. If you make a debug version, I could send you a crashlog. But I believe you'll be able to reproduce the crash yourself on your OS4 system. It generally takes place after you load a song and then try to load a sample or instrument clicking on the respective LOAD button.