Skip to contentSkip to conversation

S2API (pctv452e) artefacts in video stream

linux-dvb Jens Krehbiel-Gräther 7 participants 11 messages Jan 5, 2009 – Jan 30, 2009 3 messages not in the archive Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

Hi!

I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is dvb-usb-pctv452e.

I use the repository from Igor Liplianin (actual hg release). The module compiles and loads fine. The scanning with scan-s2 and zapping with szap-s2 also wirk fine.
But when I record TV from the USB-device with "cat /dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the actual tv-station (zapped with "szap-s2 -r SAT.1" for example). This recorded video has artefacts, even missed frames.

Anyone else having this problem? I remember that on multiproto there was a similar problem with the pctv452e until Dominik Kuhlen patched somthing since then the video was OK. Is it possible that the same "error" is in the S2API-driver?

Regards,
Jens
<http://mercurial.intuxication.org/hg/s2-liplianin>

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#1 lore raw

Hi,

Quoted 13 lines · Jens Krehbiel-Gräther

Hi!

I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is dvb-usb-pctv452e.

I use the repository from Igor Liplianin (actual hg release). The module compiles and loads fine. The scanning with scan-s2 and zapping with szap-s2 also wirk fine.
But when I record TV from the USB-device with "cat /dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the actual tv-station (zapped with "szap-s2 -r SAT.1" for example). This recorded video has artefacts, even missed frames.

Quoted 4 lines

Anyone else having this problem? I remember that on multiproto there was a similar problem with the pctv452e until Dominik Kuhlen patched somthing since then the video was OK. Is it possible that the same "error" is in the S2API-driver?

I have similar problems with my SkyStar HD (stb0899), but I am still using the multiproto drivers.

Regards, Artem

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#2 lore raw
Quoted 24 lines · Artem Makhutov

Hi,

Quoted 13 lines · Jens Krehbiel-Gräther

Hi!

I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is dvb-usb-pctv452e.

I use the repository from Igor Liplianin (actual hg release). The module compiles and loads fine. The scanning with scan-s2 and zapping with szap-s2 also wirk fine.
But when I record TV from the USB-device with "cat /dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the actual tv-station (zapped with "szap-s2 -r SAT.1" for example). This recorded video has artefacts, even missed frames.

Quoted 4 lines

Anyone else having this problem? I remember that on multiproto there was a similar problem with the pctv452e until Dominik Kuhlen patched somthing since then the video was OK. Is it possible that the same "error" is in the S2API-driver?

I have similar problems with my SkyStar HD (stb0899), but I am still using the multiproto drivers.

Quoted 6 lines

Regards, Artem

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD with the S2API drivers from the Liplianin tree.

mfg

Edgar (gimli) Hucek

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#3 lore raw

i can confirm the very same problem symptoms with a technotrend dvb-s2 3600 usb device.

-----Original Message-----
From: gimli <[email protected]>
To: Artem Makhutov <[email protected]>
Cc: [email protected]
Sent: Mon, 5 Jan 2009 2:20 pm
Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

Quoted 24 lines · Artem Makhutov

Hi,

Quoted 13 lines · Jens Krehbiel-Gräther

Hi!

I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is dvb-usb-pctv452e.

I use the repository from Igor Liplianin (actual hg release). The module compiles and loads fine. The scanning with scan-s2 and zapping with szap-s2 also wirk fine.
But when I record TV from the USB-device with "cat /dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the actual tv-station (zapped with "szap-s2 -r SAT.1" for example). This recorded video has artefacts, even missed frames.

Quoted 4 lines

Anyone else having this problem? I remember that on multiproto there was a similar problem with the pctv452e until Dominik Kuhlen patched somthing since then the video was OK. Is it possible that the same "error" is in the S2API-driver?

I have similar problems with my SkyStar HD (stb0899), but I am still using the multiproto drivers.

Quoted 6 lines

Regards, Artem

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hi=2
0have also a similar problem on the TerraTec Cinergy S2 PCI HD with the S2API drivers from the Liplianin tree.

mfg

Edgar (gimli) Hucek

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#4 lore raw

Hi!

So this problem concerns more people and should be a general bug?? My device is working well in windows, so it could not be the dish, the cable or the device itself.

Can I do anything for debugging this problem? Let me know!

Jens

Quoted 103 lines · [email protected] schrieb:

i can confirm the very same problem symptoms with a technotrend dvb-s2 3600 usb device.

-----Original Message-----
From: gimli <[email protected]>
To: Artem Makhutov <[email protected]>
Cc: [email protected]
Sent: Mon, 5 Jan 2009 2:20 pm
Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

Quoted 4 lines · Artem Makhutov

Hi,

Quoted 31 lines
Quoted 29 lines · Jens Krehbiel-Gräther

Hi!

I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is

dvb-usb-pctv452e.

I use the repository from Igor Liplianin (actual hg release). The module

compiles and loads fine. The scanning with scan-s2 and zapping with

szap-s2 also wirk fine.

But when I record TV from the USB-device with "cat

/dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the actual

tv-station (zapped with "szap-s2 -r SAT.1" for example).

This recorded video has artefacts, even missed frames.

Anyone else having this problem? I remember that on multiproto there was

a similar prob

lem with the pctv452e until Dominik Kuhlen patched

Quoted 16 lines
Quoted 3 lines

somthing since then the video was OK. Is it possible that the same

"error" is in the S2API-driver?

I have similar problems with my SkyStar HD (stb0899), but I

am still using the multiproto drivers.

Regards, Artem

Quoted 7 lines

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD

with the S2API drivers from the Liplianin tree.

mfg

Edgar (gimli) Hucek

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

------------------------------------------------------------------------
Get a *free MP3* every day with the Spinner.com Toolbar. Get it Now
<http://toolbar.aol.com/spinner/download.html?ncid=emlweusdown00000020>.

Quoted 6 lines

------------------------------------------------------------------------

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#5 lore raw

Hi!

The same problem exists with my PCTV 400e. It seems to be problem with the USB part. When I enable USB-Debug- in the kernel, I get this:

ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
...
ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)

It's the same with 2.6.28 in-kernel-drivers and with the Igor Liplianin's tree.

(A also had this problem some years ago on a PPC-Mac-Mini. The workaround was to disable HIGHMEM. But it doesn't work now. I'm now on x86 32bit).

I also want to help. But how?

Best Regards,
darav

Am 12.01.2009 um 13:16 schrieb Jens Krehbiel-Gräther:

Quoted 129 lines

Hi!

So this problem concerns more people and should be a general bug?? My device is working well in windows, so it could not be the dish, the cable or the device itself.

Can I do anything for debugging this problem? Let me know!

Jens

Quoted 107 lines · [email protected] schrieb:

i can confirm the very same problem symptoms with a technotrend dvb- s2
3600 usb device.

-----Original Message-----
From: gimli <[email protected]>
To: Artem Makhutov <[email protected]>
Cc: [email protected]
Sent: Mon, 5 Jan 2009 2:20 pm
Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

Quoted 4 lines · Artem Makhutov

Hi,

Quoted 35 lines
Quoted 32 lines · Jens Krehbiel-Gräther

Hi!

I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is

dvb-usb-pctv452e.

I use the repository from Igor Liplianin (actual hg release). The module

compiles and loads fine. The scanning with scan-s2 and zapping with

szap-s2 also wirk fine.

But when I record TV from the USB-device with "cat

/dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the actual

tv-station (zapped with "szap-s2 -r SAT.1" for example).

This recorded video has artefacts, even missed frames.

Anyone else having this problem? I remember that on multiproto there was

a similar prob

lem with the pctv452e until Dominik Kuhlen patched

Quoted 16 lines
Quoted 3 lines

somthing since then the video was OK. Is it possible that the same

"error" is in the S2API-driver?

I have similar problems with my SkyStar HD (stb0899), but I

am still using the multiproto drivers.

Regards, Artem

Quoted 7 lines

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD

with the S2API drivers from the Liplianin tree.

mfg

Edgar (gimli) Hucek

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

------------------------------------------------------------------------
Get a *free MP3* every day with the Spinner.com Toolbar. Get it Now
<http://toolbar.aol.com/spinner/download.html?ncid=emlweusdown00000020

Quoted 8 lines
Quoted 1 line

.

------------------------------------------------------------------------

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Quoted 6 lines

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux- [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#6 lore raw

Hi again,

has anybody an idea what's going wrong here?
I'm still having this problem.
Is there anything I can do to help here?

Thanks in advance,
darav

Jan 28 12:03:09 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:11 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:11 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:11 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:13 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:13 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:13 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:15 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:15 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:15 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:17 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:17 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:17 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:19 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:19 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:19 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:21 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:21 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:21 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:23 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:23 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:23 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:25 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:25 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:25 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:27 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:27 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:27 vdr ttusb2: i2c transfer failed.

Am 12.01.2009 um 19:10 schrieb [email protected]:

Quoted 23 lines

Hi!

The same problem exists with my PCTV 400e. It seems to be problem with the USB part. When I enable USB-Debug- in the kernel, I get this:

ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
...
ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)

It's the same with 2.6.28 in-kernel-drivers and with the Igor Liplianin's tree.

(A also had this problem some years ago on a PPC-Mac-Mini. The workaround was to disable HIGHMEM. But it doesn't work now. I'm now on x86 32bit).

Quoted 144 lines

I also want to help. But how?

Best Regards,
darav

Am 12.01.2009 um 13:16 schrieb Jens Krehbiel-Gräther:

Quoted 136 lines

Hi!

So this problem concerns more people and should be a general bug?? My device is working well in windows, so it could not be the dish, the
cable or the device itself.

Can I do anything for debugging this problem? Let me know!

Jens

Quoted 108 lines · [email protected] schrieb:

i can confirm the very same problem symptoms with a technotrend dvb-s2
3600 usb device.

-----Original Message-----
From: gimli <[email protected]>
To: Artem Makhutov <[email protected]>
Cc: [email protected]
Sent: Mon, 5 Jan 2009 2:20 pm
Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

Quoted 4 lines · Artem Makhutov

Hi,

Quoted 36 lines
Quoted 33 lines · Jens Krehbiel-Gräther

Hi!

I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is

dvb-usb-pctv452e.

I use the repository from Igor Liplianin (actual hg release). The module

compiles and loads fine. The scanning with scan-s2 and zapping with

szap-s2 also wirk fine.

But when I record TV from the USB-device with "cat

/dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the actual

tv-station (zapped with "szap-s2 -r SAT.1" for example).

This recorded video has artefacts, even missed frames.

Anyone else having this problem? I remember that on multiproto there was

a similar prob

lem with the pctv452e until Dominik Kuhlen patched

Quoted 16 lines
Quoted 3 lines

somthing since then the video was OK. Is it possible that the same

"error" is in the S2API-driver?

I have similar problems with my SkyStar HD (stb0899), but I

am still using the multiproto drivers.

Regards, Artem

Quoted 7 lines

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD

with the S2API drivers from the Liplianin tree.

mfg

Edgar (gimli) Hucek

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

------------------------------------------------------------------------
Get a *free MP3* every day with the Spinner.com Toolbar. Get it Now
<http://toolbar.aol.com/spinner/download.html?ncid=emlweusdown00000020

Quoted 8 lines
Quoted 1 line

.

------------------------------------------------------------------------

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#7 lore raw
In reply to [email protected]

Hi again,

has anybody an idea what's going wrong here?
I'm still having this problem.
Is there anything I can do to help here?

Thanks in advance,
darav

P.S.: now posting on the new mailinglist. Sorry for double-post.

Jan 28 12:03:09 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:11 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:11 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:11 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:13 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:13 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:13 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:15 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:15 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 28 12:03:15 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:17 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:17 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:17 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:19 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:19 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 28 12:03:19 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:21 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:21 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:21 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:23 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:23 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 28 12:03:23 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:25 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:25 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 28 12:03:25 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:27 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:27 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:27 vdr ttusb2: i2c transfer failed.

Am 12.01.2009 um 19:10 schrieb [email protected]:

Quoted 156 lines

Hi!

The same problem exists with my PCTV 400e. It seems to be problem with the USB part. When I enable USB-Debug- in the kernel, I get this:

ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
...
ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)

It's the same with 2.6.28 in-kernel-drivers and with the Igor Liplianin's tree.

(A also had this problem some years ago on a PPC-Mac-Mini. The workaround was to disable HIGHMEM. But it doesn't work now. I'm now on x86 32bit).

I also want to help. But how?

Best Regards,
darav

Am 12.01.2009 um 13:16 schrieb Jens Krehbiel-Gräther:

Quoted 129 lines

Hi!

So this problem concerns more people and should be a general bug?? My device is working well in windows, so it could not be the dish, the cable or the device itself.

Can I do anything for debugging this problem? Let me know!

Jens

Quoted 102 lines · [email protected] schrieb:

i can confirm the very same problem symptoms with a technotrend dvb-s2 3600 usb device.

-----Original Message-----
From: gimli <[email protected]>
To: Artem Makhutov <[email protected]>
Cc: [email protected]
Sent: Mon, 5 Jan 2009 2:20 pm
Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

Quoted 4 lines · Artem Makhutov

Hi,

Quoted 31 lines
Quoted 29 lines · Jens Krehbiel-Gräther

Hi!

I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is

dvb-usb-pctv452e.

I use the repository from Igor Liplianin (actual hg release). The module

compiles and loads fine. The scanning with scan-s2 and zapping with

szap-s2 also wirk fine.

But when I record TV from the USB-device with "cat

/dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the actual

tv-station (zapped with "szap-s2 -r SAT.1" for example).

This recorded video has artefacts, even missed frames.

Anyone else having this problem? I remember that on multiproto there was

a similar prob

lem with the pctv452e until Dominik Kuhlen patched

Quoted 16 lines
Quoted 3 lines

somthing since then the video was OK. Is it possible that the same

"error" is in the S2API-driver?

I have similar problems with my SkyStar HD (stb0899), but I

am still using the multiproto drivers.

Regards, Artem

Quoted 7 lines

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD

with the S2API drivers from the Liplianin tree.

mfg

Edgar (gimli) Hucek

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

------------------------------------------------------------------------
Get a *free MP3* every day with the Spinner.com Toolbar. Get it Now
<http://toolbar.aol.com/spinner/download.html?ncid=emlweusdown00000020

Quoted 8 lines
Quoted 1 line

.

------------------------------------------------------------------------

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#8 lore raw
In reply to [email protected]

Hi again,

has anybody an idea what's going wrong here?
I'm still having this problem.
Is there anything I can do to help here?

Thanks in advance,
darav

P.S.: now posting on the new mailinglist. Sorry for double-post.

Jan 28 12:03:09 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:11 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:11 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:11 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:13 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:13 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:13 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:15 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:15 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 28 12:03:15 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:17 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:17 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:17 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:19 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:19 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 28 12:03:19 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:21 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:21 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:21 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:23 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:23 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 28 12:03:23 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:25 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:25 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 28 12:03:25 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:27 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:27 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 28 12:03:27 vdr ttusb2: i2c transfer failed.

Am 12.01.2009 um 19:10 schrieb [email protected]:

Quoted 156 lines

Hi!

The same problem exists with my PCTV 400e. It seems to be problem with the USB part. When I enable USB-Debug- in the kernel, I get this:

ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
...
ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)

It's the same with 2.6.28 in-kernel-drivers and with the Igor Liplianin's tree.

(A also had this problem some years ago on a PPC-Mac-Mini. The workaround was to disable HIGHMEM. But it doesn't work now. I'm now on x86 32bit).

I also want to help. But how?

Best Regards,
darav

Am 12.01.2009 um 13:16 schrieb Jens Krehbiel-Gräther:

Quoted 129 lines

Hi!

So this problem concerns more people and should be a general bug?? My device is working well in windows, so it could not be the dish, the cable or the device itself.

Can I do anything for debugging this problem? Let me know!

Jens

Quoted 102 lines · [email protected] schrieb:

i can confirm the very same problem symptoms with a technotrend dvb-s2 3600 usb device.

-----Original Message-----
From: gimli <[email protected]>
To: Artem Makhutov <[email protected]>
Cc: [email protected]
Sent: Mon, 5 Jan 2009 2:20 pm
Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

Quoted 4 lines · Artem Makhutov

Hi,

Quoted 31 lines
Quoted 29 lines · Jens Krehbiel-Gräther

Hi!

I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is

dvb-usb-pctv452e.

I use the repository from Igor Liplianin (actual hg release). The module

compiles and loads fine. The scanning with scan-s2 and zapping with

szap-s2 also wirk fine.

But when I record TV from the USB-device with "cat

/dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the actual

tv-station (zapped with "szap-s2 -r SAT.1" for example).

This recorded video has artefacts, even missed frames.

Anyone else having this problem? I remember that on multiproto there was

a similar prob

lem with the pctv452e until Dominik Kuhlen patched

Quoted 16 lines
Quoted 3 lines

somthing since then the video was OK. Is it possible that the same

"error" is in the S2API-driver?

I have similar problems with my SkyStar HD (stb0899), but I

am still using the multiproto drivers.

Regards, Artem

Quoted 7 lines

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD

with the S2API drivers from the Liplianin tree.

mfg

Edgar (gimli) Hucek

_______________________________________________

linux-dvb mailing list

[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

------------------------------------------------------------------------
Get a *free MP3* every day with the Spinner.com Toolbar. Get it Now
<http://toolbar.aol.com/spinner/download.html?ncid=emlweusdown00000020

Quoted 8 lines
Quoted 1 line

.

------------------------------------------------------------------------

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#9 lore raw
Quoted 11 lines · [email protected] wrote:

Hi again,

has anybody an idea what's going wrong here?
I'm still having this problem.
Is there anything I can do to help here?

Thanks in advance,
darav

P.S.: now posting on the new mailinglist. Sorry for double-post.

Quoted 9 lines
Jan 28 12:03:09 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:11 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:11 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:11 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:13 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:13 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:13 vdr ttusb2: i2c transfer failed.

Looks like the demodulator did not respond at all, maybe it went bad. Does your device work in a windows environment ?

Regards,
Manu

#13 lore raw
In reply to a message not in the archive

Hi Manu,
Hello together,

in the meantime I was able to test the device on windows. It works without any problems for over an hour.

Also I tried again different SAT- und USB-cables.
Also with all other USB-devices dettached - the error still comes.

First I'm getting "TS continuity errors"
and after a while (let's say 15 minutest) ...

Jan 30 14:42:20 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 30 14:42:20 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
Jan 30 14:42:20 vdr ttusb2: i2c transfer failed.
Jan 30 14:42:22 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 30 14:42:22 vdr ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
Jan 30 14:42:22 vdr ttusb2: i2c transfer failed.
Jan 30 14:42:24 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 30 14:42:24 vdr ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)

Thanks for your help!
darav