Contact me at Rednroll@hotmail.com. I justed sent an email to Opcode because on their website they have the Mac versions downloadable for free. I asked them, "why isn't the PC version also posted"? Well, unfortunately I didn't get a response because, obviously the lights are on but nobody's home.
The PC version was a couple versions behind as far as audio features, but the midi features where eccentially identical.
One word of caution, because the real reason I was trying to contact Opcode was I recently tried to install Vision on my Windows XP machine. Vision installs fine and the program actually seems to function ok too. The problem is that there is a seperate part of Vision called "OMS Studio setup". OMS detects all your midi ports and then allows you to rename them to whatever instrument you have connected to that port. Then you can load in an instrument file or create your own, so you can easily select the patches on your keyboard/sound module easily from within Vision. Like I said before, at this point when I look at my Roland JV-90 keyboard, I don't even know how to change patches without having Vision running. I just create a midi track and then open the patch menu and all 400 of my patches are listed, where I just select the one I want. Makes it very easy to audition different sounds for the same track. You can even layer patches to create your own sounds from within Vision. Anyway....I kind of went off on a rant. OMS doesn't seem to be functioning properly on Windows XP, which means Vision can not access your midi interfaces ports. So I was contacting Opcode to see if they knew of anyone successfully running Vision on XP or if they have heard of any third party OMS studio setups which may have been written. < Chirp..Chirp..crickets>
So contact me and I can hook you up, but so far it seems you will have to run it under Windows 98se. But the nice thing is that I have Vision running on a 200Mhz machine with 96 meg of Ram and that's plenty fast. So if you have an outdated boneyard PC laying around, just think of it as another piece of gear within your studio.
If there's anyone out there that has an OMS version that runs on WinXP, I'ld love to hear from you.
wow.
Lets keep this thread up, as we have to find a good solution. I do have a PC that runs the printer close by at the studio so the way you are saying might work, but surely isnt very optimal.Using ASIO drivers I dont think Ill be able to run sonar or something similar on my normal PC either will I?
For our old mac two studios ago, we had opcode midi interfaces, and lst nite I found the vision manual. Looks like a pretty good program, that even someone with a complete lack of understanding midi can really get into.
For my case all I need is to record a midi track alongside vegas. After that I can run it in acid and "BFD " it, I think, or maybe convert the track to pulses and drumagog it.
Ill be contacting you from my bigger email at the studio, but I think SF should have some sort of MIDI solution
Heres a few more cases:
Guitar players with expression pedals. It would be nmice to be able to store those values for later on incase they couldnt decide between a wah or a mod effect
Or how about program change messages and CC messages to your outboard fx?
Maybe this might be a bit of help...(as i say *might*...)
As for as a standalone midimachine triggered with Vegas (with MTC or Midi Clock),
I still use Digital Orchestrator Pro from Voyetra on a XP machine for my midi..multiple midi outs and pretty extensive midi editiing...and (that's what I think,that's why I still use it)pretty straightforward and intuitive .Now I know this product was phased out a year ago,but probably you can get it on EBay or what have you.Also,they got the same midi-functionality preserved in the new line of Record Producer Midi,they sell it for about $ 35 on their site.
Red, allthough DOP Pro is a twoheaded beast (a win311 core with win95 enhancements) it still runs in W2K/XP.I had to juggle with some .INI files to get it stable-(even disabled the audioside of it to make it perform better,tighter with midi clocking)...took me quite some time to get it right.Maybe you missed something itsybitsy ridiculous(very common in computerland with all those compatibility-issues I presume ;) ) -a setting in an INI file,a wrong DLL version etc.If you like,I would give it a try with that OMS setup ...I drop an email-adress in this forum if you're interested...but I suspect that you did all necessary tweaking and twitching with it...right?
I haven't changed any .INI settting for midi, I don't know how too. I'ld love it, if you could give me some help in this, so I could possibly get vision running on XP.
"Or how about program change messages and CC messages to your outboard fx?"
Yeah, I use to use Vision for this all the time syncing to DA-88's. I would have Vision sync to Midi time code/smpte, then send program changes to FX devices or also do parameter changes. This worked out nice on one mix I was doing, because I ran out of external FX's in the studio I was in and needed one more requested FX. So it just happened in the first part of the song that an FX was used, but not used later during a bridge part where I needed the FX I was missing. So I used Vision to send program changes to that FX to use 1 FX module for 2 different tracks.
The ports exist, the problem is that OMS can't recognize that they exist. Therefore, Vision cannot select the midi port to play a midi track too. So it's really not a problem of being able to open or close a midi port, it's a problem of the program locating it's driver to know they even exist on my PC. You can pretty much think of it as a sound card, where you know it's properly installed and other programs use it, so you know it works, but one program doesn't know where to look to access it's driver to make it work within that program. OMS, has a feature, where you tell it to "auto detect devices". This is where it will detect the midi INs/Outs installed on your PC, then sometimes it will even be able to detect the actual type of keyboard you have connected to that port and it makes what it refers too as your "Studio setup". This helps in a lot of ways in transporting of files. If someone brings me a sequence they did in their studio saved as a vision file, well of course they might have an entirely different midi interface, and keyboards,samplers, sound modules, connected in their studio. So when I open their Vision sequence, upon opening it says "the studio setup does not match", MPC-3000 does not exist, map this instrument too? Then I map that instrument to the port I have connected to my drum machine. Well anyways, OMS will not detect that any midi interface is even installed on my PC, which it is of course.
"cant find anything in the tracktion site that mentions sync"
...That's why I discarded it as a serious tool for my setup.There is no sync whatsoever.
That's the thing what boggles me the most about freeware or cheapware:where's the sync? Where's the multiple outputs?
Red,drop a line(if you want) to smeggelioni(don'tspam_but_actually_i_couldn't_care_less_because_it_is_hotmail)@hotmail.com .I don't know how big this OMS setup is in kBytes is,but maybe you can send this later when I give you my other email adress.-unless the thingy is dongle(or floppy)protected ofcourse.