Given that Helium 11 could see files that are not included in the library, I could use this to mass edit and prepare many and many new albums at once, shaping the tracks to my own standard.
This is something that I can't do with Helium 12, having to edit one album each time, resulting in a huge impact to my workflow. I don't know exacly what is the best way to achieve this. In fact I would like HMM12 to behave just as HMM11 do (seeing all files).
Not taken for now, if it will get more interest in the future we might re-review it, but at the moments other things needs to be prioritized.
>>Does it "break data synchronization" too? Just an idea.
Yes, it will break the data consistency, since the whole architecture in Helium 12 requires that all files are available in the database.
The tag reading engine can of course understand files which are not in the database, but all tools requires that the files have an id in the database at the moment.
In older versions of Helium it was different, no database existed from start, it was added in later versions.
If we should consider to implement some kind of view with offline support in Helium 12 it needs to be upvoted by many users since it is a time demanding and complex task to do, althought possibible of course.
Our main focus though is to improve database driven views and functions, because there we have the absolute strength.
This is currently not planned at the moment, since it breaks the data synchronization, something that caused problems in Helium 11.
There are other workflows (suggested, you might even find a better one) recommended in the documentation of how to work with Helium.
Also, please note that the Tag editor is, just like in Helium 11, optimized when working with files from a sole album (multiple CDs are of course supported).
That optimizations relates to the right pane (quickly fill common fields) as well downloading of data.