Home → Problems →

Scan thirds

• Edit

justin

12 Apr, 2026 11:12 PM

Subject: Accessibility of Scan Results and CSV Workflow Challenges

Part 1 – Technical Limitation
Dear beaTunes Team,

I hope this message finds you well. I would like to share some difficulties I have been experiencing with the handling of scan results in beaTunes. Although the application generates highly valuable metadata (tempo, key, BPM, timbre, replaygain, mood, etc.), it remains challenging to make effective use of these “third results” either within beaTunes itself or when attempting to export them for external analysis. This limitation reduces the ability to integrate beaTunes metadata into other tools such as Mp3tag or broader analytical environments, which is particularly important for electronic music workflows.

Furthermore, my attempts to install and use BeaLets as a workaround have unfortunately led to repeated database corruption issues, creating instability and complicating the process further. I would be grateful if you could clarify why these scan results are not more readily accessible for external use, and whether improvements in this area are planned.

Part 2 – Workflow Impact
In addition to the technical concerns, I have also found that curating CSV lists generated by beaTunes is not straightforward. The rigid structure of these lists makes workflows cumbersome and difficult to adapt, which undermines the flexibility required for external analysis and curation. For electronic music production, the combination of limited access to scan results and the difficulty of managing CSV outputs creates a considerable bottleneck in establishing a clean, reliable workflow.

I greatly appreciate the work your team has invested in beaTunes, and I hope these observations can help inform future development. Thank you very much for your time and consideration.

Respectfully,
Jay

1. 1 Posted by steph on 13 Apr, 2026 09:30 AM

   

   Hi Jay

   I'm just a user; I have no affiliation with the company. Still, I read as many posts as possible and try to help or ask clarifying questions.

   I don’t quite understand what restriction you’re referring to, for example, regarding the use of data in MP3tag. Using the context menu, you can only open a single track in MP3tag. On a Mac, I can select hundreds of tracks in beaTunes and drag them into MP3tag, and then all the data gets loaded. Whether that also works with Windows—I have no idea.

   You mention the impact on your workflow regarding CSV. You criticize the rigid structure, but that’s always the case with CSV files. Or do you mean that you lack the ability to select the data to be exported and make the list more manageable?

   Which beatLet/plugin caused you problems? I myself only use the one for displaying/exporting Camelot-Wheel notation.

   I don’t create playlists for use as a DJ, but for hours of background music from my collection of over 119,000 tracks. That creates entirely different problems and requirements.

   best regards
   Stephan

   • Edit

2. Support Staff 2 Posted by Hendrik Schreib... on 20 Apr, 2026 04:23 PM

   

   Hey Justin,

   sorry for the late reply.

   it remains challenging to make effective use of these “third results” either within beaTunes itself or when attempting to export them for external analysis.

   I do not entirely understand what you mean with "third results" - tempo, key, etc. or something else?

   Thanks,

   -hendrik

   • Edit