
Recherche avancée
Médias (1)
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (82)
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
MediaSPIP Player : problèmes potentiels
22 février 2011, parLe lecteur ne fonctionne pas sur Internet Explorer
Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...) -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
Sur d’autres sites (5882)
-
x264/x265 options for fast decoding while preserving quality
18 août 2024, par user3301993I want to encode some videos in H264 and H265, and I would like to ask for help in order to chose the adequate options in x264/x265.


- 

- My first priority is video quality. Lossless would be the best quality for example
- My second priority is fast decoding speed (ie : I would like faster decoding without sacrificing quality)

- 

- fast decoding for me means that the decoding machine would use less CPU resources reading the resulting video
- Less RAM consumption would be a plus
- Latency is not important








- I don't care that much if the output file ends up bigger. Also, encoding speed is not important








I'm aware of the option
-tune fastdecode
in both x264 and x265. But apparently the quality gets a bit worse using it.

For x264 :


-tune fastdecode
is equivalent to--no-cabac --no-deblock --no-weightb --weightp 0
(My source isx264 --fullhelp
)

Which options preserve quality ?


For x265 :


-tune fastdecode
is equivalent to--no-deblock --no-sao --no-weightp --no-weightb --no-b-intra
(according to x265 doc)

Again, which options preserve quality ?


I tried to read some documentation on these options, but I'm afraid I'm too stupid to understand if they preserve quality or not.


To explain further what I mean by "preserving quality" :




I don't understand what the cabac option does exactly. But let's say for example that it adds some extra lossless compression, resulting in a smaller video file, but the decoding machine would need to do extra work to decompress the file


In that case, the
--no-cabac
option would skip that extra compression, resulting in no loss of quality, with a bigger file size, and the decoding machine would not need to decompress the extra compression, saving CPU work on the decoding side

In this scenario, I would like to add the
--no-cabac
option, as it speeds up decoding, while preserving quality.



I hope I could get my point across


Can anyone help me pick the right options ?


Thanks in advance


-
x264/x265 options for fast decoding while preserving quality
18 août 2024, par user3301993I want to encode some videos in H264 and H265, and I would like to ask for help in order to chose the adequate options in x264/x265.


- 

- My first priority is video quality. Lossless would be the best quality for example
- My second priority is fast decoding speed (ie : I would like faster decoding without sacrificing quality)

- 

- fast decoding for me means that the decoding machine would use less CPU resources reading the resulting video
- Less RAM consumption would be a plus
- Latency is not important








- I don't care that much if the output file ends up bigger. Also, encoding speed is not important








I'm aware of the option
-tune fastdecode
in both x264 and x265. But apparently the quality gets a bit worse using it.

For x264 :


-tune fastdecode
is equivalent to--no-cabac --no-deblock --no-weightb --weightp 0
(My source isx264 --fullhelp
)

Which options preserve quality ?


For x265 :


-tune fastdecode
is equivalent to--no-deblock --no-sao --no-weightp --no-weightb --no-b-intra
(according to x265 doc)

Again, which options preserve quality ?


I tried to read some documentation on these options, but I'm afraid I'm too stupid to understand if they preserve quality or not.


To explain further what I mean by "preserving quality" :




I don't understand what the cabac option does exactly. But let's say for example that it adds some extra lossless compression, resulting in a smaller video file, but the decoding machine would need to do extra work to decompress the file


In that case, the
--no-cabac
option would skip that extra compression, resulting in no loss of quality, with a bigger file size, and the decoding machine would not need to decompress the extra compression, saving CPU work on the decoding side

In this scenario, I would like to add the
--no-cabac
option, as it speeds up decoding, while preserving quality.



I hope I could get my point across


Can anyone help me pick the right options ?


Thanks in advance


-
lavc : remove mp3_header_(de)compress bitstream filters
24 novembre 2013, par Anton Khirnovlavc : remove mp3_header_(de)compress bitstream filters
They mangle the mp3 header in a non-standard way to save a few bytes.
People who care about space so much should just use a more efficient
codec.