Can't build for android/multi : cooker without Ogg support

I was building for android ALL and all cooking and packaging went fine.
then I’ve built for ETC1 and everything was alright too.
then I decided to built a 3-textures in one with Multi-set
and I’ve tried to build it about 3 times with restarts and etc
each time I had error with audio - ogg is not in compiler , something about cannot build None

LogAudioDerivedData:Warning: Could not find audio format to cook: None

Node ‘/Game/Assets/Sounds/Frontend_Slide_Stereo_Cue.Frontend_Slide_Stereo_Cue:
missing NodeGuid because of upgrade from old package version, this can cause deterministic cooking issues
please resave package.

LogAudio:Error: Attemped to select Ogg Vorbis encoding when the cooker is built without Ogg
Vorbis support.

then I decided to build ATC and PVRTC separately and it works again.

I think there’s some bug with “multi”, not sure where exactly.

Hey ,

  • Have you been able to replicate this on a new template within the engine?
  • Are there any specific reproduction steps that need to be complete before this error appears?
  • Could you please upload your full error output logs for comparison?


I was trying to build another game and it’s ok
I got some CUE Node Warnings
here’s logs [link text][1]

[link text][2]

88164-alphabet-backup-2016.04.23-22.41.13.log (72.4 KB)
[2]: 88165-alphabet.log (465 KB)

You should recheck your Sounds files/blueprints that you have in your project. It looks like you upgraded from an older version of the engine and it caused some trouble with the files.

Once you’ve done that, please upload full error logs again.

It would also be very helpful if you could provide me with full reproduction steps so I can test this out on a sample project here, or provide me with a sample project to review. If you choose to provide me with a sample project, upload it to something like Drive and provide the link to me through a private message on the forums.

Thanks! :slight_smile:

Hey ,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you!