Hi,
MIB-II last weekend was apparently sent in HDTV on separate PIDs. According to http://www.golem.de/0504/37384.html, the parameters were
ASTRA 1F Transponder Nr. 16 Frequenz : 11.4355 GHz Polarisation: vertikal Symbolrate : 22 MS/s QPSK FEC : 5/6 Network ID: 0x0085 Original Network ID: 0x0085 Transport StreamID: 0x0006 Service ID: 0x0292 PMT PID: 0x0060 Video PID: 0x00FF 1920x1080i, 50Hz PCR PID: 0x00FF Audio PID: 0x0103 DolbyDigital Service Name: ProSieben HD Service Provider: ProSiebenSat1
channels.conf line, anyone? My VDR didn't seem to find the channel itself. Should
ProSiebenHD;ProSiebenSat.1:11435:v:S19.2E:22000:255:256;259:0:0:658:133:6:0
work? I am not sure about the normal audio PID (if there is any, anyways).
hi
channels.conf line, anyone? My VDR didn't seem to find the channel itself. Should ProSiebenHD;ProSiebenSat.1:11435:v:S19.2E:22000:255:256;259:0:0:658:133:6:0
work? I am not sure about the normal audio PID (if there is any, anyways).
my line: ProSieben HD:11436:v:S19.2E:22000:255:257;259:0:0:658:0:0:0
it worked. i recorded parts of the movie as test.
bye, manuel.
On Tue, Apr 12, 2005 at 09:10:58PM +0200, Harald Milz wrote:
ProSiebenHD;ProSiebenSat.1:11435:v:S19.2E:22000:255:256;259:0:0:658:133:6:0
ProSiebenHD;ProSiebenSat.1:11435:vC56:S19.2E:22000:255:257=deu;259=deu:0:2:658:133:6:0
which is almost the same and is the one my VDR found (and working). (CA is set here to 2 as my budget card is the second card).
Manuel Hartl wrote:
hi
channels.conf line, anyone? My VDR didn't seem to find the channel itself. Should ProSiebenHD;ProSiebenSat.1:11435:v:S19.2E:22000:255:256;259:0:0:658:133:6:0
work? I am not sure about the normal audio PID (if there is any, anyways).
my line: ProSieben HD:11436:v:S19.2E:22000:255:257;259:0:0:658:0:0:0
it worked. i recorded parts of the movie as test.
I know it can only be *recorded* with a budget card. How do you replay it? Does the FF card/driver also crash when you try to replay such a recording on it?
Cheers,
Carsten.
Carsten Koch wrote:
it worked. i recorded parts of the movie as test.
I know it can only be *recorded* with a budget card. How do you replay it? Does the FF card/driver also crash when you try to replay such a recording on it?
Playing it back also crashes a FF card.
But asked again: Some claim, it definately can´t be recorded, then there is a document about a modification for the 1.x cards to make them able to record it. This modification was said to be the already done on V2.x cards (Nexus). Additionally, I have seen somebody last year receiving a HDTV channel using a FF card and ProgDVB (Win) with a software decoder.
So, what is the "real" situation with FF cards and HDTV?
Joerg
hi
my line: ProSieben HD:11436:v:S19.2E:22000:255:257;259:0:0:658:0:0:0
it worked. i recorded parts of the movie as test.
I know it can only be *recorded* with a budget card. How do you replay it? Does the FF card/driver also crash when you try to replay such a recording on it?
first: i recorded the movie with a FF card (i only have FF cards) (i did not watch the whole movie..see below. maybe the limited bandwidth of the FF cards disturbs recording somewhere in the movie...)
second: driver/vdr crashes when you try to replay.
i used mplayer (in X) to replay the movie. my systems seems to be at the edge of performance for HDTV replays...
bye.
hi
But asked again: Some claim, it definately can´t be recorded, then there is a document about a modification for the 1.x cards to make them able to record it. This modification was said to be the already done on V2.x cards (Nexus). Additionally, I have seen somebody last year receiving a HDTV channel using a FF card and ProgDVB (Win) with a software decoder.
So, what is the "real" situation with FF cards and HDTV?
i recorded a movie with a FF 1.3. at least parts of the movie a correct (i assume the whole movie..i did not watch the whole recording, as my system is a little bit to slow to enjoy the movie)
playback on vdr / FF 1.3 crashes as you said.
manuel.
Joerg Knitter wrote:
But asked again: Some claim, it definately can´t be recorded, then there is a document about a modification for the 1.x cards to make them able to record it. This modification was said to be the already done on V2.x cards (Nexus). Additionally, I have seen somebody last year receiving a HDTV channel using a FF card and ProgDVB (Win) with a software decoder.
So, what is the "real" situation with FF cards and HDTV?
Some users have said that the FF card HDTV support has improved in the current dvb-kernel drivers, and you can actually record many (if not all) HDTV-channels.
Anssi Hannula wrote:
Joerg Knitter wrote:
But asked again: Some claim, it definately can´t be recorded, then there is a document about a modification for the 1.x cards to make them able to record it. This modification was said to be the already done on V2.x cards (Nexus). Additionally, I have seen somebody last year receiving a HDTV channel using a FF card and ProgDVB (Win) with a software decoder.
So, what is the "real" situation with FF cards and HDTV?
Some users have said that the FF card HDTV support has improved in the current dvb-kernel drivers, and you can actually record many (if not all) HDTV-channels.
I am using kernel 2.6.11 and the drivers that come with it. When I tuned the (1.3) FF card to the ProSieben HD channel, it crashed. So I changed the channel entry CA field and allowed mu budget card only on that channel. Now the FF card indirectly shows the channel via transfer mode and still crashes. :-(
Is that fixed in a later kernel or in the CVS drivers?
Cheers,
Carsten.
Carsten Koch wrote:
I am using kernel 2.6.11 and the drivers that come with it. When I tuned the (1.3) FF card to the ProSieben HD channel, it crashed. So I changed the channel entry CA field and allowed mu budget card only on that channel. Now the FF card indirectly shows the channel via transfer mode and still crashes. :-(
Is that fixed in a later kernel or in the CVS drivers?
How should this work? This would require the HDTV signal to be downscaled to 720x576 and reencoded to MPEG1 or MPEG2 with 16:9 flag.
Joerg
Joerg Knitter wrote: ...
How should this work? This would require the HDTV signal to be downscaled to 720x576 and reencoded to MPEG1 or MPEG2 with 16:9 flag.
I do not know how hard it might be to actually replay such a stream properly on a FF card, but why should it be impossible to record the stream with a FF card? And why does it have to crash?
Carsten.
Carsten Koch wrote:
I do not know how hard it might be to actually replay such a stream properly on a FF card, but why should it be impossible to record the stream with a FF card? And why does it have to crash?
My two euro cents follows.
My channels.conf says:
ProSieben HD;ProSiebenSat.1:11435:vC56:S19.2E:22000:255:257=deu;259=deu:0:0:658:133:6:0
My syslog says about my dvb cards:
Apr 13 20:00:03 vdr kernel: cx88[0]: subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T [card=18,autodetected] Apr 13 20:00:03 vdr kernel: cx88[0]/0: found at 0000:02:0c.0, rev: 5, irq: 20, latency: 32, mmio: 0xf3000000 Apr 13 20:00:03 vdr kernel: cx88[1]: subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T [card=18,autodetected] Apr 13 20:00:03 vdr kernel: cx88[1]/0: found at 0000:02:0d.0, rev: 5, irq: 21, latency: 32, mmio: 0xf0000000 Apr 13 20:00:04 vdr kernel: cx88[0]/2: cx2388x based dvb card Apr 13 20:00:04 vdr kernel: DVB: registering new adapter (cx88[0]). Apr 13 20:00:04 vdr kernel: DVB: registering frontend 0 (Hauppauge Nova-T DVB-T) Apr 13 20:00:04 vdr kernel: cx88[1]/2: found at 0000:02:0d.2, rev: 5, irq: 21, latency: 32, mmio: 0xf1000000 Apr 13 20:00:04 vdr kernel: cx88[1]/2: cx2388x based dvb card Apr 13 20:00:04 vdr kernel: DVB: registering new adapter (cx88[1]). Apr 13 20:00:04 vdr kernel: DVB: registering frontend 1 (Hauppauge Nova-T DVB-T) Apr 13 20:00:04 vdr kernel: saa7146: found saa7146 @ mem f8a7cc00 (revision 1, irq 22) (0x13c2,0x0003). Apr 13 20:00:04 vdr kernel: DVB: registering new adapter (Technotrend/Hauppauge WinTV Nexus-S rev2.X). Apr 13 20:00:04 vdr kernel: adapter has MAC addr = 00:d0:5c:22:cf:1a Apr 13 20:00:05 vdr kernel: DVB: registering frontend 2 (ST STV0299 DVB-S)...
I am running VDR 1.3.23 with some plugins.
My kernel is "2.6.11.6-kraxel1", with DVB driver patches from bytesex.org. I had to install this bleeding edge driver stuff in order to get the new Hauppauge DVB-T cards with conexant chipset to work.
I tune to a dvb-t channel to avoid _viewing_ of the HDTV channel and create a timer to record a sample of the HDTV transmission.
The result: I get lotsa data on my hard disk. :)
Watching TV from dvb-t during the HDTV recording becomes a mess, though. The picture and sound will stutter VERY badly during HDTV recording. After deleting the timer, vdr will behave normally again.
Linux mplayer seems to playback the HDTV reconrding (almost) properly, so the stream seems to be ok. Sound is working too.
Switching "livetv" to the HDTV channel will mess up the screen completely, which was what I supposed. VDR or the firmware does not seem to crash. I can get VDR to change to another channel after quite a long delay after pressing a remote control button.
P.S. what is this?
C MORE HDTV;Telenor:11261:hC78:S1.0W:24500:517:660=eng:0:B00:3306:70:33:0
I don't have the Canal+ movie channels enabled on my smartcard right now, so I could not test this myself.
Carsten Koch wrote:
Joerg Knitter wrote: ...
How should this work? This would require the HDTV signal to be downscaled to 720x576 and reencoded to MPEG1 or MPEG2 with 16:9 flag.
I do not know how hard it might be to actually replay such a stream properly on a FF card, but why should it be impossible to record the stream with a FF card? And why does it have to crash?
I thought you spoke about replaying. Recording must be possible (and some agreed to this), but playing back can´t be possible for sure unless you really downscale it.
Streaming boxes with certain Sigma chips etc. are great, but streamdev is in heavy development (at least I hope so regarding to all those patches to get it run) and unfortunately does not support UPnP - because this combined with real-time transcoding (like Nero Digital Home does this on Windows) would be a really great solution.
Joerg
On Wed, 13 Apr 2005, "Sami J. Mäkinen" wrote:
ProSieben HD;ProSiebenSat.1:11435:vC56:S19.2E:22000:255:257=deu;259=deu:0:0:658:133:6:0
Huh.
Does prosieben actually work in Finland?
I looked at some footprints and the beam was weak at Finland (except western coast). http://www.ses-astra.com/satellites/footprints.php?sat=10
I have multifocus dish and manufacturer says it's about 70-75cm per satellite. Does anyone have any experience with multifocus and prosieben in southern Finland?
Antti Hartikainen wrote:
ProSieben HD;ProSiebenSat.1:11435:vC56:S19.2E:22000:255:257=deu;259=deu:0:0:658:133:6:0
Huh. Does prosieben actually work in Finland?
I did not make this up. :)
I looked at some footprints and the beam was weak at Finland (except western coast). http://www.ses-astra.com/satellites/footprints.php?sat=10
I have multifocus dish and manufacturer says it's about 70-75cm per satellite. Does anyone have any experience with multifocus and prosieben in southern Finland?
My dish setup is as follows:
1) Triax multifocus with four LNB:s Astra1, Hotbird, Sirius and Thor (S19.2E, S13.0E, S5.0E, S1.0W)
2) A regular 80cm dish for Eurobird/Astra2 (S28.2E)
DiSeqC setup is like this:
# LNB Diagram: # # --------------------- # | 4-port switch |-- to receiver # --------------------- # 1 2 3 4 # | | | | # 19.2E 13.0E 28.2E A/B # LNB LNB LNB | | # 5.0E 1.0W # LNB LNB
http://almamedia.fi:8000/~sjm/kuvia/2004/20040511/med/IMG_0011.JPG
I wrote a diseqc.conf by hand for my setup. A diseqc documentation pdf from eutelsat was of great help.
I live in Siuro, Nokia. That is 25km West of Tampere. Prosieben works just fine, along with many other channels. :)
-
"Sami J. Mäkinen" -
Anssi Hannula -
Antti Hartikainen -
Carsten Koch -
Grégoire Favre -
Harald Milz -
Joerg Knitter -
Manuel Hartl