I don’t think user properties has anything to do with that. Look at the error message

Warning: DVDOpen(): file ‘streams.fsb’ was not found under /.

Naturally that was the first thing that I checked. FMOD seems to be clever enough to check in the location of the fev for fsbs, although it checks the current directory first (I saw this in the documentation somewhere). Placing a copy of the fsb in the current directory I get:
[code:1dhzm9ft]FMOD: EventGroupI::loadEventDataInternal : m_flags: 00000002
FMOD: SoundBank::createStreamInstance : ev=0x9701ed30 evmode=0 mode=1572904
FMOD: SystemI::createSoundInternal : filename = streams.fsb : mode 001800aa
FMOD: SystemI::createSoundInternal : exinfo->cbsize = 108
FMOD: SystemI::createSoundInternal : exinfo->suggestedsoundtype = 8
FMOD: SystemI::createSoundInternal : 16 codecs found. Scan all until one succeeds
FMOD: CodecFSB::openInternal : attempting to open as FSB..
FMOD: Codec::release :
FMOD: CodecFSB::closeInternal :
FMOD: CodecFSB::closeInternal : done
FMOD: Plugin::release : (0x97027290)
FMOD: Plugin::release : done
FMOD: Codec::release :
FMOD: System::createSoundInternal : Fatal error (00000013) scanning the codecs. (ie not FMOD_ERR_FORMAT or FMOD_ERR_FILE_EOF)
FMOD: SoundBank::createStreamInstance : createSound failed 19[/code:1dhzm9ft]

That error is FMOD_ERR_FILE_BAD.

The FSB codec would return that, but it always prints out an error message describing why, and there is no such message in that log.
The only thing left I can see that would return that error is the low level file I/O routine, which means the disk is in a bad state.

You didnt say what platform you were talking about, but it looks like Wii due to the DVDOpen call. I can only recommend overriding the file routines yourself and determining why your dvd status is bad.

[quote:14aesi4f]You didnt say what platform you were talking about[/quote:14aesi4f]
Sorry, could have sworn I did.
[quote:14aesi4f]…but it looks like Wii due to the DVDOpen call.[/quote:14aesi4f]
Quite right.

Update:
I have now seen this failure on a different machine/devkit WITHOUT any user properties, so they are clearly not at fault, as you said.

[quote:14aesi4f]I can only recommend overriding the file routines yourself and determining why your dvd status is bad.[/quote:14aesi4f]
Will do, what fun. Thanks.

Fixed, using custom file IO functions.
Cheers Brett.