John Vere Posted May 25, 2020 Share Posted May 25, 2020 I thought all file extensions can only use 3 digits/letters. I have Cubase and it saves files as MID. not midi? Link to comment Share on other sites More sharing options...
Noel Borthwick Posted May 25, 2020 Share Posted May 25, 2020 So by extension if someone decided to arbitrarily name .wav file .wave we should support it right and it's a "bug"that we don't? ? Well verify if this is indeed coming from established Mac apps Link to comment Share on other sites More sharing options...
Jean Corivo Posted May 25, 2020 Share Posted May 25, 2020 1 hour ago, Noel Borthwick said: So by extension if someone decided to arbitrarily name .wav file .wave we should support it right and it's a "bug"that we don't? ? Well verify if this is indeed coming from established Mac apps I see your point. It seems that on Mac, we're more likely to want to reinvent the wheel... ? Here is a screenshot when saving a midi file with Cubase 10 on OSX. By default the .midi extension is selected. Link to comment Share on other sites More sharing options...
Noel Borthwick Posted May 25, 2020 Share Posted May 25, 2020 1 hour ago, Jean Corivo said: I see your point. It seems that on Mac, we're more likely to want to reinvent the wheel... ? Here is a screenshot when saving a midi file with Cubase 10 on OSX. By default the .midi extension is selected. ? Of course MIDI was invented by Apple right? 3 Link to comment Share on other sites More sharing options...
John Vere Posted May 25, 2020 Share Posted May 25, 2020 I thought Roland was a big part of the very first MIDI connector stuff. My friend had a Juno with a serial connection and a box that converted it to 5 pin so he could use his Atari. I just fired up my Cubase Elements 7 and loaded a midi file. I then tried "save as" and it had no options other than a project file. So I used Export and it does show (.mid, .midi) in the extension box but you can't choose one or the other. I exported the file and it shows as a .mid file still. So this is a Mac thing I guess. And I also realized that with the 3 character extension I was wrong as in Docx. files. Link to comment Share on other sites More sharing options...
user 905133 Posted May 29, 2020 Share Posted May 29, 2020 Looks like EA2 will be able to read *.midi files. Link to comment Share on other sites More sharing options...
Syphus Posted May 29, 2020 Share Posted May 29, 2020 It seems this has come up before: IMHO: I do not think that per the midi standard that "*.midi" is valid file extension for midi. I'm not saying that it is not used (because there are programs out there that will only output "midi" extension), but I believe that it was not a file type back in the day. Personally, I would not expect a MIDI file to have that extension. I saw the Reaper forums talking about the same issue and now Reaper recognizes that extension. Just some observations . . . Syphus Link to comment Share on other sites More sharing options...
Robert Bone Posted May 29, 2020 Author Share Posted May 29, 2020 On 5/25/2020 at 6:44 AM, Noel Borthwick said: So by extension if someone decided to arbitrarily name .wav file .wave we should support it right and it's a "bug"that we don't? ? Well verify if this is indeed coming from established Mac apps I was not classifying my request as a bug fix - for the record - it does seem that as I had noted, Cubase on a Mac was what my friend had used to create the midi files he sent me, and it apparently did export those files with the .midi extension. I would point out that Cakewalk is currently inconsistent with handling files of type *.midi, as when I double-click such a file, it opens with Cakewalk, and Cakewalk does process the file properly and set it up ready to play with TTS-1, however Cakewalk does not show those files in either the File > Open dialog box, or in the File > Import > MIDI dialog box, or by default in the Media Browser. I have the current workaround of renaming those *.midi files to *.mid, so my request is certainly not earth-shattering, nor stopping me in my tracks, should you guys elect to skip this one. I just thought that since at least one established, and widely-used music production program does create files with that extension, and since to the best of my awareness, the implementation of adding that extension to the filters in the dialog boxes wouldn't need any additional logic, that perhaps you guys would be OK with adding it. Here is a screen shot from the Cubase export for midi files, showing their default extension in this pic, as "Untitled.midi" Link to comment Share on other sites More sharing options...
Jonathan Sasor Posted May 29, 2020 Share Posted May 29, 2020 53 minutes ago, Robert Bone said: I was not classifying my request as a bug fix - for the record - it does seem that as I had noted, Cubase on a Mac was what my friend had used to create the midi files he sent me, and it apparently did export those files with the .midi extension. I would point out that Cakewalk is currently inconsistent with handling files of type *.midi, as when I double-click such a file, it opens with Cakewalk, and Cakewalk does process the file properly and set it up ready to play with TTS-1, however Cakewalk does not show those files in either the File > Open dialog box, or in the File > Import > MIDI dialog box, or by default in the Media Browser. I have the current workaround of renaming those *.midi files to *.mid, so my request is certainly not earth-shattering, nor stopping me in my tracks, should you guys elect to skip this one. I just thought that since at least one established, and widely-used music production program does create files with that extension, and since to the best of my awareness, the implementation of adding that extension to the filters in the dialog boxes wouldn't need any additional logic, that perhaps you guys would be OK with adding it. Here is a screen shot from the Cubase export for midi files, showing their default extension in this pic, as "Untitled.midi" Import is already fixed and will be in the final 2020.05 release. Link to comment Share on other sites More sharing options...
Robert Bone Posted May 29, 2020 Author Share Posted May 29, 2020 4 minutes ago, Jonathan Sasor said: Import is already fixed and will be in the final 2020.05 release. Fantastic - thank you guys SOOO much. Link to comment Share on other sites More sharing options...
Noel Borthwick Posted May 29, 2020 Share Posted May 29, 2020 Its already in the early access 2 build. Link to comment Share on other sites More sharing options...
Robert Bone Posted May 29, 2020 Author Share Posted May 29, 2020 3 minutes ago, Noel Borthwick said: Its already in the early access 2 build. Thank you Noel. When I finish up a drum map, I will check it out. Link to comment Share on other sites More sharing options...
scook Posted May 29, 2020 Share Posted May 29, 2020 1 minute ago, Robert Bone said: Thank you Noel. When I finish up a drum map, I will check it out. Just remember EA2 only does File > Open for .midi. There is post EA2 fix for import. 1 Link to comment Share on other sites More sharing options...
user 905133 Posted June 1, 2020 Share Posted June 1, 2020 (edited) Footnotes: https://www.loc.gov/preservation/digital/formats/fdd/fdd000119.shtml lists both .mid and .midi . It looks like they based it on http://filext.com/ . Though smf is listed in the The File Extension Source data base as Standard MIDI File, several other file format evidently also use smf . The Library of Congress digital preservation document does not include the .smf extension as a standard for preserving midi files. Also, it looks like opening *.midi files via several methods will be supported in the next official Cakewalk release. Edited June 1, 2020 by User 905133 to a item 4 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now