0

Volumio with the Beocreate

6515cg

March 28, 2018 20:06

None

Follow

Starting Volumio in combination with the Beocreate gives a very loud pop if you don't change the mixer settings to Volume Software controle and Hifiberry DAC. Then also change startup volume setting to zero. Then, after starting, there is only a minor click to hear because the volume is low. If you do not do this you will hear a loud pop.

A minor issue with Volumio is some clicking sounds when volume is set to zero but only when playing Internet Radio.

The best settings for me at the moment is the original B&O Beocreate software with only BT and Airplay. 

 

• Facebook
• Twitter
• LinkedIn

24 comments

• 0
  
  HiFiBerry team March 28, 2018 20:37

  You can just set the MUTE jumper an control the MUTE functionality by a start script. That's what I posted on your other thread some days ago.

  Best regards,
  Daniel

• 0
  
  6515cg March 28, 2018 20:58

  Switching to Bluetooth on MoOde Audio gives also a loud pop so permanently using a mute jumper is difficult.  I think Volumio is at the moment a better option then MoOde.

   

  Regards Ronald

  Edited by 6515cg March 28, 2018 23:43
• 0
  
  EricV February 13, 2019 13:24

  Hi Guys,

   

  I followed your instructions and now have a nice set of CX50's, playing with Volumio. No loud pop at startup, thanks to the 'mute' jumper.

  I have the impression that switching between tracks in the playlist sometimes causes a minor click.

  In general: very happy with the result! It really is the revival of vintage speakers.

  Regards,
  Eric  

  Edited by EricV February 13, 2019 13:24
• 0
  
  HiFiBerry team February 13, 2019 15:40

  Hi Eric,

  which DSP profile are you using?

  Best regards,
  Daniel

• 0
  
  EricV February 13, 2019 15:59

  Hi Daniel,

   

  I downloaded the Beocreate image and installed the CX50 profile that comes with the setup utility from the B&O link. Installation was done with the 'mute' jumper removed.

  After completion of the profile installation I did some testing with Spotify connect and then I installed the volumio image in the Pi.

  Regards,
  Eric

• 0
  
  EricV February 14, 2019 09:07

  Yesterday I did some more testing. Sometimes the click when switching tracks is weak, sometimes it is fairly strong.

  The Volumio has a 'mute' function in the volume control. If this 'mute' is activated obviously sound is off, but then I hear a click at regular intervals.

  Somewhere in this forum I read that the current DSP profiles have a mute action when the signal levels is low. Could that have something to do with the clicks?

  Regards,
  Eric 

• 0
  
  6515cg March 13, 2019 20:14

  Have the same idea. On non-DSP amplifiers like the Hifiberry Amp, there are no clicks or pops.

• 0
  
  EricV March 14, 2019 08:01

  One experiment could be to build a profile without the mute switch. On the other hand I think that there will be a good reason for including the mute function?

   

   

• 0
  
  6515cg May 08, 2019 20:00

  Now with the latest CX100 profile the loud pop between switching Internetradio stations, audio files from my NAS or switching songs with Volumio Spotify Connect on Volumio is even worse. It's an attack on your speakers, so be careful. The Beocreate in combination with 3rd party software like MoOde Audio or Volumio isn't a working combination for me. Perhaps I'm doing something wrong so help is very appreciated!

  With regards

  Ronald

  Edited by 6515cg May 08, 2019 20:11
• 0
  
  EricV May 09, 2019 07:24

  I have a sort of similar experience with the CX50 profile. There is a pop every time playing is started. For me the pop occurred in one channel (right).

  See also here.

  There is also good news though: the loud cracking sound which occurs when the system is powered up has gone in the new profile, which is nice.

  I am using Volumio as player. Not sure if the pop is related to Volumio, because I also hear this pop when running the Beocreate software. In that case I hear the pop at the moment the chime sound starts.

  Eric

   

    

  Edited by EricV May 09, 2019 10:35
• 0
  
  Tuomas May 10, 2019 10:40

  Hi Ronald and Eric,

  thanks for your reports. I haven't had success in replicating this on my hardware, but I'll try my best to help you.

  When you're using Beocreate software, do you get the pops with only certain sources (AirPlay, Bluetooth, Spotify) or all of them? Do you have anything connected to the optical input?

   

  If you could check the following for me, it could help us further:

  1. Log in via SSH.

  2. If you're on a non-BeoCreate installation and haven't done so yet, install HiFiBerry DSP.

  3. Stop playing music if something is currently playing. If you're using Bluetooth, disconnect the source device.

  4. Type dsptoolkit read-hex 62848 and press enter.

   

  This will read the status of the Asynchronous Sample Rate Converter or ASRC for short.This tells whether the source sample rate is correctly detected and converted at the inputs, in other words, if the ASRC is locked. Another algorithm is checking whether it detects an audio signal at the input. Only of both of these conditions are met, the amplifier will unmute. That your boards don't seem to behave this way suggests that the ASRC lock status is something else than what we're expecting.

  From that command, we are expecting something along the following lines:

  00 00 07 FF

  The second pair of numbers will change depending on situation:

  00: ASRC is not locked, neither for the Raspberry Pi nor optical input.

  *1: ASRC is locked for the Raspberry Pi. It should show this value as soon as something starts playing and go back to zero when playback stops.

  8*: ASRC is locked for optical input. This doesn't necessarily mean there's an audio signal (for example, many TVs maintain a signal link even though they are in standby mode).

  You may also see a combination of these – 81 would mean the ASRC is locked for both the Raspberry Pi and the optical input.

   

  5. Now, if you start playing music through the Raspberry Pi and run the previous command again, does the value change according to the description above?

  If you get values that are not what's described above, please attach them here. If they're in line with the above, it's helpful to report that too so we can rule out this possibility and think of something else.

   

  I regret the trouble this is causing you and your speakers.

  Best,

  Tuomas from Bang & Olufsen

• 0
  
  EricV May 10, 2019 11:32

  Hi Tuomas,

  I will give it a try tonight. I will need to reinstall the latest profile first.

  Don't worry about the trouble, it is also fun trying to solve issues and maybe even help improve systems.

  I do have limited experience with programming on Pi's. I have read somewhere in your manuals that HifiBerry DSP can be installed on the same computer as Volumio (which is the player software I use. So I will do that.

  My question is: can Volumio and DSP run in parallel? Or should I stop the volumio service before executing the DSP command?

  Regards,
  Eric 

• 0
  
  Tuomas May 10, 2019 12:00

  Thanks Eric, that means a lot. And you bet, all of the things we learn with and from you guys go towards making these things better.

  As far as I can tell, HiFiBerry DSP and Volumio should be able to run in parallel no problem. Please keep it running and use it to play music in the steps I outlined as you normally would. That would be most valuable.

  Looking forward to seeing what happens!

  Best,

  Tuomas

• 0
  
  HiFiBerry team May 11, 2019 09:13

  Hi,

  without dsptoolkit it's not possible to communicate with the DSP.
  what did you do to install it? Did you use the install script?

  Best regards,
  Daniel

   

• 0
  
  EricV May 12, 2019 14:29

  Hi 

  Forget about the previous complaints. I removed them

  Reinstalled Volumio and used the 'bash' script.

  At the installation end a error occurs thoug. what to do?

  Successfully installed hifiberrydsp xmltodict lxml spidev pyalsaaudio zeroconf RPi.GPIO ifaddr typing
  Cleaning up...
  Failed to stop sigmatcp.service: Unit sigmatcp.service not loaded.
  Created symlink from /etc/systemd/system/multi-user.target.wants/sigmatcp.service to /lib/systemd/system/sigmatcp.service.
  mv: failed to preserve ownership for '/boot/config.txt': Operation not permitted

  Edited by EricV May 12, 2019 14:41
• 0
  
  6515cg May 12, 2019 14:36

  Here are the result with MoOde Audio and the CX100 profile.

  Before playing a song

  
   pi@moode:~ $ dsptoolkit read-hex 62848
   00 00 00 00
   pi@moode:~ $

   During playing a song

   pi@moode:~ $ dsptoolkit read-hex 62848
   00 00 00 00
   pi@moode:~ $

  My config.txt:

   disable_splash=1
   hdmi_drive=2
   dtparam=i2c_arm=on
   dtparam=i2s=on
   dtparam=audio=off
   dtoverlay=hifiberry-dac
   #dtoverlay=pi3-disable-wifi
   #dtoverlay=pi3-disable-bt
   dtparam=spi=on

   

   

  Below the Audio Config:

   

  

  Edited by 6515cg May 12, 2019 23:12
• 0
  
  EricV May 12, 2019 15:17

  OK, simple reboot did the job.

  I now run Volumio with the CX50 profile from dec-2018 (no plops). Mute jumper installed.

  When playing a song: 00 01 07 FF

  When stopped: 00 00 07 FF

  This is as it should be, if I understand the comments of Tuomas correctly.

   

  Edited by EricV May 12, 2019 15:24
• 0
  
  EricV May 12, 2019 15:23

  If I want to install the latest profile for the CX50 (the one with the plops), can that be done with the dsptoolkit in the Volumio image? If so, I suppose that Volumio should not be playing any music?

• 0
  
  6515cg May 12, 2019 15:26

  Here are the results of Volumio and the CX100 profile.

  Before playing a song 

  volumio@volumio:~$ dsptoolkit read-hex 62848
  00 00 00 00
  volumio@volumio:~$

  During playing a song

  volumio@volumio:~$ dsptoolkit read-hex 62848
  00 00 00 00
  volumio@volumio:~$

  BTW: only two volume options. This time no hardware option.

  

  Edited by 6515cg May 12, 2019 23:11
• 0
  
  EricV May 12, 2019 15:30

  I had to run the command twice to get the results. 

  And I indeed have a hardware option for the volume. Did not try it yet....

  Update:

  tried it: the hardware option is there, but volume control does not work.

  Edited by EricV May 12, 2019 18:30
• 0
  
  EricV May 12, 2019 18:45

  OK, after installation of the most recent CX50 profile (2019-04-30) the results from the hex-read are identical:

  When playing a song: 00 01 07 FF

  When stopped: 00 00 07 FF

  There is however a significant change: the plops are gone! I  removed the mute jumper; there is also no sharp crackling at system power up. This absence of crackling was already the case when I did the first attempt. But now also the plop at starting a track  or webradio stream is gone.

  Result is great, but I do not what made the change though.....!

  Is there a way to check if a profile installation in EEPROM is OK? Checksum e.g.?

  Regards, and thanks for the help sofar.
  Eric 

  Edited by EricV May 12, 2019 18:46
• 0
  
  6515cg May 12, 2019 22:52

  Here are my results with the CX50 profile.  How do I know I'm using the  latest version? I always start with the standard Hifiberry download option http://downloads.hifiberry.com/beocreate/setup/ 

  First: without playing a sound. Second during playing sound.

  1) CX50 profile

  

  All sources works. No clicks or pops when starting up or between songs. Only playlist bug with Spotify Connect.

   

  2) CX profile and MoOde Audio

  

  Loud pop when starting up and between songs.

   

  3) CX50 profile and Volumio

  

  Loud pop when starting up and between songs.

  BTW: no hardware option to choose

  

  Eric, If I see your results, how can this be so different? I'm not using the mute connector on the board and do a clean install from the setup profile and after that a clean Volumio and choose Hifiberry DAC and Software control.

  Thanks anyway.

  Regards Ronald

   

  Edited by 6515cg May 12, 2019 23:09
• 0
  
  EricV May 13, 2019 06:36

  Hi Ronald,

  I do not know why the results are so different. I made a fresh Volumio install. And then I installed the DSP toolkit on that image with the 'bash' script. There was an error message, because this scrip wanted to change '/boot/config.txt', with no rights to do so. Reboot cleared this and the dsptoolkit worked.

  Remarkable is that when I issued the 'read-hex' command for the first time I also got the 4 x 00. Second time the same, third time I got the "00 01 07 FF" result. Do not know why, it as if the systems needs some initialisation.

  Edited by EricV May 13, 2019 19:29
• 0
  
  6515cg May 13, 2019 22:10

  My Volumio issues are solved. With the latest CX50 profile, all pop problems are gone and Volumio works fine with the Beocreate.