similar to: Why do non-lvds monitors default to dithering these days?

https://bugs.freedesktop.org/show_bug.cgi?id=34680 Summary: Enable dithering by default for eDP panels Product: xorg Version: unspecified Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Nicholas is probably right about noise. Another factor would simply be the amplitude of the resulting file. A 275 MB 24-bit file which compresses to 110 MB is probably not very loud. I assume that the average level is somewhat low, with few if any peaks that reach 0 dBFS. FLAC is very good at compressing audio that is not loud. In fact, the quieter the recording, the smaller the

https://bugs.freedesktop.org/show_bug.cgi?id=92297 Bug ID: 92297 Summary: dithering detected incorrectly Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: minor Priority: medium Component: Driver/nouveau Assignee: nouveau at

On 03/02/2018 11:29 PM, Ilia Mirkin wrote: > On Fri, Mar 2, 2018 at 5:16 PM, Mario Kleiner > <mario.kleiner.de at gmail.com> wrote: >> On 03/01/2018 07:21 PM, nouveau-request at lists.freedesktop.org wrote: >>> >>> >>> Message: 1 >>> Date: Thu, 1 Mar 2018 08:15:55 -0500 >>> From: Ilia Mirkin <imirkin at alum.mit.edu> >>>

Someone sent me a question late last night and I briefly looked at his file this morning and couldn't figure out the answer, so I'm posting here. A friend has a a ~275MB 24 bit, 48khz stereo wav file of rock music that when compressed using flac level 8 gives a flac file under 110 MB in size. When I dithered his file to 16/48 and converted that file to flac, the resulting flac file was

On Dec 2, 2010, at 07:55, scott brown wrote: > My first thought was that the file had low levels (before he sent > me the file), but that's definitely not the case with this file. > There are many peaks that reach 0dBFS. Live, uncompressed music often has peaks that are 4 dB higher, or more, than a typical commercial CD. Such peaks are brief, and would not really affect the

On 03/01/2018 07:21 PM, nouveau-request at lists.freedesktop.org wrote: > > Message: 1 > Date: Thu, 1 Mar 2018 08:15:55 -0500 > From: Ilia Mirkin <imirkin at alum.mit.edu> > To: Mario Kleiner <mario.kleiner.de at gmail.com> > Cc: nouveau <nouveau at lists.freedesktop.org> > Subject: Re: [Nouveau] [PATCH] Fix colormap handling at screen depth > 30. >

While we expose the ability to turn off hardware dithering for nouveau, we actually make the mistake of turning it on anyway, due to dithering_depth containing a non-zero value if our dithering depth isn't also set to 6 bpc. So, fix it by never enabling dithering when it's disabled. Signed-off-by: Lyude Paul <lyude at redhat.com> --- drivers/gpu/drm/nouveau/dispnv50/head.c | 24

While we expose the ability to turn off hardware dithering for nouveau, we actually make the mistake of turning it on anyway, due to dithering_depth containing a non-zero value if our dithering depth isn't also set to 6 bpc. So, fix it by never enabling dithering when it's disabled. Signed-off-by: Lyude Paul <lyude at redhat.com> --- drivers/gpu/drm/nouveau/dispnv50/head.c | 24

While we expose the ability to turn off hardware dithering for nouveau, we actually make the mistake of turning it on anyway, due to dithering_depth containing a non-zero value if our dithering depth isn't also set to 6 bpc. So, fix it by never enabling dithering when it's disabled. Signed-off-by: Lyude Paul <lyude at redhat.com> --- drivers/gpu/drm/nouveau/dispnv50/head.c | 24

From: Lyude Paul <lyude at redhat.com> [ Upstream commit fb2420b701edbf96c2b6d557f0139902f455dc2b ] While we expose the ability to turn off hardware dithering for nouveau, we actually make the mistake of turning it on anyway, due to dithering_depth containing a non-zero value if our dithering depth isn't also set to 6 bpc. So, fix it by never enabling dithering when it's disabled.

From: Lyude Paul <lyude at redhat.com> [ Upstream commit fb2420b701edbf96c2b6d557f0139902f455dc2b ] While we expose the ability to turn off hardware dithering for nouveau, we actually make the mistake of turning it on anyway, due to dithering_depth containing a non-zero value if our dithering depth isn't also set to 6 bpc. So, fix it by never enabling dithering when it's disabled.

From: Lyude Paul <lyude at redhat.com> [ Upstream commit fb2420b701edbf96c2b6d557f0139902f455dc2b ] While we expose the ability to turn off hardware dithering for nouveau, we actually make the mistake of turning it on anyway, due to dithering_depth containing a non-zero value if our dithering depth isn't also set to 6 bpc. So, fix it by never enabling dithering when it's disabled.

From: Lyude Paul <lyude at redhat.com> Nvidia display hardware provides a set of flexible dithering options for CRTCs. This dithering is actually noticeable in the CRC output for all available tap points, and can be seen as CRC values for identical frames cycling between either 2 or 4 values repeatedly (each one of these values is a different dithering phase applied to the source output).

From: Lyude Paul <lyude at redhat.com> Nvidia display hardware provides a set of flexible dithering options for CRTCs. This dithering is actually noticeable in the CRC output for all available tap points, and can be seen as CRC values for identical frames cycling between either 2 or 4 values repeatedly (each one of these values is a different dithering phase applied to the source output).

In case anyone's curious about 30bpp framebuffer support, here's the current status: Kernel: Ben and I have switched the code to using a 256-based LUT for Kepler+, and I've also written a patch to cause the addfb ioctl to use the proper format. You can pick this up at: https://github.com/skeggsb/linux/commits/linux-4.16 (note the branch!)

> Regarding dithering, I am not aware of many programs that do that without > very specific user selection. Any user savvy enough to turn on dithering > would hopefully be paying attention well enough to avoid promoting 16-bit to > 24-bit without noticing their mistake. I suspect that this is sometimes done dishonestly in order to sell hi-fi enthusiasts DVD-A's made from

On Jan 7, 2011, at 18:08, Declan Kelly wrote: > On Fri, Jan 07, 2011 at 05:11:26PM -0800, brianw at sounds.wa.com wrote: > [NIN 24/96] > >> Thanks! That's interesting to note. I think that I ended up with >> the true 24/96 files, but I am curious: How do you tell whether you >> have the full 24/96 or not? > > Extract to WAV, do a hex dump, and look for

Thanks for the replies! My first thought was that the file had low levels (before he sent me the file), but that's definitely not the case with this file. There are many peaks that reach 0dBFS. He sent me the original wav this morning and I loaded it into Wave Editor on OS X. I dithered to 16 bit using MBIT+ (high/ultra setting) and saved the 16 bit file. I did nothing else (no

https://bugs.freedesktop.org/show_bug.cgi?id=111199 Bug ID: 111199 Summary: Bug in dither.depth property set Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at