[Resolved] Does the current SDK support iOS6?

Home Forums OpenEars [Resolved] Does the current SDK support iOS6?

Viewing 10 posts - 1 through 10 (of 10 total)

  • Author
    Posts
  • #11526
    gregquinn
    Participant

    I’m getting a crash as soon as my app hears any sound – does the current SDK support iOS6? I have logging and verbose set, but all I’m seeing is lldb at ps_start_utt.

    #11527
    Halle Winkler
    Politepix

    Hmm, yes it definitely does. That kind of sounds like a missing acoustic model or a missing part of the acoustic model (meaning perhaps something going wrong when dragging the “Framework” folder into the app). Can you run the sample app in iOS6?

    #11528
    Halle Winkler
    Politepix

    To clarify — are you saying that with [OpenEarsLogging startOpenEarsLogging] and pocketsphinxController.verbosePocketSphinx = TRUE set you receive no logging at all up to the time of the crash?

    #11529
    gregquinn
    Participant

    Correct Halle; I basically imported the code from the sample into my viewcontroller code. the sample app runs fine. On googling, i see that the frameworks folder has to be added flattened out? (it seems to have symbolic linked folders) – how do i add the folder to my project?

    #11530
    Halle Winkler
    Politepix

    OK, it doesn’t actually have to be added in any particular way, however what’s important is that the entire Framework folder found at the root of the OpenEars distribution folder is dragged from the Finder into your project. That has to be the original Framework folder with the full contents in it that are found at the time of downloading the distribution. You can either add the contents as a reference or add them by copying, but if you add them as a reference, the folder has to stay where it was at the time the reference is added.

    #11531
    gregquinn
    Participant

    OK, working now – FYI, in case anyone else has a problem – I needed to add the files in hub4wsj_sc_8k out of that folder and directly into the project.
    Thanks for the fast responses Halle.

    #11532
    Halle Winkler
    Politepix

    No problem, glad it’s working for you.

    #11535
    Halle Winkler
    Politepix

    Having tested this again, I wanted to follow up that I can’t replicate an issue with adding the Framework folder itself as shown in the tutorial so I don’t think this issue is precisely that it is necessary to import that folder’s contents individually.

    It’s likely that re-importing the acoustic model files individually fixes something minor that has gone wrong a bit earlier in the process with the addition of that folder (for instance if the target was accidentally unchecked while adding or it was added as a reference and the reference was somehow problematic or became so later) so I strongly endorse gregquinn’s method described above as a troubleshooting step if you see a crash when listening starts.

    #11617
    Halle Winkler
    Politepix

    Hi Greg,

    I have the definitive answer to why this is sometimes happening — OpenEars requires that everything added to mainBundle is added at the root level (just because I don’t want to open up the can of worms of either trying to figure out at what level some crucial file is added, or forcing the developer to declare it for every file that the framework uses) and in the “add file” dialog in Xcode, if the option “Create folder references for any added folders” is selected, Xcode will create a folder inside the app’s mainBundle and put the files in there. So the acoustic model files were almost certainly in your app, but they probably couldn’t be found by the framework due to being in their own directory. I have improved the documentation to make sure this is clear and I appreciate your drawing my attention to the fact that it was a pitfall.

    #11618
    gregquinn
    Participant

    Great, thanks Halle.

Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.