Hello,
I would like to get my STB playing back video streams from streamdev-server.
The stream is transmitted my streamdev using IP-Multicast and can be
played back without any problems with VLC, but the STB has big problems
with the stream. The stream itself is from the ASTRA HD+ demo channel.
In the stream I can see a lot of clear-text messages like:
"Wilde Abenteuer und jede Menge Spaß und Action mit dem Tasmanischen
Teufel" or "Der geht brutal gegen die Rebellen in den Wäldern vor. Bei
…
[View More]ihrer Ankunft trifft Ofelia auf einen mysteriösen Faun"
I does not look like this messages belong to the stream (they do not
look like subtiles or audio-track descriptions).
Could this be some kind of EPG data, or what is this?
When streaming this recording using VLC as streaming server the STB can
playback the stream without any problems, as this messages are removed
by VLC.
I have captured a few seconds of the stream:
http://www.makhutov.org/downloads/adb/hdtv.pcaphttp://www.makhutov.org/downloads/adb/hdtv.ts
Can you help me identifying what this messages are?
Thanks, Artem
[View Less]
Hello,
VDR (1.6.0-2) crashed after stuffing the syslog with:
vdr: [24126] ERROR: possible result buffer overflow, dropped 13 out of
13 byte
vdr: [24126] ERROR: possible result buffer overflow, dropped 2048 out of
2048 byte
A backtrace shows that the function cTS2PES::write_ipack (initially
called from cTS2PES::instant_repack with Count=184) kept calling itself
(from then on with Count=180 and the same "Data" pointer all the time).
The variable "bite" was 4 on the first call and then 0 on …
[View More]all succeeding
ones.
It was a video pid being extracted, so the cVideoRepacker got called,
and I suspect its "breakAt" return value lead to the "// should never
happen" code that set "bite" to 0.
Some state information from the cTS2PES instance:
pid=1023 size=2052 found=2200 count=2052
cid=224 rewriteCid=224 subStreamId=0
plength=4194234 plen[0]=98 plen[1]=124 flag1=flag2=0 hlength=0 mpeg=0
check=0 mpeg1_required=mpeg1_stuffing=0
done=true
tsErrors=2020124 ccErrors=697951
ccCounter=8
The high error counts obviously show that the received data (from DVB-S)
was somehow defective (There were many "PES packet shortened" errors
earlier), but ideally VDR shouldn't crash even when the data is broken...
Can anyone please fix this issue?
Greetings,
Andreas
[View Less]
Op Di, 25 november, 2008 03:59, schreef VDR User:
> On Mon, Nov 24, 2008 at 9:46 AM, Nicolas Huillard <nicolas(a)huillard.net>
> wrote:
>> It's still good news to know that open-source software allowing current
>> fanless integrated motherboards to decode HDTV at ~10% CPU is on its
>> way...
>>
>> Going from 87% of 2 cores, to ~10% of an entry level CPU is good,
>> specially when the load is taken care of by existing chips.
>
I agree on that …
[View More]point. I would rather have ~10% or ~20% then the regular
57% per core on my Core 2 Quad system when I view H264 channels of my
provider.
> Yes, I agree. Just pointing out that you certainly do not need a quad
> core, that's all. Also, the price of the cpu is the same whether
> you're using 87% or 10% of it. ;) The point is you can already have
> cheap HDTV without using the new Nvidia api.
>
Well, in my case I do. When I view BBCHD, ArteHD, AnixeHD or the AstraHD
channels I don't encounter many problems. Image is clear and no stutter.
But as soon as I watch the 1080i/H264 channels of my provider (Canal
Digitaal) on Astra 23.5e, I have major stuttering. BravaTV in HD doesn't
have much problems, but NGC HD and Discovery HD is an other matter. My
Core 2 Duo just couldn't handle it with FFMPeg and Xine-lib 1.2. But since
I've put in a Core 2 Quad, I'm able to watch those channels even with fast
moving images :)
>> I'd like to have full-HDTV on a single x86 mini-ITX board. I'm now
>> seeing this will happen soon enough, and I'll wait until then before I
>> spend money on new hardware.
>
> Yes it's nice! My goal is diskless, fanless, low power consumption
> dedicated HDTV box. Very small, very low cost!
>
I again agree :) I would like an additional HDTV box in my bedroom. It
needs to have the options you wrote. But I don't want a Popcorn or some
other kind of device. I want the option to enhance it myself (flexability)
so I'm waiting desperately for GPU based decoding of H264 and VC-1
transport streams :)
Niels Wagenaar
[View Less]
Dears developers of such nice these plugins/patch
are you planing to adapt your plugins to vdr 172 ? Will someone release h264 patch for vdr 172 ?
Goga
The attached patch is what I've gathered from various postings
regarding adapting VDR to the S2API driver API (thanks to
Igor M. Liplianin, Niels Wagenaar and Edgar Hucek - did I forget anybody?).
Since the S2SAPI doesn't provide a way of determining whether
a DVB-S device supports DVB-S2 (at least I didn't find any),
you need to apply the second attached patch to the driver
in order to impelement a new capability flag that reports
the availability of DVB-S2 support.
If you don't want to …
[View More]patch the driver, you can change the line
case FE_QPSK: frontendType = (frontendInfo.caps & FE_CAN_2ND_GEN_MODULATION) ? SYS_DVBS2 : SYS_DVBS; break;
in dvbdevice.c to avoid FE_CAN_2ND_GEN_MODULATION. Either set frontendType permanently
to SYS_DVBS or SYS_DVBS2, depending on what you have.
So far DVB-S and DVB-S2 appears to tune fine.
DVB-C is completely untested.
With DVB-T tuning doesn't work, even though my TDA10046H based DVB-T card
does work with the S2API driver under VDR 1.6.0.
So for the moment I would appreciate if people could test DVB-T
tuning and check whether maybe I made some silly mistake in the
DVB-T tuning code.
Klaus
[View Less]
Hello!
This is the first release of the VDR Teletext Subtitles plug-in from
http://projects.vdr-developer.org.
New develpment site:
http://projects.vdr-developer.org/projects/show/plg-ttxtsubs
Downloads:
http://projects.vdr-developer.org/projects/list_files/plg-osdteletext
Git-Web:
http://projects.vdr-developer.org/git/?p=vdr-plugin-osdteletext.git
Anonymous Git-access :
git://projects.vdr-developer.org/vdr-plugin-osdteletext.git
For the required VDR-patches, I've also set up …
[View More]a Git-Repository, based on
the one maintained by Dieter Hametner:
http://projects.vdr-developer.org/git/?p=vdr-patches.git;a=summarygit://projects.vdr-developer.org/vdr-patches.git
Special thanks go to Rolf Ahrenberg for sending me a lot of patches!
This is now intended to be a community maintained project! Don't expect me
to fix your problems, I'm merely maintaining the project!
Please report any bugs, ideas or feature requests to the project site (no
registration required for this!). If you want to contribute patches, new
features or whatever, post an issue or patch to the projects issue tracker
or request to join the project. I would happily add everyone as a project
member, who would like to contribute to the project!
If you want to contribute but don't know what to do - start with some code
refactoring!
Recent Changes:
- Applied patch from Rolf Ahrenberg which introduces the following
changes:
- Rolf Ahrenberg
- Updated the core patch and Makefile against VDR's current API
- Added font, color, and DVB source selection
- Added UTF8 support
- Added layered OSD support
- Fixed EPG scan hiccups
- Fixed several race conditions in destructors
- Silenced compilation warnings
- Vyacheslav Diconov
- Russian translation
- Ville SkyttÃa
- fixed crash in plugin shutdown
- cleaned up logging to use syslog
- Thomas GÃŒnther
- German translation
- Michaël Nival
- Added missing const declarations
- French translation
- Luca Olivetti
- Fixed displaying subtitles setting
- Added a thread based subtitles scanner
- Added delay settings
- Tobias Grimm
- Added manual page selection mode
- Switched completely to VDR 1.6's I18N system and removed the old crap
no more support for older VDR versions!
- Removed VDR*.patch and Checkpatch.sh and added up-to-date VDR patches
into into "patches" subdirectory (thx to Rolf Ahrenberg)
- Removed location lines from *.po (thx to Rolf Ahrenberg)
- Fixed wrong GPL license text (wrong FSF address)
- Clarified license (it's GPL-2 or any later) and added a licence
header to every source file
[View Less]
Hello,
here my lastest release of vdr-image plugin...
There none further improvements planed.
Changes:
========
- Updated italian translation
- Add turkish translation
- Clear device buffer, before start playback (need by PVR350)
- Reimplement "Playback mode via 'DeviceStillPicture'"
active if 'Send encoded frame several times' set to 'no'
- Check for codec only at startup
- Add setup option to hide main menu entry
- Use now gettext for i18n texts, introduced with vdr-1.5.8 (Required)
- …
[View More]for build now 'pkg-config' needed
- Use swscale to converting image
What is it :
============
This is a plugin for vdr and allows the display of digital images, like
jpeg, tiff, png, bmp and some more, on the TV screen, using the DVB out
device from vdr.
Depends:
========
see included README for more details
netpbm, or as alternative imagemagick
ffmpeg
libexif
Link :
======
Homepage : http://vdr-image.berlios.de/
Download : http://download.berlios.de/vdr-image/vdr-image-0.3.0.tar.gz
Cu,
Andreas
[View Less]
Hi all!
I'm using Hannos vdr-extensions repository for my Ubuntu intrepid ibex.
I have for some time now tried to set up the Autosort-plugin without any
success. According to the logs, the plugin starts, creates a bunch of
groups (I'm using the example-config). But when it reaches the last
group, vdr restarts:
Here is my log:
.
..
...
Dec 14 14:32:15 vdr vdr: [18668] OSD: AutoSort: Creating Group 'WrongCa'
Dec 14 14:32:15 vdr vdr: [18668] OSD: AutoSort: Creating Group 'Old
Channels'
Dec 14 …
[View More]14:32:15 vdr vdr: [18668] OSD: AutoSort: Creating Group 'Unsorted'
Dec 14 14:32:15 vdr vdr: [18668] saved setup to /var/lib/vdr/setup.conf
Dec 14 14:32:15 vdr vdr: [18654] text2skin: loading
/var/lib/vdr/plugins/text2skin/Motz/Motz.colors
Dec 14 14:32:15 vdr vdr: [18654] parsing
/var/lib/vdr/plugins/text2skin/Motz/Motz.skin
Dec 14 14:32:15 vdr vdr: [18654] text2skin: loading
/var/lib/vdr/plugins/text2skin/enElchi/enElchi.colors
Dec 14 14:32:15 vdr vdr: [18654] parsing
/var/lib/vdr/plugins/text2skin/enElchi/enElchi.skin
Dec 14 14:32:15 vdr vdr: [18654] text2skin: loading
/var/lib/vdr/plugins/text2skin/Enigma/Enigma.colors
Dec 14 14:32:15 vdr vdr: [18654] parsing
/var/lib/vdr/plugins/text2skin/Enigma/Enigma.skin
Dec 14 14:32:15 vdr runvdr: restarting VDR
I tested also by uninstalling all vdr-modules, and running vdr just with
the Autosort-plugin. Same result.
I would appreciate any ideas, help etc that could help me getting
Autosort to work on my vdr-box.
Best Regards,
René
-=-=-
... No amount of planning will ever replace dumb luck.
[View Less]