Re: [FFmpeg-user] [External] Re: FFmpeg 4.3.1 failing to build for x86_64
Yes I did build openssl. It built successfully for all the architectures. "i386 x86_64 armv7 armv7s arm64" . However when building ffmpeg build script, the build fails for specific X86_64 architecture. Attached both openssl and ffmpeg build script for your reference. On 02/02/21, 12:49 PM, "ffmpeg-user on behalf of Carl Zwanzig" wrote: On 2/1/2021 11:05 PM, Vineeth, Surya via ffmpeg-user wrote: > 3. you have it installed exactly how? ?- Downloaded Openssl package fromhttps://www.openssl.org/source/openssl-1.1.1i.tar.gz But then you did not _build_ it? You need the _devel_ package of OpenSSL for the target architecture. z! ___ 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 subject "unsubscribe". build-libssl-bitcode.sh Description: build-libssl-bitcode.sh build-ffmpeg-sdk-all-bitcode.sh Description: build-ffmpeg-sdk-all-bitcode.sh ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] [External] Re: FFmpeg 4.3.1 failing to build for x86_64
On 2/1/2021 11:05 PM, Vineeth, Surya via ffmpeg-user wrote: 3. you have it installed exactly how? ?- Downloaded Openssl package fromhttps://www.openssl.org/source/openssl-1.1.1i.tar.gz But then you did not _build_ it? You need the _devel_ package of OpenSSL for the target architecture. z! ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] [External] Re: FFmpeg 4.3.1 failing to build for x86_64
ok, you are not capable to compose a proper email Am 02.02.21 um 08:05 schrieb Vineeth, Surya via ffmpeg-user: 1. you are running what operating system? - MacOS is the operating system where the build script is run. jesus 2. you have donloaded excatly what?- Downloaded Openssl package from https://www.openssl.org/source/openssl-1.1.1i.tar.gz 3. you have it installed exactly how? ?- Downloaded Openssl package from https://www.openssl.org/source/openssl-1.1.1i.tar.gz well, by just downloading a random source tarball there is nothing installed at all ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] [External] Re: FFmpeg 4.3.1 failing to build for x86_64
1. you are running what operating system? - MacOS is the operating system
where the build script is run. FFMPeg I am building for the iOS platform for
both simulator(i386,x86_64) and device architectures. And for specific x86_64 ,
I am facing the error "Openssl not found" when the configure script is run
2. you have donloaded excatly what?- Downloaded Openssl package from
https://www.openssl.org/source/openssl-1.1.1i.tar.gz
3. you have it installed exactly how? ?- Downloaded Openssl package from
https://www.openssl.org/source/openssl-1.1.1i.tar.gz
4. did you really download and install the *devel* package - I have
downloaded ffmpeg version 4.3.1 and trying to build with the above mentioned
openssl version. The following configure command when run for X86_64
architecture is when the error is observed. All other architecture works fine
with the same script.
echo "configure"
TMPDIR=${TMPDIR/%\/} $CWD/$SOURCE/configure \
--target-os=darwin \
--arch=$ARCH \
--cc="$CC" \
$CONFIGURE_FLAGS \
--extra-cflags="$CFLAGS" \
--extra-cxxflags="$CXXFLAGS" \
--extra-ldflags="$LDFLAGS" \
--prefix="$THIN/$ARCH" \
|| exit 1
On 02/02/21, 12:25 PM, "ffmpeg-user on behalf of Reindl Harald"
wrote:
Regards,
Surya Vineeth
Am 02.02.21 um 07:51 schrieb Vineeth, Surya via ffmpeg-user:
> I have downloaded openssl package 1.1.1i and trying to build ffmpeg.
>
> On 02/02/21, 12:14 PM, "ffmpeg-user on behalf of Carl Zwanzig"
wrote:
>
> On 2/1/2021 10:40 PM, Reindl Harald wrote:
> > the mail you refered never made it to the list
>
> I was just looking for that :), maybe the attached log was too big.
>
> >> I am facing error while building ffmpeg for x66_64 architecture.
The
> >> error says “ERROR: openssl not found”.
> Could be that you don't have the appropriate openssl dev package
installed
> for x86_64. Or that it's in the wrong location. Or your configure
line is
> pointing to the wrong location.
>
> Without substantially more info, it's all guessing.
hell, stop top-posting and that quoting style (no quoting at all,
compare your message with mine)
* you are running what operating system?
* you have donloaded excatly what?
* you have it installed exactly how?
* did you really download and install the *devel* package
___
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 subject "unsubscribe".
___
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 subject "unsubscribe".
Re: [FFmpeg-user] [External] Re: FFmpeg 4.3.1 failing to build for x86_64
On 2/1/2021 10:51 PM, Vineeth, Surya via ffmpeg-user wrote: I have downloaded openssl package 1.1.1i and trying to build ffmpeg. Did you download the -correct- openssh? Attaching the log file alone here in case you could not download the previous one. Your configure line is hideously long (1100+ chars), do you need all of that?? Since I assume you're running *nix, at least use some symlinks or shell vars to shorten things. (and what Harald said, too). z! ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] [External] Re: FFmpeg 4.3.1 failing to build for x86_64
Am 02.02.21 um 07:51 schrieb Vineeth, Surya via ffmpeg-user: I have downloaded openssl package 1.1.1i and trying to build ffmpeg. On 02/02/21, 12:14 PM, "ffmpeg-user on behalf of Carl Zwanzig" wrote: On 2/1/2021 10:40 PM, Reindl Harald wrote: > the mail you refered never made it to the list I was just looking for that :), maybe the attached log was too big. >> I am facing error while building ffmpeg for x66_64 architecture. The >> error says “ERROR: openssl not found”. Could be that you don't have the appropriate openssl dev package installed for x86_64. Or that it's in the wrong location. Or your configure line is pointing to the wrong location. Without substantially more info, it's all guessing. hell, stop top-posting and that quoting style (no quoting at all, compare your message with mine) * you are running what operating system? * you have donloaded excatly what? * you have it installed exactly how? * did you really download and install the *devel* package ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] FFmpeg 4.3.1 failing to build for x86_64
On 2/1/2021 10:40 PM, Reindl Harald wrote: the mail you refered never made it to the list I was just looking for that :), maybe the attached log was too big. I am facing error while building ffmpeg for x66_64 architecture. The error says “ERROR: openssl not found”. Could be that you don't have the appropriate openssl dev package installed for x86_64. Or that it's in the wrong location. Or your configure line is pointing to the wrong location. Without substantially more info, it's all guessing. z! ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] "instead of complaining, submit a patch" [was: Re: minterpolate problem]
Am 02.02.21 um 07:39 schrieb Carl Zwanzig: On 2/1/2021 10:30 PM, Reindl Harald wrote: muhahaha - a word document is how writers work? in case microsoft office (or libre office writer) is the solution i want my problem back So far off-topic, but YES, most writers (technical, legal, fiction, and otherwise) work in ms-word (with the occasional libre-office or other word processor) unless they use a purpose-built system (newspapers, broadcast journalism, screen-writers, etc). They do not use basic text editors as programmers do. You don't have to like it, and you can have your problem back if you want, but that's how it is. well, that explains the amount of idiots writing html mails without a single char formatted :-) ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] FFmpeg 4.3.1 failing to build for x86_64
Am 02.02.21 um 07:34 schrieb Vineeth, Surya via ffmpeg-user: Hi Team, Any update on this issue? From: "Vineeth, Surya" Date: Monday, 1 February 2021 at 11:48 AM To: "ffmpeg-user@ffmpeg.org" Subject: FFmpeg 4.3.1 failing to build for x86_64 Hi Team, I am facing error while building ffmpeg for x66_64 architecture. The error says “ERROR: openssl not found”. For all other architecture like “i386 armv7s arm64 armv7”, it works fine. Kindly help in resolving this issue. Attaching the log file for more information. the mail you refered never made it to the list anyways, you don#t tell which operating system, which compiler, if libraries are installed, in which way they are installed and so on and throw away you mail client - never seen such a bad quoting, no matter if top-posting or not ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] "instead of complaining, submit a patch" [was: Re: minterpolate problem]
On 2/1/2021 10:30 PM, Reindl Harald wrote: muhahaha - a word document is how writers work? in case microsoft office (or libre office writer) is the solution i want my problem back So far off-topic, but YES, most writers (technical, legal, fiction, and otherwise) work in ms-word (with the occasional libre-office or other word processor) unless they use a purpose-built system (newspapers, broadcast journalism, screen-writers, etc). They do not use basic text editors as programmers do. You don't have to like it, and you can have your problem back if you want, but that's how it is. z! ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] FFmpeg 4.3.1 failing to build for x86_64
Hi Team, Any update on this issue? From: "Vineeth, Surya" Date: Monday, 1 February 2021 at 11:48 AM To: "ffmpeg-user@ffmpeg.org" Subject: FFmpeg 4.3.1 failing to build for x86_64 Hi Team, I am facing error while building ffmpeg for x66_64 architecture. The error says “ERROR: openssl not found”. For all other architecture like “i386 armv7s arm64 armv7”, it works fine. Kindly help in resolving this issue. Attaching the log file for more information. Regards, Surya Vineeth ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] "instead of complaining, submit a patch" [was: Re: minterpolate problem]
Am 02.02.21 um 01:12 schrieb Phil Rhodes via ffmpeg-user: The way it would usually work, if someone was willing to do some pro bono technical writing, is that it'd be written as a word document, because that's how writers work, revised using the features built into word documents for that exact purpose, and submitted to some sort of content management system. muhahaha - a word document is how writers work? in case microsoft office (or libre office writer) is the solution i want my problem back ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] "instead of complaining, submit a patch" [was: Re: minterpolate problem]
On Monday, 1 February 2021, 23:36:19 GMT, Jim DeLaHunt wrote: > In many projects, "instead of complaining, submit a patch" is good > advice. It turns users into contributors. But FFmpeg is not just any> project. Quite. Knowing what I know, I'd sooner eat catfood than submit changes to ffmpeg. The way it would usually work, if someone was willing to do some pro bono technical writing, is that it'd be written as a word document, because that's how writers work, revised using the features built into word documents for that exact purpose, and submitted to some sort of content management system. Of course all of these things are laughably impossible in the case of ffmpeg because er, reasons and stuff. How else would they maintain such wonderful, class-leading documentation? P ___ 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 subject "unsubscribe".
[FFmpeg-user] "instead of complaining, submit a patch" [was: Re: minterpolate problem]
On 2021-01-31 05:05, Rodney Baker wrote: On Friday, 29 January 2021 21:12:06 ACDT Phil Rhodes via ffmpeg-user wrote: On Friday, 29 January 2021, 09:43:09 GMT, Mark Filipak (ffmpeg) wrote: Try 'ffmpeg -h type=filter. It fails. Why? Because "filter" is a "type", not a "name" -- never mind that the details says "... named decoder/encoder ..." Yes, this is the sort of thing that causes the problem. Easy to fix, though, you'd have thought. P Well, if you have a solution, instead of complaining, submit a patch to the ffmpeg-devel mailing list. If it gets accepted, congratulations - you've just helped to improve the product! In many projects, "instead of complaining, submit a patch" is good advice. It turns users into contributors. But FFmpeg is not just any project. How has submitting documentation patches gone for you? In my experience, substantive documentation patches trigger immune responses, and either don't get accepted but cause pain ([1a], [1b], [1c]), or get accepted only after much pain ([2a], [2b]). Both those attempts also earned me a private email from a senior developer wishing I would go away and stop participating in FFmpeg. The patches that get accepted straightforwardly were minor FAQ changes([3a], [3b]) or repo fixes [4]. [1a] https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2020-April/261467.html [1b] https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2020-May/261792.html [1c] https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2020-May/261811.html [2a] https://ffmpeg.org/pipermail/ffmpeg-devel/2017-November/220528.html [2b] https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2017-December/221596.html [3a] https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2017-November/219782.html, [3b] https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2017-November/219925.html [4] https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2017-November/220095.html My experience has persuaded me that "instead of complaining, submit a patch" is not an easy path to follow in this project. —Jim DeLaHunt ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] minterpolate problem
On 02/01/2021 11:03 AM, Paul B Mahol wrote: People your age enjoy their life. You should too. Why you want to dealt with digital video... I enjoy it. -- Someone's sneaking in and turning up the range so that my food burns. I'm sure of it. And the older I get, the more sure of it I become. ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] Subtitle Error - Suggestion
Am Mo., 1. Feb. 2021 um 03:55 Uhr schrieb Jim : > [Parsed_subtitles_0 @ 0x554ed40] Unable to open comments.srt This is the first error message. The problem was not that your file caused a parsing error that could provoke a specific error message, the problem was that your file was not detected as anything readable by FFmpeg. Carl Eugen ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] minterpolate problem
On Mon, Feb 1, 2021 at 3:49 AM Mark Filipak (ffmpeg) wrote: > Developers, kindly pay attention to this post... > > On 01/31/2021 10:24 AM, Phil Rhodes via ffmpeg-user wrote: > > On Sunday, 31 January 2021, 13:24:39 GMT, Rodney Baker < > rodney.ba...@iinet.net.au> wrote: > > > >> See man ffmpeg for detailed description of the options... > try typing > "man ffmpeg" into a google search and see what comes up... > > http://manpages.org/ffmpeg...> Look for the section titled "Generic > Options". > There you'll find the detailed descriptions you're looking for. > > ISSUE #1: > I did not get this reply from Rodney Baker. The list server apparently is > not sending out all > messages to all user-ffmpeg subscribers. I've noticed this before but > didn't 'say' anything. > > > Oh, right, yes, obviously. That's what I call first-order retrievability! > > To the broader question: > > Experts posting on this list frequently become irritated when people ask > basic questions. Well, actually, they tend to become almost comically > abusive, but that's another issue. > > If these people want to field less basic questions, they should improve > the documentation. > > If they don't want to improve the documentation, they should let someone > else do it. People have repeatedly offered. > > Rejecting all of those options and returning to the abuse is not > reasonable. > > P > > ISSUE #2: > ffmpeg -h says: "See man ffmpeg for detailed description of the options." > So I went into my Linux VM, submitted "man ffmpeg", and redirected it into > a text file. > 'man ffmpeg' is as uninformative as 'ffmpeg -h' -- this is typical of > 'man' pages. > > I had no idea 'http://manpages.org/ffmpeg' existed until I read Phil's > response to Rodney's reply. > > Why is ffmpeg documentation so scattered? > Why is ffmpeg documentation so disorganized? > Why is ffmpeg documentation so vague? > Why is the English grammar in ffmpeg documentation so poor? > > Regarding the wiki: > It is mostly just an empty shell. > Based on my experience with Wikipedia, /wiki.*/gi=='amateurish', > /wiki.*/gi=='ad hoc', > /wiki.*/gi=='incomplete', /wiki.*/gi=='non authoritative', > /wiki.*/gi=='untrustworthy', > /wiki.*/gi=='disinformation'. > Question: Why would any authoritative person contribute to a wiki? Answer: > They don't bother. > > I've been running ffmpeg approximately 14 hours per day for over 1/2 year. > I don't have a life > outside ffmpeg. (I haven't watched popular TV since 1983 and have no > social life.) I'm 74 years old > and may not have much more time left (except I do take good care of > myself). > > People your age enjoy their life. You should too. Why you want to dealt with digital video... > I'm a university engineer. I know video. I know a little about ffmpeg. The > stumbling block is ffmpeg > documentation. > ___ > 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 subject "unsubscribe". ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] co64 atom in QT / Mp4, and compatibility with Premiere _ FIXED
> On 31 Jan 2021, at 13:06, Bouke wrote: > > This is not an FFmpeg question perse, but I hope someone knows more about > atoms than I do. > > Similar to the previous thread, I am modifiying clips ‘in place / > destructive’. (For .Mp4 / .mov files) > > For that I re-write or re-order the moov atom to needs. > That all seems to work fine, if files are < 4 gig. > On larger files, when I want to change TC, I add an mdat atom with the TC > converted to frame number. > In the TC track (That I rip from a dummy FFmpeg short transcode), I change > the pointer in the TC tracks stco atom to the newly added mdat location. > So far so good. > > Now, when the new mdat pos goes over 4 gig, I add an co64 atom so I have 8 > bytes to set it, and I change the whole shebang to reflect the new length of > all atoms in the structure. > This also ‘sorta kinda’ works, as QT player displays the correct TC. > > BUT, Adobe Premiere does NOT like this, it gives me another TC that I can’t > place for the life of me… > If I omit the co64 atom and find ‘some’ spot (either inside an mdat atom or > not), it works, but it seems Premiere totally ignores the co64 info. For the archives: Fixed. trouble was that Premiere / Resolve expect the co64 atom INSTEAD of stco, rather than after to overwrite previous value. Bouke ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] minterpolate ...for Paul
On Sat, Jan 30, 2021 at 1:02 AM Mark Filipak (ffmpeg) wrote: > On 01/29/2021 07:10 PM, Carl Eugen Hoyos wrote: > > Am Sa., 30. Jan. 2021 um 01:00 Uhr schrieb Mark Filipak (ffmpeg) > > : > > > >> I don't know what you mean by "This does not look like the input file > from your command line" > > > > I meant that you provided the output file but you should (always) provide > > the input file. The output file is very, very rarely useful. > > > > Carl Eugen > > Wait, let me get this right... > > "This does not look like the input file from your command line" is your > way of saying "you should > (always) provide the input file"? > > Can you see that providing such ...oblique? ...misleading? ...cryptic? > clues to what you actually > mean instead of providing straightforward statements ...Can you see that > that's going to confuse > people? ...Can you see that, when it becomes clear what you really mean, > it can cause people to > resent you? ...Can you see those things? > > No, he's trying to help and it's best to just post the input file. Your response here isn't helpful at all and it's kinda nasty. K ___ 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 subject "unsubscribe".
Re: [FFmpeg-user] Questions about "Cannot allocate memory"
> Am 01.02.2021 um 02:28 schrieb Mark Filipak (ffmpeg) : > > "Error while filtering: Cannot allocate memory In your case, the error message simply means that you ran out of free memory. minterpolate needs gigantic buffers. (The same error unfortunately is shown if a filter cannot be found iirc.) Carl Eugen ___ 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 subject "unsubscribe".
