
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (40)
-
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...) -
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 (...) -
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users.
Sur d’autres sites (6043)
-
ffmpeg ignoring framerate settings when trancsoding mp4 to mxf
5 avril 2024, par Matt BI'm using ffmpeg to transcode an mp4 file to an mxf file for proxies.


The main problem : ffmpeg ignores my framerate settings and always encodes the output video at 59.9 fps instead of the requested 58.


In this case, the input video has an FPS of
58
(actually an avg framerate of57442500/996461
as reported by an ffmpeg probe), and I require the output to match, but ffmpeg overrides me and sets it to59.9
.

No matter what I try, I cannot get ffmpeg to write the output file at
58
fps. I've tried the-r
and-framerate
arguments and I've tried thefps=58
option withvf
. I've also tried setting-vsync cfr
, but no luck. I've also tried using the average framerate from the probe (57442500/996461
), but again, no change. I've also tried specifying the framerate in the input to match that reported by the probe (no luck).

Here's my code in
ffmpeg-python
.

in_video = 'video.mp4'
out_video = 'video.mxf'

(
 ffmpeg
 .input(
 in_video,
 )
 .output(
 out_video,
 r=58,
 )
 .global_args('-report')
 .run()
)



And here is the raw command, which I've tried manually entering as well.


ffmpeg -i "video.mp4" -r 58 "video.mxf" -report



Despite my output settings, the resulting video has an output framerate of
60000/10001
instead of58/1
or57442500/996461
.

Is there something obious I'm missing ? Does the mxf format require certain framerates ?


The source video was recorded with my phone, a Google Pixel 6a, if that matters. The
r_frame_rate
reported by the probe is60000/1001
while theavg_frame_rate
is the aforementioned57442500/996461
, which is what my editor reports as well.

Alternatively, I'm open to other proxy format suggestions. Though I'll say that .mxf files seem to be the best trade in file size and editing latency I've seen so far. Unfortunately, DaVinci Resolve, my editor, requires the proxy to have the same framerate as the source.


Edit to add report for Gyan


Source code


from pathlib import Path
import ffmpeg

src = Path(
 r"K:\StackO\vid.mp4"
)
dest = src.with_suffix('.mxf')


(
 ffmpeg
 .input(
 str(src),
 )
 .output(
 str(dest),
 r=58,
 )
 .global_args('-report')
 .run()
)



Report on pastebin. It was too large to post on SO, and even too large for pasetbin, so I omitted the middle 8,000 lines starting at line 884. Hopefully I only removed superfluous stuff.


-
FFMPEG install on server
23 juillet 2013, par s19k15I have an online server (shared hosting plan) in linux, i do not know a lot stuff about linux and i am trying to install ffmpeg.
I have tryied a lot of scripts but no luck.
Now i am trying to install the below script via putty.
<a href="https://github.com/heidisoft/FFMPEG-install-script-for-shared-host" rel="nofollow">https://github.com/heidisoft/FFMPEG-install-script-for-shared-host</a>
When the install was running i get this message and the installation stops...
Installation of MPlayer-1.0rc1.tar.bz2 ....... started
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1233 100 1233 0 0 7713 0 --:--:-- --:--:-- --:--:-- 7803
bzip2: (stdin) is not a bzip2 file.
tar: Child returned status 2
tar: Error is not recoverable: exiting now
mplayer.sh: line 32: cd: MPlayer-1.0rc1/: No such file or directory
mplayer.sh: line 33: ./configure: No such file or directory
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target `install'. Stop.
cp: cannot stat `etc/codecs.conf': No such file or directory
Installation of MPlayer-1.0rc1.tar.bz2 ....... Completed
Mplayer installation Failed :( , please visit the forumWhat can i do to install ??? Thanks !
-
Way to bypass video upload when testing using Rspec
1er mars 2014, par JustinI'm testing a page on my app that shows videos. I'm trying to speed up the test by bypassing the video upload process or another way ??
Maybe I'm using FactoryGirl incorrectly for file uploads..
Using FactoryGirl, I'm creating the video with
FactoryGirl.define do
factory :video do
user_id 1
type "Live"
title "FooBar"
description "Foo bar is the description"
video { fixture_file_upload(Rails.root.join('spec', 'files', 'concert.mov'), 'video/mp4') }
end
endAnd in the request's spec I'm describing the videos as :
describe "videos page" do
let(:user) { FactoryGirl.create(:user) }
let!(:video1) { FactoryGirl.create(:video) }
before { visit user_video_path(user) }
it { should have_title(user.name) }
it { should have_content(user.name) }
describe "videos" do
it { should have_content(video1.description) }
end
endNow, everytime I run the test for this page it goes through the file upload process which takes more time. I'm also using FFmpeg
**video.rb (video model)**
validates :video, presence: true
has_attached_file :video, :styles => {
:medium => { :geometry => "640x480", :format => 'mp4' },
:thumb => { :geometry => "470x290#", :format => 'jpg', :time => 10 }
},
:processors => [:ffmpeg]What this does when I test the page is the CLI goes through the video upload process like it would if you were uploading the video and watching your local server.