Notifications
Clear all
Topic starter
I have a bunch of old midi files I created (.mid), some as far back as the mid 1990's. The vast majority were created on Macs (prior to OSX). Some were later used on Windows machines, some have been used for CD-ROM applications, etc. At some point - and I'm not exactly sure when or how, most of them began to show as "Unix Executable File" after transferring them back onto my Mac. Many do not have the .mid file name extension now. But even when I add .mid to the file names, most are still not recognizable by any midi software I've tried; it seems that a few of them DID become recognizable and able to be opened, but not most.
The file sizes do seem to roughly match what I would expect to see of each tune, so I believe the data is still contained within these files. But what's the solution? Does it have something to do with headers/resource forks, etc.?
I'll try to link to one of the files as an example. I'd appreciate any input or solutions.
Thanks in advance!
Posted : 19/02/2025 7:52 am
I'd be happy to have a look at the file, and try to do something with it, but I cannot do anything with the DropBox link, which does not seem to directly link to any file.
Could you try to just attach the file to a normal message. If the forum does not like the filename (or the extension) just rename it to some that is accepted (i.e. a .zip) but detail in the message what you've done.
Otherwise, it would be a help to give some details about the file, i.e. the size) and/or use a hex/binary editor and list the first few bytes of the data. Is there an initial MThd segment?
Geoff
Posted : 23/02/2025 8:23 am
