Winamp For Android 2.0 Beta discussion

JMullins · 17th March 2013, 06:01

One reason is that it assumes that Androids media engine will not see though the attempt at disguise. For instance chrome has no problem properly rendering a gif named as a jpg. It looks at the file header and understands what it really is. It also assumes that the file extension will never be used by another app and confuse something even worse. It would also tend to make it difficult if you wanted to edit the album art (no I don't know why you ever would but ...). Then there would be the issue of having not one, but multiple phoney extensions to cover all of the possible formats. So for me a better solution is to use the os and its features as they are designed. Putting the artwork in a subdir resolves those issues I said before, without messing up any other apps. Not to mention that it is a fairly easy solution that would take very little effort to implement and test.

Your example of the filepath is correct. I was just being lazy. Do not forget that any time a folder art is created and the artwork copied in a .nomedia should also be created that is what would keep the artwork out of the gallery while still being available to WFA. (I will bet that it will not take very long for other developers to notice and start using it also.)

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

17th March 2013, 06:01	#11
JMullins Junior Member Join Date: Feb 2013 Posts: 30	One reason is that it assumes that Androids media engine will not see though the attempt at disguise. For instance chrome has no problem properly rendering a gif named as a jpg. It looks at the file header and understands what it really is. It also assumes that the file extension will never be used by another app and confuse something even worse. It would also tend to make it difficult if you wanted to edit the album art (no I don't know why you ever would but ...). Then there would be the issue of having not one, but multiple phoney extensions to cover all of the possible formats. So for me a better solution is to use the os and its features as they are designed. Putting the artwork in a subdir resolves those issues I said before, without messing up any other apps. Not to mention that it is a fairly easy solution that would take very little effort to implement and test. Your example of the filepath is correct. I was just being lazy. Do not forget that any time a folder art is created and the artwork copied in a .nomedia should also be created that is what would keep the artwork out of the gallery while still being available to WFA. (I will bet that it will not take very long for other developers to notice and start using it also.)