Announcement

Collapse
No announcement yet.

Primary Color Correction in Edius 9 bug.

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • #16
    Interesting. I need to check (after my vacation) I don't use PCC much I prefer YCbCr tools.
    Pawel Chyrowski

    Edius 9 Workgroup

    Writer/Director. Director of Photography. Motion Picture and Sound Editor. Colorist.

    https://facebook.com/chyrowski
    https://www.youtube.com/c/PawelChyrowski
    https://vimeo.com/pawelchyrowski

    Comment


    • #17
      'morning Grass Valley!

      Already some insight in the PCC anomaly? If it is a bug, will it be dealt with in 9.5?
      Nicola
      defacto.media
      www.defacto.media
      __________________

      Win10 SSD || Intel(R) Core(TM) i7-6820HQ || Intel(R) HD Graphics 530 / NVIDIA Quadro M2000M || 64 GB RAM || Edius 10 WG

      Comment


      • #18
        Originally posted by antonsvideo
        ....if I reduce blue, it will alter the remaining values

        or maybe it is the other way and 9 has a bug
        Anton, this would be not really an issue. But the problem is, when you change the value and slide it back to the original position, you will notice that every slider is on a different position than it had before.
        I therefore conclude that the algorithm that handles the relation of each slider to each other has a bug.
        Nicola
        defacto.media
        www.defacto.media
        __________________

        Win10 SSD || Intel(R) Core(TM) i7-6820HQ || Intel(R) HD Graphics 530 / NVIDIA Quadro M2000M || 64 GB RAM || Edius 10 WG

        Comment


        • #19
          Originally posted by nictau
          Anton, this would be not really an issue. But the problem is, when you change the value and slide it back to the original position, you will notice that every slider is on a different position than it had before.
          I therefore conclude that the algorithm that handles the relation of each slider to each other has a bug.
          I tend to agree with you that it is either an undocumented feature or a bug
          Anton Strauss
          Antons Video Productions - Sydney

          EDIUS X WG with BM Mini Monitor 4k and BM Mini Recorder, Gigabyte X299 UD4 Pro, Intel Core i9 9960X 16 Core, 32 Threads @ 4.3Ghz, Corsair Water Cooling, Gigabyte RTX-2070 Super 3X 8GB Video Card, Samsung 860 Pro 512GB SSD for System, 8TB Samsung Raid0 SSD for Video, 2 Pioneer BDR-209 Blu-ray/DVD burners, Hotswap Bay for 3.5" Sata and 2.5" SSD, Phanteks Enthoo Pro XL Tower, Corsair 32GB DDR4 Ram, Win10 Pro

          Comment


          • #20
            Originally posted by antonsvideo
            I tend to agree with you that it is either an undocumented feature or a bug
            Hi Anton:
            1) I now understand what nictau meant and can confirm this strange behaviour:


            2) If you set one slider, e.g. red, to a certain new value (precisely via numeric input) and then return to the previous value of red, the previous values for green and blue are no longer correct.


            3) I therefore agree with your opinion.
            BTW: I especially like the phrase "undocumented feature".

            // Sounds much more friendly than "bug" :-)


            Gruss kurt
            HW: ASUS Z170-A; Proz: i7-6700K; RAM: 32 GB DDR4; GPU: RTX-3070, 8GB GDDR5; SSD: SAMSUNG-850-Pro, 500 GB
            SW: WIN-10/64 PRO (22H2-19045-2364​​), Firefox u.a.
            NLE: EDIUS-X(10.34.11471)-WG​​​; RESOLVE-18.6.00006 Studio
            // Read > Test > Understand

            Comment


            • #21
              I am wondering how you experts tell the precise colour from EDIUS interface? I certainly cannot. That's why I prefer to generate a precise LUT from outside EDIUS first - then load that into PCC.
              TingSern
              --------------------------------------
              Edius 10 WG, Lenovo P72 workstation laptop, 64GB RAM, Xeon CPU, Windows 11 Pro (64 bits), 2 x 2TB Samsung M2.NVME and 1 x 4TB Samsung SSD internal. Panasonic UX180 camera, Blackmagic 4K Pocket Cinema

              Comment


              • #22
                Originally posted by tingsern
                I am wondering how you experts tell the precise colour from EDIUS interface? I certainly cannot. That's why I prefer to generate a precise LUT from outside EDIUS first - then load that into PCC.
                Hi:
                1) I am not an expert in the sense that you might mean it.
                2) I have used the words "precisely" and "numeric" only to describe how to test the problem by oneself.
                // But I will try to improve my English further (its not my native language).
                Regards kurt
                HW: ASUS Z170-A; Proz: i7-6700K; RAM: 32 GB DDR4; GPU: RTX-3070, 8GB GDDR5; SSD: SAMSUNG-850-Pro, 500 GB
                SW: WIN-10/64 PRO (22H2-19045-2364​​), Firefox u.a.
                NLE: EDIUS-X(10.34.11471)-WG​​​; RESOLVE-18.6.00006 Studio
                // Read > Test > Understand

                Comment


                • #23
                  Guys, this is completly normal nad logic. If you move eg. RED you always adding or removing the Luma (Y). In RGB you alwyas have connected Chroma (RGB) values with Luma (Y). That's why you alwyes adding Saturation when you modifing the Luma. If you want to separate this thing use 3-wheel or YUV Curve (YCbCr tools).

                  Of course you can do this in Davinci (separate Y and RGB), but this tool is mostly use RGB not YUV ( YCbCr native video color model).
                  Pawel Chyrowski

                  Edius 9 Workgroup

                  Writer/Director. Director of Photography. Motion Picture and Sound Editor. Colorist.

                  https://facebook.com/chyrowski
                  https://www.youtube.com/c/PawelChyrowski
                  https://vimeo.com/pawelchyrowski

                  Comment


                  • #24
                    Hi All who are interested:

                    We got a feedback from Japan (in summary):

                    The reported error with the sliders in the primary color correction is being worked on.
                    Probably with 9.5 comes the change.


                    Regards kurt
                    Last edited by kpot; 06-18-2019, 11:22 PM.
                    HW: ASUS Z170-A; Proz: i7-6700K; RAM: 32 GB DDR4; GPU: RTX-3070, 8GB GDDR5; SSD: SAMSUNG-850-Pro, 500 GB
                    SW: WIN-10/64 PRO (22H2-19045-2364​​), Firefox u.a.
                    NLE: EDIUS-X(10.34.11471)-WG​​​; RESOLVE-18.6.00006 Studio
                    // Read > Test > Understand

                    Comment


                    • #25
                      Originally posted by kpot
                      Hi All who are interested:

                      We got a feedback from Japan (in summary):

                      The reported error with the sliders in the primary color correction is being worked on.
                      Probably with 9.5 comes the change.


                      Regards kurt
                      Thanks Kurt.
                      Nicola
                      defacto.media
                      www.defacto.media
                      __________________

                      Win10 SSD || Intel(R) Core(TM) i7-6820HQ || Intel(R) HD Graphics 530 / NVIDIA Quadro M2000M || 64 GB RAM || Edius 10 WG

                      Comment


                      • #26
                        Originally posted by nictau
                        Thanks Kurt.

                        I had asked Mr. Lehmann-Horn (from MMM in Munich) to try to clarify your question - bug or no bug.
                        So the thanks are due to him and his team.
                        // I pressed only the button to start the rocket ;-)
                        Regards kurt
                        HW: ASUS Z170-A; Proz: i7-6700K; RAM: 32 GB DDR4; GPU: RTX-3070, 8GB GDDR5; SSD: SAMSUNG-850-Pro, 500 GB
                        SW: WIN-10/64 PRO (22H2-19045-2364​​), Firefox u.a.
                        NLE: EDIUS-X(10.34.11471)-WG​​​; RESOLVE-18.6.00006 Studio
                        // Read > Test > Understand

                        Comment


                        • #27
                          Hi nictau:


                          I have tested Version-4.0(5106):
                          The above problem seems solved!


                          // I think your (our ;-) ) problem has disappeared with the new build.?
                          Regards kurt
                          HW: ASUS Z170-A; Proz: i7-6700K; RAM: 32 GB DDR4; GPU: RTX-3070, 8GB GDDR5; SSD: SAMSUNG-850-Pro, 500 GB
                          SW: WIN-10/64 PRO (22H2-19045-2364​​), Firefox u.a.
                          NLE: EDIUS-X(10.34.11471)-WG​​​; RESOLVE-18.6.00006 Studio
                          // Read > Test > Understand

                          Comment


                          • #28
                            Originally posted by kpot
                            Hi nictau:


                            I have tested Version-4.0(5106):
                            The above problem seems solved!


                            // I think your (our ;-) ) problem has disappeared with the new build.?
                            Regards kurt
                            Yes, it has in deed. For me the most important fix in the new update.
                            Greetings.
                            Nicola
                            Nicola
                            defacto.media
                            www.defacto.media
                            __________________

                            Win10 SSD || Intel(R) Core(TM) i7-6820HQ || Intel(R) HD Graphics 530 / NVIDIA Quadro M2000M || 64 GB RAM || Edius 10 WG

                            Comment

                            Working...
                            X
                            😀
                            🥰
                            🤢
                            😎
                            😡
                            👍
                            👎