B S wrote:
>FFmpeg 5.0.1 "Lorentz"
>FFmpeg 4.4.2 "Rao"
>FFmpeg 4.3.4 "4:3"
>FFmpeg 4.2.6 "Ada"
>FFmpeg 4.1.9 "al-Khwarizmi"
>FFmpeg 3.4.9 "Cantor"
FFmpeg 3.4.10
>FFmpeg 3.2.16 "Hypatia"
FFmpeg 3.2.17
>FFmpeg 2.8.18 "Feynman"
Best regards, Reto
AV Preservation by reto.ch
zone industrielle
Kevin Hise wrote:
>Err...sample file of what?
Of the file generated.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with
peter.lysyan...@gmail.com wrote:
>Did you succeed to see any image from this file? This is a ULS
>scan of the elbow of an arm.
No, not the actual image. I could retrieve only a little shadows
by using what I know about medical imaging.
>What would you recommend instead of FFmpeg?
I am afraid,
peter.lysyan...@gmail.com wrote:
>Yes, this file is exported from SonoTouch ultrasound scanner.
>Is there a chance to open this movie?
Possibly. Yet, in my personal opinion, not with FFmpeg.
(I probably misinterpreted as showing a liver cancer, therefore
my question, but this device seems to be
Paul B Mahol wrote:
>> Below is the link to demo.cin file in my Dropbox:
>>
>> https://www.dropbox.com/s/dta1swkn2ohl91l/demo.cin?dl=0
>
>This file is not Cineon for sure.
I agree.
Is this image any related to medical imaging?
___
ffmpeg-user
Paul B Mahol wrote:
>FFmpeg currently does not have any support for Cineon (.cin
>file extension with magic bytes 0x802a5fd7 at start) at all.
If you force their lecture as DPX, then in my experience you can
use them in FFmpeg.
___
ffmpeg-user mailing
Paul B Mahol wrote:
>> Cineon (.cin) was a predecessor of DPX, introduced by Kodak as
>> a digital postproduction format for cinema movies in the early
>> 1990s, and today it's essentially one of its flavours.
>
>Do you have by any chance Cineon muxed into .mov container?
Back then, Cineon were
peter.lysyan...@gmail.com wrote:
>I was unable to use FFmpeg to convert the * .cin file to
>* .avi.
Cineon (.cin) was a predecessor of DPX, introduced by Kodak as
a digital postproduction format for cinema movies in the early
1990s, and today it's essentially one of its flavours.
Best regards,
Moritz Barsnick wrote:
>If 10.7 is a Mac OS X version (I'm guessing here):
>The binaries linked from the ffmpeg website won't work.
I guess... you guess right, Moritz!
Ilja, it works if you compile the source code yourself, but
I don't know either a build which works.
Best regards, Reto
Ilja wrote:
>I downloaded the most recent build, installed
>yasm assmebler, ran make to build ffmpeg as per instructions
>and stumbled into lots of warnings, though the building process
>completed seemingly well.
If the compilation succeeded, ignore the warning.
Best regards, Reto
Carl Eugen Hoyos wrote:
>(Yes, FFmpeg is not that easily scriptable.)
On my end, I mainly use FFmpeg commands within Perl or Bash
scripts, and I am very happy with. FFmpeg is such an outstanding
tool!
Thanks! Reto
___
ffmpeg-user mailing list
MediaMouth wrote:
>Ok, so here's what I'm working through
>- The ffmpeg version I currently have, through Brew is 4.2.2
>- The stdout I posted suggests I ran 4.2.2
>- The version Carl suggests downloading from
>https://ffmpeg.org/download.html suggests 4.2.2 is the latest
>version
>- But Carl
Am Do., 30. Jan. 2020 um 05:18 Uhr schrieb MediaMouth :
> Is the latest version accessible through 'brew upgrade"?
Yes, for both last release and head. Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
digitensions via ffmpeg-user wrote:
>I was having issues with the ‘ and “ options,
In any case, do not use the typographically correct punctuation,
but do use ' and ".
Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Noeck wrote:
>To be sure, that means a video created with
>
>ffmpeg -i in.avi -c:a flac -c:v ffv1 -level 3 -coder 1 -context
>1 -g 1 -slices 4 -slicecrc 1 out.mkv
>
>(or other settings between -coder and the output file) is
>automatically CELLAR (v0-3) compliant (the FFV1.3 video, the
>FLAC audio
Noeck wrote:
>In other words, if I encode a video with current ffmpeg, will
>the result be compliant to the IETF spec? If not, when will
>that happen?
There are actually two documents. The first one is documenting
the current FFmpeg reference implementation of version, 3 and
considers as well
wyattwong--- via ffmpeg-user wrote:
>How can I perform a static build of FFmpeg in macOS so that
>there is only one executable file ?
Not sure I understand you carefully.
There are static builds for many platforms, including macOS:
https://ffmpeg.org/download.html
and the wiki explains how
Rik Roukens wrote:
>Goal: Capture video from the DeckLink Duo 2 and write it to
>output.avi
Have you considered using vrecord?
https://github.com/amiaopensource/vrecord
Hope this helps! Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Ted Park wrote:
>Also, raw files from camera sensors in general aren’t just
>decoded, they’re rendered to a colorspace. Wouldn’t you want to
>review the original (for grading, etc) before doing anything
>with it using ffmpeg?
Yep!
___
ffmpeg-user
Carl Eugen Hoyos wrote:
>Iirc, here is a tool by Jerome that does act like a file
>archiving system for dpx files (and uses ffv1 internally).
Indeed, you {recall, remember} correctly! RAWcooked by Jérôme
Martinez, allows both to store e.g. DPX files into Матрёшка by
using FFV1 and to retrieve
Ulf Zibis wrote:
>Does the 'p' in yuv420p mean "progressive"?
No, it means "planar". Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
Dinesh Gupta wrote:
>While building 'ffmpeg' 4.0.2
Is there any reason for using this?
The current release of the 4.0 branch is 4.0.3 (since 3rd November)
and the most recent branch is 4.1 (since 6th November).
Best regards, Reto
___
ffmpeg-user
Harvey Pikelberger wrote:
>Is there something about ProRes files in general that makes
>the audio layout unrecognizable?
The container is QuickTime (.mov) or Matroska (.mkv), while
ProRes is the video codec, which has nothing to do with the
audio streams.
Best regards, Reto
Carl Eugen Hoyos wrote:
>I wonder if metadata is really sufficient to decode an mxf
>file...
In my personal opinion, no. Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To
yUGz afterLife wrote:
>-metadata TXXX:CATALOGNUMBER=’plop'
^
Don't use typographer's quote.
And, again, don't top-post.
Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
JD wrote:
ffprobe version N-51556-ge278500 Copyright (c) 2007-2013 the
FFmpeg developers
This is a very old version! Please update to the latest release
or, even better, to the HEAD.
Best regards, Reto
___
ffmpeg-user mailing list
Peter B. wrote:
On 24/07/18 21:47, Reto Kromer wrote:
We do rewrap ProRes into Matroska. Which is the reason for
transcoding it to FFV1?
...I guess the usual "way out" of proprietary formats?
As well as format normalization (to have less mixed codecs).
The problem I see in t
W M wrote:
>At the Irish Film Institute Film Archive, we are investigating
>the technicalities of normalising ProRes materials to FFV1,
We do rewrap ProRes into Matroska. Which is the reason for
transcoding it to FFV1?
Best regards, Reto
___
Mark Perry wrote:
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>>> To unsubscribe, visit link above, or email
>>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>> To unsubscribe, visit link above, or email
>>
Carl Eugen Hoyos wrote:
>I wonder if recording with 192kHz makes sense, this is
>far above what a human ear can do iirc.
Indeed! Usually it makes sense only if you have very bad
material and need to apply heavy restoration, otherwise
96 kHz is very fine for archival and 48 kHz for usage.
Best
William Caulfield wrote:
>haven't used Windows / Directshow for a few years, but back in
>the day I would have attempted this using VirtualDub and
>HuffYUV. I believe that HuffYUV is available for ffmpeg, but
>can't say that I've ever tried it.
Indeed, FFmpeg's flavour of HuffYUV is even better
Carles Vila wrote:
>ffmpeg version 2.7.2 Copyright (c) 2000-2015 the FFmpeg
>developers
You might possibly wish to upgrade to the current release 3.3.4.
Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Holger Jurna wrote:
>Hi, I would like to unsubscribe from this mailing list.
Please read the end of any email you received.
>> > > > > > ___
>> > > > > > ffmpeg-user mailing list
>> > > > > > ffmpeg-user@ffmpeg.org
>> > > > > >
Moritz Barsnick wrote:
>Does anyone ever read the complete thread? Michelle reported
>that that was solved in this email:
>http://ffmpeg.org/pipermail/ffmpeg-user/2017-July/036829.html
Yes, and as said two or three times, it actually does work well
with the current release (also without the
Michelle wrote:
>Yes, I have a snippit here -
>http://msknight.com/bbc/videos/MOV015.MOD
Thank you! I'm afrain, on my side it transcodes well to MP4 with
FFmpeg 3.3.3. I don't get the error message you mentioned at the
beginning. I have compiled with:
brew install ffmpeg --with-sdl2
Nicolas George wrote:
>You realize these counts as distributions, do you not?
Actually each one can compile with the specific options they
need, which is not possible with "classic" distributions.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Reindl Harald wrote:
>no *enduser* right in his mind don't use the
>development master of *any* software - period
+1
I already stressed out in the past the importance of the
releases for the end user community. Many audio-visual archives
do actually use - and keep up to date - FFmpeg via
msknight wrote:
>ffmpeg version 2.8.11-0ubuntu0.16.04.1
You should update to the current version of your branch, or -
even better! - to the brand new 3.3.3. Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
willin wrote:
>It looks homebrew is the easiest one for mac users to use
>ffmpeg which I haven't tried before.
Homebrew is indeed a good way to install and keep updated FFmpeg
on macOS (and Linuxbrew almost that good on different Linuxes,
including the Windows Subsystem for Linux).
Hope this
Kevin Wheatley wrote:
>On Fri, Jan 20, 2017 at 10:54 AM, Carl Eugen Hoyos
> wrote:
>> What is OCIO?
>
>OpenColorIO http://opencolorio.org/
>
>
>I'll say that adding OCIO to FFmpeg is not simple in the
>general sense. The two packages are not in the same space,
>OCIO is mostly
Moritz Barsnick wrote:
>Why do you need a release, anyway?
The question about the releases is asked from time to time.
I don't use releases myself, but I always advise AV
archivists, who implement FFmpeg in their workflow, to use
the last release of an actively maintained branch. Why?
Because
ganesh.ire...@syda.org wrote:
>ffmpeg -i "INPUT" -map 0:a -f md5 -hash md5 -
Add "-loglevel quiet".
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
Nikhil M Ranka wrote:
>ffmpeg version N-63893-gc69defd Copyright (c) 2000-2014
>the FFmpeg developers built on Oct 31 2014 05:16:04
As Carl Eugen already mentioned, you should really update.
Best regards, Reto
___
ffmpeg-user mailing list
Olexandr Melnyk wrote:
>ffmpeg version 2.8.4 Copyright (c) 2000-2015
Please update to the last release or the current HEAD.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link
Carl Eugen Hoyos wrote:
>Which date are you talking about?
The release date integrated into the version designation.
This would definitively make it more human readable.
Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Phil Rhodes wrote:
>>> Using ffmpeg version N-51556-ge278500
>
>
>> That version of ffmpeg is from April 2013.
>
>How do you tell?
>Serious question.
In my opinion, it would be useful indeed to have a version
numbering that includes the actual date, like e.g.:
2016-09-15-01234567
Yet I am
Adam Lott wrote:
>I'm
>including screenshots of my results to better show what
>happened.
Please copy and paste the console output on this list. This
makes answering much easier. Thank you! Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Eng.Hany Ahmed wrote:
>this is not work with this stream i wrote the full command
>and the output log without cut in the attachment file
>please tell me why not work
Please:
1) don't top post on this list;
2) update your version as already suggested by Moritz;
3) put the command and output
Walid Salman wrote:
>How i get the last full ffmpeg :
>In linux
See:
http://ffmpeg.org/download.html
or use Linuxbrew:
http://linuxbrew.sh/
Hope this helps! Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Avinash Jairam wrote:
>ffmpeg -f concat -i filesToMerge.txt -c copy output.mp4
Do you specify absolute file paths? This may help:
https://amiaopensource.github.io/ffmprovisr/#join_files
>ffmpeg version N-76944-g15206ff Copyright (c) 2000-2015
Please consider updating to the current git head
Celso Junior wrote:
>ffmpeg version 2.8.6-1ubuntu2 Copyright (c) 2000-2016 the FFmpeg developers
> built with gcc 5.3.1 (Ubuntu 5.3.1-11ubuntu1) 20160311
Please update to HEAD or version 3.1.1.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Keith Reilly wrote:
>ffprobe version 0.7.4
That's old! I guess the current release should be:
ffprobe version 3.0.2
Or use the HEAD. You may reinstall --with-ffplay.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Keith Reilly wrote:
>-loglevel quiet didn't give me errors. But it didn't give
>me any output either. I took out that part of the command.
>Looked like this:
>
>ffprobe -print_format json -show_format -show_streams
>file.mp4
Works fine on my side (both with and without the -loglevel
quiet
aviv solodoch wrote:
>I'm trying to create a movie from a series of .png files.
>The file names are of the form "NWAT_Vort_GB_.pg",
>where is a 4 digit number. The lowest value is =1148.
>
>I write in my windows command shell, from the same folder as the .png files:
>
>ffmpeg -f
Emre Besirik wrote:
>I think it is only you who for some reason hates to read
>top post mails and the rest of the worlds 99% of population
>doesn’t have any problems writing or reading from top or
>bottom?
I also really appreciate this highly sensitive rule. And I
disagree with you - and with
Martín Capón Borrego wrote:
>Tell me what I am wrong
1. Do not top post on this list.
2. Use subject lines describing the content.
3. Review you messages before posting.
4. Read the answers you receive.
___
ffmpeg-user mailing list
Hello Martín:
Why the hell do you not respect the elementary rules on this
list? You are incredibly impolite indeed!
Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Satinder Singh wrote:
>Sorry . Sir , I apologize .
And it would also be most appreciated, if you avoid top
posting on this list. Thank you!
Best regards, Reto
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Peter B. wrote:
>The value of "bpr" seems to stand for bits_per_sample.
"bits_per_raw_sample" is the number of bits for each sample,
commonly 8, 9, 10 or 16.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Parag Goyal IMD, Applied Chemistry, IT-BHU, Varanasi (INDIA) wrote:
And regarding top-posting , is there any protocols to be followed while
posting on this mailing list . If yes , my apologies and please let me know
them.
Again wrong! May this help?
Moritz Barsnick wrote:
P.S.:
A: Because it
These references could also be useful for the DPX discussion:
Bob Friesenhahn: SMPTE 268M-2003 Specification Inadequacies, 2005-12-03
http://www.simplesystems.org/users/bfriesen/dpx/dpx-issues.pdf
Bob Friesenhahn: SMPTE 268M (DPX) Byte Order Issues, 2006-08-22
://code.google.com/p/corkami/
Hope this helps! Reto
Reto Kromer | AV Preservation by reto.ch
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
62 matches
Mail list logo