Print

[grip]

I was playing around with the resolution settings, in fullscreen mode in milky tracker. I accidentally set it to some mode that it can't display. Now when I try to run Milky Tracker, it tries to use that mode, and crashes. I'm running it under Arch Linux, and I can't find a configuration file anywhere. Is there any way to change the settings without starting the program? Or starting with defaults?

[haschischtasche]

open milkytracker.cfg (its benath milkytracker.exe) with a hex-editor of your choice. go to line 230 and change the second byte from 31 to 30. save it, start milkytracker and configure it.
this does not do anything with the resolution (the resultion is in the lines after it), it just disables fullscreen mode.

proably you can also just delete the file and milkytracker will create a new one with default settings for you, but i am not 100% sure on that. so you should use the safe way i described above.

[Saga Musix]

go to line 230

You should be a bit more accurate for a correct answer. Various hex editors have various line lengths, mostly 8 or 16 bytes.

[haschischtasche]

the last hexedit with 8bytes line lengths i saw was at the beginning of my a500 times.

so to be more specific (just for saga ): to an ascii search for 'FULLSCREEN' and change the fifth byte after that from (hex) 31 to 30

[TraumFlug]

open milkytracker.cfg (its benath milkytracker.exe) with a hex-editor of your choice. go to line 230...

lol, he's running linux, there's no .exe or .cfg...

I think under linux the settings are all stored in "/home/username/.milkytracker_config", try deleting it to make the tracker revert to default values (better backup before...see below).

heh, there's a "-fullscreen" command line parameter, but no "-windowed", 4 lines of dead-simple code in "SDL_Main.cpp" and you could keep your settings, starting milky with windowed mode enforced  

[haschischtasche]

oh, i kind of overlooked that he is using linux.

the config file in linux (the one you told him the path for) will have the same format for sure though.

[raina]

heh, there's a "-fullscreen" command line parameter, but no "-windowed", 4 lines of dead-simple code in "SDL_Main.cpp" and you could keep your settings, starting milky with windowed mode enforced 

You're welcome to submit patches and take part in development. It's been a little slow lately on that front, no matter how open the source is.

[TraumFlug]

yeah, sure, when I've got time & enough space in my head to learn a few bits I'd love to contribute!

but another thing: I've managed to toggle fullscreen from shell, with a command. grip might find it useful to keep his settings, colours & envelopes he'd loose by deleting the config-file. thanks to inspiration from the posts above!!!

the command is, from your home directory, while milky is not running (it can't as it segfaults... ):

Code: [Select]

echo 0 | dd of=.milkytracker_config bs=1 seek=542 count=1 conv=notrunc

and milkytracker will start in windowed mode next time you launch it!

[edit] I was probably a bit too optimistic as of the config file having a fixed byte-order

please do:

Code: [Select]

dd if=.milkytracker_config bs=1 skip=528 count=10

before trying the first command. if it gives you a "FULLSCREEN" in the output (with a lot of other stats data after it, but the "fullscreen10+0" should be first), then you can switch off fullscreen mode with the first command, at least I hope so...it worked for my system & config. otherwise I can tell you how to find the right "skip" "seek" value yourself.

[Deltafire]

The -fullscreen command line option is a relic from the time when there wasn't a fullscreen setting in the config menu.  You should also be able to toggle full-screen mode using the alt-return combination.

I wonder if the seg-fault is occurring from within Milkytracker or the SDL library?

[grip]

lol, he's running linux, there's no .exe or .cfg...

Haha, yeah.

Ah yes, there it is in the home folder! I was looking everywhere for some sort of config file - guess I should have looked there first. Damn hidden files.

Anyways, deletion of the config file worked (I had barely even started using milky, so I didn't lose much).

Thanks for the help, I appreciate it!