Questions et réponses de la communauté

Bienvenue sur le forum de questions et réponses d'Audiokinetic, propulsé par la communauté. C'est l'endroit où les utilisateurs de Wwise et Strata s'entraident. Pour obtenir une aide directe de notre équipe, veuillez utiliser la page « Tickets de soutien ». Pour signaler un bug, utilisez l'option Bug Report dans l'Audiokinetic Launcher. (Veuillez noter que les rapports de bug soumis au forum questions-réponses seront rejetés. L'utilisation de notre système de rapport de bug dédié garantit que votre rapport est vu par les bonnes personnes et a les meilleures chances d'être corrigé.)

Pour obtenir rapidement les meilleures réponses, suivez ces conseils lorsque vous posez une question :

  • Soyez précis : qu'essayez-vous de réaliser ou quel est le problème spécifique que vous rencontrez ?
  • Pensez à inclure les détails importants : incluez des détails tels que les versions de Wwise et du moteur de jeu, le système d'exploitation, etc.
  • Expliquez ce que vous avez essayé de faire : indiquez aux autres les mesures que vous avez déjà prises pour essayer de résoudre le problème.
  • Concentrez-vous sur les faits : décrivez les aspects techniques de votre problème. Se concentrer sur le problème aide les autres personnes à trouver rapidement une solution.

Wwise Integration in Xcode

0 votes

Hello.

I'm currently trying to integrate Wwise into my learning project which is an iOS game made in Xcode.  I have a working game but in terms of Wwise Integration I have not been able to go really far. Following the Wwise SDK guidelines I have:

  • created an objc bridge header and checked that it works correctly;
  • imported required frameworks and updated search paths for SDK header files;
  • tried included Wwise SDK headers one by one.

Unfortunately the last step has not been successful. While the header files are found and being included, they fail to compile. There are multiple errors reported. Most of them point to AkTypes.h - I attach a screen shot of a log. The first error states that a constructor for AkExternalSourceInfo requires a specifier in addition to type name. The interesting part is the integration demo provided with the SDK does not have the issue. First I assumed the difference is in compiler settings, however I can't figure out what's wrong by straight comparison of my project with the sample one.

Any help is appreciated.

 

compile errors

dans General Discussion par Roman V. (140 points)

1 Réponse

0 votes

So far so good...

I expect those who know are not going to answer. However I already figured this out. The problem originates from including c++ headers into objc code which effectively means c++ code is sent to an objc compiler. I have switched to objc++ wrapper for the SDK.

I don't have this error any more but run into another one. Upon compilation I get a message about SDK files not containing definitions for the functions I try to use (the basic ones - memory manager, streaming manager initialization, and so on). The headers from include folder are found, so I suppose there is a problem with linking the libraries. If you read this and know what the problem might be, please let me know. For now I'm trying to figure this out on my own.

For those like me, who try to grasp this topic I have two tips:

  • do not try to integrate the SDK into swift application right away. Try first to have it working through C++. Then go for integration.
  • the SDK sample is very complicated. It's much better to start with Audiokitetic Integration Walkthrough page and implement only the basic functionality.
par Roman V. (140 points)
Adding up to my conclusions after cleaning up the project and starting the SDK integration from point aero:
- the SDK walkthrough is not complete, but with minor modifications I have finally managed to get Wwise initialized and accessible in swift;
- the configuration page states that for basic operation four libraries are required: memory manager, streaming manager, sound engineer and music engine, however I got an error related to the memory manager sinking for communication functionality.  Therefore communication library was required as well.
- the initialization page is clear enough, except the low level IO part and streaming device initialization which refers to the samples. And the latter contains a lot of interconnected files. For now I decided to skip this part. Hope it's just an advanced functionality that I do not need now.
par Roman V. (140 points)
Powered by Question2Answer
...