
Recherche avancée
Autres articles (59)
-
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Submit enhancements and plugins
13 avril 2011If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.
Sur d’autres sites (7769)
-
playing http video url using ffmpeg
17 mai 2012, par RanjithI am using libavcodec of ffmpeg to play a http video stream in my application.
I have implemented my own video player for this.This player is working fine.Now, I want to show buffering status of video (what percentage of video is downloaded by ffmpeg). But I could not find any api or event for this.
-
Excluding ARMv5 and ARMv6 devices from Google Play
14 mai 2015, par TarasI build a
ffmpeg
based library for my project and the outputs are really huge. Is it OK to remove the support of old arm processors and leave only arm-v7 and x86 libraries ?I suspect that arm-v7 won’t work on older arm processors.
The application min sdk is 4.0.3 and the question is whether the percentage of devices with old ARM is too small so I can filter them out on Google Play ?
-
Laravel MySQL DB not updating after long process
11 mai 2022, par slanginbitsI'm doing some video encoding using Laravel and FFMpeg using https://github.com/protonemedia/laravel-ffmpeg


During the video conversion, I can perform some db updates to update the percentage complete in hls_percent field :


$ffmpeg_cmd = FFMpeg::fromDisk('local_videos')
 ->open($video->filename)
 ->exportForHLS()
 ->toDisk('local_videos')
 ->setSegmentLength(3) // optional
 ->setKeyFrameInterval($key_interval) // optional
 ->onProgress(function ($percentage, $remaining = 0, $rate = 0) use ($id) {
 ItemVideo::where('id', $id)->update(['hls_percent' => $percentage]); 
 });



This process works fine and the hls_percent value gets updated to 100 and the encoded video files are generated.


After some files are moved, (takes several seconds) a final db update is not done.


ItemVideo::where('id', $id)->update(['hls_complete' => 1]);



The timeout only happens while encoding a large 150MB (10 min duration) mp4 file. Smaller/shorter videos complete the process without any issues.


I have increased the following in php.ini


memory_limit = 512M 
post_max_size = 1024M
upload_max_filesize = 1024M
max_execution_time = 2400
max_input_time = 2400
default_socket_timeout = 2400



I modified the global variables in the MySQL database server to higher timeouts
as instructed here https://sebhastian.com/lost-connection-mysql-server-during-query/


connect_timeout 2400
delayed_insert_timeout 300
have_statement_timeout YES
innodb_flush_log_at_timeout 1
innodb_lock_wait_timeout 50
innodb_rollback_on_timeout OFF
interactive_timeout 28800
lock_wait_timeout 31536000
mysqlx_connect_timeout 30
mysqlx_idle_worker_thread_timeout 60
mysqlx_interactive_timeout 28800
mysqlx_port_open_timeout 0
mysqlx_read_timeout 30
mysqlx_wait_timeout 28800
mysqlx_write_timeout 60
net_read_timeout 2400
net_write_timeout 2400
replica_net_timeout 2400
rpl_stop_replica_timeout 31536000
rpl_stop_slave_timeout 31536000
slave_net_timeout 2400
ssl_session_cache_timeout 2400
wait_timeout 28800



apache2handler :


Max Requests Per Child : 0 - Keep Alive : on - Max Per Connection : 100
Timeouts Connection : 300 - Keep-Alive : 5


I'm not getting an error messages in laravel or /var/log/apache2/error.log


What else am I missing ? How can I keep the MySQL connection alive to make the final update ?