Forum Audiophonics.fr

The script you are using is very old and is not the code that is included in the RuneAudio Image that Audiophonics has created. Still, if you would like to use it, I believe you can get it to work if you make a small change to the script.

Change line 49 from... to

The most likely reason the display is not working if it does work with the Audiophonics RuneAudio image would be due to the GPIO pins not being set correctly in the script you are running. It was unclear to me which instructions you have followed. Can you confirm what script you are running and the ...

Rikardo, Looks interesting. Do you know if there is any way to get roon to support Spotify?

I just took a quick look and it should be fairly straight forward to produce a driver for SH1106 based displays and my script. There is already an RPi based library at https://hallard.me/adafruit-oled-display-driver-for-pi/ that could be used as the foundation. The Raspdac-Display software though is...

Happy to help.

You are correct about the directory to place the oled.service file. I mistakenly gave you the directory for Rune Audio instead of Max2Play. I sometimes wish that there was more consistency between the distributions!

Glad you got it work.

Good news. It sounds like you are very close to getting this fully working. The fact that you can run the RaspDacDisplay.py script from the Raspdac-Display folder and it works is 98% of the battle. If you are using the provided oled.service file, you now just need to get RaspDacDisplay.py, pages.py,...

Current support for Moode in the Dhrone script is only for MPD. With the Rune distribution though it pulls data directly from Rune which does support Airplay metadata. I believe that Volumio 2 also supports Airplay metadata but the current Dhrone script does not pull its data from Volumio instead ge...

I'm glad to hear you got it working.

In the near future, I should have a version of the program working on other displays including 16x2 and 20x4 HD44780 based LCDs.

Have you tried running the Winstar_GraphicOLED.py program on the RPi 2 (after changing the pin assignments at the top of the file)? If yes, did it display correctly or did also fail to display anything? Did the 16x2_oled_volumio.py script work correctly on the RPi 2? The Winstar WEH001602A is what I...

The behavior you are describing would occur if there was not appropriate scripts installed to configure the power management feature of the Sabre V3. I have not looked into how piCorePlayer is configured so can not provide step-by-step instructions but you will need something similar to the sds.sh s...

I just pushed a new version (v0.7.0.2). It includes the following changes. Fixed volume bug that prevented volume changes from being displayed under some situations Fixed incorrect detection of streaming when playing MPD with playlists that only contained one song Moved PAGES configurations to their...

I'm not sure what to recommend at this point. My code has only been tested with the Winstar OLED so it's possible that it is a compatibility issue, but if you had the display working correctly on the older system using the V2 Sabre, it should work fine here. It's possible that the display itself is ...

The project is up on Github at https://github.com/dhrone/Raspdac-Display/ . Are you looking for an earlier version? If so, you can go back to an earlier commit. I'd suggest the one on April 27th if you want the previous version (0.5). There is a huge amount of additional functionality though with th...

It's not clear to me why the version of Volumio would be related to your problem. We need to see if we can get the display to work regardless of which distribution you are using. To eliminate that as a concern, you can use Winstar_GraphicOLED.py itself. It can be run separately at the command line t...

I have only tested my software using the Winstar OLED display. But, didn't you mention that this same display was working with this software on the V2 Sabre? Beyond the pin change between V2 and V3, they are pretty equivalent in regards to the display.

Mainly it looks like its wired correctly. You should verify that pins 1 and 5 (VSS and RW) are properly grounded. I was also not clear on what the white jumper was for. It's hard to tell what pins it is connecting but it looks like 2 and 6. That would definitely not be correct.

Most of the time, when the display does not work, it is either a problem with the GPIO assignments in the software or the display is not wired correctly. It sounds like you've looked at the software pretty carefully, so I would validate that you have the right pins on the DAC connected to the right ...

Did you adjust the pin assignments? Sabre V2 assigns D7 to GPIO 15 while Sabre V3 assigns D7 to GPIO 27. With the 16x2_oled_volumio.py program, there is a section at the top labeled # Define GPIO to LCD mapping. Check to see if LCD_D7 = 15. It should be LCD_D7=27. If you are using my code, the chang...

I have just issued a pre-release of a major re-write of the Raspdac-Display software. It has the following enhancements... Works across multiple distributions including Volumio, Rune, Moode, Max2Play, and piCorePlayer. Configurable display screens. You can now redefine what gets displayed. More disp...

@nicopup, The discrepancy in the pin numbers is due to the mode that gpio is being run in. There are two different wiring standards that the gpio command supports. These are the wiringPi standards and BCM_GPIO numbers. To use the BCM_GPIO numbers you need to add the -g flag to gpio. See http://wirin...

The Dhrone script was written specifically for the Winstar OLED WEH001602A. This display uses a command set that is very similar to the HD44780 though so I'm somewhat surprised that it didn't work. You may want to verify that the pins that you have assigned match the pin assignments at the top of th...

I'm really glad to hear that you resolved your problem. I've got a second RaspDac that I use for development. It recently started exhibiting problems and I also found that it was a grounding problem. Looks like something that should be highlighted in the installation instructions.

@morias, I've been trying to track down what causes this bug for a long time. It is very intermittent on my system to the point that I can go for weeks without it occurring. It sounds like on your system, it is much more frequent. If you can figure out any patterns or triggering activities that can ...

The next thing I believe would be good is a 1/2 second pause between displaying the track name and artist name. Presently they appear with no pause which is a bit abrupt. I think a short blank screen delay would improve how it switches between the information. I have never coded python, but will tr...

@GuillaumeSej, There are several advantages over the version of the code that you are running. * Smoother screen updates. * Long artist and song titles scroll * The duration that the song and artist titles are displayed is adjustable * The amount of time that a song or artist title is displayed befo...