LCD music display

Legible notes that don't cost a fortune

Similar projects worth following

The battle to display music has ranged from originally printing & taping hundreds pages together.

To the ridiculously large full sized TV.

To the ridiculously small & expensive tablet.

To the ridiculously small & cheap portable monitor.

The lion kingdom's goal was always a cheap & large 2 page display, replicating the original book format.  The easiest way to get there was 2 monitors in portrait mode.  Cheap portable LCD monitors finally started appearing in 2019, but they weren't really cheap enough to dedicate to nothing but showing music.

The lion kingdom's stock of obsolete laptops finally reached an age where they were never going to be used again & cheap HDMI to LCD converters abounded.  They were the venerable LTN156AT24 & LP156WH4.  They both had 40 pin connectors & LED backlights.  They both ran on 6 bits per channel.  The point had arrived where a dual 15.6" 1366x768 display just might be possible for under $100. 

1366x768 might be just enough resolution to replace paper if the RGB channels were used as pixels & the text was cropped.  It still remaned a much cheaper option than 1920x1080 panels.

The mane problems with these panels are they're really tall & the electronicals take a lot of space.  Besides the HDMI converter, they would need a raspberry pi, HDMI cables, & power supply.

Finding a suitable LCD controller is manely about finding one with the right cable.  All LCD controllers seem to do the same basic conversion from HDMI to a certain number of LVD pairs & they all have a header for powering a backlight inverter.  None of the converters outside China had a 40 pin cable.  They all had 30 pin cables.  The goog finally came up with a bang good match.

This is the same controller board sold by millions of sellers on, but it's the only one which specifically shows a matching 40 pin connector & describes entering a 1366x768 6 bit mode.  They're all based on the same Novatek NT68676 chip.

They also have different cables for connecting a converter board to a 40 pin or 30 pin panel.  Presumably they all connect to the same Novatek board.  Sadly, trying different cables by mail ordering from China could take years.

  • Using the Elan 33059 trackpad over USB

    lion mclionhead2 days ago 0 comments

    After 2 full days of hacking, the lion kingdom's recycled trackpad successfully communicated with the X server, thus becoming the world's 1st Elan 33059 to communicate with an X server with a PIC2450 as a bridge.

    The USB driver was originally ported from C to assembly by a younger lion when MPlab was for windows only.  Then it was heavily optimized & documented.  The mane effort was porting the improved driver back to C.  

    For the USB driver to work in C, it has to be interrupt driven.  The assembly language version only got away with polling because it was more efficient.  The source code is in  the elan.X directory of the repository, but it's probably not going to be used for annotations.

    It's obviously pretty large with the microcontroller board.  It would need a long 4 wire cable to move the micro somewhere else, but the pad  just senses motion.  To detect button presses, it would need a bundle of extra wires to the micro.  The micro could be moved to a surface mount board so it just has a USB cable.

    The T14_L pin shares the tapping bit so it can't be used.  The T19_RR, T20_RU,  T21_RL, T22_RD pins aren't sent to the status variable at all.  The 1 pin with exclusive use of a status bit is T13_R, so there could be 1 button.  Another idea for zoom is to use the page turn buttons for zooming when in annotation mode.  The GPIO buttons can't be sent to the X server though.

    It's still really clumsy to draw with.  It needs to be covered with a layer of plastic & placed on a table to be functional at all.  It glitches if any body parts get near it.  Using a stylus helps keep body parts away.

    The 1st enclosure was a big old sheet of coroplastic with everything on it.  Connected a button to the PIC18F2450's programming header.

    This could be used without a table.  With a stylus & the right acceleration setting, it was better than a mouse & probably equivalent to a trackball.  A trackball this accurate couldn't be paw held like the Elan.

    The crosshatch pattern on the Elan made it impossible to freepaw straight lines.  Sometimes, it starts permanently glitching until it gets a drop kick.  Freepawing text might have been slightly easier than a mouse, but it definitely needs a zoom feature.  

    The button

    is real bang terrible.  

    The lion kingdom recommends the MHPS2283V for a momentary pushbutton

    & the MHPS2283 for a manetained pushbutton

    They also make a MHPS2283N which is a momentary pushbutton with no click.  It's terrible.

    The trick with the MHPS line is they require a custom button & board mount instead of the screw mount of the bang terrible ones.  That's why they make 3D printers.

  • Annotation attempt 2

    lion mclionhead4 days ago 0 comments

    So the circular & hollow brushes proved useless & implementing XOR previews for a circular brush was more trouble than it was worth, so in keeping with minimalism, everything went back to a square brush.  Lions seem to recall PC Paint just supporting square brushes.  Helas, the hollow circles don't follow the contours of the XOR preview.

    Circle, disc, box, & line tools arrived.  Lions can appreciate why the Gimp doesn't have XOR previews of all the tools as PC Paint did.  The fast XOR preview entails writing every tool twice, handling corner cases for showing & hiding the XOR previews, making sure the XOR preview matches what's drawn.

    10 year old lions had no clue how to program an oval drawing routine & drawing ovals is still hard, in middle age.  Even the mighty koala paint didn't have an oval drawing routine, only circles.  The easiest way nowadays is to solve the pythagorean therum for every X to get Y on a circle, then scale the Y to get an oval.  To speed it up, it's done with a floating point lookup table.

    The result is the kind of blinking XOR cursors & line filled brush strokes that lions remember of PC Paint on an 8 Mhz Olivetti 24, but on all off 700Mhz.  Maybe it would have been faster on the framebuffer or using SDL.  The brush stroke routine is suboptimal in the limit.  Brush stroke & hollow circle definitely need improvements.  The XOR cursors are all Xorg routines drawing to the frame buffer.

    Instead of a full screen clear button, it has a filled box tool with 1 of the colors being erase.  That has greatly improved erasing to the point of almost completely replacing the erase tool.

    The line, oval tools improved annotating but it's still manely a nightmare.  The low resolution makes precision a lot more important, like it was in the days of 640x400.  Either it needs a zoom function, a way to lock lines on the axes, or a way to selectively decelerate the pointer.  A trackpad won't do the job if it's already hard with a mouse.  Lions believe a trackpad with stylus could be the best pointing device.

  • Annotation attempt 1

    lion mclionhead6 days ago 0 comments

    A pretty frustrating experience, to be sure.  It's nowhere near as easy with a mouse on a music desk as it was with a pencil or a mouse on a normal desk.  Line, oval, zoom tools might help, but drawing text without a keyboard is hopeless.  Another idea besides writing a paint program from scratch is to boot up the gimp every time the user wants to annotate, but it requires a keyboard & it's even slower.  It's pretty frustrating to not be able to go to a store & try out a trackball.

    The annotation system is a minimal drawing program based on PC Paint.  Vintage software has once again proven useful as the basis for a modern application.  Drawing programs have been the nemesis of lions ever since they tried to program one in childhood but never could finish it.

    The mane showstopper is event compression on the pi is non existent.  It seemed like a good idea to have PC Paint's XORed brush augmented with a crosshair, but it just sits & redraws single pixel mouse movements without event compression.

    The color palette ended up being the 16 original Commodore 64 colors rather than a modern color picker.  The rest is a simplified version of what lions remember of PC Paint.  Drawing is bitmap based.  There's draw & erase with different brush sizes.  There's no lasso, selection, fill, or polygon tool.  There is a foreground & background layer while the original scanned music is untouched.  There are a certain number of undo levels.

    Erasing large areas is pretty rough without a selection tool.  There is a large eraser brush to try to compensate.  The user has to hit the save button to make new annotations appear on both monitors.  It automatically saves when the user exits or loads a new file.

    Despite every effort, it composites the 2 annotation layers in every single page turn.  It would be pretty involved to make it selectively composite the annotation layers only if they're used.  The page turns have dropped back to 13 per second, with annotations & the background pixmaps required for any useful menu system.

  • Software

    lion mclionhead06/13/2021 at 05:37 0 comments

    Making a minimal confuser actually do minimal confusing is a lot harder than it used to be.  For decades, the raspberry pi foundation has labored to run as much as possible as slowly as possible.  With much coercing, it can be made to just run fvwm on X11.  The key commands are

    apt install fvwm

    xinit /usr/bin/fvwm2&

    /usr/share/fvwm/system.fvwm2rc has to be copied from somewhere else.  It needs an option in system.fvwm2rc to disable the reader's window border.

    Style "Reader" NoTitle, HandleWidth 0

    Sadly, the current versions of fvwm no longer support keeping a window on top.  That has to be done in the program.

    Then, there are commands to try to slow down the mouse speed.

    xinput --list-props "PixArt USB Optical Mouse"
    xinput --set-prop "PixArt USB Optical Mouse" "libinput Accel Speed" -1

    The lion kingdom believes the mouse speed still needs a kernel hack to be slow enough.

    The server pi needs to export NFS to the client pi so they can access the music files.

    The decision was made to finally make the Cinelerra toolkit a standalone library with the ability to strip out all its video editing features.  It works quite well as a minimal retro interface, only taking 18 minutes to compile on a 1B.  As simple as it is, it's still takes a beast to do all the listbox, textbox, & menu operations a toolkit has to do.

    Since it's not a dual head confuser, the mouse only works on 1 monitor.  It's a bit contorted to have a mouse 3 octaves away from the screen.  It definitely needs a mouse stand on top of the panel.

    Despite all the hype about a pointing device which can draw, annotations are going to slow page turns way down.  In its simplest form, every page would optionally have 2 annotation layers, a foreground & background.  Each layer would have 16 possible colors, including transparent.  The resolution wouldn't be able to use RGB subdivisions.  Annotations would go in a separate file with flat images & flags saying if an image was used.

    It needs to support 1/2 a page turn so every page can be shown on the screen with the pointer.  The client confuser needs to poll the annotation file for updates.  The annotation file needs to be in RAM along with all the music images.  The client would have to reload the entire file when it changed.  To speed this up, the annotation file can start with a table of contents, showing what revision each page is on.  The client can reload just the latest revision of 1 page.

    Then of course, the server needs a full paint program, 1/2 page turn buttons, draw, erase, color palette, layer, save file, brush size, brush type, but no undo is required.  The 2 layers need different color palettes.

    There's still a dream of just running it without RGB subdivisions, on the dual head 4B, with its horrible aliasing.  Page turns with annotations would be a lot faster.  The mouse would work on both screens.  The networking protocol, NFS, half page turns would go away.

  • Stand version 3

    lion mclionhead06/10/2021 at 18:06 0 comments

    A new batch of stands came off the printer.

    Featuring all new latches

    Much easier access to the electronicals.  Farther placement back.  Flaps to keep it from sliding forwards.

    New confuser placement.

    Plans continued for a pointing device.  All attention turned from trackballs back to an old fashioned mouse in the short term, eventually being replaced by a trackpad.

    So the Elan 33059 isn't documented anywhere, but it's similar to a more common Synaptics described on

    The ribbon cable pinout doesn't match, but the Elan version otherwise has the same signals as the Synaptics.  The test points are even labeled 

    TD - PS2 data

    TC - PS2 clock

    T13_R - right button

    T14_L - left button

    T19_RR - scroll right

    T20_RU - scroll up

    T21_RL - scroll left

    T22_RD - scroll down

    TN - ?

    TP - ?

    Source code is scarce.  The best example was

    There were comments about the source code working with an Elan chip.  It bit bangs the PS2 pins.  Sadly, a quick test showed TN & TP are not USB pins.  

  • Setup 1

    lion mclionhead06/08/2021 at 09:24 0 comments

    The fastest possible setup yielded this.

    A giant 500W Dell power supply made barely enough pixies to feed 3 raspberry pi's.  

    It was a bit weird to turn pages with the buttons.  It was hard to turn pages with the left paw, but anything was better than the ipad.  A 3rd button on the left side might aid the left paw.  Ventilation was worse.  It's going to be brutal in hot weather.

    It needs to be 5mm farther back.  The magnet holders need to be without walls so they can sit farther back.  There's a case for bolting it on the back so it can go a few inches farther back.  Maybe the viewing angle can be more horizontal.  Making it completely fold when not in use would require a major overhaul of the cables.

    The back needs panels to keep it from sliding forward.  The corners need latches.  The confusers all need to go under the instrument instead of on top of it.  Maybe that would free up enough space for a pointing device.

    As cramped as it is, it's a function of what $30,000 in annual rent can afford.  Want more space?  Pay $50,000 in rent or $80,000 after everyone moves back.

    The pointing device is the next big deal.  Selecting files without a GUI is really slow.

    There's not enough room for a mouse pad anywhere.  Alternative pointing devices have gotten nosebleed expensive.  The cheapest solution is the mighty $20 Perixx trackpad.

    It's 76x64mm.

    Good trackpads are hundreds of doll hairs.  Good trackballs start 3x more expensive than mice & a are bit bulkier than trackpads.

    It's been 25 years, but balls have retro appeal & lions remember having a better experience with them than pads.  Based on the memory, a trackball would be a better match than a trackpad for a stationary application.   All modern trackballs are just upside down mice with optical sensors pointing up.

    The best trackball is the $33 Kensington Orbit

    No dimensions are given, but it's as wide as a paw.  

    There is a thumb operated trackball

    But this would be impossible to draw annotations with.

    There is a lot of interest in reusing macbook track pads as standalone devices, but the track pads themselves are SPI devices connected by a very fine pitch ribbon cable to the mane board.  The brain that converts the keyboard & trackpad to a USB signal is on the mane board.  

    The touch pads extracted with the LCD panels have undocumented ELAN 33059 chips but appear to use I2C.  The internet has never figured out how to use these.

    There was a desire long ago to make a pointing device out of a webcam that tracked a blinking LED.  It might be too low in resolution & too consuming of space.

    Both trackballs & trackpads are harder to draw on than mice.  Given the need to draw annotations, using a phone as a trackpad may be the best option.  An interface which takes both a stylus & paw is a big win.  The phone can also show the recording interface.  There's a lot of adware for using phones as trackpads.  

  • Raspberry pi 4 busted

    lion mclionhead06/06/2021 at 04:41 0 comments

    The goal was to plug the monitors into the existing 4B which is used for sound processing.  Things were going well with the raspberry pi 1B on a single monitor, but the 4B does not support 1366x768.  The problem is it's a very uncommon mode in modern times so it was phased out in order to support dual HDMI.  

    They offered an explanation of the compromise:

    They do mention supporting a close 1360x768 resolution.

    There's no way to disable scaling on the Novatek NT68676, so 1360x768 always has aliasing which makes it worthless for showing text.  No scaled mode would allow individually addressing RGB triplets.

    It would have been a bad day for anyone who just spent $200 on portable monitors of 1366x768 resolution.

    There is a way to change the language which isn't documented anywhere.  That allowed lions to search for a non existent way to disable scaling.

    That leaves daisychaining the last 2 raspberry pi 1B's.   There were once 3, but lions unwisely stripped the HDMI header from 1 to minimize its footprint.  Many thoughts go through a lion's mind about the affordability of getting 2 new 1920x1080 monitors vs wrangling multiple raspberry pi's.  

    Relying on the sound processor to drive 2 displays & have enough clockcycles for sound processing always was a risky move.

    Xorg can be run in 8 bit mode to get the fastest page turns.  This requires adding another line to /boot/config.txt


    8 bit mode caused aliasing in the X direction, yet another unsupported mode.  The best it could do was 16 bit.


    Page turn speed vs depth:

    8 bit: 25fps

    16 bit: 25fps

    24 bit: 12fps

    Faster page turns may be possible by writing to the framebuffer directly, but 25 was good enough.

    With a simple network protocol & a bag of network cables, the 2 pages finally showed.

    Next comes a power system.  The combined panels draw 1.1A at 12V.  The PI's draw a few more amps at 5V.

  • Displaying the 1st page

    lion mclionhead06/04/2021 at 18:53 0 comments

    Rotating the framebuffer on a raspberry pi required editing /boot/config.txt & adding 


    to the top. 

    It's essential for the pointer to move in the right direction, since the lion kingdom plans on using a standard X11 pointing device.

    A growing list of configuration settings will be required to disable screen blanking & drive 2 screens.

    The Cinelerra toolkit amazingly compiled for ARM pretty easily.  Compiling Cinelerra for ARM would be problematic because all the 3rd party libraries are written in assembly language.  After a few pixel mangling functions, the text finally appeared.

    It was the 1st time a lion had a scanned piece of music in more than its original 12" height, on a practical display.

    A key feature ended up being splitting each pixel into RGB triples to get more vertical resolution.

    If all the pixels were white, it would be just 1366x768 instead of 4098x768.

    This version loaded all the pages from 300dpi PNGs, stretched, & cropped to fill the panel on the raspberry pi.  It was too slow to be practical.  The slowest step was decompressing the PNG files.  It needs to load an uncompressed image format which has already been converted directly to the framebuffer format on a faster confuser.  

  • Prototype version 2

    lion mclionhead06/04/2021 at 04:28 0 comments

    This one folded up.  It had clearances for cables.

    The cables may have to go out opposing sides when 2 monitors are side by side.  

    Alignments were a lot worse because loctite superglue doesn't set as fast as hobby glue, but it still managed to clear the buttons.

    The single latch was a disaster.  It needs 2 latches in the corners, but that's where the magnets are.

    The next task was displaying something useful, which would require native X11 programming because of the lack of clockcycles.  Tiny confusers running native software are still better than buying a $4,000,000 room to fill with tower PC's just to run a different language.

  • Prototype version 1

    lion mclionhead06/02/2021 at 06:09 0 comments

    The hardest part in an operation like this is the enclosure.

    Each panel would have its own stand.  The stand would attach by magnets & fold up.  It was too big to fit on the print bed, thus began the brutal experience of modeling & gluing 10 pieces.  The dimensional accuracy of a model split into many pieces is horrible.

    Tolerances were bad enough to keep it from folding up.  The wires took up a lot of space.

    The LVD cable needed the living daylights bent out of it to fit in there.

    The magnets held it on.  It needed a hair more clearance over the buttons.

    Viewing angle was as bad as expected.  It may end up being a single page if 2 pages are too far apart.

    Rear panel either came out too narrow or the LCD panel came out too wide.  Rear panel doesn't need a solid sheet.  LCD panel needs gaps to route cables next to the panel.  

    Might have to leave it unfolded & make a bigger cover.

View all 11 project logs

Enjoy this project?



Arsenijs wrote 05/25/2021 at 04:52 point

>>> The point had arrived where a dual 15.6" 1366x768 display just might be possible for under $100

Very much so! I'm compiling information on general reuse of these displays here: #All About Laptop Display Reuse , drop by our chatroom anytime!

>>> All LCD controllers seem to do the same basic conversion from HDMI to a certain number of LVD pairs

Yep! The controllers that you mention specifically, M.NT68676 boards, also need to be programmed with the right firmware to drive 1366x768 panels.

>>> describes entering a 1366x768 6 bit mode.

That sounds good, I didn't know that's what "LVDS mode" meant for these controllers, but it makes sense!

What I'd typically recommend is punching your panel number into the eBay search bar, in your case, you'd get this: . I went and checked - both of your panels have the same pinout, driving requirements and color bit mapping scheme, so if you buy 2pcs of this same controller, it should work with both of the panels. Searching for a panel-specific controller helps you avoid cable troubles, and in case of the eBay link I'm sending, it's also going to come out cheaper!

The second cable you're showing seems like the right deal - you definitely don't need a set of 14 different ones! =D However, you don't even need that cable if you're getting a panel-specific controller, since a panel-specific kit will be coming with the right cable already!

Nice project! Added it to #Laptop Display Things list =)

  Are you sure? yes | no

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates