@manual{ Grame00 ,
title = {MidiShare Developer Documentation v.1.80 Release Notes},
author = {Grame},
editor = {Grame},
url = {MidiShare-ReleaseNotes180.pdf},
year = {2000},
date = {2000-01-01},
abstract = {MidiShare version 1.80 is an Open Source Release: its source code is publicly available under the GNU Library General Public License. The kernel architecture has been slightly revised in order to facilitates porting on new platforms. A GNU/Linux version has been designed, based on this architecture. The main change consists in removing the IO drivers from the kernel itself and in providing mechanisms to plug these drivers dynamically as external ressources. Therefore, a new manager, the Drivers Manager, is part of the MidiShare kernel architecture: it is in charge of the drivers activation, it also routes the events to their final destination according to the drivers setup. This document describes these changes and gives the reference of the new functions and data structures introduced with this new architecture. The reader is supposed to be familiar with the MidiShare Developer Documentation.},
keywords = {MidiShare, operating, real-time, system},
pubstate = {published},
tppubtype = {manual}
}

@inproceedings{ Fober:96 ,
title = {Recent developments of MidiShare},
author = {Dominique Fober and Yann Orlarey and Stephane Letz},
editor = {ICMA},
url = {ICMC96ms.pdf},
year = {1996},
date = {1996-01-01},
booktitle = {Proceedings of the International Computer Music Conference},
pages = {40–42},
abstract = {MidiShare is a real-time multi-tasks musical operating system first presented at the ICMC 89. Based on a client/server model, MidiShare offers fast and accurate real-time performances, multi-platform support, powerful inter-application communications, while considerably simplifying the development of complex real-time musical applications. MidiShare has been used by our institution for internal developments for more than 7 years. It was awarded by the Apple Trophy 89 and the Paris-Cité 90 prize. Today, it is evolving toward a distributed multi-platform environment. The poster session will present and demonstrate its recent developments: the MidiShare environment, the developer’s kit and documentation, multi-platform development issues, libraries, Ethernet support, compatibility with other systems and third parties applications.},
keywords = {MidiShare, operating, real-time, system},
pubstate = {published},
tppubtype = {inproceedings}
}

@manual{ Grame90 ,
title = {MidiShare Developer Documentation},
author = {Grame},
editor = {Grame},
url = {MidiShare.pdf},
year = {1990},
date = {1990-01-01},
abstract = {This manual is intended for developers who wish to write MIDI applications using MidiShare. It contains a complete description of all the MidiShare functions and data structures, as well as several examples of code.},
keywords = {MidiShare, operating, real-time, system},
pubstate = {published},
tppubtype = {manual}
}

@inproceedings{ Orlarey:89 ,
title = {MidiShare : a Real Time multi-tasks software module for Midi applications},
author = {Yann Orlarey and H. Lequay},
editor = {ICMA},
url = {ICMC89ms.pdf},
year = {1989},
date = {1989-01-01},
booktitle = {Proceedings of the International Computer Music Conference},
pages = {234–237},
abstract = {This paper introduces MidiShare, a real time software module meant for the development of Midi applications in a multi-tasks context. MidiShare brings facility in most of the fields concerned with the development of musical applications: communications management, precise time control, tasks scheduling. The originality of MidiShare lies in its capacity to deal with multiple Midi applications running at the same time. Besides, MidiShare offers some interesting possibilities, particularly the one consisting in a dynamic connection between Midi applications through internal links. MidiShare was at first designed for the Macintosh under MultiFinder, it is now available on other machines.},
keywords = {communication, MIDI, operating, real-time, system},
pubstate = {published},
tppubtype = {inproceedings}
}