Recherche avancée

Médias (0)

Mot : - Tags -/configuration

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (104)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (14503)

  • Still getting FFMPEG "Segmentation fault" with network stream source with the AmazonLinux 2023 distro [closed]

    28 décembre 2023, par Matthew Drooker

    After referencing https://docs.yucca.app/en/troubleshooting/Segmentation_fault_core_dumped

    


    And using

    


    FFMPEG "Segmentation fault" with network stream source

    


    I thought I had this solved.
But still having the same issue as documented as fixed.

    


    Im using AmazonLinux 2023 distro in a Lambda custom image.

    


    Im trying to use baseImage from FROM --platform=linux/amd64 public.ecr.aws/lambda/nodejs:20

    


    Then doing- RUN dnf install nscd  -y in my Dockerfile allowing the nscd service to be installed per the answer.

    


    But, Im still getting the ffprobe was killed with signal SIGSEGV error with the new AmazonLinux Distro.

    


    Has anyone else faced this with the 2023 Distro ? Or have an answer to this question ?

    


  • 2023-04-18 18:25:05 INFO discord.player ffmpeg process ##### successfully terminated with return code of 0

    19 avril 2023, par I_am_thing

    I am making a discord music bot with discord.py and ctx, it uses Spotify

    


    I am using FFmpeg for my music feature. This is my !play code

    


    client_id = ''
client_secret = ''
client_credentials_manager = SpotifyClientCredentials(client_id=client_id, client_secret=client_secret)
sp = spotipy.Spotify(client_credentials_manager=client_credentials_manager)

bot.volume = 0.5 # initial volume of the bot (can be changed)

@bot.command()
async def play(ctx, *, track_query):
    # check if the query is a valid Spotify link
    if 'open.spotify.com/track/' in track_query:
        track_id = track_query.split('/')[-1] # extract the track ID from the link
    else:
        # search for tracks with the given name
        track_results = sp.search(q=track_query, type='track', limit=1)
        if len(track_results['tracks']['items']) == 0:
            await ctx.send(f'Sorry, I could not find any track with the name "{track_query}".')
            return
        track_id = track_results['tracks']['items'][0]['id'] # get the track ID for the first search result
    track_info = sp.track(track_id) # get the track information for the given ID
    track_name = track_info['name']
    track_artist = track_info['artists'][0]['name']
    track_duration = time.strftime('%M:%S', time.gmtime(track_info['duration_ms']//1000))
    track_preview_url = track_info['preview_url'] # get the preview URL for the track
    if track_preview_url is None:
        await ctx.send(f'Sorry, the track "{track_name}" by {track_artist} cannot be played.')
        return
    voice_channel = ctx.author.voice.channel
    if voice_channel is None:
        await ctx.send('Please join a voice channel first.')
        return
    voice_client = await voice_channel.connect()
    audio_source = discord.FFmpegPCMAudio(track_preview_url, options="-b:a 128k -bufsize 512k")
    voice_client.play(audio_source, after=lambda e: print('Player error: %s' % e) if e else None)
    voice_client.source = discord.PCMVolumeTransformer(voice_client.source)
    voice_client.source.volume = bot.volume

    # format the embed message
    embed = discord.Embed(title=track_name, description=track_artist, color=0xff8c00)
    embed.add_field(name='Duration', value=track_duration, inline=True)
    embed.set_thumbnail(url=track_info['album']['images'][0]['url'])
    embed.set_footer(text='This music is from https://www.spotify.com/')
    await ctx.send(embed=embed)

    while voice_client.is_playing():
        await asyncio.sleep(1)
    await voice_client.disconnect()


    


    I joined the unofficial ffmpeg discord server no one could find a fix I searched for ages and I couldn't fix it

    


  • FFmpeg : H.265/HEVC - does not work on Sony Smart-TV if you change encoder

    25 juillet 2019, par oigen90

    We have such Sony Bravia Smart-TV devices :

    • Sony KD-49XD7005 (2016) - Android
    • Sony KD-49XE7096 (2017) - Linux

    Those devices does have HEVC support, as well as 4K support.

    Also, we have a one minute Apple ProRes 4K video file. I need to transcode it into HEVC with some simple params, create DASH manifest and stream it into HTML5-player.
    The problem is that if I use the regular ’libx265’ codec passing it after "-c:v" - the video does not play on Sony Bravia (just freezes on ’loadstart’ player’s event). But if I use ’hevc_nvenc’ - it works ! What’s the reason of such behavior ? Both of codecs should work identically, hevc_nvenc just should be faster and was made to work on nvidia graphic cards (that’s all I know about those codecs’ difference so far). But in fact we have working stream encoded into hevc_nvenc and invalid stream encoded into libx265.

    See my FFmpeg command below.

    Which thoughts do you have ? If you want me to provide some more info - feel free to ask.

    ffmpeg -i input.mov -c:v hevc_nvenc -pix_fmt yuv420p -b:v 12000k -maxrate 14000k -bufsize 6000k -c:a copy -f mp4 output.mp4