From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-200165-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id DA58C158020
for <garchives@archives.gentoo.org>; Sun, 11 Dec 2022 04:45:37 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 48683E08FB;
Sun, 11 Dec 2022 04:45:33 +0000 (UTC)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 0DCB3E08E0
for <gentoo-user@lists.gentoo.org>; Sun, 11 Dec 2022 04:45:32 +0000 (UTC)
Received: by mail-lf1-x129.google.com with SMTP id c1so13265398lfi.7
for <gentoo-user@lists.gentoo.org>; Sat, 10 Dec 2022 20:45:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20210112;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:from:to:cc:subject:date:message-id:reply-to;
bh=k/4B7aNLOfcg5+th/6mFyLexJ8e8FmLP+SJqKfQfKc8=;
b=aLa4k8in0vfSjRgFP5HjIBZVDTChIKPVjmvMdCPbZEz8alRc9r7IzVSCT9TkZTcfJ6
pZubO5GMSYNtBEJlvLdvY2orU4KDjCrBHNOdoKNXbG7/SFyqH89X3fn7XzmBzu+3xsF4
IijUrJdQxG5rpzR/jWKy2ZURX2Nlpqk1tmchU88m1gsBhfE8eLKWEaYXUZf/687w7xtV
cOJ8xM5p5ZGmckY3OZp/F7oNcTke+ksmCdFkUzHo5Lz4Kylqf28ejPzRrCwWo2RF2wGO
5S6ALmbKgKarVJy8H4eA8LK9FcWLq37kOm4Fkz/wbyxiksijU1khLtRKLvSBkXZBFGTO
3JKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
bh=k/4B7aNLOfcg5+th/6mFyLexJ8e8FmLP+SJqKfQfKc8=;
b=CM5x+2wBDScDKbJ82neSvX2IBC/MhkWiKCCQhu4H1+617VKS4IuUzNbHVcgliUWGiR
unTyqJrdDvNA4OpS1GVwy1wngey1KQ+ly6chIxKpFoHN/hKRJ0k6cNeYTgZC76LRha53
AEyv9LEYSsnIXIuQ6DDWJllAOVHkKwbcKSGoT9tLPXQu6eLDh9CYhdrEJZnfGdjaFZ92
1ZkiI1nmrYMOgpPZgx+UibN4ykfzLBmYG2cyd8FuZCXa8AsdLXsemwGqVHuW6oX26u70
q6LuObfx0PKjNM4pkBtQuPtpd0qpGfC9PeIYAhDnxS0cVAp9N4ayUX9gYPN4ZnS5HDjx
eFlw==
X-Gm-Message-State: ANoB5plQuEIv6gDOFO2ge9SPzgypoxRB3b2B7urz1UEdVz/Mt6c+k5/J
AbJpHJiDUnRNh/Zit/RgKThD9PBuXHRU3udRFK99HNDbmXI=
X-Google-Smtp-Source: AA0mqf5lbwfHdlVSAkYfJjnBDA8YGhfR1b5KSHA4JPv8oGnHmD5icc3hJ7N+Fad/zwoYWIR0NHfM/iA+ArMahugXh/k=
X-Received: by 2002:a05:6512:2820:b0:4b5:88f0:72d1 with SMTP id
cf32-20020a056512282000b004b588f072d1mr3767918lfb.446.1670733931399; Sat, 10
Dec 2022 20:45:31 -0800 (PST)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
References: <9407e524-2226-6ba9-dd7f-bac635d083e3@gmail.com>
<c6f53c43-18f6-a034-aa50-2bc399856a61@youngman.org.uk> <Y5JMyHK/Tai8lfJt@schatulle>
<2398014.jE0xQCEvom@lenovo.localdomain> <Y5M6WLDk3yYnXEml@tp>
<73aa65e5-5384-be5c-d545-91dfc4d73095@youngman.org.uk> <Y5SxdZfNaJSusiWq@schatulle>
In-Reply-To: <Y5SxdZfNaJSusiWq@schatulle>
From: David Rosenbaum <rosenbaumd181@gmail.com>
Date: Sat, 10 Dec 2022 23:45:20 -0500
Message-ID: <CAL+8heNt38thFr984Twd+cj6W7_fTdKXuChTY4EJdv=bDGvJ6A@mail.gmail.com>
Subject: Re: [gentoo-user] NAS and replacing with larger drives
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary="0000000000007eccfc05ef860e5f"
X-Archives-Salt: d55069a9-d635-4793-8898-82a595e33b77
X-Archives-Hash: 9667faabce653c60eac36a5a367e5f48
--0000000000007eccfc05ef860e5f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thanks
Dave
On Sat, Dec 10, 2022, 11:19 AM Frank Steinmetzger <Warp_7@gmx.de> wrote:
> Am Sat, Dec 10, 2022 at 09:20:17AM +0000 schrieb Wols Lists:
>
> > > > Depending on the PVR make/model I've seen 1080p resolution
> recordings with
> > > > .m2ts and .ts file extensions, while the codecs inside them are the
> same.
> -------------------------------------^^^^^^^^^^^^^^^^^^^^^^^
> >
> > > I wasn=E2=80=99t aware that ts could contain h264. But then again=E2=
=80=94I never
> really
> ---------------------------------^^^^^^^
> > > bothered with live TV recordings in recent years.
>
> > I think this is confusing CONTAINER and CODEC.
>
> Where do we confuse those two? We specifically talked of codecs and
> =E2=80=9Ccontain=E2=80=9D.
>
> > .ts is a container format, h264 is a codec. I don't understand it mysel=
f,
> > either but think of ts as your directory structure and h264 as your fil=
e
> > structure.
>
> Now you are confusing me. You say you don=E2=80=99t understand it, but th=
en explain
> it. TS is like AVI and MKV: a file structure for the payload data. And
> payload data can be all kinds of stuff, from ASS plaintext subtitles, ove=
r
> opus audio to mpeg2 or h264 video.
>
> > Incidentally, sticking this stuff in a .tar is probably okay - that's
> just
> > another container, but sticking it in a .tar.gz is not, the gz is your
> codec
> > and will make the file BIGGER in all probability.
>
> Tar does not compress, it simply puts all inputs in a 1:1 stream. It does
> add some metadata (filename and so on). Packers reduce data volume by
> increasing information-per-byte. So if the total information stays the sa=
me
> (for lossless coding), the number of bytes decreases. Encoded video data
> ideally has even entropy. It is indistinguishable from random noise. That=
=E2=80=99s
> why compressing it again does not yield anything, or even adds some volum=
e
> again.
>
> --
> Gr=C3=BC=C3=9Fe | Greetings | Salut | Qapla=E2=80=99
> Please do not share anything from, with or about me on any social network=
.
>
> =E2=80=9CMankind must put an end to war or war will put an end to mankind=
.=E2=80=9D
> =E2=80=93 John F. Kennedy
>
--0000000000007eccfc05ef860e5f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Thanks<br><br><div data-smartmail=3D"gmail_signature">Dav=
e</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Sat, Dec 10, 2022, 11:19 AM Frank Steinmetzger <<a href=3D"mai=
lto:Warp_7@gmx.de">Warp_7@gmx.de</a>> wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Am Sat, Dec 10, 2022 at 09:20:17AM +0000 schrieb Wols Lists:<=
br>
<br>
> > > Depending on the PVR make/model I've seen 1080p resoluti=
on recordings with<br>
> > > .m2ts and .ts file extensions, while the codecs inside them =
are the same.<br>
-------------------------------------^^^^^^^^^^^^^^^^^^^^^^^<br>
> <br>
> > I wasn=E2=80=99t aware that ts could contain h264. But then again=
=E2=80=94I never really<br>
---------------------------------^^^^^^^<br>
> > bothered with live TV recordings in recent years.<br>
<br>
> I think this is confusing CONTAINER and CODEC.<br>
<br>
Where do we confuse those two? We specifically talked of codecs and<br>
=E2=80=9Ccontain=E2=80=9D.<br>
<br>
> .ts is a container format, h264 is a codec. I don't understand it =
myself,<br>
> either but think of ts as your directory structure and h264 as your fi=
le<br>
> structure.<br>
<br>
Now you are confusing me. You say you don=E2=80=99t understand it, but then=
explain<br>
it. TS is like AVI and MKV: a file structure for the payload data. And<br>
payload data can be all kinds of stuff, from ASS plaintext subtitles, over<=
br>
opus audio to mpeg2 or h264 video.<br>
<br>
> Incidentally, sticking this stuff in a .tar is probably okay - that=
9;s just<br>
> another container, but sticking it in a .tar.gz is not, the gz is your=
codec<br>
> and will make the file BIGGER in all probability.<br>
<br>
Tar does not compress, it simply puts all inputs in a 1:1 stream. It does<b=
r>
add some metadata (filename and so on). Packers reduce data volume by<br>
increasing information-per-byte. So if the total information stays the same=
<br>
(for lossless coding), the number of bytes decreases. Encoded video data<br=
>
ideally has even entropy. It is indistinguishable from random noise. That=
=E2=80=99s<br>
why compressing it again does not yield anything, or even adds some volume<=
br>
again.<br>
<br>
-- <br>
Gr=C3=BC=C3=9Fe | Greetings | Salut | Qapla=E2=80=99<br>
Please do not share anything from, with or about me on any social network.<=
br>
<br>
=E2=80=9CMankind must put an end to war or war will put an end to mankind.=
=E2=80=9D<br>
=C2=A0=E2=80=93 John F. Kennedy<br>
</blockquote></div>
--0000000000007eccfc05ef860e5f--