Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global Tempo Automation Failing with VSTs #5319

Closed
OutbackMan opened this issue Nov 12, 2019 · 3 comments
Closed

Global Tempo Automation Failing with VSTs #5319

OutbackMan opened this issue Nov 12, 2019 · 3 comments

Comments

@OutbackMan
Copy link

OutbackMan commented Nov 12, 2019

Bug Summary

Creating a global tempo automation track causes silence and intermittent sounds to be played for VSTs.
Based off discussion from: LMMS Forum Support

Steps to reproduce

  1. Download a VST, e.g. Spitefire LABS VSTs
  2. Insert a series of notes using the piano roll with this VST. It is easier to hear the effects of the tempo automation if using short repeated notes, e.g 16th notes, however any note length will work.
  3. Create a global tempo automation track whose line follows that of a 'mountain', e.g. a curve that goes up and down.

Expected behavior

The tempo of the notes played slowly increases until time reaches the maximum point of the automation curve at which the tempo of the notes slowly decreases. The tempo of the notes played steadies when the automation curve is a flat line.

Actual behavior

The tempo of the notes played slowly increases until time reaches the maximum point of the automation curve at which silence is mostly heard, with intermittent notes played. The tempo of the notes played steadies when the automation curve is a flat line.

Screenshot

JJKs8cd

LMMS version used

Windows x64 1.2.1

@OutbackMan OutbackMan added the bug label Nov 12, 2019
@OutbackMan OutbackMan changed the title Tempo Automation Failing with VSTs Global Tempo Automation Failing with VSTs Nov 13, 2019
@PhysSong
Copy link
Member

Possibly related: #3775

@Spekular
Copy link
Member

There's also #5122 and #3640.

@DomClark
Copy link
Member

Reproduced. I'm fairly sure this is a duplicate of #5122. I intend to fix that issue soon, and will reopen this issue if that doesn't fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants