southernfm
Active member
We're trialling using OneDrive with RadioBOSS.
When we've downloaded the MP3 to the hard drive using OneDrive's sync capabilities, the library search feature seems okay for tracks that are on the hard drive. E.g. we have a folder called ZZ_Themes, C:\Music\ZZ_Themes and a music library called ZZ_Themes. When searching within this library, it is responsive.
We have a large music library, with over 75,000 tracks, between 1950s-2020s, split over several libraries. These are not available on the hard drive, but can be downloaded by OneDrive as needed. When we drag the track into the playlist, or click on the track in the playlist, this is enough to trigger OneDrive to download a local copy of that file. For our purposes this would be sufficient.
However - when we attempt to search through libraries containing tracks that aren't available on the hard drive, the program becomes unresponsive most of the time. Searching for a track is pretty much impossible to do with our set up. This is the same if we reference a network attached location. In our case we're trying to set up a laptop so we can play music at outside broadcasts. The laptop hard drive isn't large enough to house the entire library.
We're working on a way to solve the issue for ourselves, but the search functionality seems to reference the tracks that are being looked up fairly heavily. Expected behaviour with the library search would be for the information within the database itself to show up within the library search. If a track or item is clicked on the library, perhaps that would warrant 'probing' the MP3 file, although personally I think that should only be done if it is in the playlist, or track tool or something like that were used on the track.
I understand there's a cache involved, but I'm not sure what the need is in probing the MP3 files within the library search itself, if we have a database that's supposed to have all the information (the cache could reference the database directly if required, instead of the MP3 file(s).
For example we search for "Eminem" in either (All) or one of the music libraries where we don't have all the MP3s on the hard drive, and the laptop starts downloading 20 tracks in OneDrive, unrelated to what we actually needed. Additionally RadioBOSS freezes and wants to crash (we've submitted bug reports).
This may be a fringe use case with RadioBOSS, but if the search was limited to pulling data out of the database only (except if File Tag APEv2 is used), instead of referencing the files directly, then it would likely improve the search speed and reliability.
When we've downloaded the MP3 to the hard drive using OneDrive's sync capabilities, the library search feature seems okay for tracks that are on the hard drive. E.g. we have a folder called ZZ_Themes, C:\Music\ZZ_Themes and a music library called ZZ_Themes. When searching within this library, it is responsive.
We have a large music library, with over 75,000 tracks, between 1950s-2020s, split over several libraries. These are not available on the hard drive, but can be downloaded by OneDrive as needed. When we drag the track into the playlist, or click on the track in the playlist, this is enough to trigger OneDrive to download a local copy of that file. For our purposes this would be sufficient.
However - when we attempt to search through libraries containing tracks that aren't available on the hard drive, the program becomes unresponsive most of the time. Searching for a track is pretty much impossible to do with our set up. This is the same if we reference a network attached location. In our case we're trying to set up a laptop so we can play music at outside broadcasts. The laptop hard drive isn't large enough to house the entire library.
We're working on a way to solve the issue for ourselves, but the search functionality seems to reference the tracks that are being looked up fairly heavily. Expected behaviour with the library search would be for the information within the database itself to show up within the library search. If a track or item is clicked on the library, perhaps that would warrant 'probing' the MP3 file, although personally I think that should only be done if it is in the playlist, or track tool or something like that were used on the track.
I understand there's a cache involved, but I'm not sure what the need is in probing the MP3 files within the library search itself, if we have a database that's supposed to have all the information (the cache could reference the database directly if required, instead of the MP3 file(s).
For example we search for "Eminem" in either (All) or one of the music libraries where we don't have all the MP3s on the hard drive, and the laptop starts downloading 20 tracks in OneDrive, unrelated to what we actually needed. Additionally RadioBOSS freezes and wants to crash (we've submitted bug reports).
This may be a fringe use case with RadioBOSS, but if the search was limited to pulling data out of the database only (except if File Tag APEv2 is used), instead of referencing the files directly, then it would likely improve the search speed and reliability.