Sep 03, 2008 01:19 am Chris Burke/Ulrichburke again, I should have put this in the original post.
Everything else, CD's/MP3s/DVDs etc. play fine, plenty of volume. The above prob. is PURELY music software specific!!
Yours in hope
ulrichburke
Can't make software obey MIDI instructions.
Posted on Sep 03, 2008 01:12 am
Chris Burke
Member Since: Sep 03, 2008
Dear Anyone.
This one's been killing me for years, literally, only just found this place, here goes.
Comp Specs. Asus m/brd, Sempron processor, 1gig RAM, M-Audio Audiophile 2496 Soundcard. Software: Garritan Personal Orchestra, Kontakt, Reason. New m/brd being saved up for, I know the above's only just fast enough.
I'm disabled. I have to use a notation package, Voyetra Music Maestro, and a mouse to write my music. So I link Voyetra to one of the packages (take your pic, this happens with ALL of them) with MIDI Yoke. Setup the sounds in the package. And they ALL come on at 127 EVERYTHING and stay there. It doesn't matter what I set volume/velocity to, the sound stays on absolute max.
Unless I set velocity to 0, then the sound goes off altogether. If I set it on 1, it's back on at 127. Volume can be on 0 all the time, the sound will still be playing on 127.
I can Import a MIDI file I've made into Reason, or any of the others, and I get the opposite prob - it's SO quiet you can hardly hear it. I'm shoving gain, maximisers, everything I can think of at it and you can only just hear it with the amplifiers on full blast. Yep, the sliders on the sound-card controls are on full.
Ideally, I'd LOVE to MIDI-Yoke Voyetra to a pack of decent sounds and just stick notes in with a mouse, hear what they sound like on playback (OBEYING MY MIDI NUMBERS!!) and add final mixing afterwards. ALL of these posh packages ASSUME you can't read music, which stunned me when I bought them (they're all legit.) I can't think in bar charts, I much prefer notes - and you don't get to hear the bars in Reason until AFTER you've put them all in anyway. (Garritan/Kontakt assume you're playing a keyboard, which I can't physically do.)
If anyone knows what the heck's up with all those programs and MIDI, you might well save my sanity!!
Yours in hope
Christopher Burke (ulrichburke on site).
P.S. I'm a wannabe New Age composer - piano and orchestra stuff - cringe now and get it over with!!
[ Back to Top ]
Sep 03, 2008 01:19 am Chris Burke/Ulrichburke again, I should have put this in the original post.
Everything else, CD's/MP3s/DVDs etc. play fine, plenty of volume. The above prob. is PURELY music software specific!!
Yours in hope
ulrichburke
Sep 03, 2008 05:52 pm Hrmmm, while I haven't used midi-yoke myself, it almost sounds like the midi signals are being mis-interpreted somehow. Kinda like either on or off. No gradients.
Could you give us some other details, like the settings/parameters in the software you're using, and what you're connecting via midi and midi-yoke? What notation package are you using?
At a glance, it almost seems to me like midi-yoke might be mis-translating something from the notation package to Voyetra. Anyhoo, some more info would help us get closer to what's actually going on. Hopefully someone who's used midi-yoke will chime in.
edit: since you said it happens with all of them, that's making me want to think there's a setting in midi-yoke that needs adjusting.
-J
Sep 03, 2008 06:25 pm I am not a midi yoke user, or even a recording engineer. I'm a live sound engineer. But, we do use midi as well.
Just read the midi yoke web site. There are plenty of warnings about how to connect to the midi yoke programme.
One thing to do, is to double check all connections. Verify that they are input to output. According to the web site, this is one of the biggest problems with midi yoke.
Another is to verify that all of your pieces follow the same midi protocol. Since there seems to be no standard.
Midi Yoke is the same as just a midi cable, that can feedback. (That was a fun little tid bit that they where throwing around!)If any of the connections are reversed, it can bring your computer to it's knees.
From your description, it sounds as if there are two protocols being observed. Or, the midi channel assignments are not properly assigned.
Sep 03, 2008 08:13 pm I guess I am curious why you are using midi yoke. Doesn't Voyetra have its own way to use VSTi or DXi?
If you are stuck using Voyetra you might take a look into some other programs out there that are capable of using the instruments either via ReWire or as a VSTi or DXi.
I used midi yoke a long time ago when forced to with a certain bit of software and I hated it. It was unstable and unpredictable as well.
But Rob is spot on about it being very picky about how it is connected to anything.
Sorry I am not much help on it.
But I am pretty sure that it is the communication between the two bits of software that is causing things to go astray.
Sep 03, 2008 11:20 pm If you can't track it down, would it be possible to do the same thing with hardware? Get a 2-in 2-out MIDI interface, use 1 set for regular MIDI stuff, and the second as a "yoke"-type interface.
My DAW doesn't automate gradual tempo changes, but Voyetra does, so I'm planning on doing this and setting the DAW as a MTC slave, with Voyetra handling the timing. I came up with this work-around before I know that MIDI Yoke existed, but still haven't actually tried it yet (lazy).
Sep 04, 2008 12:28 am i'm not sure i quite understand what a yoke is exactly....i'm dooin' research right now after this post.
but i'd guess it's a setting in your hardware midi interface (is this the yoke?) my keyboard can be set to a similar setting with all keys being any velocity i want. then there's a "real" setting which is velocity sensitive.
also what operating system are you using?
Sep 04, 2008 12:58 am WYD, Maybe you already know by now?
Here's my experience. After installing MIDI Yoke you have a number (8 or so I believe) of software MIDI device drivers. They act like the "real" thing. That opens the door to easily chain different MIDI programs.
e.g. A number of years ago I found a rather old drum sequencer program. It's small but does exactly what I want except... it can't export MIDI files because it's an evaluation version. Since it's is no longer supported there is no way I can get this to work.
That's were I use MIDI Yoke. The drum sequencer's MIDI Out is routed to the MIDI Yoke 1 driver and in my regular MIDI sequencer software I change the MIDI In to that driver too. Next step is to start recording in the regular sequencer and then start the drum sequencer. When it's through playing I stop the regular sequencer and voila... I have the drum MIDI ready in my sequencer for editing, playing and saving.
I'm using MIDI Yoke for 3-4 years now and never had a problem except for routing mistakes which can force you into a reboot.
BTW I don't think it will work in Vista.
Sep 04, 2008 01:06 am hmmm ok, i get the yoke now...
then what kind of control surface are ya using? my guess is this where the velocity problems is happening.
Sep 04, 2008 01:51 am I'm not using a control surface, so I wouldn't know if that's the cause of the problem. The end of my Yoke chain is my default sequencing software, which always outputs to a keyboard.
Sep 04, 2008 06:59 pm WYD, the Chris Burkes problem is that his sequanced midi parts from Voyetra are not using any volume control or velocity that is already written into the sequenced parts he has. It is all at max level no matter what he does.
I'm still researching a little bit on it, hopefully I will find something that could be the cause. But it is looking more and more like something is playing nice in the way Midi Yoke is routing or passing the data.
|
Related Forum Topics: |
If you would like to participate in the forum discussions, feel free to register for your free membership.