Hi all!
I'm trying to start with fruitbox.... I've watched youtube videos and it is exactly what I want to have. It's GREAT!!
When I try to start fruitbox I read "error while loading libraries: libvorbisfile.so.3: cannot open shared object file: No such file or directory"

I restart but I always receive the same error... I added some mp3 to check, I pointed to the mp3's folder.... but nothing.
Any idea??
Thanks a lot!!

I'm back from holiday - but, yes, I still have this problem and would love to try and find the cause of the problem. It still puzzles me why, with the test-button option, I can press buttons all day long and not have any delay, but run fruitbox normally and within a handful of presses / joystick movements I start to see really long delays (many seconds). It does respond eventually, so the event is not lost, just somehow queued etc. I can't tell if the pi's CPU is somehow busy with something else, but if it is already playing a song this just carries on normally.

I'd be happy to run some debug versions, but I would need the Jessie builds.

Likewise, it's the only thing stopping me from going live on my arcade machine with fruitbox!

Scally

Hi Mike - I'm hoping that you might still have some time to look at this delay problem? Just let me know if there's a debug version I should run (on Jessie).

Thanks!
Scally

Snap!
Been using the jukebox regulatory and until yesterday it's been fine and all of a sudden the lag reappears from nowhere....

Really need to get it sorted before the 16th as me and the wife are renewing our wedding vows and the jukebox will be providing the music for the after party....

Cheers
Jon

Hi Mike - I appreciate you may no longer have time to look into this. But I'm still very keen to see if the reason for the problem could be found, as I'm now very close to completing my arcade build. Having the fruitbox feature would be superb. I'm happy to run another test build if that could be done.

Hi all!
I'm trying to start with fruitbox.... I've watched youtube videos and it is exactly what I want to have. It's GREAT!!
When I try to start fruitbox I read "error while loading libraries: libvorbisfile.so.3: cannot open shared object file: No such file or directory"

I restart but I always receive the same error... I added some mp3 to check, I pointed to the mp3's folder.... but nothing.
Any idea??
Thanks a lot!!

Hi all!
I'm trying to start with fruitbox.... I've watched youtube videos and it is exactly what I want to have. It's GREAT!!
When I try to start fruitbox I read "error while loading libraries: libvorbisfile.so.3: cannot open shared object file: No such file or directory"

I restart but I always receive the same error... I added some mp3 to check, I pointed to the mp3's folder.... but nothing.
Any idea??
Thanks a lot!!

Can anybody help please? I'm totally stopped here

Hi. The program is telling you that it can't find the library "libvorbisfile.so.3". That indicates that one or more libraries may be missing from your Raspberry PI install. When you set up the software, did you follow along from the user manual? There is a line in there about installing dependencies.

Hi all!
I'm trying to start with fruitbox.... I've watched youtube videos and it is exactly what I want to have. It's GREAT!!
When I try to start fruitbox I read "error while loading libraries: libvorbisfile.so.3: cannot open shared object file: No such file or directory"

I restart but I always receive the same error... I added some mp3 to check, I pointed to the mp3's folder.... but nothing.
Any idea??
Thanks a lot!!

Can anybody help please? I'm totally stopped here

Hi. The program is telling you that it can't find the library "libvorbisfile.so.3". That indicates that one or more libraries may be missing from your Raspberry PI install. When you set up the software, did you follow along from the user manual? There is a line in there about installing dependencies.

Hi Mike - I'm hoping that you might still have some time to look at this delay problem? Just let me know if there's a debug version I should run (on Jessie).

Thanks!
Scally

Snap!
Been using the jukebox regulatory and until yesterday it's been fine and all of a sudden the lag reappears from nowhere....

Really need to get it sorted before the 16th as me and the wife are renewing our wedding vows and the jukebox will be providing the music for the after party....

Cheers
Jon

Hi Mike - I appreciate you may no longer have time to look into this. But I'm still very keen to see if the reason for the problem could be found, as I'm now very close to completing my arcade build. Having the fruitbox feature would be superb. I'm happy to run another test build if that could be done.

Thanks!
Pascal

Hello, I have the same problem. I built an Arcade machine and wanted to have a Jukebox. I use two DragonRise Inc Generic USB. The Retropie works together well, but at Fruitbox they have a delay of 30 seconds and more. If I connect only one DragonRise to RPi, the control will be greatly improved. If I plug two classic joypads into USB, Fruitbox works well.
Delay occurs when DragonRise only connects to RPi, but I create a button map using the keyboard.
I use RPi3, Retropie 4.4 (Raspbian Strech). USB audio (PCM2704 USB DAC), USB Keyboard.
Fruitbox start with command line or autostart.sh (Emulationstation).
Will someone help me?

Snap!
Been using the jukebox regulatory and until yesterday it's been fine and all of a sudden the lag reappears from nowhere....

Really need to get it sorted before the 16th as me and the wife are renewing our wedding vows and the jukebox will be providing the music for the after party....

Cheers
Jon

Hi Mike - I appreciate you may no longer have time to look into this. But I'm still very keen to see if the reason for the problem could be found, as I'm now very close to completing my arcade build. Having the fruitbox feature would be superb. I'm happy to run another test build if that could be done.

Thanks!
Pascal

Hello, I have the same problem. I built an Arcade machine and wanted to have a Jukebox. I use two DragonRise Inc Generic USB. The Retropie works together well, but at Fruitbox they have a delay of 30 seconds and more. If I connect only one DragonRise to RPi, the control will be greatly improved. If I plug two classic joypads into USB, Fruitbox works well.
Delay occurs when DragonRise only connects to RPi, but I create a button map using the keyboard.
I use RPi3, Retropie 4.4 (Raspbian Strech). USB audio (PCM2704 USB DAC), USB Keyboard.
Fruitbox start with command line or autostart.sh (Emulationstation).
Will someone help me?

Excuse my bad English, I'm from the Czech Republic ...

I hope that can provide a clue to the problem, but there are some other observations:
- When I put fruitbox into the test button mode, there are no delays at all for as long as it runs
- When I use the same setup for my arcade emulation, there are no delays at all (and this stresses the CPU/power supply quite a lot)
- The spec of the official raspberry pi power supply should be enough for the current drawn by these 2 USB controllers (as also shown by the fact there no problems with running the arcade)

I'd be more than happy to run some further debug versions or perhaps other tests whilst fruitbox is running.

Hello to all fruitboxers, and special thanks to Mike for this great work!

I am new to this forum and have limited experience with Raspis so far, so bear me for that and being no native speaker, my wording might sometimes not be clear enough or misleading for you English guys.

Ok, end of excuses

I am the unlucky owner of an original Wurlitzer OMT (princess), which was only produced in Germany, but now, as the German factory is closed, my Princess is at the end of its mechanical life and I decided to give it a new life 2.0 beig powered by electronics and software instead of mechanics which tend to break after extense use (at least my opinion as being an electronic engineer). So I was constantly looking for a smart solution which comes close to the old look and feel of an old jukebox. It seems that fruitbox is the one which has all the features I am going to implement.

Before I start rebuilding my machine I have three questions which I could not find answered so far (if I haven't overlooked something):
1. Is there a limit for the number of music files which fruitbox or the power of a Raspi 3B+ can handle (smoothly)?
2. What tagging is required or recommended to get all music files displayed in the right manner?
3. Is there a chance to install fruitbox in a dual or multiboot environment (SD card, USB-drive ..) -> I would like to have access to my NAS server via Volumio or RuneAudio

Hello to all fruitboxers, and special thanks to Mike for this great work!

I am new to this forum and have limited experience with Raspis so far, so bear me for that and being no native speaker, my wording might sometimes not be clear enough or misleading for you English guys.

Ok, end of excuses

I am the unlucky owner of an original Wurlitzer OMT (princess), which was only produced in Germany, but now, as the German factory is closed, my Princess is at the end of its mechanical life and I decided to give it a new life 2.0 beig powered by electronics and software instead of mechanics which tend to break after extense use (at least my opinion as being an electronic engineer). So I was constantly looking for a smart solution which comes close to the old look and feel of an old jukebox. It seems that fruitbox is the one which has all the features I am going to implement.

Before I start rebuilding my machine I have three questions which I could not find answered so far (if I haven't overlooked something):
1. Is there a limit for the number of music files which fruitbox or the power of a Raspi 3B+ can handle (smoothly)?
2. What tagging is required or recommended to get all music files displayed in the right manner?
3. Is there a chance to install fruitbox in a dual or multiboot environment (SD card, USB-drive ..) -> I would like to have access to my NAS server via Volumio or RuneAudio

Kind regards
Raimund

Hi Raimund,

Welcome to the group.

1. As far as I know there is no real limit to the number of music files. I have seen that discussed by the developer in another post on this group and the number tested was quite high.
2. It depends on what mode or modes your planning on running the Fruitbox in. At a minimum you'll want Song Title and Artist. If you are going to do album mode, then you'll also want album title. The documentation is a good place to find info on what MP3 tags are available for use.
3. I have no experience with multi-booting the Pi. Someone else would have to speak to that.

Using your old Wurlitzer to house your Fruitbox project sounds like a great idea. Good luck.

Thank you Steve for the quick reply.
Will continue reading all pages of this long thread (just made half of it so far).

The project is not absolutely dependend on the dual boot - but that might be a nice enhancement as both Volumio and RuneAudio not only support accessing my complete music database on the NAS (ca. 100.000 titles) but come with other nice features like internet radio or Spotify.

So booting into these applications without having to swich SD cards is my goal. And, if possible, I want to get rid of booting via SD card as for me SD cards are not very well treated by the RaspBi - at least my experience although I tried to use "safely" powering off. From time to time the RaspBi didn't detect the SD card and I had to rebuild it from scratch. Maybe SD card brand specific, but I used "officially" tested compatible brands.

I expect that the Project will take a while as I want to modify my jukebox without having to change too much of the original outfit. Will report progress from time to time, but am sure that I will also have to come back with new questions.

First of all I'd like to apologise for my lack of responses over the last few months or so...I am currently in the middle of a career transition (through redundancy) and my priority has been trying to concentrate on that.

I'm still very much interested in supporting fruitbox, and am still aware of the lag issues with the Dragonrise USB controllers. As far as I recall the last debug information we obtained suggested fruitbox wasn't introducing any lag, so further investigation is needed, potentially outside fruitbox (maybe PSU related...when fruitbox is running properly rather than in button test mode it stresses the GPU more so could potentially draw more power). So I will have a think about that. As the source code is available on GitHub anyone with C++ and Linux input device handling knowledge who would like to cast their eyes over the input source code to look for potential issues would be much appreciated

To answer a couple of the later questions:

Regarding the number of MP3 files fruitbox supports, the only limit is the size of the RAM and non-volatile storage; the initial construction of the database will take longer the more MP3s you have, but subsequently accessing a song in the database takes the same time (and is virtually instantaneous) regardless of the size of the database and where the song is in the database, due to the way the songs are indexed using a look up table.

Regarding which tags are required; well that depends on the skin. Specifically which tags the songs are sorted by (SortSongsBy config parameter), and what status information you want displayed ($variables in any status Contents files). I personally pre-process my MP3 files through the Windows program "mp3tag" and make sure at a minimum that song title and artist are correct.

Finally I'd like to add that it's great to see fruitbox still being discovered by new users and all the wonderful projects being created . On a related note, if you've designed any skins would you consider sharing them? Just let me know and I can merge them into the GitHub repo. The skins I have already made were to be honest a bit rushed and knocked up only to demonstrate and test the basic features of fruitbox. Given a bit more effort and artistic ability, I'm sure some of you talented souls out there could produce some real beauties!

Thanks for all the hard work you have put into this for us Mike and all the best with your future employment. Regarding shared skins if anybody has created a 100 selection skin similar to this one that they would like to share it would be much appreciated

My own Wurlitzer project made some progress over the last days. I could remove all mechanical parts and cables without damaging anything. Sometimes it was a bit tricky, but eventually all came out and now I have plenty of space for the modification.

I will use a 10.1" touchscreen to replace the original cardbox. As the slot of the cardbox is wider than a wide screen I had to think of how to fill up the space. Well - this gives room for some control buttons (e.g. pause, skip, shutoff, autoplay etc.). So i printed two boxes to close the gap left and right of the slot and house the control buttons.

As I wanted to reuse the original keypad (selection keys) of my Wurlitzer, I used an idle teensy 3.2, which also handles the extra control buttons. Tests are promising, but I ran into a problem with the given skins, which Mike has provided (thank you again for that great stuff). All the skins are alphanumerics while my selection pad only comes with numbers. To change the software is no issue and already tested with the numeric keypad, but I need adjusted skins which only come with numbers instead of alphanumerics. So instead of A1 to E4 (on Wurly) I would need 11 to 54.

Question for Mike: Is there a chance to easily change the alphanumerics with numerics? My graphic design capabilities are stone age level ...

As it is very late in my location right now, good night to all of you. Will post some work in progress pictures tomorrow.
Raimund

As promised last night some pictures of the work in progress.
The change from alphanumeric to numeric-only selection skins is solved. My son is familiar with Photoshop and could help me with that.

The first pictures show the result of the slaughtering process with an almost empty jukebox after having removed all mechanical items of the playing and record selection units.

Then a picture which shows my PI-fruitbox connected to the original numeric keypad being translated into USB keyboard language by a Teensy 3.2. I know, it might be an overkill, but the guy was unoccupied anyway and now has a meaningful and important new job. Will see how I can persuade the Teensy to care about starting up and shutting down my Wurlitzer 2.0. Maybe someone of the community has already done something similar to ensure especially safe shutdown process and not killing the SD card file system and could point me into the right direction. The mini keyboard will be used as remote control.

The last pictures show the wooden frame which I constructed as a 1:1 copy of the selection slot where the selection box with the record cards was located in the original Wurlitzer. Now a 10.1" touch screen will be mounted instead, with two spacers left and right as the slot is much wider than the touchscreen. Gives me the opportunity to place some additional control buttons and a power button. Yet to decide the colour of the buttons which will be lit when the jukebox has been started.

On the software side I am currently using Raspbian in a dual boot system (PINN based) running as second OS Volumio - but might not be the final version. Most likely I will stay with Raspbian lite only and if there is a need to access my NAS with the complete music collection, DS Audio will be my friend via Chromium browser.

Next steps:
- Mount the new screen with the control buttons
- Change all dead neon tubes to led tubes (where possible and available)
- Mount and connect all electronic parts in a safe and protected manner (= "party vandalism resistant")
- Cabling (don't know yet if I will use the built-in amplifier or go with an Amp2)
- Prepare jukebox music database on a separate drive, ensuring that all tagging is ok
- Install a safe power up / shutdown process
- Automatic booting into fruitbox with optional user intervention to boot to Raspbian desktop (if possible at all)
- Planning to use the built-in credit system (new job for little Teensy)
- Planning to use the built-in 7segment display (previously used to show remaining credit) as a countdown counter for remaining songs in playlist / queue -> might be a real challenge, will see.

- Last but not least and the most important part of the project: ENJOY my WURLITZER PRINCESS 2.0 !!

Regarding the skin modification, if your son is on the case then great but I am happy to do the change if necessary. For your information there is a foreground.xcf in the Wurly skin directory which, although not used by fruitbox, is the original artwork file used to create foreground.png which contains the selection codes. As far as I remember foreground.xcf contains the select codes in separate layers so it should be trivial to edit them rather than try and modify the png file.

Regarding the seven segment display, fruitbox can help in this area if you create a [status] Output file with the information you want to display. Then you'll need to read this file and drive the display using a separate program. I think this has been discussed earlier on in this forum.

Cheers
Mike

Last edited by fruitbox on Mon Nov 19, 2018 7:39 pm, edited 1 time in total.

thanks for your advice and I am happy, that you still care about your fruity baby.
Hope that you could master the first challenges in your new job and everything works out as expected.

Will have a look at the .xcf file(s);
When the next steps are done, I will care about the status output file - maybe I will use $COMING_UP_NUM_SONGS, so this information is visible at a "chair distance" and can trigger the listeners to give more credit when the queue is reaching the end.

My plan is, to use the Teensy for parsing the text and handing the information over to the 7 segment display. I am a bit experienced in Arduino programming, so I am confident that this will work.

Today my HifiBerry Amp2 arrived and I can start to test it in the next days. Most likely I will use an old 19V/5A power supply for that - depends on not causing sound issues - I am old school and in the old days switched power and hifi audio was a no go; but maybe today's circuits can live wit switched power supply.

One question: Do you or another reader have a good advice what is best to safely shutdown / power up the Jukebox?
My goal is to use only one LED lit momentary push button for powering the whole jukebox. I think that Steve (@shhammer5634) mentioned in a previous post that he is also using a Teensy 3.2 to translate button presses and wanted to create a safe shut down process using the Teensy mastering the timing. Maybe Steve, if he reads this, could post his solution here.

Will also test this week, how to benefit from my Synology NAS.
My plan is, to use it as music source (with a special folder, specified for fruitbox) and as backup destination/host.

Mike, do you know if it is possible to automatically jump from Raspbian Desktop to start the CLI based fruitbox? I remember that there was some kind of discussion about that but I also read that there are different approaches and Linux experts seem to dispute the different methods (at least, in which startup folder the script/command lines should be stored. My linux level is still scratching the ground, but will try to shoot my knowledge up.

OK, let's jump back to my project. Will report when next progress was made.
Raimund

I know about the shutdown button which I currently make use of in the test envirionment.

My question primarily aimed to a shutdown procedure including shutting down all peripherals and ensuring that the next power up is also managed safely. No problem, I will find out and test, what the best solution is - will test all scenarios I have found in the internet so far. My idea was to gain a bit time in the project by having somebody to share some experience about the do's and don'ts. When I have found a proper solution (including the "desktop" starting point), I will share it here, so that others could benefit from my experience then.

My plan is to have a jukebox running "as is" as long as there is no active user intervention during boot up - so that a 5 year old kid could start and finsh a jukebox session.

Whenever I am in the mood to launch a Spotify session via Volumio (the second OS which I have installed), I like to interrupt normal boot-up sequence and start Volumio accessing either Spotify or my complete NAS music database to have access to all my music. I am close to that right now, but the automation of booting into fruitbox w/o any user interaction is the missing piece yet.

Good night to the world - it's dark and cold in Germany right now.
Raimund

@Mike: Thinking of future enhancements -
Is there a way already today to display current playing title together with the artist, scrolling from right to left after x seconds ?
Or: is it a feature which requires a lot of programming for you to get it into a next version - if you plan any?

@Mike: Thinking of future enhancements -
Is there a way already today to display current playing title together with the artist, scrolling from right to left after x seconds ?
Or: is it a feature which requires a lot of programming for you to get it into a next version - if you plan any?

Raimund

Hi Raimund

There's no support currently for scrolling text. There's a condense option in the text parameter list which allows long strings to be squashed to fit into a specified width to allow all the characters to be visible. I may add text scrolling in a future release (it's something I have thought about in the past)