itâs a bug. if i select just the one flow and donât check, export each flow separately, the export works, if i select that flow but do check the box, the app gets a âpath exceeds maximum lengthâ error:
vstaudioengine.log - box not checked
2022-02-26 19:19:56 : AudioExport: chan 5, [20.000000,62.762740], samplerate 48000.000000, sampleFormatSize 2, channel 2, format 3
2022-02-26 19:19:56 : ID3Tag: ramblings_orchestra_v30 - 3-Ogni vita ha bisogno di un piccolo scherzo(every life needs a little joke);;;;;1
2022-02-26 19:19:56 : File: /D:/Dorico Projects/Flows/Flows from Ramblings an FTD journey - Orchestra/ramblings_orchestra_v30 - 3-Ogni vita ha bisogno di un piccolo scherzo(every life needs a little joke).mp3
2022-02-26 19:19:56 : Audio Export: Started2022-02-26 19:19:59 : Audio Export: Done (noError)
vstaudioengine.log - box not checked
2022-02-26 19:20:03 : License Info: ping response received: from silk service
2022-02-26 19:20:07 : License Info: ping response received: from silk service
2022-02-26 19:20:07 : License Info: ping response received: from silk service
2022-02-26 19:20:48 : License Info: ping response received: from silk service
2022-02-26 19:20:52 : License Info: ping response received: from silk service
2022-02-26 19:20:52 : License Info: ping response received: from silk service
2022-02-26 19:20:58 : AudioExport: chan 5, [20.000000,62.762740], samplerate 48000.000000, sampleFormatSize 2, channel 2, format 3
2022-02-26 19:20:58 : ID3Tag: ramblings_orchestra_v30 - 3-Ogni vita ha bisogno di un piccolo scherzo(every life needs a little joke);;;;;1
2022-02-26 19:20:58 : File: /D:/Dorico Projects/Flows/Flows from Ramblings an FTD journey - Orchestra/04 - 3-Ogni vita ha bisogno di un piccolo scherzo(every life needs a little joke)/ramblings_orchestra_v30 - 3-Ogni vita ha bisogno di un piccolo scherzo(every life needs a little joke).mp3
2022-02-26 19:20:58 : Audio Export: Path exceeds maximum length
Are you on Dorico 4?
I thought we already fixed this.
Maybe we just raise âpath too longâ in the audio engine but Dorico then ignoring the error number. I will checkâŚ
Thanks for reporting
i am using Version 4.0.10.1044 (Jan 28 2022)
Dorico 4 AudioEngine Version 5.0.10.113
should dorico be using 8.3 format on windows internally for this issue ? see " GetShortPathNameW"
Alternatively , shorten the flow now. i did get around this by putting the title translation in the subtitle. Also, what clearly matters is the Flowname, not what prints on the score; therefore using shorter names for the flow name is certainly not onerous. However this needs to be more clearly documented (unless i missed something). Part of the confusion is, i think, caused by The relationship betweenthe names in the flow and the project info. It appears to work like this.
â the text used when creating the flow is used as the flow title, unless, it is modified in the flow name in the project info dialoge.
â the name used for the directories by the audio extract is the name in the flow one sees in the setup (where it lists the flows on the bottom of the screen
therefore, using short names in the flows in setup are stored separately internal and the printed names can be anything really long as long as the setup flow names are short
conclusion: you can have your cake and eat it too.
Documenting this clearly to a non tech audience might be challenging.
I donât know, I have to have a look at it again. But from my understanding, it does not matter what the file or folder name is, itâs just that the total length of the path shall not exceed 256 characters. But I will do my investigations and come back.
My tests show that it is solely a matter of the overall path length. If it is longer than 260 characters ( 256 characters + â.wavâ or â.mp3â) then the export fails.
The problem is rather how Dorico creates the export path. Depending on whether you just export a single flow or multiple flows it puts in an extra folder, and that folder name is based on the project and flow name. So if you have a long flow name, you easily get into that limit of 260 characters.
Look at your path in case of error (in bold is that extra folder I mentioned):
D:/Dorico Projects/Flows/Flows from Ramblings an FTD journey - Orchestra /04 - 3-Ogni vita ha bisogno di un piccolo scherzo(every life needs a little joke)/ramblings_orchestra_v30 - 3-Ogni vita ha bisogno di un piccolo scherzo(every life needs a little joke).mp3
So the conclusion is:
Doricoâs naming scheme is maybe not optimal when it comes to long names (project or flow).
Dorico shall not only say âexport errorâ but tell that the path is too long.
i agree. However, the point i was trying to make is that the string Dorico uses is the flow name not the title, which is what is printed on the score. As long as the flow name is short enough, the user will not have a problem. Therefore, what users need to know is that 1. they are different and 2. they can use anything as a title, but need to make sure that the flow name is short enough.
I disagree If you have a long enough project title you equally run into the âtoo long pathâ issue, even if your flows are just named âFlow 1â or so. Though admittedly, it is less likely that someone uses a very long project title
I just ran into this problem, with one flow out of four in the project. It would be nice if the error message was a bit more informative than âerror exporting audioâ, which implies a technical fault of some kind rather than a simple syntactic thing.
Just noticed, also, that the mp3 file name includes both the Dorico file name and the project title. Maybe Dorico could default to the former in the absence of the latter, or where the two are identical â otherwise using only the project title?
I have read this whole thread and there is a wonderful solution to this problem.
Enable custom filenaming of audiofiles and stop creating folder upon folder with long names, that I delete anyway, once the export is done. It is cumbersome and superfluous.
And I am sorry to scratch this sore but this is possible in Sibilius. Why have you chosen, this remarkably awkward way to export audio???
If you have a long enough project title you equally run into the âtoo long pathâ issue, even if your flows are just named âFlow 1â or so. Though admittedly, it is less likely that someone uses a very long project title