Hype:

I forgot to express my approval in this thread. I approve this release.

I vote no.

Lazerbeat wrote:

Quick question, I am trying to map instrument select to F11 and F12 but I am not having much luck. I have this in my keymap file

K_KP_MINUS = K_F11
K_KP_PLUS = K_F12

Any idea what I am doing wrong?

EDIT :

Whoops, had it backwards,

K_F11 = K_KP_MINUS
K_F12 = K_KP_PLUS

Working on a laptop? If you happen to have more keys in that mapping, could I include it as some kind of standard laptop compatibility keymap?

Still not able to get it running under Win 8.1 64bit. sad But my patience is with me, since I'm able to continue working with it on my second laptop under Win 7.

https://dl.dropboxusercontent.com/u/119 … -win32.zip

Unzip, double click "run.bat", post the results. I bundled the debugger with the debug build so it should show exactly where it crashes.

I should remove that warning. It just means the currently selected theme doesn't have the font file, so the default file will be used.

Lazerbeat wrote:

Gorgeous themes!

Was the 64 bit linux version updated? I just downloaded and it still show 1309?

Ah sorry, I somehow uploaded the old file. Give me five minutes.

Edit: Fixed!

Better prepare for bug reports I guess: https://github.com/kometbomb/klystrack/releases/tag/1.6

Probably should post update information here as well (and I forgot my Nabble password).

This build should fix all of the mouse cursor weirdness: https://dl.dropboxusercontent.com/u/119 … -win32.zip

And most of all, I fixed the filter distortion bug with loud volumes and mixing waveforms. It was because the soft distortion algorithm overflowed, so I replaced it with a simple hard clipping. It shouldn't be that audible, not sure if the soft distortion ever kicked in.

It also adds a default song feature, Default.kt is loaded on startup and you can customize the file if you like. Now it's just a song with a few empty patterns.

So I managed to break the window resizing. If you don't resize the window after startup it will work ok. If you resize, you need to restart for the mouse to start working. If you get weird keyboard behavior after switching windows, try hitting Alt. Sometimes if you use Alt+Tab to switch, one of the windows will think the keys are still held down (because the release key event goes to the next window). So you get Alt+LEft keyhits in klystrack instead of just a Left.

n00bstar wrote:

Also.. should we move this conversastion to the klystrack forum entirely? I always feel like we're borrowing CMO for something the LSDJ crowd doesn't give a shit about smile

Sure. At least the technical discussion is quite off-topic.

Yeah I found out it's a bug in SDL, something about it not knowing the window is visible again. It's apparently been fixed a while ago but simply not released yet.

It's really, really annoying how the SDL folks have been overdue on the next release for almost a year. Who on earth thinks that is acceptable behavior in this day and age?





</teh sacrasm>

I rewrote some of the window resizing code which might have caused that black window problem. I can only test it myself tomorrow at work but here's the fixed build: https://dl.dropboxusercontent.com/u/119 … -win32.zip

Turns out I had just compiled the nightly so part of it thought MIDI was still there... I'm kinda bummed because I thought that crash would lead into some real problem that causes all kinds of trouble.

Edit: Fixed that button placement bug.

Edit: https://dl.dropboxusercontent.com/u/119 … -win32.zip

Found out that buttons work actually, but their hitbox is moved up a little bit. So, to press a button you should press above it.

Thanks this helps a lot. Created an issue for this. The dialog works quite wonkily if you resize the application window while not in the main view so not all resize events are caught.

Don't kid yourself. Clicking on Wavegen now crashes the application.

Well, at least it is consistently happening here as well. Still: FUCK.

Knock on wood. I think the only remaining problem is that screen of blackness, though on this work machine it never crashes, you only need to resize the window and it's black no more. It's annoying though.

The MIDI implementation could send some random-ish events and perhaps that isn't thread-safe. It's probably the only remaining difference between your system and my system and I haven't tested that thoroughly (I can only do some fancy memory testing on my Linux debug system and MIDI is not available there).

Yeah well now every save will try to create a backup (except for .WAV export) so that feature pretty much is there.

Also: https://dl.dropboxusercontent.com/u/119 … -win32.zip (disabled MIDI because it doesn't work anyways and I'm trying to eliminate things that might crash) Does this or the build from yesterday hang when quitting? Does it crash when you save? Does it only crash when you click one of the "Save unused data" buttons but not when you click the other?

If it still crashes then I will send a debug .exe that you can run under the debugger and it will show the exact line where it crashes. I can probably automate it so it shouldn't be too technical, it would be cool if you could spend a few minutes trying to get it crash (it sounds like you encounter crashes quite a bit unless you are exaggerating) and then send me the info the debugger displays after you type in a short bit.