|
|
Member
Posts: 11
| Hello all,
I am using reViSiT to trigger VST instruments, and the midi signals seem to be out of sync.
this is what I did :
Midi channel 1 : VSTi triggered by midi
Midi channel 2 : same VSTi triggered by reViSiT (with same pattern) through LoopBe1.
result :
Strangely enough the midi signals sent by reViSiT (channel 2) occur before the midi signals sent by the host (channel 1)... I would like to set a delay only on the midi signals coming from reViSiT. I tried to play with the settings of LoopBe1 and of ReViSiT but with no success. Can you help me with this?
Thanks
Edited by gewfz 2009-11-14 12:14 PM
|
|
| |
|
Expert
Posts: 512
Location: Netherlands | Odd, the only thing I'm experiencing with LoopBe (the full registered version that is) is that I'll have to export in real-time mode as the non-real-time mode gives me timing errors on anything going through LoopBe. |
|
| |
|
Member
Posts: 11
| Hello CS TBL
I just tried with another virtual midi cable (mapple) and I had the same problem. I am using ableton live as host for revisit, maybe there is an issue with ableton a virtual midi ports? |
|
| |
|
Expert
Posts: 512
Location: Netherlands | I dunno, do you see a chance to -even if it's temporarily- test this midi thing with Cubase SX3? That's one DAW which works flawlessly with reViSiT. |
|
| |
|
Member
Posts: 11
| I've been making some investigations, and here are some observations I made :
- Ableton (7) has a "Device Delay Compensation" which is supposed to compensate the latency of the midi outputs from VST instruments.
- when the "Device Delay Compensation" is switched off, the user is not able to make any delay compensation on any channel, and the VST signals are slightly delayed.
- when switched on, the "Device Delay Compensation" applies to both reViSiT AND the VST Instrument it triggers. As a consequence, the midi output is compensated twice! (That's why the sound is played in advance). Unfortunately, the delay compensations that is used for the midi channels are linked to the notes edited in the host (and not in reViSiT)...
Now I have to figure out a way to bypass the "Device Delay Compensation" on the channel where I put reViSiT....
But : In the F12 options, there's an option called "Midi Delay". I tried to play with it, but it had no effect on the delay of the VST... What is this option? |
|
| |
|
Developer
Posts: 746
 
Location: England | Hi gewfz,
I'll try to have a look at what Live is up to, concerning reViSiT and MIDI. Since reViSiT is also able to generate audio, for its own instruments, the MIDI Delay option in F12 is there in case the MIDI triggered instruments are out-of-sync with the audio instruments. Indeed, it sounds like it might be useful in your case - I don't know why it's not having an apparent effect, so I'll look into that too.
Two things to try to workaround / reduce the problem:
1) You might be able to add a MIDI Delay effect after reViSiT and before your VSTi. I don't know how Live works in this regard, but Cubase has a small collection of MIDI effects for such scenarios.
2) Try reducing your ASIO buffer size. The delay you're experiencing will be as long as the latency, so if you can drag it to within a few milliseconds, it might become less noticeable.
'Hope this helps,
Chris |
|
| |
|
Member
Posts: 11
| Hello Chris, thanks for your reply
The MIDI delay option in F12 seem to be exactly what I am looking for (but has no effect indeed). I tried to use both MIDI and audio in reViSiT, and indeed MIDI was out of sync (MIDI before audio) : maybe the delay option works only when audio signal is before MIDI signal?
I will try your other solutions. I'll let you know if this works on ableton.
Cheers |
|
| |
Midi signals sent by reViSiT not in sync
