Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

0 votes

Hi All,

Description: I am experiencing the 'Segment look-ahead plus pre-entry duration is longer than previous segment in sequence' error on the profiler whenever a music transition with 0 bars designation gets played (Setup with the same post-exit and pre entry point as in lesson r in 201 course. The transition file lenght is about a second and music segment lenghts are 10-25 seconds. Transitions play between segments. 

Decreasing look-ahead time, as per the manual doesn't seem to fix it.

Only thing that seems to help if I disable the lookahead completely by setting it to 0, however, that doesn't seem like a good idea to me as it may introduce other issues.

At the moment I do not experience any audible errors but documentation says that this error can case music de-synchronisation.

Questions:

1. Has anybody experienced this error?

2. Is it something I should be worried about or or is it a harmless known issue?

3. Is setting lookahead to 0 a good idea or can it cause any issues?

in General Discussion by Pawel G. (170 points)

1 Answer

0 votes
Hi! Yes, getting the same error. Did you manage to get rid of it?
by Johan W. (140 points)
...