MEP2013 Color Correction: Buggy?

terrypin wrote on 12/6/2012, 4:03 PM

I must admit first that I have very little experience of using the Color Correction feature. But I've just been trying it and am getting very weird results. I'll amplify when I've done more testing, but so far I've had:

1. No selection occurring after following the instructions to the letter. This happened 10 minutes or so into the session within the dialog.

2. Unable to remove the 'Color correction' label in the object by any means (e.g, resetting in Color Correction itself, or Reset vide effects)

3. Corrupted display. (I'll capture it next time.)

4. Strangest of all, monitor displaying a previously used object! As if MEP's memory has been scrambled.

Restarted MEP but no change.

Anyone else seeing this sort of oddness?

--
Terry, East Grinstead, UK

Last changed by terrypin on 12/6/2012, 4:03 PM, changed a total of 1 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

Comments

terrypin wrote on 12/7/2012, 9:07 AM

Returned to this today. Definitely buggy IMO. Evidence:

 

 

I'm now worried that I'll never be able to use this again, if I can't get rid of whatever corruption has occurred!

Any feedback appreciated. Meanwhile I'm reporting it as a bug.

--
Terry, East Grinstead, UK

Last changed by terrypin on 12/7/2012, 9:07 AM, changed a total of 1 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

Scenestealer wrote on 12/7/2012, 3:40 PM

No problem here Terry!

Peter

Last changed by Scenestealer on 12/7/2012, 3:40 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

terrypin wrote on 12/8/2012, 5:23 AM

Hi Peter,

That's odd...

Did you play around with it as described?

Try these steps:

 

 

 

 

I also suspect it's complicated by the bug I identified in the following thread, because the behaviour seems to depend on the filenames and whether they've been inside MEP previously or not.

http://www.magix.info/uk/mep-17-mx-2013-sizing-display-bug.forum.883613.html

Did you also see my comments last night about this in my reply to you here?
http://www.magix.info/uk/green-screen-results-magix-v-paintshop-pro.forum.892818.html

--
Terry, East Grinstead, UK

Last changed by terrypin on 12/8/2012, 5:30 AM, changed a total of 2 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

terrypin wrote on 12/8/2012, 12:57 PM

All of that buggy/unstable behaviour disappeared when I changed Program Settings > Display options > Video mode from Standard (H/W Accel) to Alternative (Overlay Mixer).

The price I pay for this is that rendering takes about 25% longer. Although I suppose I could switch it back on just for that? And maybe there are other downsides?

--
Terry, East Grinstead, UK

Last changed by terrypin on 12/8/2012, 12:57 PM, changed a total of 1 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

Scenestealer wrote on 12/10/2012, 4:31 AM

Hi Terry

You sure seem to get some strange things happening.That switching out of H/W accel display mode makes me  wonder maybe that your system has a problem. Perhaps your graphics card has a fault - can you do some sort of torture test or swap it out and see if things improve. My 8800GT died a while ago but it was fairly sudden and obvious. GPU-Z has a ? button next to the PCI Bus Info window which starts a render test which cranks the card up to maximum. While it says it is not a stress test, it might show something.

I did see your comments in the other thread and have been doing a bit of testing following your step by step and I can not say I am getting display corruption but I do see the colour correction indication on the clip as soon as I select it which can not be removed by resetting. This is strange but I do not see it causing a problem and I also see it in MX. I did however start getting program lock ups after much fiddling around in CC and a couple of access violations in the ntdll.dll, but all this went away after a Windows restart.

The CC is actually more correctly called Secondary Colour Correction and using Add > Foreground creates a mask when a colour is selected with the pipette, which allows you adjust that area only, with the hue wheel. The grey area selected only becomes active when you adjust the wheel colour angle / level or the saturation. Once foreground is adjusted you can switch to background > add and adjust everything else to a different colour or black and white.

I had already considered your idea as to whether CC could be used to make your Greenscreen a better green and in fact it can even out the variation in shades by multiple selections with the pipette but I could not get any benefit in terms of creating a cleaner edge selction if the edge does not have a definite change in contrast/colour. I tested this in Chroma Key by using a jpeg of a Hue wheel where it fades from one hue and shade to the next. Actually it is well worth having a play with such an image in Chroma Key as it helps you to get a feel for what the sliders are doing. If you do the same with the SMPTE colour bar swatch in MEP you can get a different angle on it and see that with a defined edge the selection is very accurate even with the preview monitor zoomed 800% (Ctrl+Mousewheel).

I realised during this that my observation about the Chroma key selection being hit or miss was in fact nonsense, not realising that in CKey you have to drag over an area to select and a bounding box appears. Should have read the manual.....

Peter

 

 

 

Last changed by Scenestealer on 12/10/2012, 4:31 AM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

terrypin wrote on 12/10/2012, 2:50 PM

Hi Peter,

Thanks for the thorough testing, much appreciated. It's surprising that no one else can reproduce these problems. It could indeed be a graphics card problem but I'm inclined to doubt it as I get no problems in other graphics or video apps. And it does seem to be consistent with the other HWA-related problesm I've had, most of which Ralf has reproduced.

Although I gave my case innards a good air blasting a week or so ago, I suppose it could be a temperature problem, under intensive processing? I still can't remember what that tool was I used to use to check GPU temp, can you? I seem to remember you had the same utility? An unusual hotkey combination immediately displayed a full screen showing a 'carousel' of options. I've been scouring my HD but so far haven't found it!

If the only downside of unchecking the HWA video mode is 25% slower rendering, then for the time being at least I reckon I'll leave it like that and get on with some creative work!

Yes, I reckoned at the time that you'd made the same mistake as I did initially, and simply clicked the colour (which is what i do in PSP8) instead of dragging out a section.

I think I've now got the hang of the CC dialog, but IMO it sure is anything but obvious!

 

--
Terry, East Grinstead, UK

 

 

Last changed by terrypin on 12/10/2012, 2:50 PM, changed a total of 1 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

Scenestealer wrote on 12/10/2012, 3:29 PM

Hi Terry

It's a pleasure to be able to help and it always clarifies things in my own mind as well. Like the colour selection in Chromakey which is different to the click by click selection in CC!

Forget about that tool you are thinking of - it was an Nvidia thing and we both uninstalled it be cause it seemed to be causing problems. In my last reply I was talking about GPU-Z - free from TechPowerup. It is much better and you can do the test I mentioned as well as monitor in realtime on the sensors tab - GPU load, memory controller load, temp and fanspeed and a raft of other stuff. Interesting to observe it when HW rendering an export and you can see that Magix is using quite a lot of the graphics card resources.

Peter

Last changed by Scenestealer on 12/10/2012, 3:29 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

terrypin wrote on 12/18/2012, 12:34 PM

Feedback from Magix:

"The very specifics of the problem might be a little different due to this being related to HWA (where you could say that it might be in the very nature of the thing that it can be different from system to system) and obviously also due to the source material you are using and where exactly you are clicking. It is, however, pretty obvious to me that the cause of the problem between your problem and my problem is identical, with the selection of the intended colour via the mouse click apparently never yielding any selection for you at all and sometimes yielding no selection and somtimes yielding the wrong selection on my end, depending on where I click."

--
Terry, East Grinstead, UK

Last changed by terrypin on 12/18/2012, 12:34 PM, changed a total of 1 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)