You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That MIDI file has only one track, but MidiParser makes two tracks out of it, putting the notes on the first track and the name on the second track. That causes problems for apps that try to find notes based on the name of the track.
Oddly, if you load the same file into the current version of Logic Pro, it splits it into two files as well. However, both the notes and the track name are on the second track in the display. However, it's event list puts the name on the upper track, even though it displays on the bottom.
I wasn't trying to create a difficult track and I've spent a day or so just trying to figure out what is going on (and not really successful at that). I created the track by simply cutting two measures of a drum pattern sample track and pasting it to a new track in Logic Pro at the beginning. Then I erased everything else and wound up with this.
So possibly it is a very odd case and unimportant. In any event, it would be great to hear the the project is still active. I'm using it for an iPad music app that I am designing and building now. Thanks.
(later).After looking at the source code of this repository, I see that I think it relies on Apple's Midi Sequence classes in AudioToolbox to do the actual parsing. If so, the problem must be within there. That also may explain why I saw some similar problems with Logic Pro handling the same type of file.
I need to kludge my way through this for my own app somehow. So currently I am trying an awful write around where, if I look up the name and find it on track 1, but track 1 has no note events, I use track 0 instead. It actually seems to work so far, but it feels like opening a can of worms.
The text was updated successfully, but these errors were encountered:
Hi! I really like this project. Is it still being updated? Is there a newer version somewhere?
Here's my situation
Random16s.mid.zip
That MIDI file has only one track, but MidiParser makes two tracks out of it, putting the notes on the first track and the name on the second track. That causes problems for apps that try to find notes based on the name of the track.
Oddly, if you load the same file into the current version of Logic Pro, it splits it into two files as well. However, both the notes and the track name are on the second track in the display. However, it's event list puts the name on the upper track, even though it displays on the bottom.
I wasn't trying to create a difficult track and I've spent a day or so just trying to figure out what is going on (and not really successful at that). I created the track by simply cutting two measures of a drum pattern sample track and pasting it to a new track in Logic Pro at the beginning. Then I erased everything else and wound up with this.
So possibly it is a very odd case and unimportant. In any event, it would be great to hear the the project is still active. I'm using it for an iPad music app that I am designing and building now. Thanks.
(later).After looking at the source code of this repository, I see that I think it relies on Apple's Midi Sequence classes in AudioToolbox to do the actual parsing. If so, the problem must be within there. That also may explain why I saw some similar problems with Logic Pro handling the same type of file.
I need to kludge my way through this for my own app somehow. So currently I am trying an awful write around where, if I look up the name and find it on track 1, but track 1 has no note events, I use track 0 instead. It actually seems to work so far, but it feels like opening a can of worms.
The text was updated successfully, but these errors were encountered: