Peppy WebRadio
-
paulaner -
5. Februar 2018 um 17:11 -
Erledigt
Heute ist Stammtischzeit:
Jeden Donnerstag 20:30 Uhr hier im Chat.
Wer Lust hat, kann sich gerne beteiligen. ;)
Jeden Donnerstag 20:30 Uhr hier im Chat.
Wer Lust hat, kann sich gerne beteiligen. ;)
-
-
Peppy WebRadio? Schau mal ob du hier fündig wirst!
-
Hallo homer2009,
der Codeblock ist nicht notwendig für Zitate oder normalen Text. Codeblock ist wichtig für
- Terminaleingaben uns -Ausgaben
- Skripte
- Textdateien
peppy.player hat in Beitrag #1088 geschrieben, wie das Waveshare 3.5 LCD(B) Rev.2.0 zu installieren ist.
Aber der Aufruf unterscheidet sich, je nachdem ob man eine Kommandozeilen-Obefläche oder eine grafische Oberfläche verwendet.
Betriebssystem Aufruf Kommandozeilen-Oberfläche Raspberry Pi OS - Lite ./LCD35B-show-V2 lite grafische Oberfläche Raspberry Pi OS with desktop ./LCD35B-show-V2 Für den Peppy Player verwendest Du die Kommandozeilen-Oberfläche
- folgende Datei muß vorhanden sein: /boot/overlays/waveshare35b-v2.dtbo
- zeige bitte deine /boot/config.txt in einem Codeblock (mit Button )
Schönen Gruß, kle
-----------------
Hi homer2009,
the codeblock is not necessary for quotes or normal text. Codeblock is important for
- terminal inputs and outputs
- scripts
- Text files
peppy.player wrote in post #1088 how to install the Waveshare 3.5 LCD(B) Rev.2.0.
But the call differs depending on whether you use a command line interface or a graphical interface.
Operating system call command line interface Raspberry Pi OS - Lite ./LCD35B-show-V2 lite graphical user interface Raspberry Pi OS with desktop ./LCD35B-show-V2 For the Peppy Player you use the command line interface
- the following file must exist: /boot/overlays/waveshare35b-v2.dtbo
- please show your /boot/config.txt in a code block (with button )
Regards, kle
--------------------
Translated with http://www.DeepL.com/Translator (free version)
-
-
Hallo homer2009,
du bist hier im deutschen Raspberry Pi Forum. Weil die allermeisten Benutzer deutsch sprechen wird hier im Forum in deutsch geschrieben. Dieses Thema "Peppy WebRadio" ist eine Ausnahme. Weil peppy.player, der Author des Peppy Players, besser englisch als deutsch spricht, hat Hyle (Mod.) in diesem Thema vorgeschlagen die Beiträge in deutsch und in englisch zu schreiben.
Mit DeepL kannst du deine polnischen Beiträge in deutsch und englisch übersetzen.
I have connected the waveshare 3.5inch RPi LCD (B) Rev2.0 display. Everything started only on the display, the colors are not reproduced correctly. What needs to be done to correct it
- Für Waveshare 3.5inch LCD(B) Rev2.0:
Das overlay in config.txt ist korrekt: dtoverlay=waveshare35b-v2
die dazugehörige Datei ist vorhanden /boot/overlays/waveshare35b-v2.dtbo - Solltest du noch ein altes Waveshare 3.5inch LCD(B) haben?
(das wird mit ./LCD35B-show lite installiert)
in config.txt: dtoverlay=waveshare35b
overlay Datei /boot/overlays/waveshare35b.dtbo
Schönen Gruß, kle
--- english -------------------------------------------
Hi homer2009,
you are here in the German Raspberry Pi forum. Because most of the users speak German, the forum is written in German. This topic "Peppy WebRadio" is an exception. Because peppy.player, the author of the Peppy Player, speaks better English than German, Hyle (Mod.) suggested in this Thread to write the posts in German and in English.
With DeepL you can translate your polish posts into english and german.
I have connected the Waveshare 3.5inch RPi LCD (B) Rev2.0 display. Everything started only on the display, the colors are not reproduced correctly. What needs to be done to correct it
- For Waveshare 3.5inch LCD(B) Rev2.0:
The overlay in config.txt is correct: dtoverlay=waveshare35b-v2
the corresponding file exists /boot/overlays/waveshare35b-v2.dtbo. - Should you still have an old Waveshare 3.5inch LCD(B)?
(that is installed with ./LCD35B-show lite)
in config.txt: dtoverlay=waveshare35b
overlay file /boot/overlays/waveshare35b.dtbo
Best regards, kle
Translated with http://www.DeepL.com/Translator (free version)
- Für Waveshare 3.5inch LCD(B) Rev2.0:
-
Hallo,
ich habe Peppy Player schon ein paar mal erfolgreich installiert. Aber gerade habe ich ein Problem und komme nicht richtig dahinter. Ich habe schon einige Male die Anleitung befolgt.
Ich installiere das aktuelle Image für Raspberry PI OS Lite von https://www.raspberrypi.com/software/operating-systems/
Dann folge ich den wesentlichen Schritten, die wo auf https://github.com/project-owner/Peppy.doc/wiki/Expert genannt sind. Da ich das Radio als Headless aufsetze verzichte auf die Schritte für LCD, Drehregler sowie Spotify und Airport, die ich ebenfalls nicht benötige. Da 'Bluealsa' im aktuellen Repo regulär nicht verfügbar ist, habe ich die Version aus testing installiert.
Da das webinterface nicht erreichbar war, habe ich dann mal manuell per "python peppy.py" und erhalte zunächst folgende Fehlermeldung:
pi@raspberrypi:~/Peppy $ python peppy.py
pygame 1.9.6
Hello from the pygame community. https://www.pygame.org/contribute.html
Traceback (most recent call last):
File "/home/pi/Peppy/peppy.py", line 34, in <module>
from ui.screen.radiogroup import RadioGroupScreen
File "/home/pi/Peppy/ui/screen/radiogroup.py", line 20, in <module>
from ui.screen.menuscreen import MenuScreen
File "/home/pi/Peppy/ui/screen/menuscreen.py", line 22, in <module>
from ui.factory import Factory
File "/home/pi/Peppy/ui/factory.py", line 32, in <module>
from util.util import IMAGE_VOLUME, V_ALIGN_CENTER, H_ALIGN_CENTER, IMAGE_TIME_KNOB, KEY_HOME, KEY_PLAYER
File "/home/pi/Peppy/util/util.py", line 42, in <module>
from util.imageutil import ImageUtil, EXT_MP4, EXT_M4A
File "/home/pi/Peppy/util/imageutil.py", line 33, in <module>
from svg import Parser, Rasterizer
ImportError: cannot import name 'Parser' from 'svg' (/home/pi/.local/lib/python3.9/site-packages/svg/__init__.py)
raspblock
-
Was passiert wenn Du mit python3 peppy.py startest? Selber Fehler?
-
Hallo,
der Peppy Player funktioniert z.Z nicht mit bullseye (debian 11.*).
Das liegt daran, daß dort python3.9.* installiert ist und und die Grafik mit pynanosvg aufbereitet wird.
pynanosvg funktioniert bis python3.7 (oder auch 3.8, das habe ich nicht getestet).
Versuche python3.7 in bullseye zu installieren, damit könnte es funktionieren.
Vergiß nicht pythgon3.7 anstatt python3 zu verwenden
Schönen Gruß, kle
--- english -------------------
the Peppy Player does not work with bullseye (debian 11.*).
This is because python3.9.* is installed there and the graphics are prepared with pynanosvg.
pynanosvg works up to python3.7 (or even 3.8, I didn't test that).
Try to install python3.7 in bullseye, that might work.
Remember python3 is python3.9.*, use python3.7 for Peppy Player
Regards, kle
Edit: hyle das gleiche Problem muß veloci für NewTron Radio lösen. Ich kenne keine Alternative zu pynanosvg (Cairo ist viel zu mächtig).
-
hyle , leider die selbe fehlermeldung.
kle, habe es ausprobiert..
zuerst habe ich python 3.7.9 installiert mit den hier beschriebenen schritten: https://tecadmin.net/install-python-3-7-on-ubuntu-linuxmint/
dann funktionierte es immer noch nicht. nach dem deinstallieren von python und nochmal installieren von python 3.7.9 fehlen mir nun auch zusätzliche python-komponenten, wie 'config'.
Es ist wohl zum gegenwärtigen Zeitpunkt das beste weiter auf Buster zu setzen. Mit Bullseye gibt es ja eine Reihe von Änderungen, die eventuell zu berücksichtigen wären.
Ich habe es trotz Installation von Buster nicht hinbekommen. Peppy player startet nicht und die Log-Datei peppy.log bleibt auch leer.
-
Guten Abend forum Nutzer,
Habe ein Problem mit dem Peppy Player in Verbindung mit dem HifiBerry DAC+ RCA. Bekomme kein Ton beim Player. Könnte mir da jemand Helfen?
Touchscreen funktioniert Prima. Ton erhalte ich nur über aplay.
Code
Alles anzeigendmesg log [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.10.52-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1441 SMP Tue Aug 3 18:10:09 BST 2021 [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model A Plus Rev 1.0 [ 0.000000] random: fast init done [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Reserved memory: created CMA memory pool at 0x17c00000, size 64 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000000000-0x000000001bffffff] [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x000000001bffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000001bffffff] [ 0.000000] On node 0 totalpages: 114688 [ 0.000000] DMA zone: 1008 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 114688 pages, LIFO batch:31 [ 0.000000] percpu: Embedded 20 pages/cpu s50700 r8192 d23028 u81920 [ 0.000000] pcpu-alloc: s50700 r8192 d23028 u81920 alloc=20*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 113680 [ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=480 bcm2708_fb.fbheight=320 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash fbcon=map:2 fbcon=font:ProFont6x11 [ 0.000000] Kernel parameter elevator= does not have any effect anymore. Please use sysfs to set IO scheduler for individual devices. [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] Memory: 371684K/458752K available (10240K kernel code, 1312K rwdata, 2948K rodata, 1024K init, 863K bss, 21532K reserved, 65536K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] ftrace: allocating 32043 entries in 63 pages [ 0.000000] ftrace: allocated 63 pages with 6 groups [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] Rude variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] random: get_random_bytes called from start_kernel+0x3ac/0x580 with crng_init=1 [ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns [ 0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns [ 0.000020] Switching to timer-based delay loop, resolution 52ns [ 0.000303] Console: colour dummy device 80x30 [ 0.000375] printk: console [tty1] enabled [ 0.000432] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000) [ 0.000460] pid_max: default: 32768 minimum: 301 [ 0.000659] LSM: Security Framework initializing [ 0.000894] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.000915] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.002333] cgroup: Disabling memory control group subsystem [ 0.002593] CPU: Testing write buffer coherency: ok [ 0.003079] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.004311] Setting up static identity map for 0x100000 - 0x10003c [ 0.004496] rcu: Hierarchical SRCU implementation. [ 0.005412] smp: Bringing up secondary CPUs ... [ 0.006557] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.007841] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.009041] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.009199] smp: Brought up 1 node, 4 CPUs [ 0.009221] SMP: Total of 4 processors activated (153.60 BogoMIPS). [ 0.009233] CPU: All CPU(s) started in HYP mode. [ 0.009243] CPU: Virtualization extensions available. [ 0.010188] devtmpfs: initialized [ 0.028383] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 [ 0.028620] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.028650] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.031944] pinctrl core: initialized pinctrl subsystem [ 0.033084] NET: Registered protocol family 16 [ 0.037215] DMA: preallocated 1024 KiB pool for atomic coherent allocations [ 0.042966] audit: initializing netlink subsys (disabled) [ 0.043832] thermal_sys: Registered thermal governor 'step_wise' [ 0.044838] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1 [ 0.045019] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.045033] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.045326] Serial: AMBA PL011 UART driver [ 0.068103] bcm2835-mbox .mailbox: mailbox enabled [ 0.080108] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-08-03T18:17:07, variant start [ 0.090118] raspberrypi-firmware soc:firmware: Firmware hash is [ 0.134480] Kprobes globally optimized [ 0.139543] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1 [ 0.141810] SCSI subsystem initialized [ 0.142069] usbcore: registered new interface driver usbfs [ 0.142134] usbcore: registered new interface driver hub [ 0.142204] usbcore: registered new device driver usb [ 0.144355] clocksource: Switched to clocksource arch_sys_counter [ 1.917432] VFS: Disk quotas dquot_6.6.0 [ 1.917553] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.917754] FS-Cache: Loaded [ 1.918019] CacheFiles: Loaded [ 1.928912] NET: Registered protocol family 2 [ 1.929116] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 1.930301] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) [ 1.930440] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear) [ 1.930511] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 1.930614] TCP: Hash tables configured (established 4096 bind 4096) [ 1.930761] UDP hash table entries: 256 (order: 1, 8192 bytes, linear) [ 1.930800] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear) [ 1.931106] NET: Registered protocol family 1 [ 1.932078] RPC: Registered named UNIX socket transport module. [ 1.932092] RPC: Registered udp transport module. [ 1.932103] RPC: Registered tcp transport module. [ 1.932115] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.933989] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available [ 1.937914] Initialise system trusted keyrings [ 1.938199] workingset: timestamp_bits=14 max_order=17 bucket_order=3 [ 1.947752] zbud: loaded [ 1.949826] FS-Cache: Netfs 'nfs' registered for caching [ 1.950705] NFS: Registering the id_resolver key type [ 1.950759] Key type id_resolver registered [ 1.950771] Key type id_legacy registered [ 1.950930] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 1.950944] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 1.952121] Key type asymmetric registered [ 1.952135] Asymmetric key parser 'x509' registered [ 1.952194] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 1.952208] io scheduler mq-deadline registered [ 1.952221] io scheduler kyber registered [ 1.955790] bcm2708_fb soc:fb: FB found 1 display(s) [ 1.960510] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 480x320 [ 1.964260] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled [ 1.965084] bcm2835-aux-uart 3f215040.serial: there is not valid maps for state default [ 1.966920] bcm2835-rng 3f104000.rng: hwrng registered [ 1.967405] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB) [ 1.968251] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000 [ 1.980513] brd: module loaded [ 1.992533] loop: module loaded [ 1.994301] Loading iSCSI transport class v2.0-870. [ 1.995946] libphy: Fixed MDIO Bus: probed [ 1.996235] usbcore: registered new interface driver lan78xx [ 1.996313] usbcore: registered new interface driver smsc95xx [ 1.996338] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [ 2.724995] Core Release: 2.80a [ 2.725011] Setting default values for core params [ 2.725039] Finished setting default values for core params [ 2.925395] Using Buffer DMA mode [ 2.925408] Periodic Transfer Interrupt Enhancement - disabled [ 2.925420] Multiprocessor Interrupt Enhancement - disabled [ 2.925433] OTG VER PARAM: 0, OTG VER FLAG: 0 [ 2.925448] Dedicated Tx FIFOs mode [ 2.925971] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = 97d14000 dma = 0xd7d14000 len=9024 [ 2.926001] FIQ FSM acceleration enabled for : Non-periodic Split Transactions Periodic Split Transactions High-Speed Isochronous Endpoints Interrupt/Control Split Transaction hack enabled [ 2.926015] dwc_otg: Microframe scheduler enabled [ 2.926091] WARN::hcd_init_fiq:457: FIQ on core 1 [ 2.926108] WARN::hcd_init_fiq:458: FIQ ASM at 807c8de0 length 36 [ 2.926124] WARN::hcd_init_fiq:497: MPHI regs_base at 9c810000 [ 2.926146] dwc_otg 3f980000.usb: DWC OTG Controller [ 2.926185] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 [ 2.926250] dwc_otg 3f980000.usb: irq 89, io mem 0x00000000 [ 2.926304] Init: Port Power? op_state=1 [ 2.926315] Init: Power Port (0) [ 2.926670] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10 [ 2.926687] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.926702] usb usb1: Product: DWC OTG Controller [ 2.926716] usb usb1: Manufacturer: Linux 5.10.52-v7+ dwc_otg_hcd [ 2.926730] usb usb1: SerialNumber: 3f980000.usb [ 2.927508] hub 1-0:1.0: USB hub found [ 2.927574] hub 1-0:1.0: 1 port detected [ 2.928812] dwc_otg: FIQ enabled [ 2.928824] dwc_otg: NAK holdoff enabled [ 2.928836] dwc_otg: FIQ split-transaction FSM enabled [ 2.928854] Module dwc_common_port init [ 2.929168] usbcore: registered new interface driver usb-storage [ 2.929388] mousedev: PS/2 mouse device common for all mice [ 2.930611] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer [ 2.933429] sdhci: Secure Digital Host Controller Interface driver [ 2.933442] sdhci: Copyright(c) Pierre Ossman [ 2.934091] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe [ 2.934829] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [ 2.935081] sdhci-pltfm: SDHCI platform and OF driver helper [ 2.936843] ledtrig-cpu: registered to indicate activity on CPUs [ 2.937258] hid: raw HID events driver (C) Jiri Kosina [ 2.937414] usbcore: registered new interface driver usbhid [ 2.937426] usbhid: USB HID core driver [ 2.941802] Initializing XFRM netlink socket [ 2.941844] NET: Registered protocol family 17 [ 2.941974] Key type dns_resolver registered [ 2.942752] Registering SWP/SWPB emulation handler [ 2.942900] registered taskstats version 1 [ 2.942935] Loading compiled-in X.509 certificates [ 2.943773] Key type ._fscrypt registered [ 2.943786] Key type .fscrypt registered [ 2.943799] Key type fscrypt-provisioning registered [ 2.955634] uart-pl011 3f201000.serial: cts_event_workaround enabled [ 2.955735] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2 [ 2.957967] bcm2835-aux-uart 3f215040.serial: there is not valid maps for state default [ 2.958661] printk: console [ttyS0] disabled [ 2.958848] 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 86, base_baud = 50000000) is a 16550 [ 2.959098] printk: console [ttyS0] enabled [ 2.960131] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver [ 2.961843] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0 [ 2.961859] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated [ 2.988430] sdhost: log_buf @ (ptrval) (d7d13000) [ 3.026474] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 3.028138] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.029803] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.032779] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 3.037278] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) [ 3.040342] of_cfs_init [ 3.040623] of_cfs_init: OK [ 3.041797] Waiting for root device /dev/mmcblk0p2... [ 3.120571] mmc1: new high speed SDIO card at address 0001 [ 3.124720] mmc0: host does not support reading read-only switch, assuming write-enable [ 3.128902] mmc0: new high speed SDHC card at address aaaa [ 3.129760] mmcblk0: mmc0:aaaa SE32G 29.7 GiB [ 3.132039] mmcblk0: p1 p2 [ 3.169268] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 3.169356] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [ 3.177102] devtmpfs: mounted [ 3.184013] Freeing unused kernel memory: 1024K [ 3.194865] Run /sbin/init as init process [ 3.194877] with arguments: [ 3.194888] /sbin/init [ 3.194899] splash [ 3.194909] with environment: [ 3.194920] HOME=/ [ 3.194930] TERM=linux [ 3.778400] systemd[1]: System time before build time, advancing clock. [ 3.915465] NET: Registered protocol family 10 [ 3.916899] Segment Routing with IPv6 [ 3.994756] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 3.995983] systemd[1]: Detected architecture arm. [ 4.058858] systemd[1]: Set hostname to <raspberrypi>. [ 4.910631] random: systemd: uninitialized urandom read (16 bytes read) [ 4.930352] random: systemd: uninitialized urandom read (16 bytes read) [ 4.933937] systemd[1]: Created slice system-systemd\x2dfsck.slice. [ 4.934283] random: systemd: uninitialized urandom read (16 bytes read) [ 4.935116] systemd[1]: Listening on udev Kernel Socket. [ 4.935832] systemd[1]: Listening on Syslog Socket. [ 4.936911] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 4.937380] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 4.938809] systemd[1]: Created slice system-getty.slice. [ 4.940152] systemd[1]: Created slice system-serial\x2dgetty.slice. [ 5.139016] i2c /dev entries driver [ 5.690853] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [ 5.813203] systemd-journald[115]: Received request to flush runtime journal from PID 1 [ 6.502091] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned. [ 6.506027] bcm2835_vc_sm_cma_probe: Videocore shared memory driver [ 6.506056] [vc_sm_connected_init]: start [ 6.510218] mc: Linux media interface: v0.10 [ 6.513395] [vc_sm_connected_init]: installed successfully [ 6.556062] videodev: Linux video capture interface: v2.00 [ 6.582889] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 6.582895] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 6.582901] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 6.598612] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned. [ 6.600977] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. [ 6.618491] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13 [ 6.620863] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14 [ 6.621318] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15 [ 6.621638] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16 [ 6.621669] bcm2835-isp bcm2835-isp: Register output node 0 with media controller [ 6.621695] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller [ 6.621715] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller [ 6.621736] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller [ 6.621982] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp [ 6.622853] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. [ 6.647327] bcm2835-codec bcm2835-codec: Device registered as /dev/video10 [ 6.647383] bcm2835-codec bcm2835-codec: Loaded V4L2 decode [ 6.654089] bcm2835-codec bcm2835-codec: Device registered as /dev/video11 [ 6.654158] bcm2835-codec bcm2835-codec: Loaded V4L2 encode [ 6.663605] bcm2835-codec bcm2835-codec: Device registered as /dev/video12 [ 6.663657] bcm2835-codec bcm2835-codec: Loaded V4L2 isp [ 7.029240] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 7.134629] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 7.202205] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 7.227350] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 7.230616] usbcore: registered new interface driver brcmfmac [ 7.490055] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 7.490207] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 7.501828] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e [ 7.781927] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 7.787135] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned. [ 7.788039] fb_ili9486 spi0.0: fbtft_property_value: regwidth = 16 [ 7.788063] fb_ili9486 spi0.0: fbtft_property_value: buswidth = 8 [ 7.788099] fb_ili9486 spi0.0: fbtft_property_value: debug = 0 [ 7.788131] fb_ili9486 spi0.0: fbtft_property_value: rotate = 90 [ 7.788170] fb_ili9486 spi0.0: fbtft_property_value: fps = 30 [ 7.788206] fb_ili9486 spi0.0: fbtft_property_value: txbuflen = 32768 [ 7.827501] ads7846 spi0.1: supply vcc not found, using dummy regulator [ 7.835918] ads7846 spi0.1: touchscreen, irq 199 [ 7.837468] input: ADS7846 Touchscreen as /devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/input/input0 [ 8.368076] graphics fb1: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 32 KiB buffer memory, fps=33, spi0.0 at 16 MHz [ 9.850139] random: crng init done [ 9.850161] random: 7 urandom warning(s) missed due to ratelimiting [ 10.058275] 8021q: 802.1Q VLAN Support v1.8 [ 10.064842] uart-pl011 .serial: no DMA platform data [ 10.621806] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled [ 10.694883] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS [ 17.294818] Bluetooth: Core ver 2.22 [ 17.294965] NET: Registered protocol family 31 [ 17.294978] Bluetooth: HCI device and connection manager initialized [ 17.295730] Bluetooth: HCI socket layer initialized [ 17.295754] Bluetooth: L2CAP socket layer initialized [ 17.295792] Bluetooth: SCO socket layer initialized [ 17.306254] Bluetooth: HCI UART driver ver 2.3 [ 17.306266] Bluetooth: HCI UART protocol H4 registered [ 17.306345] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 17.307060] Bluetooth: HCI UART protocol Broadcom registered [ 17.540666] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 17.540678] Bluetooth: BNEP filters: protocol multicast [ 17.540695] Bluetooth: BNEP socket layer initialized [ 17.582446] Bluetooth: RFCOMM TTY layer initialized [ 17.582468] Bluetooth: RFCOMM socket layer initialized [ 17.582492] Bluetooth: RFCOMM ver 1.11 [ 19.233414] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 20.815656] ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net.ipv6.neigh.wlan0.retrans_time - use net.ipv6.neigh.wlan0.retrans_time_ms instead
aplay -l
Code**** List of PLAYBACK Hardware Devices **** card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 [HiFiBerry DAC+ HiFi pcm512x-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0
Code
Alles anzeigenSimple mixer control 'DSP Program',0 Capabilities: enum Items: 'FIR interpolation with de-emphasis' 'Low latency IIR with de-emphasis' 'High attenuation with de-emphasis' 'Fixed process flow' 'Ringing-less low latency FIR' Item0: 'FIR interpolation with de-emphasis' Simple mixer control 'Analogue',0 Capabilities: pvolume Playback channels: Front Left - Front Right Limits: Playback 0 - 1 Mono: Front Left: Playback 1 [100%] [0.00dB] Front Right: Playback 1 [100%] [0.00dB] Simple mixer control 'Analogue Playback Boost',0 Capabilities: volume Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: 0 - 1 Front Left: 0 [0%] [0.00dB] Front Right: 0 [0%] [0.00dB] Simple mixer control 'Auto Mute',0 Capabilities: pswitch Playback channels: Front Left - Front Right Mono: Front Left: Playback [on] Front Right: Playback [on] Simple mixer control 'Auto Mute Mono',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Auto Mute Time Left',0 Capabilities: enum Items: '21ms' '106ms' '213ms' '533ms' '1.07s' '2.13s' '5.33s' '10.66s' Item0: '21ms' Simple mixer control 'Auto Mute Time Right',0 Capabilities: enum Items: '21ms' '106ms' '213ms' '533ms' '1.07s' '2.13s' '5.33s' '10.66s' Item0: '21ms' Simple mixer control 'Clock Missing Period',0 Capabilities: enum Items: '1s' '2s' '3s' '4s' '5s' '6s' '7s' '8s' Item0: '1s' Simple mixer control 'Deemphasis',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Digital',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 207 Mono: Front Left: Playback 207 [100%] [0.00dB] [on] Front Right: Playback 207 [100%] [0.00dB] [on] Simple mixer control 'Max Overclock DAC',0 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 40 Mono: 0 [0%] Simple mixer control 'Max Overclock DSP',0 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 40 Mono: 0 [0%] Simple mixer control 'Max Overclock PLL',0 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 20 Mono: 0 [0%] Simple mixer control 'Volume Ramp Down Emergency Rate',0 Capabilities: enum Items: '1 sample/update' '2 samples/update' '4 samples/update' 'Immediate' Item0: '1 sample/update' Simple mixer control 'Volume Ramp Down Emergency Step',0 Capabilities: enum Items: '4dB/step' '2dB/step' '1dB/step' '0.5dB/step' Item0: '4dB/step' Simple mixer control 'Volume Ramp Down Rate',0 Capabilities: enum Items: '1 sample/update' '2 samples/update' '4 samples/update' 'Immediate' Item0: '1 sample/update' Simple mixer control 'Volume Ramp Down Step',0 Capabilities: enum Items: '4dB/step' '2dB/step' '1dB/step' '0.5dB/step' Item0: '1dB/step' Simple mixer control 'Volume Ramp Up Rate',0 Capabilities: enum Items: '1 sample/update' '2 samples/update' '4 samples/update' 'Immediate' Item0: '1 sample/update' Simple mixer control 'Volume Ramp Up Step',0 Capabilities: enum Items: '4dB/step' '2dB/step' '1dB/step' '0.5dB/step' Item0: '1dB/step
-
-
ich will es eigentlich selbst hinbekommen. aber ich werde es damit versuchen. danke für den hinweis. -
Elperator,
Ich gehe davon aus das deine DAC noch auf mute steht schaue bitte mal in den beiden Beiträgen nach, hier wurde dies schon einmal erklärt.
#653 und #672
Gruß Alex
___________________
Elperator,
I'm assuming that your DAC is still on mute, please take a look at the two posts, this has already been explained here.
# 653 and # 672Regards Alex
-
Guten Abend zusammen,
kann mir jemand bei folgendem Problem helfen:
Ich möchte gerne die in peppyalsa produzierten VU-Signale über UART des RaspberryPi an einen Arduino senden. (Wie im Wiki beschrieben: Serial VU-Meter ) In der config.txt des peppymeter screensavers habe ich das Serial interface aktiviert und die korrekten Daten unter Serial.Interface eingetragen:
[current]
meter = random
random.meter.interval = 20
screen.size = large
output.display = True
output.serial = True
output.i2c = False
output.pwm = False
output.http = False
output.websocket = False
use.logging = False
frame.rate = 30
[serial.interface]
device.name = /dev/serial0
baud.rate = 9600
include.time = True
update.period = 0.1
Sobald ich jetzt Peppy starte, fährt die WEB-UI nicht mehr hoch (kein Zugriff über WEB mehr) und der 7"-Bildschirm bleibt schwarz. Schalte ich unter [current] den EIntrag output.serial auf False, funktioniert alles wieder.
Starte ich Peppy direkt aus der ssh-Konsole mit python3 peppy.py (Vorher das DISPLAY exportiert mit export DISPLAY=:0) startet Peppy zwar. Wenn ich aber via WEB darauf zugreifen will, kommt:
[2021-11-22 20:18:10,978] {web.py:2243} INFO - 304 GET /fonts?current (192.168.1.24) 5.63ms
[2021-11-22 20:18:10,990] {web.py:2243} INFO - 101 GET /ws (192.168.1.24) 3.89ms
[2021-11-22 20:18:10,991] {websockethandler.py:42} DEBUG - Added web client
[2021-11-22 20:18:10,997] {web.py:1793} ERROR - Uncaught exception GET /ws (192.168.1.24)
HTTPServerRequest(protocol='http', host='192.168.1.56:8123', method='GET', uri='/ws', version='HTTP/1.1', remote_ip='192.168.
1.24')
Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/tornado/websocket.py", line 647, in _run_callback
result = callback(*args, **kwargs)
File "/home/pi/Peppy/web/server/handlers/websockethandler.py", line 48, in on_message
self.handle_command(d)
File "/home/pi/Peppy/web/server/handlers/websockethandler.py", line 68, in handle_command
self.redraw_web_ui()
File "/home/pi/Peppy/web/server/webserver.py", line 143, in redraw_web_ui
self.send_json_to_web_ui(self.screen_to_json())
File "/home/pi/Peppy/web/server/webserver.py", line 177, in screen_to_json
current_screen = self.peppy.current_screen
AttributeError: 'Peppy' object has no attribute 'current_screen'
[2021-11-22 20:18:11,005] {websockethandler.py:55} DEBUG - Removed web client
Woran kann es liegen?
Viele Grüße
Stefan
-
OK, and in English:
Good Evening,
I need some help regarding the following problem:
I would like to compute the VU signals produced by peppyalsa on an arduino with neopixels . The arduino will be attached on RXD and TXD of the raspberry pi UART. (Simular situation as described in the wiki : Serial VU-Meter , nixie project of Tobias). In the moment the arduino is not connected yet. In config.txt of the peppymeter screensaver I activated the serial interface as follows:
[current]
meter = random
random.meter.interval = 20
screen.size = large
output.display = True
output.serial = True
output.i2c = False
output.pwm = False
output.http = False
output.websocket = False
use.logging = False
frame.rate = 30
[serial.interface]
device.name = /dev/serial0
baud.rate = 9600
include.time = True
update.period = 0.1
BUT: As soon as I start Peppy with this config file, the web interface does not come up anymore (no access via browser UI nor touchscreen UI). The attached 7-inch screen does not show the peppy interface. If I do switch the entry output.serial to False in [current] section everything works again as expected.
If I start Peppy from the ssh terminal with python3 peppy.py (after export DISPLAY=:0) Peppy starts but there is no acces via the web interface either. The following error appears:
[2021-11-22 20:18:10,978] {web.py:2243} INFO - 304 GET /fonts?current (192.168.1.24) 5.63ms
[2021-11-22 20:18:10,990] {web.py:2243} INFO - 101 GET /ws (192.168.1.24) 3.89ms
[2021-11-22 20:18:10,991] {websockethandler.py:42} DEBUG - Added web client
[2021-11-22 20:18:10,997] {web.py:1793} ERROR - Uncaught exception GET /ws (192.168.1.24)
HTTPServerRequest(protocol='http', host='192.168.1.56:8123', method='GET', uri='/ws', version='HTTP/1.1', remote_ip='192.168.
1.24')
Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/tornado/websocket.py", line 647, in _run_callback
result = callback(*args, **kwargs)
File "/home/pi/Peppy/web/server/handlers/websockethandler.py", line 48, in on_message
self.handle_command(d)
File "/home/pi/Peppy/web/server/handlers/websockethandler.py", line 68, in handle_command
self.redraw_web_ui()
File "/home/pi/Peppy/web/server/webserver.py", line 143, in redraw_web_ui
self.send_json_to_web_ui(self.screen_to_json())
File "/home/pi/Peppy/web/server/webserver.py", line 177, in screen_to_json
current_screen = self.peppy.current_screen
AttributeError: 'Peppy' object has no attribute 'current_screen'
[2021-11-22 20:18:11,005] {websockethandler.py:55} DEBUG - Removed web client
Any ideas to solve that? I need the peppyalsa export of the data via UART to drive my neopixel VU-meter.
Does anyone use this peppymeter UART functionality with success?
Best regards
Stefan
-
Hallo Stefan,
Ich habe gerade die neueste Renoir Edition auf dem Pi 4 mit dem offiziellen 7"-Display getestet. Ich habe output.serial = True gesetzt und ich konnte den Player starten und die Benutzeroberfläche sehen.
Welches Display verwendest du? Ist es an GPIO angeschlossen? Sind Sie sicher, dass es nicht die serielle Schnittstelle verwendet?
Die Standardeinstellungen für das VU-Meter funktionieren nur für den Bildschirmschoner. Wenn Sie also den Bildschirmschoner stoppen, fließen die Daten nicht über die serielle Schnittstelle. Wenn Sie möchten, dass die Daten ständig über die serielle Schnittstelle fließen, müssen Sie die folgende Eigenschaft in der Konfigurationsdatei des Players auf True setzen:
https://github.com/project-owner/…/config.txt#L21
Mit freundlichen Grüßen
--------------------------------------------------------------------------------------
Hi Stefan,
I've just tested the latest Renoir Edition running on Pi 4 with the official 7" display attached to it. I set output.serial = True and I was able to start player and see UI.
Which display do you use? Is it connected to GPIO? Are you sure that it doesn't use the serial interface?
The default settings for the VU Meter work only for the screensaver. So if you stop screensaver the data will not go through the serial interface. If you need the data flow through the serial interface all the time you need to set the following property in the player config file to True:
https://github.com/project-owner/…/config.txt#L21
Best regards
-
Hello peppy.player,
thanks for the quick response!
I've just tested the latest Renoir Edition running on Pi 4 with the official 7" display attached to it. I set output.serial = True and I was able to start player and see UI.
Which display do you use? Is it connected to GPIO? Are you sure that it doesn't use the serial interface?
The default settings for the VU Meter work only for the screensaver. So if you stop screensaver the data will not go through the serial interface. If you need the data flow through the serial interface all the time you need to set the following property in the player config file to True:
I started with renoir headless on a RPi 3B+ with hifiberry amp+ and added my screen and hifi in /boot/config.txt. My display is a Watterott 7" touchdisplay. The display is only attached via HDMI, touch function is disabled (means not connected) in the moment. So there is no serial interface connected to the display. Peppy player starts normal, everything is fine until I set output.serial = True in peppymeter/config.txt. If I set it back to False it works again.
The serial communication to the arduino works in principle: if I send data via minicom to the arduino it receives themand vice versa.
The data flow is enabled as vu_meter is set to true already.
Is there another log file I should check? What does the above mentioned error message mean 'Peppy' object has no attribute 'current_screen'.
Ideas and help to solve the issue is appreciated!
Here a first impression of my player:
You can see the neopixel rings around the speakers.
Regrads
Stefan
-
Hello,
I think I am one step further:
In my Peppy/config.txt touchscreen=True was set, even there is no touch function used. I switched that to False and now data are send.
Regards
Stefan
-
Hallo Stefan,
Du hast ein interessantes Projekt. Das Design ist sehr nah an der ursprünglichen Peppy-Player und Neopixel ist eine schöne Ergänzung. Bitte lass mich wissen, wenn du das Projekt fertiggestellt hast. Ich werde es gerne in die Galerie stellen.
Ich habe meine Installationsanweisungen überprüft und es sieht so aus, als ob ich die Bibliothek für die serielle Schnittstelle (python3-serial) nur an einer Stelle erwähnt habe:
https://github.com/project-owner/…c/wiki/Headless
Haben Sie sie installiert?
pip3 install python3-serial
Das ist wahrscheinlich der Grund für Ihre Probleme.
Beste Grüße.
----------------------------------------------------------------------------------
Hi Stefan,
You have interesting project. The design is very close to the original Peppy player and neopixel is a nice addition. Please let me know when you finish the project. I'll be glad to place it in the Gallery.
I've checked my installation instructions and it looks like I mentioned about the library for the serial interface (python3-serial) only in one place:
https://github.com/project-owner/…c/wiki/Headless
Did you install it?
pip3 install python3-serial
That's probably the reason for your issues.
Best regards.
-
Hallo peppy.player!
the python3-serial is installed. After deactivating the touchscreen in config.txt the VU-meter works over serial. I have to tune the arduino side now to display different kind of patterns and colors. Of course I will come up with some videos and fotos if everything works so far.
One question I still have: The VU-meter data send via peppymeter seem to be independent from the volume that is adjusted. There is no relation between loadness and intensity of the data, right?
I was thinking about show some overdrive if the volume is too high but my values look completely irrespective of the volume.
Thanks again for your great enthusiasm in this project
Regards
Stefan
-
Hallo Stefan,
Lass uns die Regeln dieses Forums nutzen und Nachrichten auf Deutsch und optional auf Englisch posten.
Ich bin mir nicht sicher, wie das "Touchscreen"-Flag mit dem seriellen Signal in Verbindung gebracht werden kann.
Du kannst versuchen, den Lautstärkeregelungstyp 'player' anstelle von 'amixer' zu verwenden:
https://github.com/project-owner/…config.txt#L166
Ich denke, in diesem Fall hängt die Amplitude von der Lautstärke des Lautstärkereglers ab.
Soweit ich mich erinnere, gab es auch eine Möglichkeit, dies in ALSA zu tun. Ich erinnere mich aber nicht mehr daran. Vielleicht kann sich jemand in diesem Forum daran erinnern.
Und schließlich kann man das serielle Signal anhand des aktuellen Lautstärkepegels skalieren. Aber das muss noch implementiert werden.
Mit freundlichen Grüßen.
---------------------------------------------------------------------------
Hi Stefan,
Let's use the rules of this forum and post messages in German and optionally in English.
I'm not sure how 'touchscreen' flag can be related to the serial signal.
You can try to use 'player' volume control type instead of 'amixer':
https://github.com/project-owner/…config.txt#L166
I think in this case the amplitude will depend on the level of your volume control.
As far as I remember there was also a way to do that in ALSA. Though I don't remember it. Maybe someone in this forum could remind.
And finally you can scale the serial signal using the current volume level. But that needs some implementation.
Best regards.
-
Jetzt mitmachen!
Du hast noch kein Benutzerkonto auf unserer Seite? Registriere dich kostenlos und nimm an unserer Community teil!