[yoshimi-user] Contollers bug
- From: Will Godfrey <willgodfrey@xxxxxxxxxxxxxxx>
- To: yoshimi-user@xxxxxxxxxxxxxxxxxxxxx
- Date: Sun, 15 Jun 2014 10:59:52 +0100
On Sun, 15 Jun 2014 02:09:06 +0000
Jonathan E Brickman <jeb@xxxxxxxxxxxxxxxx> wrote:
I don't actually do much with routing at this time, so I don't want to claim
to test effectively, but I did find one additional. I tried clicking the
"Controllers" button on the default window, and it caused Yoshimi to eat most
of the CPU and cause xruns untill killed. What does this button do? I made
sure (on the second try) that I had a MIDI input/controller device running
and connected via Jack.
Unfortunately you've hit on a *very* obscure bug I've been trying to track down
for a while. I kept quiet because nobody else had seemed to have hit it.
The controllers window enables/disables and sets the various controllers for
each individual part, and this bug *only* affects the window for the first part
(part 1).
What makes this stranger is that it also depends on the size of Yoshimi's
config file. I have a saved file here that repeatably causes this bug to
surface, and another file that never does.
All of this suggests it's some kind of buffer overrun situation.
This bug does not appear in V 1.0 but does appear in V 1.1, and tracing back
through the master branch it first appears at the time multiple part output was
introduced. I don't know if that was the cause, or if it simply exposed a
hitherto dormant problem.
This is why I was trying to contact Andrew Deryabin.
He provided the patch, so I was hoping he could shed some light on the issue.
It is also what particularly pushed me into trying to get a far more detailed
understanding of C++.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Other related posts:
- » [yoshimi-user] Contollers bug - Will Godfrey