Downloaded 2.0v too and checking it out currently.
Looking good
Just a more general question and not only moode related: is there an advantage to have the album cover as a separate "cover.jpg" file compared to an "embedded" cover approach (where the cover is added via MP3tag for instance) ?
Thanks in advance.
Looking good
Just a more general question and not only moode related: is there an advantage to have the album cover as a separate "cover.jpg" file compared to an "embedded" cover approach (where the cover is added via MP3tag for instance) ?
Thanks in advance.
Hi,
Thanks for the compliment!
I have 3 DAC's that have hardware volume controllers: IQaudIO Pi-DAC+, Hifiberry DAC+ and JDS Labs ODAC. The IQauDIO and Hifiberry devices use the same Burr Brown PCM5122 DAC chip and so I just test with the IQaudIO and ODAC devices.
Attached are screen shots of alsamixer for IQaudIO and ODAC. They show that for both devices the 0dB point is 100 on the main volume slider. Main volume is named 'PCM' for the ODAC and "Digital" for the IQaudIO device.
The IQaudIO device also has 2 analog volume controls named 'Analogue'. According to IQaudIO guy, these need to be set to 100 for 0dB overall for the device.
Note that the ALSA main volume can be set from Moode System config page.
What DAC are u using?
Regards,
Tim
Attachments
Downloaded 2.0v too and checking it out currently.
Looking good
Just a more general question and not only moode related: is there an advantage to have the album cover as a separate "cover.jpg" file compared to an "embedded" cover approach (where the cover is added via MP3tag for instance) ?
Thanks in advance.
Hi,
The advantage of separate album art file is that most audio players support this method and not all players, for example Moode, support embedded album art.
I have "implement embedded art method" on my to-do list but there is a learning curve that I have to get through to understand which is the best way to implement the feature. Plan is to implement it in one of the 2.x series releases.
In the meantime, if you don't already have separate art files in your collection then a utility or script can be used to automatically extract them from the song files and place them in the Album dirs.
I used a script from Doug's Apple Scripts to do this for my ALAC collection a while back. Now, whenever I add an album I just manually copy/paste the embedded image as Folder.jpg file.
Moode checks for Folder.jpg (upper case F) first so I'd suggest using this file name if you end up making separate album art files.
Regards,
Tim
For the first problem, I used a linux machine with GParted and now I've 28GB
Hi,
Maybe this can be automated and turned into a feature using a dedicated local folder instead of something under /WEBRADIO. What is the command string u used to make the partition larger?
Regards,
Tc
For the first problem, I used a linux machine with GParted and now I've 28GB
Well done
.for the second part... any files you store on the card should have off-card backup as whenever you update to a new version of MoOde the card will be overwritten.
Provided you are happy to resize and reload each update then I don't see a problem.
SDcards do have a finite number of read/write cycles so potential exists for increased wear... (I've not worn one out yet in 8 years of camera use so wonder if that is a real world issue ? anyone care to comment on their experiences...?)
Tim, I think we have both used the GParted gui...
That would be great ! I have tried to make a local folder using Ubuntu file manager but it says 'error backend not supported'
Last edited:
HTML:
Yes, I used GParted as graphical tool because on Linux it has been easy. I previously tried with some manual command on OSX without success.Tim, I think we have both used the GParted gui...
That would be great ! I have tried to make a local folder using Ubuntu file manager but it says 'error backend not supported'
And yes, also for me will be fantastic to have a directory just for upload my mp3 but I think that will be impossible to save the content in case of a new image of MoOde replacement. But I hope in Time ideas
Hi,
Source name:
This is a friendly name that you specify that represents the root of your music collection. I usually use the name Music. This name will show up in the Browse Panel under NAS.
File share protocol:
Most NAS devices come with the Samba package that provides SMB/CIFS file share protocol. Try this protocol unless you have specifically configured your NAS to use NFS. If thats the case then select NFS as the file share protocol.
IP address:
Enter the IP address of your NAS device in this field.
Remote directory:
In the file sharing section of your NAS device a Share Name can be defined that refers to a directory on the NAS. For example, lets say there is a directory on the NAS named /MyFiles that has the following sub directories:
/MyFiles
.../MyDocs
.../MyPhotos
.../MyMusic
If a Share Name called MYFILES were defined that refers to /MyFiles, the Remote directory field would be MYFILES/MyMusic
Username and Password:
If you have enabled access control on the directory containing your music collection then you need to enter the username and password in these fields.
Regards,
Tim
I would like to comment on the new way of setting the volume control:
At least with my Rpi2 and Hifiberry DAC+ you have to be carefull with the
amixer sset Digital (hwmixer)
On the command line you can specify the volume in dB
amixer sset Digital 0dB yields
Simple mixer control 'Digital',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 207 [81%] [0.00dB] [on]
Front Right: Playback 207 [81%] [0.00dB] [on]
If you set this any higher than ca. 82% in
MoOde customize "Hardware Volume Control"
the sound becomes increasingly distorted at 100% in the GUI (clipping).
BTW you can reduce the volume by x dB steps
for example by -6 dB from the 0dB level:
root@moode:~# amixer sset Digital 6dB-
Simple mixer control 'Digital',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 195 [76%] [-6.00dB] [on]
Front Right: Playback 195 [76%] [-6.00dB] [on]
root@moode:~#
Maybe this is only valid for the HifiBerry DAC+
YMMV Silicium
At least with my Rpi2 and Hifiberry DAC+ you have to be carefull with the
amixer sset Digital (hwmixer)
On the command line you can specify the volume in dB
amixer sset Digital 0dB yields
Simple mixer control 'Digital',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 207 [81%] [0.00dB] [on]
Front Right: Playback 207 [81%] [0.00dB] [on]
If you set this any higher than ca. 82% in
MoOde customize "Hardware Volume Control"
the sound becomes increasingly distorted at 100% in the GUI (clipping).
BTW you can reduce the volume by x dB steps
for example by -6 dB from the 0dB level:
root@moode:~# amixer sset Digital 6dB-
Simple mixer control 'Digital',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 195 [76%] [-6.00dB] [on]
Front Right: Playback 195 [76%] [-6.00dB] [on]
root@moode:~#
Maybe this is only valid for the HifiBerry DAC+
YMMV Silicium
Hi,
The Moode volume control maps knob 0-100 range to alsa 0-100 range using either a 1-1 (linear) mapping or a logarithmic mapping depending on the Yes/No Logarithmic setting on the Customize popup.
I just tested a Hifiberry DAC+ on 3.18.14 kernel and alsa 100 = a whopping +24dB gain! The 0dB gain point is reached at a very low alsa 40. This suggests an issue in the Hifiberry device driver. I think the driver is responsible for establishing the correct hardware to alsa 100 = 0dB gain mapping, but could be wrong about that.
Here is what the Moode -> ALSA volume mapping looks like for this DAC with Logarthmic volume on/off.
LOG YES: knob 47 = alsa 40 = 0dB
LOG NO : knob 81 = alsa 40 = 0dB
EITHER : knob 100 = alsa 100 = +24dB
A workaround that will achieve knob 100 = alsa 81 (0dB) is:
(1) set Logarithmic volume OFF
(2) set Max volume(%) to 81
NOTE: for the IQaudIO Pi-DAC+ which uses the same PCM5122 chip as Hifiberry DAC+, knob 100 = alsamixer 100 = 0dB gain.
Refer to attached Hifiberry and IQaudIO alsamixer screen shots.
Regards,
Tim
Attachments
Hi, how can i access a usb hard drive (files) plugged in raspberry pi using my macosx browser (safari) ?
Is it possible ? Like this www.moode.local\usb ?
They are in the same wifi network. By the way i would like to copy my music files (located in macbook) direct to raspberry pi external usb hard drive.
thanks in advance
Is it possible ? Like this www.moode.local\usb ?
They are in the same wifi network. By the way i would like to copy my music files (located in macbook) direct to raspberry pi external usb hard drive.
thanks in advance
Hi Tim,
My "workaround", if you like to call it a workaround,
only limits the h/w volume control to 81%
No need to disable logarithmic volume.
Dial @ 100% corresponds to 207 [81%] 0.00dB
Audio Information
...
DSP Operations
Resampler: off
Format:
Volume: Hardware, Logarthmic curve, More (+18) slope, Vol-max 81%
...
Audio Device
Device: HiFiBerry DAC+
DAC chip: Burr Brown PCM5122
Architecture: Sigma/Delta Advanced Segment 24 bit 192 kHz
Interface: I2S
Other: H/W volume
Can you explain what alsa 40 vs. alsa 81 means?
Isn't it just a different (display) mapping?
I can only see that reducing the alsa volume in the GUI to, for example,
20% just reduces the amixer sget Digital value to 67%. Anything else?
BTW: amixer sset Analogue 0/1 reduces/increases the output by 6dB
I don't know at which point in the signalprocessing this occurs
root@moode:~# amixer sset Analogue 0
Simple mixer control 'Analogue',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 1
Mono:
Front Left: Playback 0 [0%] [-6.00dB]
Front Right: Playback 0 [0%] [-6.00dB]
root@moode:~# amixer sset Analogue 1
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]
My "workaround", if you like to call it a workaround,
only limits the h/w volume control to 81%
No need to disable logarithmic volume.
Dial @ 100% corresponds to 207 [81%] 0.00dB
Audio Information
...
DSP Operations
Resampler: off
Format:
Volume: Hardware, Logarthmic curve, More (+18) slope, Vol-max 81%
...
Audio Device
Device: HiFiBerry DAC+
DAC chip: Burr Brown PCM5122
Architecture: Sigma/Delta Advanced Segment 24 bit 192 kHz
Interface: I2S
Other: H/W volume
Can you explain what alsa 40 vs. alsa 81 means?
Isn't it just a different (display) mapping?
I can only see that reducing the alsa volume in the GUI to, for example,
20% just reduces the amixer sget Digital value to 67%. Anything else?
BTW: amixer sset Analogue 0/1 reduces/increases the output by 6dB
I don't know at which point in the signalprocessing this occurs
root@moode:~# amixer sset Analogue 0
Simple mixer control 'Analogue',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 1
Mono:
Front Left: Playback 0 [0%] [-6.00dB]
Front Right: Playback 0 [0%] [-6.00dB]
root@moode:~# amixer sset Analogue 1
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]
For a file based access (copy/delete etc.) you should use
either the SMB or the NFS protocol.
For example SMB: \\MOODE\USB Music\<subfolder>
I assume that you are familiar with both protocols.
Within Moode you can see the detected USB devices via
http://moode.fritz.box/sources.php
Any detected USB sources should be listed there.
Subsequently update the MPD DB and the songs will be added
to the library.
As I am not using USB-storage devices on my Moode player myself I could be wrong here.
Last edited:
Hi,
(1) Volume: Hardware, Logarthmic curve, More (+18) slope, Vol-max 81%
Interesting. I see that selecting logarithmic curve and a steep slope (More +18) also compensates for the mapping issue in the Hifiberry driver.
(2) Can you explain what alsa 40 vs. alsa 81 means? Isn't it just a different (display) mapping?
One of the challenges associated with volume is that there are several different unit scales in use that are all related to one another through math. I should have used the term Alsamixer instead of alsa... Alsamixer units are different than the percentages shown in MPD and amixer. See NOTE #1 below.
The volume mapping in Moode works by taking the knob setting and computing the appropriate logarithmic value then setting MPD volume to this value. MPD uses a percentage scale. If logarithmic volume is set to No then MPD volume is set to the knob value as-is.
Attached is a screen shot of Hifiberry and IQaudIO examples with added volume scales. The data suggests the Hifiberry DAC+ driver might be reporting an incorrect hardware volume range to ALSA.
(3) BTW: amixer sset Analogue 0/1 reduces/increases the output by 6dB. I don't know at which point in the signalprocessing this occurs
Since they are analog controls I would assume they receive the signal after the DAC stage. According to the IQaudIO guy, the two analogue volume controls in PCM5122 should both be set to 100. I assume it's the same for the Hifiberry DAC+
NOTE #1: (from an old 2011 alsa devel maining list)
"Now, alsamixer shows the percentage in a different way. It's
explained well in the source code (alsamixer/volume_mapping.c), but
not mentioned in the man page, unfortunately.
* The mapping is designed so that the position in the interval is proportional
* to the volume as a human ear would perceive it (i.e., the position is the
* cubic root of the linear sample multiplication factor). For controls with
* a small range (24 dB or less), the mapping is linear in the dB values so
* that each step has the same size visually. Only for controls without dB
* information, a linear mapping of the hardware volume register values is used
* (this is the same algorithm as used in the old alsamixer).
The percentage representation in alsamixer corresponds to this
mapping, thus it's neither dB nor linear percent."
Regards,
Tim
