View Issue Details

IDProjectCategoryView StatusLast Update
0005711ardourbugspublic2020-04-19 20:16
Reporterblablack Assigned Tox42  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0 
Summary0005711: Export has been aborted due to an error!
DescriptionHello,

There is a bug in Ardour when exporting Regions.

To reproduce:
- Have a region that is stereo and one minute long
- Reduce it's length by snapping it to the previous bar
- Right click on a Region and select Export
- Click Export

The process will go through, but at the end the following error will appear:
"Export has been aborted due to an error!
See the Log for details."

And in the Ardour logs:
[INFO]: Searching for export formats in /home/blablack/.config/ardour3/export:/opt/Ardour-3.4-dbg/share/export
[ERROR]: Export ended unexpectedly: Exception thrown by AudioGrapher::SilenceTrimmer<float>: process() after reacing end of input


I hope the error description is clear enough - do not hesitate to ask for more details if needed.

Kind Regards,
Aurélien
Additional InformationIn Ardour 3.4
Tags3.5.403, export, marker, range

Relationships

related to 0005091 closedx42 A3 ends file export unexpectedly then locks up 

Activities

jrigg

2013-09-30 18:16

reporter   ~0015355

See 0005091.

When I've seen this error message the exported region sounded OK.

blablack

2013-09-30 20:00

reporter   ~0015356

In my case the file is unusable and is only 44 bytes.

fozzy

2014-02-04 01:28

reporter   ~0015653

I am getting the same behaviour in 3.5.284 with the export ranges feature: Session/Export/Export to Audio Files then expand "Time span and channel options and select the ranges in that list.

I get the 44 byte WAV file containing just the WAV header. In my case the other downside is that it stops the batch of files being exported at that point.

I can work around it by editing the end point of the range and then deselecting the ranges that worked and re-exporting.

mirage

2014-08-24 15:38

reporter   ~0015872

I am getting the same behaviour in 3.5.308

acolomb

2015-01-23 15:57

reporter   ~0016275

Last edited: 2015-01-23 16:01

Just hit this error as well, both with a precompiled 3.5.403-1kxstudio1 package and using latest git master (3.5-4356-g1473442). Seems to be a real problem with the EndOfInput flag logic.

It happens only on one of the CD range markers defined in my session, and the export works perfectly if I move the range's end earlier by one CD frame (1280 samples @96 kHz).

The range end marker is actually beyond the end of the region on the track which should be exported. I suspect the actual file contents are not at fault here, since I already tried replacing everything in interchange/ with silence and still hit the error.

Feel free to contact me for debugging assistance / testing.

x42

2015-01-24 16:19

administrator   ~0016278

I cannot reproduce with the original recipe (3.5-4362-gfe08965, NB current git-head 3.5-4364-gb4e32cd has an unrelated bug 0006149).

It depends on the session and export-preset, the issue comes up once every while but so far there has not been a reliable way to reproduce and investigate.

@acolomb: Could you please zip-up the session and attach it here or make it otherwise available (remove all audio, it'll be replaced by silence on load -> small zip).

2015-01-26 11:08

 

acolomb

2015-01-26 11:10

reporter   ~0016282

Okay, uploaded my failing session with all interchange/ and peak/ data removed.

To reproduce the error, just try to export with the current settings (hope they are stored within the session). It fails during the export of the fourth CD track "Made of Time", all other time spans work correctly.

To work around the error, move the range end marker for "Made of Time" earlier by one CD frame.

x42

2015-01-27 01:22

administrator   ~0016285

acolomb. thanks, yes I can reproduce the error with the attached session.

This is great news, we finally have a handle on the issue.

x42

2015-01-27 22:18

administrator   ~0016286

The SilenceTrimmer exception is [hopefully] fixed in 3.5-4391-g36bbd14

Please test.


PS. I was not able to reproduce the "44bytes issue" - though that effect has been known to exist with jackd < 1.9.11 (jack2 freewheeling bug). jack1 and Ardour's ALSA/Dummy backend are known to be safe.

acolomb

2015-01-28 08:40

reporter   ~0016291

The export exception was thrown before the normalizing step, that is enough for me to explain why the file is empty / only header present.

Currently testing the fix... standby.

acolomb

2015-01-28 09:24

reporter   ~0016292

Fixed for me.

All my recent sessions in this project could be re-exported without error by version 3.5-4391-g36bbd14. If anybody else still has trouble, we could still reopen the issue, right?

system

2020-04-19 20:16

developer   ~0023276

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-30 17:30 blablack New Issue
2013-09-30 18:16 jrigg Note Added: 0015355
2013-09-30 20:00 blablack Note Added: 0015356
2014-02-04 01:28 fozzy Note Added: 0015653
2014-08-24 15:38 mirage Note Added: 0015872
2015-01-23 15:57 acolomb Note Added: 0016275
2015-01-23 16:01 acolomb Note Edited: 0016275
2015-01-23 16:02 acolomb Tag Attached: 3.5.403
2015-01-23 16:02 acolomb Tag Attached: export
2015-01-23 16:02 acolomb Tag Attached: marker
2015-01-23 16:02 acolomb Tag Attached: range
2015-01-24 16:19 x42 Note Added: 0016278
2015-01-26 11:08 acolomb File Added: 2015-01-15 Album premaster 96-resampled.tar.xz
2015-01-26 11:10 acolomb Note Added: 0016282
2015-01-27 01:22 x42 Note Added: 0016285
2015-01-27 13:10 x42 Relationship added related to 0005091
2015-01-27 22:18 x42 Note Added: 0016286
2015-01-27 22:18 x42 Status new => feedback
2015-01-28 08:40 acolomb Note Added: 0016291
2015-01-28 09:24 acolomb Note Added: 0016292
2015-01-29 04:21 x42 Status feedback => resolved
2015-01-29 04:21 x42 Resolution open => fixed
2015-01-29 04:21 x42 Assigned To => x42
2020-04-19 20:16 system Note Added: 0023276
2020-04-19 20:16 system Status resolved => closed