{"id":1340,"date":"2022-07-21T15:10:10","date_gmt":"2022-07-21T13:10:10","guid":{"rendered":"https:\/\/websites.fraunhofer.de\/video-dev\/?p=1340"},"modified":"2022-07-21T15:10:10","modified_gmt":"2022-07-21T13:10:10","slug":"talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs","status":"publish","type":"post","link":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/","title":{"rendered":"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs"},"content":{"rendered":"\n<p>Spoiler alert: What lies between <code>2<sup>37.58<\/sup><\/code> and <code>2<sup>37.59<\/sup><\/code> ? No, my cat did not walk over my keyboard and just entered some random numbers (I don&#8217;t even have a cat). Somewhere in between these two numbers lies a magical number. At least a magical number when debugging DASH streams on Samsung 2017 devices. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">I can&#8217;t hear you over the voices in my head<\/h2>\n\n\n\n<p>Ok, let&#8217;s wind back a bit. Quite recently one of our customer approached us with an odd problem. They produced a set of MPEG-DASH test streams for different platforms. On Samsung 2017 TV devices the unencrypted and the encrypted versions of these streams behaved differently when running in dash.js: For some reason there was no sound in the unencrypted version of the content. Isn&#8217;t this usually the other way around? Typically, something is not working in the encrypted content. Consequently, when we first heard about this we were a bit skeptical and started our tests. And what can we say? They are right!<\/p>\n\n\n\n<p>The issue is easy to reproduce. Simply take a stream from the DASH-IF Live simulator, for instance <a href=\"https:\/\/livesim.dashif.org\/livesim\/testpic_2s\/Manifest.mpd\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/livesim.dashif.org\/livesim\/testpic_2s\/Manifest.mpd<\/a>. Build a small Tizen application including dash.js, throw that stream on a Samsung 2017 and you will hear &#8230;. nothing! No sound at all, the video, however, is playing fine. Consequently, there has to be data in the audio SourceBuffer of the Media Source Extensions. Otherwise, playback wouldn&#8217;t start at all.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">206.879.537.681 is a magic number<\/h2>\n\n\n\n<p>At this point, we will spare you all the details about our first attempts comparing different codec profiles, levels and so on and get straight to the point: Our test devices don&#8217;t like large timestamps in the media segments. What do we consider large? Well, a number between  <code>2<sup>37.58<\/sup><\/code> and <code>2<sup>37.59<\/sup><\/code>, of course.<\/p>\n\n\n\n<p>Let&#8217;s dive a bit deeper into DASH terminology. The <code>MPD@availabilityStartTime<\/code> is the anchor time for dynamic media presentations (live streams). Typically, the presentation time zero maps to the wallclock time that is defined in  <code>MPD@availabilityStartTime<\/code>. Many packagers simply use the UNIX epoch <code>availabilityStartTime=\"1970-01-01T00:00:00Z\"<\/code><\/p>\n\n\n\n<p>That leads to high timestamps in the media segments depending on the <code>timescale<\/code> value. Taking the DASH-IF Live Simulator MPD from above we find a value such as <code>79603623840768<\/code> for the <code>baseMediaDecodeTime<\/code> of an audio segment in the <code>tfdt<\/code> box. This is precisely what seems to cause the problems on our Samsung 2017 device. Once the timestamps reach a certain value (between <code>2<sup>37.58<\/sup><\/code> and <code>2<sup>37.59<\/sup><\/code>) we don&#8217;t hear sound anymore.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Wait! I think I can hear something!<\/h2>\n\n\n\n<p>Now how can we fix this? There are basically two ways, a rather simple one and a complicated one. The simple one is to adjust the <code>MPD@availabilityStartTime<\/code> in our packager and let it produce segments with smaller timestamps. For the DASH-IF Live simulator we can simply add the target time to the URL, for example: <a href=\"https:\/\/livesim.dashif.org\/livesim\/ast_1658390879\/testpic_2s\/Manifest.mpd\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/livesim.dashif.org\/livesim\/ast_1658390879\/testpic_2s\/Manifest.mpd<\/a>. This leads to <code>availabilityStartTime=\"2022-07-21T08:07:58Z\"<\/code><\/p>\n\n\n\n<p>And voil\u00e0, we got sound again (at least for some time). The timestamps in the segments are much smaller now, for instance <code>865632256<\/code>. In general, the magic formula to find the right <code>MPD@availabilityStartTime<\/code> could look this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>App.prototype.generateUrl = function(threshold) {\n\tvar basicSourceFirstPart = 'https:\/\/livesim.dashif.org\/livesim\/';\n\tvar basicSourceLastPart = '\/testpic_2s\/Manifest.mpd';\n\tvar timescale = 48000;\n\tvar valueInSeconds = parseInt(threshold \/ timescale);\n\tvar now = parseInt(Date.now() \/ 1000);\n\tvar ast = Math.max(now-valueInSeconds, 0);\n\n\treturn basicSourceFirstPart + 'ast_' + ast + basicSourceLastPart;\n}<\/code><\/pre>\n\n\n\n<p>The <code>threshold<\/code> needs to be smaller than <code>2<sup>37.59<\/sup><\/code>, don&#8217;t forget to take the runtime of your content into account.<\/p>\n\n\n\n<p>For means of completion, let&#8217;s briefly discuss the other option to overcome this issue. In theory, we could keep <code>availabilityStartTime=\"1970-01-01T00:00:00Z\"<\/code> in our manifest and simply rewrite the timestamps in the media segments. However, by rewriting the timestamps we are also changing the position of the segments in the buffer. To account for this we can adjust the <code>@presentationTimeOffset<\/code> in the MPD. A client is positioning the media segment in the buffer the following way:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Sourcebuffer.timestampOffset = Period@start - MPD@presentationTimeOffset\nPosition in the buffer = Sourcebuffer.timestampOffset + Segment.baseMediaDecodeTime + Segment.compositionOffset<\/code><\/pre>\n\n\n\n<p>By setting the <code>@presentationTimeOffset<\/code> to a negative value we could shift the segments with lowered timestamps to their original position. However, this is just a theory we had, we did not confirm that this approach really works.<\/p>\n\n\n\n<p>That concludes our journey into the world of magic numbers and the fun that can be stream debugging. If you have any question regarding our DASH activities or dash.js in particular, feel free to check out our\u00a0<a href=\"https:\/\/www.fokus.fraunhofer.de\/go\/dash\">website<\/a>\u00a0and contact us.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Spoiler alert: What lies between 237.58 and 237.59 ? No, my cat did not walk over my keyboard and just entered some random numbers (I don&#8217;t even have a cat). Somewhere in between these two numbers lies a magical number&#8230;.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,4,2],"tags":[],"coauthors":[6],"class_list":["post-1340","post","type-post","status-publish","format-standard","hentry","category-dash-js","category-media-source-extensions","category-mpeg-dash"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs - Video-Dev<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs - Video-Dev\" \/>\n<meta property=\"og:description\" content=\"Spoiler alert: What lies between 237.58 and 237.59 ? No, my cat did not walk over my keyboard and just entered some random numbers (I don&#8217;t even have a cat). Somewhere in between these two numbers lies a magical number....\" \/>\n<meta property=\"og:url\" content=\"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/\" \/>\n<meta property=\"og:site_name\" content=\"Video-Dev\" \/>\n<meta property=\"article:published_time\" content=\"2022-07-21T13:10:10+00:00\" \/>\n<meta name=\"author\" content=\"Daniel Silhavy\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dsilhavy\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Silhavy\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\\\/\"},\"author\":{\"name\":\"Daniel Silhavy\",\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/#\\\/schema\\\/person\\\/f7e1eee3cb4eae87a59648195014a809\"},\"headline\":\"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs\",\"datePublished\":\"2022-07-21T13:10:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\\\/\"},\"wordCount\":695,\"commentCount\":0,\"articleSection\":[\"dash.js\",\"Media Source Extensions\",\"MPEG-DASH\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\\\/\",\"url\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\\\/\",\"name\":\"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs - Video-Dev\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/#website\"},\"datePublished\":\"2022-07-21T13:10:10+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/#\\\/schema\\\/person\\\/f7e1eee3cb4eae87a59648195014a809\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/#website\",\"url\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/\",\"name\":\"Video-Dev\",\"description\":\"Future Applications and Media - Video Development Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/#\\\/schema\\\/person\\\/f7e1eee3cb4eae87a59648195014a809\",\"name\":\"Daniel Silhavy\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/wp-content\\\/uploads\\\/2019\\\/11\\\/0-1-150x150.jpegccb13c1b60303228bf3c575f3345fe29\",\"url\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/wp-content\\\/uploads\\\/2019\\\/11\\\/0-1-150x150.jpeg\",\"contentUrl\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/wp-content\\\/uploads\\\/2019\\\/11\\\/0-1-150x150.jpeg\",\"caption\":\"Daniel Silhavy\"},\"description\":\"Daniel Silhavy studied Computer Science at the Technical University of Berlin (TUB). He received his Masters degree with the completion of his thesis \u201cAd Insertion in MPEG-DASH\u201d at Fraunhofer Institute for Open Communication Systems (FOKUS) in 2015. Currently, he is employed as a scientific assistant and project manager at the Business Unit Future Applications and Media (FAME). He specializes in the R&amp;D of topics dealing with IPTV and adaptive media streaming.\",\"sameAs\":[\"https:\\\/\\\/www.fokus.fraunhofer.de\\\/fame\\\/team\\\/silhavy\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/daniel-silhavy-21650a129\\\/\",\"https:\\\/\\\/x.com\\\/dsilhavy\"],\"url\":\"https:\\\/\\\/websites.fraunhofer.de\\\/video-dev\\\/author\\\/silhavy\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs - Video-Dev","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/","og_locale":"en_US","og_type":"article","og_title":"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs - Video-Dev","og_description":"Spoiler alert: What lies between 237.58 and 237.59 ? No, my cat did not walk over my keyboard and just entered some random numbers (I don&#8217;t even have a cat). Somewhere in between these two numbers lies a magical number....","og_url":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/","og_site_name":"Video-Dev","article_published_time":"2022-07-21T13:10:10+00:00","author":"Daniel Silhavy","twitter_card":"summary_large_image","twitter_creator":"@dsilhavy","twitter_misc":{"Written by":"Daniel Silhavy","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/#article","isPartOf":{"@id":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/"},"author":{"name":"Daniel Silhavy","@id":"https:\/\/websites.fraunhofer.de\/video-dev\/#\/schema\/person\/f7e1eee3cb4eae87a59648195014a809"},"headline":"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs","datePublished":"2022-07-21T13:10:10+00:00","mainEntityOfPage":{"@id":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/"},"wordCount":695,"commentCount":0,"articleSection":["dash.js","Media Source Extensions","MPEG-DASH"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/","url":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/","name":"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs - Video-Dev","isPartOf":{"@id":"https:\/\/websites.fraunhofer.de\/video-dev\/#website"},"datePublished":"2022-07-21T13:10:10+00:00","author":{"@id":"https:\/\/websites.fraunhofer.de\/video-dev\/#\/schema\/person\/f7e1eee3cb4eae87a59648195014a809"},"breadcrumb":{"@id":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/websites.fraunhofer.de\/video-dev\/talk-to-me-finding-the-magic-number-when-debugging-dash-streams-on-samsung-2017-smarttvs\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/websites.fraunhofer.de\/video-dev\/"},{"@type":"ListItem","position":2,"name":"Talk to me: Finding the magic number when debugging DASH streams on Samsung 2017 SmartTVs"}]},{"@type":"WebSite","@id":"https:\/\/websites.fraunhofer.de\/video-dev\/#website","url":"https:\/\/websites.fraunhofer.de\/video-dev\/","name":"Video-Dev","description":"Future Applications and Media - Video Development Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/websites.fraunhofer.de\/video-dev\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/websites.fraunhofer.de\/video-dev\/#\/schema\/person\/f7e1eee3cb4eae87a59648195014a809","name":"Daniel Silhavy","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-content\/uploads\/2019\/11\/0-1-150x150.jpegccb13c1b60303228bf3c575f3345fe29","url":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-content\/uploads\/2019\/11\/0-1-150x150.jpeg","contentUrl":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-content\/uploads\/2019\/11\/0-1-150x150.jpeg","caption":"Daniel Silhavy"},"description":"Daniel Silhavy studied Computer Science at the Technical University of Berlin (TUB). He received his Masters degree with the completion of his thesis \u201cAd Insertion in MPEG-DASH\u201d at Fraunhofer Institute for Open Communication Systems (FOKUS) in 2015. Currently, he is employed as a scientific assistant and project manager at the Business Unit Future Applications and Media (FAME). He specializes in the R&amp;D of topics dealing with IPTV and adaptive media streaming.","sameAs":["https:\/\/www.fokus.fraunhofer.de\/fame\/team\/silhavy","https:\/\/www.linkedin.com\/in\/daniel-silhavy-21650a129\/","https:\/\/x.com\/dsilhavy"],"url":"https:\/\/websites.fraunhofer.de\/video-dev\/author\/silhavy\/"}]}},"_links":{"self":[{"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/posts\/1340","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/comments?post=1340"}],"version-history":[{"count":11,"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/posts\/1340\/revisions"}],"predecessor-version":[{"id":1351,"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/posts\/1340\/revisions\/1351"}],"wp:attachment":[{"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/media?parent=1340"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/categories?post=1340"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/tags?post=1340"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/websites.fraunhofer.de\/video-dev\/wp-json\/wp\/v2\/coauthors?post=1340"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}