2
0.60.9 25 Oct 2011 Maintenance release, fanning linear potentiometers
4
Reworked the envelope to have a linear attack and with gentler control of the
5
decay/release times. The linear attack was a Moog thing but was not universally
6
appreciated - it does not work very well for long attack times. Several synths
7
such as the Synthi preferred the use of exponential for this and other reasons.
8
The actual envelope code does not have linear or exponential attack as a fixed
9
value, it can be configured by the emulator although at the moment they all just
10
take the default setting, now linear. There is a ./configure option to have them
11
default to exponential rather than linear: --enable-exp-attack
13
It is now also possible to build with an alternative ADSR max ramp duration,
14
the following will give you a maximum ramp of 30 seconds, default is 10.
15
./configure BRISTOL_RAMP_RATE=30
16
These changes were to correct an anomaly in the previous design where the
17
actual ramp was a function of the sampling rate, hence if you step up to 96KHz
18
or even 192KHz for the improved sound quality then the ramp times would change
19
(now fixed). If you want to use very long attack times then exponential attack
20
will give arguably better results, that is admittedly opinion.
22
NOTE that these envelope changes will affect existing patches to some extent.
24
Added code to have fanning linear pots. The further the mouse is from the axis
25
of the pot the finer the value changes become.
27
Resolved a error in midinote.c that broke the scala file support. A patch was
28
posted to SFDN a long while ago now, this just rolls it into a release.
30
MIDI Program Change events were not being filtered by channel - they were being
31
tracked as OMNI. Applied same change to Bank Select. Have not tested all the
32
multilayered synths, they have exceptions since some use separate memory
33
indeces and some use combined settings.
35
Reconfiguring the continuous controllers as things like inverse mappings were
36
failing. The issue was that both the engine and GUI might be using the same
37
mapping file, dual inversion negated the effect. Corrected this with only doing
38
the mapping in the GUI but added a token called modWheel for the 'mcm' file to
39
allow the engine to have alternative curves for the modulation wheel.
41
The request to have an inverted modWheel requires the following: Start the
42
engine with -tracking to prevent the GUI tracking some events. Edit mini.mcm
48
This file is emulator global, ie, to have different settings with the same
49
synth then a user would have to configure different bristol cache variables.
50
A better way to do this might be to have an ALSA event manager in front of the
53
Ported over some note loss fixes from the 0.70 (smartphone) stream where with
54
excessive system load there were lost notes. This was never actually reproduced
55
on Linux so will discuss the fix with end users. The original change resolved
56
the issue when seen on a 600MHz ARM A8 on Maemo/N900 from Nokia and which were
57
also tested/confirmed on Android. It concerned signalling between the note
58
allocation code and the ADSR envelope states.
60
The multilayered synths would lose tracking of the PitchWheel - the pitch was
61
correctly calculated but only applied to the first bristolAudio structure in
64
The Polysix gives click/tick at high frequencies and mods. The cause was the
65
change from the precached buffers to recalculated buffers. The code was changed
66
to have the buffers always calculated/cached on note events as a fix to the
67
existing band limited oscillator code. The code change was only the prophetdco
68
but it could be pushed into the other oscillators.
70
The BME noise mix was all but silent, readjusted the gain settings for the mix.
72
The Pro1 and Prophet10 saved sequencer memory was not reloaded on restart. Had
73
to apply changes to a few different parts of the arpeggiator/sequencer code.
75
Gain levels seemed low on the ARP 2600 and the Direct Out final stage gain left
76
a signal that was almost inaudible.
78
Added the option to use a memory barrier over the jack ringbuffer. The issue
79
is that the JRB can be demonstrated to fail on ARM CPU due to them having weak
80
memory ordering. Intel should not be affected. AMD is a marginal case. The
81
config option is --enable-memory-barrier which defaults to no barrier since
82
most of the installs will probably be on Intel.
2
84
0.60.8 23 Dec 2010 Maintenance release, Hammond optimisations.
4
86
Made some changes to the way bristolrc is handled. If the file exists then a
added
removed
ChangeLog
