View Issue Details

IDProjectCategoryView StatusLast Update
0005701ardourbugspublic2020-04-19 20:16
Reporternettings Assigned Topaul  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0 
Summary0005701: export works only the first time. subsequent exports hang with no playhead motion.
Descriptionas of shortly after 04d66a9e3ad2585b4bdd9ea3a022582ec2b9d428
(Sat Sep 21 13:56:59 2013), only the first export after each fresh start of ardour works as expected. subsequent exports hang at 0% in the export dialog, the playhead never starts to move. the situation is recoverable by clicking "stop export", and normal operation resumes, but export will keep failing until ardour is restarted. this is particularly obvious if the "export multiple regions" feature is used.
TagsNo tags attached.

Activities

veda_sticks

2013-09-28 10:24

reporter   ~0015354

If you are using the alsajack bridge try stopping the alsa jack bridge. There is a bug that prevents exporting from working.

I have to stop the the bridge before i can export at all.

nettings

2013-10-01 18:51

manager   ~0015358

a2jmidid seems to be unrelated to this, at least on my machine. i can start export with a2jmidid enabled (i'm running it by default) for the _first_ time, but killing it does not fix the issue on subsequent export runs.

nettings

2013-10-02 19:23

manager   ~0015359

rgareus reports the last version to work is 4a135c82fb

mikkl

2013-10-11 09:58

reporter   ~0015372

I can confirm this issue. Not using a2jmidi.

veda_sticks

2013-10-11 10:34

reporter   ~0015375

Is the cadence snd-aloop deamon running? If your running kx studio, open cadence and stop the alsa audio jack bridge.

what distro are you using?

Ive just tested exporting and cant reproduce it. This must have been fixed in recent updates to KX Studio.

Previously i would have the same behaviour, export would work first time round, but then fail until restart. Unless the alsa audio jack bridge was stopped.

mikkl

2013-10-11 16:33

reporter   ~0015376

I'm not using any other jack clients or additional tools or daemons, just plain jack with Ardour and it seems to be the exact same issue as the reporter. Tested this on two machines running Gentoo Linux.

nettings

2013-10-12 20:24

manager   ~0015377

fixed by las in 7444ac128e80c9221b37889bbd4baf0a844169f3

system

2020-04-19 20:16

developer   ~0023274

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2013-09-26 21:18 nettings New Issue
2013-09-28 10:24 veda_sticks Note Added: 0015354
2013-10-01 18:51 nettings Note Added: 0015358
2013-10-02 19:23 nettings Note Added: 0015359
2013-10-11 09:58 mikkl Note Added: 0015372
2013-10-11 10:34 veda_sticks Note Added: 0015375
2013-10-11 16:33 mikkl Note Added: 0015376
2013-10-12 20:24 nettings Note Added: 0015377
2013-10-12 20:24 nettings Assigned To => paul
2013-10-12 20:24 nettings Status new => resolved
2013-10-12 20:24 nettings Resolution open => fixed
2013-10-12 20:24 nettings Fixed in Version => 3.0 from src repository (git)
2020-04-19 20:16 system Note Added: 0023274
2020-04-19 20:16 system Status resolved => closed