|
|
Developer
Posts: 746
  
Location: England | Hi everyone,
I'm pleased to present you with reViSiT 1.3.2 Pro, which includes a number of fixes and small tweaks, most notably towards improved external MIDI timing. There'd been elusive issues with this for some time now, but a flash of inspiration has allowed me to significantly increase the precision of live and recorded MIDI events sent to external drivers (e.g. LoopBe1, hardware interfaces). A number of other minor refinements are also included in this release (see below). Download reViSiT v1.3.2 Pro from http://www.nashnet.co.uk/experiment/download.asp.
(not registered? Register for free, as part of the reViSiT Experiment) Enjoy!
Chris --------------------------------------------------------
v1.3.2
[MOD] Improved External MIDI timing precision.
[MOD] Clicking selections without dragging now deselects.
[MOD] New reViSiT logo on toolbar (links to website).
[FIX] MIDI Delay not working for External MIDI.
[FIX] Shift- not triggering hanging notes.
[FIX] Interpolate not working with maximum values.
[FIX] Drag outline extends one row too far. |
|
| |
|
Expert
Posts: 512
Location: Netherlands | I have a problem, but I don't know what it is - yet.
After a while (minutes) LoopBe stops receiving anything that goes out from reViSiT via those LoopBe ports. Can you check whether there's any chance you've broken something there? :P |
|
| |
|
Expert
Posts: 512
Location: Netherlands | Demons found!
Your shut-up routine (a.k.a. F8) scares the feeble bits out of LoopBe. LoopBe doesn't report anything special though (so it's not a feedback loop or something). |
|
| |
|
Developer
Posts: 746
Location: England | Are these two posts about the same issue?
It's possible Windows is running out of timers - the new timing mechanism solves some problems by using multiple timers, but the number is limited in Windows. |
|
| |
|
Expert
Posts: 512
Location: Netherlands | It was the same issue yes.
So.. the solution will be? :P |
|
| |
|
Developer
Posts: 746
Location: England | I'll have to look at a way of reducing the number of timers, if I confirm it to be that. reViSiT uses one timer per audio buffer, but releases the timer as soon as all the scheduled MIDI events are dispatched. So, should that be where the problem is, you might be able to workaround it by increasing your ASIO buffer / latency.
Let me know if that makes any difference.
Best,
Chris |
|
| |
|
Expert
Posts: 512
Location: Netherlands | Quick, before the Mayan calendar runs out:
Run a velocity sensitive VSTi, input notes in the rev.Pattern, every so many notes the note auditioning velocity is lower than others. |
|
| |
|
Developer
Posts: 746
Location: England | Maarten, I've looked into the velocity issue you mentioned, using MIDI monitor to see what velocities a VSTi is receiving and everything looks fine. The same velocity is maintained each time. Could it be something to do with how you're using MIDI channel volume? |
|
| |
|
Expert
Posts: 512
Location: Netherlands | Try inputting the same note all over again. Like a whole column o' C4's or so. |
|
| |
|
Expert
Posts: 512
Location: Netherlands | I've proof on video :D Will try to find a small videoformat in order to send it. |
|
| |
|
Expert
Posts: 512
Location: Netherlands | A side note: I acquired a netbook today (practical for college). I'll prolly put part of my music shebang on it as well. While I don't expect much oddness in terms of revisit, I'll try to run things on it now and then. |
|
| |
reViSiT v1.3.2 Pro update available
