Jump to content

Xoo

Members
  • Posts

    4,313
  • Joined

  • Last visited

Posts posted by Xoo

  1. On 4/28/2024 at 12:08 AM, msmcleod said:

    MIDI latency was an issue that gave me grief for years, until I worked out what was going on.

    In Preferences->Project->Clock, you can choose your clock source.  It defaults to Audio, which is by far the most accurate and reliable.

    The only issue is, you need the audio engine to be running for this to work.  If you've a MIDI only project (like I used when I used racks of MIDI synth modules), then this isn't going to work unless you have audio or a soft-synth in your project.  If you don't, then the timer essentially isn't running, and MIDI timing is all over the place.

    If you're recording only MIDI, you could set the clock to "Internal" - this will work for MIDI only projects, but its accuracy can then depend on whether the high-resolution timer is enabled both on your motherboard and in Windows, and how well they play together.  Sometimes enabling the high-resolution timer can make things better, sometimes worse, and in many cases can cause a whole bunch of other system instabilities/blue screens if its set wrong.... best not to play with it. Really.   Feel free to try the "Internal" clock setting - if it works right away, great - but don't mess around with high-res-timer stuff unless you really know what you're doing and know how to revert it.



    By far the easiest solution is to leave it set to Audio, then insert a soft synth or an audio track with a silent clip, and do this before you start recording any MIDI. 

     

    Audio metronome enabled?

  2. 7 minutes ago, pwal³ said:

    no it was at a regular discotheque we did, it included optikinetics oil wheels, and a set of strobes that we would spin around the room and make people fall over... also far too much smoke machine smoke haha

    We used loads of the Optikinetics - amazing things :-)

    • Like 1
×
×
  • Create New...