Please backport Bristol | current version on karmic (9.10) is bristol_0.40.1-0.1 | version required bristol_0.40.6-1 available on lucid.

Bug #502035 reported by salvoinzk
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Karmic Backports
Invalid
Undecided
Unassigned

Bug Description

Please backport Bristol

current version on karmic (9.10) is bristol_0.40.1-0.1

version required bristol_0.40.6-1 available on lucid, (not available on karmic-updates)

of course "bristol-data_0.40.6-1 package" needed, too, for the dependance.

Thanks in advances!

salvoinzk (salvoinz)
summary: Please backport Bristol | current version on karmic (9.10) is
bristol_0.40.1-0.1 | version required bristol_0.40.6-1 available on
- lucid, (not available on karmic-updates) | of course "bristol-
- data_0.40.6-1 package" needed, too, for the dependance. Thanks in
- advances!
+ lucid.
Revision history for this message
Ilya Barygin (randomaction) wrote :

0.40.6-1 builds with no changes. Package is available in my PPA: https://launchpad.net/~randomaction/+archive/ppa, please test and give feedback here.

Revision history for this message
salvoinzk (salvoinz) wrote :
Download full text (13.5 KiB)

Hi Ilya,

Thank you very much!
Now it works!!!

I have installed both package :

"bristol-data_0.40.6-1~karmic1~ppa1_all.deb" and "bristol_0.40.6-1~karmic1~ppa1_amd64.deb".

Well here is some report:

when you start bristol alone, you have to type: startBristol -b3 ( -b3 is for the hammond b3 of course you know) and it goes, here is the output:

salvo@piera-laptop:~$ startBristol -b3
checking availability of TCP port 5028
using port 5028
generate bandwidth limited waveforms(31, 12)
spawning midi thread
could not reschedule thread
parent going into idle loop
Init waiting for midi thread OK status
Fixing samplerate at 44100
midi sequencer: bristol
Opened listening control socket: 5028
midiOpen: 5028(100)
Client ID = 129
Queue ID = 0
Registered 129 0
Device name "bristol" did not parse, defaults 128.0
Got midi thread OK status
bristol version 0.40.6
connected to :0.0
display is 1366 by 768 pixels
Window is w 1366, h 768, d 24, 0 0 0
Using DirectColor display
Initialise the hammondB3 link to bristol: 20b5f60
hostname is localhost, bristol
TCP port: 5028
Accepted connection from 0 (3) onto 2 (5)
Connected to the bristol control socket: 4
bristolengine already active
created 32 voices: allocated 32 to synth
        sid is 0
spawning audio thread
could not reschedule thread
init waiting for audio thread OK status
bristolAudioOpen(plughw:0,0, 44100, 256, 1a00008)
audioOpen(b09740c0, 0, 1024): plughw:0,0
opening device plughw:0,0, flags 0000000d
open playback on plughw:0,0, pre 8
Plug PCM: Hardware PCM card 0 'HDA NVidia' device 0 subdevice 0
Its setup is:
  stream : PLAYBACK
  access : RW_INTERLEAVED
  format : S16_LE
  subformat : STD
  channels : 2
  rate : 44100
  exact rate : 44100 (44100/1)
  msbits : 16
  buffer_size : 2048
  period_size : 256
  period_time : 5804
  tstamp_mode : NONE
  period_step : 1
  avail_min : 256
  period_event : 0 ...

Revision history for this message
salvoinzk (salvoinz) wrote :

If you want to use bristol with Ardour, for example, you should follow these steps:

1) launch jack
2) start Ardour
3) now start jack
4) open a shell and type: startBristol -jack -b3 (I mean you have to specify the jack driver, -b3 is always for hammon b3)
5) make the connection with jack and play.

Changed in karmic-backports:
status: New → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

karmic is no longer supported and receives no further updates

Changed in karmic-backports:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.