Support and General Use > Theming and Appearance Customization

Album ARt

<< < (2/5) > >>

bascule:
Part of it is that the patch may or may not be stable and/or not efficiently coded and no core dev has yet seen fit to commit it. In addition, it is often (perhaps almost always) used in conjuction with other, non-committed, patches such as scrolling margins.

Above all of that, a major upcoming (don't ask when ;) ) feature, metadata on buffer, will immediately render the patch obsolete, AFAIK, because there would then be a much better way of achieving the Album Art functionality.

Dr Schlong:
Thanks for clearing that up, btw I love the crossfade option!  

Nate!:
Somewhat off topic, but to clear it up for me.  The implementation of album art in the official build is dependant on two things, Metadata on Buffer and Viewports.  

Viewports, from what I gather, is how data gets displayed in a WPS.  Seems like the display is divided into sections and display data, i.e. track name, file info, and etc, don't overlap outside of their "section" of the display.  This should take care of the scrolling margins patch, multifont, and other similiar patches.

Metadata on buffer, is pretty self explanatory.  Sounds like it reads the metadata of a file into a buffer for extraction and use.   Information in metadata can include Album Art.

The viewport implementation is huge, from what I have seen in searching the forums.  It will determine precisely where text/images will get displayed at the pixel/cell level and how it gets displayed.  So all of the other patches will become moot.

Is this the jist?

NicolasP:
Although you seem to have gotten the idea, I feel like a few clarifications are needed.
First, album art (AA) is dependent on metadata on buffer (MoB), but not really on viewports. Without MoB, it's not possible to implement AA in a clean way, whereas viewports will provide more flexibility for WPS creators, but are not really related.

What Nate! said about viewports seems about right to me, although the concept is still not very well defined. It seems amiconn has a clear idea about it but doesn't explain it in very much detail. They are very promising but aren't needed to do a clean AA implementation.

MoB, on the other hand, is a real requirement: we put track metadata on the main buffer (currently it is only used to store compressed music data waiting to be decoded). This will remove the limit of what quantity of metadata we can store for a track, and therefor allow crazy things like album art. In no way it makes the AA patch obsolete. The patch will be practically the same, only the location where it takes the bitmaps to be displayed will have changed, that's all. Without it, we'd have to allocate a fixed amount of memory for bitmap storage, and for some it would be wasted, whereas for others it would be too small.

bascule:

--- Quote from: NicolasP on March 22, 2007, 01:51:09 PM ---...In no way it makes the AA patch obsolete. The patch will be practically the same, only the location where it takes the bitmaps to be displayed will have changed, that's all...
--- End quote ---
Thanks. I stand corrected.

Navigation

[0] Message Index

[#] Next page

[*] Previous page