IBM-Cloud / openwhisk-darkvisionapp

Discover dark data in videos with IBM Watson and IBM Cloud Functions
Other
110 stars 257 forks source link

Audio Processing stuck #47

Closed lmcmanus1 closed 7 years ago

lmcmanus1 commented 7 years ago

After uploading a 30sec mp4 clip to my deployed Dark Vision app, it's getting stuck at 90% every time it tries processing audio - it's been stuck for 1hr+

Any known reasons?

screen shot 2017-03-13 at 17 27 01
l2fprod commented 7 years ago

It could be the Speech to Text callback not correctly registered.

1/ can you check the deployment pipeline log to make sure the Watson Speech to Text callback was correctly registered? Specially the log of the first DEPLOY. There should be a log showing "created" after the OpenWhisk header.

2/ look at the activation logs for the speechtotext action to make sure it was correctly triggered: wsk activation list speechtotext then look at the individual activations

3/ repeat with the textanalysis action

lmcmanus1 commented 7 years ago

Thanks for the quick response!

I just checked the pipeline deployment log and the callback failed - do you know how I go about correctly triggering it?

I don't have a dev/programming background so I'm running a little blind here. Any tips would be greatly appreciated!

Thanks

On 13 March 2017 at 19:01, Frederic Lavigne notifications@github.com wrote:

It could be the Speech to Text callback not correctly registered.

1/ can you check the deployment pipeline log to make sure the Watson Speech to Text callback was correctly registered? Specially the log of the first DEPLOY.

2/ look at the activation logs for the speechtotext action to make sure it was correctly triggered: wsk activation list speechtotext then look at the individual activations

3/ repeat with the textanalysis action

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/IBM-Bluemix/openwhisk-darkvisionapp/issues/47#issuecomment-286209615, or mute the thread https://github.com/notifications/unsubscribe-auth/AVSQKn9mX2bQFT1nai-H7AWKRaJIoL6gks5rlZJ_gaJpZM4Mbkum .

-- Luke McManus Human Digital @ M&C Saatchi 36 Golden Square London W1F 9EE

+44 (0) 7476 606 636 luke@human-digital.com marlen@human-digital.com www.human-digital.com

lmcmanus1 commented 7 years ago

Scratch that - I redeployed the pipeline and everything seems to be working now.

Thanks for your hard work in creating this app, the possibilities are really quite exciting.

On 14 March 2017 at 12:25, Luke McManus luke@human-digital.com wrote:

Thanks for the quick response!

I just checked the pipeline deployment log and the callback failed - do you know how I go about correctly triggering it?

I don't have a dev/programming background so I'm running a little blind here. Any tips would be greatly appreciated!

Thanks

On 13 March 2017 at 19:01, Frederic Lavigne notifications@github.com wrote:

It could be the Speech to Text callback not correctly registered.

1/ can you check the deployment pipeline log to make sure the Watson Speech to Text callback was correctly registered? Specially the log of the first DEPLOY.

2/ look at the activation logs for the speechtotext action to make sure it was correctly triggered: wsk activation list speechtotext then look at the individual activations

3/ repeat with the textanalysis action

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/IBM-Bluemix/openwhisk-darkvisionapp/issues/47#issuecomment-286209615, or mute the thread https://github.com/notifications/unsubscribe-auth/AVSQKn9mX2bQFT1nai-H7AWKRaJIoL6gks5rlZJ_gaJpZM4Mbkum .

-- Luke McManus Human Digital @ M&C Saatchi 36 Golden Square London W1F 9EE

+44 (0) 7476 606 636 <+44%207476%20606636> luke@human-digital.com marlen@human-digital.com www.human-digital.com

-- Luke McManus Human Digital @ M&C Saatchi 36 Golden Square London W1F 9EE

+44 (0) 7476 606 636 luke@human-digital.com marlen@human-digital.com www.human-digital.com

l2fprod commented 7 years ago

@lmcmanus1 what was the error with the callback in the log?