this site is for reference purposes for those interested in learning about original hardware + software from the late 80s + early 90s thanks for visiting + contributing
Who | MIDI | USB Audio | Firewire Audio | TIMELINE | PCI | ISA | ATARI ST | IBM/DOS | WIN/PC | MAC | Drums | Synths | Modules | Sequencers | Samplers | Tape |
Mixers | Artists | Recent | VST | iOS | E-mu | Ensoniq | Akai "S" | Roland "MC" | MPCs | Roland "S" | Drum Machines | Roland JV | early 90s Synths | late 80s synths
guests are encouraged to: REGISTER for permission to  view file attachments + add relevant videos, downloads, resources. (credit your SOURCE!).
to post a youtube video simply paste the url! the embed will be automatically added

Author Topic: OMS for Windows (for use with Vision for Windows) (mid 1990s)  (Read 2157 times)

0 Members and 1 Guest are viewing this topic.

Offline chrisNova777

  • Administrator
  • Posts: 6663
  • Karma: +20/-0
  • Gender: Male
  • "Vintage MIDI Sequencing + Audio Production"
    • www.oldschooldaw.com | vintage audio production software + hardware info
OMS for Windows (for use with Vision for Windows) (mid 1990s)
« on: December 08, 2014, 11:56:39 PM »
trying to find this
i know it exists and is packaged with studio vision 2.5 for pc i think according to an article i quoted here:

documentation:
http://web.archive.org/web/19961113032736/http://www.opcode.com/downloads/techpubs/windows/oms/
http://web.archive.org/web/19970616193434/http://www.opcode.com/downloads/oms/windows/

http://web.archive.org/web/19961113032810/http://www.opcode.com/downloads/techpubs/windows/oms/OMSnmgr.pdf




Quote
VISIONS OF THE FUTURE: OMS & THE PC

Opcode's Open MIDI System was devised on the Mac as a central point for all MIDI-related interface and device information, and now Opcode have made a deal with Microsoft to incorporate OMS into a future release of Windows 9x. Certainly, this should be an improvement on Windows 95's half-baked way of handling audio and MIDI, though such facilities will only be really beneficial if everyone joins in. OMS 2.0, as supplied with the PC version of Vision, is a basic affair; it sniffs out all installed MIDI interfaces and represents them graphically. From its main screen, you define which synths, controllers, drum machines, and so on, are connected to each port, specifying their channels and transmit/receive requirements. A warning message tells you if you add instruments whose channels overlap. Opcode provide a (far from exhaustive) list of instruments, but thankfully there is provision for adding unknowns. Those that are known are supplied with an initial bank of factory patch names, which can be edited if required. This is an area which has great potential, since any OMS-aware application will have common access to the studio file, so that patch-bank updates made in editors and librarians will be reflected in the current studio settings which, in turn, will be known throughout the system. I wouldn't like to speculate on how long this may take to become established, though, as there is currently no release information for a Windows version of Galaxy (Opcode's own universal librarian). With Microsoft's backing, things look hopeful. Eventually.

 

Quote
SYSTEM REQUIREMENTS

« Last Edit: November 08, 2015, 03:14:56 PM by chrisNova777 »

Offline chrisNova777

  • Administrator
  • Posts: 6663
  • Karma: +20/-0
  • Gender: Male
  • "Vintage MIDI Sequencing + Audio Production"
    • www.oldschooldaw.com | vintage audio production software + hardware info
Re: OMS for Windows
« Reply #1 on: November 08, 2015, 03:15:31 PM »
hah just a little note to say that i actually got this installed just now on windows 95b
and setup was actually really easy (compared to installing windows 95 itself! holy shit what a bitch it was)
it installed oms for windows!!! and it automatically found my "roland mpu-401 compatible"
game port which is actually the yellow thing next to the parallel port, built into the Aopen AX3S-U motherboard (part of its built in soundmax soundcard)

not sure ill get much use of this.. but i was surprised how easily + fast it was installed.. with no problems
im sure if someone tried to use the same app on xp or win7 it would not work out as smooth
but perhaps it would work fine on ME or 98se.. i will find out soon ;)
im guessing this app was probably coded around 1996... and that win95b was probably exactly what it was
meant to run on (Based on how easily + error free the install was)

just a note to say...
i tried to install vision 2.5 for windows on windows 98se and the installer crashed... it doesnt even install properly

just a note to say:
i have successfully installed vision 2.5 on windows 3.11 ;)  -afro-
oms for windows is included in this package!
and it looks identical to the mac oms


Offline cpr2323

  • Newbie
  • Posts: 1
  • Karma: +1/-0
Re: OMS for Windows, coded in part by Chris Roberts
« Reply #2 on: December 21, 2015, 01:30:54 PM »
Hey guys,

 My name is Chris Roberts, and I was one of the software engineers who worked on the Windows version of Vision. Among all of the tasks I was involved in, I wrote the OMS for Windows code. This code was a really simple wrapper, or shim, around the Windows MME MIDI API. A real version of OMS was never written for Windows, as Microsoft eventually went another direction.

 In some ways, that is how the entire project was done. We didn't rewrite Vision for Windows. Instead, we documented what Mac OS calls were made, and then wrote a shim that translated the underlying work to the Window API's. It turns out, early versions of ProTools for Windows used the same approach (I also wrote the OMS emulation layer for ProTools) where they used a third party library, which I believe was called Altura.
« Last Edit: November 30, 2016, 09:04:56 AM by chrisNova777 »

Offline chrisNova777

  • Administrator
  • Posts: 6663
  • Karma: +20/-0
  • Gender: Male
  • "Vintage MIDI Sequencing + Audio Production"
    • www.oldschooldaw.com | vintage audio production software + hardware info
Re: OMS for Windows
« Reply #3 on: December 21, 2015, 02:43:14 PM »
really interesting stuff! thanks for sharing!!  8)
re; oms layer for protools; i assume u are referring to protools LE5 for windows 98??? or did you mean an earlier version of pro tools 4 for windows?

http://www.musetrap.com/cpr/resume/
http://www.musetrap.com/cpr/resume/digidesign_details.html
i guess this is your resume Chris?

Quote

1997 - 1999    Digidesign,Inc
1.5 years   Senior Software Engineer
Permanent
Windows NT, Windows'95/98, C++/C, 80x86 assembly, MacOS, MIDI, digital audio
Part of team porting Macintosh Digital Audio software to Windows NT
Developed installer using InstallShield
Developed MIDI IAC driver for NT

1996 - 1997    AppleComputer, Inc
8 months   Senior Software Engineer
Contractor
Windows'95, Windows NT, Windows 3.x, C++/C, InstallShield, Netscape Plug-In SDK
Developed installer for Quicktime Browser Plug-in for Win3.x, Win'95, and Win NT 3.x & 4.0
Added features/fixed bugs in Quicktime Browser Plug-In
Researched Java integration with Quicktime Browser Plug-In
Researched ActiveX integration with Quicktime Browser Plug-In

1992 - 1996    OpcodeSystems, Inc.
4.9 years   Senior Software Engineer/Engineering Lead
Permanent
Windows 3.x, Windows'95, C++/C, 80x86 assembly, Mac OS, 680x0 assembly, MIDI, digital audio
Porting Macintosh music software to Windows 3.x and Windows'95
Technical liaison  for Opcode/Microsoft contract
Ongoing research into cross-platform development solutions
Opcode's Windows specialist
Successfully telecommuting 5 days a week
Implemented source control via SourceSafe
Assisted in resolving cross-platform build issues and setting up autobuild system
« Last Edit: November 30, 2016, 09:02:52 AM by chrisNova777 »

Offline chrisNova777

  • Administrator
  • Posts: 6663
  • Karma: +20/-0
  • Gender: Male
  • "Vintage MIDI Sequencing + Audio Production"
    • www.oldschooldaw.com | vintage audio production software + hardware info
re: chris roberts, possibly involved with UAD-1 cards?
« Reply #4 on: November 30, 2016, 09:04:15 AM »
Hey guys,

 My name is Chris Roberts, and I was one of the software engineers who worked on the Windows version of Vision. Among all of the tasks I was involved in, I wrote the OMS for Windows code. This code was a really simple wrapper, or shim, around the Windows MME MIDI API. A real version of OMS was never written for Windows, as Microsoft eventually went another direction.

 In some ways, that is how the entire project was done. We didn't rewrite Vision for Windows. Instead, we documented what Mac OS calls were made, and then wrote a shim that translated the underlying work to the Window API's. It turns out, early versions of ProTools for Windows used the same approach (I also wrote the OMS emulation layer for ProTools) where they used a third party library, which I believe was called Altura.

wow i see also on your online resume, http://www.musetrap.com/cpr/resume/, it makes reference to Universal Audio? does that mean u were involved in someway with the UAD-1 cards?