u/yeaahnop

but for linux users, with bash, no autokey needed.

https://codeberg.org/eamanola/ff9-scripts-linux/src/branch/master/ff9-1000x-ropes-linux.sh

Anyone played with MediaSource?

Whats the strategy for long videos (over SourceBuffer QuotaExceededError).

When giving a stream url directly to <video> src the whole buffered is seekable, say all 20min.

But going through MediaSource the seekable area is reduced to SourceBuffer size (eg. 10 min around video.currentTime)

How is the browser doing it? afaik there is no prepending to SourceBuffer, nor multiple SourceBuffers per video stream.

The documentation on mdn doesnt touch this. any help or resources to look into would be much appriciated.

thanks in advance

trying to encode av1 video.

current command: `ffmpeg -y -i input -map 0:0 -c:v av1_nvenc -pix_fmt yuv420p -preset slow -f webm output`

it does the basics, and voila playable av1. But when seeking the video, it pauses for up to 5sec, before resuming playback.

any flags or options to address this?

thanks in advance

// edit: solved

my node libraries are commonjs, so jsr seems ruled out.

are there any others out there?

plus, if they use package.json, and not some custom file(s)

extra plus, if they work seemlessly with at least (p)npm i, after npm config set registry

thanks in advance

is there any advantages of having one db vs many files?

for consideration, the data sets are completely separate, no cross references at all.

thanks & sorry in advance, if redundant question.

Hey all

this might be more of a design question.

Im making yet another media server for home use.

The files are in various formats/codecs, and no preprocessing is done.

basically:

1. the client (<video/audio> in browser) asks for a file,

2. gets it as a file download

3. plays it, or fails to decode, in which case

3.1) asks for a transcoded version to a supported codec

3.2) the transcode (ffmpeg process) pipes chucks to client on demand, and halts when client have enough

this all works well.

Sometimes during transcode for one reason or another the client closes connection. 99% user has left the player view, and <video> is unloaded, in which case transcode is not needed anymore.

When connection closes the transcode process is killed.

With that background

Sometimes the halts between chucks can get too long. client downloads half, or more of the media, and while playing it, timesout/or other reason closes the connection, before requesting for the rest.

killing the process becomes problematic, since when the half already downloaded finished playing, transcode would have to start from 0:00, causing up to minutes of pause.

reattaching new connection to stdout/pipe doesnt seem to work (might be doing it wrong).

any ideas how to approach this. trying to

- to have no pre processing (save time)

- only transcode when necessary (save cpu/gpu)

- only transcode chunks on demand (save cpu/gpu)

- and resume transmission, if connection failed mid way

thanks in advance

Otsikko. Onko hyviä konsteja / aineita, millä pääsisi eroon rikkakasveista, jotka kasvaa kivityksen välissä?

tattista etukäteen

What is docker updating on the deb (others) packages?

they seem to have several updates per week. is it bug fixes, and development, or some sort of key/other sec variable update?

thanks in advance

curious user