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

Triple oscillator not working from rc2.9. #3292

Closed
bieltoni opened this issue Jan 24, 2017 · 11 comments
Closed

Triple oscillator not working from rc2.9. #3292

bieltoni opened this issue Jan 24, 2017 · 11 comments

Comments

@bieltoni
Copy link

bieltoni commented Jan 24, 2017

When a track with a tripleoscillator is played, a sound distorsion occurs. I have compiled different versions of lmms to determine from which the problem occurs and the rc2.8 version works correctly. From the version rc2.9 the tripleoscilator stops working correctly.

Debian 8 x64 with KXStudio repositories.

@bieltoni bieltoni changed the title Triple oscilator not working from rc2.9. Triple oscillator not working from rc2.9. Jan 24, 2017
@bieltoni
Copy link
Author

The problem occurs when you play the Triple Oscillator within the song editor. It seems as if buffers information gets corrupted.

@BaraMGB
Copy link
Contributor

BaraMGB commented Jan 26, 2017

Can you provide a video, please?

@BaraMGB
Copy link
Contributor

BaraMGB commented Jan 27, 2017

Theres definitely something wrong. I can reproduce it when TripleOSC playes with kicker together and TripleOSC has a OSC with sawwave. Then the sound stops and the peak of 3OSC goes to max.

I guess it's something with: #3145

@michaelgregorius
Copy link
Contributor

@BaraMGB Can you provide a small project that can be used to reproduce the problem? Thanks!

@musikBear
Copy link

What OS are this relevant for?
I have tested RC2.8 on win32
I cant reproduce this bug, No matter what saw-osc (1-3) or wheater or not the kicker is in B&B or song-editor, there is no loss of either 3oc or kicker notes over 3 octaves

If any track is muted in the problem project then, Couldent this be the 'silenced B&B-track' bug?

File: https://lmms.io/lsp/?action=show&file=10214

@bieltoni
Copy link
Author

@BaraMGB Here is another test file.
https://lmms.io/lsp/?action=show&file=10220

A video where it works correctly
https://youtu.be/n_rDyxVusBQ

And a video with the latest version of LMMS with the bug. I hope it helps.
My system is a Debian 8 64bit.
https://youtu.be/Ch8JZ4uMCRY

@michaelgregorius
Copy link
Contributor

michaelgregorius commented Jan 29, 2017

I have tested with https://lmms.io/lsp/?action=show&file=10220 and also with "Surrender-Main" from the "shorties" files and here are some more findings:

  • The bug seems to be more likely to occur in release builds.
  • The bug seems to be only triggered when at least two instruments go into one FX mixer channel.
  • Related to the previous observation: If you solo a problematic channel the problem goes away but comes back if you unsolo the channel. If you route each instrument into its own channel the problem goes away.

michaelgregorius added a commit that referenced this issue Feb 4, 2017
…ync") (#3145)"

This reverts commit e3e14bb in an
attempt to fix issue #3292.

The problem that's addressed is very elusive:
* It cannot be reproduced reliably.
* It seems to be more prone to appear in release builds.
* It only seems to appear when two or more instruments are mixed into
  one channel.
* If you solo a problematic Triple Osc it goes away.

The observations above seem to indicate that there's rather a problem
with the mixing (due to multithreading?) and that the changes made to
Triple Osc seem to trigger this deeper problem more quickly.
@michaelgregorius
Copy link
Contributor

I have reverted the changes from #3145 with commit cf26da3. However, due to the symptoms described above I think it's rather a problem with the mixing and multithreading. The fact that soloing a Triple Oscillator makes the problem go away and yields correct sound also seems to indicate that there is nothing wrong with the computation of the audio and the update of the phase information. But as we are in an RC phase right now I guess it's better to revert the changes.

@bieltoni Can you please check if the bug is solved once there is a newer RC available? Please only close this ticket if you find that it's solved. Thanks!

@BaraMGB
Copy link
Contributor

BaraMGB commented Feb 12, 2017

For me the issue seems fixed.

@musikBear
Copy link

It would be a big setback, if the off-phase behaviour is re-instated.
The post 3145 3oc (as in RC2.8) is a significantly better instrument -

@bieltoni
Copy link
Author

bieltoni commented Feb 13, 2017

@michaelgregorius I have check in a new system (build in Debian 9 without KXStudio sources) and the last git version, works perfect.

sdasda7777 pushed a commit to sdasda7777/lmms that referenced this issue Jun 28, 2022
…ync") (LMMS#3145)"

This reverts commit 291942f in an
attempt to fix issue LMMS#3292.

The problem that's addressed is very elusive:
* It cannot be reproduced reliably.
* It seems to be more prone to appear in release builds.
* It only seems to appear when two or more instruments are mixed into
  one channel.
* If you solo a problematic Triple Osc it goes away.

The observations above seem to indicate that there's rather a problem
with the mixing (due to multithreading?) and that the changes made to
Triple Osc seem to trigger this deeper problem more quickly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants