Hi Brambus,
I have pretty the same configuration as yours.
But it works not so well for me.
With my RPI3 + Audiophonics 9028 + Kali Using 3.8.1, 9028 driver And LL or RT kernels, DSD128 are cracking and got slowdowns and distortion.
(Which is not the case with 3.7 + LL + 9018 driver.)
Did you experienced this too?
Are you Using DoP or not?
thank you for your answer.
I have pretty the same configuration as yours.
But it works not so well for me.
With my RPI3 + Audiophonics 9028 + Kali Using 3.8.1, 9028 driver And LL or RT kernels, DSD128 are cracking and got slowdowns and distortion.
(Which is not the case with 3.7 + LL + 9018 driver.)
Did you experienced this too?
Are you Using DoP or not?
thank you for your answer.
Hello
My current installation is RPi3, Allo Isolator, Kali and Audiophonics 9028 Q2M.
I listen with a Relaixed2 Passive pre, Sjostrom QRV08 phone amp and Beyer DT880.
Moode 3.8 works fine with Audiophonics 9023 LTE driver; MPD oversampling at 32/*, multithread on.
This seems to work better than 384/32 at least with standard 16/44.1 samples (CD standard).
I don't understand the driver option "bclk_ratio_int_div" that i keep disabled. But Audiophonics 9028Q2M has a microprocessor that should rule out all the driver options.
My two cents. Thank you for the nice work
Brambus
Hi Tim,
DHCP on the ethernet port might suit a "minimalist" setup.
Where there is no (alot less) 3.x GHz energy in the listening room. The radiating element on the Pi is only a few cm from the underside of the DAC and a few more from the RCA cables.
Just connect a quiet laptop and play / stream music (without any network concerns)..
As bizzare as this may be (i cannot easily prove this), but there seems to be a slight difference in DAC output with / without wifi (Ver 3.1 wifi and bluetooth disabled on RPi3).
If i went with the wifi route for connectivity, ideally.... a wired connection from the Pi to a distant access point.
I really like the sound that i'm getting from the Moode audio player & the audiophonics i-sabre dac combo. I'm in the throes of coming up a functional listening area around it.
Great work!
DHCP on the ethernet port might suit a "minimalist" setup.
Where there is no (alot less) 3.x GHz energy in the listening room. The radiating element on the Pi is only a few cm from the underside of the DAC and a few more from the RCA cables.
Just connect a quiet laptop and play / stream music (without any network concerns)..
As bizzare as this may be (i cannot easily prove this), but there seems to be a slight difference in DAC output with / without wifi (Ver 3.1 wifi and bluetooth disabled on RPi3).
If i went with the wifi route for connectivity, ideally.... a wired connection from the Pi to a distant access point.
I really like the sound that i'm getting from the Moode audio player & the audiophonics i-sabre dac combo. I'm in the throes of coming up a functional listening area around it.
Great work!
Hi,
The process is to just add tracks to the main Playlist, then save it. To create a new playlist, select the first track in the Playlist, then remove all the tracks, then add new tracks to the empty Playlist then save that one, etc.
Are you referring to the Encoded-at rate and audio format (flac, mp3, arc, etc)?
Bitrate is already displayed right under the Album art.
-Tim
Hi Tim and guys,
I'm scared it's just so obvious but I can't figure how to save my playlist...
Hi Tim,
Is it possible to do DOP decoding in 32bit?
Hi,
AFAIK, 24 bit is per the DoP specification.
-Tim
Hi Tim and guys,
I'm scared it's just so obvious but I can't figure how to save my playlist...
Click the \/ icon in upper left of Playback screen then "save playlist" input field will appear at bottom left.
Hi,
AFAIK, 24 bit is per the DoP specification.
-Tim
Thank you Tim.
Hi everybody,
just installed 3.81 today and I am (again) very pleased vith the new version.
However, I have one question and one issue :
- Last time I installed (v3.7) AlloBoss DAC didn't work with regular kernel (I had to "upgrade" to Advanced Kernel to use it. This time, it worked at once, without installing any special kernel ... is this new? Then is there any point in installing an advanced kernel?
- I can't get MoodeAudio to "remember" a volume warning limit. Each time I try to push volume past 20, I get the warning message, change the limit in the dialog box and press "update" but when I try to turn it up after that, I get the same message ... Has anybody faced the same problem? Can anyone suggest a solution?
Thanks a lot !
Etienne
just installed 3.81 today and I am (again) very pleased vith the new version.
However, I have one question and one issue :
- Last time I installed (v3.7) AlloBoss DAC didn't work with regular kernel (I had to "upgrade" to Advanced Kernel to use it. This time, it worked at once, without installing any special kernel ... is this new? Then is there any point in installing an advanced kernel?
- I can't get MoodeAudio to "remember" a volume warning limit. Each time I try to push volume past 20, I get the warning message, change the limit in the dialog box and press "update" but when I try to turn it up after that, I get the same message ... Has anybody faced the same problem? Can anyone suggest a solution?
Thanks a lot !
Etienne
Hi @etimalandain,
Refresh Browser after changing volume warning limit.
Allo devices work in both Std and Adv kernels starting with moOde 3.8. Below is from 3.8 release notes.
- UPD: Allo devices supported in both Std and Adv kernels
- UPD: Pi-Zero W supported in both Std and Adv kernels
With upcoming moOde 3.8.2 release which runs on newest 4.9.41 kernel, the full feature set of the Piano 2.1 DAC is available in both Std and Adv kernel including 384K sample rate 🙂
-Tim
Refresh Browser after changing volume warning limit.
Allo devices work in both Std and Adv kernels starting with moOde 3.8. Below is from 3.8 release notes.
- UPD: Allo devices supported in both Std and Adv kernels
- UPD: Pi-Zero W supported in both Std and Adv kernels
With upcoming moOde 3.8.2 release which runs on newest 4.9.41 kernel, the full feature set of the Piano 2.1 DAC is available in both Std and Adv kernel including 384K sample rate 🙂
-Tim
Got around the paypal browser out of date hurdle...
Looking foward to trying the new code out.
Would this be something for the todo list ? 😀
An externally hosted image should be here but it was not working when we last tested it.
dhcp would mean i wont need to run TFTPD32 and i can just plug the thing in. Could not get 3.1 going with a static IP for some reason.
I've got three MoOde units, all of them have always been static IP'd from the original 1.7 release.
Your problem is external to MoOde, maybe your IP settings were incorrect? That certainly one area I've never had a problem with MoOde.
Hi Tim,
DHCP on the ethernet port might suit a "minimalist" setup.
Where there is no (alot less) 3.x GHz energy in the listening room. The radiating element on the Pi is only a few cm from the underside of the DAC and a few more from the RCA cables.
Just connect a quiet laptop and play / stream music (without any network concerns)..
As bizzare as this may be (i cannot easily prove this), but there seems to be a slight difference in DAC output with / without wifi (Ver 3.1 wifi and bluetooth disabled on RPi3).
If i went with the wifi route for connectivity, ideally.... a wired connection from the Pi to a distant access point.
I really like the sound that i'm getting from the Moode audio player & the audiophonics i-sabre dac combo. I'm in the throes of coming up a functional listening area around it.
Great work!
I'm not sure what '3.xGHz in the listening room' is, but if your wifi is struggling to reach all parts of your house, fix your wifi.
You can run a long cable, if your environment makes that easy, but you could also use a PowerLine device to attenuate networking over your mains cables or upgrade your router to a MIMO-capable 802.11AC unit. All of those are easy and cheap to do.
If you bought an Apple TV and you were having trouble with connectivity, would you write to Apple to get them to change their device, or would you fix your environmental problem? It does rather seem like you're using the nut to crack the hammer.
Hi,
thanks Tim for the answers.
Unforunately, I can't get the volume limit to change, even after refreshing the web browser (or changing the web browser, in case this is a browser related issue).
Since Advanced kernel is not mandatory any more, I reversed to standard kernel, but still no change.
Here's some more info, if anyone encounters the problem :
When I click on vol+ I get the warning message. I change the value, press update and then I can raise vol one step further before getting the message again (from 20 to 21, from 21 to 22, etc.) but the value in the box remains locked at 20.
Since the alloboss supports it, I use hardware volume control. I have never encoutered this issue since I bought it.
Thanks again and have a nice day everybody !
thanks Tim for the answers.
Unforunately, I can't get the volume limit to change, even after refreshing the web browser (or changing the web browser, in case this is a browser related issue).
Since Advanced kernel is not mandatory any more, I reversed to standard kernel, but still no change.
Here's some more info, if anyone encounters the problem :
When I click on vol+ I get the warning message. I change the value, press update and then I can raise vol one step further before getting the message again (from 20 to 21, from 21 to 22, etc.) but the value in the box remains locked at 20.
Since the alloboss supports it, I use hardware volume control. I have never encoutered this issue since I bought it.
Thanks again and have a nice day everybody !
Well, much ado about nothing ... I disabled all dac related options then reconfigured and ... problem solved !
Sorry for bothering you 🙁
Thanks again for the great piece of software!
Sorry for bothering you 🙁
Thanks again for the great piece of software!
Hello Tim,
I just upgraded Moode to the last 3.8.1 version: I activated the USB boot option, but it seems that the software is still booting from the SD card. Is it then necessary to do manually something to transfer the software to my USB harddisk ?
Thank you in advance for your support,
I just upgraded Moode to the last 3.8.1 version: I activated the USB boot option, but it seems that the software is still booting from the SD card. Is it then necessary to do manually something to transfer the software to my USB harddisk ?
Thank you in advance for your support,
Hi @pkdick,
You have to write moOde image to a USB drive, same as writing it to an SD card.
Also, if you have both a bootable SD card and USB drive plugged in then Linux will boot from the SD card.
-Tim
You have to write moOde image to a USB drive, same as writing it to an SD card.
Also, if you have both a bootable SD card and USB drive plugged in then Linux will boot from the SD card.
-Tim
Hi @pkdick,
You have to write moOde image to a USB drive, same as writing it to an SD card.
Also, if you have both a bootable SD card and USB drive plugged in then Linux will boot from the SD card.
-Tim
Hi Tim,
Thank you for this information. So I have first to install MoOde on a SD, then activate the USB Boot mode (as I have a RPI 3B), then either install again MoOde on my USB hard disk or manage to copy my first SD installation on it, am I right ?
Hi @pkdick,
1) Boot from SD card and Configure your Pi-3 for USB boot. The (i) help text is below
Programs Pi-3B OTP memory to enable booting from USB drive.
- This is a pernament modification and only needs to be done once.
- After OTP is updated, system can boot from SD card or USB drive.
2) Write a fresh moOde 3.8.1 image to the USB drive using the same image writer that u use to write to an SD card. It should support writing to USB drive but if not then use one of the utilities in the following link from moOde Setup Guide.
WRITING MOODE IMAGE ONTO AN SD CARD OR USB DRIVE
Installing operating system images - Raspberry Pi Documentation
3) Plug in just the USB drive and then power up.
-Tm
1) Boot from SD card and Configure your Pi-3 for USB boot. The (i) help text is below
Programs Pi-3B OTP memory to enable booting from USB drive.
- This is a pernament modification and only needs to be done once.
- After OTP is updated, system can boot from SD card or USB drive.
2) Write a fresh moOde 3.8.1 image to the USB drive using the same image writer that u use to write to an SD card. It should support writing to USB drive but if not then use one of the utilities in the following link from moOde Setup Guide.
WRITING MOODE IMAGE ONTO AN SD CARD OR USB DRIVE
Installing operating system images - Raspberry Pi Documentation
3) Plug in just the USB drive and then power up.
-Tm
I have 3.8.1 version and i can*t connect it to a usb dac. In i2s device settings was earlier Usb Audio device possibility and none possibility. After choosing Usb Audio device dac plays. Now i have None and many I2s devices but no Usb Audio device possibility. After chosing none if i use usb device, usb dac is not working. I have no i2s device connected to PiB+why are shown in i2s devices...earlier was not so.
Thank you
Thank you
Hi @androa76,
For USB audio devices "I2S audio device" should be set to "None". This is how its always been when using USB audio device.
Per moOde Setup Guide:
1. INITIAL SETUP
a) insert boot SD card or USB drive
b) connect USB or I2S audio device
c) connect USB storage devices
- Ethernet mode
a) insert ethernet cable
b) power on
c) Nymeria
- Access Point (AP) mode
a) insert WiFi adapter that supports AP mode
b) power on
c) join network SSID=Moode, pwd=moodeaudio
d) Nymeria
2. AUDIO DEVICE SETUP
- USB DEVICE
a) Menu, Configure, Audio, MPD options: EDIT SETTINGS
b) leave Volume control set to "Software"
c) set Audio output to "USB audio device" then APPLY
- I2S DEVICE
a) Menu, Configure, Audio
b) select an I2S audio device then SET
c) reboot
d) Menu, Configure, Audio, MPD options: EDIT SETTINGS
e) leave Volume control set to "Software"
f) verify Audio device is set to "I2S audio device" then APPLY
-Tim
For USB audio devices "I2S audio device" should be set to "None". This is how its always been when using USB audio device.
Per moOde Setup Guide:
1. INITIAL SETUP
a) insert boot SD card or USB drive
b) connect USB or I2S audio device
c) connect USB storage devices
- Ethernet mode
a) insert ethernet cable
b) power on
c) Nymeria
- Access Point (AP) mode
a) insert WiFi adapter that supports AP mode
b) power on
c) join network SSID=Moode, pwd=moodeaudio
d) Nymeria
2. AUDIO DEVICE SETUP
- USB DEVICE
a) Menu, Configure, Audio, MPD options: EDIT SETTINGS
b) leave Volume control set to "Software"
c) set Audio output to "USB audio device" then APPLY
- I2S DEVICE
a) Menu, Configure, Audio
b) select an I2S audio device then SET
c) reboot
d) Menu, Configure, Audio, MPD options: EDIT SETTINGS
e) leave Volume control set to "Software"
f) verify Audio device is set to "I2S audio device" then APPLY
-Tim
- Home
- Source & Line
- PC Based
- Moode Audio Player for Raspberry Pi