Messages

Yes, maybe I have connected the vomp before (for some tests) to the other VDR. I will test if this is the reason. But were does the vomp stores the recording listing, so that it is available after a vomp restart?

Claus

Hi Marten,

that is the "default", but not wished. If I don't start the vompclient and than do a reboot, I can see at boot time the boot log messages. But I will do some further tests with the "fbset" stuf, you have posted before. Maybe that fix it. An other idea is to select a specific resolution in the config.txt. Maybe that will help. I must test this also.

If there is no HDMI connected, the remote will just fail when connecting at the startup of vomp.

I have connected the hdmi. I also can see the vompclient, but just noting before the vompclient starts. Maybe there is a problem in the startup sequence? Maybe you first do the remote cec connect and after that activate the hdmi output? OK, I think this problem will be fixed if I found the reason, why the hdmi output will be disabled on reboot and I can fix this.

Hi,

if I reboot my RPI, after reboot the vompclient can not controlled by cec, but if I press a key the TV shows a message to select the cec client that should be controlled. If I now select the the RPI, I even so can not control the vompclient. After I restart the vompclient, every thing is ok.

Claus

PS.: After reboot, the hdmi output is disabled, until the vompclient will started. On shoutdown I see the console 1 and the shutdown log messages.

I have made some further test now. It's not necessary that the video Output is the hdmi. But it's necessary, that a hdmi device is connected at vompclient startup.
E.g. if I start without a hdmi device connected, automatically the av out will be activated. If I now try to start the vompclient, I will get the seg fault. If I now connect a hdmi device (it can not show the video, because the hdmi port is disabled by firmware), I can start the vompclient witout the segfault.

Claus

Anyway, in current git, you can switch "off" vomp using the power key.
It is the same way the mvp was switched "off", just turning off the video signal ...
And then you can it switch on using the power key (of your remote for the cec device or your usb remote or the esc key on a keyboard).

How can I check, if the power off signal will be send to the vompclient? If I press the power button, the TV will switch off. So I can not see, If the vompclient will also switch off the video out.

Claus

Hi,

I have found a problem with a local vdr server.
If I connect the vompclient to a local vdr (by using the -s 127.0.0.1) Option, I get the recordings list of my other vdr PC.
OK, this is nice, since I have no recordings on my local vdr, but mainly not that, what I expected

Claus

Hi,

after I use again the latest version (a some days newer version) of the kernel, the problem gone.
So it was only a problem of a single kernel version.

Claus

Hi,

if I use the av output (or don't connect a hdmi device), I get a segmentation fault on vompclient start:

Code Select Expand

MLD> vompclient -s 127.0.0.1 -d
19:23:37.709310 [info]   2393 Core - Starting up...
19:23:37.712131 [info]   2393 Core - Signal handlers set up successfully
19:23:37.713999 [EMERG]  2393 Core - Could not retrieve free virtual console, please change permissions
19:23:37.720040 [notice] 2393 Remote - Init LibCEC
19:23:37.903586 [debug]  2393 Remote - CECLOG: 127 4 unregistering all CEC clients
19:23:37.906977 [debug]  2393 Remote - CECLOG: 131 16 Broadcast (F): osd name set to 'Broadcast'
19:23:37.909537 [debug]  2393 Remote - CECLOG: 133 16 InitHostCEC - vchiq_initialise succeeded
19:23:37.911406 [debug]  2393 Remote - CECLOG: 135 16 InitHostCEC - vchi_initialise succeeded
19:23:37.913336 [debug]  2393 Remote - CECLOG: 137 16 InitHostCEC - vchi_connect succeeded
19:23:37.915931 [debug]  2393 Remote - CECLOG: 140 16 received data: header:00060040 p0:0000000F p1:0000FFFF p2:00000000 p3:00000000 reason:40
19:23:37.917748 [debug]  2393 Remote - CECLOG: 142 16 logical address changed to Broadcast (f)
19:23:37.920117 [debug]  2393 Remote - CECLOG: 144 16 RegisterLogicalAddress - registering address e
19:23:37.922600 [debug]  2393 Remote - CECLOG: 146 1 RegisterLogicalAddress - vc_cec_set_logical_address(E) returned invalid arg (8)
19:23:37.924401 [debug]  2393 Remote - CECLOG: 148 1 Open - vc_cec could not be initialised
19:23:37.926214 [debug]  2393 Remote - CECLOG: 150 4 connection opened
19:23:37.929749 [debug]  2393 Remote - CECLOG: 153 4 << Broadcast (F) -> TV (0): POLL
19:23:37.931829 [debug]  2393 Remote - CECLOG: 156 16 initiator 'Broadcast' is not supported by the CEC adapter. using 'Free use' instead
19:23:37.933987 [debug]  2393 Remote - CECLOG: 158 8 << e0
19:23:37.936079 [debug]  2393 Remote - CECLOG: 160 16 >> POLL not sent
19:23:37.937834 [debug]  2393 Remote - CECLOG: 159 16 processor thread started
19:23:37.940340 [debug]  2393 Remote - CECLOG: 164 4 registering new CEC client - v1.9.0
19:23:37.942335 [debug]  2393 Remote - CECLOG: 166 16 detecting logical address for type 'recording device'
19:23:37.944254 [debug]  2393 Remote - CECLOG: 168 16 trying logical address 'Recorder 1'
19:23:37.946004 [debug]  2393 Remote - CECLOG: 170 4 << Recorder 1 (1) -> Recorder 1 (1): POLL
19:23:37.947708 [debug]  2393 Remote - CECLOG: 172 8 << 11
19:23:37.949592 [debug]  2393 Remote - CECLOG: 173 16 >> POLL not sent
19:23:37.951455 [debug]  2393 Remote - CECLOG: 175 4 using logical address 'Recorder 1'
19:23:37.953505 [debug]  2393 Remote - CECLOG: 177 16 Recorder 1 (1): device status changed into 'handled by libCEC'
19:23:37.955086 [debug]  2393 Remote - CECLOG: 179 16 Recorder 1 (1): power status changed from 'unknown' to 'on'
19:23:37.957217 [debug]  2393 Remote - CECLOG: 181 16 Recorder 1 (1): CEC version 1.4
19:23:37.958963 [debug]  2393 Remote - CECLOG: 183 16 AllocateLogicalAddresses - device '0', type 'recording device', LA '1'
19:23:37.961086 [debug]  2393 Remote - CECLOG: 185 16 RegisterLogicalAddress - registering address 1
19:23:37.963166 [debug]  2393 Remote - CECLOG: 187 1 RegisterLogicalAddress - vc_cec_set_logical_address(1) returned invalid arg (8)
19:23:37.964644 [debug]  2393 Remote - CECLOG: 188 16 Recorder 1 (1): osd name set to 'vomp'
19:23:37.966351 [debug]  2393 Remote - CECLOG: 190 16 Recorder 1 (1): menu language set to 'eng'
19:23:37.968106 [debug]  2393 Remote - CECLOG: 192 16 SetDevicePhysicalAddress - not setting invalid physical address ffff
19:23:37.969911 [debug]  2393 Remote - CECLOG: 194 4 setting HDMI port to 1 on device TV (0)
19:23:37.971652 [debug]  2393 Remote - CECLOG: 195 16 Recorder 1 (1): physical address changed from ffff to 1000
19:23:37.973132 [debug]  2393 Remote - CECLOG: 197 4 << Recorder 1 (1) -> broadcast (F): physical adddress 1000
19:23:37.974818 [debug]  2393 Remote - CECLOG: 199 8 << 1f:84:10:00:01
19:23:37.976825 [debug]  2393 Remote - CECLOG: 201 8 << 1f:84:10:00:01
19:23:37.978718 [debug]  2393 Remote - CECLOG: 203 16 making Recorder 1 (1) the active source
19:23:37.981081 [debug]  2393 Remote - CECLOG: 205 4 >> source activated: Recorder 1 (1)
19:23:37.983106 [debug]  2393 Remote - CECLOG: 207 16 scheduling active source message for 'Recorder 1'
19:23:37.985233 [debug]  2393 Remote - CECLOG: 209 4 CEC client registered: libCEC version = 1.9.0, client version = 1.9.0, firmware version = 1, log
19:23:37.987421 [debug]  2393 Remote - CECLOG: 211 16 Recorder 1 (1) was already marked as active source
19:23:37.989481 [debug]  2393 Remote - CECLOG: 213 16 sending active source message for 'Recorder 1'
19:23:37.991612 [debug]  2393 Remote - CECLOG: 215 8 << 10:04
19:23:37.993384 [debug]  2393 Remote - CECLOG: 217 8 << 10:04
19:23:37.995303 [debug]  2393 Remote - CECLOG: 219 16 failed to make 'Recorder 1' the active source. will retry later
19:23:37.997122 [ERR]    2393 Remote - CEC:Failed set active source
19:23:37.998737 [info]   2393 Core - Remote module initialised
19:23:38.000828 [info]   2393 Core - LED module initialised
19:23:38.002220 [info]   2393 Core - Mtd module initialised
19:23:38.004304 [info]   2393 Core - Timers module initialised
19:23:38.006008 [info]   2393 Core - Read from MTD: PAL 720x576
19:23:38.007785 [debug]  2393 Video - Setting aspect to 0
19:23:38.010181 [notice] 2393 Video - No CEA modes found abort
19:23:38.011749 [info]   2393 Core - Video module initialised
19:23:38.014859 [notice] 2393 OSD - OpenGL_ES OpenVG
19:23:38.016630 [notice] 2393 OSD - EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_vg_parent_image EGL_KHR_gl_texture_2D
19:23:38.018066 [notice] 2393 OSD - _image EGL_KHR_gl_texture_cubemap_image EGL_KHR_lock_surface
19:23:38.021535 [notice] 2393 OSD - Displaysize is 720 x 576
19:23:38.034706 [debug]  2393 OSD - Making egl current in12393
19:23:38.036385 [notice] 2393 OSD - 1.1
19:23:38.038103 [notice] 2393 OSD - Broadcom
19:23:38.039892 [notice] 2393 OSD - VideoCore IV HW
19:23:38.041615 [notice] 2393 OSD - VG_KHR_EGL_image
19:23:38.193929 [debug]  2393 OSD - Making egl current out 12393
19:23:38.208243 [info]   2393 Core - OSD module initialised
19:23:38.211268 [debug]  2393 Audio - MUTE OFF OFF OFF
19:23:38.216808 [info]   2393 Core - Audio module initialised
19:23:38.218415 [info]   2393 Core - VDR module initialised
19:23:38.220309 [info]   2393 Core - BoxStack module initialised
19:23:38.222706 [info]   2393 Core - Command module initialised
19:23:38.225111 [notice] 2393 Core - Startup successful
19:23:38.226977 [debug]  2393 OSD - shutdown mark1
19:23:38.230332 [debug]  2393 OSD - shutdown mark2
19:23:38.232123 [debug]  2393 OSD - shutdown mark3
19:23:38.233800 [notice] 2393 Video - Shutdown video module
19:23:38.235525 [debug]  2393 Video - enter deallocatecodecsomx
19:23:38.237349 [debug]  2393 Video - leave deallocate codecs OMX
19:23:38.268639 [debug]  2393 OSD - Making egl current out final
19:23:38.288397 [notice] 2393 Video - No CEA modes found abort
19:23:38.290089 [notice] 2393 OSD - OpenGL_ES OpenVG
19:23:38.291773 [notice] 2393 OSD - EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_vg_parent_image EGL_KHR_gl_texture_2D
19:23:38.293424 [notice] 2393 OSD - _image EGL_KHR_gl_texture_cubemap_image EGL_KHR_lock_surface
19:23:38.296073 [notice] 2393 OSD - Displaysize is 720 x 576
19:23:38.314340 [debug]  2393 OSD - Making egl current in12393
19:23:38.315930 [notice] 2393 OSD - 1.1
19:23:38.317515 [notice] 2393 OSD - Broadcom
19:23:38.319370 [notice] 2393 OSD - VideoCore IV HW
19:23:38.321030 [notice] 2393 OSD - VG_KHR_EGL_image
19:23:38.463342 [debug]  2393 OSD - Making egl current out 12393
19:23:38.465920 [debug]  2393 BoxStack - Update called
19:23:38.467869 [debug]  2393 BoxStack - Locked for update
Segmentation fault

Du you have any ideas or have test this yourself?

Claus

I have found the reason. It's the new kernel. Now I must see, witch part of the kernel makes the problem. Mainly the frequence scaling is added in the new kernel.

Claus

Yes, please post the Patch.

Claus

Hi,

now I test an update of a older installation with the latest firmware and the same vompclient as I use in my newer installation. This starts without problems. I think I have now a lot of work, until I find the different between this both installation. I was sure, this both was the only different,...

Claus

I can not recommend using the switch in a cord, it is very likely that you damage the file system on your sd card.
Anyway, in current git, you can switch "off" vomp using the power key.
It is the same way the mvp was switched "off", just turning off the video signal ...
And then you can it switch on using the power key (of your remote for the cec device or your usb remote or the esc key on a keyboard).

I think, this behaviour is grate. But I need a small extension, if it's not already included.
I need to call a script, if the vompclient go into (and before leave) the power save mode. It's necessary, because e.g. I want to disable the connected dvb devices (or set them also in a power save mode), since some of them needs a lot of power. Or I will shutdown and wakeup the vdr server, it it's not a local vdr.
Is it possible, e.g. to add a command line option, to define such a function, that than will be called with the argument "suspend" or "resume" (or two different command line options)? This will also make it possible to call a shutdown script, if somebody prefer to shutdown the RPI.

Claus

Hi Marten,

my Problem with this is, that I don't know were (and with witch function) to set the startup volume. Also I don't know, how to add this to the setup and to store it. I think it would be only a small think for you, but a big think for me.
But I have a new idea. I think, if I use the hdmi audio out, it's right to use a default volume of 100% (ok, in my case this is also bad, because if I switch the hdmi source, I must also change the volume on the TV from 50% to 10% to have the same level, but this is maybe only my problem), but if I use the analog out (as I plan for the bad room), and I connect speakers that have no volume control (as I also plan), than I have a problem, if I can not set up the default volume, and it is set to 100%.
I think it will be the best solution, if I can set up a different default startup volume for analog output and hdmi output. The hdmi default volume should be 100%, the analog default level should be 70%. I also use this setup for the xineliboutput front end on PCs after a long discussion about the best preset values for this both cases.
It will be grate, if you can help us with this, since it seems, that also other users has the same problem as I with a not change able default volume.

Claus

No, I don't test it on raspian. I use raspian only in a VM to build my distry.
I will test today, to disable the auto select and switch to a free console before start the vompclient.
I will also test and older installation with the newest vompclient.

Claus

I must show this immediately my wife 

Claus