# MediaReaderFLV.open: Metadata Appears to Be Bad **URL:** \ **Category:** Wowza Streaming Engine\ **Created:** [November 12, 2010, 9:45am UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848 "2010-11-12T09:45:35Z")\ **Posts on this page:** 9\ **Page:** 2
**Author:** ![Jake\_Hilton](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@Jake\_Hilton](https://community.wowza.com/u/Jake_Hilton)\ **Post date:** [September 7, 2011, 8:59am UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848/21 "2011-09-07T08:59:45Z")
Richard, I did attempt to use that model but it doesn’t preserve the path to the recorded file. So for example… if I have a path like so: parent/child/grandchild/video.flv… it renames the file like so: parent\_child\_grandchild\_video.flv. So I had to user a more granular approach and modify it for my needs. I’m using this approach: [https://www.wowza.com/docs/how-to-use-imediawriteractionnotify-to-programmatically-move-and-rename-recordings-of-live-streams](https://www.wowza.com/docs/how-to-use-imediawriteractionnotify-to-programmatically-move-and-rename-recordings-of-live-streams) I had hoped because I was using the s3fs caching with the s3 mount it would use the tmp location for all the file operations and only sync when the file was done being written… as it does for other file operations. Thanks, Jake ---
**Author:** ![Peter\_Braat](https://avatars.discourse-cdn.com/v4/letter/p/e68b1a/32.png) [@Peter\_Braat](https://community.wowza.com/u/Peter_Braat)\ **Post date:** [January 1, 2013, 10:12am UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848/22 "2013-01-01T10:12:15Z")
Hi yesterday morning this message suddenly popped up on a LIVE stream that had been going for years. Nothing was changed in the set-up. When I try to access it with the LiveVideoStreaming client from the first WOWZA server in the link (that picks it up from the camera), it plays fine, but the nect server in the link (the stream is sent there through PushPublish) started giving said error message. I’ve rebooted and restarted all machines, camera and servers but it did not help. The camera is an Axis P5532. What could cause this to suddenly start happening and how can it be resolved? Thanks. ---
**Author:** ![Julien\_Jabouin](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@Julien\_Jabouin](https://community.wowza.com/u/Julien_Jabouin)\ **Post date:** [July 9, 2011, 5:05pm UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848/23 "2011-07-09T17:05:16Z")
Hello, I had the same issue but with a .mp4 file : MediaReaderFLV.open: Metadata Appears to Be Bad: f513ba3e-fb74-102e-a4ca-001cc049c7f5.mp4 If i put mp4:xxxxx.mp4 it’s ok to see the file but why i need to add mp4: before the name of file ? If i look the log file before prefix by mp4: i had : rtmpe://xxxxxx/videos/f513ba3e-fb74-102e-a4ca-001cc049c7f5.mp4.flv and with the mp4: prefix i had : rtmpe://xxxxxx/videos/f513ba3e-fb74-102e-a4ca-001cc049c7f5.mp4.mp4 Thanks, Julien ---
**Author:** ![Robert\_Filipovich](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@Robert\_Filipovich](https://community.wowza.com/u/Robert_Filipovich)\ **Post date:** [December 13, 2012, 11:27am UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848/24 "2012-12-13T11:27:28Z")
I am getting this using the ModuleStreamControl when I play video files it all works fine, however when I try to switch a live stream into the stream point I get the met data is bad. Is there a way around this? I use a .stream file to call the point I want to bring in. It is h.264 encoded video but I do not know of a way to make a designation to use the mp4 in a live stream file. Any suggestions? Thanks ---
**Author:** ![Robert\_Filipovich](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@Robert\_Filipovich](https://community.wowza.com/u/Robert_Filipovich)\ **Post date:** [December 13, 2012, 12:16pm UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848/25 "2012-12-13T12:16:25Z")
You are correct. I made the change and stopped getting the error but the video is not playing, but no errors. Do I change the length value as well? I am using 0 and -1 for files and now -2 and -1 for live streams. Are there any considerations for where the live stream is published? Again no error now, but none at all either, just no video, but if you watch the stream directly that is being switched in, its there. Thanks ---
**Author:** ![Robert\_Filipovich](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@Robert\_Filipovich](https://community.wowza.com/u/Robert_Filipovich)\ **Post date:** [December 13, 2012, 2:21pm UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848/26 "2012-12-13T14:21:56Z")
I think I understand now. It appears that the live stream has to be in the app/appinst of the stream you want to switch into. Once I did that all worked fine, it was having an issue for some reason getting a stream from another app/appinst eventhough on the same server. Thanks ---
**Author:** ![Silas\_Silva](https://avatars.discourse-cdn.com/v4/letter/s/8c91f0/32.png) [@Silas\_Silva](https://community.wowza.com/u/Silas_Silva)\ **Post date:** [November 12, 2010, 10:13am UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848/27 "2010-11-12T10:13:32Z")
Work´s fine, but how can i discover what type FLV user video has been uploaded ? If FLV contain h.264 video i need used mp4 prefix. If mp3 I use flv prefix. There´s a away to do this automatic ? ---
**Author:** ![Roger\_Littin1](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@Roger\_Littin1](https://community.wowza.com/u/Roger_Littin1)\ **Post date:** [December 14, 2012, 7:03am UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848/28 "2012-12-14T07:03:22Z")
Hi, Can you open a ticket at support@wowza.com. Please provide steps to replicate. Zip up your conf & logs folders and if you are using a custom module can you include the relative src code for that. Please also include a link to here. Roger. ---
**Author:** ![Jeff\_King](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@Jeff\_King](https://community.wowza.com/u/Jeff_King)\ **Post date:** [June 24, 2013, 9:54am UTC](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848/29 "2013-06-24T09:54:16Z")
First of all, new user here, and I am grateful for any and all help. I have my server running, and I made the file MC.Stream in the content dir. The content of that file reads: rtsp://user:password@192.168.1.150:554/PSIA/Streaming/channels/h264 (local IP because I am testing in behind my firewall for now) I go to the Stream manager and start the live stream (I do have the application set up in the application dir) and I get this error: WARN server comment - MediaReaderFLV.open: Metadata appears to be bad: MC.Stream My camera does load its rtsp stream (only way to really connect to it) in VLC with this url: rtsp://user:password@192.168.1.150:554/PSIA/Streaming/channels/h264 I am kinda lost in this error… [Previous page](https://community.wowza.com/t/mediareaderflv-open-metadata-appears-to-be-bad/34848.md?page=1)