bhf3737 said:
HarryFilm said:
Here is a screenshot of the Windows, iOS, MacOS, Android and Linux CODEC control program which can be run in almost ANY video editor, video player and transcoder application that is Windows Direct-X/Apple/Linux/iOS/Android compatible (i.e. BM Resolve, Adobe CC, Corel Video Studio, Vegas, Avid, Lightworks, FCP-Pro, AVI-Synth, Virtual Dub).
[...]
The screenshot does not prove anything. I can make it with a mockup tool in less than 10min and a more beautiful and functional one, too. The screenshot you provided actually indicates that you don't know simple principle of hierarchical design. Who puts ALL options ON THE SAME SCREEN and CLUTTERS the view? Now I UNDERSTAND why your testing is taking so much time. If you want to TEST it (combinatorial testing) as it is it would take close to infinite time to TRULY TEST IT ALL.
And by the way, in your screenshot there was no option to load an image or video file!!
Anyway, your screenshot does not show that there is actually a working program behind it that could possibly accept a user's settings and produce something good using the in-camera processing resources.
And let's make it easier for you: if your supposed program (codec whatever) runs on any of those OS flavors mentioned, forget the in camera processing and release the code for skeptic users to just run it on their computer and check whether it can encode/decode/transcode a sample MXF or MP4 file recorded by a camera. If you do that a skeptic user can find that there is actually something going on in your claim.
---
The user interface is a simple control system. It's NOT MEANT to be pretty!
The CODEC is meant FOR THE CAMERA...the menu system just controls it outside of a camera. The load imagery (media files) button is on another screen - I was just showing you what options ARE AVAILABLE!
And combinatorial system testing IS A NO BRAINER...I have a four GPU system,
it takes MERE MINUTES to do all the combinations of PIXEL TYPES, resolutions, bit rate and pixel depth.
My Testing of codec itself IS NOT THE ISSUE...the codec works fine!
It's the hook into Canon's onboard Camera BIOS that is the issue!
I am having the SAME ISSUES that Magic Lantern had. You can BRICK
a camera if you put a BIOS hook in the wrong place in the Microcode.
My codec is useless if it can't get loaded onto the camera properly
and hook into the right microcode addresses ... and EACH MODEL
is different ESPECIALLY the 1Dx/1Dc and C100/C200/C300/C500/C700
series which are the MOST problematic. on the higher end models,
you normally have to send them into Canon to get bios upgrades.
I have figured out a more gentle method to upload a bios addition
in those higher end models.