[phpBB Debug] PHP Notice: in file /viewtopic.php on line 988: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.
[phpBB Debug] PHP Notice: in file /viewtopic.php on line 988: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4505: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3706)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4507: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3706)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4508: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3706)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4509: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3706)
Sagan Technology Metro • View topic - MIDI import/export

MIDI import/export

Please post any ideas for new features in Metro or Metro SE here.

MIDI import/export

Postby Fred » Wed Mar 12, 2003 6:20 am

On importing a MIDI file Metro *sometimes* puts program numbers into the tracks window. Such partial information is more misleading than useful and i propose to omit these program numbers altogether.

On exporting a MIDI file Metro generates several Meta-Events, eg. Sequence Number, Instrument, SMPTE Offset, Key Signature. I think these are generally rather useless and may even cause troubles in other sequencers. Thus i propose to export only (as usual): Tempo and Time Signature.
Fred
 
Posts: 25
Joined: Sat Feb 15, 2003 11:36 am

Re: MIDI import/export

Postby Jerm » Wed Mar 12, 2003 9:40 am

Fred wrote:On importing a MIDI file Metro *sometimes* puts program numbers into the tracks window. Such partial information is more misleading than useful and i propose to omit these program numbers altogether.


I am not sure if you explained this to me before but perhaps you could explain why this is misleading?

Fred wrote:On exporting a MIDI file Metro generates several Meta-Events, eg. Sequence Number, Instrument, SMPTE Offset, Key Signature. I think these are generally rather useless and may even cause troubles in other sequencers. Thus i propose to export only (as usual): Tempo and Time Signature.


Perhaps an option to omit this information would be useful. Metro uses this information when re-importing and can definitely be useful especially if you are trying to provide backward compatibility with older versions.
Jerm
 
Posts: 2707
Joined: Tue Feb 11, 2003 12:50 pm
Location: Massachusetts

Postby Fred » Wed Mar 12, 2003 11:31 am

Well, if you have a MIDI file imported and some (but not all) program numbers are shown you suspect that some tracks have no program defined. But inspecting such a track in list editor reveals that there is a program change, only preceeded by other control events, eg. Volume or Pan. This order is sometimes generated by sequencers. As you have mentioned earlier, a possible solution is to scan the track from the beginning for a program change which appears before the first note event. Then it is clear that the track will play this program (at least at the beginning, but it's normally not changed later on). To make the solution complete, also Bank Select should be scanned and put into the tracks window, following the rule "all or nothing".

As for the Meta-Events i would appreciate an option to switch off all except Tempo and Time Signature. This is for example convenient if you want to publish a MIDI file for general use.
Fred
 
Posts: 25
Joined: Sat Feb 15, 2003 11:36 am

All or nothing

Postby Guest » Wed Mar 12, 2003 3:35 pm

Fred wrote:...To make the solution complete, also Bank Select should be scanned and put into the tracks window, following the rule "all or nothing".


All or nothing? Or Once or nothing? :?:
Guest
 

Meta Events

Postby Jerm » Wed Mar 12, 2003 3:55 pm

Fred wrote:As for the Meta-Events i would appreciate an option to switch off all except Tempo and Time Signature. This is for example convenient if you want to publish a MIDI file for general use.


What about key-signature?

Of course with a little more work we could have check boxes for all the meta items but that would probably not be appropriate for the SE version. Too complicated.
Jerm
 
Posts: 2707
Joined: Tue Feb 11, 2003 12:50 pm
Location: Massachusetts

Postby Fred » Wed Mar 12, 2003 6:47 pm

What about key-signature?


ok, i have to admit, key-signature is generally useful. Look at a sheet of music: There are time-signature, key-signature and tempo as global "meta events". Consequently this is the natural basic set for MIDI files.
Fred
 
Posts: 25
Joined: Sat Feb 15, 2003 11:36 am

Postby buserror » Wed Mar 12, 2003 7:17 pm

I had noticed that in metro, a MIDI track that has tempo changes embedded (past delta T 0) are handled perfectly, but if there are time signature changes embedded in the same way, they are ignored (most noticeably when using the metronome)

I don't consider thit a "lack of functionality", just worth being noted, I think :-)
buserror
 
Posts: 65
Joined: Sat Feb 15, 2003 8:11 am
Location: UK

Postby Fred » Thu Mar 13, 2003 4:52 am

I had noticed that in metro, a MIDI track that has tempo changes embedded (past delta T 0) are handled perfectly, but if there are time signature changes embedded in the same way, they are ignored (most noticeably when using the metronome)

I don't consider thit a "lack of functionality", just worth being noted, I think


But actually it is. Compare again with sheet of music: time-signature, key-signature and tempo can be changed at any point.

However, i am not claiming more functionality and features. On the contrary ("less is more"), i vote for clearness and simplicity, ie. to omit useless stuff and information not being well-defined.
Fred
 
Posts: 25
Joined: Sat Feb 15, 2003 11:36 am

Postby Fred » Thu Mar 13, 2003 8:31 am

One (final) remark on the issue of MIDI import: Program change and bank select are changes of STATE. In principle there may be different such states within a track. Thus it seems not appropriate to display just one (eg. the first) of these states in the tracks window. Special analysis of the track is possible, but i don't think it's worth the effort and again raises the question how to display the results.

On the other hand there is an appropriate place in Metro to show state changes, namely the instruments window. As far as i have seen, all relevant states like program number, volume, pan are properly shown on playback, except perhaps bank select. If not, this would be my "feature request".
Fred
 
Posts: 25
Joined: Sat Feb 15, 2003 11:36 am


Return to Metro/LX/SE Feature Request

Who is online

Users browsing this forum: No registered users and 0 guests

cron