I have spotted a minor GUI issue which is present up to version 8.3.7:
Cover images which have a larger height than width (e.g. the picture of a DVD sized case with a ratio of roughly 1.4) pose problems for the GUI in some places: On the main screen the space below the image may get too small to fully display the track title and metadata (which are just cut off at the bottom of the screen). In tag library view the cover image on the left hand side of the track list is cut off at the bottom.
Note that other parts of the GUI handle these cover images perfectly: Im album view, for example, the full cover image is shown nicely in the rectangular grid.
I have spotted a minor GUI issue which is present up to version 8.3.7:
Cover images which have a larger height than width (e.g. the picture of a DVD sized case with a ratio of roughly 1.4) pose problems for the GUI in some places: On the main screen the space below the image may get too small to fully display the track title and metadata (which are just cut off at the bottom of the screen). In tag library view the cover image on the left hand side of the track list is cut off at the bottom.
Note that other parts of the GUI handle these cover images perfectly: Im album view, for example, the full cover image is shown nicely in the rectangular grid.
Regards
Jens
Post one of the images and I'll test on my end.
Hi Tim,
I tried on my side... the fix (not needed everywhere, from what I can see) consists to always specify width AND height (and both the same) in the IMG tags' css, together with object-fit: contain
Any image with height != width, such as 500 x 300 (AND reverse) should highlight the issue.
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.
(01-24-2024, 12:57 AM)michaelagiles Wrote: 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.
Do you perhaps happen to have one of those DACs that can report the sample rate they are getting?
It could be a bug in SOX, although I doubt. It could also be a miscalculation in moOde's Audio-info page. The DAC, though, will definitely tell us the truth.
(01-24-2024, 12:57 AM)michaelagiles Wrote: 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.
Do you perhaps happen to have one of those DACs that can report the sample rate they are getting?
It could be a bug in SOX, although I doubt. It could also be a miscalculation in moOde's Audio-info page. The DAC, though, will definitely tell us the truth.
It is the ProtoDac. I have no idea about what it can report but would guess that it has no such capability.
Thanks!
01-24-2024, 06:22 AM (This post was last modified: 01-24-2024, 06:23 AM by Nutul.)
(01-24-2024, 03:40 AM)michaelagiles Wrote:
(01-24-2024, 02:43 AM)Nutul Wrote:
(01-24-2024, 12:57 AM)michaelagiles Wrote: 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.
Do you perhaps happen to have one of those DACs that can report the sample rate they are getting?
It could be a bug in SOX, although I doubt. It could also be a miscalculation in moOde's Audio-info page. The DAC, though, will definitely tell us the truth.
It is the ProtoDac. I have no idea about what it can report but would guess that it has no such capability.
Thanks!
Yes, I see now.
Well, to be sure SOX acts correctly the only thing I can think of is one of us setting up the resampling as you did, and check how things go with the two base-frequencies.
I've never done such a thing, but maybe later today I can try. My DAC reports on its screen what is being fed with, so the check will be quick to do.
(01-24-2024, 12:57 AM)michaelagiles Wrote: 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.
(01-24-2024, 12:57 AM)michaelagiles Wrote: 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.
