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

#61
VOMP General / MVP / Re: Issues for next release
March 15, 2006, 22:31:30
Thanks Harry, I received your vdr files.

This is a different problem. Here, the actual timestamps transmitted by the TV station "jump" during the recording. The jump happens when "Hamburg Journal" starts and the music changes. This is also why VDR has split the file into pieces. If you play 002.vdr in mplayer, for example, you'll see that it starts at this point.

I'm guessing that 003.vdr starts when "Hamburg Journal" finishes, and then the timestamps are back in the original sequence. So the total length is correct when you play it, because vomp calculates the length from timestamps in 001.vdr and 003.vdr.

We assumed that timestamps would always be continuous, but it seems that some TV stations don't work this way. Have you seen things like this on recordings from other channels?

Mark
#62
VOMP General / MVP / Re: Issues for next release
March 15, 2006, 13:17:17
There is a known problem with reading timestamps from the video stream. Sometimes the VDR recording includes data that looks like a video timestamp, but it isn't. This shouldn't happen. I'm investigating and thinking about the best way to fix it, or work around it.

Harry: this is probably the cause of your weird display, and it could be to do with the way VDR has split the files, or just corrupted data in the file. Would it be possible to give me access to the 001.vdr file and the first 4 megabytes or so of 002.vdr? If you don't have any webspace where you can post it then you can email it if you like, provided it's only 8 MB or so:
m dot calderbank at iname dot com

MarkC
#63
VOMP General / MVP / Re: Dongle creation guide
February 08, 2006, 16:17:12
Sorry, I started writing my last post before I saw yours!

Remove the colon from the end of your LD_LIBRARY_PATH, or just unset LD_LIBRARY_PATH.

It might be possible to get the scripts to resume half-way through, but personally I'd start again from the beginning, just to be sure it's right.

MarkC
#64
VOMP General / MVP / Re: Dongle creation guide
February 08, 2006, 15:54:02
I've just built a toolchain and there's another problem at the end. You will probably get an error something like this:

We check GLIBC_EXTRA_CONFIG (--without-fp) to see if it contains
--without-fp to decide.
+ case "$GLIBC_EXTRA_CONFIG" in
+ cp -a /opt/crosstool/powerpc-405-linux-gnu/gcc-2.95.3-glibc-2.2.5/powerpc-405-linux-gnu/lib/nof/libstdc++-3-libc6.1-2-2.10.0.so /opt/crosstool/powerpc-405-linux-gnu/gcc-2.95.3-glibc-2.2.5/powerpc-405-linux-gnu/lib/nof/libstdc++-libc6.1-2.so.3 /opt/crosstool/powerpc-405-linux-gnu/gcc-2.95.3-glibc-2.2.5/powerpc-405-linux-gnu/lib
cp: cannot create regular file
`/opt/crosstool/powerpc-405-linux-gnu/gcc-2.95.3-glibc-2.2.5/powerpc-405-linux-gnu/lib/libstdc++-3-libc6.1-2-2.10.0.so':
Permission denied
Done.

This is because it's trying to overwrite a shared library that doesn't have write permissions.
The best thing to do is edit crosstool.sh, line 299, before running mvp-ppc405.sh:
299c299
<       cp -a ${PREFIX}/${TARGET}/lib/nof/*.so* ${PREFIX}/${TARGET}/lib
---
>       cp -af ${PREFIX}/${TARGET}/lib/nof/*.so* ${PREFIX}/${TARGET}/lib

If you have already started, don't worry, this is actually the very last part of the process! So you can just copy and paste the cp command, replacing -a with -af.
Then your toolchain should be complete and working.

MarkC
#65
VOMP General / MVP / Re: Dongle creation guide
February 08, 2006, 14:07:02
How strange. As you've probably noticed, it's just a difference in whitespace between the patch and the original file. It used to work though...!
Looks like the patch on loggytronic.com needs fixing.

At this stage, the quickest and easiest solution is to remove the crosstool-0.25 directory and start again from the beginning.
Before running "sh mvp-ppc405.sh", change line 65 of crosstool-0.25/getandpatch.sh:

65c65
<               patch -p1 -f < $p
---
>               patch -p1 -l -f < $p

Patch will then ignore differences in whitespace. I don't think this will have any unwanted effects.

Good luck!
MarkC