13,420
edits
Changes
no edit summary
<span style="color:blue">Hi Murray Saul,<br /><br />The cause of the processes getting terminated is probably Jack complaining about CPU utilisation. Some of these synths ran to 10% CPU per voice, that is on my Xeon 2.2GHz machine. When Jack cannot keep up due to process load then it terminates processes. Somewhere in the 0.50 stream I finally got around to filter optimisation and the results were what I was after, the CPU utilisation per voice comes down to below 2% on the same CPU: it has been tested with a 32 voice Prophet-5 running as a Unison synth, 64 oscillator all running together slightly detuned, it took 65% CPU to do it admittedly.<br /><br />Bristol does not raise any limit on what you do. You can run 7 different bristol emulators over Jack (use the -audiodev option to separate them) or if you use the -engine feature then you can run 7 emulators on the same bristol engine. The difference is a bit like having lots of synths or having one multitimbral synth with 32 voices. Bristol supports both methods of use, the default is multiple synths rather than a multitimbral synth.<br /><br />Now how far that will get you depends a little on what you want to do. If you want 7 synths running at the same time then typically each synth engine will get 32 voices, depending on your Jack version then all of the synths may have to run on a single core so if you stay within a limit of, say, 48 voices total it will work. Check out JackDMP/Jack2, whatever it is called these days for distributed processing where you can get multiples of the 48 voices as Jack will use multiple CPU cores.<br /><br />I am pretty certain you will get better results if you go for 0.60.5, the most recent release. I would be interested in seeing an example shell script for how you start all of these, it would show which method you are using and I could also give some feedback on other options you could use.<br /><br />Kind regards, nick.</span>
Hi Nick,
Attached is a rough shell script showing launching of bristol apps. You asked me to send a shell script so you can look at it...
Also 2 other questions:
1. Is there a way to place different organs on different locations on screen?
(I tried -geometry +#+#, but didn't work - I'm using 0.4)
2. Are there keyboard commands as shortcut to control the parameters of the organs?
Thanks,
Murray Saul
<span style="color:blue">Hi Murray Saul,<br /><br />I will have a look at the script presently, bit bogged down in work at the moment.<br /><br />1. Currently there is no way to get the -geometry to work so window position is still dependent on what your window manager wants to do. Now I was avoiding the use of -geom because of issues with 'WxH' since the windows actually want to impose their own aspect ratio on the window. If you want to see the issue try the following:<br /><br />startBristol -mini -ar<br /><br />Then change the size of the window - make it really wide. It works but it eventually doesn't look right. So, if I honour WxH+X+Y then aspect ratio will almost always be broken. Having said that I am quite interested in just +X+Y as an option and will look into how easily that can be integrated for you.<br /><br />2. There are not a great deal of keyboard shortcuts to the GUI - are you looking to change parameters? If you place the mouse over a drawbar and press <Shift><Up> it will move the control but the only other keyboard control was to play the synth.<br /><br />This is actually another pretty cool idea of yours though. At the moment if you put the mouse over a potmeter or slider and press the middle mouse button, then move a control on your midi surface it will link them together. That could be done,
theoretically, for the ASCII keyboard. If you don't want to play the synth from your QWERTY then <middlemouse><ASCII KEY> could also map to the control such that the key is down and <Shift><Key> is up?<br /><br />Now as an alternative, try using the -cli option. This opens a CLI for the synth but it only works for one synth per command line window. It does have key
mappings for controller movement though.<br /><br />kind regards nick.</span>
<span style="color:blue">Hi Murray Saul,<br /><br />The next release will include a -geom/-geometry option which will allow you to do window placement. The following should be honoured:<br /><br />-geom +100+100 will do just window placement<br />-geom 800+100+100 will scale the width to 800 pixels, adjust height to maintain aspect ratio and place the window<br />-geom 800x200+100+100 will take the literal size you request and place it on the screen, aspect ratio is lost.<br /><br />The interface will also configure antialiasing if the window size changes by more than about 10% from default.<br /><br />kind regards. Nice feature by the way, am glad your requested it as I had never considered the option and it seems pretty useful.<br /><br />nick.</span>
