Official moOde 8 support thread

[michaelagiles]

I have had an issue arise that maybe someone can help with. I have setup SOX resampling to selectively resample to 384 but adhere to the base frequency.  This works for 44.1, resampling to 352 but on 48 base data it still indicates 352 rather than the correct 384 when I check Audio Info. Is this what is actually happening or is it a reporting error?
Can it be corrected?
MG

Pi 4b, FifopiMA, Moode 8.3.7,  ProtoDAC, Pass B1 , Pass SLOB active Xover, Luxman and Ayima, OB Markaudio and Dayton Audio.

A quick test and I'm not seeing this issue.
The ProtoDAC is on top of an Allo Kali Reclocker.



Try without the FifoPiMa

I will try next time I have it apart. Till then I posted a screenshot of audio info, I will try sample to 192 and see if that works.
MG

[Tim Curtis]

I have had an issue arise that maybe someone can help with. I have setup SOX resampling to selectively resample to 384 but adhere to the base frequency.  This works for 44.1, resampling to 352 but on 48 base data it still indicates 352 rather than the correct 384 when I check Audio Info. Is this what is actually happening or is it a reporting error?
Can it be corrected?
MG

Pi 4b, FifopiMA, Moode 8.3.7,  ProtoDAC, Pass B1 , Pass SLOB active Xover, Luxman and Ayima, OB Markaudio and Dayton Audio.

A quick test and I'm not seeing this issue.
The ProtoDAC is on top of an Allo Kali Reclocker.



Try without the FifoPiMa

I will try next time I have it apart. Till then I posted a screenshot of audio info, I will try sample to 192 and see if that works.
MG

Try w/o polarity inversion and then if no change turn off the custom SoX settings and retry.

[michaelagiles]

I have had an issue arise that maybe someone can help with. I have setup SOX resampling to selectively resample to 384 but adhere to the base frequency.  This works for 44.1, resampling to 352 but on 48 base data it still indicates 352 rather than the correct 384 when I check Audio Info. Is this what is actually happening or is it a reporting error?
Can it be corrected?
MG

Pi 4b, FifopiMA, Moode 8.3.7,  ProtoDAC, Pass B1 , Pass SLOB active Xover, Luxman and Ayima, OB Markaudio and Dayton Audio.

A quick test and I'm not seeing this issue.
The ProtoDAC is on top of an Allo Kali Reclocker.



Try without the FifoPiMa

I will try next time I have it apart. Till then I posted a screenshot of audio info, I will try sample to 192 and see if that works.
MG

Try w/o polarity inversion and then if no change turn off the custom SoX settings and retry.

No change with either phase inversion settings or non custom recipe. But A192 seems to work. If i switch back to 384 the next play works but only 1 play! After that it reverts to 352.

[Tim Curtis]

Very odd.
In Audio Config what I2S selection (driver) are you using?

The ProtoDAC w/o reclocker or with a reclocker like Allo Kali or FifoPi Qx should use the i2s-dac (passive mode) driver. This is automatically assigned when selecting "ProtoDAC TDA1387 X8" from the I2s dropdown.

For the FifoPiMa recliocker the hifiberry-dacplus (master mode) driver should be used. This is automatically assigned when selecting "ProtoDAC TDA1387 X8 (FifoPiMa)" from the I2s dropdown.

[michaelagiles]

Very odd.
In Audio Config what I2S selection (driver) are you using?

The ProtoDAC w/o reclocker or with a reclocker like Allo Kali or FifoPi Qx should use the i2s-dac (passive mode) driver. This is automatically assigned when selecting "ProtoDAC TDA1387 X8" from the I2s dropdown.

For the FifoPiMa recliocker the hifiberry-dacplus (master mode) driver should be used. This is automatically assigned when selecting "ProtoDAC TDA1387 X8 (FifoPiMa)" from the I2s dropdown.

I had been using the hifiberry driver and just changed to the protodac+hifiberry. No change.

[Tim Curtis]

I suppose the next logical test is to take the Q7 out of the stack and just run the ProtoDAC + Pi using the "ProtoDAC TDA1387 X8" I2S selection.

[Tim Curtis]

I have created a test cover file and also attached the result I see in the WebUI on my notebook. Thanks for having a look!

Best regards
Jens

Cover file (500 x 350):


Main screen:


Tag view:


Album view:

I've gotten to this item on the TODO list and I have some comments and questions.

Comments:

Since the aspect ration of these DVD style covers is portrait the way to format them so they can correctly be displayed as Album art is to actually add letterboxing on the sides using an image editor In my case using Pixelmator I would expand the canvas horizontally to match the image height and then fill the new empty side spaces in the canvas with black or gray. I end up with a square image after doing that and it appears correctly in the WebUI.

If thats not done and instead the CSS is modified as @Nutul suggested we end up with oddness in several areas:

1. In Album view the (...) menu icon is halfway outside the cover image
2. In Playback view it just looks odd seeing a DVD sized cover :-0
3. In Playbar, Folder view, Queue, etc the small thumbs are already square but the image is heavily distorted. It may be some upstream CSS that making them square or possibly something in the Thumbnail generator.

Question:

How many of these types of covers are we talking about in a typical music collection?

[Nutul]

I have created a test cover file and also attached the result I see in the WebUI on my notebook. Thanks for having a look!

Best regards
Jens

Cover file (500 x 350):


Main screen:


Tag view:


Album view:

I've gotten to this item on the TODO list and I have some comments and questions.

Comments:

Since the aspect ration of these DVD style covers is portrait the way to format them so they can correctly be displayed as Album art is to actually add letterboxing on the sides using an image editor In my case using Pixelmator I would expand the canvas horizontally to match the image height and then fill the new empty side spaces in the canvas with black or gray. I end up with a square image after doing that and it appears correctly in the WebUI.

If thats not done and instead the CSS is modified as @Nutul suggested we end up with oddness in several areas:

1. In Album view the (...) menu icon is halfway outside the cover image
2. In Playback view it just looks odd seeing a DVD sized cover :-0
3. In Playbar, Folder view, Queue, etc the small thumbs are already square but the image is heavily distorted. It may be some upstream CSS that making them square or possibly something in the Thumbnail generator.

Question:

How many of these types of covers are we talking about in a typical music collection?

You can manipulate all the images in batch with imagemagik. I actually use it to crop / rescale the album art in all my flacs to always be 500x500
Its syntax is not the easiest to understand, but given an image it can do literally everything to it.

[michaelagiles]

I suppose the next logical test is to take the Q7 out of the stack and just run the ProtoDAC + Pi using the "ProtoDAC TDA1387 X8" I2S selection.

Its not that important at the moment. When I have to disassemble for some reason. I'm enjoying the music too much!

I checked HiFiBerry's website and this DAC has a limit of 192k. Could this be reflected in the driver somehow and limiting the output rate available? Just a thought.
I will ask Iancanada also - he might have an idea about whats happening.
Thanks!

[Tim Curtis]

The driver for PCM5xxx supports up to 384K.