Size/Position Maximize: changed in MX?

terrypin wrote on 6/18/2012, 2:49 AM

Can others reproduce the following behaviour please, which only arises for me in MEP MX, not MEP 17.

Select an object, say a JPG. Using Movement > Size/Position create a KF at its start with a zoom of say 150. Then move the slider to its end and create another KF by clicking Maximize, which in all previous versions has been equivalent to entering 100 for that specific KF. But in MX that gets applied to all KFs. Removing all animation.

A deliberate change in the meaning of Maximize after all these years, or a bug?

--
Terry, East Grinstead, UK

Last changed by terrypin on 6/18/2012, 2:49 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.)

Comments

asoeli wrote on 6/18/2012, 8:31 AM

Hello Terry,

Yes, exactly the same happens here. MEP MX set all KF back to 100% with Maximize. But MEP 17 does not. ---- And MEP 16 is different.

Andreas

terrypin wrote on 6/18/2012, 8:53 AM

Thanks for confirming, Andreas.

And I've also found that the same thing happens with the Centre button.

It definitely seems like a bug to me. If we want to remove all size and positioning KFs, that is what the Reset button does!

--
Terry, East Grinstead, UK

Last changed by terrypin on 6/18/2012, 8:53 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.)

johnebaker wrote on 6/18/2012, 4:27 PM

Hi Terry

I occassionaly get this in both MEP 17 and MX - it appears to be related to the particular effect you are trying to change with keyframes.

I just repeat the first setting after the second and everything is OK

John

Last changed by johnebaker on 6/18/2012, 4:27 PM, changed a total of 2 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

terrypin wrote on 6/19/2012, 1:28 AM

Hi John,

Never happened for me in MEP17 or earlier. Same with Centre. It's a bug IMO, as neither of those buttons now has any sensible purpose in MX. They effectively do the same as Reset.

--
Terry, East Grinstead, UK

Last changed by terrypin on 6/19/2012, 1:28 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.)

johnebaker wrote on 6/19/2012, 12:09 PM

Hi Terry

The particular effect in 17 that is regularly did it with me was image rotation.

John

Last changed by johnebaker on 6/19/2012, 12:09 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

terrypin wrote on 6/20/2012, 9:28 AM

Reproduced by Magix Support.

This and the audio recorder 'jumping marker' bug slow my workflow down so much that I've reverted to MEP17. Unfortunately that gives me problems when exporting to HD MP4, so I'm hopping between the two versions.

--
Terry, East Grinstead, UK

 

Last changed by terrypin on 6/20/2012, 9:28 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.)