0
0

Transitions from one segment to another are sometimes not perfect. I’ve assembled the samples in my wave editor and they don’t have any gaps, but they do when played with fmod music player or in game. Original files are PCM waves.
Is that bank compression issue? What kind of compression should I use?

Another thing is also about segments.
Can I move to another segment before the one playing is over?
Sometimes I don’t want to wait till the segment is over, but just want to next link to go execute.
Or is there a way to go through connections (or links) on every beat or so?

Thanks!

  • You must to post comments
0
0

So just playing one segment after another isn’t possible? 😳

  • You must to post comments
0
0

[quote="jocorok":1miynnjm]So just playing one segment after another isn’t possible? :oops:[/quote:1miynnjm]

Sure it is, just connect the segments with a link to create a simple sequence – where one segment is played after the other has completed.

The complication comes when you want to leave a segment early (on cue) to progress to another segment. In this scenario, you need to use a default transition move between segments.

This will be covered in more detail in the user manual of the next release.

cheers,
Templar

  • You must to post comments
0
0

[quote="jocorok":21klbfqh]Transitions from one segment to another are sometimes not perfect. I’ve assembled the samples in my wave editor and they don’t have any gaps, but they do when played with fmod music player or in game. Original files are PCM waves.
Is that bank compression issue? What kind of compression should I use?[/quote:21klbfqh]

It could be a bank compression issue. You can test this by changing the compression to PCM and rebuilding – if the gaps are gone, it’s a compression issue. Also, testing with the audition console in Designer uses the source wave data, so if there are no gaps there, it’s probably a compression issue.

Another possibility is that you could have the segment tempos set incorrectly. The music system rounds the segment length to the nearest whole number of beats, which can introduce gaps – see http://52.88.2.202/forum/viewtopic.php?t=10189#37026 for a bit more explanation.

[quote="jocorok":21klbfqh]Another thing is also about segments.
Can I move to another segment before the one playing is over?
Sometimes I don’t want to wait till the segment is over, but just want to next link to go execute.
Or is there a way to go through connections (or links) on every beat or so?
[/quote:21klbfqh]

Currently there isn’t a way to follow a link before the current segment is finished, but we are planning to introduce transition points which will allow this. Look for this in a future release.

It is possible to exit a segment early via a crossfade default transition between themes. This requires that your source and destination segments are in different themes.

Ben

  • You must to post comments
0
0

Hey, thanks for the response.

The tempo caused the gaps, so after cutting files and changeing tempo it works well.
Howerver here comes another problem. Is there there a way the tempo wouldn’t affect how the segments are played?
It’s not that I don’t trust the FMOD’s BPM system, but we do have music wich tempo varies and i’d just like to play one segment after another.

  • You must to post comments
0
0

[quote="ben":1etb0svb]

It is possible to exit a segment early via a crossfade default transition between themes. This requires that your source and destination segments are in different themes.

Ben[/quote:1etb0svb]

How is this done? Our audio designer and I were attempting to achieve this via parameters, but nothing we did could force the immediate transition out of a segment. Since the granularity exposed to the engine seems to presently be limited to changing cues, we’d like a finer degree of granularity such that we can change themes in the middle of a segment at will.

Thanks for all your help and your quick replies!

  • You must to post comments
0
0

[quote="brussell":1vktgjtp][quote="ben":1vktgjtp]

It is possible to exit a segment early via a crossfade default transition between themes. This requires that your source and destination segments are in different themes.

Ben[/quote:1vktgjtp]

How is this done? Our audio designer and I were attempting to achieve this via parameters, but nothing we did could force the immediate transition out of a segment. Since the granularity exposed to the engine seems to presently be limited to changing cues, we’d like a finer degree of granularity such that we can change themes in the middle of a segment at will.

Thanks for all your help and your quick replies![/quote:1vktgjtp]

Take a look at:

http://52.88.2.202/files/transition-options.zip

Things to note:

  • This project demonstrates instant transitions, crossfaded transitions and transitions on selected beats.

  • Nearly all the transition logic is handled at the theme level using ‘default transitions’

  • All transitions are attached to prompts. Add all cues to the audition console. You should probably switch ‘sticky mode’ to off. Switching between ‘ones’ and ‘twos’ you’ll clearly hear the different transition styles.

  • Uses the new feature ‘shared timelines’. Using shared timelines you can synchronize playback of multiple segments along a single timeline.

If you have any other questions, please ask!

cheers,
Templar

  • You must to post comments
0
0

So then the only way to do it is to change cues from the engine? We’re a little reluctant at the moment about this, considering the somewhat awkward method of referencing cues (as I’m sure you’re aware – tying the asset pipeline to the code that heavily is inelegant for our project).

You say it’s handled at the theme level, but I can’t see how that could use parameter-driven transitions as opposed to code-driven cue changes.

  • You must to post comments
0
0

[quote="brussell":80umhhvn]So then the only way to do it is to change cues from the engine? We’re a little reluctant at the moment about this, considering the somewhat awkward method of referencing cues (as I’m sure you’re aware – tying the asset pipeline to the code that heavily is inelegant for our project).

You say it’s handled at the theme level, but I can’t see how that could use parameter-driven transitions as opposed to code-driven cue changes.[/quote:80umhhvn]

You’re correct about the default transitions not responding to parameter changes. At this point in time, the only way a segment can be exited before it has finished playing is through the use of default transitions. As Ben stated, transition points within a file have been considered for future release.

Have you thought about cutting the segment file up into smaller pieces and using a segment playlist? While it wouldn’t allow you to change segments instantly, it would certainly allow the music system to be far more responsive – it could possibly sound a little more musical too (I tend to think on beat transitions sound a little better than instant transitions).

cheers,
Templar

  • You must to post comments
0
0

[quote="brussell":1mma3ufa]So then the only way to do it is to change cues from the engine? We’re a little reluctant at the moment about this, considering the somewhat awkward method of referencing cues (as I’m sure you’re aware – tying the asset pipeline to the code that heavily is inelegant for our project).[/quote:1mma3ufa]

Yes, we’re aware that referencing cues and parameters can be somewhat awkward at the moment. We’re planning to add cue and parameter enumeration that only uses data loaded from the FEV (i.e. no header file or programmer report required) by mid-august.

Thanks,
Ben

  • You must to post comments
0
0

[quote="Templar":4irntnbz][quote="brussell":4irntnbz]So then the only way to do it is to change cues from the engine? We’re a little reluctant at the moment about this, considering the somewhat awkward method of referencing cues (as I’m sure you’re aware – tying the asset pipeline to the code that heavily is inelegant for our project).

You say it’s handled at the theme level, but I can’t see how that could use parameter-driven transitions as opposed to code-driven cue changes.[/quote:4irntnbz]

You’re correct about the default transitions not responding to parameter changes. At this point in time, the only way a segment can be exited before it has finished playing is through the use of default transitions. As Ben stated, transition points within a file have been considered for future release.

Have you thought about cutting the segment file up into smaller pieces and using a segment playlist? While it wouldn’t allow you to change segments instantly, it would certainly allow the music system to be far more responsive – it could possibly sound a little more musical too (I tend to think on beat transitions sound a little better than instant transitions).

cheers,
Templar[/quote:4irntnbz]

I apologize if I was misleading; transitioning on a beat is perfectly acceptable, as long as we’re talking about at an ‘arbitrary’ point in the sequence (not just the end). If I could evaluate a parameter on every beat and transition then, it would be helpful. Is this possible?

  • You must to post comments
0
0

[quote="brussell":3izxob52]
I apologize if I was misleading; transitioning on a beat is perfectly acceptable, as long as we’re talking about at an ‘arbitrary’ point in the sequence (not just the end). If I could evaluate a parameter on every beat and transition then, it would be helpful. Is this possible?[/quote:3izxob52]

Currently the only way to do it, is to cut the segment audio into smaller pieces (each beat), and use the segment playlist (in sequence mode) to recreate the whole piece. This means the link transition is considered at the end of each small piece (that represents a beat of the segment audio).

The bigproblem with this is all the extra work to cut up the audio…and you also lose the ability to use the segment playlist for more creative variation.

I’dd add the option to evaluate a the link on every selected beat as a feature request.

cheers,
Templar

  • You must to post comments
Showing 11 results
Your Answer

Please first to submit.