nerdculture.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
Be excellent to each other, live humanism, no nazis, no hate speech. Not only for nerds, but the domain is somewhat cool. ;) No bots in general. Languages: DE, EN, FR, NL, ES, IT

Administered by:

Server stats:

1.2K
active users

#mpeg2ts

0 posts0 participants0 posts today
T_X<p><span class="h-card" translate="no"><a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ffhl</span></a></span> <span class="h-card" translate="no"><a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>videolan</span></a></span> (wobei "proprietär" vll. doch etwas zu stark ist, gibt da zumindest <a href="https://chaos.social/tags/RFC2250" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC2250</span></a>, dass das <a href="https://chaos.social/tags/MPEG2TS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MPEG2TS</span></a> für <a href="https://chaos.social/tags/RTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RTP</span></a> spezifiziert. Und für die <a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a> muss es ja eigentlich patentfrei sein? Aber ich bin an sich kein Freund von der <a href="https://chaos.social/tags/MPEG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MPEG</span></a>, die sonst für ihr Patentmafia-Wesen berüchtigt sind.)</p>
T_X<p><span class="h-card" translate="no"><a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ffhl</span></a></span> <span class="h-card" translate="no"><a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>videolan</span></a></span> die technische Hintergrund der neuen Streams:<br>Statt <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> / UDP / <a href="https://chaos.social/tags/RTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RTP</span></a> / <a href="https://chaos.social/tags/Opus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Opus</span></a>. Ist es jetzt: IPv6 / UDP / <a href="https://chaos.social/tags/MPEG2TS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MPEG2TS</span></a> / RTP / Opus.<br>Es ist also noch ein gaaanz toller (Sarkasmus), proprietärer, unnötiger Protokollheader dazwischen gekommen, der nur das Paket aufbläht. VLC v3 kann aber noch nicht das <a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IETF</span></a> <a href="https://chaos.social/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> standardisierte, native RTP-Opus, das kann erst der nightly/v4.<br>Sobald VLC endlich mal releasen sollte, schmeiß ich das MPEG-TS auch ganz schnell wieder weg.</p><p><a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>multicast</span></a></p>