Problems with a Project

Hi!

At first I excuse me for my terrible english. I’m from Germany und I speak english not so good.

To my Problem:
I recorded a Band. I recorded it with an Hard-Disk Multitrack Recorder. Later I transfer this tracks to my PC. Now I have 15Files, the different Tracks of Recording. Every File has a size of 1Gb, about 2 hours. I can imported this files to Ardour. I can edit this Mix and play. Finally, I save my settings so I can go on the next day. But the next day I can not open this file. I can start Ardour , my file can select , but after a short loading time Ardour is terminated without notification. This is very annoying , because a lot of work has gone. What could go wrong?
I use Kubuntu 14.04 on AMD A10 CPU.
If more information is needed , please ask

Thanks

Dennis

The standard response:
https://ardour.org/debugging_ardour.html

The obvious question, what version of Ardour are you using, and where did you get it from?

   Seablade

Hi!

I tried to debug Ardour, as described in your Link. I get many Errors.

dennis@Notebook-Dennis:~$ /opt/Ardour-3.5.403-dbg/bin/ardour3 --debug
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright © 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
This GDB was configured as “x86_64-linux-gnu”.
Type “show configuration” for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type “help”.
Type “apropos word” to search for commands related to “word”…
Reading symbols from /opt/Ardour-3.5.403-dbg/bin/ardour-3.5.403…done.
(gdb) run
Starting program: /opt/Ardour-3.5.403-dbg/bin/ardour-3.5.403
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/lib/x86_64-linux-gnu/libthread_db.so.1”.
bnd txt domain [gtk2_ardour3] to /opt/Ardour-3.5.403-dbg/share/locale
Ardour3.5.403 (kompiliert mit Version 3.5-403-gec2cb31 und GCC Version4.4.6)
ardour: [INFO]: Ihre Systemkonfiguration beschränkt Ardour auf nur 4096 offene Dateien
[New Thread 0x7fffe900f700 (LWP 3403)]
ardour: [INFO]: Lade Systemkonfigurationsdatei /opt/Ardour-3.5.403-dbg/etc/ardour_system.rc
Lade Benutzerkonfiguration /home/dennis/.config/ardour3/ardour.rc
Using SSE optimized routines
[New Thread 0x7fffe880e700 (LWP 3404)]
[New Thread 0x7fffe3fff700 (LWP 3405)]
[New Thread 0x7fffe37fe700 (LWP 3406)]
Kann die SIGPIPE Fehlerbehandlung nicht installieren
(ardour-3.5.403:3399): Gtk-WARNING **: Im Modulpfad »oxygen-gtk« konnte keine Themen-Engine gefunden werden,
ardour: [INFO]: lade voreingestellte UI-Konfigurationsdatei /opt/Ardour-3.5.403-dbg/etc/ardour3_ui_default.conf
Lade benutzerdefinierte UI-Konfigurationsdatei /opt/Ardour-3.5.403-dbg/etc/ardour3_ui.conf
(ardour-3.5.403:3399): GLib-GObject-WARNING **: Attempt to add property gtkmm__CustomObject_N9Gtkmm2ext25CellRendererColorSelectorE::color after class was initialised
ardour: [INFO]: Loading ui configuration file /opt/Ardour-3.5.403-dbg/etc/ardour3_ui_dark.rc
(ardour-3.5.403:3399): Gtk-WARNING **: Im Modulpfad »oxygen-gtk« konnte keine Themen-Engine gefunden werden,
[New Thread 0x7fffe1aae800 (LWP 3407)]
[New Thread 0x7fffe13fa700 (LWP 3408)]
Cannot connect to server socket err = Verbindungsaufbau abgelehnt
Cannot connect to server request channel
jack server is not running or cannot be started
[Thread 0x7fffe13fa700 (LWP 3408) exited]
[New Thread 0x7fffd3fff700 (LWP 3409)]
[New Thread 0x7fffd0d3f700 (LWP 3410)]
[New Thread 0x7fffc974c700 (LWP 3411)]
Found 0 along /home/dennis/.config/ardour3/templates:/opt/Ardour-3.5.403-dbg/share/templates
run dialog
Announcement is:
[Thread 0x7fffe1aae800 (LWP 3407) exited]
[Thread 0x7fffd0d3f700 (LWP 3410) exited]
[Thread 0x7fffc974c700 (LWP 3411) exited]
JACK command line will be: /usr/bin/jackd -t 200 -p 2048 -R -T -d alsa -n 2 -r 48000 -p 1024 -d hw:Generic,0
[New Thread 0x7fffe13fa700 (LWP 3431)]
Cannot connect to server socket err = Verbindungsaufbau abgelehnt
Cannot connect to server request channel
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2013 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 10
audio_reservation_init
Acquire audio card Audio1
creating alsa driver … hw:Generic,0|hw:Generic,0|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
[New Thread 0x7fffd0094700 (LWP 3440)]
[New Thread 0x7fffc8d45700 (LWP 3441)]
[New Thread 0x7fffc974c700 (LWP 3442)]
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
no more csLADSPA plugins
Scanning folders for bundled LV2s: /opt/Ardour-3.5.403-dbg/lib/LV2
(ardour-3.5.403:3399): GLib-GObject-WARNING **: Attempt to add property gtkmm__CustomObject_N9Gtkmm2ext23CellRendererPixbufMultiE::active after class was initialised
[New Thread 0x7fffa03b5700 (LWP 3443)]
[New Thread 0x7fffa0334700 (LWP 3444)]
[New Thread 0x7fffa02b3700 (LWP 3445)]
[New Thread 0x7fffa0232700 (LWP 3446)]
[New Thread 0x7fffa01b0800 (LWP 3447)]
[New Thread 0x7fffd0d3f700 (LWP 3448)]
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Unknown destination port in attempted (dis)connection src_name [ardour:auditioner/midi_out 1] dst_name [ardour:Midiaudition]
JackGraphManager::Connect already connected port_src = 22 port_dst = 17
JackGraphManager::Connect already connected port_src = 23 port_dst = 18
JackGraphManager::Connect already connected port_src = 25 port_dst = 17
JackGraphManager::Connect already connected port_src = 26 port_dst = 18
JackGraphManager::Connect already connected port_src = 28 port_dst = 17
JackGraphManager::Connect already connected port_src = 29 port_dst = 18
JackGraphManager::Connect already connected port_src = 31 port_dst = 17
JackGraphManager::Connect already connected port_src = 32 port_dst = 18
JackGraphManager::Connect already connected port_src = 34 port_dst = 17
JackGraphManager::Connect already connected port_src = 35 port_dst = 18
JackGraphManager::Connect already connected port_src = 37 port_dst = 17
JackGraphManager::Connect already connected port_src = 38 port_dst = 18
JackGraphManager::Connect already connected port_src = 40 port_dst = 17
JackGraphManager::Connect already connected port_src = 41 port_dst = 18
JackGraphManager::Connect already connected port_src = 43 port_dst = 17
JackGraphManager::Connect already connected port_src = 44 port_dst = 18
JackGraphManager::Connect already connected port_src = 46 port_dst = 17
JackGraphManager::Connect already connected port_src = 47 port_dst = 18
JackGraphManager::Connect already connected port_src = 49 port_dst = 17
JackGraphManager::Connect already connected port_src = 50 port_dst = 18
JackGraphManager::Connect already connected port_src = 52 port_dst = 17
JackGraphManager::Connect already connected port_src = 53 port_dst = 18
JackGraphManager::Connect already connected port_src = 55 port_dst = 17
JackGraphManager::Connect already connected port_src = 56 port_dst = 18
JackGraphManager::Connect already connected port_src = 58 port_dst = 17
JackGraphManager::Connect already connected port_src = 59 port_dst = 18
JackGraphManager::Connect already connected port_src = 61 port_dst = 17
JackGraphManager::Connect already connected port_src = 62 port_dst = 18
JackGraphManager::Connect already connected port_src = 64 port_dst = 17
JackGraphManager::Connect already connected port_src = 65 port_dst = 18
JackGraphManager::Connect already connected port_src = 7 port_dst = 3
JackGraphManager::Connect already connected port_src = 8 port_dst = 4
JackGraphManager::Connect already connected port_src = 1 port_dst = 5

Need you more informations?

Dennis

I forgot somethings. This part of the code is repeated over and over again:

JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackAudioDriver::ProcessGraphAsyncMaster: Process error

I have to close the console, because it will never ending.

Dennis

You are not running JACK in the right way for debugging. You need to start it with the largest period (buffer) size and not in realtime mode. You should also probably start JACK outside of Ardour so that JACK’s output does not get mingled in with the output from Ardour and gdb.

Thanks for your answer . Jack before start Ardour does not work, because Jack brings only error messages. With smaller projects, it works when I start Ardour , Jack then starts automatically . Then perhaps this is also exactly the problem and not with Ardour .

Dennis

There is no reason for not being able to start JACK if Ardour can start it. What are the error messages if you try?

Here the Output from Jack:

21:56:50.750 Steckfeld deaktiviert.
21:56:50.750 Statistik zurückgesetzt.
21:56:50.783 ALSA-Verbindung geändert.
21:56:51.237 D-BUS: Dienst ist verfügbar (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
jack server is not running or cannot be started
21:56:51.254 Schaubild der ALSA-Verbindungen geändert.
21:56:54.262 D-BUS: JACK-Server konnte nicht gestartet werden. Tut mir leid
Sun Dec 7 21:56:54 2014: Starting jack server…
Sun Dec 7 21:56:54 2014: JACK server starting in non-realtime mode
Sun Dec 7 21:56:54 2014: Acquired audio card Audio0
Sun Dec 7 21:56:54 2014: creating alsa driver … hw:0|-|1024|2|48000|0|0|nomon|swmeter|-|32bit
Sun Dec 7 21:56:54 2014: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Sun Dec 7 21:56:54 2014: ERROR: Cannot initialize driver
Sun Dec 7 21:56:54 2014: ERROR: JackServer::Open failed with -1
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
jack server is not running or cannot be started
Sun Dec 7 21:56:54 2014: ERROR: Failed to open server
Sun Dec 7 21:56:55 2014: Saving settings to “/home/dennis/.config/jack/conf.xml” …
21:57:14.302 Keine Verbindungsaufnahme als Client zum JACK-Server möglich. - Gesamtbetrieb schlug fehl. - Verbindungsaufnahme zum Server gescheitert. Bitte sehen Sie im Meldungsfenster nach weiteren Informationen.
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
jack server is not running or cannot be started

Dennis

You’d need to come onto IRC to get more help on this. I can’t help with issues like this via a web forum, its the wrong place for it. See the Support page for details on IRC.

I was on IRC . Now everything works. The problems with Jack , I have resolved itself . It was really the wrong hardware selected that is not noticed at first. Ardour but still would not start after that. My mistake was to blindly trust the German Ubuntu wiki . So I installed old Calf plugins. I have found the current plugins , but only with the help of the IRC I was able to remove the old one. Now everything is and I would like to thank everyone who helped me. Ardour is really a great program .

Dennis

Hi Dennis,
I have exactly this problem, and am also using the Calf plugins. Can you describe exaclty what you did in order to fix it?