AMCDX Video Patcher v0.1.0 officially released.
The main update is Performance optimizations… Now decoder is almost x10 faster and encoder x5 faster. which allows decode and encode 4k content realtime even on 4 cores machines
Also added timecode display and Audio playback
Bugs fixed:
1) Crash on open file with alpha (files not supported yet but no crash)
2) Crash on Open file with a width which not aligned to 16
3) Audio bit depth detection
4) Crash when trying to open a file if edit “In Progress”
5) Show error message when attempted to open Mov file without prores content
Features:
1) Performance optimization (multithreaded ProRes decoding and encoding, realtime playback of 4K footage)
2) Audio playback
3) Show current frame / timecode during playback
4) Show name/path of current file
Whats next?
Next will be File to File insert eg:
1) insert one or more frames from one ProRes file to another
2) Insert Rectangle from (eg Picture in Picture)
Some files refuse to load/play:
– 8K files won’t play/show video
– MOV with 5.1 track won’t load
– MOV with HLG tagged ProRes won’t load
Thanks, Andrew,
Id love to check these files if you have chance to share…
5.1 is bug for sure I`m able to reproduce it
8K might should not be a problem, but the behavior described sounds like there is an alpha channel (its not supported yet)
anyway I`m down to check all files
Not sure if I can share precisely those I’ve tried, but I can make others which produce same behaviour.
that works
thanks
Hi
It’s all good (except one with 5.1 as you said).
8K problem was alpha related. I tried 444 and XQ without alpha and it worked fine (also HQ mode).
MOV with HLG tagged ProRes won’t load – it was DNxHR file not a ProRes 🙂
Speed wise there is something not right:
QT X =100
0.07 version = 200
0.1 version= 350
CPU usage on my Mac for HD playback.
that looks ok to me, basically, in v010 I added multithreaded decoding/encoding so all cores used during playback (even though for HD 1 thread should be enough)
Threads are busy but performance is crazy poor. Why do I need 4 cores for HD ?
What are they doing then?
thread needed for ui, thread needed for an audio renderer, threads needed for decoding, thread to read video/audio…
its complex. it technically could be optimized but I dont see yet if its really needed on current stage
Slow version 0.07 plays 3K ProRes on my laptop with no issue without maxing CPU load and new (x10 speed up version) maxes CPU and still unable to play same video?
Sorry, but where is this x10 speed gone? Sound like x10 slow down.
Audio decoding needs almost no resources (specially PCM), video rendering as well. 95% of whole CPU power need in a player goes typically to video decoding. Rest is/should be marginal.
Does it keep FPS? for me, 1 thread was enough to decode just ~20-25 HD frames eg not real-time.
I agree that maxing CPU not the best in payback case, but on File-to-file insert, or transcode it will be beneficial.
Anyway thats for the feedback I will check what can I do here
It was struggling with 3K playback on 4 core Mac.
Maybe problem is not with decoder itself, but whole playback path.
that might be audio related… if you share the file I can check,
but audio still a bit experimental.
I removed audio, still the same.
0.01 version 3K ProRes=450% CPU, no real time 30p playback
0.007 version = 200% CPU maybe 10fps
QT X = 140-200% CPU no problem with realtime playback
can I have that file? couple of frames will be enough.
or can you try v0.1.1
V0.1.1
Does not start on my Mojave:
QQmlApplicationEngine failed to load component
qrc:/main.qml:2 module “QtQuick.Controls” version 2.12 is not installed
logout
Saving session…
…copying shared history…
…saving history…truncating history files…
…completed.
Deleting expired sessions…55 completed.
oh sorry, I messed up wtih Qt versions 🙁
going to release new version this weekend with basic metadata editor
Metadata editor would be great.
I can help with testing.
Still working on new version?
yeah, I work on my project only on weekends, I started CLAP atom edit on sunday but there is too much UI work 🙁
Hi
Do it as cmd line. Way better than nothing.
v0.2.0
Looking good.
Just to make it “full” I think you should use all possible values for Color Matrix (regales if some one them are never used):
https://github.com/bbc/qtff-parameter-editor
Not sure if I understand how CLAP options work.
I like how JESExtensifier has it implemented:
https://video.informer.com/s1/mac/jes-extensifier/jes-extensifier.mp4
55 seconds in the video (you define PASP and cope values around edges)
Could you also add “old” gamma tag as it still can be useful (49 seconds in mentioned video).
What does “frame” setting change- first frame of ProRes private data or in whole stream?
1) JES allow only integer clap values when in reality it can be Rational represented as 2 integer values (numerator and denominator)
2) Yes I have plans to add/remove/edit gamma atom
3) frame meta changed for every single frame in the file
P.S. Andy, can you email to me alex(at)mogurenko.com