0
0

Hi,

I have a question regarding a console problem in XCode 4 when using the iPhone simulator. The Xcode console stops logging data seemingly random but always in the middle of fmod log output. I’m not 100% sure whether this is an fmod issue, it might be a coincidence since fmod is rather verbose when it comes to logs. Only console output from the iPhone simulator is affected, the console output from an iOS device is functioning normally

Here’s a snippet of the console’s last words:
[code:d4g4q025]
...
FMOD: SystemI::createSoundInternal : filename = /Users/ronaldmannak/Library/Application Support/iPhone Simulator/4.3.2/Applications/8C5CDAC0-8401-4C06-A79D-9FE8EB3A6ABB/AirGuitar.app/menuArt/MainMenu.m4a : mode 000000c2
FMOD: SystemI::createSoundInternal : 17 codecs found. Scan all until one succeeds
FMOD: CodecTag::openInternal : attempting to open ID3 or ASF tags..
FMOD: Codec::release :
FMOD: Plugin::release : (0x574c600)
FMOD: Plugin::release : done
FMOD: Codec::release : done
FMOD: CodecFSB::openInternal : attempting to open as FSB..
FMOD: CodecFSB::openInternal : Header check failed. Not an FSB
FMOD: Codec::release :
FMOD: CodecFSB::closeInternal :
FMOD: CodecFSB::closeInternal : done
FMOD: Plugin::release : (0xc508c90)
FMOD: Plugin::release : done
FMOD: Codec::release : done
FMOD: CodecWav::openInternal : attempting to open as WAV..
FMOD: Codec::release :
FMOD: Plugin::release : (0xc508c90)
FMOD: Plugin::release : done
FMOD: Codec::release : done
FMOD: CodecOggVorbis::openInternal
[/code:d4g4q025]

After this, no output is shown in the console until I stop and restart the app.

Any suggestions are highly appreciated.

  • You must to post comments
0
0

Hi Mathew, Thanks for your help. Setting Debug_SetLevel to FMOD_DEBUG_LEVEL_WARNING seems to have solved the problem. Can it be that Xcode 4 chokes on a flood of fprintfs?

  • You must to post comments
0
0

This isn’t something I have see before, however we haven’t properly switched to Xcode 4 for development yet due to certain backwards compatibility implications.

As a test you could write an application that spews a lot of TTY output and see if it has the same result. Internally FMOD simply uses fprintf(stderr "foo") for all debug output, nothing special. Also you can control how verbose FMOD is via the Debug_SetLevel function.

  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.