
Recherche avancée
Autres articles (39)
-
Support audio et vidéo HTML5
10 avril 2011MediaSPIP 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 (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP 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 (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (5715)
-
How to add transitions using FFmpeg and HTML5 ?
7 octobre 2020, par parthshuklaa very quick question. I want to create a basic application that allows the user to input two files in a HTML based web-app, and select a transition from dropdown ; which is then downloaded to the local machine. Is there a way to achieve this functionality ?


-
Avisynth total frames does not equal VirtualDub total frames
7 mai 2017, par CorpuscularIt appears that Dissolve and/or Fade change the total number of frames in .avs scripts. When I add up the total number of frames in the avs script and then load the avs script in Vdub the total number of frames is different. My real world example below shows a difference of 822 frames vs 1368 frames for the same script. I have run some basic tests which appear to support this hypothesis. Of course I may be doing something stupid. Any guidance would be greatly appreciated. Please let me know if I can clarify anything. Ffmpeg also borks on the same script which leads me to think this is an Avisynth issue. Or my lack of avs coding skills.
System specs :
Win7,
FFmpeg version : 20170223-dcd3418 win32 shared,
AVISynth version : 2.6Test1.avs = 200 frames long = Expected behaviour
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\VSFilter.dll")
v1=ImageReader("1.png", fps=24, start=1, end=100)
v2=ImageReader("2.png", fps=24, start=1, end=100)
video = v1 + v2
return videoTest2.avs with return Dissolve = 195 frames long = Unexpected behaviour
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\VSFilter.dll")
v1=ImageReader("1.png", fps=24, start=1, end=100)
v2=ImageReader("2.png", fps=24, start=1, end=100)
return Dissolve(v1, v2, 5)Test3.avs with fadeOut(fadeIn = 202 frames long = Unexpected behaviour
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\VSFilter.dll")
v1=ImageReader("1.png", fps=24, start=1, end=100)
v2=ImageReader("2.png", fps=24, start=1, end=100)
fadeOut(fadeIn(v1 + v2, 60), 60)Test4.avs with dissolve and fade = 197 frames long = Unexpected behaviour
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\VSFilter.dll")
v1=ImageReader("1.png", fps=24, start=1, end=100)
v2=ImageReader("2.png", fps=24, start=1, end=100)
v3 = Dissolve(v1, v2, 5)
fadeOut(fadeIn(v3, 60), 60)Test5.avs explicity specifying frame rates on dissolve and fade = 197 frames = Unexpected behaviour
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\VSFilter.dll")
v1=ImageReader("1.png", fps=24, start=1, end=100)
v2=ImageReader("2.png", fps=24, start=1, end=100)
v3 = Dissolve(v1, v2, 5, 24)
fadeOut(fadeIn(v3, 60, $000000, 24), 60, $000000, 24)realExample = 822 frames long = Expected behaviour (this is what I want)
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\VSFilter.dll")
v1=ImageReader("1.png", fps=24).trim(1,106)
v3=ImageReader("3.png", fps=24).trim(1,471)
v9=ImageReader("9.png", fps=24).trim(1,58)
v10=ImageReader("10.png", fps=24).trim(1,35)
v11=ImageReader("11.png", fps=24).trim(1,152)
video = v1 + v3 + v9 + v10 + v11
return videorealExample = 1368 frames long
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\VSFilter.dll")
v1=ImageReader("1.png", fps=24).trim(1,106)
v3=ImageReader("3.png", fps=24).trim(1,471)
v9=ImageReader("9.png", fps=24).trim(1,58)
v10=ImageReader("10.png", fps=24).trim(1,35)
v11=ImageReader("11.png", fps=24).trim(1,152)
d1 = Dissolve(v1, v3, 5)
d3 = Dissolve(v3, v9, 5)
d9 = Dissolve(v9, v10, 5)
d10 = Dissolve(v10, v11, 5)
fadeOut(fadeIn(d1 + d3 + d9 + d10,60),60) -
FFMPEG Compilation on Windows 32 bit Vs 64 bit
15 janvier 2016, par ARKWhen I try to compile ffmpeg using MinGW, targeting 32-bit, I observed below error for several files :
c :\mingw\include\unistd.h:79:1 : error : expected ’,’ or ’ ;’ before
’int’
int __mingw_sleep( unsigned long, unsigned long ) ;
^
In file included from c :\mingw\include\zconf.h:452:0,
from c :\mingw\include\zlib.h:34,
from c :/Work/FFMPEG_2.8.4/src/libavcodec/pngenc.c:35 :
c :\mingw\include\unistd.h:105:1 : error : expected ’,’ or ’ ;’ before
’int’
int nanosleep( const struct timespec *, struct timespec * ) ;
^
c :\mingw\include\unistd.h:125:28 : error : expected ’,’ or ’ ;’
before ’usleep’
int _cdecl __MINGW_NOTHROW usleep( useconds_t
)__MINGW_ATTRIB_DEPRECATED ;
^
c :\mingw\include\unistd.h:138:10 : error : conflicting types for ’_cdecl’
unsigned _cdecl
__MINGW_NOTHROW sleep( unsigned ) ;
^
c :\mingw\include\unistd.h:125:5 : note : previous declaration of ’_cdecl’ was hereint _cdecl _MINGW_NOTHROW usleep( useconds_t
)_MINGW_ATTRIB_DEPRECATED ;
^
c :\mingw\include\unistd.h:138:33 : error : expected ’,’ or ’ ;’ before ’sleep’
unsigned _cdecl _MINGW_NOTHROW sleep( unsigned ) ;
^
c :\mingw\include\unistd.h:153:12 : error : expected ’=’, ’,’, ’ ;’, ’asm’ or ’_att
ribute__’ before
’ftruncate’ int _cdecl ftruncate( int, off_t ) ;
^
make : *** [libavcodec/pngenc.o] Error 1Similar issue was faced by someone and I provided a solution (workaround) in another forum
Recently, I started FFMPEG compilation targeting to 64-bit. FFMPEG code (version 2.8.4) downloaded from the ffmpeg site compiled straight for 64-bit. I was expecting errors, but surprisingly I don’t see above errors. Then I thought FFMPEG could have fixed the issues, but it started showing up above errors again when I compiled it for 32-bit. Initially I thought it may be to do with my compilation environment, but similar issue was faced by some other people as well. So, I can confidently rule out the compilation environment factor.
So the question here is, how come above error is specific to 32-bit. I couldn’t understand a bit, any idea about this behavior ??