Messages

It may be coincidence but there is a thread on the VDR mailing list right now where someone is discussing the VFAT switch. It seems that one of the functions of that switch is to replace colon ( and other suspicious characters in recording filenames, since the filesystem character set on M$ platforms is more restrictive than on Unix. Also VDR 1.3.32 now uses dots by default within filenames in place of colons. I'm not sure how this related to your problem though, unfortunately.

Dave

I'm using vdr 1.3.32 and the latest vompserver with no problems on UK DTV, so I don't think there is anything fundamentally wrong at the server end.

Dave

No problem. Incidentally have you spotted that on the current CVS the 'welcome' screen is never redrawn, so the clock remains frozen at the time the MVP was booted?

Dave

Yes I'm looking at the i18n stuff, and the code is coming along nicely.

Dave

Can I put in a request for an option similar to the previous behaviour?

My telly dates from 1988, a time before widescreen, Dolby Digital and DTV. Its SCART expects +12v on pin 8 to switch from broadcast to A/V and doesn't understand the +6v widescreen option. Hence when selecting a 'wide' program on VOMP the TV switches back to broadcast - very confusing since it appears that VOMP is not changing channels correctly!

How about a 'nailed-up' 4:3 option which always presents +12v? Or should I start saving for a new TV 

Dave

Given that selecting Resume on a recording with no resume point appears to have identical effect as selecting Play, why bother with all the extra coding in looking for resume points?

It provides feedback to the user that there *is* a resume point set for the recording, so maybe they've watched part of this before. No big deal though.

Dave

Make "Resume" the default if there is a resume point set for the recording, otherwise "Play"?

Dave

VDR 1.3.30 introduced a new framework to allow plugins to interact directly, rather than through VDR. This may eventually provide a method of implementing new features, so for example instead of vomp playing MP3 files directly it calls the MP3-player plugin.

In the meantime though I agree that the important thing is to get the basic set-top-box and PVR functions working.

Dave

My understanding is that the MVP is 100Mb half-duplex. If your network hub can't autonegotiate to this then you may get excessive packet loss.

Incidentally it is possible to telnet into the MVP and poke around - it's just a stripped-down linux system after all. I'm sure the network interface settings are somewhere in the /proc tree but can't remember where...

Dave

Sheesh, 1800 channels... Are any of them worth watching 

Dave

Works for me with vdr 1.3.29 and last night's CVS, but then I'm using UK DVB-T and I suspect Hoochster is not.

How about turning up the log level in vompserver to see what is happening in mvpclient.c? I've been meaning to ask how the new logging system works - presumably a config file setting determines the level?

A black screen sounds like the client crashing because of unexpected data.

Dave

Your non-working channel has a non-zero value in the "Conditional Access" field - that's the '1810,1801,1800' value. Vomp with vdr 1.3.x currently ignores any non-Free-To-Air channels which is why you don't see it in the list.

There are two possibilities: either this is a valid channel which you are able to view with some kind of CA card, in which case a rethink is needed (a user-set option?) or the channels.conf is corrupt. I've never seen vdr used with encrypted channels so I'm not sure which is correct.

To see the documentation for channels.conf enter "man 5 vdr".

Dave

The code for VDR 1.3.x says that if vpid !=0 and apid !=0 then it's a valid TV channel, if vpid=0 and apid !=0 then it's a radio channel. Are your missing entries lurking in the radio list?

Post your channels.conf if you can't work it out. The 1.3.x code has AFAIK only been tested with DVB-T in the UK; other countries and other systems such as DVB-S may have quirks which haven't been taken into account.

Dave

The channel list comes from VDR's channels.conf.

Which version of VDR are you using? Version 1.3.x actively maintains the channel list (by default), so Vomp only displays those channels which actually have data (ie where VDR has set a non-zero vpid and apid in channels.conf). With VDR version 1.2.x the channels.conf is static.

Dave

Using Dongle 007 and today's CVS, when I tune to a non-transmitting channel I get the new 'No Data' popup. However *every* channel selected thereafter also produces the popup. It doesn't stop viewing since the message disappears after a few seconds.

This is with vdr-1.3.27. BTW VOMP does work with the latest development version 1.3.28.

Dave