
Recherche avancée
Autres articles (48)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
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. -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs
Sur d’autres sites (6019)
-
Video call between eyebeam and baresip SIP clients
7 décembre 2012, par user1490337I am trying to achieve video call on 2 SIP clients
- Baresip
- Eyebeam
Till now I have succeeded in getting audio stream both ways but the video stream is one way i.e iam getting the stream at the baresip terminal but I cannot see video at the EYEBEAM terminal. I can't understand where I am going wrong.
The eyebeam is sending STAP-a and Fu-a packets to eyebeam as I checked it through wireshark. But baresip is not sending any STAP-a and Fu-a packets to eyebeam hence no video.. Both the clients support H.264.
Pointers in the right direction are welcome.
-
How to queue ffmpeg FIFO
29 avril 2013, par Francoiswe build a service similar to youtube. Also converting runs fine with ffmpeg using this script from another post here :
#!/bin/bash
pipe=/tmp/ffmpeg
trap "rm -f $pipe" EXIT
# creating the FIFO
[[ -p $pipe ]] || mkfifo $pipe
while true; do
# can't just use "while read line" if we
# want this script to continue running.
read line < $pipe
# now implementing a bit of security,
# feel free to improve it.
# we ensure that the command is a ffmpeg one.
[[ $line =~ ^ffmpeg ]] && bash <<< "$line"
doneThis works pretty good when i send one by one to the named pipe. When i send more than one at same time the second one queues the terminal to the point the first one finished. if a try more than 2 the third one will not be transcoded.
So i tried to workaround with background sending to get the terminal free (just drop the echo command and close the ssh connection) but this doesn't work, then i played around with screen -X but also no luck. Maybe someone has a good idea to deal this.
What i wanna do is : Every uploaded video which is needed to transcode will send a echo to the named pipe. FIFO should match but not blocking the terminal. So i think i need something to really queue ffmpeg input.
kindest regards
Francois -
FFMpeg : CFLAGS=-D__STDC_CONSTANT_MACROS ./configure where ?
24 avril 2013, par olidevI got this problem " 'UINT64_C' was not declared in this scope" while using the ffmpeg library for Eclipse running under Ubuntu.
After a while, I have found this solution : http://code.google.com/p/ffmpegsource/issues/detail?id=11
But I could not know how to this :
This should be fixed in our build system no matter what version of ffmpeg you're using. If you're still getting it, run configure like so :
CFLAGS=-D__STDC_CONSTANT_MACROS ./configure
and your problems should go away. This applies to other C++ programs using ffmpeg as well and not just to ffms2, but I can't guarantee that other programs won't break if you define that macro (they really shouldn't, though).Where can I run the configure ? from Terminal ? I tried with Terminal but it does not work.
Anybody has an idea how to run the configure ?
Thanks in advance and your help is much appreciate !