Why would a video of any resolution made with kdenlive and linked on a web page not fill the Firefox web navigator window on a 4k monitor?
the code is as simple as it gets:
<a href="videoname.webm">videoname.webm</a>
ffprobe.exe key01.mp4
ffprobe movie.mp4
Why would a video of any resolution made with kdenlive and linked on a web page not fill the Firefox web navigator window on a 4k monitor?
the code is as simple as it gets:
<a href="videoname.webm">videoname.webm</a>
Why would a video of any resolution made with kdenlive and linked on a
web page not fill the Firefox web navigator window on a 4k monitor?
the code is as simple as it gets:
<a href="videoname.webm">videoname.webm</a>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
On Sun, 5/17/2026 10:53 PM, bad sector wrote:
Why would a video of any resolution made with kdenlive and linked on a web page not fill the Firefox web navigator window on a 4k monitor?
the code is as simple as it gets:
<a href="videoname.webm">videoname.webm</a>
I'm not much of a video person, and my collection of samples
is pretty small.
*******
Have you used any other tools to check the video and audio
stream details of the project ?
ffmpeg
ffplay
ffprobe
ffprobe.exe key01.mp4
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'key01.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: isommp42
creation_time : 2015-05-04T17:26:26.000000Z
Duration: 02:55:10.32, start: 0.000000, bitrate: 5001 kb/s
Stream #0:0(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 125 kb/s (default)
Metadata:
creation_time : 2015-05-04T17:26:26.000000Z
handler_name : Mainconcept MP4 Sound Media Handler
vendor_id : [0][0][0][0]
Stream #0:1(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720
SAR 1:1 DAR 16:9, 4869 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
Metadata:
creation_time : 2015-05-04T17:26:26.000000Z
handler_name : Mainconcept MP4 Video Media Handler
vendor_id : [0][0][0][0]
encoder : AVC Coding
You can see that video is 1280x720, and playing it on a 4K monitor
requires the player wrapper frame to declare a somewhat larger value
if I wanted it to fill the screen.
I've seen other videos like that, 720x480, and those get scaled
quite a bit, to not fill a 4K monitor, but to be significantly
larger than the encoded format.
I would be careful about assuming every video ever made,
is actually natively 3840x2160 or something. That hardly
ever happens, because the cameras aren't good enough for that.
A RED 8K camera could likely make a nice 4K video. It might not
be as sharp as a tack though, it might betray the 8K origin.
I've tried a few RED samples, ones which were just dreadful
(creators at fault), and this is really the only decent one.
Name: epicw8k-standard-24fps-7to1redcode_16x9.zip 8192x4320 @ 23.976 FPS (153 frames, 6.09 seconds)
Size: 1478855973 bytes (1410 MiB)
SHA256: 81DC8B50B878A43FAC699213368E4A5452C7789AB7BC7EAA4813A6AE2CE6C152
Needs a RED provided program to read the file. FFMPEG cannot
handle it. I converted it to an MP4 with the RED software.
There is no sound track. It's a scene of Hong Kong, collected at night.
There are cars driving on the street. Everything is lit up, animated billboards and such.
D:> ffprobe movie.mp4
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'movie.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.29.100
Duration: 00:00:06.38, start: 0.000000, bitrate: 16095 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc), 3840x2160
SAR 16:15 DAR 256:135, 16091 kb/s, 24 fps, 24 tbr, 12288 tbn, 48 tbc (default)
Metadata:
handler_name : VideoHandler
vendor_id : [0][0][0][0]
That's one of the few 4K video samples I've got :-)
When I used ffplay on it, my screen is HIDPI and is set to 200%,
because it is only 27 inches and not the correct dimension
for a good 4K screen. Most of the video goes off the screen with
ffplay.exe, I have to bring up Task Manager and kill it so I
can use my screen again after the 6 second movie.
I could do this on a Linux setup too, but the monitors are
smaller elsewhere in the room, so it's not the same.
Summary: Dump the metadata on the sample and see what's up.
Paul
On 2026-05-18 04:53, bad sector wrote:
Why would a video of any resolution made with kdenlive and linked on a
web page not fill the Firefox web navigator window on a 4k monitor?
the code is as simple as it gets:
<a href="videoname.webm">videoname.webm</a>
What does "not fill" mean? Do you see black borders up, down, left, and
top? If you see black borders or window borders on all four edges simultaneously, then there is a problem.
If the video fills left and right to the edge, but not up-dn, then there
is no problem.
You did not say the pixel count of the video.
Does this sound like a workable workaround? I did my lowest
res. video and raised it from 854x480 to 3840x21604. The result is acceptable.
On Mon, 18 May 2026 00:47:37 -0400, Paul wrote:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Nowadays we just say
<!DOCTYPE html>
and that indicates HTML 5 or later.
On 5/18/26 3:19 AM, Carlos E.R. wrote:
On 2026-05-18 04:53, bad sector wrote:
Why would a video of any resolution made with kdenlive and linked on a web page not fill the Firefox web navigator window on a 4k monitor?
the code is as simple as it gets:
<a href="videoname.webm">videoname.webm</a>
What does "not fill" mean? Do you see black borders up, down, left, and top? If you see black borders or window borders on all four edges simultaneously, then there is a problem.
If the video fills left and right to the edge, but not up-dn, then there is no problem.
You did not say the pixel count of the video.
It's different sizes from 854x480 up to 1920x1200 and yes, all 4 sides i.e. not just an aspect ratio issue. VLC lets me set up so as to open a file with a window size equal to video resolution, not sure if it has an option to fill window whatever size it opens to but I tought there would be such an option in browsers.
On Sun, 5/17/2026 10:53 PM, bad sector wrote:
Why would a video of any resolution made with kdenlive and linked on a web page not fill the Firefox web navigator window on a 4k monitor?
the code is as simple as it gets:
<a href="videoname.webm">videoname.webm</a>
OK, let's play with it now.
I have my six second movie, 3840x2160 or so. The derivative of the RED short clip.
I can do anything I want with it now.
I can code WWW, I know I can do this, it's like Hello World only several lines longer.
firefox test.htm
Current working directory contents:
432 May 18 00:37 test.htm
12,826,013 Mar 16 2022 movie.mp4
I got the idea for my wrapper, from here.
https://www.w3schools.com/html/html5_video.asp
I used Seamonkey Composer, which made a mess, but I waded in
with a text editor and cleaned it up a bit.
********************** test.htm **********************************
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>test.htm</title>
</head>
<body>
<video width="1440" height="900" controls>
<source src="movie.mp4" type="video/mp4">
<source src="movie.ogg" type="video/ogg">
Your browser does not support the video tag.
</video>
</body>
</html>
********************** END test.htm ******************************
I have a movie that seems to play.
Maybe I'm supposed to wrap that "Your browser" line with something... :-) Like I know how to code a web page o.O .
Even though my wrapper window is smaller than the video, it
handled it without whining.
However, browsers playing videos with resolution over the monitor
resolution are zoomed down to that level, soooooooo...
I do an ff thingie on all MY videos on that link list to make them 4k
ffmpeg -i input.mp4 -vf "scale=3840:2160" -c:v libx264 -crf 18 -c:a copy output_4k.mp4
...and then they will fill the browser window on all except 5k monitors.
I could also make them 5k but there are very few of those monitors and
the overhead is 80% more than 4k.
Does this sound like a workable workaround?
On 2026-05-18 06:47, Paul wrote:
On Sun, 5/17/2026 10:53 PM, bad sector wrote:
Why would a video of any resolution made with kdenlive and linked on a web page not fill the Firefox web navigator window on a 4k monitor?
the code is as simple as it gets:
<a href="videoname.webm">videoname.webm</a>
OK, let's play with it now.
I have my six second movie, 3840x2160 or so. The derivative of the RED short clip.
I can do anything I want with it now.
I can code WWW, I know I can do this, it's like Hello World only several lines longer.
firefox test.htm
Current working directory contents:
432 May 18 00:37 test.htm
12,826,013 Mar 16 2022 movie.mp4
I got the idea for my wrapper, from here.
https://www.w3schools.com/html/html5_video.asp
I used Seamonkey Composer, which made a mess, but I waded in
with a text editor and cleaned it up a bit.
********************** test.htm **********************************
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8"> >> <title>test.htm</title>
</head>
<body>
<video width="1440" height="900" controls>
<source src="movie.mp4" type="video/mp4">
<source src="movie.ogg" type="video/ogg">
Your browser does not support the video tag.
</video>
</body>
</html>
********************** END test.htm ******************************
I have a movie that seems to play.
Maybe I'm supposed to wrap that "Your browser" line with something... :-)
Like I know how to code a web page o.O .
Even though my wrapper window is smaller than the video, it
handled it without whining.
I tried your code on a video here:
index.html
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8"> <title>test.htm</title>
</head>
<body>
<video width="640" height="480" controls>
<source src="video.mkv" type="video/mkv">
Your browser does not support the video tag.
</video>
</body>
</html>
I get a player window, but no video plays in it. Sniff :'-(
Does this sound like a workable workaround?
It sounds like a 1995's bad solution, best solution would be to just
provide it in it's original resolution.
On Tue, 5/19/2026 4:35 AM, Carlos E.R. wrote:
On 2026-05-18 06:47, Paul wrote:
I tried your code on a video here:
index.html
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8"> >> <title>test.htm</title>
</head>
<body>
<video width="640" height="480" controls>
<source src="video.mkv" type="video/mkv">
Your browser does not support the video tag.
</video>
</body>
</html>
I get a player window, but no video plays in it. Sniff :'-(
And what is a browser prepared to play ? I don't know
the answer to that. All I know is I try MP4 first. This is
my movie.mp4 which is h264.
ffprobe movie.mp4--
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'movie.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.29.100
Duration: 00:00:06.38, start: 0.000000, bitrate: 16095 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc), 3840x2160
SAR 16:15 DAR 256:135, 16091 kb/s, 24 fps, 24 tbr, 12288 tbn, 48 tbc (default)
Metadata:
handler_name : VideoHandler
vendor_id : [0][0][0][0]
Maybe the doctype is affecting your result ?
See the message from Lawrence.
I seem to remember we had some test to be run on a browser,
to determine whether it could handle HTML5, and the test
may have included attempting to play some modern formats.
Paul
On 19/05/2026 12:35, J.O. Aho wrote:
Does this sound like a workable workaround?
It sounds like a 1995's bad solution, best solution would be to just provide it in it's original resolution.
Indeed, most browsers these days are much better at scaling than a fixed ffmpeg script.
If anything, have a look at jwplayer: https://jwplayer.github.io/jwplayer/ (not tested).
On Mon, 5/18/2026 10:43 PM, bad sector wrote:I usually keep the window around 80% of monitor size and think that it
On 5/18/26 3:19 AM, Carlos E.R. wrote:
On 2026-05-18 04:53, bad sector wrote:
Why would a video of any resolution made with kdenlive and linked on a web page not fill the Firefox web navigator window on a 4k monitor?
the code is as simple as it gets:
<a href="videoname.webm">videoname.webm</a>
What does "not fill" mean? Do you see black borders up, down, left, and top? If you see black borders or window borders on all four edges simultaneously, then there is a problem.
If the video fills left and right to the edge, but not up-dn, then there is no problem.
You did not say the pixel count of the video.
It's different sizes from 854x480 up to 1920x1200 and yes, all 4 sides i.e. not just an aspect ratio issue. VLC lets me set up so as to open a file with a window size equal to video resolution, not sure if it has an option to fill window whatever size it opens to but I tought there would be such an option in browsers.
You might be able to write code, that gets the current window
dimensions, and then picks arguments for the video wrapper.
Apparently this is called "responsive video embedding".
Paul
On Mon, 5/18/2026 9:10 PM, Lawrence D’Oliveiro wrote:
.
On Mon, 18 May 2026 00:47:37 -0400, Paul wrote:I didn't type that in, the Composer did that and I didn't waste time
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Nowadays we just say
<!DOCTYPE html>
and that indicates HTML 5 or later.
messing with it.
The whole exercise was pretty painful, in that I practically retyped
the thing twice.
On Tue, 19 May 2026 02:44:57 -0400, Paul wrote:
On Mon, 5/18/2026 9:10 PM, Lawrence D’Oliveiro wrote:
.
On Mon, 18 May 2026 00:47:37 -0400, Paul wrote:I didn't type that in, the Composer did that and I didn't waste time
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Nowadays we just say
<!DOCTYPE html>
and that indicates HTML 5 or later.
messing with it.
The whole exercise was pretty painful, in that I practically retyped
the thing twice.
So you wasted time *not* messing with it?
This is why we read the docs <https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/video>.
You know the old saying among handypersons -- “measure twice, cut
once”? Well, how about “read the docs twice, code once”?
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,118 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 16:36:42 |
| Calls: | 14,340 |
| Calls today: | 3 |
| Files: | 186,356 |
| D/L today: |
2,556 files (803M bytes) |
| Messages: | 2,532,455 |