-
Videoon 3/17/2023
FFMetrics -- Yet another program for quality metrics calculation
Version 1.3.2b published- Bugfix: High CPU/GPU utilisation caused by hidden Progress Bars with IsIndeterminate="True" (bugfix back-ported from 1.4.7b) Version 1.4.0b published- New: Added a new command line parameter "-exit" that works in conjunction with "-run"- Change: Updated components HarfBuzzSharp, SkiaSharp, SkiaSharp.HarfBuzz, SkiaSharp.Views.Desktop.Common and System.Memory- Bugfix: Fixed crash that could happen while processing short command line arguments Version 1.4.1b published- Change: Default LAVFI template changed from: [0:v]{{main}}[main];[1:v]{{ref}}[ref];[main][ref]{{filter}} to: [0:v]{{main-trim}},{{main-settb}},{{main-setpts}},{{main-scale}},{{main-setrange}},{{main-format}}[main];[1:v]{{ref-trim}},{{ref-settb}},{{ref-setpts}},{{ref-setrange}},{{ref-format}}[ref];[main][ref]{{filter}} All values in double curly brackets are substituted as required. Version 1.4.2b published- Change: Updated components: System.Drawing.Common (6.0.0 => 7.0.0), Newtonsoft.Json (13.0.1 => 13.0.2), OxyPlot.Core, OxyPlot.SkiaSharp, OxyPlot.SkiaSharp.Wpf, OxyPlot.Wpf, OxyPlot.Wpf.Shared (all Oxy*: 2.1.0 => 2.1.2)- Change: Changes to make sure that external program (ffmpeg.exe) is closed (possible fix for crash while extracting bad frames)- Bugix: For ffmpeg with in-build VMAF models option 'model=path=file.json' is used for external json models instead of old option 'model_path=file.json'. The old option claimed as deprecated, but in fact does not work at all (#107) Version 1.4.3b published- New: A number of bad frames that should be extracted can be configured in FFMetrics.conf (see FFMetrics.conf.example)- New: FFMpeg arguments for getting FFMpeg version info, checking VMAF models, getting media info, extracting bad frames and getting thumbnails can be defined in FFMetrics.conf (see FFMetrics.conf.example)- Change: Timeout for extracting bad frames increased to 30 seconds.- Change: FFMetrics.conf format is changed (see FFMetrics.conf.example) Version 1.4.3b2 published- Bugfix: Fixed bug with escaping FFMpeg command line parameters (introduced in 1.4.3b) Version 1.4.5b published- New: FFMpeg arguments for getting metrics can be defined in FFMetrics.conf (see FFMetrics.conf.example)- Change: -r <framerate> added before -i <filespec> to FFMpeg arguments while getting metrics (as per VMAF recommendation)- Change: TBR is used instead of FPS if available and not differ too much from FPS (should help with some VFR footage)- Bugfix: Skip was ignored when extracting bad frames- Bugfix: Project options were not always restored correctly on program startup Version 1.4.6b published- New: Click on metric column header order files by metric value (#98) Version 1.4.7b published- Bugfix: High CPU/GPU utilisation caused by hidden Progress Bars with IsIndeterminate="True" Version 1.4.8b published- Change: "Action | Show plots window" in menu should not be tickable option- Change: Updated component: Newtonsoft.Json (13.0.2 => 13.0.3)
-
Videoon 11/16/2022
AMD Adrenalin 22.11.1 - I feel sentenced!
We are always encouraged to update our graphics driver for a better performance. Ha-ha. You should never install driver as soon it is released unless you have an issue that was fixed in it.
-
Videoon 11/16/2022
AMD Adrenalin 22.11.1 - I feel sentenced!
But why install this non-WHQL and just released driver?
-
Videoon 11/7/2022
FFMetrics -- Yet another program for quality metrics calculation
While trimming before comparison with ffmpeg you should not forgot: 1. In most cases you will need to use "accurate trim" that require video stream decoding and so it is slow, especially if you trimming quite a lot; 2. In most cases re-encoding will occur so you should save as uncompressed/lossless (even slower, require a lot of disk space, you should be careful with colours); 3. In my experiments sometimes -ss before -i does not work as expected. This is the reason ffmetrics uses 'trim' instead that I've found more reliable. I'm not sure how hash/checksum can help as here we are not trying to find out if two files are exactly equal.
-
Videoon 11/4/2022
Vegas Pro 19.0 Completly different colours after rendering video
I've got "video is cyan after rendering" issue with RX6600 using AMD driver 22.8.2 in VP18 and VP19 (rendered with Magix AVC and Voukoder encoders). On timeline colours were fine. It was possible to render without the issue if I turn off GPU acceletarion in Preferences/Video. Changing anything on Preferences/File I/O was not fixed the issue. Upgraded to AMD driver 22.10.3 and the issue is gone.
-
Videoon 10/28/2022
FFMetrics -- Yet another program for quality metrics calculation
As a current workaround you can try to install avisynth and create a single .avs file for the ref to cut first 10 seconds. Then you can ask FFMetrics to skip first 10 seconds. That should be easier then trimming all files externally. However, there is always a trick: as the metrics require frame accutacy, you will need to find out your exact trim duration. As for implementation of your feature request -- unfortunately, adding this into UI will make the program much more complicated and as a "visual guy" who would like to keep the UI as simple as possible, I would like to avoid this. I will never add the skip options per "every distorted file". Sorry. I may consider separate skip durations (one for ref and another for _all_ distorted files), but will need to think about this. P.S. I do have a ticket on github for implementing auto-sync. This would be better approach that is also help in your situation.
-
Videoon 10/14/2022
FFMetrics -- Yet another program for quality metrics calculation
The latest beta (v1.3.1 beta 2) is released as v1.3.1 stable.
-
Videoon 9/12/2022
FFMetrics -- Yet another program for quality metrics calculation
Unfortunately, I cannot comment on different values. I was playing with ffmpeg5.0.x a little, but did not notice any metrics differences on my sources. Probably you need to run the ffmpeg commands manually (you can copy them from log) in console and double check results. I can only guess that the differences related to colour range (discussed earlier in the thread already) that version 5 is handling differently. As for vmaf model without file extension: you probably using the most recent version of ffmetrics that is detecting vmaf-models in-build into ffmpeg.exe. However, I have no idea why the values are different. They should be the same, unless VMAF developers modified these models. They were the same in my tests when I compared in-build models vs json models with ffmpeg5.0.x. P.S. For encoders comparison I'd use 'neg' vmaf-model. Do not remember if it is available for '4k'.
-
Videoon 7/3/2022
VEGAS Pro 19 Update 5 (Build 643)
What Magix has done with the simple overwriting of version 636 with 643 contradicts all basic rules of quality management and document control. +1 Another bad idea was to make saves within one version to be incompatible. I tried to update from 550 to 636 and all my settings reset so I rolled back straight away. Do not feel comfortable to try 643 as I'm in the middle of a few projects atm. Is it possible to disable notification about new version on Vegas startup?
-
Videoon 6/11/2022
Can VEGAS Upscale or Topaz Video Enhance AI make a better job of this?
When I compared last time upscalers 1-2 year ago (including the Topaz, but not the most recent version), the avisynth won. However, I used BlackmanResize resizer instead of Lanczos4Resize that gives slightly better results (on my taste). I tried my scripts (with tiny deshaking) and they provide results similar to yours. However, a bit hard to compare it directly as you applied CC. Not sure why you just stretched video. It does not make sense to me. Why not leave just black lined on sides? P.S. My player shows your video slightly squeezed comparing to original DV version. Not a dramma as it is for further editing.
-
Videoon 4/29/2022
FFMetrics -- Yet another program for quality metrics calculation
Version v1.2.0 beta 1 published - New: Libvmaf options that should be used for checking supported vmaf models can be defined (see "FFMetrics.conf.example") (#81) - New: Built-in ffmpeg vmaf models can be used (see "FFMetrics.conf.example") (#81) - Change: FFMetrics.conf format is changed. Case sensitive metric properties 'Filter' and 'Lavfi' must be used instead of 'LavfiTemplate' (see "FFMetrics.conf.example"). You need to adjust your FFMetrics.conf is you use one - Bugfix: Metric model property "default" was not correct parsed while using in FFMetrics.conf Version v1.2.1 beta 1 published - New: Temp dir can be specified in FFMetrics.conf (see "FFMetrics.conf.example") (#83) - New: FFMpeg colon escape characters can be specified in FFMetrics.conf (see "FFMetrics.conf.example") (#84) - Change: With command line parameter "-log-level=debug", option 'Write FFMpeg commands into log' is turned on automatically and disabled in UI (#82) - Change: model_path and log_path enclosed in single quotes separately
-
Videoon 4/14/2022
FFMetrics -- Yet another program for quality metrics calculation
Version 1.1.0 beta 1 published - New: OxyPlot library upgraded to version 2.1.0. Much faster renderer used (vital when many long files analyzed in one go)- New: Plots moved to separate window that opened manually or automatically when metrics calculation started. So more room for distorted files list that is handy for someone who do not care about graphs and only looking on per file metrics (#44)- New: Plots can be saved as SVG (smaller file size and better quality when upscaled)- New: Plots update frequency can be adjusted using menu: "Options" | "Plot update speed" or using command line parameter "-plot-update-speed=HIGH|NORMAL|LOW|OFF"- New: Plot line styles can be configured (see "FFMetrics.conf.example") (#71)- New: New project options "Auto-save results on completion" and "Results auto-save file" (#18)- New: A number of distorted files displayed in program main window title- New: New command line parameter "-temp-dir=C:\Path\To\Temp". The program will try to create the folder if required (#75)- New: Command line parameters can be specified in *nix style with double dash: "--param=value"- Change: Maximum number of distorted files increased from 12 to 24 by default. User may further increase it by manually configuring plot line styles (see "FFMetrics.conf.example") (#3)- Change: While extracting bad frames, program also extracts and save the same frames from reference file (#26)- Bugfix: Files are incorrectly updating on plots while re-ordering- Bugfix: Extracting bad frames is not accurate (#78)- Bugxif: Unable to drop file dragged from Windows Explorer to ref input (#77)- Bugfix: Crash while dragging item from distorted files list over blank Ref field (#79)
-
Videoon 3/8/2022
FFMetrics -- Yet another program for quality metrics calculation
You should not use the program like that. Take original file (from camcorder) and encode it twice -- with nvenc and with vouk. Then add original file into the program as ref and 2 encoded files and then calculate metrics. This way you will be able to say that encoder A with settings XYZ encoded better/worse than encoder B with settings ZYX
-
Videoon 3/8/2022
FFMetrics -- Yet another program for quality metrics calculation
Looks like a bug. Unfortunately, my current dev version is far ahead and there is no reason to investigate what was wrong with the version 1.0. Too many changes. Sorry. P.S. PM me if you're interested in testing new version.
-
Videoon 12/22/2021
VEGAS Pro 19 Build 458
Is it possible to TURN OFF the auto-resize crop/filters window? It is jumping all the time, hard to use for me. Thanks.
-
Videoon 11/30/2021
Best Upgrade Path To Take From Ryzen 7 1700 CPU For Vegas Pro 18
How much performance do you believe you’ve gained going from the R7 1700 to the R7 3700X overall, not just video editing? Sorry, my path was slightly different: Ryzen 1600 + AMD RX-470 => Ryzen 3700X + AMD RX-470 => Ryzen 3700X + AMD RX-580 When I upgraded CPU (having RX-470) I only got about 15-20% speed increase in render speed using Sony AVC/Mainconcept AVC/Magix AVC (CPU only). The biggest change was in NeatVideo (+80-120%) and HandBreak re-encoding (+90%). Unfortunately, I only measuring video editing related performance changes as this was my "bottleneck". I'm playing games a little, but do not have performance issues here. P.S. I can send you excel spreadsheet with my numbers if you like.
-
Videoon 11/30/2021
Best Upgrade Path To Take From Ryzen 7 1700 CPU For Vegas Pro 18
I'm not really understand what issue you are trying to fix (sorry, I have not read the whole thread). 80% CPU utilisation while rendering? This is normal! With 1700 or 5800 you will probably have about the same. BUT 5800 will do the job faster. IF your issue is preview performance (that is from my opinion is the most important thing) -- you should find out what causing it. May be your footage is quite hard to decode and the only options in this case would be re-encode/re-wrap OR use GPU/iGPU that support decoding of the footage. 1700 => 5800 will not help in this case at all. May be some filters. And it is possible they are only optimized for specific GPUs/CPUs. Let say Intel + NVidia so 1700 => 5800 will not improve things too much. So I'd start with providing your footage media info and used filters. P.S. I'm on RX580 + 3700X atm. Upgraded from 1700. But my footage -- 1080-60p, not 4K.
-
Videoon 11/22/2021
Want to save project assets from different drives onto one main drive
"Save your project w/assets" means: File | Save As | Choose new folder Tick "Copy media with project" checkbox at the bottom of the File Save dialog Save
-
Scriptingon 11/10/2021
Magic YUV on VP19?
Have you copied it from VP18 folder? It does not work if you copy it from VP17 folder, for example.
-
Videoon 11/9/2021
VP17/18 -- Scopes UI "flashing"?
VP19 build 424 still have the issue. 2+ years passed since it was introduced :)
-
Videoon 11/9/2021
Esc in Render As dialog -- strange behaviour
A bit sad that the tiny UI issue was not fixed in VP19 build 424
-
Videoon 11/3/2021
AVCHD files with VP17 and Win 7
Sorry, my bad. My footage -- m2ts with AC3 5.1/Stereo, not mts (files on camcorder are mts, but when I'm copying them to PC using manufacturer software they "converted" to m2ts).
-
Videoon 11/2/2021
AVCHD files with VP17 and Win 7
You need to disable so4 in VP17.
-
Videoon 10/26/2021
Vegas 19 generating .tmp files on C drive
Have you double checked with simple steps like adding sole media file onto timeline & rendering? If the issue is still there, have you reported the bug to Magix?
fifonik
Offline, Last login 3/21/2023, Member since 1/24/2018