KToghia
Posts: 1
Joined: Tue Dec 20, 2016 6:39 pm

Another Fruitbox and ELO touchscreen

Tue Mar 10, 2020 12:46 pm

Hello,

I've read through all the other users having issues. I have tried everything from reordering the event handlers so that the touchscreen was event0, I've run the evtest and output the startup. The screen by default comes up as event3 and is responsive. if I just use the button config option Fruitbox recognizes the touches as a mouse event. Any help is really appreciated. Here is what I have:

fruitbox v1.16 (Feb 17 2020, 15:28:38) by Mike Kingsley
A customisable MP3 Retro Jukebox for the Raspberry Pi.
-----------------------------------------------------------------------------------------------
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x4e7 product 0x20 version 0x100
Input device name: "Elo TouchSystems, Inc. Elo TouchSystems 2700 IntelliTouch(r) USB Touchmonitor Interface"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 272 (BTN_LEFT)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 2960
Min 0
Max 4095
Event code 1 (ABS_Y)
Value 2357
Min 0
Max 4095
Event code 40 (ABS_MISC)
Value 0
Min 0
Max 256
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1583843734.923476, type 3 (EV_ABS), code 0 (ABS_X), value 1917
Event: time 1583843734.923476, type 3 (EV_ABS), code 1 (ABS_Y), value 2785
Event: time 1583843734.923476, type 3 (EV_ABS), code 40 (ABS_MISC), value 40
Event: time 1583843734.923476, -------------- SYN_REPORT ------------
Event: time 1583843734.931460, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843734.931460, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1583843734.931460, type 3 (EV_ABS), code 40 (ABS_MISC), value 53
Event: time 1583843734.931460, -------------- SYN_REPORT ------------
Event: time 1583843734.939454, type 3 (EV_ABS), code 40 (ABS_MISC), value 65
Event: time 1583843734.939454, -------------- SYN_REPORT ------------
Event: time 1583843734.947455, type 3 (EV_ABS), code 40 (ABS_MISC), value 75
Event: time 1583843734.947455, -------------- SYN_REPORT ------------
Event: time 1583843734.959454, type 3 (EV_ABS), code 40 (ABS_MISC), value 81
Event: time 1583843734.959454, -------------- SYN_REPORT ------------
Event: time 1583843734.967457, type 3 (EV_ABS), code 0 (ABS_X), value 1918
Event: time 1583843734.967457, type 3 (EV_ABS), code 40 (ABS_MISC), value 82
Event: time 1583843734.967457, -------------- SYN_REPORT ------------
Event: time 1583843734.975457, type 3 (EV_ABS), code 40 (ABS_MISC), value 78
Event: time 1583843734.975457, -------------- SYN_REPORT ------------
Event: time 1583843734.983453, type 3 (EV_ABS), code 40 (ABS_MISC), value 72
Event: time 1583843734.983453, -------------- SYN_REPORT ------------
Event: time 1583843734.995454, type 3 (EV_ABS), code 40 (ABS_MISC), value 58
Event: time 1583843734.995454, -------------- SYN_REPORT ------------
Event: time 1583843735.003453, type 3 (EV_ABS), code 40 (ABS_MISC), value 46
Event: time 1583843735.003453, -------------- SYN_REPORT ------------
Event: time 1583843735.011453, type 3 (EV_ABS), code 40 (ABS_MISC), value 36
Event: time 1583843735.011453, -------------- SYN_REPORT ------------
Event: time 1583843735.019452, type 3 (EV_ABS), code 40 (ABS_MISC), value 30
Event: time 1583843735.019452, -------------- SYN_REPORT ------------
Event: time 1583843735.031455, type 3 (EV_ABS), code 0 (ABS_X), value 1917
Event: time 1583843735.031455, type 3 (EV_ABS), code 40 (ABS_MISC), value 25
Event: time 1583843735.031455, -------------- SYN_REPORT ------------
Event: time 1583843735.039454, type 3 (EV_ABS), code 40 (ABS_MISC), value 22
Event: time 1583843735.039454, -------------- SYN_REPORT ------------
Event: time 1583843735.083467, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843735.083467, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1583843735.083467, type 3 (EV_ABS), code 0 (ABS_X), value 1918
Event: time 1583843735.083467, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1583843735.083467, -------------- SYN_REPORT ------------
Event: time 1583843735.547456, type 3 (EV_ABS), code 0 (ABS_X), value 3093
Event: time 1583843735.547456, type 3 (EV_ABS), code 1 (ABS_Y), value 1865
Event: time 1583843735.547456, type 3 (EV_ABS), code 40 (ABS_MISC), value 31
Event: time 1583843735.547456, -------------- SYN_REPORT ------------
Event: time 1583843735.555446, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843735.555446, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1583843735.555446, type 3 (EV_ABS), code 0 (ABS_X), value 3094
Event: time 1583843735.555446, type 3 (EV_ABS), code 1 (ABS_Y), value 1863
Event: time 1583843735.555446, type 3 (EV_ABS), code 40 (ABS_MISC), value 43
Event: time 1583843735.555446, -------------- SYN_REPORT ------------
Event: time 1583843735.567441, type 3 (EV_ABS), code 0 (ABS_X), value 3095
Event: time 1583843735.567441, type 3 (EV_ABS), code 1 (ABS_Y), value 1861
Event: time 1583843735.567441, type 3 (EV_ABS), code 40 (ABS_MISC), value 56
Event: time 1583843735.567441, -------------- SYN_REPORT ------------
Event: time 1583843735.575441, type 3 (EV_ABS), code 0 (ABS_X), value 3096
Event: time 1583843735.575441, type 3 (EV_ABS), code 1 (ABS_Y), value 1859
Event: time 1583843735.575441, type 3 (EV_ABS), code 40 (ABS_MISC), value 69
Event: time 1583843735.575441, -------------- SYN_REPORT ------------
Event: time 1583843735.583439, type 3 (EV_ABS), code 0 (ABS_X), value 3097
Event: time 1583843735.583439, type 3 (EV_ABS), code 1 (ABS_Y), value 1857
Event: time 1583843735.583439, type 3 (EV_ABS), code 40 (ABS_MISC), value 80
Event: time 1583843735.583439, -------------- SYN_REPORT ------------
Event: time 1583843735.591440, type 3 (EV_ABS), code 0 (ABS_X), value 3098
Event: time 1583843735.591440, type 3 (EV_ABS), code 1 (ABS_Y), value 1855
Event: time 1583843735.591440, type 3 (EV_ABS), code 40 (ABS_MISC), value 90
Event: time 1583843735.591440, -------------- SYN_REPORT ------------
Event: time 1583843735.603441, type 3 (EV_ABS), code 1 (ABS_Y), value 1853
Event: time 1583843735.603441, type 3 (EV_ABS), code 40 (ABS_MISC), value 98
Event: time 1583843735.603441, -------------- SYN_REPORT ------------
Event: time 1583843735.611440, type 3 (EV_ABS), code 0 (ABS_X), value 3099
Event: time 1583843735.611440, type 3 (EV_ABS), code 1 (ABS_Y), value 1852
Event: time 1583843735.611440, type 3 (EV_ABS), code 40 (ABS_MISC), value 103
Event: time 1583843735.611440, -------------- SYN_REPORT ------------
Event: time 1583843735.619440, type 3 (EV_ABS), code 0 (ABS_X), value 3100
Event: time 1583843735.619440, type 3 (EV_ABS), code 1 (ABS_Y), value 1850
Event: time 1583843735.619440, type 3 (EV_ABS), code 40 (ABS_MISC), value 105
Event: time 1583843735.619440, -------------- SYN_REPORT ------------
Event: time 1583843735.627439, type 3 (EV_ABS), code 0 (ABS_X), value 3101
Event: time 1583843735.627439, type 3 (EV_ABS), code 1 (ABS_Y), value 1848
Event: time 1583843735.627439, -------------- SYN_REPORT ------------
Event: time 1583843735.635440, type 3 (EV_ABS), code 0 (ABS_X), value 3102
Event: time 1583843735.635440, type 3 (EV_ABS), code 1 (ABS_Y), value 1847
Event: time 1583843735.635440, type 3 (EV_ABS), code 40 (ABS_MISC), value 99
Event: time 1583843735.635440, -------------- SYN_REPORT ------------
Event: time 1583843735.647440, type 3 (EV_ABS), code 0 (ABS_X), value 3103
Event: time 1583843735.647440, type 3 (EV_ABS), code 1 (ABS_Y), value 1845
Event: time 1583843735.647440, type 3 (EV_ABS), code 40 (ABS_MISC), value 87
Event: time 1583843735.647440, -------------- SYN_REPORT ------------
Event: time 1583843735.655440, type 3 (EV_ABS), code 0 (ABS_X), value 3104
Event: time 1583843735.655440, type 3 (EV_ABS), code 1 (ABS_Y), value 1843
Event: time 1583843735.655440, type 3 (EV_ABS), code 40 (ABS_MISC), value 75
Event: time 1583843735.655440, -------------- SYN_REPORT ------------
Event: time 1583843735.663440, type 3 (EV_ABS), code 0 (ABS_X), value 3105
Event: time 1583843735.663440, type 3 (EV_ABS), code 1 (ABS_Y), value 1842
Event: time 1583843735.663440, type 3 (EV_ABS), code 40 (ABS_MISC), value 64
Event: time 1583843735.663440, -------------- SYN_REPORT ------------
Event: time 1583843735.671440, type 3 (EV_ABS), code 0 (ABS_X), value 3106
Event: time 1583843735.671440, type 3 (EV_ABS), code 1 (ABS_Y), value 1841
Event: time 1583843735.671440, type 3 (EV_ABS), code 40 (ABS_MISC), value 54
Event: time 1583843735.671440, -------------- SYN_REPORT ------------
Event: time 1583843735.679441, type 3 (EV_ABS), code 0 (ABS_X), value 3107
Event: time 1583843735.679441, type 3 (EV_ABS), code 1 (ABS_Y), value 1840
Event: time 1583843735.679441, type 3 (EV_ABS), code 40 (ABS_MISC), value 43
Event: time 1583843735.679441, -------------- SYN_REPORT ------------
Event: time 1583843735.691438, type 3 (EV_ABS), code 40 (ABS_MISC), value 31
Event: time 1583843735.691438, -------------- SYN_REPORT ------------
Event: time 1583843735.727442, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843735.727442, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1583843735.727442, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1583843735.727442, -------------- SYN_REPORT ------------
Event: time 1583843736.111465, type 3 (EV_ABS), code 0 (ABS_X), value 2554
Event: time 1583843736.111465, type 3 (EV_ABS), code 1 (ABS_Y), value 920
Event: time 1583843736.111465, type 3 (EV_ABS), code 40 (ABS_MISC), value 59
Event: time 1583843736.111465, -------------- SYN_REPORT ------------
Event: time 1583843736.119460, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843736.119460, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1583843736.119460, type 3 (EV_ABS), code 0 (ABS_X), value 2553
Event: time 1583843736.119460, type 3 (EV_ABS), code 40 (ABS_MISC), value 71
Event: time 1583843736.119460, -------------- SYN_REPORT ------------
Event: time 1583843736.127456, type 3 (EV_ABS), code 1 (ABS_Y), value 918
Event: time 1583843736.127456, type 3 (EV_ABS), code 40 (ABS_MISC), value 80
Event: time 1583843736.127456, -------------- SYN_REPORT ------------
Event: time 1583843736.139455, type 3 (EV_ABS), code 1 (ABS_Y), value 916
Event: time 1583843736.139455, type 3 (EV_ABS), code 40 (ABS_MISC), value 87
Event: time 1583843736.139455, -------------- SYN_REPORT ------------
Event: time 1583843736.147458, type 3 (EV_ABS), code 0 (ABS_X), value 2552
Event: time 1583843736.147458, type 3 (EV_ABS), code 1 (ABS_Y), value 914
Event: time 1583843736.147458, type 3 (EV_ABS), code 40 (ABS_MISC), value 91
Event: time 1583843736.147458, -------------- SYN_REPORT ------------
Event: time 1583843736.155455, type 3 (EV_ABS), code 1 (ABS_Y), value 912
Event: time 1583843736.155455, type 3 (EV_ABS), code 40 (ABS_MISC), value 95
Event: time 1583843736.155455, -------------- SYN_REPORT ------------
Event: time 1583843736.163463, type 3 (EV_ABS), code 0 (ABS_X), value 2551
Event: time 1583843736.163463, type 3 (EV_ABS), code 1 (ABS_Y), value 910
Event: time 1583843736.163463, type 3 (EV_ABS), code 40 (ABS_MISC), value 97
Event: time 1583843736.163463, -------------- SYN_REPORT ------------
Event: time 1583843736.175456, type 3 (EV_ABS), code 1 (ABS_Y), value 907
Event: time 1583843736.175456, type 3 (EV_ABS), code 40 (ABS_MISC), value 96
Event: time 1583843736.175456, -------------- SYN_REPORT ------------
Event: time 1583843736.183459, type 3 (EV_ABS), code 0 (ABS_X), value 2550
Event: time 1583843736.183459, type 3 (EV_ABS), code 1 (ABS_Y), value 905
Event: time 1583843736.183459, type 3 (EV_ABS), code 40 (ABS_MISC), value 92
Event: time 1583843736.183459, -------------- SYN_REPORT ------------
Event: time 1583843736.191455, type 3 (EV_ABS), code 1 (ABS_Y), value 903
Event: time 1583843736.191455, type 3 (EV_ABS), code 40 (ABS_MISC), value 83
Event: time 1583843736.191455, -------------- SYN_REPORT ------------
Event: time 1583843736.199457, type 3 (EV_ABS), code 0 (ABS_X), value 2549
Event: time 1583843736.199457, type 3 (EV_ABS), code 1 (ABS_Y), value 900
Event: time 1583843736.199457, type 3 (EV_ABS), code 40 (ABS_MISC), value 67
Event: time 1583843736.199457, -------------- SYN_REPORT ------------
Event: time 1583843736.211439, type 3 (EV_ABS), code 0 (ABS_X), value 2548
Event: time 1583843736.211439, type 3 (EV_ABS), code 1 (ABS_Y), value 899
Event: time 1583843736.211439, type 3 (EV_ABS), code 40 (ABS_MISC), value 50
Event: time 1583843736.211439, -------------- SYN_REPORT ------------
Event: time 1583843736.219438, type 3 (EV_ABS), code 0 (ABS_X), value 2547
Event: time 1583843736.219438, type 3 (EV_ABS), code 1 (ABS_Y), value 897
Event: time 1583843736.219438, type 3 (EV_ABS), code 40 (ABS_MISC), value 34
Event: time 1583843736.219438, -------------- SYN_REPORT ------------
Event: time 1583843736.255442, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843736.255442, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1583843736.255442, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1583843736.255442, -------------- SYN_REPORT ------------
Event: time 1583843736.683440, type 3 (EV_ABS), code 0 (ABS_X), value 998
Event: time 1583843736.683440, type 3 (EV_ABS), code 1 (ABS_Y), value 1049
Event: time 1583843736.683440, type 3 (EV_ABS), code 40 (ABS_MISC), value 23
Event: time 1583843736.683440, -------------- SYN_REPORT ------------
Event: time 1583843736.691439, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843736.691439, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1583843736.691439, type 3 (EV_ABS), code 40 (ABS_MISC), value 33
Event: time 1583843736.691439, -------------- SYN_REPORT ------------
Event: time 1583843736.699439, type 3 (EV_ABS), code 0 (ABS_X), value 997
Event: time 1583843736.699439, type 3 (EV_ABS), code 40 (ABS_MISC), value 45
Event: time 1583843736.699439, -------------- SYN_REPORT ------------
Event: time 1583843736.707438, type 3 (EV_ABS), code 0 (ABS_X), value 996
Event: time 1583843736.707438, type 3 (EV_ABS), code 40 (ABS_MISC), value 55
Event: time 1583843736.707438, -------------- SYN_REPORT ------------
Event: time 1583843736.719439, type 3 (EV_ABS), code 0 (ABS_X), value 995
Event: time 1583843736.719439, type 3 (EV_ABS), code 1 (ABS_Y), value 1048
Event: time 1583843736.719439, type 3 (EV_ABS), code 40 (ABS_MISC), value 64
Event: time 1583843736.719439, -------------- SYN_REPORT ------------
Event: time 1583843736.727439, type 3 (EV_ABS), code 0 (ABS_X), value 994
Event: time 1583843736.727439, type 3 (EV_ABS), code 1 (ABS_Y), value 1047
Event: time 1583843736.727439, type 3 (EV_ABS), code 40 (ABS_MISC), value 72
Event: time 1583843736.727439, -------------- SYN_REPORT ------------
Event: time 1583843736.735439, type 3 (EV_ABS), code 0 (ABS_X), value 993
Event: time 1583843736.735439, type 3 (EV_ABS), code 1 (ABS_Y), value 1046
Event: time 1583843736.735439, type 3 (EV_ABS), code 40 (ABS_MISC), value 80
Event: time 1583843736.735439, -------------- SYN_REPORT ------------
Event: time 1583843736.743439, type 3 (EV_ABS), code 0 (ABS_X), value 992
Event: time 1583843736.743439, type 3 (EV_ABS), code 40 (ABS_MISC), value 88
Event: time 1583843736.743439, -------------- SYN_REPORT ------------
Event: time 1583843736.755439, type 3 (EV_ABS), code 0 (ABS_X), value 991
Event: time 1583843736.755439, type 3 (EV_ABS), code 1 (ABS_Y), value 1045
Event: time 1583843736.755439, type 3 (EV_ABS), code 40 (ABS_MISC), value 94
Event: time 1583843736.755439, -------------- SYN_REPORT ------------
Event: time 1583843736.763441, type 3 (EV_ABS), code 0 (ABS_X), value 990
Event: time 1583843736.763441, type 3 (EV_ABS), code 1 (ABS_Y), value 1044
Event: time 1583843736.763441, type 3 (EV_ABS), code 40 (ABS_MISC), value 97
Event: time 1583843736.763441, -------------- SYN_REPORT ------------
Event: time 1583843736.771439, type 3 (EV_ABS), code 0 (ABS_X), value 989
Event: time 1583843736.771439, type 3 (EV_ABS), code 1 (ABS_Y), value 1043
Event: time 1583843736.771439, type 3 (EV_ABS), code 40 (ABS_MISC), value 94
Event: time 1583843736.771439, -------------- SYN_REPORT ------------
Event: time 1583843736.779438, type 3 (EV_ABS), code 0 (ABS_X), value 987
Event: time 1583843736.779438, type 3 (EV_ABS), code 40 (ABS_MISC), value 81
Event: time 1583843736.779438, -------------- SYN_REPORT ------------
Event: time 1583843736.791439, type 3 (EV_ABS), code 0 (ABS_X), value 986
Event: time 1583843736.791439, type 3 (EV_ABS), code 40 (ABS_MISC), value 63
Event: time 1583843736.791439, -------------- SYN_REPORT ------------
Event: time 1583843736.799439, type 3 (EV_ABS), code 0 (ABS_X), value 985
Event: time 1583843736.799439, type 3 (EV_ABS), code 40 (ABS_MISC), value 44
Event: time 1583843736.799439, -------------- SYN_REPORT ------------
Event: time 1583843736.835440, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843736.835440, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1583843736.835440, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1583843736.835440, -------------- SYN_REPORT ------------
Event: time 1583843737.159464, type 3 (EV_ABS), code 0 (ABS_X), value 398
Event: time 1583843737.159464, type 3 (EV_ABS), code 1 (ABS_Y), value 2655
Event: time 1583843737.159464, type 3 (EV_ABS), code 40 (ABS_MISC), value 35
Event: time 1583843737.159464, -------------- SYN_REPORT ------------
Event: time 1583843737.167460, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843737.167460, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1583843737.167460, type 3 (EV_ABS), code 1 (ABS_Y), value 2656
Event: time 1583843737.167460, type 3 (EV_ABS), code 40 (ABS_MISC), value 50
Event: time 1583843737.167460, -------------- SYN_REPORT ------------
Event: time 1583843737.179453, type 3 (EV_ABS), code 40 (ABS_MISC), value 66
Event: time 1583843737.179453, -------------- SYN_REPORT ------------
Event: time 1583843737.187455, type 3 (EV_ABS), code 1 (ABS_Y), value 2657
Event: time 1583843737.187455, type 3 (EV_ABS), code 40 (ABS_MISC), value 82
Event: time 1583843737.187455, -------------- SYN_REPORT ------------
Event: time 1583843737.195456, type 3 (EV_ABS), code 0 (ABS_X), value 399
Event: time 1583843737.195456, type 3 (EV_ABS), code 40 (ABS_MISC), value 94
Event: time 1583843737.195456, -------------- SYN_REPORT ------------
Event: time 1583843737.203456, type 3 (EV_ABS), code 1 (ABS_Y), value 2658
Event: time 1583843737.203456, type 3 (EV_ABS), code 40 (ABS_MISC), value 102
Event: time 1583843737.203456, -------------- SYN_REPORT ------------
Event: time 1583843737.215455, type 3 (EV_ABS), code 1 (ABS_Y), value 2659
Event: time 1583843737.215455, type 3 (EV_ABS), code 40 (ABS_MISC), value 105
Event: time 1583843737.215455, -------------- SYN_REPORT ------------
Event: time 1583843737.223457, type 3 (EV_ABS), code 0 (ABS_X), value 400
Event: time 1583843737.223457, type 3 (EV_ABS), code 1 (ABS_Y), value 2660
Event: time 1583843737.223457, type 3 (EV_ABS), code 40 (ABS_MISC), value 101
Event: time 1583843737.223457, -------------- SYN_REPORT ------------
Event: time 1583843737.231454, type 3 (EV_ABS), code 1 (ABS_Y), value 2661
Event: time 1583843737.231454, type 3 (EV_ABS), code 40 (ABS_MISC), value 86
Event: time 1583843737.231454, -------------- SYN_REPORT ------------
Event: time 1583843737.239463, type 3 (EV_ABS), code 0 (ABS_X), value 401
Event: time 1583843737.239463, type 3 (EV_ABS), code 1 (ABS_Y), value 2662
Event: time 1583843737.239463, type 3 (EV_ABS), code 40 (ABS_MISC), value 70
Event: time 1583843737.239463, -------------- SYN_REPORT ------------
Event: time 1583843737.251455, type 3 (EV_ABS), code 0 (ABS_X), value 402
Event: time 1583843737.251455, type 3 (EV_ABS), code 1 (ABS_Y), value 2664
Event: time 1583843737.251455, type 3 (EV_ABS), code 40 (ABS_MISC), value 57
Event: time 1583843737.251455, -------------- SYN_REPORT ------------
Event: time 1583843737.259455, type 3 (EV_ABS), code 0 (ABS_X), value 403
Event: time 1583843737.259455, type 3 (EV_ABS), code 1 (ABS_Y), value 2665
Event: time 1583843737.259455, type 3 (EV_ABS), code 40 (ABS_MISC), value 43
Event: time 1583843737.259455, -------------- SYN_REPORT ------------
Event: time 1583843737.307442, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843737.307442, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1583843737.307442, type 3 (EV_ABS), code 0 (ABS_X), value 405
Event: time 1583843737.307442, type 3 (EV_ABS), code 1 (ABS_Y), value 2667
Event: time 1583843737.307442, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1583843737.307442, -------------- SYN_REPORT ------------
Event: time 1583843737.807440, type 3 (EV_ABS), code 0 (ABS_X), value 3328
Event: time 1583843737.807440, type 3 (EV_ABS), code 1 (ABS_Y), value 2864
Event: time 1583843737.807440, type 3 (EV_ABS), code 40 (ABS_MISC), value 27
Event: time 1583843737.807440, -------------- SYN_REPORT ------------
Event: time 1583843737.815440, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843737.815440, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1583843737.815440, type 3 (EV_ABS), code 1 (ABS_Y), value 2865
Event: time 1583843737.815440, type 3 (EV_ABS), code 40 (ABS_MISC), value 40
Event: time 1583843737.815440, -------------- SYN_REPORT ------------
Event: time 1583843737.823438, type 3 (EV_ABS), code 0 (ABS_X), value 3329
Event: time 1583843737.823438, type 3 (EV_ABS), code 1 (ABS_Y), value 2866
Event: time 1583843737.823438, type 3 (EV_ABS), code 40 (ABS_MISC), value 52
Event: time 1583843737.823438, -------------- SYN_REPORT ------------
Event: time 1583843737.831438, type 3 (EV_ABS), code 0 (ABS_X), value 3330
Event: time 1583843737.831438, type 3 (EV_ABS), code 1 (ABS_Y), value 2868
Event: time 1583843737.831438, type 3 (EV_ABS), code 40 (ABS_MISC), value 56
Event: time 1583843737.831438, -------------- SYN_REPORT ------------
Event: time 1583843737.843438, type 3 (EV_ABS), code 1 (ABS_Y), value 2869
Event: time 1583843737.843438, type 3 (EV_ABS), code 40 (ABS_MISC), value 53
Event: time 1583843737.843438, -------------- SYN_REPORT ------------
Event: time 1583843737.851437, type 3 (EV_ABS), code 1 (ABS_Y), value 2871
Event: time 1583843737.851437, type 3 (EV_ABS), code 40 (ABS_MISC), value 49
Event: time 1583843737.851437, -------------- SYN_REPORT ------------
Event: time 1583843737.859438, type 3 (EV_ABS), code 0 (ABS_X), value 3331
Event: time 1583843737.859438, type 3 (EV_ABS), code 1 (ABS_Y), value 2873
Event: time 1583843737.859438, type 3 (EV_ABS), code 40 (ABS_MISC), value 46
Event: time 1583843737.859438, -------------- SYN_REPORT ------------
Event: time 1583843737.867437, type 3 (EV_ABS), code 1 (ABS_Y), value 2876
Event: time 1583843737.867437, type 3 (EV_ABS), code 40 (ABS_MISC), value 43
Event: time 1583843737.867437, -------------- SYN_REPORT ------------
Event: time 1583843737.875437, type 3 (EV_ABS), code 0 (ABS_X), value 3332
Event: time 1583843737.875437, type 3 (EV_ABS), code 1 (ABS_Y), value 2880
Event: time 1583843737.875437, type 3 (EV_ABS), code 40 (ABS_MISC), value 40
Event: time 1583843737.875437, -------------- SYN_REPORT ------------
Event: time 1583843737.887437, type 3 (EV_ABS), code 1 (ABS_Y), value 2883
Event: time 1583843737.887437, type 3 (EV_ABS), code 40 (ABS_MISC), value 37
Event: time 1583843737.887437, -------------- SYN_REPORT ------------
Event: time 1583843737.895437, type 3 (EV_ABS), code 1 (ABS_Y), value 2887
Event: time 1583843737.895437, type 3 (EV_ABS), code 40 (ABS_MISC), value 31
Event: time 1583843737.895437, -------------- SYN_REPORT ------------
Event: time 1583843737.903437, type 3 (EV_ABS), code 1 (ABS_Y), value 2891
Event: time 1583843737.903437, type 3 (EV_ABS), code 40 (ABS_MISC), value 24
Event: time 1583843737.903437, -------------- SYN_REPORT ------------
Event: time 1583843737.939439, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1583843737.939439, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1583843737.939439, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1583843737.939439, -------------- SYN_REPORT ------------

EAHendrix
Posts: 2
Joined: Sat Mar 14, 2020 3:52 am

Re: fruitbox MP3 jukebox

Sat Mar 14, 2020 4:00 am

I am looking to upgrade a failing Rowe CD100 and was hoping to use fruitbox to do it. I was wanting to maintain the hardware controls and basic style of the unit. Is there an available skin that would look like the image below. If not I am willing to pay someone to customize it.

Image

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: fruitbox MP3 jukebox

Sat Mar 14, 2020 10:52 pm

EAHendrix wrote:
Sat Mar 14, 2020 4:00 am
I am looking to upgrade a failing Rowe CD100 and was hoping to use fruitbox to do it. I was wanting to maintain the hardware controls and basic style of the unit. Is there an available skin that would look like the image below. If not I am willing to pay someone to customize it.

Image
Hi

There's no skin quite like that, but it shouldn't be too difficult to get something fairly close to start with. Are the displays near the buttons active? (i.e. do they light up under different conditions?) Could you post close-ups of these please? Fruitbox could potentially control these via GPIO outputs driven by status objects if they are just lights. On the left looks like a simple display... this could potentially be controlled using a separate script reading a status Output file. And of course the buttons and coin mechanism should be easily used by connecting them to GPIO too (assuming they are normally open type switches). Finally can you quickly explain how the selection works? From what I can tell from the picture each album has a unique code, but so do each of the songs in the album....

Cheers
Mike

davidmval
Posts: 6
Joined: Wed Jul 24, 2013 10:38 pm

Re: fruitbox MP3 jukebox

Tue Mar 17, 2020 9:16 pm

Hi Mike.
First of all, I want to congratulate you on your great work, it is incredible!!.
I have seen that the libraries used in fruitbox are libjpeg.so.62.
I wanted to ask you if it is possible that fruitbox works with libjpeg.so.8 libraries instead of libjpeg.so.62, since I want to integrate it into batocera / recalbox (retrogames launcher), but I see that it has libjpeg.so.8 libraries integrated. and I cannot install version 6.2 because it is a closed system and does not allow modifying it (no apt-get, no yum, no dpkg, etc ...) Would there be any solution?
Could you compile fruitbox with libjpeg.so.8 libraries?
Thank you very much in advance.

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: fruitbox MP3 jukebox

Wed Mar 18, 2020 7:19 am

davidmval wrote:
Tue Mar 17, 2020 9:16 pm
Hi Mike.
First of all, I want to congratulate you on your great work, it is incredible!!.
I have seen that the libraries used in fruitbox are libjpeg.so.62.
I wanted to ask you if it is possible that fruitbox works with libjpeg.so.8 libraries instead of libjpeg.so.62, since I want to integrate it into batocera / recalbox (retrogames launcher), but I see that it has libjpeg.so.8 libraries integrated. and I cannot install version 6.2 because it is a closed system and does not allow modifying it (no apt-get, no yum, no dpkg, etc ...) Would there be any solution?
Could you compile fruitbox with libjpeg.so.8 libraries?
Thank you very much in advance.
Hi

For the next release I'll use the later libjpeg version, no problem.

In the meantime, you could compile fruitbox yourself...just follow the instructions in build.txt in the build directory.

Cheers
Mike

WillyOl
Posts: 1
Joined: Thu Mar 19, 2020 11:03 am

Re: fruitbox MP3 jukebox

Thu Mar 19, 2020 11:08 am

Hello Mike

Thank you very much for the very nice program.

I would like to use fruitbox to recreate a Rock Ola 418 Rhapsody (http://www.jukebox-world.de/Forum/Archi ... .O.418.htm). For this I bought a Dell U3415W used monitor. Now I have rebuilt the skin to be able to select 160 songs, 8 rows with 20 tracks. If I took advantage of the resolution of the Dell monitor ( 3440x1440 ), then the Rapberry Pi 3 will be on its knees. So I reduced the resolution to 1720x720. I can work very well with that. Maybe another version of fruitbox brings the possibility to control a Raspi 4 or a PC with Linux and I can increase the resolution again.

Now I want to perform the 160 songs with A...V and 0...9. the Rock Ola does not use the letters I and O. It would be nice if you could release more letters in an up-to-date version. For the control I would like to use two 4x4 matrix membrane keypad, 16 letters, 10 digits and 8 keys for further functions. Does anyone have any experience controlling these buttons via the Raspi's GIOP? Now I was able to get the original keypad of a Rock Ola last week. As a final stage of expansion, it would now be desirable to control the keyboard via the GIOP of the Raspi or via supporting Arduinos.


Greetings from Oldenburg, Northwest Germany

Wilfried

DoctorC
Posts: 7
Joined: Wed Jun 20, 2012 10:52 am

Re: fruitbox MP3 jukebox

Thu Mar 19, 2020 1:56 pm

Hi,
I'm absolutely new to fruitbox.
I'm trying to make it work on a raspy 3 connected by ethernet cable to a windows 10 machine running a remote desktop.
Fruitbox starts and hangs after outputting:

Code: Select all

fruitbox v1.16 (Feb 17 2020, 15:28:38) by Mike Kingsley
A customisable MP3 Retro Jukebox for the Raspberry Pi.
No buttons or monitor are connected to raspy. Is this the cause?
Is there a way to make it run on a bare board. I need to make some tests and eventually create my own skin.

Thanks,
Enrico

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: fruitbox MP3 jukebox

Thu Mar 19, 2020 2:08 pm

DoctorC wrote:
Thu Mar 19, 2020 1:56 pm
Hi,
I'm absolutely new to fruitbox.
I'm trying to make it work on a raspy 3 connected by ethernet cable to a windows 10 machine running a remote desktop.
Fruitbox starts and hangs after outputting:

Code: Select all

fruitbox v1.16 (Feb 17 2020, 15:28:38) by Mike Kingsley
A customisable MP3 Retro Jukebox for the Raspberry Pi.
No buttons or monitor are connected to raspy. Is this the cause?
Is there a way to make it run on a bare board. I need to make some tests and eventually create my own skin.

Thanks,
Enrico
Hi Enrico

It's not hanging, it's just outputting its display on the monitor port which isn't connected to anything. Also it takes its input from the local devices (keyboard etc) so the only thing you can do remotely Ctrl-C it.

Cheers
Mike

DoctorC
Posts: 7
Joined: Wed Jun 20, 2012 10:52 am

Re: fruitbox MP3 jukebox

Thu Mar 19, 2020 2:35 pm

fruitbox wrote:
Thu Mar 19, 2020 2:08 pm
Hi Enrico

It's not hanging, it's just outputting its display on the monitor port which isn't connected to anything. Also it takes its input from the local devices (keyboard etc) so the only thing you can do remotely Ctrl-C it.

Cheers
Mike
Mike,
Thanks for the quick answer.
That's what I supposed...
I don't have a monitor at the moment to connect to the raspy. Is there a way to redirect the output? And the Input :)

Enrico

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: fruitbox MP3 jukebox

Thu Mar 19, 2020 5:09 pm

DoctorC wrote:
Thu Mar 19, 2020 2:35 pm
fruitbox wrote:
Thu Mar 19, 2020 2:08 pm
Hi Enrico

It's not hanging, it's just outputting its display on the monitor port which isn't connected to anything. Also it takes its input from the local devices (keyboard etc) so the only thing you can do remotely Ctrl-C it.

Cheers
Mike
Mike,
Thanks for the quick answer.
That's what I supposed...
I don't have a monitor at the moment to connect to the raspy. Is there a way to redirect the output? And the Input :)

Enrico
Hi Enrico

For the input, I don't think so, fruitbox uses low level device event handlers which don't show up remote terminals. For the output, I don't think so either...there may be a way using something like VNC or setting the display environment variable but it's not something I've played with.

Cheers
Mike

davidmval
Posts: 6
Joined: Wed Jul 24, 2013 10:38 pm

Re: fruitbox MP3 jukebox

Thu Mar 19, 2020 6:04 pm

fruitbox wrote:
Wed Mar 18, 2020 7:19 am
davidmval wrote:
Tue Mar 17, 2020 9:16 pm
Hi Mike.
First of all, I want to congratulate you on your great work, it is incredible!!.
I have seen that the libraries used in fruitbox are libjpeg.so.62.
I wanted to ask you if it is possible that fruitbox works with libjpeg.so.8 libraries instead of libjpeg.so.62, since I want to integrate it into batocera / recalbox (retrogames launcher), but I see that it has libjpeg.so.8 libraries integrated. and I cannot install version 6.2 because it is a closed system and does not allow modifying it (no apt-get, no yum, no dpkg, etc ...) Would there be any solution?
Could you compile fruitbox with libjpeg.so.8 libraries?
Thank you very much in advance.
Hi

For the next release I'll use the later libjpeg version, no problem.

In the meantime, you could compile fruitbox yourself...just follow the instructions in build.txt in the build directory.

Cheers
Mike
Thank you very much for answering.
I will try to compile as you say, but I don't think I will succeed, since I have buildroot version and I don't have the apt-get, yum, dpkg, ... commands available.
Would it be possible to make a version of fruitbox to work on versions made with buildroot, that is, that it is not necessary to download additional libraries with apt-get, etc.? I don't know if it would be possible for fruitbox to integrate everything necessary internally, so I ask.
However, when is the new version expected?
Sorry for my bad english.
Last edited by davidmval on Sat Mar 21, 2020 1:33 pm, edited 1 time in total.

EAHendrix
Posts: 2
Joined: Sat Mar 14, 2020 3:52 am

Re: fruitbox MP3 jukebox

Fri Mar 20, 2020 4:18 am

fruitbox wrote:
Sat Mar 14, 2020 10:52 pm

There's no skin quite like that, but it shouldn't be too difficult to get something fairly close to start with. Are the displays near the buttons active? (i.e. do they light up under different conditions?) Could you post close-ups of these please? Fruitbox could potentially control these via GPIO outputs driven by status objects if they are just lights. On the left looks like a simple display... this could potentially be controlled using a separate script reading a status Output file. And of course the buttons and coin mechanism should be easily used by connecting them to GPIO too (assuming they are normally open type switches). Finally can you quickly explain how the selection works? From what I can tell from the picture each album has a unique code, but so do each of the songs in the album....

Cheers
Mike
Sorry I missed your previous reply, I am not near the jukebox, but I will check it out tomorrow and answer your questions.

fury0
Posts: 1
Joined: Sat Mar 21, 2020 4:23 pm

Re: fruitbox MP3 jukebox

Sat Mar 21, 2020 5:07 pm

Hi all,
First , I would like to thank the author for this nice vintage software!
I've installed fruitbox on an old Pi Model B+.
It works like a charm for the audio part.
I would like to know why fruitbox use so much CPU (more than 50% of CPU on my old Pi) while doing nothing? Once playing an MP3 the CPU usage grown to 80% (50+30%) , which, I think is normal. But I don't understand why so much CPU while "standby". I've try all the dist-skins but it's the same with all.
Thank you very much and sorry for my "frenglish" ;)
Last edited by fury0 on Tue Mar 24, 2020 4:11 pm, edited 1 time in total.

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: fruitbox MP3 jukebox

Sat Mar 21, 2020 11:20 pm

fury0 wrote:
Sat Mar 21, 2020 5:07 pm
Hi all,
First , I would like to thank the author for this nice vintage software!
I've installed fruitbox on an old Pi 2 Model B+.
It works like a charm for the audio part.
I would like to know why fruitbox use so much CPU (more than 50% of CPU on my old Pi) while doing nothing? Once playing an MP3 the CPU usage grown to 80% (50+30%) , which, I think is normal. But I don't understand why so much CPU while "standby". I've try all the dist-skins but it's the same with all.
Thank you very much and sorry for my "frenglish" ;)
Hi,

It's because fruitbox is constantly updating the display, even if nothing appears to be changing. Probably not the most efficient way of doing it, but easier to code and more flexible, especially when supporting skins written by other people.

Cheers,
Mike

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: fruitbox MP3 jukebox

Sat Mar 21, 2020 11:29 pm

WillyOl wrote:
Thu Mar 19, 2020 11:08 am
Hello Mike

Thank you very much for the very nice program.

I would like to use fruitbox to recreate a Rock Ola 418 Rhapsody (http://www.jukebox-world.de/Forum/Archi ... .O.418.htm). For this I bought a Dell U3415W used monitor. Now I have rebuilt the skin to be able to select 160 songs, 8 rows with 20 tracks. If I took advantage of the resolution of the Dell monitor ( 3440x1440 ), then the Rapberry Pi 3 will be on its knees. So I reduced the resolution to 1720x720. I can work very well with that. Maybe another version of fruitbox brings the possibility to control a Raspi 4 or a PC with Linux and I can increase the resolution again.

Now I want to perform the 160 songs with A...V and 0...9. the Rock Ola does not use the letters I and O. It would be nice if you could release more letters in an up-to-date version. For the control I would like to use two 4x4 matrix membrane keypad, 16 letters, 10 digits and 8 keys for further functions. Does anyone have any experience controlling these buttons via the Raspi's GIOP? Now I was able to get the original keypad of a Rock Ola last week. As a final stage of expansion, it would now be desirable to control the keyboard via the GIOP of the Raspi or via supporting Arduinos.


Greetings from Oldenburg, Northwest Germany

Wilfried
Hi Wilfried

That's a lot of new extra select letters! But I will endeavour to add them all in for the next release. FYI, you can already omit letters by not specifying them in the SelectButton(s) list , i.e. SelectButtons = ACDE will omit the letter B.

Regarding controlling a 4x4 matrix keyboard from the GPIO, I haven't done this, but I'm sure it has been done before, and would be something like a simple program to produce keyboard codes to fruitbox running alongside it.

Also, you can compile fruitbox for any flavour of Linux, by following the build instructions in the build.txt file in the build subdirectory, but exclude the _RPI switch. This will omit the RPI-specific GPIO support though. Also, I have had it running on an RPI4, but only on Buster desktop (not lite); again you'll have to build it from scratch on a RPI4.

Cheers,
Mike

Jason812
Posts: 4
Joined: Sat Mar 21, 2020 9:22 pm

Re: fruitbox MP3 jukebox

Sun Mar 22, 2020 2:35 am

Hello, First of all Thank You Mike for creating this wonderful Juke. I am having trouble with a problem of mine, not the app's. I have several Jukeboxes that are in one room and i have a sequencer that controls all of them. The sequencer will rotate through the machines looking for a machine with a selection, and when it finds that machine it sends a signal back to my PLC to let THAT machine play one song. I have the output figured out, (when a song is playing an que'd) however i am having difficulty with the input. The input that the sequencer would send when it found that the fruitbox has a song in the que waiting to be played. could someone point me in the right direction? Or is this possible the way it is?
I am using TouchOne with the latest fruitbox version and the pi touchscreen.

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: fruitbox MP3 jukebox

Sun Mar 22, 2020 7:42 am

Jason812 wrote:
Sun Mar 22, 2020 2:35 am
Hello, First of all Thank You Mike for creating this wonderful Juke. I am having trouble with a problem of mine, not the app's. I have several Jukeboxes that are in one room and i have a sequencer that controls all of them. The sequencer will rotate through the machines looking for a machine with a selection, and when it finds that machine it sends a signal back to my PLC to let THAT machine play one song. I have the output figured out, (when a song is playing an que'd) however i am having difficulty with the input. The input that the sequencer would send when it found that the fruitbox has a song in the que waiting to be played. could someone point me in the right direction? Or is this possible the way it is?
I am using TouchOne with the latest fruitbox version and the pi touchscreen.
Hi

Yes I'd like to help, but don't really understand your problem, sorry. (I'm not familiar with sequencers). Could you reword it somehow or give me an example, then I may be able to suggest a solution.

Cheers
Mike

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: Another Fruitbox and ELO touchscreen

Sun Mar 22, 2020 12:18 pm

KToghia wrote:
Tue Mar 10, 2020 12:46 pm
Hello,

I've read through all the other users having issues. I have tried everything from reordering the event handlers so that the touchscreen was event0, I've run the evtest and output the startup. The screen by default comes up as event3 and is responsive. if I just use the button config option Fruitbox recognizes the touches as a mouse event. Any help is really appreciated.
Hi

I'll see if I can get hold of a ELO touchscreen monitor and investigate the problem.

Cheers
Mike
Last edited by fruitbox on Sun Mar 29, 2020 1:49 pm, edited 2 times in total.

kramg
Posts: 36
Joined: Sun Jan 27, 2019 10:49 pm
Location: Ottawa, Canada

Re: fruitbox MP3 jukebox

Sun Mar 22, 2020 1:47 pm

Jason812 wrote:
Sun Mar 22, 2020 2:35 am
Hello, First of all Thank You Mike for creating this wonderful Juke. I am having trouble with a problem of mine, not the app's. I have several Jukeboxes that are in one room and i have a sequencer that controls all of them.
fruitbox wrote:
Sun Mar 22, 2020 7:42 am
Hi

Yes I'd like to help, but don't really understand your problem, sorry. (I'm not familiar with sequencers). Could you reword it somehow or give me an example, then I may be able to suggest a solution.

Cheers
Mike
A diagram might help along with a word about what, at a high level, you are trying to achieve. Are you trying to ensure only one Fruitbox plays at a time or do you just want to track what songs are being played by which machine? Or are you trying to recreate a classic diner set-up where several remotes control one player?
Jason812 wrote:
Sun Mar 22, 2020 2:35 am

The sequencer will rotate through the machines looking for a machine with a selection, and when it finds that machine it sends a signal back to my PLC to let THAT machine play one song.
How are the Fruitboxen, sequencer and Programmable Logic Controller (PLC) connected - Ethernet, USB or some proprietary interface?
By THAT machine do you mean the PLC configured as a music player or the Fruitbox that made the selection? I'm guessing the Fruitbox.
Jason812 wrote:
Sun Mar 22, 2020 2:35 am

I have the output figured out, (when a song is playing an que'd) however i am having difficulty with the input. The input that the sequencer would send when it found that the fruitbox has a song in the que waiting to be played. could someone point me in the right direction? Or is this possible the way it is?
That is going to depend on how the fruitbox is connected to the sequencer and PLC. By the way, how did you stop the Fruitbox from playing once the selection had been queued?


Cheers,

- gustav

Jason812
Posts: 4
Joined: Sat Mar 21, 2020 9:22 pm

Re: fruitbox MP3 jukebox

Sun Mar 22, 2020 2:50 pm

sorry for the confusion. Really all i need to do with the fruitbox is to give it an input to allow it to play the next song in the cue. All the machines i have are old mechanical jukeboxes, trying to adapt this fruitbox to them. I have found that i can put songs in the cue without them playing, my problem is getting the next song to play with a gpio input.

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: fruitbox MP3 jukebox

Sun Mar 22, 2020 2:58 pm

Jason812 wrote:
Sun Mar 22, 2020 2:50 pm
sorry for the confusion. Really all i need to do with the fruitbox is to give it an input to allow it to play the next song in the cue. All the machines i have are old mechanical jukeboxes, trying to adapt this fruitbox to them. I have found that i can put songs in the cue without them playing, my problem is getting the next song to play with a gpio input.
When the currently playing song finishes, fruitbox will remove the next song from the front of the queue and start playing that one. You can pause the currently playing song, or stop it (skip it) completely, which will then start the next queued up song (if any). The maximum size of the queue can also be defined in the skin file.

Cheers
Mike

Jan1977
Posts: 1
Joined: Sun Mar 22, 2020 3:11 pm

Re: fruitbox MP3 jukebox

Sun Mar 22, 2020 3:14 pm

Hi Mike,

I got Fruitbox running but when I try to make it auto start the songs won’t start I can use my keyboard and make a selection but then nothing happens, please can you help me?

With kind regards,

Jan

Jason812
Posts: 4
Joined: Sat Mar 21, 2020 9:22 pm

Re: fruitbox MP3 jukebox

Sun Mar 22, 2020 3:14 pm

thats my problem. i dont want it to start playing the next song unless gpio xx is HI allowing the fruitbox to play the song. this in effect stops my machines from playing music at the same time.

Jason812
Posts: 4
Joined: Sat Mar 21, 2020 9:22 pm

Re: fruitbox MP3 jukebox

Sun Mar 22, 2020 3:17 pm

if i block this code (by placing "#" in front)

Code: Select all

[status]
Position = 30 12
Size = 352 84
Text = 2 255 255 255 255 right false true false 0 0 350
Contents = now_playing.txt
LineSpacing = 4
TimerTickPeriod = 60
when a song is selected they go into the que. i now need to get the next song from the cue to NOW_PLAYING with an gpioxx input

User avatar
fruitbox
Posts: 438
Joined: Mon Feb 22, 2016 7:35 pm
Location: UK

Re: fruitbox MP3 jukebox

Sun Mar 22, 2020 3:29 pm

Jason812 wrote:
Sun Mar 22, 2020 3:17 pm
if i block this code (by placing "#" in front)

Code: Select all

[status]
Position = 30 12
Size = 352 84
Text = 2 255 255 255 255 right false true false 0 0 350
Contents = now_playing.txt
LineSpacing = 4
TimerTickPeriod = 60
when a song is selected they go into the que. i now need to get the next song from the cue to NOW_PLAYING with an gpioxx input
FYI, commenting out the status object will not affect the way fruitbox plays songs from the queue...it will merely not display what's playing. The operation of the queue is hard-coded...if there's no song playing and the queue is not empty, fruitbox will ALWAYS start playing the first in the queue.

You could map the pause button to a gpio pin, which can be used to toggle the pause each time GPIO goes high. You could then check for a song loading event to then pulse that GPIO to trigger a pause. (You can increase the song load time in the skin file to give your system more time to respond).

To check for a song load event externally from fruitbox you can use a [status] object which could set another GPIO pin high if a song is loading. Your system could presumably check for this GPIO high level to then subsequently issue the pause on the other GPIO assigned to the pause button. This may work...

Cheers
Mike

Return to “Graphics, sound and multimedia”