Hi Scally
fruitbox version 1.14 for Jessie is now on GitHub
Cheers,
Mike
Hi Scally
Do you have an update on this?KGP2005 wrote: ↑Sun Feb 03, 2019 12:34 pmHi Mike
I know you help alot, and i also just hope to can fix this error. I have been looking forward for some time to start "my" project jukebox after i find your videos on youtube.
It was a dobble tread, but i still get the error after i wrote, and you fixed it.
Kim
Thanks, now working....
Hi
I was able to install the update today. My arcade doesn't have a keyboard, but by chance I discovered that by typing the config-buttons command into my PC's Putty window it started up on my arcade machine, which was a bit of luck. I had to delete the original button file as it caused the new version to crash, but it then recreated it ok when running the config-buttons.
Glad the new release has fixed your delay problem. I wasn't exactly sure what the issue was, but I did notice that the DragonRise controllers produced a vast amount of Z-axis analogue joystick events, from the looks of it due to a noisy analogue signal from the stick. In the release of fruitbox up to 1.12 the input events were handled by the Allegro library, and I suspect it was being swamped by these events. The re-coded input handling in release 1.14 no longer uses the Allegro library, and I filter out joystick events I don't need and this has appeared to remove the lag.
I deliberately didn't mark "Key" button events with a device ID (like I do with the Joystick (ABS) events) because I assumed Key type buttons generating the same event code would like be to treated as the same. Obviously I was wrong! So I have changed it as requested, and it's available in release 1.15, coming soon.Scally wrote: ↑Sun Feb 10, 2019 12:57 pmHowever, I have 2 of these USB controllers plugged into my pi, and I noticed that although the joysticks are identified separately, e.g. as 0 0 1 and 1 0 1 for left on each, the buttons have duplicate numbers, so my player 1 button 0 has the same code (e.g. 292) as the player 2 button 0, so I am unable to assign different functions to each side (which I intended to use as A-B-C and 1-2-3 functions). On your version 1.11 they did show up separately, so I wonder if this is something you could look into?
If you have upgraded from release 1.11 to 1.14 then you need to also update your skins, because in release 1.12 I changed the way the select codes are specified in the skin config file. Please see the below post for details...Scally wrote: ↑Sun Feb 10, 2019 12:57 pmFYI, I only updated the executable, no other files, in case that matters.
Then, on my WallJuke skin, I also noticed that the skin shows the labels as A1-4, B1-4, but when I use the joystick to move around, the bottom right status box shows the labels as A0..9, B0..9, so doesn't match the skin. Given than I only have 6 buttons for each player, it would be great to match the A1-4 labelling. I didn't spot anything in the skin cfg file, but maybe I missed a statement somewhere.
Code: Select all
# .asoundrc
pcm.!default {
type plug
slave.pcm "hw:Loopback"
}
pcm.loopin {
type plug
slave.pcm "hw:Loopback,0,0"
}
pcm.loopout {
type plug
slave.pcm "hw:Loopback,1,0"
}
Is it ./fruitbox --config-buttons, because that not working,fruitbox wrote: ↑Thu Feb 07, 2019 3:51 pmHi
You have to configure the correct buttons for touch input rather than keyboard, so run fruitbox with the --config-buttons option and follow the instructions. In your case, just press the screen each time fruitbox asks for a button you want to use in touch mode... any other buttons you don't need for the skin just press the ESC keyboard key. When it has finished, fruitbox will create a file called fruitbox.btn which it will use in the future. Now run fruitbox again normally (ie. without the --config-buttons option) and it should all work ok.
Please read the user guide if you are unsure.
Cheers
Mike
Code: Select all
./fruitbox --config-buttons
When runningrpt007 wrote: ↑Tue Feb 12, 2019 2:45 pm@KGP2005:
I hope I understood your issue - if not come back with more details.
Looking at your command it is not clear to be seen, if you have one or two "-" after "./fruitbox" -> you need two "-".
Make sure that you are in the correct starting directory:
In my case it is: /home/pi/rpi-fruitbox-master/
Then you start the button configuration withIf you are logged in as "pi" you will have sudoer-permissions and don't need to have "sudo" in front of a command - but it won't hurt anyway.Code: Select all
./fruitbox --config-buttons
Assuming you are coming from Windows -> linux OS is much more strict (straight) compared to Windows.
So make sure you follow the fruitbox user guide precisely.
Cheers
Raimund
Code: Select all
./fruitbox --config-buttons
Hi
Hi Mikefruitbox wrote: ↑Tue Feb 12, 2019 9:33 pmHi
Yes, fruitbox supports a mixture of button types, so you can have touch, GPIO, joysticks and keyboards all at the same time. You need to run fruitbox as sudo when configuring or testing buttons, and if using GPIO in normal mode. If you look closely when you got the mmap error message it gave you a clue
Regarding the X11 error, I'm not 100% sure about this but it could be that you are launching from the desktop and not a pure command line as I recommend.
Cheers
Mike
Code: Select all
sudo ./fruitbox --config-buttons
Code: Select all
sudo ./fruitbox --config-buttons
Hi,
Just typeKGP2005 wrote: But where or how can i see that its mounted?
Code: Select all
sudo ls /mnt/usb/
Thanks Mikefruitbox wrote: ↑Fri Feb 15, 2019 4:25 pmJust typeKGP2005 wrote: But where or how can i see that its mounted?which should show you what's on it and hence if it's mounted.Code: Select all
sudo ls /mnt/usb/
Mike
Code: Select all
/mnt/usb/Music/Music
Code: Select all
/mnt/usb/Music/Music/
Sounds like a great project Jason looking into doing something similar with a wallbox . I have 3 complete wallboxes sitting in boxesJasonLong wrote: ↑Thu Apr 19, 2018 5:35 amHi Mike,
Awsome work on fruitbox. Saw it and decided to go big with it. Bought a 1962 Wurlitzer 2610 that had been left outside in the rain for many years. Wouldnt even consider it a parts machine. But all the chrome and trim was in ok shape. So I rebuilt the wood cabinet better than the original and cleaned up the chrome and aluminum and transferred it over to the new cabinet. In place of the song title holders I put in a 23" screen, new speakers, a commercial amp and a raspberry pi running fruitbox. Created a skin that looks like the 2610 originally did with 100 songs on a page. Got the original buttons working with fruitbox no problem.
My question is (and sorry if its been asked before) is there any way to exclude a button from the song database build? i.e. the 2610 has no I key its A through H and J and K. Guess they did that so no one confused the I with a 1. The issue I am having is I had to set up button j as i and k as j so that the song selection would work correctly. Now in the selection part of the skin pressing j displays i. Is this just a matter of using $IF_BUTTON_I_PRESSED in the selection part of the skin to bandaid it or is there another solution? Not entirely sure how the displays work yet. I have been focused on everything else. If you want a copy of my skin or a screenshot let me know. Id be more than happy to share pictures of the build if anyone is interested.
Thanks
Jason