Hi @Wheaten
I probably won’t do any more development work on mpd_oled until the availability of the Raspberry P improves, or until a reasonable alternative emerges.
Adrian.
I did have some great ideas for a JSON based layout system, I’ve probably forgotten them all by now! I do intend to take a branch from mpd_oled dev and what magic I can do - Adrian can review it and see what features he likes! 
Adrian has already done all the hard work. Have no idea on timescale, probably when Pis are available again OR when I free up one of my other pis… In experiments I managed to get the artwork resized and converted into a monochrome image and it looked shite!
wel there a bunch of people using MPD_OLED with a pi and a new group using the x86 
I wrote quite a lot of code for configuration and customisation, but based on Hjson (the human json).
I realised that all mpd_oled was doing was monitoring sources of data (playback data, audio data, IP address, WiFi strength, etc) and displaying formatted data, and that it didn’t especially have anything to do with music players, and also that it could support displaying on multiple screens.
The configuration code I wrote was to support compiled plugins, which could be data monitors or display components. The configuration file could then be used to enable monitors, and specify components to display the monitor data at a location on a particular screen. I got quite far with it!
the day is not over yet
It’s a fun project, so I might return to it.
1 Like
Already did the difficult part. 
Running on x86
Only showing CAVA
Added a max hold to CAVA.
Sounds like next level shit! 
Trouble is when you’re developing for yourself it’s easy to get feature creep and then lose interest when the going gets tough, especially when you have the continued maintenance of the stable version of mpd_oled to look for.
Thoughts for another day: you would’t need human json for configuration if there’s a web based configuration tool where the user can configure the screen themselves in a browser! (no need for edit any files then)
1 Like
That’s the great thing about mpd_oled is that it’s so easy to change it! Easy for me to say as I’m a developer… 
1 Like
No, you’ve done well to customise it yourself! 
Most people wouldn’t bother but if you know a little bit of programming and there’s some feature that you really want it’s possible to change it. A few people have created their own branches of mpd_oled on github. 
Am loving your changes though! 
I didn’t take any pics of my version that did album art
indeed, only bottleneck is C.
last time I did C was 2003. Then a lot of other languages came by. And it’s very trouble some to code as I am trying to insert pieces of JS, Python, VB,…
But is gets me of the street…
i did the album art to, with Python. But without greyscale it looks like some white blocks. i expect that Metellica (the black album)
or The Beatles (The white album) looks acceptable.
This evening I will try to get GPIO working together with i2c. So far no success as GPIO ports keep reporting locked/busy.
So I can add a switch for the display lay-out while playing.
-L <val> Layout type cava: t - trackinfo (default), n - No trackinfo, CAVA only
- Track info + CAVA
- CAVA only
1 Like
You can even call http://localhost/api/v1/getQueue to get the queue in a list…
No it’s just for the play display. Data is already present. It just switching between:
I just mean it could be an extra option for mpd_oled, i.e. you could have page that has a full size equaliser, another for current queue, another for clock, etc… What else could you have? Pie in the sky thinking…
Aha, got you.
A bit stuck on calling MPD_OLED with the different parameters.
Got GPIO detection running, but the while loop keeps aborting after one run.
need some digging to do
I’ve just bought a Wyse 3040 from eBay so I can play with the big boys! 
1 Like
wrong place to buy from 
What did you pay?
1 Like