Closed ram430 closed 1 month ago
After going to the bucket lma-aistack-XXXXXX-webappbucket-XXXXXX I could see that the extension file lma-chrome-extension-v0.2.4.zip is missing. It seems the current stack is not generating the extension file when updating an existing stack but I'm not sure about if the issue is also affecting brand new deployments.
I am experiencing the same issue mentioned above.
Thanks for reporting it.. I see we had a problem publishing the build to S3. The source code zip file referenced in the template is not in the S3 bucket, causing the browser extension CodeBuild run to fail.
I just re-published the release in the S3 buckets, and verified that another update resolved the issue..
Sorry for the inconvenience. Can you update your stack again and verify that all is well? Tx!
Thanks Bob!
Thanks Bob, appreciate for the quick support. So, for the latest build (v0.2.4), The extension feature is now working, it was breaking before. However, the zoom option is showing reduced performance with meeting session has not moved to the done state after complete the zoom meeting end. It is unable to accurately decipher who is speaking and mostly just tags every conversation to a single person. This wasn't always the case, when we tested it before, version number v0.2.2 - The zoom feature was working good.
Right now, I do not see the v0.2.2 version - could you share the build code for v0.2.2 version.
When we tried to pull v0.2.2 - artifacts are still pointing to v0.2.4, which means we are unable to deploy v0.2.2 version successfully.
We also noticed another issue with the extension: it seems that the transcription is only capturing conversations from one participant while missing contributions from all others. This functionality was working correctly in version 0.2.2. We are planning to onboard this feature into the client environment in the coming few days.
Hi @ram430
Right now, I do not see the v0.2.2 version - could you share the build code for v0.2.2 version.
Here's the URL for template version 0.2.2: https://aws-ml-blog-us-east-1.s3.us-east-1.amazonaws.com/artifacts/lma/lma-main.yaml?versionId=sojJYmfHIatahV3uKiD3TiD_XN3sanKn
However, the zoom option is showing reduced performance with meeting session has not moved to the done state after complete the zoom meeting end. It is unable to accurately decipher who is speaking and mostly just tags every conversation to a single person. This wasn't always the case, when we tested it before, version number v0.2.2 - The zoom feature was working good.
I just tried a zoom call myself where I joined as a second speaker from my phone, but could not replicate this, alas.
Some possibilities:
We have a known issue outstanding - see https://github.com/aws-samples/amazon-transcribe-live-meeting-assistant/issues/116 - it was reported for the virtual participant (not the browser extension) but quite possibly it affects both. Can you check if this could be your issue.
Another possibility is that it is related to Issue #130 / PR #132 - the PR was for the Virtual Participant only - not the browser extension, so it wouldn't have introduced an issue for you, but could be that you are affected by the same problem?
It could also be that the Zoom web app DOM has changed in a way that breaks the browser extension. Also please check if it is related to other aspects of the Zoom meeting itself.. i.e. if video sharing is on/off, screen sharing on/off, chat window displayed, or not. Use the Chrome developer tools to try to troubleshoot the extension and see if you can narrow it down.
ASK: Please open a new Issue for this issue since it's unrelated to the original issue. Include all the steps to reproduce, screenshots if they help, and the details of any troubleshooting steps.
We also noticed another issue with the extension: it seems that the transcription is only capturing conversations from one participant while missing contributions from all others.
I cannot repro this one either, unfortunately. ASK: Please open another new Issue for this issue since it too seems unrelated to the previous. Include all the steps to reproduce, screenshots if they help, and the details of any troubleshooting steps.
Thank you, @rstrahan, for the quick support and for providing the requested template and also addressing all the encountered issues. I will close this issue now and open a new one if we face any further problems.
Is your feature request related to a problem? Please describe. Yes
Describe the solution you'd like As previous version v0.2.2 has working expected with chrome extension, while latest release extension throwing exception and not able to download the new version extension. while hitting the ICON it's routing to the app directly without downloading the extension zip.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.