View Full Version : New user confusion...

06-21-2011, 11:06 PM
I'm evaluating Mezzmo at pres but have to say I'll prob purchase when the trial ends as it works - well mostly!
I have a Panasonic plasma G20 connected to my network. I also have a Netgear Duo NAS box where I keep all the films I want to watch. I run Mezzmo on my desktop PC (a dual core AMD of 3 year vintage!)
When I watch some films, say recorded as an MP4, I'm finding it occasionally stutters/stops but then goes again.
My question is, is running mezzmo on one machine and having my films stored on on another causing this problem? If not, what can I do to resolve it please?

06-22-2011, 09:45 AM
Hi David,

My first guess would be that those files are being transcoded and the CPU is not powerful enough to transcode for real-time playback. If they're native (not being transcoded), then possibly the network could be an issue (if it's wireless). Can you please post FFmpeg information (in Mezzmo right-click on the file and use the "Get FFmpeg Information" command) on one of those files, and also please tell me which device profile you're using.

06-22-2011, 09:50 AM
Here Dennis. The network is 1000mps and wired so I'd be rather miffed it it was that! Once I'd closed 'everything' down (including virus software) it did improve a little. Is it best if the file is one the same PC?

ffmpeg version git-N-30186-gd9d5603, Copyright (c) 2000-2011 the FFmpeg developers
built on May 25 2011 12:16:07 with gcc 4.4.2
configuration: --enable-memalign-hack --arch=x86 --target-os=mingw32 --cross-prefix=i686-mingw32- --enable-static --disable-shared --enable-zlib --disable-ffprobe --disable-ffplay --prefix=/media/windows/ffmpeg --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect --pkg-config=pkg-config
libavutil 51. 2. 1 / 51. 2. 1
libavcodec 53. 6. 0 / 53. 6. 0
libavformat 53. 2. 0 / 53. 2. 0
libavdevice 53. 0. 0 / 53. 0. 0
libavfilter 2. 10. 0 / 2. 10. 0
libswscale 0. 14. 0 / 0. 14. 0
libpostproc 51. 2. 0 / 51. 2. 0

Seems stream 0 codec frame rate differs from container frame rate: 47.95 (66893/1395) -> 23.98 (66893/2790)
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\\Nasbox01\films\Harry Potter And The Deathly Hallows Part 1.mp4':
major_brand : isom
minor_version : 1
compatible_brands: isom
creation_time : 2011-03-30 09:11:02
Duration: 02:26:05.31, start: 0.000000, bitrate: 2450 kb/s
Stream #0.0(und): Video: h264 (High), yuv420p, 1280x528 [PAR 1:1 DAR 80:33], 2046 kb/s, 23.98 fps, 23.98 tbr, 66893 tbn, 47.95 tbc
creation_time : 2011-03-29 16:09:49
Stream #0.1(und): Audio: aac, 48000 Hz, 5.1, s16, 400 kb/s
creation_time : 2011-03-30 09:20:29
At least one output file must be specified

---> DB Level Info: 41

06-22-2011, 09:52 AM
If you're using the Panasonic Viera device profile, then this file will be transcoded. Most likely it's not transcoded quickly enough.

Please turn on logging (see this thread: http://forum.conceiva.com/showthread.php/419-FAQ-How-to-turn-on-diagnostic-logging) then try playing it again and once it starts to stutter, stop the server and send zipped up logs to support (at) conceiva (dot) com and we'll take a look.

06-22-2011, 09:55 AM
how do I use a Viera device profile or know if I am?

06-22-2011, 09:56 AM
Just click on the Media Devices button in the toolbar and it'll show what you have and what device profiles you are using.

06-22-2011, 09:59 AM
Each time I close down I also get:
MexxmoMediaServer.exe app error.
Instruction at 0x0000000 referenced memory at 0x0000000. Memory could not be 'read'.
Any ideas?

06-22-2011, 10:01 AM
There're a few possibilities; if you send in the logs, perhaps they'll give us more hints.

06-22-2011, 10:01 AM
Its th ecorrect profile. And it also says its a gigabyte connection.

06-22-2011, 10:02 AM
Ok, so just leave those settings as they are and send in the logs and we'll see what's going on.

06-22-2011, 10:02 AM
wil try it now and see what happens and get back to you . Thanks for your help.

06-22-2011, 10:41 AM
Files sent as requested. Now alos getting media server app error re memory being written!

06-22-2011, 10:45 AM
Thanks, we'll get back to you via e-mail.