Corrupted takes, washed-out and over-exposed

Rockie wrote on 2/11/2015, 12:04 PM

I have been working with Magix editing software since 2006.

Some months ago I installed MEP 2014 on this new computer and have completed a number of disc projects without any notable problems. Now I have just started a very big multi-track wildlife project and suddenly I have major software issues: the takes are all perfect in the timeline but when I shut down and restart the project, many but not all the clips become washed-out and over-exposed. If I click on the video object transparency handle of a washed-out clip, the exposure reverts temporarily to normal but jumps back to the problem as soon as I start playback. 


I have taken the actions recommended by Magix Support i.e. uninstalling a problematic Windows
update and re-installling the MAGIX software (including the download patch), shutting down
and restarting etc as well as resetting program settings to default. 

After the first start-up following the above actions, I was very disappointed to
find the corrupted clips still in the movie! I deleted them and reloaded those takes - all
fine and normal after that. So I carried on with project, shutting down and restarting a
couple of times to make sure that everything was remaining stable and okay.


However, on opening the project the next morning, I found the problem had returned to
many (but not all) of the new clips! The original set of takes I deleted and re-loaded into the movie is
still fine. I don't know if this is important info but it seems that takes loaded on tracks 1 - 4 are nearly all corrupted, while thus far takes loaded on tracks 5 - 12 have remained perfectly normal. I have also made sure that no video effects were added inadvertently. 

 Has anyone out there had this problem as well? Regretably it seems that Magix Support cannot assist any further. Need help guys, please. 

Computer info: HP ProDesk 490 G1 MT, Windows 7 Professional 64-bit, Intel i5-4570 CPU @ 3.20GHz, 8.00 GB RAM.  Magix Edit Pro 2014 version 13.0.5.4    

Comments

terrypin wrote on 2/11/2015, 2:33 PM

Hi,

I suspect this is going to be a tough one without getting our hands on an example.

Can you make a small, non-confidential project exhibiting the problem and use File > Backup > Copy project and media into a folder, zip it up and upload it to a host site (I use Dropbox for instance) so that we can see what you mean and maybe try to reproduce it.

BTW, when you refer to 'takes' I assume you mean imported video clips, and not as in 'Save objects as takes'. The Takes feature in MEP 2014 is very buggy.

--------------------

Also, when you had a correct-looking project on the timeline, did you try opening a new empty movie, copy/pasting the misbehaving one to it, deleting the original movie and resaving the project with a new name?

 

Last changed by terrypin on 2/11/2015, 2:37 PM, changed a total of 3 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 2/11/2015, 3:35 PM

Hi

Try setting the program back to its default settings - File, Settings, Reset program settings . . . .

John

Last changed by johnebaker on 2/11/2015, 3:59 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 24H2 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.

Scenestealer wrote on 2/11/2015, 3:53 PM

Hi

Is it just this project that exhibits the behaviour or can you reproduce it with other previous or new projects.

Can you find one of the automatic backups from the project folder for this project, that doesn't have the problem, and work from there after saving it with a new name?

Peter 

Last changed by Scenestealer on 2/11/2015, 3:53 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 2/23/2015, 3:52 AM

Hi,

12 days since what sounded like your rather urgent problem and 12 days since our suggestions. Did you solve the issue or just lose interest? Feedback is always appreciated.

Last changed by terrypin on 2/23/2015, 3:52 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.)