Cockos Incorporated Forums - View Single Post - REAPER 5.40: The night is dark and full of terrors

levets · 04-01-2017, 10:20 AM

MIDI

support ".midi" as an importable file extension, in addition to the usual ".mid"

Not April Fools:

WTF?

Not only can no one do General MIDI correctly, but now they're making up their own filename extensions?

I had to Google it and there's very little information other than it seems to be screwing people up.

.mid is the correct file extension. If ".midi" is to ".mid" as ".aiff" is to ".aif", then people should be using the 3 letter extension to make it cross-platform compatible.

So THIS is important but being able to select sounds from the TCP isn't?

Or as mentioned above, any of the other long-standing issues?

I mean, I guess I'll go search for the thread here where 10,000 users complained that they couldn't import ".midi" files so the Devs felt the need to incorporate it.

But I haven't heard very much discussion of it here...not that I'm a long-standing member or anything, but really, come on.

It's just a tease - it's frustrating to think that someone might actually be out there listening and that things could actually be changed, and that a program so customizable would be so much easier to implement these changes in, unlike Apple or Avid.

Life was much easier when you paid a fortune for Pro Tools and you just accepted the fact that making any changes to the program simply wasn't going to happen and your input would be completely ignored. You got on with the business of making music in whatever way the program allowed.

04-01-2017, 10:20 AM	#19
levets Human being with feelings Join Date: Jan 2017 Posts: 159	MIDI support ".midi" as an importable file extension, in addition to the usual ".mid" Not April Fools: WTF? Not only can no one do General MIDI correctly, but now they're making up their own filename extensions? I had to Google it and there's very little information other than it seems to be screwing people up. .mid is the correct file extension. If ".midi" is to ".mid" as ".aiff" is to ".aif", then people should be using the 3 letter extension to make it cross-platform compatible. So THIS is important but being able to select sounds from the TCP isn't? Or as mentioned above, any of the other long-standing issues? I mean, I guess I'll go search for the thread here where 10,000 users complained that they couldn't import ".midi" files so the Devs felt the need to incorporate it. But I haven't heard very much discussion of it here...not that I'm a long-standing member or anything, but really, come on. It's just a tease - it's frustrating to think that someone might actually be out there listening and that things could actually be changed, and that a program so customizable would be so much easier to implement these changes in, unlike Apple or Avid. Life was much easier when you paid a fortune for Pro Tools and you just accepted the fact that making any changes to the program simply wasn't going to happen and your input would be completely ignored. You got on with the business of making music in whatever way the program allowed.