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

#16
The problem are the missing development files for 1.8.1-1 .
Since I have only patched with raspberry pi support. I do not know, if the raspbian folks managed to included support for the raspi in their libcec version.
Anyway, did you switch to jessie? Since I do not have the split into libcec1 and libcec2.

Marten
#17
The problem is that scaling the video beyond the borders of the screen is the correct behaviour. This is called overscan and always the case for television and is done on purpose.
Vomp does  put in values for aspect ratio correction manually to ensure the right aspect ratio. (I do not remember, if I got WSS to work on raspberry pi).
If you think the calculation is wrong, you should rather correct the calculation, than just turning the mechnism off.

Marten
#18
Thanks, I got the file, but it still  does not crash.
So we have to dig deeper, which os are use using?
Raspbian? For raspbian please do an apt-get dist-upgrade, there was a major change regarding the audio and libavcodec, which only comes with dist-upgrade.

If this does not help, can you please find out, which commit breaks it? (Best thing would be a binary search algorithm).

Marten
#19
QuoteAs per the question if there are subtitles? Yes the recording has Swedish subtitles. As far as I know the subtitles are part of the stream and cannot be disabled. I hardly ever use any other fronted than vompclient to vdr so I'm pretty unfamiliar with any possibility to turn off subtitles.
Well, you can hit the green button and select no subtitles, then the subtitle content is ignored by vomp. Or are your subtitles part of the video stream?
Anyway your debug trace shows clearly, that the crash happens inside the subtitle decoder. I expect something with now using the default vdr setting for subtitles, which turns your subtitles on.
(Does the crash occur at every skip? Or how often do I have to try?).
The gdb stuff did not help, since it looks like a currupted stack.
I tried to reproduce it, but I failed. Can you please prepare do the following:
1) Tell me your default setting for languages and subtitles on vdr side?
2) Report the selected tracks, if you hit the green button.
3) Deapply patch from http://git.vomp.tv/gitweb/?p=vompclient.git;a=commitdiff;h=de6fbe2d494aac80e0be1051f06ad72ad6718473 and http://git.vomp.tv/gitweb/?p=vompclient.git;a=commitdiff;h=89d00b9f8d3e3b5a3deeb87b6f6aafd6ec11c7ca, this way we see if it has something to do with the get subtitle settings from vdr patch.
4) Go back to the normal code (without modifications form 3)) and uncomment the line logger->log("VDR", Log::DEBUG, "Langpref %s %d %d", newpref.langcode.c_str(),  newpref.audiopref,  newpref.subtitlepref); in vdr.cc and give me the corresponding log. This way I can see your subtitle settings. (only if 3) does not show a crash)
5) Prepare a short recording for me, which shows the desired crash, so that I can analyze it.

Marten
#20
I can not reproduce it. (Did you make a clean before building, sometimes the dependency algorithm does not work well enough to rebuild everything, that needs to be rebuild?).
Can you please create a core file with setting "ulimit -c unlimited" and after the crash executing "gdb -tui vompclient core" and tell me, where it crashed inside the code?

Marten
#21
Makefile is fixed now.
Does the crash only occur with subtitles turned on?

Marten
#22
Now everything should be ready, except some bugs. Also the windows client is updated:
http://forum.loggytronic.com/index.php?topic=760.0

Marten
#23
Hi,
attached is an executable with scraper support and vector based osd. (see http://forum.loggytronic.com/index.php?topic=753.0)
The legacy version has the old osd and should run also on XP, the improved version needs at least vista with plattform update.

Marten
#24
VOMP for Raspberry Pi / Re: compiling git problem?
November 28, 2014, 06:58:45
Please go to the scraper support branch of vomp.
There I have adapted vomp to the changes in the new version of libav.
The old code is just not working with the new libs. (If you do not want to use the new branch, you may just replace the audioomx files).

Marten
#25
Thanks,
I have put corresponding changes into the scraper_support branch in git, which is more or less going to be at some time the next release.

Marten
#26
Can you please do the following at the vompserver?
Go into the file recplayer.cc to the method "unsigned long RecPlayer::getBlock(unsigned char* buffer, ULLONG position, unsigned long amount)"
and change "fseek" to "fseeko" and recompile the server.
And tell me if this fixed the problem.

Marten
#27
Hi,
well, I do not use files larger than 4 GB (since some file systems and network have still the 4 GB restriction).
So it is hard for me to debug it.
But anyway, can you please answer the following questions:
1) We are using the framenumber as index, so what does the recording time say (if you hit ok), does it jump backward or does it stay at advanced time?
2) A log of the serverside would be helpful, especially the " "getblock pos = %llu length = %lu" messages will help, where the problem is. (server or client side).
3) Do you use the windows client or mvp client? If yes does it happen there as well?

Marten
#28
Is now fixed!

Marten
#29
QuoteI was meaning the debugging (logging) switch -d. I did only manage to get the log once, after that every run seems to work, but without the -d switch it always gets jammed with a black screen, without loading the start menu.
Then do not do the test, this sounds like I can reproduce it this way.

Marten
#30
Hard to say, I have changed a lot during the last commit.
So we have to revert it, step by step.
1) First try, can you please use mutex.h and mutex.cc of the commit before. If it works, we already have to problem.
2) If this did not fix, it try to use the old boxstack.cc and boxstack.h with the new mutex files.

1 and 2 are unrelated, other changes are connected to optimizations in the rendering classes, so not so easy to disentangle for this:

3) It it would be helpful, if you attach the debugger using "gdb -tui -p PIDOFVOMP", you can get the pid of vomp using ps. Now, using "info threads" should give a list where all threads are. You can select every thread with "thread THREADNUMBER", now it getting information, where every thread is using, "bt" can help. 

Another question, before you only see the keep alive packets, are the log lines then always the same?
Furthermore what do you mean with "with debugging"? Compiling with debug symbols? With attached debugger?  ???  Maybe there is a way, where I can reproduce it... I tested everything with a debug build and with switch "-d".

Marten