# Has the syntax for playing MP4 recordings changed without warning?

**URL:** https://community.wowza.com/t/has-the-syntax-for-playing-mp4-recordings-changed-without-warning/185
**Category:** Wowza Player
**Created:** [December 15, 2016, 10:12pm UTC](https://community.wowza.com/t/has-the-syntax-for-playing-mp4-recordings-changed-without-warning/185 "2016-12-15T22:12:43Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/system/32/447_2.png) [@system](https://community.wowza.com/u/system)
#### Post date: [December 15, 2016, 10:12pm UTC](https://community.wowza.com/t/has-the-syntax-for-playing-mp4-recordings-changed-without-warning/185/1 "2016-12-15T22:12:43Z")

</div>

I caused the problem below - I had a WowzaPlayer.createElement already in my HTML and I was dynamically creating one in javascript elsewhere, so they conflicted.

> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >

This one is a bit hard to understand. The syntax for playing a recordings is given as:

However, if I enter “sourceURL”:“https%3A%2F%2F%5Bwowza-ip-address%5D%3A1935%2Fvod%2Fmp4%3Asample.mp4%2Fplaylist.m3u8”,

the recording will not play. It worked a week ago.

But - and this is very strange - if I leave off “https%3A%2F%2F%5Bwowza-ip-address%5D%3A1935%2F” at the start and “%2Fplaylist.m3u8” at the end, it works - the player must have somehow cached my wowza-ip-address, or head office uses my [wowza-player-license-key] to get it from records.

Has anyone else encountered this?

Alan

---

<div class="post-metadata">

### Author: ![alan\_costello](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@alan\_costello](https://community.wowza.com/u/alan_costello)
#### Post date: [January 14, 2017, 12:02am UTC](https://community.wowza.com/t/has-the-syntax-for-playing-mp4-recordings-changed-without-warning/185/2 "2017-01-14T00:02:12Z")

</div>

I caused the problem myself - I had a WowzaPlayer.createElement({ etc }) already in my HTML and I was dynamically creating one in javascript elsewhere, so they conflicted.
