-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this still being updated/supported? #52
Comments
Hi TheFloridaChannel, Thanks for posting! Yes, we do support Fire App Builder. What are your questions specifically? I see a single question about subtitles from you on GitHub. Please note that we review each request, but it's ultimately up to the Fire App Builder team to prioritize them, and decide whether to implement it or not, and when. In addition, this project is released as open source, so that you as a developer can modify and extend it if you wish to do so. Thank you for understanding. |
Levon,
Thank you for your email. My question specifically is why can’t we get valid CC side car files to render in FireApp builder. We’re supplying the correct path to valid files and none of the sidecar close captions work. Embedded 608 captions work but sidecar .VTTs don’t. I just have never received a response about this after numerous questions regarding this issue. There is just never any guidance to indicate what is wrong, or that it is acknowledged that this feature is not working as it should. I understand this is open source but your documentation states that .VTT closed captions are supported natively, and I cannot get them to work.
All of the code below is valid and they just never work. Is this a bug and if not, what is wrong with what I have in my recipe? I wish I didn’t have to resort to asking this question in many different places, but this has gone unaddressed for almost a year and I just want to know what to do if anything? Please advise. Is this a bug or not?
I
https://developer.amazon.com/docs/fire-app-builder/caption-support.html
Fire App Builder supports the same closed captions/subtitles that Exoplayer supports<https://google.github.io/ExoPlayer/supported-formats.html>. The formats include TTML, WebVTT, and CEA-608. The priority of support is as follows:
1. CEA-608 inband (if enabled — see below)
2. WebVTT and TTML outband
3. WebVTT and TTML inband
To enable inband CEA-608 closed captions, open Navigator.json (located in app > assets). In the config object, add "enableCEA608": true. Here's an example:
Recipe:
"cooker": "DynamicParser", "format": "xml", "model": "com.amazon.android.model.content.Content", "translator": "ContentTranslator", "modelType": "array", "query": "/feed/item", "matchList": [ "title/#cdata-section@mTitle", "contentId/#text@mId", "title/#cdata-section@mDescription", "media/streamUrl/#text@mUrl", "#attributes/hdImg@mCardImageUrl", "#attributes/hdImg@mBackgroundImageUrl", "contentId/#text@mChannelId", "srt@mCloseCaptionUrls" ]
<srt>
https://invintus-client-media.s3.amazonaws.com/2443575804/850b7fce2b2043f3bcf928e1551ae09c4a86afa8.vtt
</srt>
From: Levon [mailto:[email protected]]
Sent: Monday, October 7, 2019 5:52 PM
To: amzn/fire-app-builder <[email protected]>
Cc: TFC-Support <[email protected]>; Author <[email protected]>
Subject: Re: [amzn/fire-app-builder] Is this still being updated/supported? (#52)
Hi TheFloridaChannel,
Thanks for posting! Yes, we do support Fire App Builder. What are your questions specifically? I see a single question about subtitles from you on GitHub. Please note that we review each request, but it's ultimately up to the Fire App Builder team to prioritize them, and decide whether to implement it or not, and when. In addition, this project is released as open source, so that you as a developer can modify and extend it if you wish to do so. Thank you for understanding.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/amzn/fire-app-builder/issues/52?email_source=notifications&email_token=AGJKBO46HBRT3KG5PNYJBWTQNOVRBA5CNFSM4I6IQR32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAR5SMY*issuecomment-539220275__;Iw!5Xm4_O-4tfk!mfXJFjiIX3ByJ90I429WCMyy_Yg8ydCe_kCHzPLomnHbExezhWsQcm-objpYX0n2YLM$>, or mute the thread<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AGJKBOYWRD3OLVG6DE7XBQ3QNOVRBANCNFSM4I6IQR3Q__;!5Xm4_O-4tfk!mfXJFjiIX3ByJ90I429WCMyy_Yg8ydCe_kCHzPLomnHbExezhWsQcm-objpYUlABTcA$>.
|
Levon,
Has the team been able to review this item? Will I ever hear back about this?
Please advise.
From: TFC-Support
Sent: Tuesday, October 8, 2019 7:53 AM
To: amzn/fire-app-builder <[email protected]>; amzn/fire-app-builder <[email protected]>
Cc: TFC-Support <[email protected]>; Author <[email protected]>
Subject: RE: [amzn/fire-app-builder] Is this still being updated/supported? (#52)
Levon,
Thank you for your email. My question specifically is why can’t we get valid CC side car files to render in FireApp builder. We’re supplying the correct path to valid files and none of the sidecar close captions work. Embedded 608 captions work but sidecar .VTTs don’t. I just have never received a response about this after numerous questions regarding this issue. There is just never any guidance to indicate what is wrong, or that it is acknowledged that this feature is not working as it should. I understand this is open source but your documentation states that .VTT closed captions are supported natively, and I cannot get them to work.
All of the code below is valid and they just never work. Is this a bug and if not, what is wrong with what I have in my recipe? I wish I didn’t have to resort to asking this question in many different places, but this has gone unaddressed for almost a year and I just want to know what to do if anything? Please advise. Is this a bug or not?
I
https://developer.amazon.com/docs/fire-app-builder/caption-support.html
Fire App Builder supports the same closed captions/subtitles that Exoplayer supports<https://google.github.io/ExoPlayer/supported-formats.html>. The formats include TTML, WebVTT, and CEA-608. The priority of support is as follows:
1. CEA-608 inband (if enabled — see below)
2. WebVTT and TTML outband
3. WebVTT and TTML inband
To enable inband CEA-608 closed captions, open Navigator.json (located in app > assets). In the config object, add "enableCEA608": true. Here's an example:
Recipe:
"cooker": "DynamicParser", "format": "xml", "model": "com.amazon.android.model.content.Content", "translator": "ContentTranslator", "modelType": "array", "query": "/feed/item", "matchList": [ "title/#cdata-section@mTitle", "contentId/#text@mId", "title/#cdata-section@mDescription", "media/streamUrl/#text@mUrl", "#attributes/hdImg@mCardImageUrl", "#attributes/hdImg@mBackgroundImageUrl", "contentId/#text@mChannelId", "srt@mCloseCaptionUrls" ]
<srt>
https://invintus-client-media.s3.amazonaws.com/2443575804/850b7fce2b2043f3bcf928e1551ae09c4a86afa8.vtt
</srt>
From: Levon [mailto:[email protected]]
Sent: Monday, October 7, 2019 5:52 PM
To: amzn/fire-app-builder <[email protected]<mailto:[email protected]>>
Cc: TFC-Support <[email protected]<mailto:[email protected]>>; Author <[email protected]<mailto:[email protected]>>
Subject: Re: [amzn/fire-app-builder] Is this still being updated/supported? (#52)
Hi TheFloridaChannel,
Thanks for posting! Yes, we do support Fire App Builder. What are your questions specifically? I see a single question about subtitles from you on GitHub. Please note that we review each request, but it's ultimately up to the Fire App Builder team to prioritize them, and decide whether to implement it or not, and when. In addition, this project is released as open source, so that you as a developer can modify and extend it if you wish to do so. Thank you for understanding.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/amzn/fire-app-builder/issues/52?email_source=notifications&email_token=AGJKBO46HBRT3KG5PNYJBWTQNOVRBA5CNFSM4I6IQR32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAR5SMY*issuecomment-539220275__;Iw!5Xm4_O-4tfk!mfXJFjiIX3ByJ90I429WCMyy_Yg8ydCe_kCHzPLomnHbExezhWsQcm-objpYX0n2YLM$>, or mute the thread<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AGJKBOYWRD3OLVG6DE7XBQ3QNOVRBANCNFSM4I6IQR3Q__;!5Xm4_O-4tfk!mfXJFjiIX3ByJ90I429WCMyy_Yg8ydCe_kCHzPLomnHbExezhWsQcm-objpYUlABTcA$>.
|
Apologies but an update. We’ve tried both inband and outband VTT and neither work as expected. Can we at least just get a confirmation that: our recipe is deficient or this is an issue with Fire App Builder? Please?
Thank you
From: TFC-Support
Sent: Tuesday, October 8, 2019 7:53 AM
To: amzn/fire-app-builder <[email protected]>; amzn/fire-app-builder <[email protected]>
Cc: TFC-Support <[email protected]>; Author <[email protected]>
Subject: RE: [amzn/fire-app-builder] Is this still being updated/supported? (#52)
Levon,
Thank you for your email. My question specifically is why can’t we get valid CC side car files to render in FireApp builder. We’re supplying the correct path to valid files and none of the sidecar close captions work. Embedded 608 captions work but sidecar .VTTs don’t. I just have never received a response about this after numerous questions regarding this issue. There is just never any guidance to indicate what is wrong, or that it is acknowledged that this feature is not working as it should. I understand this is open source but your documentation states that .VTT closed captions are supported natively, and I cannot get them to work.
All of the code below is valid and they just never work. Is this a bug and if not, what is wrong with what I have in my recipe? I wish I didn’t have to resort to asking this question in many different places, but this has gone unaddressed for almost a year and I just want to know what to do if anything? Please advise. Is this a bug or not?
I
https://developer.amazon.com/docs/fire-app-builder/caption-support.html
Fire App Builder supports the same closed captions/subtitles that Exoplayer supports<https://google.github.io/ExoPlayer/supported-formats.html>. The formats include TTML, WebVTT, and CEA-608. The priority of support is as follows:
1. CEA-608 inband (if enabled — see below)
2. WebVTT and TTML outband
3. WebVTT and TTML inband
To enable inband CEA-608 closed captions, open Navigator.json (located in app > assets). In the config object, add "enableCEA608": true. Here's an example:
Recipe:
"cooker": "DynamicParser", "format": "xml", "model": "com.amazon.android.model.content.Content", "translator": "ContentTranslator", "modelType": "array", "query": "/feed/item", "matchList": [ "title/#cdata-section@mTitle", "contentId/#text@mId", "title/#cdata-section@mDescription", "media/streamUrl/#text@mUrl", "#attributes/hdImg@mCardImageUrl", "#attributes/hdImg@mBackgroundImageUrl", "contentId/#text@mChannelId", "srt@mCloseCaptionUrls" ]
<srt>
https://invintus-client-media.s3.amazonaws.com/2443575804/850b7fce2b2043f3bcf928e1551ae09c4a86afa8.vtt
</srt>
From: Levon [mailto:[email protected]]
Sent: Monday, October 7, 2019 5:52 PM
To: amzn/fire-app-builder <[email protected]<mailto:[email protected]>>
Cc: TFC-Support <[email protected]<mailto:[email protected]>>; Author <[email protected]<mailto:[email protected]>>
Subject: Re: [amzn/fire-app-builder] Is this still being updated/supported? (#52)
Hi TheFloridaChannel,
Thanks for posting! Yes, we do support Fire App Builder. What are your questions specifically? I see a single question about subtitles from you on GitHub. Please note that we review each request, but it's ultimately up to the Fire App Builder team to prioritize them, and decide whether to implement it or not, and when. In addition, this project is released as open source, so that you as a developer can modify and extend it if you wish to do so. Thank you for understanding.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/amzn/fire-app-builder/issues/52?email_source=notifications&email_token=AGJKBO46HBRT3KG5PNYJBWTQNOVRBA5CNFSM4I6IQR32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAR5SMY*issuecomment-539220275__;Iw!5Xm4_O-4tfk!mfXJFjiIX3ByJ90I429WCMyy_Yg8ydCe_kCHzPLomnHbExezhWsQcm-objpYX0n2YLM$>, or mute the thread<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AGJKBOYWRD3OLVG6DE7XBQ3QNOVRBANCNFSM4I6IQR3Q__;!5Xm4_O-4tfk!mfXJFjiIX3ByJ90I429WCMyy_Yg8ydCe_kCHzPLomnHbExezhWsQcm-objpYUlABTcA$>.
|
Just see a ton of open issues and my bosses are asking why we cannot launch our fire app. I have had tickets that remain open with the response that we should be looking for fixes in the next update. When is that going to happen? Does Amazon still support FireAppBuilder?
The text was updated successfully, but these errors were encountered: