m4a container can be both lossy and lossless
Posted: June 8th, 2013, 14:14
Hi,
I found a minor bug with the file symbols. The m4a extensions show up with the yellow icon, which indicates lossy format, however m4a is a container which can have both. In my case it's lossless ALAC, and the resonic player knows this actually when reads the Hz, bit depth, bitrate, etc info from the file.
I guess there is no easy fix for this, because if the player needs to look into every file to tell if it's lossy or lossless, then it would hurt the performace.
I suggest the following:
- Introduce a new symbol for containers which can have both lossy and lossless audio. This symbol would match both lossy and lossless filtering criterias and could have half blue/half yellow icon, or gray, or whatever
- If you are currently working on the library support, then I guess you are doing some kind of database, where you put all the data for the indexed files. You might consider to have a lossy/lossless field in the database, so we can filter correctly and show the correct symbol for these problematic files, if they are indexed already. (I don't know if the folder browser will actually use the library database or not, but even if it doesn't, we can benefit from this field in the libarary browsing mode)
I hope I was clear...
I found a minor bug with the file symbols. The m4a extensions show up with the yellow icon, which indicates lossy format, however m4a is a container which can have both. In my case it's lossless ALAC, and the resonic player knows this actually when reads the Hz, bit depth, bitrate, etc info from the file.
I guess there is no easy fix for this, because if the player needs to look into every file to tell if it's lossy or lossless, then it would hurt the performace.
I suggest the following:
- Introduce a new symbol for containers which can have both lossy and lossless audio. This symbol would match both lossy and lossless filtering criterias and could have half blue/half yellow icon, or gray, or whatever
- If you are currently working on the library support, then I guess you are doing some kind of database, where you put all the data for the indexed files. You might consider to have a lossy/lossless field in the database, so we can filter correctly and show the correct symbol for these problematic files, if they are indexed already. (I don't know if the folder browser will actually use the library database or not, but even if it doesn't, we can benefit from this field in the libarary browsing mode)
I hope I was clear...