Have been using v6 for a while now and I do encounter some problems. Some of them have been mentioned before but have not been addressed so far. (I have deleted the other topics)
[ul][li]Pitch and Tempo in the song properties seem not to have any effect anymore.[/li]
[li]The number of prebuffered items in the Playlist doesn’t seem to have any effect. In the config app I have set the number to 5, still 9 songs are prebuffered. [/li]
[li]Looking for a song or jingle with a specific duration is not possible anymore. No problem with this in v4 and v5.[/li]
[li]Synchronizing new songs takes much longer than it used to. R128 has not been ticked.[/li]
[li]Scheduling just one hour takes much longer than before. Scheduling a week is about the same time as in v5.[/li]
[li]Looking for a specific song in the database takes much longer now.[/li][/ul]
Prebuffer count: Unable to reproduce; I have set it to 5, and it does in fact prebuffer exactly 5 items (plus the 2 in the players, total 7). What happens when you start with an empty list, then insert items one by one, how far will the prebuffering go?
Search for duration: Fixed in b3605.
Sync: “Much longer” means how many seconds per song? Normalization and loudness is BOTH turned off? Actually performance should be roughly the same as in v5 when you don’t use any of these.
DB performance: I would like to try to reproduce these issues with your database, so can you please upload the database file somewhere? Also make sure you have confirmed the problems with the latest builds (early v6 versions had worse performance).
[ul][li]Tempo and Pitch: Thanks![/li]
[li]Prebuffer count: My bad, I’m using 4 players, that’s why still 9 songs were/are prebuffered and I didn’t notice any difference.[/li]
[li]Duration: Thanks![/li]
[li]Sync: Loudness was turned off but Normalization was on (like it was in v5). Still think it is slower than it used to be. I will give it a try with Normalization turned off.[/li]
[li]I will send you a link to my database by e-mail. At present I’m using v6.0.2 build 3603. [/li][/ul]
Thanks for your time!
Edit: It looks like Tempo and Pitch are still not having any effect in 3605. Looking for duration is fixed now, thanks!
Thanks for the DB file. The bottleneck is your large playlist history - going back all the way to 2009, must be faithful mAirList user - and SQlite being picky about the way the subquery is constructed that retrieves the last/next use information.
I have rewritten the SQL query now, can you check if build 3606 is now faster? Should effect both library browsing and the scheduler initialization part.
Regarding tempo/pitch, can you double-check if its enabled in the config (audio settings -> general)?
Strange, I have been using mAirlist since summer of 2013 and my first playlist dates from 08-2013. Nevertheless I consider myself a faithful user
I’ll check build 3606 asap and will let you know accordingly.
Tempo and Pitch was not ticked in the config app. It was in v5 as far as I remember and I assumed it would still be ticked in v6 after the migration. So I guess this is solved than. Again, I’ll check this too as soon as I am at home.
Thanks again for your time Torben, really appreciated!
Just checked build 3610 and it’s as fast as it used to be! Thanks Torben!
Pitch and Tempo is working too! (after I ticked the right setting in the config app ;))
- and SQlite being picky about the way the subquery is constructed that retrieves the last/next use information.
