nrbrook

Forum Replies Created

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

  • Author
    Posts
  • in reply to: Recognition lag #1023545
    nrbrook
    Participant

    Ok thanks.

    in reply to: Recognition lag #1023498
    nrbrook
    Participant

    The error I initially reported in the first post could suggest the problem.

    in reply to: Recognition lag #1023497
    nrbrook
    Participant

    Yes, I would recommend adding a warning or error for the threshold bounds as you said elsewhere the default was 1.5 and lowering it would reduce the noise threshold, which is what I was trying as it wouldn’t recognise back.

    in reply to: Recognition lag #1023494
    nrbrook
    Participant

    I am not sure what the difference is there, but I have changed it.

    So if you take the new project, drag in rejecto, import it, and change the language model generation line to

    NSError *error = [languageModelGenerator generateRejectingLanguageModelFromArray:@[@"BACK",@"NEXT",@"REPEAT"] withFilesNamed:@"FirstOpenEarsDynamicLanguageModel" withOptionalExclusions:nil usingVowelsOnly:NO withWeight:nil forAcousticModelAtPath:[OEAcousticModel pathToModel:@"AcousticModelEnglish"]];

    It rarely recognises ‘back’

    in reply to: Recognition lag #1023490
    nrbrook
    Participant

    It would only not be valid if rejecto generates different files each time?

    in reply to: Recognition lag #1023489
    nrbrook
    Participant

    Ok, so if you adjust vadThreshold my other problem is ‘BACK’ is very rarely recognised. It worked much more often in v1 of the framework.

    I’m not sure how rejecto is being used in an unsupported way as in the sample it just creates the same files on-the-fly that I am using in the edited version? It’s just not generating them every time.

    in reply to: Recognition lag #1023444
    nrbrook
    Participant

    I have a sample App which exhibits the problem, where should I send it?

    in reply to: [Resolved] Missing notifications in 2.0 #1023441
    nrbrook
    Participant

    You could just check on delegate set if the delegate implements the removed methods and log a warning.

    in reply to: [Resolved] Missing notifications in 2.0 #1023439
    nrbrook
    Participant

    You can do

    – (void) method __deprecated;

    But it doesn’t display a warning, so it isn’t much use…

    http://stackoverflow.com/questions/11432452/attribute-deprecated-does-not-work-on-objective-c-protocol-methods

    in reply to: [Resolved] Missing notifications in 2.0 #1023437
    nrbrook
    Participant

    Ah, my mistake, I thought it still existed in the protocol.

    in reply to: Recognition lag #1023431
    nrbrook
    Participant

    I replaced them again with the versions from the archive, I’m still getting the message 25 seconds after I start listening, every time.

    Step 1 and 2 are replacing the bundles and frameworks. I’ve definitely done this.

    Step 5 is architectural changes. The pocketsphinx usage I have changed, I’m not generating a language model. I am using OEEventsObserver correctly.

    Thanks

    in reply to: Recognition lag #1023429
    nrbrook
    Participant

    Which steps? I have followed all the steps and apart from step 1, step 2 and step 5 the project would not compile if I had not made the changes successfully

    in reply to: [Resolved] Language mode generator + rejecto not working #1023411
    nrbrook
    Participant

    Ok thanks. If I have a static language model do I still require the rejecto plugin in my project which uses that language model?

    in reply to: [Resolved] Language mode generator + rejecto not working #1023409
    nrbrook
    Participant

    Ok, thanks, however now the same code outputs:

    Dynamic language generator completed successfully, you can find your new files (null)
    and
    (null)
    at the paths
    (null)
    and
    (null)

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