41 thoughts on “AMCDX VIDEO PATCHER V0.6.7”

  2. Alex,

    Thanks a lot for developing AMCDX. The application has been a time saving in several occasions where QuickTime video files were exported with the wrong color space tag for the web and Apple ecosystem devices, which starting with MacOS Catalina, requires, Rec.709 tag (1-1-1).

    BTW, how to identify within the application the current version I’m using? I couldn’t find this information where usually it’s located, “About this application” at the menu level.

    Is there a donation that can be made to support the development of the app?

    Thanks once again for the support and contribution.

    Reply

  3. Hey Alex,

    thank you very much for sharing your work with us. I come here from the Davinci Resolve forums, because I have the problem that Resolve, when exporting to an mxf Container is just not setting the pasp flag. I thought I can add it with your tool, but it seems I can only change Metadata that is already there and not add new ones. When I open a .mov container which contains pasp, I can change it with your tool. So basically it works, but as I said, if the mxf container is not having pasp set, I can not add it with your tool. Or did I miss an important button / menu? I am using your Windows build by the way.

    Reply

    1. you are right pasp was added only for MOV…
      I will add it to the features list

      Reply

  4. Hi Alex — Thank you SO much for making this app. It’s a very worthy replacement for JES Extensifier.

    I was wondering if it would be possible to add the ability to set the audio channel assignment descriptors in MOV files that contain PCM/WAV audio (it’s just an attribute that describes whether a channel is Mono, Left, Right, Center, LFE Screen, etc)

    This is a feature that Quicktime 7 has (via Window -> Show Movie Properties -> Audio Settings), yet *no* other app can do it. This essentially means it has become impossible to do on 64bit Macs.

    I’d be much obliged to send a donation your way if this is a function that could be added.

    Thank you so very much once again.

    Reply

  6. Hi Alex,

    I’m having an issue changing metadata on a .mxf file. When I try to chance the “coding equation” to ITU-R BT.709 it keeps resetting to “unknown” when I reload the file and I think it is this that is causing Adobe Media Encoder to read to file incorrectly and exports a washed out ProRes 422 file.

    Please let me know if there’s something I can do on my end to fix this or if you can apply a fix.

    Thank you.

    Reply

      1. Hi Alex,

        Unfortunately it’s a 1tb file, so I can’t share it. It’s a DNX 444 12bit 4K file .mxf

        I’m on PC and I need to export it to ProRes 422 HQ 4K via Adobe Media Encoder, but the levels are off and I always get a washed out export, so I was hoping changing the levels from Video to Full would solve the issue. Unfortunately it did not, so I’m now leaning to the fact that it’s missing the ITU-R BT.709 setting for quoting equation and that that is the reason Adobe is not able to export it correctly to ProRes 422 HQ.

        Let me know your thoughts. Thank you!

        Reply

          1. You mean export a few frames from the DNX 444 12bit right? Sure. I’ll do that today and upload to Google Drive and post the link. Thank you.

        2. I just checked the file you shared and yes I have a problem displaying correct coding equation, but it’s just UI bug. after Apply pressed correct meta applied and you can see it in media info

          Reply

          1. So technically, Adobe Media Encoder should be able to transcode the 444 12bit file into Prores 422 HQ without any issues right? I wonder why I am still getting a washed out file with incorrect levels. Ugh. 🙁

          2. Did you try to transcode to 444? it might be a chroma downsampling issue, as a second option try to change color range to Full and check if it helps

  7. Hi Alex,

    Do you mean transcoding to ProRes 444? No I haven’t tried that yet. I guess that might be a good workaround, though my deliverable would still end up being a 3rd transcode (DnX 444 Original – ProRes 444 to ProRes 422 HQ) Hopefully there will be minimal quality loss. Thanks for all your help.

    Reply

    1. hi Jack,

      what im trying to say is ProRes always YUV, but DNX444 might be RGB so when you transcode from DNx to ProRes there is a conversion from RGB to YUV applied. If you have incorrect metadata it might cause issues (for example you convert using rec709 matrices but display using bt2020) but it also might be just chroma downsampling issue.

      so I suggest you to try transcode to prores444 and check if it looks better. if it still looks wrong try to change the metadata of the result (prores file) file instead of trying to fix dnx file

      Kind Regards,
      Alex

      Reply

  8. Hi Alex,

    This is a great software, may ask specifically, I have a ProRes 4444 XQ that even though I am exporting as Full, the flag of the file is perceived as Video YUV, is there any way I can change the metadata using this tool?

    Thank you in Advance
    Nik

    Reply

    1. ProRes is always YUV and technically it can be full or video range but there is no real way to find out if the input was full or limited range.
      the encoder Apple delivers accepts RGB as input in this case RGB will be converted to YUV video range, but there is also possible to pass YUV as input in this case you can pass YUV full range. Im not sure what most NLEs do most probably they just do the simplest eg go RGB way.
      Nuke in V13.1 allows you to choose full or video range

      P.S. I’m sure only about Nuke 13.1

      Reply

  9. Hey, just wanted to say thanks for developing this tool. AS11 exports from Premiere have been broken for 4 years but the metadata editor here fixes the Coding Equations bug and gets it through quality control. Nice one!

    Reply

  10. Thank you for this software. We use it to replace JES Extensifier.

    Is there an option to remove the “tapt” atom? (track aperture)

    It’s necessary fo iTunes Packages.

    Reply

  11. Hi Alex.
    Thanks for your sofware. It could save my professional life 😀
    I have !!! to change the NCLC tag to 1-2-1.
    But none of your options in “transfer fonction” alows to get that.
    Could you add the possibility to just type the number we want in this field ?

    Cheers

    Reply

      1. Hello! I’m also looking for this answer. I don’t see an option to change the NCLC tagging from 1-1-1 to 1-2-1.
        Thanks!
        Anita

        Reply

          1. Dear Alex, what a fantastic tool! I can confirm that “Unspecified” (2) can not be correctly set with the GUI as it resolves to “Untagged”. Setting value 2 for “Unspecified” via the command line works as expected:

            ‘processor’: “mov_meta”,
            ‘params’: {
            ‘video_file’: qt,
            ‘headers_to_the_end’: True,
            ‘nclc’: {
            ‘in_file’: True,
            ‘primaries’: 1,
            ‘transfer’: 2,
            ‘matrix’: 1
            },
            ‘gama’: {
            ‘in_file’: True,
            ‘gamma’: 2.4
            }
            }

  12. Hi Alex,

    I’m back once again, still with the same issue regarding DNXHR 444 to Prores 422 HQ.

    One interesting find that may perhaps help resolve this:

    When I change the levels from “Video” to “Full” a program like Switch does indeed register the difference, even though media encoder still refuses to do so. I wonder if there is perhaps another bit of information somewhere in the metadata that is preventing adobe media encoder from seeing the DNXHR 444 as “video” levels once the change is made. Let me know if you think you might be able to resolve this puzzle.

    Thank you!

    Reply

    1. there are a million of possible cases, but its possible media encoder just converts video to full range. If you have. sample files with correct metadata eg files media encoder handle correctly I can compare meta

      Reply

      1. Sure, let me send you some small files, few seconds clips so that you can perhaps see what media encoder interprets correctly and what it doesn’t. Thanks!

        Reply

  13. I THINK I FOUND IT! (MAYBE… I HOPE)

    In MediaInfo I see “Active Format Description” listed as 15 in files with “limited” (video) levels and when rendered as “Full” levels, I see media info has “Active Format Description” listed as 0. So perhaps this is the key to get Adobe Media Encoder to recognize that the metadata has been edited in your program. Let me try and clarify as I know this might sound confusing:

    When I change the metadata with your program from “video” levels to “full” media info and other programs recognize the change, but media encoder still refuses to do so. That led me to believe that there must be some other bit of information that adobe is clinging onto, so perhaps it’s this “Active Format Description” value that is preventing media encoder from recognizing the right level values once they’ve been changed. I have no clue how hard it might be for you to try and find this string of metadata with your software so that we can try to change it from 15 to 0 and see if that does the trick.

    Hope you might have the time to do it. Thank you for all your help!

    Reply

    1. Nope… Never mind. Please ignore my last comment, I think that may just have had something to do with the version of Resolve I was exporting with before, as I just set it back to auto and the AFD was also 0, so my mistake. Still no clue what in the metadata is causing media encoder to ignore the change once it’s made with your software 🙁

      Reply

  16. Trying to change the Coding equation on an MXF file to pass QC, when I hit apply and re-import it doesn’t recognise that I’ve changed it. Is there an extra step I’m missing?

    Reply

    1. Might be a bug or maybe MXF has 2 headers with metadata. Hard to say without having problem file

      Reply

  17. Hello Alex!
    I’m actually looking for a solution with STILLS exported from Resolve and the difference (Gamma?) with what you see inside Resolve on the hero monitor
    Does your software handle this issue?
    Thanks a lot in advance for your work!!

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *