Audio Corruption when I CROSSFADE or use any video fades?

registry wrote on 12/30/2014, 8:06 AM

When I use ANY cross fade and there is audio crossfade the audio becomes distorted/damaged/corrupt...

I have an example file (about 20 seconds but dont see anywhere to upload to? So I have listed one below on YouTube as an example. With music in the audio its much worse.

This issue happens on all crossfades, whether one or everywhere in the video (on the audio track).

I use a Xeon 2.8 with at least 12gb ram, SDD for the drive too so there should be no issues there?

I use win 8.1

I use Movie Edit Pro 2015 Premium and this error is causing me to stop using the software... version 14.0.0.162

If you view this video:

and at 8:35 where I fade from one view to the next listen to the audio... its the SAME before I export too. If I dont crossfade then that does not happen and the audio sounds perfect on both parts.

The footage was recorded on a very high quality cinema camera and the audio is in HQ stereo on all of the used footage.

I have checked the PC many times over the last day and I'm about to throw Magix in the bin if this cant be resolved.

FYI this software used to run perfectly? Now it does not... I have repaired/reinstalled/etc. all day!

H E L P!

Back to post

Comments

browj2 wrote on 12/31/2014, 9:40 AM

@Terry,

I think that you missed the message way back where Tony posted 2 short raw mts clips. Those were the ones that I used in my reply.

@Tony,

What I meant by mixing down was only the audio. This is quite fast. Select the audio portion of the clip (I always have my audio show up on a second track), Edit, Compile audio, or Shft+D. I usually always normalize my audio portion as well (Alt+N). This replaces the original audio with a wave file, right at the same place on the timeline, and it's fast. The wave form also shows up much better.

Try this to see if it solves your problem.

BTW, the original audio is still available by right clicking on the video object, Audio functions, Restore original sound.

For my tutorials, I always end up with some original sound and a lot of added audio recorded directly into MEP. It is usually a dog's breakfast and I use the mixer, volume curves, etc to get the sound right, and then I export it all to a wave file, import it into Magix Audio & Music Lab, apply some effects, mostly the DeEsser, Gate to get rid of breathing between phrases, and a bit of reverb to give the sound some depth. Sometimes I have audio that I recorded onto one channel of a stereo file and I have to transform it into mono or get the sound on both channels. Since I use a reasonably good mic plugged into an external mixer, I don't pick up much background noise or hiss, unless the dog barks. Then I re-export to a wave file, import it into MEP, and mute all of the original audio. Then I realize that something was not quite right and I have to.......

Your published videos sound excellent, but the raw files that you uploaded are definitely not the same quality and would require some work, which is why I asked if you did some cleaning.

terrypin wrote on 12/31/2014, 9:54 AM

@Terry,

I think that you missed the message way back where Tony posted 2 short raw mts clips. Those were the ones that I used in my reply.

@John,

No, I saw those, although not until after I'd worked with the 500 MB file.

My point is that when you get an elusive issue like this which is obvious to you but not to others, then for productive discussion you need to package a complete project for others to reproduce. This will demonstrate the behaviour exactly as you are experiencing it yourself. The source files and the project configuration both become easily accessible for unambiguous analysis.

browj2 wrote on 1/1/2015, 11:44 AM

@Terry,

Point taken. We need all files including the MVP to properly test.

Have a Happy New Year!

@Tony,

How about all of the files as Terry asked? The MVP should have a cross-fade that gives the bad sound.

registry wrote on 1/7/2015, 10:53 AM

Heres the official line to this problem :(

Regarding your problem: Looks like we could replicate your issue here. It's similar to an issue we had before, but that was fixed in the previous version via an update. Your issue now seems to be specific to the source material you're using, which has PCM audio on AVCHD video. This is a possible combination (according to the AVCHD standard), but not very common with most cameras, which is probably why it hasn't come up yet. We will report this to development for their attention. Unfortunately, we cannot promise how soon this can be addressed and patched. We're currently about to test and release a new update, but this one doesn't seem to be able to handle these files at all any longer (import without sound). So, we will need to get on this matter either way. For the time being, I can only ask you to stick with your workaround solution of converting the files or extracting the audio prior to working with the material and editing the project. We hope for your understanding. Thanks again for the detailed and accurate problem description and the sample files. Appreciated.

Unfortunately Sony is a rather famous brand of camera and my model is absolutely industry standard (Sony NEX-FS100E) which is a professional video camera... and that makes me question the software not being able to support this format. BTW I tested the same footage with the far more expensive X version and that failed the test too.

So maybe Magix will fix this or not it seems :(

registry wrote on 1/8/2015, 7:33 AM

@Terry,

I think that you missed the message way back where Tony posted 2 short raw mts clips. Those were the ones that I used in my reply.

@John,

No, I saw those, although not until after I'd worked with the 500 MB file.

My point is that when you get an elusive issue like this which is obvious to you but not to others, then for productive discussion you need to package a complete project for others to reproduce. This will demonstrate the behaviour exactly as you are experiencing it yourself. The source files and the project configuration both become easily accessible for unambiguous analysis.

Thanks for your help with this problem, but I did not supply any such 'packaged' project to Magix. They simply used what I have previously posted and the problem seemed obvious. In fact, I could not even crossfade for 10th of a second without the issue being present :(

But thanks anyway.