LMMS gubi dźwięk, Bristol nie działa


(kijek) #1

Witam. Podczas korzystania z instrumentów w programie LMMS, bardzo często przestaje w nim działać dźwięk. W okienku Beat+Bassline Editor szary kwadracik niby zmienia swój kolor na zielony wraz z naciśnięciem klawisza, ale w FM Mixer na kanale 0 (Master) nie widać, by dźwięk działał i dźwięku nie ma. Najczęściej na tą dolegliwość pomaga zrestartowanie komputera. Drugi mój problem związany jest z programem Bristol. Otóż normalna próba uruchomienia go poleceniem

startBristol -vox

skutkuje pojawieniem się na chwilę czarnego okienka i następującym tekstem w terminalu

kijek@blaszak ~ $ startBristol -vox

jackstats found -rate -count

[: 411: =: unexpected operator

checking availability of TCP port 5028

using port 5028

starting logging thread [@1294527785.390138]

Copyright (c) by Nick Copeland 1996,2010

This program comes with ABSOLUTELY NO WARRANTY; for details type ` w'.

This is free software, and you are welcome to redistribute it

under certain conditions; type ` g' for details of GPL terms.

starting logging thread [@1294527785.486892]

Jan 9 00:03:05 bristol [0.078032] starting console logging [@1294527785.390138]

Jan 9 00:03:05 bristol [0.083963] bristol version 0.60.5

Jan 9 00:03:05 bristol [0.083983] bristol

Jan 9 00:03:05 bristol [0.083994] -rate -count

Jan 9 00:03:05 bristol [0.084004] -vox

Jan 9 00:03:05 bristol [0.084015] -port 5028

Jan 9 00:03:05 bristol [0.084025] startBristol -vox

Jan 9 00:03:05 bristol [0.084072] generate bandlimited waveforms(31, 12, 84, 1.50, 0.80, 0)

Jan 9 00:03:05 bristol [0.084583] could not reschedule thread

Jan 9 00:03:05 bristol [0.088855] Fixing samplerate at 0

Jan 9 00:03:05 bristol [0.159690] midi jack: 128.1

Jan 9 00:03:05 bristol [0.159885] Opened listening control socket: 5028

Jan 9 00:03:05 bristol [0.159908] opened control socket

Jan 9 00:03:05 bristol [0.159927] midiOpen: 5028(100)

Jan 9 00:03:05 bristol [0.159945] opened device socket

Jan 9 00:03:05 brighton [0.100024] starting console logging [@1294527785.486892]

Jan 9 00:03:05 brighton [0.124475] vox emulation defaults:

Jan 9 00:03:05 brighton [0.124539] -voices 32

Jan 9 00:03:05 brighton [0.124559] -detune 0

Jan 9 00:03:05 brighton [0.124640] -gain 2

Jan 9 00:03:05 brighton [0.124662] -pwd 2

Jan 9 00:03:05 brighton [0.124680] -glide 5

Jan 9 00:03:05 brighton [0.124697] -curve 520

Jan 9 00:03:05 brighton [0.135328] brighton version 0.60.5

Jan 9 00:03:06 brighton [1.135478] brighton

Jan 9 00:03:06 brighton [1.135541] -vox

Jan 9 00:03:06 brighton [1.135571] -port 5028

Jan 9 00:03:06 brighton [1.136149] starting event management thread

Jan 9 00:03:06 brighton [1.136909] connected to :0.0

Jan 9 00:03:06 brighton [1.137040] display is 1920 by 1080 pixels

Jan 9 00:03:06 brighton [1.137131] Window is w 1920, h 1080, d 24, 0 0 0

Jan 9 00:03:06 brighton [1.137909] Using DirectColor display

Jan 9 00:03:06 brighton [1.230186] Initialise the vox link to bristol: 0x8b7b970

Jan 9 00:03:06 brighton [1.230371] bristolMidiTCPActive(localhost, 0)

Jan 9 00:03:06 brighton [1.230403] hostname is localhost, bristol

Jan 9 00:03:06 brighton [1.230802] TCP port: 5028

Jan 9 00:03:06 bristol [1.305467] Accepted connection from 0 (4) onto 1 (6)

Jan 9 00:03:06 brighton [1.230991] Connected to the bristol control socket: 6

Jan 9 00:03:06 brighton [1.231030] bristolengine already active (0)

Jan 9 00:03:06 brighton [1.236393] opened GUI midi handles: 0, 0

Jan 9 00:03:06 bristol [1.565472] could not reschedule thread

Jan 9 00:03:06 bristol [1.565531] registering jack interface: bristol

kijek@blaszak ~ $ Jan 9 00:03:07 brighton [1.522830] no data in alsa buffer for 0 (close)

Jan 9 00:03:11 brighton [6.435990] closing down TCP sockets

po przejrzeniu pomocy doszedłem do tego, że najprawdopodobniej winne jest GUI programu. Gdy je wyłączę, program wydaje się działać, a konsola wywala coś takiego

kijek@blaszak ~ $ startBristol -vox -gui

jackstats found -rate -count

[: 411: =: unexpected operator

checking availability of TCP port 5028

using port 5028

starting logging thread [@1294527936.927814]

Jan 9 00:05:37 bristol [0.102878] starting console logging [@1294527936.927814]

Jan 9 00:05:37 bristol [0.103011] Copyright (c) by Nick Copeland 1996,2010

Jan 9 00:05:37 bristol [0.103025] This program comes with ABSOLUTELY NO WARRANTY; for details type

Jan 9 00:05:37 bristol [0.103036] `bristol warranty'. This is free software, and you are welcome to redistribute it

Jan 9 00:05:37 bristol [0.103046] under certain conditions; type `bristol conditions' for details of terms.

Jan 9 00:05:37 bristol [0.103057] bristol version 0.60.5

Jan 9 00:05:37 bristol [0.103067] bristol

Jan 9 00:05:37 bristol [0.103076] -rate -count

Jan 9 00:05:37 bristol [0.103086] -vox

Jan 9 00:05:37 bristol [0.103096] -gui

Jan 9 00:05:37 bristol [0.103105] -port 5028

Jan 9 00:05:37 bristol [0.103115] startBristol -vox -gui

Jan 9 00:05:37 bristol [0.103126] generate bandlimited waveforms(31, 12, 84, 1.50, 0.80, 0)

Jan 9 00:05:37 bristol [0.103136] could not reschedule thread

Jan 9 00:05:37 bristol [0.104123] Fixing samplerate at 0

Jan 9 00:05:37 bristol [0.107221] midi jack: 128.1

Jan 9 00:05:37 bristol [0.107357] Opened listening control socket: 5028

Jan 9 00:05:37 bristol [0.107414] opened control socket

Jan 9 00:05:37 bristol [0.107425] midiOpen: 5028(100)

Jan 9 00:05:37 bristol [0.107435] opened device socket

nie mam jednak pewności, ponieważ nie mam jak sprawdzić, czy jest dźwięk. Tak więc mam trzy pytania. Co zrobić, by w LMMS ciągle działał dźwięk, jak odpalić Bristol wraz z GUI i w jaki sposób połączyć z nim klawiaturę MIDI.