-
Notifications
You must be signed in to change notification settings - Fork 115
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
Support for FFV1 #10
Comments
I'll see about adding FFV1 in the next update. For now there are only the presets But you can select Denoise Here are more details on the filter: Then press the Run button. |
Hey, how are you doing? I know it might be too much to ask, but would it be
possible to implement Rav1e AV1 encoder in Axiom? Current Libaom is
incredibly slow, while Rav1e is comparatively fast enough to be used.
However it is not implemented in FFmpeg, so I'm guessing there is a lot of
compatibility issues, maybe you have some suggestions?
Link to Rav1e: https://github.com/xiph/rav1e
…On Tue, 17 Jul 2018 at 22:36, Matt McManis ***@***.***> wrote:
I'll see about adding FFV1 in the next update.
For now there are only the presets default, light, medium, heavy for
denoising.
But you can select Denoise Heavy and press the Script button and change
the value of threshold and steps in
vaguedenoiser=threshold=6:method=soft:nsteps=5.
Here are more details on the filter:
https://ffmpeg.org/ffmpeg-filters.html#vaguedenoiser
Then press the Run button.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfiKlAV0tOZIoSKrHjoz4Qy8ABQFyeKTks5uHjyrgaJpZM4VQRFq>
.
|
Unfortunately Axiom can only generate commands for FFmpeg. It would require a whole new set of rules to generate the different commands for rav1e. But if it is simple enough, I may create a separate GUI just for rav1e in the future.
________________________________
From: Monteco <notifications@github.com>
Sent: Thursday, July 19, 2018 12:04 AM
To: MattMcManis/Axiom
Cc: Matt McManis; Comment
Subject: Re: [MattMcManis/Axiom] Support for FFV1 (#10)
Hey, how are you doing? I know it might be too much to ask, but would it be
possible to implement Rav1e AV1 encoder in Axiom? Current Libaom is
incredibly slow, while Rav1e is comparatively fast enough to be used.
However it is not implemented in FFmpeg, so I'm guessing there is a lot of
compatibility issues, maybe you have some suggestions?
Link to Rav1e: https://github.com/xiph/rav1e
On Tue, 17 Jul 2018 at 22:36, Matt McManis ***@***.***> wrote:
I'll see about adding FFV1 in the next update.
For now there are only the presets default, light, medium, heavy for
denoising.
But you can select Denoise Heavy and press the Script button and change
the value of threshold and steps in
vaguedenoiser=threshold=6:method=soft:nsteps=5.
Here are more details on the filter:
https://ffmpeg.org/ffmpeg-filters.html#vaguedenoiser
Then press the Run button.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfiKlAV0tOZIoSKrHjoz4Qy8ABQFyeKTks5uHjyrgaJpZM4VQRFq>
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#10 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXx6Qkh3IJchJYnGrzFoqgOZNMfvpWWkks5uIC9vgaJpZM4VQRFq>.
|
Thanks for letting me know.
…On Thu, Jul 19, 2018, 17:16 Matt McManis ***@***.***> wrote:
Unfortunately Axiom can only generate commands for FFmpeg. It would
require a whole new set of rules to generate the different commands for
rav1e. But if it is simple enough, I may create a separate GUI just for
rav1e in the future.
________________________________
From: Monteco ***@***.***>
Sent: Thursday, July 19, 2018 12:04 AM
To: MattMcManis/Axiom
Cc: Matt McManis; Comment
Subject: Re: [MattMcManis/Axiom] Support for FFV1 (#10)
Hey, how are you doing? I know it might be too much to ask, but would it be
possible to implement Rav1e AV1 encoder in Axiom? Current Libaom is
incredibly slow, while Rav1e is comparatively fast enough to be used.
However it is not implemented in FFmpeg, so I'm guessing there is a lot of
compatibility issues, maybe you have some suggestions?
Link to Rav1e: https://github.com/xiph/rav1e
On Tue, 17 Jul 2018 at 22:36, Matt McManis ***@***.***>
wrote:
> I'll see about adding FFV1 in the next update.
>
> For now there are only the presets default, light, medium, heavy for
> denoising.
>
> But you can select Denoise Heavy and press the Script button and change
> the value of threshold and steps in
> vaguedenoiser=threshold=6:method=soft:nsteps=5.
>
> Here are more details on the filter:
> https://ffmpeg.org/ffmpeg-filters.html#vaguedenoiser
>
> Then press the Run button.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#10 (comment)>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AfiKlAV0tOZIoSKrHjoz4Qy8ABQFyeKTks5uHjyrgaJpZM4VQRFq
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<
#10 (comment)>,
or mute the thread<
https://github.com/notifications/unsubscribe-auth/AXx6Qkh3IJchJYnGrzFoqgOZNMfvpWWkks5uIC9vgaJpZM4VQRFq
>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfiKlPD1WVegyDElQgRkzf-PUjJkQ2-Dks5uIJTZgaJpZM4VQRFq>
.
|
Hey, axiom started having problems when trying to encode AV1 video, it
gives:
Could not write header for output file #0 (incorrect codec parameters ?):
Invalid data found when processing input
Error initializing output stream 0:0 --
ffmpeg version N-91634-gc2eec1762d Copyright (c) 2000-2018 the FFmpeg
developers
built with gcc 8.2.1 (GCC) 20180813
configuration: --enable-gpl --enable-version3 --enable-sdl2
--enable-fontconfig --enable-gnutls --enable-iconv --enabl
e-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame
--enable-libopencore-amrnb --enable-libopencore-amr
wb --enable-libopenjpeg --enable-libopus --enable-libshine
--enable-libsnappy --enable-libsoxr --enable-libtheora --enab
le-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp
--enable-libx264 --enable-libx265 --enable-libxml2 --
enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab
--enable-libvorbis --enable-libvo-amrwbenc -
-enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom
--enable-libmfx --enable-amf --enable-ffnvcodec --e
nable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2
--enable-avisynth
|
It may have to do with the video stream selected or sometimes if the video has image subtitles instead of text it gives a similar error.
…________________________________
From: Monteco <notifications@github.com>
Sent: Saturday, August 18, 2018 9:11:45 AM
To: MattMcManis/Axiom
Cc: Matt McManis; Comment
Subject: Re: [MattMcManis/Axiom] Support for FFV1 (#10)
Hey, axiom started having problems when trying to encode AV1 video, it
gives:
Could not write header for output file #0 (incorrect codec parameters ?):
Invalid data found when processing input
Error initializing output stream 0:0 --
ffmpeg version N-91634-gc2eec1762d Copyright (c) 2000-2018 the FFmpeg
developers
built with gcc 8.2.1 (GCC) 20180813
configuration: --enable-gpl --enable-version3 --enable-sdl2
--enable-fontconfig --enable-gnutls --enable-iconv --enabl
e-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame
--enable-libopencore-amrnb --enable-libopencore-amr
wb --enable-libopenjpeg --enable-libopus --enable-libshine
--enable-libsnappy --enable-libsoxr --enable-libtheora --enab
le-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp
--enable-libx264 --enable-libx265 --enable-libxml2 --
enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab
--enable-libvorbis --enable-libvo-amrwbenc -
-enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom
--enable-libmfx --enable-amf --enable-ffnvcodec --e
nable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2
--enable-avisynth
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#10 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXx6Qj4TjBYrD6-KPnrLCwk4MVpdxz91ks5uSDzBgaJpZM4VQRFq>.
|
....so, still planning on adding lossless coded FFV1? Or nah? Coz the latest Alpha, I don't see FFV1 anywhere in the MKV container option.....also while we're at it, any plans on the other lossless video codecs? Like LAagarith, Utvideo, MSU and Huffyuv? And what about more channel support for FLAC? I notice there is only 4 options - source, stereo, mono and 5.1 - I believe FLAC supports more than just these 4 options..... I have a huge ass 500GB RAW footage I would like to transcode to lossless format for both audio and video for archival and storage purposes and to use as the master.......and it would seem you do not offer lossless video code, but do offer FLAC which is lossless audio...what's going on there? Which we're on the lossless audio codec subject here, if I pick source for FLAC, does that mean it would also transcode any and all spartial, ie fake channels in or leave those out as well, like what handbrake does as it doesn't support 7.1 nor fake channels? Yes I could transcode to x.264 with a constant rate factor of zero, but that isn't exactly lossless.....as I experienced this with handbrake and I can still see some loss in quality in various places if I look hard enough....plus handbrake down coverts the full RGB colourspace to 4:2:0 whatever, which is also not a lossless transcode.... |
In the latest release I recoded most of the program with a better design. I can now more easily add new codecs.
Each codec now has it's own class with a database table that lists the values for each option.
https://github.com/MattMcManis/Axiom/blob/master/source/Axiom/Axiom/Codecs/Video/x264.cs
I will work on adding FFV1, Huffyuv, and Lagarith in the next release in a few days.
The reason it's missing some lossless codecs is because the program began as a very simple webm converter and I started adding the more popular codecs over time. A popular combination I've seen is MKV with x265 10-bit / FLAC.
For surround sound FFmpeg gives the error "Specified channel layout '7.1' is not supported" when using the -ac 7 or -ac 8 command, it may have to be done with a special filter. But if you leave the channel as Source it should preserve the original layout and fake channels. I will have to ask the FFmpeg devs more about this. Axiom is missing a lot of options for audio channels right now. https://trac.ffmpeg.org/wiki/AudioChannelManipulation
…________________________________
From: DumbJoe <notifications@github.com>
Sent: Wednesday, March 13, 2019 5:24 AM
To: MattMcManis/Axiom
Cc: Matt McManis; Comment
Subject: Re: [MattMcManis/Axiom] Support for FFV1 (#10)
....so, still planning on adding lossless coded FFV1? Or nah? Coz the latest Alpha, I don't see FFV1 anywhere in the MKV container option.....also while we're at it, any plans on the other lossless video codecs? Like LAagarith, Utvideo, MSU and Huffyuv?
And what about more channel support for FLAC? I notice there is only 4 options - source, stereo, mono and 5.1 - I believe FLAC supports more than just these 4 options.....
I have a huge ass 500GB RAW footage I would like to transcode to lossless format for both audio and video for archival and storage purposes and to use as the master.......and it would seem you do not offer lossless video code, but do offer FLAC which is lossless audio...what's going on there? Which we're on the lossless audio codec subject here, if I pick source for FLAC, does that mean it would also transcode any and all spartial, ie fake channels in or leave those out as well, like what handbrake does as it doesn't support 7.1 nor fake channels?
Yes I could transcode to x.264 with a constant rate factor of zero, but that isn't exactly lossless.....as I experienced this with handbrake and I can still see some loss in quality in various places if I look hard enough....plus handbrake down coverts the full RGB colourspace to 4:2:0 whatever, which is also not a lossless transcode....
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#10 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXx6QvRVmyDMHJ9AW9WhGA5IdcbeuPULks5vWO3ygaJpZM4VQRFq>.
|
I have added FFV1 and released a new version 1.5.3 for you to test.
Select MKV, then FFV1 in Codecs.
The Video Quality dropdown menu will have Auto and Lossless.
Auto will default to 2 Pass. Lossless will default to 1 Pass, but can be changed.
I don't know if 2 Pass gives better quality, but I see it used here https://avpres.net/FFmpeg/im_MKV.html
Auto is also used for Codec Copy auto-detect if input/output extensions are the same. Codec Copy can also be selected manually if needed.
I've had to hardcode the FFV1 version 3 Parameters to default values. https://trac.ffmpeg.org/wiki/Encode/FFV1
If you want to change them to fine tune it, generate a script then edit it in the window and press Run.
I may be able to create new dropdown menus for changing the parameters later.
…________________________________
From: Matt M <mattmcmanis@outlook.com>
Sent: Wednesday, March 13, 2019 9:49 AM
To: MattMcManis/Axiom
Subject: Re: [MattMcManis/Axiom] Support for FFV1 (#10)
In the latest release I recoded most of the program with a better design. I can now more easily add new codecs.
Each codec now has it's own class with a database table that lists the values for each option.
https://github.com/MattMcManis/Axiom/blob/master/source/Axiom/Axiom/Codecs/Video/x264.cs
I will work on adding FFV1, Huffyuv, and Lagarith in the next release in a few days.
The reason it's missing some lossless codecs is because the program began as a very simple webm converter and I started adding the more popular codecs over time. A popular combination I've seen is MKV with x265 10-bit / FLAC.
For surround sound FFmpeg gives the error "Specified channel layout '7.1' is not supported" when using the -ac 7 or -ac 8 command, it may have to be done with a special filter. But if you leave the channel as Source and it should preserve the original layout and fake channels. I will have to ask the FFmpeg devs more about this. Axiom is missing a lot of options for audio channels right now. https://trac.ffmpeg.org/wiki/AudioChannelManipulation
________________________________
From: DumbJoe <notifications@github.com>
Sent: Wednesday, March 13, 2019 5:24 AM
To: MattMcManis/Axiom
Cc: Matt McManis; Comment
Subject: Re: [MattMcManis/Axiom] Support for FFV1 (#10)
....so, still planning on adding lossless coded FFV1? Or nah? Coz the latest Alpha, I don't see FFV1 anywhere in the MKV container option.....also while we're at it, any plans on the other lossless video codecs? Like LAagarith, Utvideo, MSU and Huffyuv?
And what about more channel support for FLAC? I notice there is only 4 options - source, stereo, mono and 5.1 - I believe FLAC supports more than just these 4 options.....
I have a huge ass 500GB RAW footage I would like to transcode to lossless format for both audio and video for archival and storage purposes and to use as the master.......and it would seem you do not offer lossless video code, but do offer FLAC which is lossless audio...what's going on there? Which we're on the lossless audio codec subject here, if I pick source for FLAC, does that mean it would also transcode any and all spartial, ie fake channels in or leave those out as well, like what handbrake does as it doesn't support 7.1 nor fake channels?
Yes I could transcode to x.264 with a constant rate factor of zero, but that isn't exactly lossless.....as I experienced this with handbrake and I can still see some loss in quality in various places if I look hard enough....plus handbrake down coverts the full RGB colourspace to 4:2:0 whatever, which is also not a lossless transcode....
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#10 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXx6QvRVmyDMHJ9AW9WhGA5IdcbeuPULks5vWO3ygaJpZM4VQRFq>.
|
Ah I see, thought you were trying to replace the many programs here: https://github.com/amiaopensource/ffmpeg-amia-wiki/wiki/3)-Graphical-User-Interface-Applications-using-FFmpeg which are now basically out of date or appear to be abandoned....except Handbrake - that seems to still be in active development, except it doesn't really have as much options as I would like, such as lossless video codec FFV1.....they appear to mainly focus on the x264 and the new x265 codecs coupled with probably lossy AAC audio codec, though they do have FLAC available to use if you're keen on lossless audio transcode.
Do please get back to me on that whatever the reasoning is, but yeah, according to that link, 7.1 should be supportable....
What about MSU and Utvideo?
Thanks, will give that a whirl....
Usually more than one pass gives a better quality but unless you have the patience to wait or and doing it on like less than 20GB files, but in this case since all codecs is lossless which means you can't really get any better quality than the original input, the only thing that would probably change is the file size, being slightly smaller....and that slightly, even if it's just a few megabytes I would happily wait to do a two or more pass of it....since this is for archiving and storage purposes after all anyways, so there's no rush to get this out as quickly as possible.... But I'll do both, one with one pass and the other with two pass to see if there is any difference in file size....
Of course, naturally you would want the latest version..... |
I've only used Handbrake and Avanti a few years ago, but haven't tried the others on that list. I've been developing Axiom as I learn C#, and use it to batch convert videos for my own projects. And it's great to see other people have used it for their work. I used to keep multiple webm and mp4 FFmpeg scripts in a text file that I would copy paste and modify to convert videos, but I thought wouldn't it be much easier if I made a program that would generate the scripts for me. I tried to focus on a UI that sets the correct dropdown menus for each codec, to prevent from choosing an incompatible setting on accident. And Auto Quality mode, which uses FFprobe bitrate detection, so that if someone doesn't know the correct settings they can leave it on Auto and still get a good encode. I will also see about adding Utvideo, but I don't see MSU listed in the FFmpeg codecs. I read that the pixel format for FFV1 should be I've fixed a few bugs in the latest version 1.5.3.3. Let me know if you come across any or if the program generates any wrong commands in the script. It should be becoming very stable now. |
Hmmmm, it seems to be Proprietary from here: www.compression.ru/video/ls-codec/index_en.html wikipedia: https://en.wikipedia.org/wiki/MSU_Lossless_Video_Codec so it doesn't seem to be associated with ffmpeg which probably why it's not in its codecs.... I only got that codec from reading various videohelp forum topics where they were having an argument on which lossless video codec was best...haha Default pixel format is fine as long as there are options to change to something else if your source material is RGB, for example. FFMPEG isn't multithreaded is it? Otherwise it's gonna take a while to transcode a 100GB+ file......on a single core/thread on a multicore CPU.....pegged at 100%.....whilst all other cores are sitting idly by, unless you managed to overclock your cores to like over 10Ghz, preferably 40Ghz to compensate using a single core on an 8 core CPU that's rated for 5Ghz each, assuming you've managed to get it stable at this high of a clock rating.....hah.... I've only done left Handbrake to digest such big files..... Ah I guess I'll find out when I transcode to FFV1.... I guess while you're on this, may as well add every other lossless codec possible that can be transcoded in ffmpeg, whether by itself or if it requires third party files to make it happen(maybe ffmpeg needs third party files to transcode MSU lossless codec?), for thoroughness. ☺hahaha. .. |
I've updated the Pixel Formats for all codecs in v1.5.4.0. Some codecs are limited in formats, but FFV1 can use many. I believe it is multithreaded, but may depend on the codec. In the For For now I'd only want to add the most popular lossless codecs so not to clutter up the menus with too many options. |
Thanks, now to get my other computer working again which has the file(s) I need to transcode with.....windows updates seems to have broken the computer and it now gets stuck at "Personalizing Settings (Not Responding)" with a black background screen and has been like that for the past 3 days....so it doesn't look like it's gonna be loading anytime soon if it's been hanging for 3 days like that! hahahaha ...any ideas? :P Bah, I won't pull you into this problem of mine - you probably already got heaps to deal with already; I guess I'll figure this one out myself..... hahaha
Ok fair enough. ☺ |
I'm unsure how to fix that windows problem. There seem to be some answers online. I read in here someone pressed Ctrl+Alt+Delete and were able to sign out and restart and it fixed it. Maybe you could also start in safe mode and see if it passes the Personalize Settings screen. |
Yeah, I can boot into safe mode but it's not quite same as using it normal mode....plus my mouse is really sensitive without razor synapse running and can't run that without internet connection.....oh and I'm on windows 7 btw....not 10. ☺ Also that Hmmmm.... :| |
Take a look here. Be careful not to corrupt your registry when editing it. Also if you have the Windows 7 disc, run a startup repair. http://www.justinswan.com/windows-7-stuck-on-personalized-settings-for-windows-desktop-update.html https://www.sysprobs.com/fix-temporary-profile-windows-7 I'll let you know when I add more codecs to the program. |
I've added |
Sorry, the computer decided to no longer cooperate with me....hah....took a while to figure out that clearing CMOS fixed that..... No it doesn't look like that fixed it, unfortunately......it still halts at the "Personalizing settings" but without the (not responding) part but at least get a default background, instead of the black one....maybe I should have backed up the registry.......before deleting stuff.....and startup repair disc just says my windows is not compatible.....rip......
Doesn't the colour profile also depends on the source material? Because if source is YUV444 or RGB, then yuv422p10le would be a lossy transcode which would be ironic if you intended to transcode to a lossless format for the purpose of preserving original material quality.... |
You're right. For FFV1, which color profile do you think is best to set as default? bgra Here's a list of the supported profiles for that codec https://pastebin.com/raw/7V82kQ49 |
Whoa, that's a lot! Is it possible that your program can auto detect the colour space and pick the correct equivalent by default? That would probably be the best choice for default; because then an average joe who doesn't know a thing about all these technical jargon could go "ok, I guess I'll just let the program best choose my ideal settings for me. " or add tooltips what their use case with examples.... Speaking of which, are you able to add in various transcode profiles, just like how handbrake has it on theirs so an average joe could just click on a profile that reads like what he thinks is acceptable and just go with that and all the guess work is done for them? For example have a transcode profile that's fit for uploading to youtube in various resolution options or a transcode profile that's best for viewing on mobile devices, etc., just take a look at what the authors of hanbrake has done to theirs.... |
I'm not able to find the FFprobe command to detect pixel format or color space, I'm not sure if it's in the file properties, so it's not able to auto detect. I could possibly make more Preset Profiles with extending dropdown menu levels. |
Hm, it would have to be, otherwise how else would MediaInfo be able to achieve this? What does the current "auto" option do in 1.5.8-Alpha? Is that an attempt of your own auto-detect and apply appropriate pixel format or colour profile?
Yes that'd be most welcomed! Also, back to my own problem, managed to fix it by loading last known good configuration.....hah.....but thanks for trying though! ☺ |
I will have to ask the devs or people more knowledgeable about FFprobe to find out the command to get that info. The current auto option just leaves the command blank, which allows FFmpeg to choose for itself, but sometimes it chooses one that makes the quality worse. That's why I force it to select yuv420p on most formats. If you want to open an issue titled something like "Add more transcode profiles", we can post more about it in the new thread and keep this thread for FFV1 and Lossless codecs. |
AHhh...
Sure! |
Hm, so I'm doing my transcode on version 1.5.8-Alpha build and notice that in FLAC, there isn't a compression settings.....and I know FLAC has 9 levels of compression(from using another tool that converts audio files), the highest giving you the smallest file but takes longer to do or the lowest that gives the biggest file but takes the quickest time if you are in a hurry. Where is this option? There are probably other lossless audio codecs that also provide a compression level that I've not used yet, what default does FLAC be on with your frontend gui? As for colour space, since my footage was taken in fraps, using the uncompressed box checked, my test sample is in RGB and the only RGB option there is is "rgb48le", I think.....should have probably researched all those profiles(From your raw pastebin) before clicking on one that looks like it will be it....hahaha facepalm.png |
Hmmm, supposedly fraps footage are either yuvj420p or bgr24 (someone mentioned bgra?) if you record with lossless RGB checked, both in REC. 709; according to this thread: http://forum.doom9.org/showthread.php?p=1556914 |
I think I can add a new compression level slider or dopdown menu for FLAC. I'll release it in the next update soon.
Opus also uses it, |
I've added Let me now how it works. |
Oh, there were a few more levels above 9 that dBpoweramp failed to tell me about....? huh....there is no way to pull this information once the file is transcoded is there? Like pick up what compression level was used for encoding the flac codec...?
Oh, that's new...never would have thought a lossy format to use a compression setting other than bitrate to derive your desired file size......interesting...... So I had done some tests on the older 1.5.8 version and here are the results for 2pass vs. 1pass: CPU utilization doesn't seem to be strict because none of my 12 workers are pegged to 100% when I encode a 300GB file: And changing thread count doesn't seem to do a thing either: https://i.imgur.com/afONWpf.png - I pick one thread thinking it would peg only one core of my hexacore CPU, but nope, uses all 12 threads inefficiently........but at least it spread the load.......maybe ffmpeg is single threaded and not multithreaded and thus windows is trying to distribute the load evenly on all 12 threads, as it was only handbrake that brought multithread feature to boost efficiency? hmmm... |
I think And For
For threading, I read this post here, they say,
You might want to try |
I guess if you want to clean it up a bit more, you could alphabetize the supported profiles, so it looks like this: and not this:
This is their official site: https://xiph.org/flac/documentation_tools_flac.html and they make no mention of levels 10 to 12.....only -0 to -8 which is 1 to 9 in human speak.....hah...
Heh, with lossy, you don't really wanna add additional compression to it not unless enjoy the metallic robotic sound artifacts of low quality audio streams! But, I guess different strokes for different folks, some don't mind this and others do; but at least Opus is more effecient than either AAC, AC3 and MP3 combined together so at the same bitrate level, Opus would be better but media info doesn't always display this for some reason...
Hmmm, I suspected so too, let me know what they say. ☺
Yeah I'll give those a try next. |
I'll look into sorting the color profiles. I copy pasted them straight from ffmpeg codec info output. Here's info on the I tested |
Now this is more like it! https://i.imgur.com/VGedp9D.png I chose a small 200MB file I had lying around and transcoded that using the UHD Disc preset setting and ensuring the thread option is set to optimal in the dropdown menu. Hm, which begs the question, why don't you just force it on optimal setting so the transcode always work as efficiently as possible if the other settings do jack all? hahaha.... |
Ahh.
Hmmmm, interesting..... So, I did another test and found out that setting the threads to "all" in the dropdown menu also pegs all cores and threads to 100%, then I changed the preset to something else, say your archive preset under UHD and notice that using the same "all" option for thread, it doesn't peg all the available CPU power you have, but hovers at around 50%....... Perhaps it's the encoder used to encode FFV1 isn't multithreaded, but the one used for x264 and x265 is.....? You can just take a look at the picture, I've commented it inside.... |
Optimize Preset The scaling options get complicated. Size I believe Widescreen videos should be scaled width first, height Full Screen should be scaled height first, width I may have to redesign how this all works to make it easier. Aspect Ratio If you're resizing, just use Size dropdown menu Format |
In the latest update, I added a Screen Format dropdown menu. Select if your video is Widescreen or Full Screen, and it will automatically set the Size width and height when you use a Size Preset like Maybe I will have it use the actual with instead of calculating it with auto. Use the Aspect Ratio menu if your input video ratio different that your output video's resolution. So if you're doing an input You can also use Aspect if you want to quickly change a video's ratio without having to re-encode, but it might give warning For Full Screen, if I scaled by width and used heigth If you want to discuss more about this, open a new issue and we can continue it there. |
Will Axiom have FFV1 support?
Also are there more advanced settings for denoising?
The text was updated successfully, but these errors were encountered: