Version: 2.0 (using KDE KDE 3.1.1) Installed from: Debian testing/unstable Packages OS: Linux I have some code that generates single track midi files with embedded lyrics. timidity handles these files well, prints the lyrics, and generates correct wav files. kmid is having trouble after a few lines of lyrics, and stops being able to play sound or show lyrics. I think there's something in the parsing of the text events. I've seen it print the first two lyrics, then a line from the middle (deterministic for the file, but I can't tell how it's chosen), and then the last line. Small modifications to the lyrics, like removing a space, seem to change which lyrics are shown. It doesn't matter whether the text events are type 1 or type 5. If I output the midi file without lyrics at all, kmid can handle that version just fine. kmidi is able to grok the lyrics, perhaps because it uses timidity as a back-end. I'll attach a sample mid file (it's just a boring drum track with lyrics) and the output of timidity -Ol to show that there are lyrics and timidity handles them. kmid prints only the first line in its window. I've spent quite a while assuming this is caused by a fault in my drum machine code, but with kmidi and timidity happy with the lyrics, kmid happy with the lyrics-free midi, and the only apparent lyrics test cases (the bundled .kar files) having a dedicated text events track, I've concluded that kmid may not handle text events in one-track midi files correctly. Thanks, kmid looks very close to what I need, and I look forward to being able to use its karaoke features.
Created attachment 1387 [details] test case - text events kmid 2.0 doesn't parse
Created attachment 1388 [details] test case - expected text events, output by timidity -Ol
kmidi no longer exists.
Darn simple search! This isn't a kmidi bug. My apologies!
Is this bug still present in a recent version of KDE, such as 3.5.8 or 4.0.1?
KMid2 is a rewrite of the old KMid, for KDE4. The first preview release have been published: http://userbase.kde.org/KMid2 The attached test case file is correctly parsed, played, and displayed in KMid2. Please test.
This issue has been addressed in the last KMid release (2.2.2). Please test.