-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for a complete build version of this great modification! #7
Comments
Which platform? mac/linux/win? |
I need both win and linux versions actually, but either one of them is still good enough. Thank you in advance. |
Sorry sir, do you have any update on this matter? |
None update; If you want to compile by yourself, you need install libx265 |
It's really not hard to compile yourself if your motivated. These guys
already do a significant amount of work every day without compensation from
anyone. When quqi first came out with his rtmp using h265 it was only for
mac and i needed it for PC, i spent a few weeks learning where the code was
different and eventually slipped the code into a windows build. Then i
used the dll's for OBS and now i can stream h265 over rtmp in obs using
nvidia acceleration. Now i need to fix wowza so it will make h265 hls.
When people give you code for free, you should do your own work to
understand how to use it in your own application.
Keep in mind that it can be illegal or a violation of copyright laws for
someone to provide compiled executables that are completely legal for you
to compile on your own.
…On Sun, Jul 25, 2021, 1:03 AM yanlong ***@***.***> wrote:
Which platform? mac/linux/win?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIW77MFFPQFDASDK7L3IKIDTZOLLBANCNFSM5A5ES4FQ>
.
|
I will support one shell script for compile this project, you can compile use it by yourself. |
That is very nice of you Mr. It's not that I do not want to compile it myself, just difficult to find a good start document. I'm intending to use this tool for compiling: https://github.com/m-ab-s/media-autobuild_suite#custom-patches since it seems to be the least complicated one. The problem is how to replace the original git src of ffmpeg (that the tool will use) by your version. Best Regards. |
Compile Script: |
Hello Mr, I have been trying to compile ffmpeg on Windows 10 (using your src code) with x264 and x265 since the last week and everytime I thought I have gotten it, the process fails with a new kind of error and this time is the one that I have no clue on how to overcome it. To be more specific, I have followed 2 tutorials that I found: x265: http://www.gregwessels.com/dev/2017/10/27/ffmpeg-x265.html After compiling the 2 above libraries, I set the pkg-config path to where I have installed x265 --> verify that it is there certainly and run the ffmpeg configure command: CPPFLAGS="$CPPFLAGS -I/usr/local/x86_64-w64-mingw32/include" ./configure --extra-ldflags='-L/usr/local/x86_64-w64-mingw32/lib'--prefix=/usr/local/x86_64-w64-mingw32 --target-os=mingw32 --enable-w32threads --arch=x86_64 --enable-runtime-cpudetect --enable-static --disable-shared --enable-gpl --enable-libx264 --enable-libx265 --enable-asm --enable-x86asm And it ended up with this message which I wonder if the reason could be an incompatible x265 version with your ffmpeg? Thank you so much. |
It looks like that you have not link the libx265. Do you install the x265 librarys? |
Here compile guide :https://trac.ffmpeg.org/wiki/CompilationGuide you can compile with it |
you may wish to also add hardware support as I have, encoding h265 is much
easier with nvidia nvenc and it works great with RTMP
also you can add all this to OBS if you build the static and transplant the
DLL into your obs system.
I believe this and the extra libraries linked will do the trick ...
…--enable-nonfree --enable-nvenc --enable-libx264 --enable-gpl
--enable-cuda --enable-cuvid --enable-cuda-nvcc
Kind Regards,
Jeffrey Morrison
954.214.6322
On Tue, Aug 3, 2021 at 10:57 PM yanlong ***@***.***> wrote:
Yes sir, I think I do have x265 linked using pkg path.
[image: image]
<https://user-images.githubusercontent.com/28868992/128106799-dfd0835c-d8ec-48ff-90a6-b2dc19b82276.png>
Here compile guide :https://trac.ffmpeg.org/wiki/CompilationGuide
you can compile with it
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIW77MAX3OUQFYKUDCR2YMLT3CUCLANCNFSM5A5ES4FQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Dear Mr,
May I request a compiled version of your version of ffmpeg? It's the exact solution that I'm looking for to get the flv h265 streaming work. However, I do not really know how to go from this pure src code only.
Best Regards.
The text was updated successfully, but these errors were encountered: