I can't believe I never noticed this in all the years I've been working in Ableton. When I export a looped section that loops perfectly fine during playback in the DAW, the export is not at the correct zero crossing when it should start and this wouldn't normally be an issue for full tracks but when composing for video games it becomes a serious issue because it creates a glitch/skip in the loop. Screenshot 1 is the project zoomed in at the start, midi/audio is at correct point. Screenshot 2 is how the master is rendered out which is clearly off. Even warping the rendered audio to fix it doesn't hold when bouncing that down again. Anyone else have similar issues? Any workarounds?

 

Nevermind, it seems this issue has been going on since Ableton had the option to render as mp3. Exporting in wav is fine

 

i never export as mp3, wave is fine and then if i need i simply export as mp3 with an audio editor.

Is this reproducible in Live Beta? then you can send a bug report on their centercode.

 

Upon further research I've discovered that this is in an issue in ANY DAW that renders to mp3 because of the nature within mp3 compression there is always a small gap within the render. I was never aware of this because in my work, I always render to wav. The client I'm composing for (a Video Game company) tried looping one of the demo mp3s I sent which exposed this issue so I was racking my brain thinking the issue was across both formats, lol. I also compose for sample pack companies and this never came up because all the loops/stems are bounced in wav. Being that any major project I work on requires lossless, I'm no longer concerned about this issue. But it is good knowledge for anyone not aware of this glitch.

 

didnt know. But i wonder, why extra converting creates this problem? I mean i thought its a serial processing, render to wav and then convert to FLAC, MP3, what you desire ...