Critical: Placing 20 to 40 or more SongSync Devices at level will cause some SoundCue assets are not working within the project.

General Issues and Bug Reporting
, , ,
1

Summary

Placing 20 to 40 or more SongSync Devices at level will cause some SoundCue assets are not working within the project.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Audio

Steps to Reproduce

1, Create a new project.
2, Import a SoundWave (used .flac format).
3, Create a SoundCue from the SoundWave.
4, Place 40 or more Song Sync Devices in the level.

Expected Result

Even after placing over 40 Song Sync Devices, you can still:

  • Play the Sound Cue from Audio Player Devices during the session.
  • Preview playback of the Sound Cue in the Content Browser.

Observed Result

  • Playback of audio using the Sound Cue from the Audio Player Device becomes unavailable during the session.
  • The playback preview of the Sound Cue in the Content Browser stops functioning.

Platform(s)

Windows 11

Additional Notes

Based on my observations, the issue reproduces as follows:

  • The SoundCue asset cannot be previewed in the Content Browser.
  • If the Sound Cue is added to the Sequencer, it does not play.
  • There are SoundCue assets that are affected by this issue and others that are not. (It seems that this varies depending on the number of devices placed in the level.)
2

This issue is very critical because it makes it difficult to implement the MIDI usage patterns with SongSync within the game. For example, in a game that features a collection of mini-games, it would not be possible to have more than 40 players participating simultaneously on a single island using SongSync.(because it is necessary to manage the gameplay for each player with a dedicated SongSync)
Additionally, if we wanted to introduce more patterns that utilize SongSync within the mini-games, the number of players who can participate at once would significantly decrease.

3

@Flak Sorry for the mentioning.
But, This issue is so critical. Could you confirm?

4

The status of FORT-803497 incident has been moved from ‘In Testing’ to ‘Closed’. Resolution Reason: ‘Fixed’