
Recherche avancée
Médias (91)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
-
avec chosen
13 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
sans chosen
13 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
config chosen
13 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
Autres articles (29)
-
Demande de création d’un canal
12 mars 2010, parEn fonction de la configuration de la plateforme, l’utilisateur peu avoir à sa disposition deux méthodes différentes de demande de création de canal. La première est au moment de son inscription, la seconde, après son inscription en remplissant un formulaire de demande.
Les deux manières demandent les mêmes choses fonctionnent à peu près de la même manière, le futur utilisateur doit remplir une série de champ de formulaire permettant tout d’abord aux administrateurs d’avoir des informations quant à (...) -
Gestion de la ferme
2 mars 2010, parLa ferme est gérée dans son ensemble par des "super admins".
Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
Dans un premier temps il utilise le plugin "Gestion de mutualisation" -
MediaSPIP Core : La Configuration
9 novembre 2010, parMediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...)
Sur d’autres sites (4594)
-
Modifying incorrect h.264 dimension in existing video file
11 juin 2015, par RichyJAfter searching a lot, I’m more confused than ever !! To summarise :
I recorded a video using my HTC One M8, using 1920x1088 resolution, and it came out fine. The next day, for some reason, in the settings I changed to 1920x1080 and the next video was weird - green bar across the top, diagonal green lines throughout and odd colour stripes. The underlying image was fine, although there seem to be some ’frame jumps’ at times. Unfortunately, this second video contained a section I would like to keep, so I’m trying to fix it...
I’ve learned a bit about AVC/H.264, but it’s pretty confusing. Essentially, I wonder whether I can just change the ’1080’ in the file info to ’1088’ and salvage the footage - there’s no audio to worry about. I read that since 1080 is not directly divisible by 16, most encoders actually do 1088 then the player discards the remaining 8 lines at playback time. I wonder whether this is the root of the problem ? I tried to get into NALs, SPS/PPS etc, but couldn’t really fathom whether this was even relevant to my problem. A hex search didn’t even find anything that looked like the NALs given as examples elsewhere :
What does this NAL header data mean ?
Fetching dimensions of a video
I’ve loaded both files into a Hex editor and compared as best I can (around the moov and avcC parts), but haven’t fixed it yet. One of the single byte changes I made and saved to a new ’test’ file brought up additional info in the mediainfo program, showing that the original recording was at 1088 - this hadn’t been there before, but it still played wrongly. I found info regarding the encoding of height and width (units-1 * 16) but couldn’t work out how to use this info in practice.
I tried ffmpeg and dumping to raw video, but couldn’t make this play at all as a yuv file.
So, my question is, will I be able to change just one byte (or a few) in the file, to make it read as 1088 to the player, or am I looking in totally the wrong direction ?!? Is this even possible ? As I say, the actual images look intact throughout, just the colours are wrong and the lines are there, so I believe it’s something to do with YCrCb problems, but at this point, I’m lost...
I know this isn’t specifically about programming, but the above links were all from this site, so thought it might be OK to ask here. Any help would be much appreciated !!
I’ve recreated the conditions and done 2 short clips at 1080 and 1088 for you to see the problem but as I’m new, I can’t post them here yet. They’re on my Photobucket page if you are willing to look at them (hope this isn’t breaking the rules !!). The blueish line at the bottom is the windowsill...
-
discord.py music bot can't play next song
6 décembre 2020, par borkI'm making a discord music bot using ffmpeg and youtube-dl. I have a premade playlist of urls that would play the list of songs once a user chooses it.

this is my code for playing the audio

ydl_opts = {
 'format': 'bestaudio', 
 'noplaylist':'True',
 'youtube_include_dash_manifest': False
 }
FFMPEG_OPTIONS = {
 'before_options': '-reconnect 1 -reconnect_streamed 1 -reconnect_delay_max 5',
 'options': '-vn'
 }

songs = url[playlist]
dur_min = 0
pre_dur_sec = 0
with YoutubeDL(ydl_opts) as ydl:
 for i in songs:
 info = ydl.extract_info(i, download = False)
 dur = info['duration']
 playlist_songs.append(info)

playlist_songs_copy = playlist_songs.copy()
for i in playlist_songs_copy:
 info = playlist_songs.pop(0)
 URL = info['formats'][0]['url']
 player = FFmpegPCMAudio(URL, **FFMPEG_OPTIONS)
 q.append(player)
 q_playlist.append(playlist)

if not voice.is_playing():
 source = q.pop(0) 
 playlist = q_playlist.pop(0)
 dur_min = duration_min.pop(0)
 dur_sec = duration_sec.pop(0) 
 voice.play(source, after = lambda e: play_next(ctx, source)) 
 voice.is_playing()
 await ctx.send(f'```nim\n*Now Playing:*\nplaylist {playlist}: {name[playlist]}\n\n{content[playlist]}\n\ntotal duration: {dur_min}:{dur_sec}```')



and this is my code for playing the next song


def play_next(ctx, source):
 voice = get(client.voice_clients, guild = ctx.guild)
 if len(q) >= 1:
 try:
 del combine_q[0]
 source = q.pop(0)
 playlist = q_playlist.pop(0)
 dur_min = duration_min.pop(0)
 dur_sec = duration_sec.pop(0)

 except:
 pass

 voice.play(source, after = lambda e: play_next(ctx, source))
 try:
 asyncio.run_coroutine_threadsafe(ctx.send(f'```nim\n*Now Playing:*\nplaylist {playlist}: {name[playlist]}\n\n{content[playlist]}\n\ntotal duration: {dur_min}:{dur_sec}```'), client.loop)
 
 except:
 asyncio.run_coroutine_threadsafe(ctx.send('```nim\nPlaying the next song...```'), client.loop)
 
 else:
 time.sleep(30) 
 if not voice.is_playing():
 asyncio.run_coroutine_threadsafe(voice.disconnect(), client.loop)
 asyncio.run_coroutine_threadsafe(ctx.send("```nim\nNo more songs in queue.```"),client.loop)
 voice.is_paused()



Up till today, it's been working fine. But I was using the bot just now and instead of playing the song and sending the message "Playing the next song..." as usual, it just stopped and spammed the message for about 30 times before it disconnected. When I checked the logs, it showed

socket.send() raised exception

, which was also spammed in the terminal. When I tried making the bot reconnect, it joined my voice channel but didn't respond to any commands and would keep making the discord "connecting" noise. It wouldn't even leave with my .leave command unless I completely turned it off via the script.

The same connecting problem would continue even after I reran the script and would only stop after I restarted my VS Code which is really odd...


After some testing I found out that as of now, the bot is only able to play two songs before breaking. I really need help as this just happened randomly and I'm unable to find anything online about the problem.


-
Anomalie #2003 (Nouveau) : calculer_select, jointures complexes
25 février 2011, par Jean-Jacques PuigBonjour, J’ai observé un dysfonctionnement dans les recherches sur des données traitées par le plugin forms_and_tables_2_0 ; cependant, je rapporte ce problème ici car il ne me semble pas évident que la correction doive se faire du côté de ce plugin. Le problème vient d’une combinaison du critère (...)