Намедни прочитал заметку о редакторе Ardour 3.2 и поставил себе его из репозитария (там версия 2 с копейками). От этого редактора мне нужна его способность корректного редактирования аудио-дорожек в видеофайлах.
Пакет встал без проблем.
Но запустить его не могу: после старта открывается окно начальных настроек - ОК - и получаю сообщение со скриншота:
"Параметры звука" менял, как только можно - без разницы.
Запускал и из консоли под root-ом - бесполезно.
Сервер JACK (понятия не имею, что это) - в процессах системы не обнаружил.
Памяти в системе 16 Гб.
Помогите совладать со зверюгой!
P. S. Вот выдача консоли:
| sudo ardour2 [sudo] password for sancho: WARNING: Your system has a limit for maximum amount of locked memory! This might cause Ardour to run out of memory before your system runs out of memory. You can view the memory limit with 'ulimit -l', and it is normally controlled by /etc/security/limits.conf Ardour 2.8.14 (built using 13065 and GCC version 4.7.2) Copyright (C) 1999-2008 Paul Davis Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker Ardour comes with ABSOLUTELY NO WARRANTY not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This is free software, and you are welcome to redistribute it under certain conditions; see the source for copying conditions. loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc ardour: [INFO]: Ardour will be limited to 4096 open files загружается файл конфигурации системы "/etc/ardour2/ardour_system.rc" ardour: [INFO]: Using SSE optimized routines ardour: [INFO]: поиск протоколов управляющих устройств в /root/.ardour2/surfaces/:/usr/lib/ardour2/surfaces/ ardour: [INFO]: обнаружен протокол управляющего устройства: "Generic MIDI" ardour: [INFO]: протокол управляющего устройства Tranzport не пригоден к использованию ardour: [INFO]: обнаружен протокол управляющего устройства: "Mackie" powermate: Opening of powermate failed - Нет такого файла или каталога ardour: [INFO]: протокол управляющего устройства powermate не пригоден к использованию Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel jack server is not running or cannot be started NSD response -5 folder = JACK COMMAND: /usr/bin/jackd -p 128 -R -P 60 -T -d alsa -n 2 -r 0 -p 1024 -d hw:0,0 Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel jackdmp 1.9.9 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2012 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 60 control device hw:0 control device hw:0 audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0,0|hw:0,0|1024|2|0|0|0|nomon|swmeter|-|32bit control device hw:0 ATTENTION: The playback device "hw:0,0" is already in use. The following applications are using your soundcard(s) so you should check them and stop them as necessary before trying to start JACK again: pulseaudio (process ID 3851) JackTemporaryException : now quits... Cannot initialize driver JackServer::Open failed with -1 Failed to open server Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel jack server is not running or cannot be started NSD response -5 folder = JACK COMMAND: /usr/bin/jackd -m -p 97 -R -P 60 -u -T -d alsa -n 2 -r 0 -p 1024 -d hw:0,0 Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel jackdmp 1.9.9 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2012 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 60 control device hw:0 control device hw:0 audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0,0|hw:0,0|1024|2|0|0|0|nomon|swmeter|-|32bit control device hw:0 ATTENTION: The playback device "hw:0,0" is already in use. The following applications are using your soundcard(s) so you should check them and stop them as necessary before trying to start JACK again: pulseaudio (process ID 3851) JackTemporaryException : now quits... Cannot initialize driver JackServer::Open failed with -1 Failed to open server Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel Cannot connect to server socket err = Нет такого файла или каталога Cannot connect to server request channel jack server is not running or cannot be started (ardour-2.8.14:7333): Gtk-CRITICAL **: IA__gtk_table_attach: assertion `child->parent == NULL' failed NSD response -6 folder = |
P. P. S. Файл /etc/security/limits.conf:
| # /etc/security/limits.conf # #Each line describes a limit for a user in the form: # #<domain> <type> <item> <value> # #Where: #<domain> can be: # - an user name # - a group name, with @group syntax # - the wildcard *, for default entry # - the wildcard %, can be also used with %group syntax, # for maxlogin limit # - NOTE: group and wildcard limits are not applied to root. # To apply a limit to the root user, <domain> must be # the literal username root. # #<type> can have the two values: # - "soft" for enforcing the soft limits # - "hard" for enforcing hard limits # #<item> can be one of the following: # - core - limits the core file size (KB) # - data - max data size (KB) # - fsize - maximum filesize (KB) # - memlock - max locked-in-memory address space (KB) # - nofile - max number of open files # - rss - max resident set size (KB) # - stack - max stack size (KB) # - cpu - max CPU time (MIN) # - nproc - max number of processes # - as - address space limit (KB) # - maxlogins - max number of logins for this user # - maxsyslogins - max number of logins on the system # - priority - the priority to run user process with # - locks - max number of file locks the user can hold # - sigpending - max number of pending signals # - msgqueue - max memory used by POSIX message queues (bytes) # - nice - max nice priority allowed to raise to values: [-20, 19] # - rtprio - max realtime priority # - chroot - change root to directory (Debian-specific) # #<domain> <type> <item> <value> # #* soft core 0 #root hard core 100000 #* hard rss 10000 #@student hard nproc 20 #@faculty soft nproc 20 #@faculty hard nproc 50 #ftp hard nproc 0 #ftp - chroot /ftp #@student - maxlogins 4 # End of file |
