CSV export file error during Soundiz import (ref#VOONJ1)

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

CSV export file error - when exporting a selection of tracks for import to Soundiz. I try to import to Spotify, but I think the file created by Roon is not in the correct format (or what Soundiz expect) See attached file.

Describe your network setup

N/A

Here is result/log form Soundiz

Hey @Moonshiner,

Thanks for writing in!

Can you be more specific here? Are you attempting to export a playlist, album, or simply a select few number of tracks? Are they local files, or tracks from Tidal?

Are you able to successfully import any file exported from Roon to soundiz?

Please upload the file to the internal uploader below:

https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external

Thank you :pray:

Thanks for reply,
I`m trying to export a playlist from library (about 80% local and 20% Tidal)

I have been successful before to export from Roon to Spotify via Soundiz. Lately all my export have failed. From what I can tell the export file looks strange and not correct. Will upload it to the internal uploader for you to have a look.

I select all tracks inside a playlist - export - Generate a CSV list of tracks for importing to Soundiiz

Hi @Moonshiner,

Thank you for sharing. This particular export is incorrectly concatenated - however, we’re not able to reproduce this behavior in-house when exporting a playlist containing mixed local/streaming files as you’ve indicated.

What happens if you test the following exports?

  1. Export a playlist containing only local files for Soundiz via .csv
    2 Export a playlist containing only Tidal files for Soundiz via .csv

Please let us know if either .csv is generated in the correct format. We’ll follow up from there. Thanks!

Thanks for looking into this,
as mentioned it has worked before with no issues

I have uploaded two files, one with local and one with tidal

Hi @Moonshiner,
Thanks for providing the CSV files. We were able to replicate the issue in house. The next step here is to bring this case to our development team. Once we have some next steps for you we will let you know here.

Thanks :smiley:
Then I assume there will be a solution for this in a future update

Hi @Moonshiner,

Please keep an eye on Software Release Notes, where you’ll see the associated ticket merge into a release when it’s ready for testing. Thanks!

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.