News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - MartenR

#106
VOMP for Raspberry Pi / Re: Not a deb file?
June 09, 2013, 07:59:42
Quote
Is there a german translation of the vomp menu? Is this client or server related?
You can select at client side the language in the properties menu and of course german is included.
For the autostart of vomp, I would recommend to create a deb while from the sources with dpkg-buildpackage, but remember once installed the package local access to the console is not possible anymore, so you should setup ssh first.


Marten
#107
VOMP for Raspberry Pi / Re: Not a deb file?
June 07, 2013, 07:06:06
No, but you need a running vompserver with the same version as the client.
#108
VOMP for Raspberry Pi / Re: Not a deb file?
June 05, 2013, 07:15:47
Your download is broken 512 bytes is too small, download the deb file again.

Marten
#109
Comment to the second patch.
There are likely (hdmi cec) remotes out there, who do not have play,pause and rewind and fastforward.
Therefore it is necessary to not change the behaviour of the left, right etc. buttons, in order that these user can use vomp with their tvs.

Marten
#110
I have fix the sanity check.


QuoteI will continue looking into the demuxer and audio parsing code. It annoys me a lot not finding the root of the problems I see.
I think it is very likely, that all problems originate from "DeliverMediaPacket". It is very likely, since you mentioned, that there is no problem on the mvp.

For the ac3 data you can compare passthrough mode and non passthrough mode. In the case of passthrough mode, you would not see any libav messages, since everything is done in the tv, but if the data delivered to "DeliverMediaPacket" is corrupt, you will hear it.
If everything is working fine, that error must be after the "else" related to "if (passthrough) {".

Good luck!

Marten
#111
Quoteannoying high frequency chirps
These are probably still misdetected mpeg audio frames. But I do not know how to identify them.
Anyway, I suggest, that you select the ac3 audio track, since all your problems are related to mpeg audio.

Marten
#112
I have implemented sanity checks similar to your checks.
Please test it.

Marten
#113
Should work out of the box from the vomp side.
You may have to set up your tv to enable HDMI CEC.
You might have to change some key onder properties.

Marten
#114
I suspect, the driver reports all keys with the same scan code.
Test it by using cat on the /dev/input/event device of your remote, unfortunetely for some remotes the kernel module does not contain all keys. (Maybe look for Kernel patches).
Then manually editing the config will not help.

Anyway RemoteKey96, says nothing, it only says, that it is the 96th remote translation rule. The rule itself is encoded in the heaxdecimal number.

Marten
#115
I will look into the patch and implement sth. similar.

QuoteSince recordings play fine using other methods I must ask. Is the vompserver plugin modifying the stream before its sent in some way compared to e.g. the streamdev plugin? In other words. Is the problems I see perhaps on the server side and not on the client side.
Of course vomp modifies it in some way. Everything is done on the client side.
We have a demuxer, then the parsing code in audioomx. Everything there can have an error which drops some data.
Also it is possible that the playerlivetv has droped some data, look for the log message "Dropped chunk", if this occurs the number of max buffers PLAYER_MAX_STREAMING_BUFFERS defined in defines.h is too small.

Anyway the message, "big_values too big" is a sanity check in side the mpeg audio layer 3 decoder. Since audio should be layer 1 or 2 in DVB (check this please for your channel), it is very likely, that  it is still not synced properly.

Marten
#116
Quotenot only checking if the framesync is correct but also checking the values of the layer, bitrate and frequency.
It might be necessary to implement this as well....

I have no additional documentation for mpeg audio than the ones you mentioned. There might be the specification...

Marten
#117
You are correct, this is wrong. Thanks. (I will commit this soon).
Regarding the mpeg2 variable I think it indicates mpeg version 2.5.
lsf indicates mpeg2 vs. mpeg1, if I remember correctly.

Marten
#118
Maybe the path is not correct. You should check in the source code of the configure skript, what is causing the failure. Alternatively you can seek in the forum, some posted some change for vomp to work 2.0.

Marten
#119
You should compile the older libcec for yourself, if I remember correctly, it was necessary to patch the libcec somewhere.
#120
libcec is too new. Since I am developing with raspbian I stick to the pre 2.0 libcec version.

Marten