13,420
edits
Changes
no edit summary
Murray
<span style="color:blue">Hi Murray,<br /><br />To get a good overdriven hammond sound you would get the best results by piping bristol through a valve amp emulator: guitarix, rackarack, caps all spring to mind, you should be able to connect them up to jack and then route the organ through them. Bristol has a distortion control but it sounds ripped rather than a
typically creamy overdriven tube sound.<br /><br />You will probably get results off the 'bright' control. There was also another gearbox I once defined that was very 'dirty' - the engine allows you to redefine things like each toothwheel shape, the amount of crosstalk in the comparments and everything. I was thinking of resurrecting the gearbox definition though and posting it on the website for those who did want the more grungy sound. I quite liked the result - the lower harmonics had a real hollow tone due to flattening out the teeth to be more like the original hammond design but without the shaping filters.<br /><br />Will let you know if I find it.<br /><br />The request to have a pulldown menubox will have to be pushed out, the GUI cannot do this very easily. It can be done: the memories have fields for patch names and author names but I do not fill them in. Perhaps it is something that could go into one of the bristol management apps like monoBristol?<br /><br />Regards, nick. </span>
Murray
<span style="color:blue">Hi Murray,<br /><br />This is correct, when the Jack MIDI interface became more widely tested and stable (my part, not necessarily Jacks part as that probably already was stable) then I correct my default settings:<br /><br />-alsa give you ALSA audio and MIDI<br />-jack gives you Jack audio and MIDI<br />-oss gives you OSS audio and MIDI<br /><br />Having Jack with this exception was only a temporary solution. The options you now give are correct. There are a few things you can do here to make life easier for you: create a file ${HOME}/.bristol/bristolrc and add one line as follows:<br /><br />-jack -midi seq<br /><br />This will be used as default switches every time you start bristol, now you don't have to type them in every time. There will be some changes to this in 0.60.8 to give some more flexibility but this method will still work. All the changes will be documented in the ChangeLog.<br /><br />Additionally, attached are some new gearbox files, there are two of them. One is the original 0.30 release which is very grungy - I still think you would need something like rackarack to give you a valve overdrive and speaker cab emulation to get a decent Steve Winwood sound though. The second one is a very clean gearbox - smoother waves and less crosstalk. You might find this works well with external effects processing, I quite like it, the sound is a lot sweeter.<br /><br />Take this file and put it in ${HOME}/.bristol/memory/profiles/tonewheel and then start bristol. You can load them dynamically but they are really intended for startup. If you don't like them then just delete this copy and you will get the 0.60 default gearbox back. You may have to create the 'profiles' directory but I should do that for you whenever you save a memory.<br /><br />Kind regards, nick.</span>
Murray
<span style="color:blue">Hi Murray,<br /><br />A quick question, I will give this some more thought later but am kind of wrapped up in family stuff at this time of year. Many seasonal greetings to you and yours.<br /><br />Can you start bristol as follows, then send me the output along with your config.log?<br /><br />startBristol -b3 -channel 4 -gain 3 -jack -midi seq -debug 1<br /><br />You can find your config.log in the directory where you did the ./configure<br /><br />Kind regards, nick</span>
Murray
<span style="color:blue">Hi Murray,<br /><br />So I would not put the clicks down to memory, much more likely to be CPU load or potentially digital overload, ie, exceeding the resolution of the 16bit audio sample space. Lets see:<br /><br />CPU load: The -lwf option will have no effect here, these are filter banks for the synths only, I don't use them on the organs. Now I am not sure why the organ should suffer from this, the algorithm (there are two discussed below) is that when you press a single key I run all 92 tonewheels - that is a fat piece of CPU activity. After that taking single keys is actually very efficient. In short, if you can do one voice then you already have the gearbox running and should have pretty unlimited polyphony. Now there are two algorithms I use, one is the above, I call it the Jimmy Smith gearbox - it does emulate all the wheels but uses a big pretty constant lump of CPU. The other is to just use dynamic voice allocation and have each voice generate just the tones it needs. This will have a CPU profile that really does depend on the number of keys. You can select between the two algorithms from the 'Preacher' button in the Opts window.<br /><br />What kind of CPU profile do you see? With one key pressed I get about 25% load on my company laptop but 100% (over)load on my N900 phone with the Preacher enabled but on the laptop the load does not change much if I press a whole load of keys. Without the preacher I get a few percent per voice but that does change a lot as I press more keys.<br /><br />You mention an RT kernel: I take it you have cpu speedstepping disabled? That also causes this kind of problem but I know people normally disable this as a normal part of turning the PC into a realtime audio system.<br /><br />If this is digital overdrive then you can lower the digital gain on the B3 Volume control and increase the offboard gain on your amp however you should be able to hear this by just having a strong signal from the B3 emulator. I do check for this situation as well, ie, if the internal floating point numbers exceed +/-32K I limit the signal level and occasionally display 'Clipping' messages.<br /><br />Kind regards, nick.</span>