Danke kle,
sehen gut aus. Deine kurze Zusammenfassung spitze.
Danke kle,
sehen gut aus. Deine kurze Zusammenfassung spitze.
Peppy WebRadio? Schau mal ob du hier fündig wirst!
meigrafd sind die Bilder klein genug?
Ich hab mich nie über Bildergrößen beschwert... Das verwechselst du.
jaja der Alzheimer schlägt zu. War es dann jar der an einer langsamen Leitung hing?
Jedenfalls ist mir in Erinnerung, daß ich darauf aufpassen muß.
Schönen Gruß, kle
Wow, you have 3 different systems.
Did you buy all enclosures or made some of them yourself?
As it was mentioned already the only recommendation would be to improve the
sound quality as the sound from 3.5 mm jack is not so good. But for
that you need to attach additional DAC or Amplifier to the GPIO. In that
case the design becomes not so compact. Only if USB DAC is in use...
Congratulations! Great job!
If you have any questions/proposals feel free to post it here or contact me directly.
Hi peppy.player,
with the same hardware I used NewTron-Radio.
Instead of raspbian-lite as OS I used pipaos (pipaos-guarana-console-5.0.img.gz), a very fast and small 'raspbian-jessie-lite'.
Sound via bluetooth to speaker JBL Go.
I used the bluez-alsa package for bluetooth.
Best regards, kle
Did you buy all enclosures or made some of them yourself?
I bought them all.
Bluetooth is a good alternative. Though I've never used it myself.
Could you share the details of this connection?
What are the extra steps required? Do you really need any additional packages?
Is it reliable connection? Does it work well with WiFi? How far you can move the speakers?
How about sound quality?
Thanks in advance!
RPi 3B and RPi Zero W have an internal bluetooth controller. You need the package pi-bluetooth to use the internal controller.
Attention: the internal bluetooth controller uses the serial interface.
Every Raspbian Release (wheezy, jessie and stretch) handles bluetooth devices in a special way.
wheezy --> alsa --> bt-speaker
jessie --> alsa --> pulseaudio1 --> bt-speaker
stretch --> alsa2 --> bt-speaker
1 pulseaudio sound server uses the pulseaudio-module-bluetooth to send sound to a bt-speaker.
2 alsa uses bluealsa (package bluez-alsa) to send sound to a bt-speaker.
jessie and stretch there is the command bluetoothctl to control bluetooth devices (scan, pair, trust, connect, disconnect, remove, ...).
pulseaudio runs as session daemon.
mpd runs as system daemon.
jessie GUI has bluetooth desktop controls to connect a speaker to pulseaudio.
stretch GUI has bluetooth desktop controls to connect a speaker to bluealsa.
You can build bluealsa also for jessie (raspbian-jessie-lite, pipaos-guarana-console, )
If the package pulseaudio-module-bluetooth is installed, remove it. (Afterwards jessie bluetooth desktop controls doesn't work any more!)
Bluealsa works with jessie/stretch and mpd/vlc1/???mplayer
1 there is an issue #23 'bad sound with VLC' and a work around. Details in Bluetooth for Peppy Player with VLC.
Proposals for improvement welcome.
If it works you can edit /etc/rc.local to autostart Peppy Player
same as VLC except
3. change players.txt
nano ~/Peppy/players.txt
...
[audio]
player.name = mplayer
music.folder.linux =
...
[mplayer.linux]
#server.command = mplayer -ao alsa:device=hifiberry -idle -slave -quiet -msglevel statusline=6 -msglevel global=6
server.command = mplayer -ao alsa:device=headset -idle -slave -quiet -msglevel statusline=6 -msglevel global=6
kle, thanks a lot for very detailed instructions!
New version (Vermeer Edition) of the Peppy Player was just released.
User kle from this forum provided very valuable and helpful input for this release especially in resolving several issues related to the Peppy Player configuration. Thanks a lot Klaus! I appreciate your help very much!
Here are the new features:
- Replaced HiFiBerry Amp+ by HiFiBerry Amp2. That solved audiobooks playback issues.
https://github.com/project-owner/Peppy.doc/wiki/Amplifier
https://github.com/project-owner/…i/HiFiBerry-Amp
- Added CD Player mode.
https://github.com/project-owner/Peppy.doc/wiki/CD-Player
https://github.com/project-owner/Peppy.doc/wiki/CD-Browser
- Made Home menu customizable.
- Added configuration files for screensavers.
- Refactored VU Meter screensaver.
- Improved logging functionality.
- Provided disk images to simplify player installation and configuration.
https://github.com/project-owner/…iki/Disk-Images
- Added Wish List to the Wiki pages:
https://github.com/project-owner/…/wiki/Wish-List
- Updated Gallery with new images depicting projects created by Klaus:
Even though it seems like all english posts here are solely made by you, peppy.player, please keep up writing these update notes! I like them, and a bit of multilingual reading in here won't hurt anyone...
New version (Rubens Edition) of the Peppy Player was released today.
New features:
- Streamlined the process of adding new languages.
https://github.com/project-owner/Peppy.doc/wiki/Languages
Here are the screenshots showing Language and Home menus in Japanese:
- Added CD album art functionality. The CD cover images are retrieved from the largest free web collection on Discogs.com. Here are examples of CD Player with album art:
- Made Screensaver and Language menus customizable.
- Implemented Weather forecast screensaver.
https://github.com/project-owner/Peppy.doc/wiki/Weather
Here are the examples of the Weather screensaver:
- Added information about connecting Bluetooth devices.
https://github.com/project-owner/…uetooth-Devices
- Provided disk images.
I'm not sure why images are not visible inline. When I edit the message all images look OK inline. But when I submit they transform into links
ZitatI'm not sure why images are not visible inline.
Its a new Law.
Nach der Installation kann ich Peppy starten, wenn ich es aus dem Ordner Peppy starte läuft alles, beim Start aus dem pi Verzeichnis mit Python3 /home/pi/Peppy/peppy.py kommt die Fehlermeldung unten:
Jemand eine Idee?
Ziel ist es Peppy automatisch zu starten. Wie kann man Peppy mit Hilfe der LXDE Autostart starten? Müsse zuerst wissen warum man nicht aus einem anderen Order starten kann.
File "/usr/lib/python3.5/configparser.py", line 1135, in _unify_values
sectiondict = self._sections[section]
KeyError: 'screen.info'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./Peppy/peppy.py", line 1120, in <module>
main()
File "./Peppy/peppy.py", line 1116, in main
peppy = Peppy()
File "./Peppy/peppy.py", line 70, in __init__
self.util = Util()
File "/home/pi/Peppy/util/util.py", line 123, in __init__
self.config_class = Config()
File "/home/pi/Peppy/util/config.py", line 91, in __init__
self.load_config(self.config)
File "/home/pi/Peppy/util/config.py", line 112, in load_config
c = {WIDTH : config_file.getint(SCREEN_INFO, WIDTH)}
File "/usr/lib/python3.5/configparser.py", line 816, in getint
fallback=fallback, **kwargs)
File "/usr/lib/python3.5/configparser.py", line 806, in _get_conv
**kwargs)
File "/usr/lib/python3.5/configparser.py", line 800, in _get
return conv(self.get(section, option, **kwargs))
File "/usr/lib/python3.5/configparser.py", line 778, in get
d = self._unify_values(section, vars)
File "/usr/lib/python3.5/configparser.py", line 1138, in _unify_values
raise NoSectionError(section)
configparser.NoSectionError: No section: 'screen.info'
Peppy kann die Konfigurationsdatei nicht finden, wenn du sie aus einem anderen Ordner starten.
Du müssen zuerst den Ordner wechseln. Zum Beispiel um den Spieler automatisch zu starten
Beim Start kann die folgende Zeile zur Datei /etc/rc.local hinzugefügt werden:
Dies wird hier beschrieben:
https://github.com/project-owner/…er-installation
Tschüss
Mein System:
Raspbian 4.14
Kedei 3,5" Touchscreen
sonst erstmal nichts.
Autostart mit rc.local startet bevor die Oberfläche gestartet ist -> funktioniert bei mir nicht, daher wollte ich Peppy in der /etc/xdg/lxsession/LXDE-pi/autostart eintragen.
Hallo,
Du bootest in die grafische Oberfläche.
Der Peppy-Player läuft in der Konsole.
Ich habe es nur über RealVNC geschafft, den Peppy-Player in der grafischen Oberfläche zu automatisch starten. Der TFT-Screen bleibt dann schwarz.
Auch kalibrieren mit kleinen Displays ist schwierig.
---- prinzipiell sollte es so gehen: ---
zum Autostart von Programmen mit Grafik-Oberfläche (hier pygame) bei Desktop (oder auch GUI genannt) sollte X11 gestartet sein.
ich würde die Datei /home/pi/.config/lxsession/LXDE-pi/autostart benutzen, da das peppy.py unter dem Benutzer 'pi' laufen muß (wegen der Rechte).
Aber, wie gesagt das Touchdisplay bleibt schwarz.
Schönen Gruß, kle
Ich habe diese anzeige noch nie probiert. Soweit ich verstehe, funktioniert diese anzeige nur mit einem eigenen Disk-Image, das einen grafischen desktop (X) hat. Ist es möglich, bildschirmtreiber auf Raspbian Stretch Lite zu installieren, die keinen grafischen desktop haben?
Du hast noch kein Benutzerkonto auf unserer Seite? Registriere dich kostenlos und nimm an unserer Community teil!