03-10-2016, 05:49 PM
Am I correct that "loading all" always renders all the songs in the setlist?
It seems to me so since it takes quite a lot of time to load when I have many songs in a setlist.
If you just need a setlist for a set that's not a big problem because there rarely will be more than 20 or 30 songs in a set.
But since I got your advice I'm using the setlist as temporary editing pool for mass cropping. And it takes ages to load if I put > 50 songs in it.
Also if I notice an error in a song in the title or somewhere else and I edit it, it starts to load the complete setlist again.
Since setlists are usually played and used sequentially, isn't it possible and more efficient to render just a few and cache them (I read you reduced the caching in the new version) and render the rest in the background "on demand"?
It seems to me so since it takes quite a lot of time to load when I have many songs in a setlist.
If you just need a setlist for a set that's not a big problem because there rarely will be more than 20 or 30 songs in a set.
But since I got your advice I'm using the setlist as temporary editing pool for mass cropping. And it takes ages to load if I put > 50 songs in it.
Also if I notice an error in a song in the title or somewhere else and I edit it, it starts to load the complete setlist again.
Since setlists are usually played and used sequentially, isn't it possible and more efficient to render just a few and cache them (I read you reduced the caching in the new version) and render the rest in the background "on demand"?