From: gfoot AT mc31 DOT merton DOT ox DOT ac DOT uk (George Foot)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro MIDI looping
Date: 10 Mar 1997 15:55:16 GMT
Organization: Oxford University
Lines: 22
Distribution: world
Message-ID: <5g1at4$ekg@news.ox.ac.uk>
References: <5ftn9v$ks1 AT freenet-news DOT carleton DOT ca> <4DU9nOAGn9IzEwDI AT talula DOT demon DOT co DOT uk>
NNTP-Posting-Host: mc31.merton.ox.ac.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Shawn Hargreaves (Shawn AT talula DOT demon DOT co DOT uk) wrote:
: Paul Derbyshire writes:
: >The problem with making this part of the MIDI file structure instead of
: >coding it in the software, is that it requires inventing a whole pile of
: >editors and stuff for making these special MIDIs, and until one comes out,

: It can be done with standard MIDI commands that are supported by every
: sequencer. For example, MIDI defines 128 controller messages, of which
: it only uses a handful (1=modulation, 7=volume, etc), so I could use,
: say, controller 100 to set a marker and controller 101 to goto a marker. 

If you choose this route, you should allow people to change the 'base'
value away from 100, in case that means something for their MIDI hardware.

OTOH, you could use the manufacturer-specific meta event (I think it starts
with meta event type F7, and ends with a FF, or something similar). Again I
think some provision should be made to avoid clashing with real hardware
events.

-- 
George Foot <gfoot AT mc31 DOT merton DOT ox DOT ac DOT uk>
Merton College, Oxford.