Recherche avancée

Médias (1)

Mot : - Tags -/punk

Autres articles (95)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (8289)

  • Scalable Video Stream Processing and Redirection in the Cloud - More Efficient Alternatives to RTMP ?

    18 juillet 2023, par dumbQuestions

    I'm currently working on a project that involves processing and redirecting video streams from multiple users in real time.

    


    Here's how my current implementation works :

    


      

    • Users send their video streams to an RTMP server.

      


    • 


    • I use OpenCV to connect to the source RTMP server and capture the video stream.
The video frames are processed using OpenCV.

      


    • 


    • I then use FFmpeg to forward the processed video stream to another RTMP server.

      


    • 


    


    I want to deploy it with cloud providers, but I'm worried that RTMP servers might not be the best choice for scalability, especially with increasing users. I'm seeking recommendations for efficiently implementing such video stream processing and redirection with good scalability. Is my current implementation somewhat viable, is there a better solution ?

    


    Ideally, I'm looking for solutions that can handle a large number of concurrent video streams and provide low latency

    


    Is there a cloud-based alternative to the RTMP-based approach that can meet these requirements and offer better scalability and efficiency ? Any insights, experiences, or recommendations are greatly appreciated. Thank you !

    


  • problem in making HLS using ffmpeg problem

    24 juin 2023, par AMZ

    I have a function do run in background and create m3u8 for some videos : (I is running in background and updating some fields in django).

    


    def convert_to_hls(episode):
    # Set the output directory for HLS files
output_dir = os.path.join(settings.MEDIA_ROOT, 'hls')
os.makedirs(output_dir, exist_ok=True)

# Set the input video file path
input_file_path = episode.videoFile.path

# Set the output filename and path for the HLS playlist
# filename = os.path.splitext(os.path.basename(input_file_path))[0]
characters = string.ascii_letters + string.digits
filename = ''.join(random.choice(characters) for _ in range(45))
playlist_path = os.path.join(output_dir, f'{filename}.m3u8')

# Set the output path for the HLS segments
segments_path = os.path.join(output_dir, f'{filename}_%05d.ts')

# Construct the ffmpeg command for HLS conversion
command = [
    'ffmpeg',
    '-i', input_file_path,
    '-c:v', 'libx264',
    '-crf', '23',
    '-preset', 'medium',
    '-c:a', 'aac',
    '-b:a', '128k',
    '-f', 'hls',
    '-hls_time', '10',
    '-hls_list_size', '0',
    '-hls_segment_filename', segments_path,
    playlist_path
]
# Execute the ffmpeg command
subprocess.run(command, check=True)

episode.hls_created = True
episode.hls_url = playlist_path.replace("/home/debian/project","")
episode.save()

return True


    


    this code works well for most of my videos but for some .mp4 files gets :

    


    [Fri Jun 23 17:05:47.511095 2023] [wsgi:error] [pid 19975:tid 140289048565504] Exception in thread Thread-1:
[Fri Jun 23 17:05:47.511198 2023] [wsgi:error] [pid 19975:tid 140289048565504] Traceback (most recent call last):
[Fri Jun 23 17:05:47.511244 2023] [wsgi:error] [pid 19975:tid 140289048565504]   File "/opt/bitnami/python/lib/python3.8/threading.py", line 932, in _bootstrap_inner
[Fri Jun 23 17:05:47.512078 2023] [wsgi:error] [pid 19975:tid 140289048565504]     self.run()
[Fri Jun 23 17:05:47.512124 2023] [wsgi:error] [pid 19975:tid 140289048565504]   File "/opt/bitnami/python/lib/python3.8/threading.py", line 870, in run
[Fri Jun 23 17:05:47.512707 2023] [wsgi:error] [pid 19975:tid 140289048565504]     self._target(*self._args, **self._kwargs)
[Fri Jun 23 17:05:47.512748 2023] [wsgi:error] [pid 19975:tid 140289048565504]   File "/home/debian/project/twapp/views/episode_backgrounds.py", line 41, in convert_to_hls
[Fri Jun 23 17:05:47.512950 2023] [wsgi:error] [pid 19975:tid 140289048565504]     subprocess.run(command, check=True)
[Fri Jun 23 17:05:47.512989 2023] [wsgi:error] [pid 19975:tid 140289048565504]   File "/opt/bitnami/python/lib/python3.8/subprocess.py", line 516, in run
[Fri Jun 23 17:05:47.513500 2023] [wsgi:error] [pid 19975:tid 140289048565504]     raise CalledProcessError(retcode, process.args,
[Fri Jun 23 17:05:47.513657 2023] [wsgi:error] [pid 19975:tid 140289048565504] subprocess.CalledProcessError: Command '['ffmpeg', '-i', '/home/debian/project/media/videos/introduction_to_raster_qBhrnAx.mp4', '-c:v', 'libx264', '-crf', '23', '-preset', 'medium', '-c:a', 'aac', '-b:a', '128k', '-f', 'hls', '-hls_time', '10', '-hls_list_size', '0', '-hls_segment_filename', '/home/debian/project/media/hls/ZN3fsJVEfTDEc8MFb5DrP7Y34JFNLj0hfWnGRZAwFdjuG_%05d.ts', '/home/debian/project/media/hls/ZN3fsJVEfTDEc8MFb5DrP7Y34JFNLj0hfWnGRZAwFdjuG.m3u8']' returned non-zero exit status 1.


    


    Also it does not work for .MOV files.

    


  • Bitrate with mp3 - Can I put whatever I want ? [closed]

    5 juillet 2023, par AtyKlaxas

    I'm actually on a project to re-encode a large amount of audio files

    


    all over the internet I see people encoding in 320k, 196k, 128k

    


    If there is a rule for encoding values, what is it ?
Is there a reference table of encoding levels for mp3s ?
or i pur whatever i want ? (example 120k or 280k)

    


    I've tried asking ChatGPT
I expect to get these answers

    


    There's a reference table, you can't encode anything other than this : 320k, 256k, 196k, 128k (ect ...)

    


    There is no reference table, but the rules that are not written down and accepted by everyone are : (explanation)
and this gives us a list of bitrates 320k, 256k, (...)

    


    There are no rules at all, you can encode in any bitrate you like.
benchmarks such as 320k or 256k are only indicative and reflect nothing other than an arbitrary choice