For various embedded environments that use busybox it's busybox's brand of ash. I generally enjoy the opportunity to learn when bumping up against these kind of edge cases.
Aye. Even though I'm more than happy to rely on bashisms in my normal work/play, I like to know where the edges are. Even if I don't know off the top of my head what the POSIX way is for something I usually use the bash sugar for, when I need it I know I need it and how to find it.
I also really enjoyed this show and rewatched it a few years ago on DVD. But I certainly noticed the main title music was different. I don't recall noticing in-episode music though, and wouldn't have remembered it from the show.
I went looking for the PAL DVDs after seeing your comment, and found one season but not a full set. After looking a little online it seems like the PAL release might have been cropped down a bit from the NTSC release? If that's the case it seems pretty disappointing.
Wouldn't this require a man-in-the-middle since the PS5 is transmitting data to a specific server, YouTube or Twitch in the article?
There are extensions to RTMP to use encryption or even just TLS. But do you mean that the risk of fragments of audio and video bitstreams going out unprotected presents a remote code execution risk? That seems less a problem of vulnerability and more one of privacy.
In my (admittedly limited) experience, adding audio tracks to a video track that weren't produced together often requires editing. If not for sample rate reasons, content reasons, like extra space for additional video space at the beginning or ending most basically. It seems like in any instances like that, which I would count as "nominal," it would be appropriate to identify those as "modified from" which would seemingly place you squarely into "hybrid" space within the taxonomy of this comment thread.
Right. There is some degree of transformation which is normal or necessary. For example, if one of {video, audio} is 24fps and the other is 23.976fps, the video will have its frame rate adjusted to match the audio. For basic video/audio mismatches you may need to trim audio, insert null audio, or add a mkv container delay.
These things are normally detailed in release notes. People write pretty detailed notes laying out exactly what they did.
The muxer can apply a timestamp offset to a track, so while the audio stream remains untouched it starts at some offset relative to the start of the video stream.
Agree once you're compensating for drift by scaling the audio track you've pushed yourself out of remux territory, but again these aren't hard and fast rules (evidenced by the disagreement over terminology).
Scrubs was another one with pretty obvious music changes, because some were part of the dialogue or a joke that just doesn't make sense after the change.
> Movies and especially TV shows on the other hand are a mess. It shouldn't be a miracle to get a high-quality, faithful official remaster like the one Star Trek: TNG got.
Star Trek: TNG was a bit of a special case though, because it had to be re-cut and new digital special effects created and edited into scenes.
I think this perspective holds more true for things that were broadcast in HD but only got commercial DVD releases. That's a disappointing lapse in high quality availability where HD content was distributed, just not in a persistent form for home use. In those cases the best quality available is an HD TV or satellite recording which might not have been preserved even in online media sharing communities.
And on top of all that, sales were not what they hoped, and with that we lost any chance of an official remaster of DS9 or Voyager, since the same work would have to be done as for TNG.
reply