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 - odin4242

#1
VOMP for Raspberry Pi / Re: Sound with clicking noise
September 20, 2012, 20:35:04
So,

the new Wheezy Image is installed and it's much better! The OSD is more responsive and the analog output is ok now.
Now, how about HD Deinterlacer for Servus TV? ;)
#2
The chvt 8 && ./vompclient is a good solution for now. Only the cursor is blinking in the top left corner while watching 16:9, since i have a 4:3 monitor. Black on black as color would be good, but that's realy nice to have now.
In the end it would be cool to auto start vomp in a blank console at boot. I don't care how it's done  ;)
#3
@Marten
Currently all inputs in the vompclient are also executed in the console. It happens from time to time, that i start a second vompclient (up and ok)
Is it a big thing to change that?
#4
VOMP for Raspberry Pi / Re: Sound with clicking noise
September 19, 2012, 20:21:49
I tried to update my Pi with apt-get update and apt-get upgrade but unfortunately that killed my /boot on the SD card...
That finishes my testing for today since the download will take another 2 hours  :o

With HDMI sound is fine, but the volume control is not working.

I traced the clicking on the analog jack with debug logging, but found nothing. The ffmpeg is printing "incorrect frame size" over and over again to the console, but that seems to be a known thing (googled it)

So next try in a few days when the SD card is ready again.

Till
#5
VOMP for Raspberry Pi / Sound with clicking noise
September 18, 2012, 07:56:36
Hi Marten,

i compiled the latest version yesterday evening. Since i use an HDMI to DVI Converter i play the sound through the analog jack. On some channels i have a clicking noise that get worse in the course of time. Switching channels usually solves the problem for a short time.  I'll have a look in the debug.log next time i try. I deactivated the SD Deinterlacer and had the feeling, that it was a bit better. But the clicking is audible on HD channels, too.

Do you have any idea? Is there a similar problem with HDMI output?

Thanks for all your efforts
Till
#6
Sorry, just realized, you posted this in the Raspberry Pi section. Forget about the dongle than. You will need to update to the latest server version to use the raspberry client.
#7
Hi Magnus,

only one channel indicates, that the client and the server are running different versions. You should use a V0.3.1 dongle for your MVP.
This one should do: http://www.russle.net/vomp/0.3.1/vomp-dongle-0.3.1-3-Yaris.tar.bz2
I can not help on the ebuilds, sorry

Till
#8
VOMP for Raspberry Pi / Re: default startup action
September 13, 2012, 10:36:31
Well, my MVP running Vomp has that feature?!? I think it was introduced with some yaris patches ages ago.
I fear i will be home late today, so i can double check this not earlier than Friday evening
#9
1000mA is recommended, i currently use a 800mA (since i still haven't found the one i bought with the pi).
#10
VOMP for Raspberry Pi / Re: default startup action
September 13, 2012, 10:08:08
That feature already exists on the MVP-Boxes. Should not be a big deal
#11
Quote from: clausmuus on September 12, 2012, 09:40:10

Maybe it helps you to know, that I don't use a full HD screen, but a 1280x1024 TFT via DVI.

Hi Claus,

does your Monitor Support HDCP? Mine does not. You can change some settings in the config.txt concerning HDMI/DVI. Unfortunately i had no time yesterday to dig deeper into this.

Till
#12
It would make sense to store those Images on the Server, doesn't it? The Vompserver could deliver them to the client.
#13
Hi Marten,

maybe i recall it wrong, but haven't you said once, that you had some type of skin able GUI ready?
So is there a urgent need to change something in the handling for the GUI?

Till
#14
But maybe, Martens solution with the transcoder will enable the Pi for mpeg2 playback without additional costs?
I don't know, if the omxplayer has an API to be used by VOMP, so currently i guess the license will be of no use for us anyway?

Cheers,
Till
#15
Marten commited some changes to the git 39 hours ago:

Custom libav + transcode patches + first mpeg2 playback through transcoding

Maybe i'll have some time tonight to try that