[Terteory]

I use MSiOS since three weeks. I imported my library from MS-Android and most things work fine.
Only the midi files will not play in the iOS-Version, because the files cannot load (there is an error-message, when I open the song). In the android version, the midi files will play.
Any suggestions, what to do?
Ulba

[Zubersoft]

Unfortunately, Apple does not support playing back MIDI files as audio with CoreAudio (their audio framework). So until I have time to implement my own MIDI sequencer and synthesizer, that is not supported on iOS. It's also not supported on Windows for the same reason. You'll have to convert those files to mp3 files.

Mike

[RoSong]

Hi Terteory, 

I just posted in this forum my workaround for playing midis. I saw your post the other day. I had asked the same thing a while back. 

I just figured everything out and got it set up yesterday. It's kind of long and involved, so I thought it should be a new post, as I tried to give specific instructions. 

If you're new to the apple ecosystem, you might have to do a bit of research on some of the information. Can't tell you how many countless hours I've spent over the past couple of years googling "how to" with regard to this ipad, having always used android ( will probably stay with android phones). The main reason I chose an ipad is the 4:3 ratio and I don't regret it. The shortcut automation is also amazing for editing both chordpro and pdfs.

Anyway, my workaround is not the same as being imbedded in the app, but it works really well. I hope it's helpful to you.


Mike, 

On another note, I tried another approach which did not work, but maybe could with some code adjustments?

I used a smart button and chose Open file and I put in the path and file. I have put several midi player apps on my device, and lo and behold it opened in one of the players. But it was stuck there. It wouldn't go back to MS because it thought it was still there. There's a Done in the RH corner, and pressing that does take me back to MS, but the music will not continue to play. 

Ios doesn't let you choose default apps, so it picks which app it will use and that it. It uses NS Midi Player as the default. 

This also works in Files. If I click on any midi file in Files, or longpress and choose quick look, it will automatically open in this app. It's very basic. No bells and whistles, but it does play the file. When in Files and the midi is playing, it shows the NS Midi Player screen. Pressing Done takes you back to Files. 

The interesting thing is, once you've played one, and gone back to Files, it registers in the "Now Playing" in control center, but no audio sounds if you press play on it, although the track moves like it's playing. Also, when other music apps have something loaded in the now playing icon of control center, even other midi programs, they play, pause, rewind, from the control center and pressing the icon takes you into the app. None of that works when doing it through Files, though, or by extension the smart button in MS. 

Okay, I just tested it and another interesting thing is that NS player, even though no setting exists to choose "play in background" it actually DOES (and the contol center "now playing" features  work, as well, IF starting in that app! But it runs differently when using Files.

Several of the other midi apps I tried have a setting to play in background or do not sleep, but the simple player ios chooses to play a file doesn't have that option. (And yet it does automatically if not gone to from Files.)

I also tried uninstalling NS Midi Player, since I have other midi-playing apps, I thought maybe, ios would pick something else to open, but it didn't work. It tried to open in text format.

The share featue in Files works well though, to play through other midi apps, but I was hoping that opening natively without extra steps would work with the smart button. I've been trying to find way incorporate using shortcuts to extend what happens after pressing the the smart button and getting the file, but couldn't figure anything out.

Please read through my workaround post, using shortcuts and accessibility features. Maybe there's something useful for you to use in the future.