Tracks with three periods in the file path fail to export [Ticket open]

Ran an export of my 25k-ish-track library. 20ish tracks failed to export, and they all had the same thing in common: three periods in the album name. Maybe the filesystem is expecting you to escape the periods? Here’s an excerpt from my roon_log (I know, I know, bad boy, shouldn’t look inside the support package, but it let me diagnose this issue):

10/06 22:50:33 Debug: [export] compute output path, newdir: The Dresden Dolls/Yes, Virginia…, cachedir: The Dresden Dolls/Yes, Virginia…
10/06 22:50:33 Debug: [export] test tmppath: C:\Users\Joe_2\AppData\Local\Temp.roonexportdata-9c7f6967-e5e0-46a9-8446-0885a49fcd96\5fcab121-9685-406b-acd5-2b9377abb044.m4a
10/06 22:50:33 Debug: [easyhttp] GET to http://192.168.1.102:9100/file/4627b856-91f1-4b20-8c75-201ef0844ccb/4300546865204472657364656e20446f6c6c732f5965732c2056697267696e69612e2e5f2f30392053686f726573204f662043616c69666f726e69612e6d3461.m4a
10/06 22:50:36 Trace: [export] scaling image 1024,1024 => 1141,1023 correct_aspect=1.11455108359133
10/06 22:50:36 Error: [export] Could not copy file C:\Users\Joe_2\AppData\Local\Temp.roonexportdata-9c7f6967-e5e0-46a9-8446-0885a49fcd96\5fcab121-9685-406b-acd5-2b9377abb044.m4a to The Dresden Dolls/Yes, Virginia…/1-09 Shores of California.m4a: Result[Status=UnexpectedError, ErrorText=System.IO.DirectoryNotFoundException: The system cannot find the path specified.

at Base.IO.LongPathCommon.GetFileHandle(String normalizedPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Base.IO.LongPathFile.Open(String path, FileMode mode, FileAccess access, FileShare share)
at Roon.FileSystem.AttachedFileSystem.<>c__DisplayClass3f.b__3c()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Roon.FileSystem.AttachedFileSystem.d__41.MoveNext()]

And another album with the same issue:

10/06 22:50:19 Debug: [export] compute output path, newdir: Counting Crows/Films About Ghosts_ The Best Of…, cachedir: Counting Crows/Films About Ghosts_ The Best Of…
10/06 22:50:19 Debug: [export] test tmppath: C:\Users\Joe_2\AppData\Local\Temp.roonexportdata-9c7f6967-e5e0-46a9-8446-0885a49fcd96\ae6c2579-8a29-4675-83e1-272f0e303aac.m4a
10/06 22:50:19 Debug: [easyhttp] GET to http://192.168.1.102:9100/file/29bdcae6-b5fd-d666-27bf-a1f6afceabac/43006954756e65732f6954756e6573204d656469612f4d757369632f436f756e74696e672043726f77732f46696c6d732041626f75742047686f7374735f205468652042657374204f662e2e5f2f3137204163636964656e74616c6c7920496e204c6f76652e6d3461.m4a
10/06 22:50:21 Error: [export] Could not copy file C:\Users\Joe_2\AppData\Local\Temp.roonexportdata-9c7f6967-e5e0-46a9-8446-0885a49fcd96\ae6c2579-8a29-4675-83e1-272f0e303aac.m4a to Counting Crows/Films About Ghosts_ The Best Of…/1-17 Accidentally In Love.m4a: Result[Status=UnexpectedError, ErrorText=System.IO.DirectoryNotFoundException: The system cannot find the path specified.

at Base.IO.LongPathCommon.GetFileHandle(String normalizedPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Base.IO.LongPathFile.Open(String path, FileMode mode, FileAccess access, FileShare share)
at Roon.FileSystem.AttachedFileSystem.<>c__DisplayClass3f.b__3c()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Roon.FileSystem.AttachedFileSystem.d__41.MoveNext()]

I’m exporting from a core on a Mac Mini to a client on a Windows 10 box. Happy to send the whole support package if helpful.

1 Like

I remember having seen the same issue but during import on my Nuc/Rock.

Hi @Joe_Gratz ----- Thank you for the report and sharing your feedback with us, both are appreciated!

Moving forward, to help us better understand this behavior, would you kindly provide me with the following:

  • An expanded description of your current setup, using this link as a guide.

  • A set of your Roon logs from the device hosting your Roon core, using the instructions found here.

  • If possible, can you please provide us with a few media samples that you noticed this issue you with via “shared” dropbox link for analysis.

-Eric

Same here. Genesis “…And Then There Were Three” was not imported until changing folder name to “And Then There Were Three”.
Roon Server - xUbuntu, Intel NUC. Multiple Roon Bridge (NUCs, Raspberry Pi, Cubox, Odroid).

got this problem trying to export But Seriously Folks… by Joe Walsh

Hi @Sallah_48 ---- Thank you for chiming in here and sharing your observations with me.
Upon seeing your report I setup a test core to see what I can come up with whil trying to export a track with “…” in it.

Core = MacBook Air (v1.5 B323)
Artist = Pink Floyd
Song = “The Gold It’s in the…”

As you can see from my screenshot below I had no issues during export:

-Eric

Thanks @eric

I am running PC with Windows 10 64bit, I guess this would handle characters differently in filenaming to Mac?

Thanks for verifying that you are running on a Windows based machine @Sallah_48 , I am going to have one of our tech team members confirm what the experience is like on a Win10 core. I will let you know what they come up with.

-Eric

1 Like

The song title in your example uses an ellipsis not three periods: vis-à-vis ...

1 Like

All — Letting you know that our tech team has been able to re-create this behavior in house and have taken out a ticket with our DEV team for further investigation.

While I cannot say for certain as to when this behavior will be addressed, I can however assure you that I will be certain to keep thread up to date with any feedback provided to me from the team. Your patience during this process is greatly appreciated!

-Eric

Exporting my library, after finishing I get Messages like:

Looking in the log file and searching for “error” it Shows e.g.:

06/17 23:24:00 Debug: [export] compute output path, newdir: Mylène Farmer/L'Autre..., cachedir: Mylène Farmer/L'Autre...
06/17 23:24:00 Debug: [export] test tmppath: C:\Users\Frank\AppData\Local\Temp\.roonexportdata-8db4637f-c274-4ecd-9e09-e6aa49888a4c\9ad81afe-233e-4693-b709-30390e180189.flac
06/17 23:24:00 Debug: [easyhttp] GET to http://192.168.1.110:9100/file/3de35429-c311-4b02-8f67-309518fab753/43004d4b2f4d7573696b2f506f70526f636b2f4d796c656e65204661726d65722f4c272041757472652f3033204c272041757472652e666c6163.flac returned after 0 ms, status code: 200
06/17 23:24:04 Debug: [export] path as bytes:  4D-79-6C-65-CC-80-6E-65-20-46-61-72-6D-65-72-2F-4C-27-41-75-74-72-65-2E-2E-2E-2F-31-2D-30-33-20-4C-27-41-75-74-72-65-2E-66-6C-61-63
06/17 23:24:04 Debug: [export] path as string: Mylène Farmer/L'Autre.../1-03 L'Autre.flac
06/17 23:24:04 Error: [export] Could not copy file C:\Users\Frank\AppData\Local\Temp\.roonexportdata-8db4637f-c274-4ecd-9e09-e6aa49888a4c\9ad81afe-233e-4693-b709-30390e180189.flac to Mylène Farmer/L'Autre.../1-03 L'Autre.flac: Result[Status=UnexpectedError, ErrorText=System.IO.DirectoryNotFoundException: Das System kann den angegebenen Pfad nicht finden.

Is there an easy way to have those 44 failed tracks listed and a way to fix it?

Hey @fschmeis,

I moved your post over to an existing topic on the subject. There is a ticket with out dev team that is under investigation, as mentioned in @eric’s post above.

Based on the logs you shared, it looks like the files that experienced this issue all have three periods in the path, which is why they failed to export.

We can’t say for sure when this will be a addressed, but we will be sure to keep everyone updated here when we receive feedback from the team!

Regards,
Dylan

Hi @dylan, thanky for moving my post; my use case: my girl friend and I moved together and I am in the process to put our Collections together, means: I would like to get rid of all the duplicates by exporting our combined library; therefore would appreciate a fix very much to save a lot of manual work …

Hello,

I’m trying to search for this existing topic to read up on.

I’m in same situation. But interestingly, this bug only affects exporting flac.

Exporting by the “same” album if exporting as dsf, then Roon seem to “append” the “(2)” so the path becomes “…And Then There Were Three… (2)” which Windows 10 can cope with since dots are not trailing in the name.

Thanks much.

Tried the same export on Mac.

Thought would work, i.e. “…And Then There Were Three…” as folder name.

Nope.

Gets this error,

image

So, windows has issue with trailing dots,

image

And Mac (i suppose Unix/Linux as well) has issue with beginning dots.

What’s odd is that Roon (not core) remote in windows 10 exporting track from such album will error out.

But Mac just keeps on going. Finishes. But nothing there in the expected export location.

You’re getting the error because the file name has three full stops instead of the ellipsis character: … vis-à-vis …

Replace with this before exporting:

Thank you. I just saw your comment above, about using ellipsis (single) char over 3 full dots.

I don’t think i’ve (ever) used such ellipsis char.

Silly question - where would i be doing this replacement?

In Roon edit of the album name?

Or, in each file’s tag for album name? <<------- i’ve already removed the 3 full dots from file’s tag and still same error

So, i’m wondering if i should be doing this replacement here?

Yep, that worked, i.e.

Thank you!

Yes, that’s correct. Click on edit box and then the copy button and edit the text.

I’ll need to Google this ellipse char and how to type this (instead of copy and paste from your char).

Interestingly,

image

, end result is, underscore?

Same in Mac,

image

This is “okay” workaround, at least unblock my exporting.

Side effect (probably expected) is Roon is not coalescing this album with the others with the same title, except on ellipse versus 3 dots, hence treats replaced album name as separate and not as different versions. :frowning: