0
0

Hi Folks,

I’m experiencing glitches when using the default transition method to go between themes.
I’ve set up a simple interactive music test in Designer, using default transitions. I have 3 cues/themes, one for low intensity combat music, one for medium, and one for high respectively. I have set the themes default transition properties to crossfade with a 0 ms fade. Each theme contains only one segment which in turn contains multiple audio files. The bpm and time signature is correct in all segments.
When i audition the above, about 7 times out of 10 i will experience an audible glitch when going between the themes. I have not tested this in-game, only in the audition console of Designer.
Is this a common problem? Is it a latency issue? Could it be down to my particular hardware? (even though i have tested it on 2 PCs, one being a powerful beast).

Also, is default transitions the most common (and recommended) method of going between various intensities of combat music. Or do most users prefer using a different method, such as a parameter? My goal is to achieve seamless stitching of music across the different intensity levels, rather than crossfading slowly between them.
I’ve tried the tutorials on the FMOD wiki, and as far as i can gather, i would not be able to use a parameter to ensure responsive changes of musical intensity unless i chop up the audio files into bar/beat chunks. Is this a correct assumption?

Thanks as always for your help.

Cheers,

Simon

  • You must to post comments
0
0

…just to add to the above. The audio files are perfectly edited, no gaps at the start or end. And they are uncompressed wavs, so no silence would have been added due to compression.

  • You must to post comments
0
0

[quote="slipperhero":1mmkakkx]…just to add to the above. The audio files are perfectly edited, no gaps at the start or end. And they are uncompressed wavs, so no silence would have been added due to compression.[/quote:1mmkakkx]

I’m having a little luck repro’ing your problem (I’m using mac with the latest version of designer). Is it a DC offset style glitch? Switching immediately between two signals (0ms crossfade) might be causing a DC glitch. Can you increase the crossfade to 5ms and see if that changes the number of errors?

cheers,
Templar

  • You must to post comments
0
0

It’s not a DC offset problem, I’ve ensured that all files are faded to O% at the start and end. I’ve tried changing the crossfade to 5, 10, 20, all the way up to 100ms, yet I still experience occasional glitches. To investigate further i captured FMOD’s output in Wavelab, and noticed that the glitches are in fact 30-50ms silent gaps. Note that this gap never occurs between files contained in a single segment, I can loop one segment (containing multiple audio files) all day long and it won’t glitch when it starts playback of a new audio file. It’s only when i transition between themes. Seems to me that once requested, the new theme takes a little while to get "kick started" into playback.

  • You must to post comments
0
0

I’d like to send you guys the project file and the associated audio files highlighting this problem, so you could take a look at it. Would that be ok? Where should i send it?

Simon

  • You must to post comments
0
0

Thanks for the report! This issue was due to the crossfade logic not handling crossfades correctly if they were too short. This has been fixed by making the fadein part of all crossfades happen 50ms sooner. This fix will be in the next release.

  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.