[lumihei premium]

lumihei premium

3. Mai 2017 at 22:50 #28684

Hi,

As mentioned I do not use any of the buttons. Thus the overlap should not be of an issue.

Also as mentioned I had this successfully running under a different system. Pity this drags out so long until someone within max2play acknowledges the issue and fixes it in the plugin (where I believe it resides).

[lumihei premium]

lumihei premium

25. April 2017 at 18:38 #28491

Here the pics. Please note that the buttons on the display are not being used.
In terms of player: I get the Sound working w/o the display in *any* player, sound even works under the console (with mplayer, speaker-test and co.).
Only when I use the Display plugin the sound disappears (and now the display works instead). No error messages, no log entries on that, all looks as if it was working – but sound does not. As mentioned above – repeatable behavior with fresh install every time.

Would be interesting understanding what issue Ronald had – and if he was able resolving it by not using your plugin, but going the (little harder) way.

PS.: getting images to show in this Forum is a pain… not really user-friendly.

• This reply was modified 7 years, 8 months ago by lumihei.
• This reply was modified 7 years, 8 months ago by lumihei.
• This reply was modified 7 years, 8 months ago by lumihei.

[lumihei premium]

lumihei premium

20. April 2017 at 22:57 #28393

Hi Mohammad,

Thanks for the clarification. My Hifiberry DAC (not DAC+) came from Hifiberry with a longer GPIO header though, which at the time was an official option – which means it is stackable (thus physically that works fine to have both Hifiberry DAC and the Display attached at the same time)

When I follow your steps (which are pretty much the ones I described above) I repeatedly run into the same issue. Tried 3 times.
Also checked your step 6, trying out every option – including checking things under the console (alsa + speaker-test, etc.). Again, everything is there and looks OK, but no sound coming from the speakers.

As Ronald seems to have experienced the same as I, it still feels there really is an issue with the display plugin.

• This reply was modified 7 years, 8 months ago by lumihei.

[lumihei premium]

lumihei premium

20. April 2017 at 12:44 #28383

Sorry Mohammad,

but not sure that this makes total sense:

GPIO’s used by Hifiberry:

„Pin 27 and 28 are always reserved for an ID EEPROM on the Raspberry Pi. Independently which card you use, these pins are always reserved and should never be used to connect external components.“
and
„Only the pins on the P5 header are used for the HiFiBerry DAC“

(From: https://support.hifiberry.com/hc/en-us/articles/205376201-GPIO-usage-of-HiFiBerry-boards )

GPIO’s used by Adafruit 2,8″ display v.1

„PiTFT uses: hardware SPI pins (SCK, MOSI, MISO, CE0, CE1) and GPIO #25 and #24“ – older version uses for GPIO buttons „From left to right the buttons correspond to GPIO #23, #22, #27, and #18. (Note: If you have a revision 1 board then #27 is #21 – you’ll just have to change the code a little)“
(Note 2: not using any of the last 4 button GPIO’s if you just don’t use the buttons!!)

(From: https://learn.adafruit.com/raspberry-pi-pygame-ui-basics/from-gpio-to-screen
and
https://learn.adafruit.com/adafruit-pitft-28-inch-resistive-touchscreen-display-raspberry-pi )

Also, as mentioned above: I had both running with a different Distro of Linux Raspbian already (for MPD) – without your plugins.
This to me therefore looks pretty much like a clear problem in your display plugin.

[lumihei premium]

lumihei premium

17. April 2017 at 22:44 #28295

Thanks Roland – let me understand:
If you replace my step 4 with the steps from the tutorial (thus *NOT* using the plugin to get the Display working), you got both working at the same time?

Thanks
Lutz