New alpha dongle Dec. 04

[Lindsay]

Martin, don't know whether this is the right place for this or not.

Tonight, using 4 Dec dongle, played a recording but using exit button at end I got a black screen. Eventually a screen came up but it wasn't handling remote commands at all well. It seemed to store (discard?) them then a screen would change. Had to pwr the mvp off and on to restore service.

Sorry I am not clever enough to get your telnet logging going. Don't even know if this is the one you have been tracking.

Lindsay.

PS Don't worry about the bastard who slagged you off by email. There are far more of us than him! (grammar not good!!).

[pz1]

Martin,
Please accept my continued support for this dongle. I have not been active here recently, but I am testing all new dongles you release. I do have a lot of jerky live TV and video lately, but I am pretty sure it are NOT the dongles that cause it. So do not get upset about nasty emails.
Pieter

[mvallevand]

when i browse the filesystem on mvp, only directories are shown. so i can't playback the mpg directly. what do i miss? turas

Offhand that could be two things

1 - the file is not an mpeg/mpg file. Without the vlc interface only native video formats are supported. If this is the case, the o-t-f transcoding could actually be the source of the problem.

2. When files are moved files into a Windows share they have won't have be given Guest permission. I use the calcs command line tools to show the permissions and if guest is not on use this syntax

cacls filename /E /G Guest:R

Martin

[mvallevand]

Tonight, using 4 Dec dongle, played a recording but using exit button at end I got a black screen. Eventually a screen came up but it wasn't handling remote commands at all well. It seemed to store (discard?) them then a screen would change. Had to pwr the mvp off and on to restore service.

That sounds like the problem, but it isn't specific to the Dec. 4th dongle, because there was no emulation mode change in it. The GBPVR logs are still helpful, I am trying to see when the blocking starts.

Martin

[mvallevand]

Martin,
Please accept my continued support for this dongle. I have not been active here recently, but I am testing all new dongles you release. I do have a lot of jerky live TV and video lately, but I am pretty sure it are NOT the dongles that cause it. So do not get upset about nasty emails.
Pieter

Thanks Pieter (and everyone else). The email didn't really bother me, but when added to some other comments on the forum it did make me think that maybe I am the only one having a good level of success. If nothing else it helped push me to find a potential problem with the pause.

As for the the jerkiness the new command line option to return the demux to the original state is --no-seek-sync if you feel that could be the problem.

Martin

[jksmurf]

Martin,

I used the mvpmc test file in my dongle config dir and Putty using the method here and took screen captures. I have NO IDEA what I'm doing but if it is correct I hope it helps.

I am trying to give you some feedback for my non-responsive remote (new batts).

Steps Taken:

1. d/loaded the mvpmc file from http://www.mvpmc.org/~mvallevand/mvpmc.zip (no extension) - I THINK you need to d/l this again following each new dongle release.
   
2. Unzip it into C:\Program Files\devnz\gbpvr\Dongle\mvpmc where the dongle.bin.config resides. [EDIT]The folder is shared, BUT you "might" need to right click the file and ADD share permissions for Guest, if it hasn't already done so during the unzip. If you unzip to desktop and then drag to the share dir, you will likely need to do this. I forgot the first time.
   
3. Set Putty profile 192.168.1.200 (MY mvpmc IP reserved by my router) on Port 23, telnet. [EDIT]Suggest you also enable logging in PuTTy (and SAVE the profile after you choose logging)!
   
4. telnetted to mvpmc, got screen 192.168.1.200 login:
   
5. Typed in "root" at login: prompt
   
6. Got "BusyBox v1.1.3 (2007.10.11-03:43+0000) Built-in shell (ash)
   Enter 'help' for a list of built-in commands."
   
7. Issued killall mvpmc. Got a bunch of killall mvpmc messages. See attached jpg.
   
8. After "killing mvpmc" you should set the time with: rdate -s "ntp server" where the ntp server is your choice. e.g. time.windows.com, asia.pool.ntp.org. See http://support.ntp.org/bin/view/Servers/NTPPoolServers. This ensures the seconds in both logs will be the same. e.g. rdate -s time.windows.com
   
9. Issued "/etc/mvpmc/mvpmc -m pal -a 16:9auto -o svideo -o passthru --flicker 2 --startup emulate --emulate 192.168.1.10 &" NOTE: The contents of YOUR dongle.bin.config will MOST LIKELY be different! "mvpmc --emulate 192.168.1.10 &" is a simple test alternative, but you still need your Server's IP (mine is 192.168.1.10).
   
10. Went downstairs, chose emulation mode on mvpmc, navigated around to see if same lag (slow) or non-responsive remote key presses persisted.
    
11. Issued ctrl-c:killed this mvpmc. [EDIT]The only thing ctrl-c doesn't really kill mvpmc when you put the & at the end of the command line, but it will exit the telnet shell leaving mvpmc running.

I wrote it as above so maybe other folks can help you by stepping through this (for me) a little daunting, but not impossible procedure.

k.

p.s.
1. Sorry I forgot to enable the putty.log, hope the screen captures are OK.
2. Do you need mvpmc logs from gbpvr? Attached.

[mvallevand]

Turas and k there is a similarity in both your logs as I seem to see this as the final line that shows.

Code:

2007-12-12 19:31:22.903    ERROR    [6]    Unable to find node: /settings/Custom/ConverterElement[@name="converter3"]

I have no idea what this error means or where it comes from, but it is a place to start.

k, thanks alot there I will digest things more when I get home. You may have an issue with share permissions and I suggest you look at the file attributes with cacls as I suggested to turas. Alternative if you unzip mvpmc directly into that folder the proper permissions should be created.

Martin

[Lindsay]

Sorry, Martin, I should have attached the logs.

[Sheik Yerbouti]

Hi Martin,

Today I had two moments where the MVP didn't respond to my remote. It happened at 21:37 and 22:00. I didn't make the screenshots when it happened, because I thought I could go back in the output of Putty. Later that evening I did press Ctrl+C to stop the log from refreshing all the time, trying to make a screenshot.
However, at 21:37 I did see something like "Broken Pipe" in the log, is this any help? How can I make sure I don't lose the logs the next time?

OK, I found an option in Putty: lines of scrollback. It's set at 200, and I've just changed it to 20000. Now I'm hoping the problem returns tomorrow!

[mvallevand]

Thanks Sheik, I will have a look this evening.

For everyone helping with client side logs, rather then using Putty a much more "transparent" solution is available if you can make your mvpmc share read/write and enable this in your config file with these two changes.

1) Add

mount.cifs //ip/mvpmc /etc/mvpmc -o guest

2) Change the config file from

mvpmc options &

to

/etc/mvpmc/mvpmc options > /etc/mvpmc/mvpmc.log &

You can modify this to write to any share you'd like.

Martin