Messages

If this all won't help, then it can also be a hardware issue. Maybe your MVP has a deffect TI DSP chip.
The PowerPC chip in the MVP is used for the normal OSD, the video is only passed to the DSP chip for decoding. So this DSP maybe deffect.

In order to check if it is working at all, you may also check if the Windowsclient is working. But to be honest this is hard to check. E.g. for me I did only get crashes, but as I don't need this client I didn't get much more in detail to it. Also having no video output is also one of the problems you may face with this program normally (when not using the correct libraries).

Again, your setup in general is correct, as you:
1. Get a dongle loaded
2. Get the OSD displayed
3. Even get the sound when playing MPEG2 streams

So either the dongle / plugin version is wrong or you have a hardware deffect.

Hello Goldfish,

apt-show-versions tells me:

gustav:/tftpboot# apt-show-versions vdr-plugin-vompserver
vdr-plugin-vompserver/experimental uptodate 0.2.6-5

gustav:/tftpboot# apt-show-versions vdr-vompclient-mvp
vdr-vompclient-mvp/experimental uptodate 0.2.6-1

Are these different versions?

These are correct versions from the packages. But my doubts are here, if these are really used.

You also tried the mediamvp-plugin (as I've seen in the vdr forum) and I'm unsure if this may have some effects on the right dongle loading.
AFAICR for the mvpplugin you need an extra TFTDBOOT server and so on. Maybe due to this "try" you have an older dongle version loaded.

Additional I tried the dongle.bin from http://www.loggytronic.com/dl/vomp-dongle-0.2.6 but I get no video - only audio.

Have you tried without any dongle in the respective directory (just rename the current to a stupid name)?
This would at least give you the hint, which dongle is really loaded.

This behaviour looks like you are running different versions of vdr-plugin and dongle.

Are you sure the right vdr-plugin AND the right dongle is loaded?

Reason:
In between the versions i.e. the video code has changed, so everything will work but you don't see video output.

Hello,

just to let you know, how I was setting up my development environment.

I didn't have a DVB-card left, so long time I didn't know how to set up a dev environment for VDR and VOMP for sure I didn't want to touch the running system.
Okay, others may have found the solution earlier, but for me it took months.

Just use a virtual machine and use the streamdev-plugin for your virtual development VDR.

For the virtual machine you can use your most favourate one (VMWare, Bochs, etc.), the only thing it must support is bridged networt, as your MVP need access to the VDR in the virtual machine.

Then you need the dhcpd.conf configured with the "next-server" option. Chris mentions on his Howto "Investigation needed", but it does work.

Attached is my shortened version of /etc/dhcpd.conf:

192.168.178.1 is my gateway to the internet (AVM Fritzbox, dhcp disabled)
192.168.178.10 is my normal VDR
192.168.178.11 is my development VDR
192.168.178.200 is one of my normal MVPs
192.168.178.210 is my development MVP
All PCs get ips form x.x.x.30 to x.x.x.100

Code Select Expand

option domain-name-servers 192.168.178.1;
option subnet-mask 255.255.255.0;
default-lease-time 31600;
max-lease-time 43200;

subnet 192.168.178.0 netmask 255.255.255.0 {
    range 192.168.178.30 192.168.178.100;
    option broadcast-address 192.168.178.255;
    option routers 192.168.178.1;

    host mvp-normal {
        hardware ethernet 00:0D:FE:00:23:FE;
        fixed-address 192.168.178.200;
        filename "vomp-dongle";
    }

    group {
        next-server 192.168.178.11;
        host mvp-dev {
            hardware ethernet 00:0D:FE:00:71:DF;
            fixed-address 192.168.178.210;
            filename "mvp-kernelimage-nfsroot";
            option root-path "/diskless/nfs/mvp";
        }
    }
}


As you can see, the important thing is that you put the next-server option into a "group". Then it works. This is the setup for a NFS dev environment, using dongles is similar.

Streamdev-plugin:
The VDR in your virtual machine will not have a DVB-Card. This is not a big issue. You only need on your normal VDR the streamdev-server plug-in and on your Dev environment the streamdev-client plug-in. How to set it up is your task, but it is no magic.

The only thing is that your purer virtual VDR doesn't have an output device yet, so you should also add the dummy-plugin to your development VDR - otherwise VDR doesn't start (which makes also sense to put it onto your productive VDR in case like me that your only output device is VOMP).

There is for sure one limitation: Streamdev only provides one channel, so you cannot record 2 channels or record and watch another channel. But this doesn't hurt on a dev environment.

Again, maybe nothing new to some of you, but I didn't find any hint yet in the forum about this way of setting up a dev environment.

If you have questions, just let me know.

Hello,

I attached a (small) patch to fix 2 drawing issues:

1. Recordlist: Endings of long recordingnames are not deleted when scrolled http://www.loggytronic.com/forum/index.php?PHPSESSID=8qoviesscgemsrti29so1ekn13&topic=232.0

2. Titlebars: In case the titelbar content is too long, the text had 5 pixels at left end, but not on the right end. Currently wasn't ugly like 1., but I still like it better this way.

How this was fixed:
I added implemented in the drawText function in surface.cc a width check and added the necessary functions with the new argument. All current drawText function still work, as with a width of 0, no length check is done.

Remarks:
1, Currently it is only a width check as I don't think that a height check makes sense
2. I didn't implemented a check for right aligned or centered text yet. Chris: If you want these as well, I will implement it for sure.
3. This check can now be used at other places as well, like for fixing e.g. http://sourceforge.net/tracker/index.php?func=detail&aid=1453263&group_id=139484&atid=743655, but I wait till you say you accept the implementation


(Changed: attachement removed because of new version available)

[lost connection]

It often happens that we watch a recording then after stopping it, we get a lost connection message. It also happens when after deleting a recording but less often when just accessing the recordings list from the main menu. It certainly seems to have gotten worse recently.

This behaviour I have too (same points of crashes), but our recording lists are normally in the range of max 20 - 30 entries.
So I would say, this "lost of connenction" is not bound to the number of entries in the recording list.

I don't have networking issues (at least I'm not aware of any)

No need to try something.

LinVDR is incompatible with this library.

The library is for Suse 10.something.

Suse uses already the GCC 4.something while linvdr use a 3.something.

Between the version, the c++ bindings have changed. It is known to be incompatible.
So no way to use it directly. And the library where you get the error exactly states that it is a c++ library (/usr/lib/libstdc++.so.6)

Either upgrade your installation or compile the library on your own.

I had the same issue, when I was using C't Vdr 4.5 which is sarge based. After uprading to Etch this issue was solved.

Hello Andreas,

I didn't try the new code yet.
This is mostly because of your comment stating: "Because of the new key mapping I had to stop both vdr and vomp, delete the 00-xx-xx..conf file and restart both."

If I understand this correctly it means that I cannot switch anymore between the plugin and dongle of the official release and this test versions anymore.

Is my assumption correct?

@Andreas,

I will check in more details - but will only be able to do it at the end of the week.

But as your libvdr is from SuSE and the original I have is from/for Etch, there maybe also other issues involved with dependecies on the distribution used. As stated before I now have Etch as system.

I have also had some random crashes when setting a timer, sometimes it worked sometimes vdr crashed (not the dongle).

As stated before, I first need to check it in more details before you start to investigate to much. Or someone else can confirm this behaviour.

Philipp

Yes. In the timerlist I can see all the timers existing but every name is just a "c", so the names are wrong.

I cannot see this on mine.
Maybe I still need some more testing (but really didn't change things there...).

I have checked this in more detail.
It is not related to the dongle (I checked both) but to the libvdr. When I use the original libvdr-vompserver I get the normal names whichever dongle I use.
When I use your libvdr-vompserver then I have the "c", whichever dongle I use.

Another one: As soon as I press OK on a timer in the list, the client crashes. Not that I use this option very often, but still a crash.

Fixed this and uploaded new patch + dongle at www.wellenvogel.de/software/vomp

Yes fixed

Thanks,

Philipp

Hi Andreas,

The timer issue (on my site) was a pure crash -i .e. immediately when you try to set a timer from the epg vomp crashed.
Does this still happen?

Fixed

Or is there any other issue?

Yes. In the timerlist I can see all the timers existing but every name is just a "c", so the names are wrong.
Another one: As soon as I press OK on a timer in the list, the client crashes. Not that I use this option very often, but still a crash.

I'm also sure that I use the newest dongle you provided as within MP3 I can jump with 0-9.

For the ID3 issue:
In general if no ID3 is there there will only be the small display with file info and mpge info (if there).

Yes, I have seen that.

For empty fields (album, artist) there is no special handling in the moment.

That's what I meant with empty displaying.

For title I check for completely empty fields - it should display the filename in this case in the view headline.
The other things I could put on the list - maybe not prio 1.

Yes not prio 1.

Cannot wait for the next features. And yes spring is also pressing me outdoor with the kiddies.

Hello,

just loaded now the new dongle.
May you also provide the new vdrlib, otherwise the timer is still broken (at least here it is with just the new dongle).
I still don't have a vdr compilation environment (still trying to get my new computer booting linux - sata issue) and in case you have it anyway compiled would be cool to have it for us as well.

Music now works great. Just one thing: The ID3 tag recognition sometimes shows nothing. I assume there could be a check if the tag exists but has no content.

Thanks,

Philipp

Do you have any suggestions how to improve the selection?

Not really much we can do about it. If you have 850 pictures in a directory, then beside of the filename there is not much more info available.
So either you do the organization manually by dividing into subdirectories or you have all in one. Even Thumbnails wouldn't help with 850 pictures (but would if it is on the range <100).
Exif may have additional info or maybe future cameras will include a GPS information as well. Using additional software with database integration (digikam, kimdaba) is not usable as well, as such info is not standardized.

As stated before I would propose to show directories in a different color and from sorting always on top. That's the only thing I'm missing.

Another general point:
You define in media which directories should be included.
E.g. /home/dude/myPictures.
The "ugly" point in the file selection is that this path is always displayed and if the path is long it doesn't really add info.
I would propose to have for each entry in media-section the path and a "name" which is then displayed as "root" for the path displayed. Or at least only display the last directory name.

Of course it would be helpfull to have thumbnails - but this will surely contradict the performance issue.

The thumbnail view should be optional. It's faster to find a special picture if you have a preview, but for sure if I want to see anyway a slideshow of the full directory this is definitely not needed.

Bug:
One tiny bug I found:
In case your path is not entered correctly in the media-section, then during display an error message is displayed. If you now press "back" then the display is broken but functional working. Just tiny as you only do the setup of the path once.

Feature requests:
1. Delete. It would be an easy way to delete the double pictures you made and only remain the best one. At least we do always 3-4 pictures of a scene and when we see the result on a big screen, just leave the best ones.
´
2. Exif orientation:
You can use the orientation stored in the EXIF info right from the beginning. No need for a full EXIF library just to do that. A code snippet how to read it can be found in following source file of mvpmc: Just look into the function "get_exif_orient".

Thanks, thanks, thanks.
I have just enjoyed now 2h sitting with my wide on the sofa and watching the photos from the server. No crash or similar things. Worked like a charm.

Thanks also for providing the binaries as well.
I have the C't installation and in order to use the binaries I had to update to Etch (which I wanted to do anyway). I know it's because of the new GCC version...

Performance:
I have pictures of a 1M and a 10M camera. For sure the 1M pictures were rather instantly available (1,5s) and the 10M needed 4-5s.

Just 1 thing at the moment:
Would be good in the file selection view directories could be differentiated easier than at the moment.

Your download site needs authorization with username and password at the moment