| Post Reply | RetroFed Forums Forum Index » techsupport |
| Author | Message | ||
|---|---|---|---|
printf("%s", name);
piefed.blahaj.zone
akunohana@piefed.blahaj.zoneJoined: 2026-03-30 |
Edit: I encode to/with(?) the codec h246. This question is about containers/filename extensions. I am digitizing old video mediums, such as VHS, VHS-C and Mini DV. A few colleagues have asked me to do it for them, which is awesome and feels great. Now, for personal use, I |
||
| 9 Original | |||
|
nicgentile
lemmy.world
nicgentile@lemmy.world Joined: 2024-03-22 |
Maybe burn storage space, have a raw version that you use as the main source, and you can encode at your will to whatever as purpose requires. |
||
| 4 | |||
printf("%s", name);
piefed.blahaj.zone
akunohana@piefed.blahaj.zoneJoined: 2026-03-30 |
Maybe burn storage space, have a raw version that you use as the main source, and you can encode at your will to whatever as purpose requires.
Thanks! I always keep the raws, unless they explicitly ask me to delete them. My question is rather about which re-encoded/target container would be easiest to use for my colleagues and potential customers from a compatibility perspective. |
||
| 4 | |||
|
remon
ani.social
remon@ani.social Joined: 2024-09-25 |
Pretty sure every remotely modern device can open a .mkv container. It's much more important which video codec you used for the video inside the container, that's what will cause the compatibility issues. You want to use h264 for maximum compatibility (but at the expense of taking up more storage). |
||
| 8 | |||
|
nicgentile
lemmy.world
nicgentile@lemmy.world Joined: 2024-03-22 |
Thanks! I always keep the raws, unless they explicitly ask me to delete them. My question is rather about which re-encoded/target container would be easiest to use for my colleagues and potential customers from a compatibility perspective.
H264 MKV or MP4. |
||
| 4 | |||
|
one_old_coder
piefed.social
one_old_coder@piefed.social Joined: 2026-02-08 |
I'm not an expert but MKV should be ubiquitous enough to please most people. You can tell reluctant people to install VLC and it should work with any codec. I download most movies who are encoded in MP5/x265/whatever265 because it saves space, but MP4 could be better for people who only have iPhones or old TVs. |
||
| 5 | |||
|
hendrik
palaver.p3x.de
hendrik@palaver.p3x.de Joined: 2021-08-21 |
Pretty sure every remotely modern device can open a .mkv container. It's much more important which video codec you used for the video inside the container, that's what will cause the compatibility issues. You want to use h264 for maximum compatibility (but at the expense of taking up more storage).
Edit: I didn't read properly... You're doing this for other people. Maybe you should go with the conservative option, then. (I mean if their devices already support it, there's no harm in forgoing compatibility and just go with a more modern encoding format like HEVC or better AV1. It's not like the next laptop or TV will be unable to play it... But H264 is certainly a safe bet. That's supported everywhere.) Also second the point about the container. It doesn't really matter, just go with mkv. In the unlikely case it doesn't work, you can always take the video an put it in a different container. That kind of conversion is fast and without loss. |
||
| 2 | |||
|
sexual_tomato
lemmy.dbzer0.com
sexual_tomato@lemmy.dbzer0.com Joined: 2023-08-17 |
When I digitize stuff I used MKV because it was a format that was resilient to whatever program that created it crashing in the middle of creation. Mkv is segmented and doesn't need anything to be written about the entire file. It's just small sections kind of stitched together. In my opinion this is what you should digitize to initially and then if you need other codecs then transcode later. |
||
| 5 | |||
Bo7a
piefed.ca
Bo7a@piefed.caJoined: 2025-06-10 |
anecdata - I recently sent a usb full of .mkvs to a buddy and they all came up unplayable on his TV. I converted them to mp4 and he was fine. |
||
| 3 | |||
printf("%s", name);
piefed.blahaj.zone
akunohana@piefed.blahaj.zoneJoined: 2026-03-30 |
Pretty sure every remotely modern device can open a .mkv container. It's much more important which video codec you used for the video inside the container, that's what will cause the compatibility issues. You want to use h264 for maximum compatibility (but at the expense of taking up more storage).
Ah, gotcha. Thanks! I was already using h246, so all good there then. :D |
||
| 2 | |||
|
ramble81
lemmy.zip
ramble81@lemmy.zip Joined: 2025-06-08 |
Pretty sure every remotely modern device can open a .mkv container. It's much more important which video codec you used for the video inside the container, that's what will cause the compatibility issues. You want to use h264 for maximum compatibility (but at the expense of taking up more storage).
This is the best answer. MKV is just a container. It’s the codec that will matter the most. As mentioned H264 is going to be the most ubiquitous. Even if you were to try to do MP4 it’s still dependent on the codec. You could do an MKV with MPEG Layer 2, but that’s starting to become too old as well. Also for H264, the RF plays a big part too. Go for something higher like 22-24. It’ll make for a slightly larger file, but you’ll great quality without being a raw file size. Too low and you’ll end up with a potato. As for audio, also stick with a safe codec like MP3. Using WAV is too large, AAC is limited as are some others as well. |
||
| 5 | |||
printf("%s", name);
piefed.blahaj.zone
akunohana@piefed.blahaj.zoneJoined: 2026-03-30 |
Edit: I didn't read properly... You're doing this for other people. Maybe you should go with the conservative option, then. (I mean if their devices already support it, there's no harm in forgoing compatibility and just go with a more modern encoding format like HEVC or better AV1. It's not like the next laptop or TV will be unable to play it... But H264 is certainly a safe bet. That's supporte...
Thanks! For some reason on Linux, I can (in some cases) "simply" rename the file with a different extension name. Would that be sufficient to do on the recipient's device, or would I need to process it more "properly" with ffmpeg (which I am using, by the way)? |
||
| 2 | |||
printf("%s", name);
piefed.blahaj.zone
akunohana@piefed.blahaj.zoneJoined: 2026-03-30 |
H264 MKV or MP4.
Thanks! |
||
| 2 | |||
printf("%s", name);
piefed.blahaj.zone
akunohana@piefed.blahaj.zoneJoined: 2026-03-30 |
I'm not an expert but MKV should be ubiquitous enough to please most people. You can tell reluctant people to install VLC and it should work with any codec. I download most movies who are encoded in MP5/x265/whatever265 because it saves space, but MP4 could be better for people who only have iPhones or old TVs.
Thanks! My very first "customer" is a Samsung guy, so mkv should work in his case. I'll definitely try somebody's iPhone to see what containers and codecs they support. |
||
| 2 | |||
printf("%s", name);
piefed.blahaj.zone
akunohana@piefed.blahaj.zoneJoined: 2026-03-30 |
When I digitize stuff I used MKV because it was a format that was resilient to whatever program that created it crashing in the middle of creation. Mkv is segmented and doesn't need anything to be written about the entire file. It's just small sections kind of stitched together. In my opinion this is what you should digitize to initially and then if you need other codecs then transcode later.
Thanks! I'll definitely stay with mkv then! :) |
||
| 2 | |||
printf("%s", name);
piefed.blahaj.zone
akunohana@piefed.blahaj.zoneJoined: 2026-03-30 |
anecdata - I recently sent a usb full of .mkvs to a buddy and they all came up unplayable on his TV. I converted them to mp4 and he was fine.
That's crazy, because I was in the very same situation a few weeks ago. A friend wanted some stuff and they specifically wanted to be able to simply play it from the USB stick on their TV. I anticipated compatibility issues, so I made sure to grab mp4 copies from the start. It worked. :D |
||
| 3 | |||
|
one_old_coder
piefed.social
one_old_coder@piefed.social Joined: 2026-02-08 |
Thanks! My very first "customer" is a Samsung guy, so mkv should work in his case. I'll definitely try somebody's iPhone to see what containers and codecs they support.
For Apple users, MP4 has been the standard for decades. |
||
| 2 | |||
printf("%s", name);
piefed.blahaj.zone
akunohana@piefed.blahaj.zoneJoined: 2026-03-30 |
This is the best answer. MKV is just a container. It’s the codec that will matter the most. As mentioned H264 is going to be the most ubiquitous. Even if you were to try to do MP4 it’s still dependent on the codec. You could do an MKV with MPEG Layer 2, but that’s starting to become too old as well. Also for H264, the RF plays a big part too. Go for something higher like 22-24. It’ll make for a...
Shoot! Thanks so much for mentioning the audio codecs! I was about to encode as flac because why not LOL. The audio of old family tapes are probably not considered high fidelity audiophile material anyway 🤣 |
||
| 4 | |||
gnufuu
lemmy.ca
gnufuu@lemmy.caJoined: 2026-06-10 |
Careful, you seem to confuse video encodings (e.g. mpeg, h264, h265, av1) with video containers (e.g. mkv, avi, webm). When digitizing old media, the encoding is much more important because changing it afterwards means losing quality whereas changing the container format doesn't. |
||
| 1 | |||
|
hendrik
palaver.p3x.de
hendrik@palaver.p3x.de Joined: 2021-08-21 |
Thanks! For some reason on Linux, I can (in some cases) "simply" rename the file with a different extension name. Would that be sufficient to do on the recipient's device, or would I need to process it more "properly" with ffmpeg (which I am using, by the way)?
You definitely want to do it properly with something like ffmpeg. Just renaming it leaves you with a misnamed mkv file. (Or whatever is inside.) Linux is clever enough to figure that out, because in the good old days, file extensions weren't all that important. But yeah, some other device might not. And even some Linux software might not get that. Also you won't really change anything, a name is just a name. |
||
| 2 | |||
|
Onomatopoeia
lemmy.cafe
Onomatopoeia@lemmy.cafe Joined: 2025-01-02 |
Thanks! My very first "customer" is a Samsung guy, so mkv should work in his case. I'll definitely try somebody's iPhone to see what containers and codecs they support.
As a Samsung TV owner, it can play MKV. But it does better (more consistent) with MP4. To MKV is a more future-proof solution. MP4 is more compatible, today. Tough call. Though since it's for other people, I'd probably give them MP4, and highest quality those videos can benefit from. |
||
| 2 | |||
|
Onomatopoeia
lemmy.cafe
Onomatopoeia@lemmy.cafe Joined: 2025-01-02 |
Pretty sure every remotely modern device can open a .mkv container. It's much more important which video codec you used for the video inside the container, that's what will cause the compatibility issues. You want to use h264 for maximum compatibility (but at the expense of taking up more storage).
I've run into issues with MKV - like my Samsung TV can technically play them, but it does much better with MP4 (I still use MKV for future-proofing, and just deal with the tv being fickle). Most people aren't like me, and won't tolerate that inconvenience. |
||
| 1 | |||
|
Labna
lemmy.world
Labna@lemmy.world Joined: 2024-03-20 |
The question is partially answered by the other comments. I have just few details to had : As it's the compatibility that matter you have a question of target player to answer :
Now you can choose ! |
||
| 2 | |||
|
grue
lemmy.world
grue@lemmy.world Joined: 2023-06-13 |
This is the best answer. MKV is just a container. It’s the codec that will matter the most. As mentioned H264 is going to be the most ubiquitous. Even if you were to try to do MP4 it’s still dependent on the codec. You could do an MKV with MPEG Layer 2, but that’s starting to become too old as well. Also for H264, the RF plays a big part too. Go for something higher like 22-24. It’ll make for a...
Personally, I would value fidelity over ubiquity. After all, the recipient can transcode it themselves if they need to, but they're not necessarily going to be able to re-digitize it with higher quality in the future. As such, I'd use the most modern video codec I could find (and use generous quality settings with it) and use FLAC for audio. |
||
| 1 | |||
| Post Reply |
Back to top |