Ah, I now realize that I need to use the buildme.sh in vendor, a whole
different ball of wax. I've got that built now. Is there any way to
unravel this so that it uses the dependencies from the OS rather than
compiling from source? Maybe the new versions of these libraries don't
need the
Me three. I've built it before and journeyed down the rabbit hole of
dependencies, not too excited about doing it again. Maybe I'll setup a
virtual machine so I can use it to build it the next time.
rpress's Profile:
So I ran the buildme.pl script, and it was successful but I still get
the Perl errors upon startup. It looks like there are binaries in
/usr/share/squeezeboxserver/CPAN/arch/5.18/x86_64-linux-thread-muti/auto
and there is no corresponding 5.20 folder. These binaries are in the
Logitech git
Gurney wrote:
Hi rpress,
Sorry, I'm not fit with compiling. Could you describe how to build the
driver?
I'm not sure whether it builds just a module or a full blown kernel.
Thanks a lot!
It can be built either way. To build as a module you need the exact
kernel headers and config
The driver you need is on my github, you shouldn't need anything else.
It should work with Raspberrry PI as it was designed for this in the
first place.
With the power sequence, I did not do anything special. But now that
you mention it I see the SSD1322 datasheet mentions the sequence. The
Triode wrote:
I've added a vis branch to my squeezelite and jivelite repos which adds
visualizer support. Its based on your work, but with some changes to
the shared struct and recovery from one or other processes restarting.
Could you try it out? [Doesn't include your skin, but includes
davidismynaim wrote:
how would this play on your display, if cool, I might find the time to
create all 25 positions, but dont want to do it if it does not look
right!
Hey thanks! I'll see if I can try this out in the next few days.
gorman wrote:
Considering one of the main disadvantages
JJZolx wrote:
Damn. I think I'd design another case.
I'm certainly tempted to go that route, but I already made three
components (two amplifiers and a DAC/DSP) that are in the same size
case. There is a smaller VFD from Noritake, maybe I will try to sell
the large VFD.
Anyone who wants to use the OLED display can also buy it here:
https://www.digilentinc.com/Products/Detail.cfm?NavPath=2,719,1084Prod=PMOD-OLED2
It's the same screen on a different carrier board than the one I have.
To run it as SPI a jumper wire must be installed but otherwise it looks
like it
I received the Noritake display, unfortunately the grayscale one is
discontinued. It's too big for my case! I didn't pay close enough
attention, it's about 10mm too wide. It's big and beautiful, there is
something indeed special about a VFD display. The drivers are working
and the display is
Pascal Hibon wrote:
Great work!
That seems like a big screen too. Which of those displays you tested has
your preference?
Yes the size is good, it would look good in a 2U case; that's what I'm
doing, one of the HiFi2000 Galaxy Maggiorato cases in 2U height, 1/2
width.
I only tested with the
I have a preliminary driver for the FTDI chip. It is working just fine,
about 60 fps, very smooth; CPU usage is low as well. You can see in the
photo that everything is over USB.
https://github.com/presslab-us/ftdi_spigpio
15061
The adapter is a FT2232H one I had laying around, but I think
Pascal Hibon wrote:
If Im not mistaken, the VU meters on the Squeezebox 3 was also a
community effort and some people created nice VU meters for the Touch in
the past. So it is doable.
Can you post the images you already modified? Im willing to take a look
at it but cant promise that
Triode wrote:
Hi - visualisations definitely look interesting. I'm not near a linux
machine right now, but interested in merging into squeezelite/jivelite
based on this once you have something and I've looked at in more
detail.
For the squeezelite component do we really need to apply the
Thanks gorman. :)
I've updated my repos with the code necessary to get it all working.
It's not finished by any means but it's certainly workable for anyone
who wants to play with it. You can use the skin on a desktop PC just
fine, to get an idea.
I also have implemented the visualizations,
Thanks guys! Here is the display I am using now. I had to modify the
parts on the board a bit, it had some crosstalk problems; it looks
pretty good now, though. I don't know if this is the best solution for
everyone, due to the changes needed. Noritake has always had very good
quality so
Pascal Hibon wrote:
Can you elaborate a bit more on the parts modification of the Wandboard
?
Sorry, I meant the parts on the circuit board that is attached to the
OLED board. The crosstalk problem was in the image, where bright
pixels in a row caused other pixels to be darker. I fixed this
I do like the OLED, but VFD would be nice too!
http://noritake-vfd.com/gu256x64f-3900.aspx
This is nice and big (6.7 diagonal), I might get one of these to play
with too. The electrical interface is different than mine, but there is
a USB option. Or an adapter to SPI (like my OLED) is not so
The viewing area is 136x34mm (5.35x1.34) or 5.5 diagonal.
rpress's Profile: http://forums.slimdevices.com/member.php?userid=31544
View this thread: http://forums.slimdevices.com/showthread.php?t=98960
Well I have the OLED display working in Jivelite. You can see that the
skin is way too big! :)
15036
So I've decided for now to make a new skin rather than try to use the
old Boom interface. Hopefully the UI will work nicely with this aspect
ratio. The font rendering looks pretty nice with
Triode wrote:
There's no actual server support for greyscale rendering of the classic
interface. This should do everything a boom/classic will do except
scroll the text as I didn't add that to the server.
Yeah, when I did the empeg I saw that it uses one 32 bit word for the
32 pixels
Thanks Triode and Ralphy!
With a few more minor changes I have RetroBrowser working on Jivelite.
I modified the resolution to that of the display I plan to use at
256x64. The downside is the decreased resolution in Y (RetroBrowser
already doubles the pixels) and also there is no support for
Thanks for the replies!
RetroBrowser looks really interesting and I'd like to play with it. But
it doesn't work with Jivelite as it uses deprecated functions
addCategory along with other problems I imagine. Has anyone got it
working with more modern Squeezeplay/Jivelite?
It seems the
I'd like to do a Boom type user interface using the Wandboard and
Community Squeeze OS.
The hardware will consist of a 256x64 OLED display along with an RF
remote control.
The display interface with the SPI port will be easy enough; the remote
is USB. The software framebuffer driver needs
JimmyBondi wrote:
For the records: this is a HD44780 compatible display connected to the
Wandboard via USB and an lcd2usb interface.
Very nice! I will be working on an interface soon for the Wandboard.
You can see my thread below. Maybe you can answer with your opinion?
Okay I think I have them both fixed now.
rpress's Profile: http://forums.slimdevices.com/member.php?userid=31544
View this thread: http://forums.slimdevices.com/showthread.php?t=96306
Yeah try the packages I built and see how they work. I had to change a
bunch of stuff so it would compile right, the biggest problem being that
there was no audio.
rpress's Profile:
Here's a deb package I've build with Squeezeplay 7.8.0~9704, for amd64
(64-bit). It's working on my Ubuntu 12.10 with alsa audio, no changes
are needed. It also installs the icon and .desktop file so you can just
run it from Unity with no problems. Let me know how it works for you!
28 matches
Mail list logo