search

markusschwenk / midieditor

Provides an interface to edit, record, and play Midi data
GNU General Public License v3.0
468 stars 69 forks source link

Interface disappears, despite mostly functioning #59

Open MrMagolor opened 4 years ago

MrMagolor commented 4 years ago

After editing a midi and closing the editor after saving, I loaded it again, but when I do, all the events, as well as even the measures, disappear, despite all tracks and channels being set to visible. Despite this, playback still works perfectly fine, and I noticed no issues with the sound. I'm unsure if it's an issue with the midi, and if so, how I can fix it, as the events aren't visible for me to fix said issues.

I would attach the midi here, but I'm unsure how to go about that as GitHub does not support attaching that file type.

trebmuh commented 4 years ago

I would attach the midi here, but I'm unsure how to go about that as GitHub does not support attaching that file type.

Just add a .txt at the end of the filename extension, and that'd do.

MrMagolor commented 4 years ago

Here it is, then

La-Mulana+2+OST+-+False+Ruler+(Nibiru+theme).txt

GabrielMiceli commented 4 years ago

The MIDI file appears to be not working. MidiEditor says "The file is damaged and cannot be opened," MIDITrail says "Unsupported SMF format," and pmidi does nothing. Try opening this file and letting me know your results: https://www.dropbox.com/s/ryn8gd3g51hsiwt/soundchk.mid?dl=1

MrMagolor commented 4 years ago

That one works fine, the other midis i've tried to edit work fine - the only thing I can think that would have caused the issue is that I may have overlaid two events on one track and channel, would that have caused the file damage? And if so, is there a way to repair it?

GabrielMiceli commented 4 years ago

I just opened the file in a hex editor and found that many bytes were 0x20 (Space) when they most likely should have been 0x00 (NULL). Go to https://hexed.it and open the file. You should see "4D 54 68 64 00 00 00 06" at the start. If you do, try uploading the file to Dropbox, Google Drive, OneDrive, whatever and sharing the link here, as something converted the nulls to spaces the way you uploaded it the first time. If you see "4D 54 68 64 20 20 20 06" like I do, your file is nearly impossible to fix.