Sequencer bpm issue with keyboard

Forums Forums Qu Forums Qu troubleshooting Sequencer bpm issue with keyboard

This topic contains 26 replies, has 5 voices, and was last updated by Profile photo of janw janw 5 years, 4 months ago.

Viewing 12 posts - 16 through 27 (of 27 total)
  • Author
    Posts
  • #55498
    Profile photo of MarkPAman
    MarkPAman
    Participant

    Ah delays….. maybe not tempo changes?

    Maybe You’ve set the desk up with the keys feeding through an inserted effects unit, which could introduce a delay. Or you can add a small, <85ms, delay at the input of each channel, so check that too.

    #55518
    Profile photo of Zecure
    Zecure
    Participant

    Just to confirm. He meant tempo changes not delays.

    #55522
    Profile photo of [XAP]Bob
    [XAP]Bob
    Participant

    The QU can’t produce tempo changes – it doesn’t have enough memory to do the serious buffering required.

    Changes in delay are generally accompanied by digital clicks since the QU has to throw away or insert samples to move from one delay period to another.

    A recording of this would be appreciated.

    I’d also suggest trying it again with a fully reset desk, and plugging into two channels on different PCBs – cahnnel 1 & 10 maybe…

    #55523
    Profile photo of DavidCo
    DavidCo
    Participant

    I’d just like to reiterate my original point that it is *impossible* for the Qu to control BPM via an audio signal going the other way. Qu doesn’t even generate a MIDI timing clock (0xF8) which would be responsible for mastering a BPM. I don’t see how you came to such solid conclusions based upon circumstance alone. I suggest you make the recordings as requested above, and clearly explain what the symptom is that is apparent in the recording.

    DC

    #55580
    Profile photo of janw
    janw
    Participant

    Below is a link to a sequence recording without A&H but just connected to an active speaker.
    The lights on the iPad (app=”tempo”) indicate the bpm=126 ; as you can see perfectly in sync, no issues at all.
    [video src="https://dl.dropboxusercontent.com/u/5518126/Sequence.mp4" /]
    Later this week we’ll do a recording on the A&H to compare the difference.

    #55583
    Profile photo of DavidCo
    DavidCo
    Participant

    Okay, so is the sequencer an app running on the iPad? If so, it could be possible that another process (such as QuPad) is taking a share of the CPU resource, and the sequencer app isn’t written in a way that compensates for sharing that CPU resource, and instead accumulates a time error?

    DC

    #55585
    Profile photo of janw
    janw
    Participant

    The sequence is run on the synth = Korg M50 which is connected to the active speaker through a DI box (radial)
    There is NO link with the ipad ; the latter is just used as a convenient way to measure & show BPM

    #55590
    Profile photo of DavidCo
    DavidCo
    Participant

    Okay, in which case my above theory isn’t relevant. I await the next video.

    DC

    #55603
    Profile photo of janw
    janw
    Participant

    thank you very much. I really appreciate you want to help looking into this.
    We will do the tests on our QU-24 this Wednesday
    Below is a live recording of our last gig where we also used A&H equipment (but not ours). I referred to it in my initial explication. As you can hear, there is no tempo change/delay whatever so my conviction is it has to do with the settings on our A&H

    #55630
    Profile photo of DavidCo
    DavidCo
    Participant

    So the above video is connected to an A&H desk and there was no BPM change, and wasn’t supposed to be one?

    DC

    #55632
    Profile photo of janw
    janw
    Participant

    that’s correct, the above is a connection to an A&H (not ours but the one of the organizer of the event) that shows that there are no BPM changes introduced by the synth

    #55711
    Profile photo of janw
    janw
    Participant

    We tried to record the problem yesterday but believe it or not : we were not able to reproduce it…
    What did we change ?
    Nothing…expect for a USB stick we formatted on the QU-24 and kept in the system for a while. But even if we detached it from the QU we could not reproduce the problem anymore. This might sound “good” but we feel very unsecure as that it might pop up again just like that during our next GIG. I will keep trying to reproduce/record it.

Viewing 12 posts - 16 through 27 (of 27 total)

You must be logged in to reply to this topic.