Now uses separate paths for each ASL requester, so it should be more convenient if you have modules in one dir and samples somewhere else
Oh cool, thanks - a small addition for the programmer but a giant leap for the composer! And as I was the one requesting this feature, I'll send a small donation your way.
Two more little things come to mind with regard to the next release candidate:
- Could you please add a version string? - Because the Amiga port handles file paths in its own way (through ASL), perhaps you could also add icon tooltypes for the default module and sample paths for the ASL requester to pick up?
- Because the Amiga port handles file paths in its own way (through ASL), perhaps you could also add icon tooltypes for the default module and sample paths for the ASL requester to pick up?
Currently requester code is not aware of sample/module/other at all, it simply stores paths like:
dict["dialog title"] = path
So there would have to be some kind of mapping from tooltype to dialog title for this mechanism to work.
MilkyTracker has a config file so ideally upstream could implement some path storage (maybe there is, didn't check it yet).
Link to the new SDL 2.0.14 version: this should fix some cosmetic issues in fullscreen related to ASL requester. Add version string. Add stack cookie of 100000 bytes.
I just downloaded, and I must have something set wrong because playback is very choppy and sounds bad. Playback with a much older version of Milky is fine. This is on my X1000 using motherboard audio. Something I missed?
Thanks for response. The older version I have installed on my X1000 since ages is 0.90.80. It plays back fine. I don't ever create anything with it, just play modules made by others. Only thing I don't like about this version is I cannot figure out how to tell its built-in file requester to go to another device/volume -- only to folders going back to root. Probably I am missing something obvious.
Was pleased to see your version uses ASL, and that works a treat. Just have this problem where playback is bad. In fits and starts, very choppy. Maybe there is a setting I can adjust if this is not a bug???
Again, I am using an X1000 with Lyle's audio driver for onboard sound, and I am running OS4.1 FE Update 2.
Could you check the CPU usage without MilkyTracker and with MilkyTracker? Could you also check if there is some debug "storm" on the serial port, for example using Sashimi tool?
Have you tried removing the MilkyTracker config file?
It would be great is someone else with X1000 could also test?
EDIT: Actually the testing took me minutes not hours, and all is good here.
When I went to test against I found that I had too hastily deleted the new MilkyTracker so after I extracted the program from the archive again and ran it and used it to play some modules.... well, I find that all is working fine. Playback is perfect.
So I do not know what the problem was previously. My apologies for sounding the alarm. All is well here.
Edited by mbrantley on 2021/4/3 20:32:10 Edited by mbrantley on 2021/4/3 20:32:41 Edited by mbrantley on 2021/4/4 13:03:17