Printable View
Going through the Mezzmo Device Profile list does not show SMP-N200 from Sony. It shows the N100 unit but not the 200. The N100 profuile only allows for one type of transcoding. The N200 is more divers in it's format recognition. I would like a N200 Profile or equivelant. I would Like to transcode to the same format as the other devices read MP4 or MKV...something like that.
Currently I'm having trouble reading MPEG2-TS files.. they stutter baddly on stream... but play fine on the server.
The N100 device profile does supports many video/music/image formats. For video, it supports mpeg-2, mpegts and avi. For video transcoding, it does prefer mpegts.
The N200 manual says the it does not support WMV, AVCHD or MP4 via DLNA streaming.
Please tell us the FFmpeg information for the file that is stuttering. To do this, right-click on the file in Mezzmo and click 'Get FFmpeg Information'.
Here is the FFmpeg info you requested. This is for one file, but all mpeg2-ts files stutter.
ffmpeg version N-36036-ga40f43d, Copyright (c) 2000-2011 the FFmpeg developers
built on Dec 22 2011 13:44:49 with gcc 4.6.2
configuration: --enable-memalign-hack --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32- --enable-static --disable-shared --enable-zlib --disable-postproc --prefix=/media/ffmpeg --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect --extra-cflags=-I/home/dennis/cc/include --extra-ldflags=-L/home/dennis/cc/lib --pkg-config=pkg-config --disable-w32threads
libavutil 51. 32. 0 / 51. 32. 0
libavcodec 53. 46. 1 / 53. 46. 1
libavformat 53. 27. 0 / 53. 27. 0
libavdevice 53. 4. 0 / 53. 4. 0
libavfilter 2. 53. 0 / 2. 53. 0
libswscale 2. 1. 0 / 2. 1. 0
[mpeg2video @ 030ba720] mpeg_decode_postinit() failure
Last message repeated 1 times
[mp1 @ 030c7240] Header missing
[mpeg2video @ 030ba720] mpeg_decode_postinit() failure
Last message repeated 3 times
[mp1 @ 030c7240] Header missing
[mpeg2video @ 030ba720] mpeg_decode_postinit() failure
Last message repeated 2 times
[mp1 @ 030c7240] Header missing
Last message repeated 35 times
[mpegts @ 01ff8860] max_analyze_duration 5000000 reached at 5024000
[NULL @ 030c7240] start time is not set in estimate_timings_from_pts
[NULL @ 030cd580] start time is not set in estimate_timings_from_pts
Input #0, mpegts, from 'I:\TV\Two and a Half Men-(Palmdale, Ech)-2012-03-19-0.tp':
Duration: 00:34:57.27, start: 9307.616033, bitrate: 14937 kb/s
Program 1
Stream #0:0[0x31]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 17652 kb/s, 31.44 fps, 29.97 tbr, 90k tbn, 59.94 tbc
Stream #0:1[0x34](eng): Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), s16, 384 kb/s
Stream #0:2[0x35](spa): Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, mono, s16, 96 kb/s
Stream #0:3[0x110]: Audio: mp1 ([6][0][0][0] / 0x0006), 0 channels, s16
Stream #0:4[0x111]: Unknown: none (TVG1 / 0x31475654)
At least one output file must be specified
---> DB Level Info: 4, 4
---> Frame rate: 31.44
---> Aspect ratio: 16:9
You stated that Sony says the N200 does not play MP4. Mine plays MP4 h264 beatuifully through Mezzmo as well as any other server i've streamed it from. but this isn't about MP4. just trying to get the TV shows I'm recording to be watchable streaming. My DVR software is recording in mpeg2ts and it's causing me fits. :)
Thanks for your help.
Thanks for the information. I think we need to see a set of logs to know exactly what is happening. In Mezzmo, go to the Transcoding Settings dialog and delete all your transcoded files. Next, please enable logging (see this thread: http://forum.conceiva.com/showthread...nostic-logging) then start your Mezzmo server and connect to Mezzmo from your N200 and stream a mpegts file. Then, stop your Mezzmo server, zip up all the logs and send them us at support [at] conceiva [dot] com.
Thank you for your help.
I am not sure how to "zip up" the logs. Some help there would be apreciated.
I am also no convinced the problem is with the Mezzmo software.
My network is run by a Ubee wireless b/g router. Now, I'm a newb and don't know much about networking but it is my very limited understanding that MP2TS files are a higher bitrate than MP4 files. It would seem that MP2TS files would therefore be more demanding on the network bandwidth than MP4 format. It would seem then that the b/g wireless router could be "choking" the MP2TS streams. I am going to setup an N wireless network this afternoon and see if there is any change in MP2TS stream performance
Further evidence of this theory is that I get the same MP2TS stuttering on playback on both of the front end media devices of different manufacture, the Sony N200 and the Samsung BD-C6500. Aswell the stuttering problem described occured on MP2TS streams on all streams recorded in that format as well as on any and all backend server programs I have thus far tried. also, when streaming the MP2TS files to the front end devices I can pause the stuttering file and resume the playback and it will play smoothly flawlessly for 5-12 seconds and then resume stuttering. The length of pausing the playback does effect the length of smooth playback to a degree, but the maximum length of smooth playback achieved this way has been 15 seconds pausing for 3-5 mins, longer lengths of pausing did not yield longer periods of smooth playback.
All that said, the stuttering files play flawlessly on the server computer. I am going to change wireless routers from the b/g to the b/g/n router today possibly using a bonded channel for the server to the router. I will also get you the logs you requested. But I have a sneaking suspicion it's the router. ;)
"Zip up" means compress them into an archive so they are easier & smaller to email to us. I'd suggest downloading and installing a free compression program called 7zip. That will let you "zip" all the log files into a single archive that you can send to us. We will "unzip" your archive that you send us to access all the log files.
Your network can certainly be the bottleneck when it comes to stuttering. So trying wireless N with full signal strength (or, even better, trying Ethernet cables) is an excellent idea.
Regarding MPEGTS and MP4 bitrates, either file type can have low or high bitrates - it just depends on the source video that has been encoded into the particular MPEGTS or MP4 file. So it is an individual file consideration and not a format consideration.
Let us know how your network upgrade goes.
My ISP provided me with a Ubee wireless b/g gateway/router with the service i have. It dawned on me tuesday night that I already had a b/g/n gateway router in the garage stored away from a previous service I had a couple years ago. So I figured I'd try that unit, a Motorola SBG6580. So called my ISP yesterday from my office before I went home to see if they would allow use of that unit. Since it's DOCSIS 3.0 they said no problem, while I had them on the phone I decided to upgrade my Internet speed from 10 to 20 Mbps, no problem there. While I was on the phone they told me of a Cable TV bundle they had so I upgraded that..... The Cable upgrade required a tech to come out to coplete the order. Ok, no big deal. He won't be here until tuesday.
So when I got home from the office I called my ISP to give them the info on the SBG6580 b/g/n gateway router. I made all the physical connections to it required and gave them all the pertinent info only for them to tell me after 30 mins on the phone they could not input the new gateway router to their system while there was an open work order for the cable tv... ugh! so I had to set the old b/g gateway router back up and put the network back as it was until tuesday when the tech comes out to complete the cable tv intall. what a drag!
After all this I was still determined to do what I could to elininate the gateway/router as the bottleneck for the streams. I tried setting up the network via hardwire, but i could not get any of the devices to "see" one another over the wired network. One device, the Samsung BD-C6500, does not allow sharing over LAN, only WLAN...how retarded is that? it says so in their documentation. The other device I'm sure had to do with the router settings or device settings and with limited time i could not dive into the matter too much. In the end I thought to test the files themselves directly on the frontend devices. I uploaded a files to USB drive and played it back on the SMP-N200 and it played flawlessly.
To me that seems to indicate it's not a file issue but a network issue. what do you think?
It could well be your network that's causing your problems. I agree with you that you should get your network sorted out first, and then try streaming your files. Let us know if you have any problems with streaming files after your home network is upgraded and we will gladly help.Quote:
Originally Posted by Crash1976