Re: Afatech AF9013
On Mon, 2011-08-29 at 20:40 +0200, Josu Lazkano wrote: > 2011/8/23 Jason Hecker : > > Damn, this patch didn't help so maybe forget this patch. Tuner A is > > still messed up. > > > > Hello, thanks all to reply this post. I have no idea how to apply the > patch on my Debian Squeeze. Can you help to apply the patch? > > Thanks your all your help. It is best applied using media_build and using a copy from the patchwork server. You can just copy the raw email to a text file, but sometimes it is malformed. Since you originally used s2-liplianin you just need patchutils to apply it to that. However, since it is older, I doubt it will apply cleanly. https://patchwork.kernel.org/patch/1090012/ For media build, check if the required packages for Debian Squeeze are the same as Ubuntu. But, it appears the patch makes no difference. Regards Malcolm MEDIA BUILD INSTALL (Instructions here are for Ubuntu) Using Terminal install git, patchutils and perl with sudo apt-get install git(or git-core) sudo apt-get install patchutils sudo apt-get install libdigest-sha1-perl sudo apt-get install libproc-processtable-perl Always build somewhere in your home directory with local user rights. Only use super user rights to install. git clone git://linuxtv.org/media_build.git cd media_build ---NO PATCH--- ./build sudo make install ---PATCH TO BE APPLIED--- Download any patch and place in the media_build directory and apply in the following way. ./build (skip this if already built) Wait for download and start to build. If you are confident that the build will complete without errors break the build with C Apply the patch. Make sure if applying multipliable patches they are applied oldest first. Just test the patch. patch -d linux -p1 --dry-run < the_patch_name.patch If okay apply it. patch -d linux -p1 < the_patch_name.patch make distclean make sudo make install More in depth instructions here http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
2011/8/23 Jason Hecker : > Damn, this patch didn't help so maybe forget this patch. Tuner A is > still messed up. > Hello, thanks all to reply this post. I have no idea how to apply the patch on my Debian Squeeze. Can you help to apply the patch? Thanks your all your help. Best regards. -- Josu Lazkano -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Re: Afatech AF9013 [TEST ONLY] AF9015 stream buffer size aligned with max packet size.
> I think what might happening is that TS packets are getting chopped, as > device seems to want > to align to max packet size. Oh, I also noticed that the Linux driver uses a smaller USB packet count than Windows. Is there any discernible reason for this? Lag on DVB isn't an issue for me and probably everyone else due to the stream going to secondary storage first. Great, I'll try it out later. I have been studying the source code and noticed that the bus locking mechanism is TODOed and may be part of the problem. My symptom is that Tuner A fails when Tuner B is started and I have a theory that somehow the TDA18271 is getting some I2C data and being corrupted because of a gating problem with the I2C signal. The TDA18271 can change the last 2 bits of it's default I2C address by setting a voltage on its AS pin (presumably with resistor dividers) but I haven't delved in to determine if this what Leadtek have done - both tuners might be set to address 0xC0. I can only truly test this by putting CRO probe on and seeing if the I2C is going down the wrong path at the wrong time. I just wish ITE/Afa would release their data sheet to the public and make it as detailed and USEFUL as the TDA18271 data sheet. This obfuscation, need for NDAs and a half arsed data sheet and bloody sniffing Windows USB transactions for programming clues is such a waste of time and I fail to see how it benefits ITE to do this. The Afatech chips are 4+ years old anyway - what's the problem? If anyone wants to send me the data sheets and more importantly the DESIGN MANUAL from the devkit I'd be most grateful. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] Re: Afatech AF9013 [TEST ONLY] AF9015 stream buffer size aligned with max packet size.
On Tue, 2011-08-23 at 11:47 +1000, Jason Hecker wrote:
> Damn, this patch didn't help so maybe forget this patch. Tuner A is
> still messed up.
Try this patch, applied to the latest media_build. it aligns buffer size to the
max packet
size instead of TS packet size.
I think what might happening is that TS packets are getting chopped, as device
seems to want
to align to max packet size.
Afatech seem to want create rather large buffers at considerable delay. The
size of the buffer
has also been considerably reduced. If you want to increase it change
TS_USB20_PACKET_COUNT
in multiplies of 2 (56 ... 112).
---
drivers/media/dvb/dvb-usb/af9015.c | 13 +++--
1 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/media/dvb/dvb-usb/af9015.c
b/drivers/media/dvb/dvb-usb/af9015.c
index d7ad05f..eaf0800 100644
--- a/drivers/media/dvb/dvb-usb/af9015.c
+++ b/drivers/media/dvb/dvb-usb/af9015.c
@@ -404,21 +404,22 @@ static int af9015_init_endpoint(struct dvb_usb_device *d)
We use smaller - about 1/4 from the original, 5 and 87. */
#define TS_PACKET_SIZE188
-#define TS_USB20_PACKET_COUNT 87
-#define TS_USB20_FRAME_SIZE (TS_PACKET_SIZE*TS_USB20_PACKET_COUNT)
-
#define TS_USB11_PACKET_COUNT 5
#define TS_USB11_FRAME_SIZE (TS_PACKET_SIZE*TS_USB11_PACKET_COUNT)
-#define TS_USB20_MAX_PACKET_SIZE 512
+#define TS_USB20_MAX_PACKET_SIZE 128
#define TS_USB11_MAX_PACKET_SIZE 64
+#define TS_USB20_PACKET_COUNT 28
+#define TS_USB20_FRAME_SIZE (TS_USB20_MAX_PACKET_SIZE\
+ *TS_USB20_PACKET_COUNT)
+
if (d->udev->speed == USB_SPEED_FULL) {
frame_size = TS_USB11_FRAME_SIZE/4;
packet_size = TS_USB11_MAX_PACKET_SIZE/4;
} else {
- frame_size = TS_USB20_FRAME_SIZE/4;
- packet_size = TS_USB20_MAX_PACKET_SIZE/4;
+ frame_size = TS_USB20_FRAME_SIZE;
+ packet_size = TS_USB20_MAX_PACKET_SIZE;
}
ret = af9015_set_reg_bit(d, 0xd507, 2); /* assert EP4 reset */
--
1.7.4.1
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
Damn, this patch didn't help so maybe forget this patch. Tuner A is still messed up. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
I might have found one bug so far with the Afa9013 driver. As part of refactoring the code in http://git.linuxtv.org/linux-2.6.git/commitdiff/edb709b61abd3ba475e59d1ad81aab21ad025db6 I think one of the u32->u8 calculations is wrong. The think the second last u32 in the tables has to be changed. Here is the diff. I will try it later as I have run out of time to test it this morning. This may not fix the problems we are having but it might help... So patch the file af9013_priv.h with this in the latest git media_build and see what happens. I'll report back later with my results. af9013_priv.h.diff -- 74c74 < 0x29, 0x03, 0x5d, 0x7a, 0xec, 0x01, 0x45, 0x14, 0x14 } }, --- > 0x29, 0x00, 0xa2, 0x85, 0x14, 0x01, 0x45, 0x14, 0x14 } }, 77c77 < 0xe4, 0x03, 0x71, 0xcb, 0xe8, 0x01, 0x1c, 0x71, 0x32 } }, --- > 0xe4, 0x00, 0x8e, 0x34, 0x72, 0x01, 0x1c, 0x71, 0x32 } }, 80c80 < 0x9e, 0x03, 0x86, 0x1c, 0x31, 0x00, 0xf3, 0xcf, 0x0f } }, --- > 0x9e, 0x00, 0x79, 0xe3, 0xcf, 0x00, 0xf3, 0xcf, 0x0f } }, 84c84 < 0x49, 0x03, 0x1b, 0x74, 0xdb, 0x01, 0xc9, 0x24, 0x25 } }, --- > 0x49, 0x00, 0xe4, 0x8b, 0x25, 0x01, 0xc9, 0x24, 0x25 } }, 87c87 < 0x00, 0x03, 0x38, 0x06, 0x40, 0x01, 0x90, 0x00, 0x00 } }, --- > 0x00, 0x00, 0xc7, 0xf9, 0xc0, 0x01, 0x90, 0x00, 0x00 } }, 90c90 < 0xb7, 0x03, 0x54, 0x97, 0xa4, 0x01, 0x56, 0xdb, 0x1c } }, --- > 0xb7, 0x00, 0xab, 0x68, 0x5c, 0x01, 0x56, 0xdb, 0x1c } }, 94c94 < 0x05, 0x03, 0x58, 0xd6, 0x34, 0x01, 0x4e, 0x5e, 0x03 } }, --- > 0x05, 0x00, 0xa7, 0x29, 0xcc, 0x01, 0x4e, 0x5e, 0x03 } }, 97c97 < 0x25, 0x03, 0x6d, 0xbb, 0x6e, 0x01, 0x24, 0x92, 0x12 } }, --- > 0x25, 0x00, 0x92, 0x44, 0x92, 0x01, 0x24, 0x92, 0x12 } }, 100c100 < 0x44, 0x03, 0x82, 0xa0, 0xa7, 0x00, 0xfa, 0xc6, 0x22 } }, --- > 0x44, 0x00, 0x7d, 0x5f, 0x59, 0x00, 0xfa, 0xc6, 0x22 } }, 104c104 < 0xe7, 0x03, 0x44, 0xc6, 0xf3, 0x01, 0x76, 0x7d, 0x34 } }, --- > 0xe7, 0x00, 0xbb, 0x39, 0x0d, 0x01, 0x76, 0x7d, 0x34 } }, 107c107 < 0x0a, 0x03, 0x5c, 0x2e, 0x14, 0x01, 0x47, 0xae, 0x05 } }, --- > 0x0a, 0x00, 0xa3, 0xd1, 0xec, 0x01, 0x47, 0xae, 0x05 } }, 110c110 < 0x2d, 0x03, 0x73, 0x95, 0x36, 0x01, 0x18, 0xde, 0x17 } }, --- > 0x2d, 0x00, 0x8c, 0x6a, 0xca, 0x01, 0x18, 0xde, 0x17 } }, -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
2011/8/22 Jason Hecker : > I just tried LiveCDs of Mythbuntu 10.04 and 10.10 but had limited luck > with the former and some joy with the latter. Unfortunately the > default framebuffer slowed things down. Anyway in LiveCD 10.10 I used > mplayer to set up and view Tuner A and Tuner B and Tuner A only showed > some slight errors when Tuner B was being set up. After that for some > strange reason attempt at retuning with mplayer failed utterly so I > suspect there is some problems with the older versions of mplayer. > > These cards have blue LEDs for each tuner and light up when in use. I > did notice in my testing that the LED on tuner A would flicker off > briefly (and presumably issue the errors) when Tuner B was being set > up. I am wondering if there is a general setup problem or even a I2S > timing problem. Could someone contact me off list about sending me > the data sheets for the AF901x chips? > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Hello again, yesterday I try to connect the KWorld USB Dual DVB-T TV Stick (DVB-T 399U) on my HTPC, I start MythTV and both tuners were working great, I could record a channel and watch an other one, both HD. But 2 hours later they start to watch bad, with pixeled images: http://dl.dropbox.com/u/1541853/kworld.3gp I don't know what happens with this tuner. I have two identical ones and both have same issues. I could share a SSH root access to everyone that want to test the tuner. I will install a fresh Debian Squeeze on my laptop and give full access to the machine. Anyone interested? I don't know what else to try with it. Thanks and best regards. -- Josu Lazkano -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
I just tried LiveCDs of Mythbuntu 10.04 and 10.10 but had limited luck with the former and some joy with the latter. Unfortunately the default framebuffer slowed things down. Anyway in LiveCD 10.10 I used mplayer to set up and view Tuner A and Tuner B and Tuner A only showed some slight errors when Tuner B was being set up. After that for some strange reason attempt at retuning with mplayer failed utterly so I suspect there is some problems with the older versions of mplayer. These cards have blue LEDs for each tuner and light up when in use. I did notice in my testing that the LED on tuner A would flicker off briefly (and presumably issue the errors) when Tuner B was being set up. I am wondering if there is a general setup problem or even a I2S timing problem. Could someone contact me off list about sending me the data sheets for the AF901x chips? -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
On Sun, 2011-08-21 at 11:51 +1000, Jason Hecker wrote: > I have tried everything imaginable to nail down the problem but can't > seem to fix it. Even "options dvb-usb force_pid_filter_usage=1" seems > to improve the problem somewhat but the errors are still there. I > have tried every firmware from 4.65 to 5.10, adjusting the PCI latency > from 32 to 96, fed each card directly from the antenna (taking the > splitter out of the loop), one card fitted, both cards fitted, kernel > and system upgrades (Mythbuntu 10.04 to 11.04), mplayer vs MythTV but > the results are always the same. Tuner B is perfect, tuner A > corrupts when Tuner B is used. There are no errors or warnings in > syslog or dmesg to > suggest anything has failed. I think there is a BUG, where on some systems, the frontends become swapped between kernels 2.6.35 and 2.6.38 on dual tuners. I haven't fully investigated the cause, but I think it's to do with applying a later build of dvb-usb to an earlier kernel. So, Tuner B on 2.6.38(11.04) is the old Tuner A. Regards Malcolm -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
Hello again, thanks Jason for your reply. It is interesting to ear that is not just my problem. I add the dual device on a laptop with same kernel 2.6.32. It works well, both tuners working great with no pixeled images. Two weeks ago, I must change my HTPC power supply, a 300W PFC. I had some problems when connecting a 2,5 USB drive (it use to shutdown). On the local shop they test it and there are more than 5V on the USB, so they change it. How can I test the USB? Is there any USB debug tool? I don't know how to continue with this, thanks for all your help, best regards. 2011/8/21 Jason Hecker : > I have a problem that may be related to the issues on this thread and > it's driving me nuts. > > I have two dual tuner Afatech based cards, they are both Leadtek > 2000DS cards, one made by Leadtek and the other branded as KWorld but > they are otherwise identical in spite of different VID:PID. > > On each card tuner A is an AF9015 and tuner B is an AF9013. The > KWorld card worked just fine for about 18 months in Mythbuntu 10.04 > with the rebuilt and patched modules as described in the Wiki entry on > the 2000DS. A few weeks ago tuner A started giving errors making the > viewing unwatchable so figuring the card had died I bought the > Leadtek. To my surprise it gave the same problem as the KWorld when > using tuner A. It seems Tuner A is OK until Tuner B is used and then > Tuner A gets a lot of errors. Tuner B never has errors. I did try > using the latest "media_build" from V4L but that didn't help. > > So, I installed Mythbuntu 11.04 and with both cards I > still get the same problem. Watching live TV with MythTV or with > mplayer on tuner A gives errors and tuner B is always flawless even > with "media_build" updates. > > I honestly can't recall if when the failure first occurred if I had > done a routine kernel update at that time - though it would have just > been the usual 2.6.32 update that is in line with 10.04 maintenance. > > I have tried everything imaginable to nail down the problem but can't > seem to fix it. Even "options dvb-usb force_pid_filter_usage=1" seems > to improve the problem somewhat but the errors are still there. I > have tried every firmware from 4.65 to 5.10, adjusting the PCI latency > from 32 to 96, fed each card directly from the antenna (taking the > splitter out of the loop), one card fitted, both cards fitted, kernel > and system upgrades (Mythbuntu 10.04 to 11.04), mplayer vs MythTV but > the results are always the same. Tuner B is perfect, tuner A > corrupts when Tuner B is used. There are no errors or warnings in > syslog or dmesg to > suggest anything has failed. > > I'd appreciate any suggestions at this point as I am pretty unhappy > with the situation considering it *used* to work. > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Josu Lazkano -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
I have a problem that may be related to the issues on this thread and it's driving me nuts. I have two dual tuner Afatech based cards, they are both Leadtek 2000DS cards, one made by Leadtek and the other branded as KWorld but they are otherwise identical in spite of different VID:PID. On each card tuner A is an AF9015 and tuner B is an AF9013. The KWorld card worked just fine for about 18 months in Mythbuntu 10.04 with the rebuilt and patched modules as described in the Wiki entry on the 2000DS. A few weeks ago tuner A started giving errors making the viewing unwatchable so figuring the card had died I bought the Leadtek. To my surprise it gave the same problem as the KWorld when using tuner A. It seems Tuner A is OK until Tuner B is used and then Tuner A gets a lot of errors. Tuner B never has errors. I did try using the latest "media_build" from V4L but that didn't help. So, I installed Mythbuntu 11.04 and with both cards I still get the same problem. Watching live TV with MythTV or with mplayer on tuner A gives errors and tuner B is always flawless even with "media_build" updates. I honestly can't recall if when the failure first occurred if I had done a routine kernel update at that time - though it would have just been the usual 2.6.32 update that is in line with 10.04 maintenance. I have tried everything imaginable to nail down the problem but can't seem to fix it. Even "options dvb-usb force_pid_filter_usage=1" seems to improve the problem somewhat but the errors are still there. I have tried every firmware from 4.65 to 5.10, adjusting the PCI latency from 32 to 96, fed each card directly from the antenna (taking the splitter out of the loop), one card fitted, both cards fitted, kernel and system upgrades (Mythbuntu 10.04 to 11.04), mplayer vs MythTV but the results are always the same. Tuner B is perfect, tuner A corrupts when Tuner B is used. There are no errors or warnings in syslog or dmesg to suggest anything has failed. I'd appreciate any suggestions at this point as I am pretty unhappy with the situation considering it *used* to work. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
2011/8/17 Antti Palosaari : > On 08/17/2011 10:36 AM, Josu Lazkano wrote: >> I don't know how wide is the stream, but it could be a USB wide >> limitation. My board is a little ION based and I have some USB >> devices: >> $ lsusb >> Bus 001 Device 002: ID 1b80:e399 Afatech >> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I don't think so. Total under 50Mbit/sec stream should not be too much > for one USB2.0 root hub. > > Which is chipset used ION (it is southbridge which contains usually USB > ports)? > >> The problematic twin device is the "Afatech" one, there is an DVB-S2 >> USB tuner, a bluetooth dongle, a IR receiver and a wireless >> mouse/keybord receiver. >> >> Now I am at work, I will try to disconnect all devices and try with >> just the DVB-T device. >> >> I use to try with MythTV if it works or not. Is there any other tool >> to test and debug more deep about USB or DVB wide? > > You can look stream sizes using dvbtraffic tool. It is last line of > output which shows total stream size. > > tzap can be used to tune channel. But it you can use some other app like > MythTV and then run dvbtraffic same time. > >> I apreciate your help. Thanks and best regards. > > regards > Antti > > -- > http://palosaari.fi/ > Thanks Antti, I don't know the chipset model, my board is this one: ZOTAC ION ITX-G Synergy Edition: http://www.zotac.com/pdbrochures/mb/ION-ITX-G-E-Synergy-Edition_v1.3.pdf On the BIOS there is something about southbridge, but now I am connected remotely so I can not access to the BIOS, I must change something on the BIOS? I make this steps to record a TV channel: 1. Scan with w_scan with both adapters: w_scan -a 2 -ft -c ES >> canales1_TDT.conf w_scan -a 3 -ft -c ES >> canales2_TDT.conf Here is the output and the channel files: http://dl.dropbox.com/u/1541853/w_scan1 http://dl.dropbox.com/u/1541853/canales1_TDT.conf http://dl.dropbox.com/u/1541853/w_scan2 http://dl.dropbox.com/u/1541853/canales2_TDT.conf I think there is something wrong, because there must be more channels as TVE 1, La 2... How can I tune the correct channel? I try this: $ tzap -a 2 -c canales1_TDT.conf -r "TELECINCO" using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' reading channels from file 'canales1_TDT.conf' ERROR: could not find channel 'TELECINCO' in channel list I want to try to tune the channel and record it with gnutv and see if there is any problem. Thanks for the dvbtraffic tool. Thanks for all your help, best regards. -- Josu Lazkano -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
On Wed, 2011-08-17 at 19:27 +0200, Josu Lazkano wrote: > 2011/8/17 Malcolm Priestley : > > On Wed, 2011-08-17 at 01:23 +0200, Jose Alberto Reguero wrote: > >> On Martes, 16 de Agosto de 2011 22:57:24 Antti Palosaari escribió: > >> > On 08/16/2011 11:27 PM, Jose Alberto Reguero wrote: > >> > >> options dvb-usb force_pid_filter_usage=1 > >> > >> > >> > >> I change the signal timeout and tuning timeout and now it works > >> > >> perfect! > >> > >> > >> > >> I can watch two HD channels, thanks for your help. > >> > >> > >> > >> I really don't understand what force_pid_filter_usage do on the > >> > >> module, is there any documentation? > >> > >> > >> > >> Thanks and best regards. > >> > > > >> > > For usb devices with usb 2.0 when tunned to a channel there is enought > >> > > usb bandwith to deliver the whole transponder. With pid filters they > >> > > only deliver the pids needed for the channel. The only limit is that > >> > > the > >> > > pid filters is limited normaly to 32 pids. > >> > > >> > May I ask how wide DVB-T streams you have? Here in Finland it is about > >> > 22 Mbit/sec and I think two such streams should be too much for one USB > >> > bus. I suspect there is some other bug in back of this. > >> > > >> > regards > >> > Antti > >> > >> Here the transport stream is like yours. About 4 Mbit/sec by channel, and > >> about 5 channels by transport stream. The problem I have is that when I > >> have > >> the two tuners working I have a few packets lost, and I have some TS > >> discontinuitys. With pid filters the stream is perfect. Perhaps Josu have > >> another problem. > > > > I am certain it is the configuration of the second frontend that ripples > > through Afatech devices. > > > > I have only got a single AF9015 device so can't test the dual > > configuration. > > > > Does the same problems exist when running the second frontend solo or > > dual with the Windows driver? > > > > With the IT1937(aka AF9035) the second frontend appeared not to work at > > all in Windows in dual mode. > > > > tvboxspy > > > > > > Thanks Malcolm, sorry but I don't understand very good your post (my > poor english). > > On Microsoft Windows XP the dual device works great, I can watch two > different channels (different transponder). > > I want to know if there is an other command-line tool to test them, > because it will be MythTV playback problem. > > The most problem is that sometimes one adapter work, then no adapter > work and then both adapter work but there is no clear image (pixeled). > > How could I test if there is some packet drop? Looks like you need pid filtering on, but if you force the pid filter on, it won't work because there is no functions setup for it on the driver for the second frontend. btw, you need to force the pid filter on at boot time, add a line in file. /etc/modules (or /etc/modules.preload) dvb_usb force_pid_filter_usage=1 Otherwise, it keeps going off. But, it will only work on the first frontend(adapter). It works fine on my single one. Regards Malcolm -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
On 08/17/2011 10:36 AM, Josu Lazkano wrote: > I don't know how wide is the stream, but it could be a USB wide > limitation. My board is a little ION based and I have some USB > devices: > $ lsusb > Bus 001 Device 002: ID 1b80:e399 Afatech > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I don't think so. Total under 50Mbit/sec stream should not be too much for one USB2.0 root hub. Which is chipset used ION (it is southbridge which contains usually USB ports)? > The problematic twin device is the "Afatech" one, there is an DVB-S2 > USB tuner, a bluetooth dongle, a IR receiver and a wireless > mouse/keybord receiver. > > Now I am at work, I will try to disconnect all devices and try with > just the DVB-T device. > > I use to try with MythTV if it works or not. Is there any other tool > to test and debug more deep about USB or DVB wide? You can look stream sizes using dvbtraffic tool. It is last line of output which shows total stream size. tzap can be used to tune channel. But it you can use some other app like MythTV and then run dvbtraffic same time. > I apreciate your help. Thanks and best regards. regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
2011/8/17 Malcolm Priestley : > On Wed, 2011-08-17 at 01:23 +0200, Jose Alberto Reguero wrote: >> On Martes, 16 de Agosto de 2011 22:57:24 Antti Palosaari escribió: >> > On 08/16/2011 11:27 PM, Jose Alberto Reguero wrote: >> > >> options dvb-usb force_pid_filter_usage=1 >> > >> >> > >> I change the signal timeout and tuning timeout and now it works perfect! >> > >> >> > >> I can watch two HD channels, thanks for your help. >> > >> >> > >> I really don't understand what force_pid_filter_usage do on the >> > >> module, is there any documentation? >> > >> >> > >> Thanks and best regards. >> > > >> > > For usb devices with usb 2.0 when tunned to a channel there is enought >> > > usb bandwith to deliver the whole transponder. With pid filters they >> > > only deliver the pids needed for the channel. The only limit is that the >> > > pid filters is limited normaly to 32 pids. >> > >> > May I ask how wide DVB-T streams you have? Here in Finland it is about >> > 22 Mbit/sec and I think two such streams should be too much for one USB >> > bus. I suspect there is some other bug in back of this. >> > >> > regards >> > Antti >> >> Here the transport stream is like yours. About 4 Mbit/sec by channel, and >> about 5 channels by transport stream. The problem I have is that when I have >> the two tuners working I have a few packets lost, and I have some TS >> discontinuitys. With pid filters the stream is perfect. Perhaps Josu have >> another problem. > > I am certain it is the configuration of the second frontend that ripples > through Afatech devices. > > I have only got a single AF9015 device so can't test the dual > configuration. > > Does the same problems exist when running the second frontend solo or > dual with the Windows driver? > > With the IT1937(aka AF9035) the second frontend appeared not to work at > all in Windows in dual mode. > > tvboxspy > > Thanks Malcolm, sorry but I don't understand very good your post (my poor english). On Microsoft Windows XP the dual device works great, I can watch two different channels (different transponder). I want to know if there is an other command-line tool to test them, because it will be MythTV playback problem. The most problem is that sometimes one adapter work, then no adapter work and then both adapter work but there is no clear image (pixeled). How could I test if there is some packet drop? Thanks for your great help. Best regards. -- Josu Lazkano -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
On Wed, 2011-08-17 at 01:23 +0200, Jose Alberto Reguero wrote: > On Martes, 16 de Agosto de 2011 22:57:24 Antti Palosaari escribió: > > On 08/16/2011 11:27 PM, Jose Alberto Reguero wrote: > > >> options dvb-usb force_pid_filter_usage=1 > > >> > > >> I change the signal timeout and tuning timeout and now it works perfect! > > >> > > >> I can watch two HD channels, thanks for your help. > > >> > > >> I really don't understand what force_pid_filter_usage do on the > > >> module, is there any documentation? > > >> > > >> Thanks and best regards. > > > > > > For usb devices with usb 2.0 when tunned to a channel there is enought > > > usb bandwith to deliver the whole transponder. With pid filters they > > > only deliver the pids needed for the channel. The only limit is that the > > > pid filters is limited normaly to 32 pids. > > > > May I ask how wide DVB-T streams you have? Here in Finland it is about > > 22 Mbit/sec and I think two such streams should be too much for one USB > > bus. I suspect there is some other bug in back of this. > > > > regards > > Antti > > Here the transport stream is like yours. About 4 Mbit/sec by channel, and > about 5 channels by transport stream. The problem I have is that when I have > the two tuners working I have a few packets lost, and I have some TS > discontinuitys. With pid filters the stream is perfect. Perhaps Josu have > another problem. I am certain it is the configuration of the second frontend that ripples through Afatech devices. I have only got a single AF9015 device so can't test the dual configuration. Does the same problems exist when running the second frontend solo or dual with the Windows driver? With the IT1937(aka AF9035) the second frontend appeared not to work at all in Windows in dual mode. tvboxspy -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
2011/8/17 Jose Alberto Reguero : > On Martes, 16 de Agosto de 2011 22:57:24 Antti Palosaari escribió: >> On 08/16/2011 11:27 PM, Jose Alberto Reguero wrote: >> >> options dvb-usb force_pid_filter_usage=1 >> >> >> >> I change the signal timeout and tuning timeout and now it works perfect! >> >> >> >> I can watch two HD channels, thanks for your help. >> >> >> >> I really don't understand what force_pid_filter_usage do on the >> >> module, is there any documentation? >> >> >> >> Thanks and best regards. >> > >> > For usb devices with usb 2.0 when tunned to a channel there is enought >> > usb bandwith to deliver the whole transponder. With pid filters they >> > only deliver the pids needed for the channel. The only limit is that the >> > pid filters is limited normaly to 32 pids. >> >> May I ask how wide DVB-T streams you have? Here in Finland it is about >> 22 Mbit/sec and I think two such streams should be too much for one USB >> bus. I suspect there is some other bug in back of this. >> >> regards >> Antti > > Here the transport stream is like yours. About 4 Mbit/sec by channel, and > about 5 channels by transport stream. The problem I have is that when I have > the two tuners working I have a few packets lost, and I have some TS > discontinuitys. With pid filters the stream is perfect. Perhaps Josu have > another problem. > > Jose Alberto > Thanks both! I don't know how wide is the stream, but it could be a USB wide limitation. My board is a little ION based and I have some USB devices: $ lsusb Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 002 Device 005: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless keyboard/mouse Bus 002 Device 004: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver Bus 002 Device 003: ID 9022:d660 TeVii Technology Ltd. DVB-S2 S660 Bus 002 Device 002: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1b80:e399 Afatech Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The problematic twin device is the "Afatech" one, there is an DVB-S2 USB tuner, a bluetooth dongle, a IR receiver and a wireless mouse/keybord receiver. Now I am at work, I will try to disconnect all devices and try with just the DVB-T device. I use to try with MythTV if it works or not. Is there any other tool to test and debug more deep about USB or DVB wide? I apreciate your help. Thanks and best regards. -- Josu Lazkano -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
On Martes, 16 de Agosto de 2011 22:57:24 Antti Palosaari escribió: > On 08/16/2011 11:27 PM, Jose Alberto Reguero wrote: > >> options dvb-usb force_pid_filter_usage=1 > >> > >> I change the signal timeout and tuning timeout and now it works perfect! > >> > >> I can watch two HD channels, thanks for your help. > >> > >> I really don't understand what force_pid_filter_usage do on the > >> module, is there any documentation? > >> > >> Thanks and best regards. > > > > For usb devices with usb 2.0 when tunned to a channel there is enought > > usb bandwith to deliver the whole transponder. With pid filters they > > only deliver the pids needed for the channel. The only limit is that the > > pid filters is limited normaly to 32 pids. > > May I ask how wide DVB-T streams you have? Here in Finland it is about > 22 Mbit/sec and I think two such streams should be too much for one USB > bus. I suspect there is some other bug in back of this. > > regards > Antti Here the transport stream is like yours. About 4 Mbit/sec by channel, and about 5 channels by transport stream. The problem I have is that when I have the two tuners working I have a few packets lost, and I have some TS discontinuitys. With pid filters the stream is perfect. Perhaps Josu have another problem. Jose Alberto -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
On 08/16/2011 11:27 PM, Jose Alberto Reguero wrote: >> options dvb-usb force_pid_filter_usage=1 >> >> I change the signal timeout and tuning timeout and now it works perfect! >> >> I can watch two HD channels, thanks for your help. >> >> I really don't understand what force_pid_filter_usage do on the >> module, is there any documentation? >> >> Thanks and best regards. >> > > For usb devices with usb 2.0 when tunned to a channel there is enought usb > bandwith to deliver the whole transponder. With pid filters they only deliver > the pids needed for the channel. The only limit is that the pid filters is > limited normaly to 32 pids. May I ask how wide DVB-T streams you have? Here in Finland it is about 22 Mbit/sec and I think two such streams should be too much for one USB bus. I suspect there is some other bug in back of this. regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
On Martes, 16 de Agosto de 2011 18:37:49 Josu Lazkano escribió: > Thanks again, I edit /etc/modprobe.d/options.conf > > options dvb_usb_af9015 adapter_nr=4,5 > options dvb-usb disable_rc_polling=1 > options dvb-usb force_pid_filter_usage=1 > > I change the signal timeout and tuning timeout and now it works perfect! > > I can watch two HD channels, thanks for your help. > > I really don't understand what force_pid_filter_usage do on the > module, is there any documentation? > > Thanks and best regards. > For usb devices with usb 2.0 when tunned to a channel there is enought usb bandwith to deliver the whole transponder. With pid filters they only deliver the pids needed for the channel. The only limit is that the pid filters is limited normaly to 32 pids. Jose Alberto > 2011/8/16 Jose Alberto Reguero : > > On Martes, 16 de Agosto de 2011 00:22:05 Josu Lazkano escribió: > >> 2011/8/16 Jose Alberto Reguero : > >> > I have problems with a dual usb tuner. I limit the bandwith using pid > >> > filters and the problem was gone. > >> > > >> > Jose alberto > >> > > >> > On Lunes, 15 de Agosto de 2011 15:34:20 Josu Lazkano escribió: > >> >> Hello, I have a problem with the KWorld USB Dual DVB-T TV Stick > >> >> (DVB-T 399U): > >> >> http://www.linuxtv.org/wiki/index.php/KWorld_USB_Dual_DVB-T_TV_Stick_ > >> >> (DV B- T_399U) > >> >> > >> >> I am using it on MythTV with Debian Squeeze (2.6.32). It is a dual > >> >> device, sometimes the second adapter works great, but sometimes has a > >> >> pixeled images. The first adapter always has pixeled images, I don't > >> >> know how to describe the pixeled images, so here is a mobile record: > >> >> http://dl.dropbox.com/u/1541853/kworld.3gp > >> >> > >> >> I have this firmware: > >> >> http://palosaari.fi/linux/v4l-dvb/firmware/af9015/5.1.0.0/dvb-usb-af9 > >> >> 015 .fw > >> >> > >> >> I read on the linuxtv wiki and there are some problems with dual > >> >> mode, there is some links for how to patch the similar driver > >> >> (Afatech/ITE IT9135), but I am not good enough to understand the > >> >> code. > >> >> > >> >> I check the kernel messages: > >> >> > >> >> Aug 15 13:53:58 htpc kernel: [ 516.285369] af9013: I2C read failed > >> >> reg:d2e6 Aug 15 13:54:29 htpc kernel: [ 547.407504] af9013: I2C read > >> >> failed reg:d330 Aug 15 13:54:44 htpc kernel: [ 561.902710] af9013: > >> >> I2C read failed reg:d2e6 > >> >> > >> >> It looks I2C problem, but I don't know how to debug it deeper. > >> >> > >> >> I don't know if this is important, but I compile the s2-liplianin for > >> >> other devices this way: > >> >> > >> >> apt-get install linux-headers-`uname -r` build-essential > >> >> mkdir /usr/local/src/dvb > >> >> cd /usr/local/src/dvb > >> >> wget > >> >> http://mercurial.intuxication.org/hg/s2-liplianin/archive/tip.zip > >> >> unzip s2-liplianin-0b7d3cc65161.zip > >> >> cd s2-liplianin-0b7d3cc65161 > >> >> make CONFIG_DVB_FIREDTV:=n > >> >> make install > >> >> > >> >> Can you help with this? This hardware is a very cheap and works well > >> >> for HD channels but, I don't know why sometimes has pixeled images. > >> >> > >> >> Thanks for your help, best regards. > >> > >> Thanks Jose Alberto, I search on google for pid filters but I don't > >> find any interesting info. > >> > >> How can I limit bandwidth on dvb? > >> > >> Thanks for your help, I have two dual devices waiting for this fix on my > >> HTPC. > >> > >> Best regards. > > > > If the driver has pid filters you can enable it with the parameter > > force_pid_filter_usage=1 of dvb-usb. > > > > Jose Alberto -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
Thanks again, I edit /etc/modprobe.d/options.conf options dvb_usb_af9015 adapter_nr=4,5 options dvb-usb disable_rc_polling=1 options dvb-usb force_pid_filter_usage=1 I change the signal timeout and tuning timeout and now it works perfect! I can watch two HD channels, thanks for your help. I really don't understand what force_pid_filter_usage do on the module, is there any documentation? Thanks and best regards. 2011/8/16 Jose Alberto Reguero : > On Martes, 16 de Agosto de 2011 00:22:05 Josu Lazkano escribió: >> 2011/8/16 Jose Alberto Reguero : >> > I have problems with a dual usb tuner. I limit the bandwith using pid >> > filters and the problem was gone. >> > >> > Jose alberto >> > >> > On Lunes, 15 de Agosto de 2011 15:34:20 Josu Lazkano escribió: >> >> Hello, I have a problem with the KWorld USB Dual DVB-T TV Stick (DVB-T >> >> 399U): >> >> http://www.linuxtv.org/wiki/index.php/KWorld_USB_Dual_DVB-T_TV_Stick_(DV >> >> B- T_399U) >> >> >> >> I am using it on MythTV with Debian Squeeze (2.6.32). It is a dual >> >> device, sometimes the second adapter works great, but sometimes has a >> >> pixeled images. The first adapter always has pixeled images, I don't >> >> know how to describe the pixeled images, so here is a mobile record: >> >> http://dl.dropbox.com/u/1541853/kworld.3gp >> >> >> >> I have this firmware: >> >> http://palosaari.fi/linux/v4l-dvb/firmware/af9015/5.1.0.0/dvb-usb-af9015 >> >> .fw >> >> >> >> I read on the linuxtv wiki and there are some problems with dual mode, >> >> there is some links for how to patch the similar driver (Afatech/ITE >> >> IT9135), but I am not good enough to understand the code. >> >> >> >> I check the kernel messages: >> >> >> >> Aug 15 13:53:58 htpc kernel: [ 516.285369] af9013: I2C read failed >> >> reg:d2e6 Aug 15 13:54:29 htpc kernel: [ 547.407504] af9013: I2C read >> >> failed reg:d330 Aug 15 13:54:44 htpc kernel: [ 561.902710] af9013: I2C >> >> read failed reg:d2e6 >> >> >> >> It looks I2C problem, but I don't know how to debug it deeper. >> >> >> >> I don't know if this is important, but I compile the s2-liplianin for >> >> other devices this way: >> >> >> >> apt-get install linux-headers-`uname -r` build-essential >> >> mkdir /usr/local/src/dvb >> >> cd /usr/local/src/dvb >> >> wget http://mercurial.intuxication.org/hg/s2-liplianin/archive/tip.zip >> >> unzip s2-liplianin-0b7d3cc65161.zip >> >> cd s2-liplianin-0b7d3cc65161 >> >> make CONFIG_DVB_FIREDTV:=n >> >> make install >> >> >> >> Can you help with this? This hardware is a very cheap and works well >> >> for HD channels but, I don't know why sometimes has pixeled images. >> >> >> >> Thanks for your help, best regards. >> >> Thanks Jose Alberto, I search on google for pid filters but I don't >> find any interesting info. >> >> How can I limit bandwidth on dvb? >> >> Thanks for your help, I have two dual devices waiting for this fix on my >> HTPC. >> >> Best regards. > > If the driver has pid filters you can enable it with the parameter > force_pid_filter_usage=1 of dvb-usb. > > Jose Alberto > -- Josu Lazkano -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
On Martes, 16 de Agosto de 2011 00:22:05 Josu Lazkano escribió: > 2011/8/16 Jose Alberto Reguero : > > I have problems with a dual usb tuner. I limit the bandwith using pid > > filters and the problem was gone. > > > > Jose alberto > > > > On Lunes, 15 de Agosto de 2011 15:34:20 Josu Lazkano escribió: > >> Hello, I have a problem with the KWorld USB Dual DVB-T TV Stick (DVB-T > >> 399U): > >> http://www.linuxtv.org/wiki/index.php/KWorld_USB_Dual_DVB-T_TV_Stick_(DV > >> B- T_399U) > >> > >> I am using it on MythTV with Debian Squeeze (2.6.32). It is a dual > >> device, sometimes the second adapter works great, but sometimes has a > >> pixeled images. The first adapter always has pixeled images, I don't > >> know how to describe the pixeled images, so here is a mobile record: > >> http://dl.dropbox.com/u/1541853/kworld.3gp > >> > >> I have this firmware: > >> http://palosaari.fi/linux/v4l-dvb/firmware/af9015/5.1.0.0/dvb-usb-af9015 > >> .fw > >> > >> I read on the linuxtv wiki and there are some problems with dual mode, > >> there is some links for how to patch the similar driver (Afatech/ITE > >> IT9135), but I am not good enough to understand the code. > >> > >> I check the kernel messages: > >> > >> Aug 15 13:53:58 htpc kernel: [ 516.285369] af9013: I2C read failed > >> reg:d2e6 Aug 15 13:54:29 htpc kernel: [ 547.407504] af9013: I2C read > >> failed reg:d330 Aug 15 13:54:44 htpc kernel: [ 561.902710] af9013: I2C > >> read failed reg:d2e6 > >> > >> It looks I2C problem, but I don't know how to debug it deeper. > >> > >> I don't know if this is important, but I compile the s2-liplianin for > >> other devices this way: > >> > >> apt-get install linux-headers-`uname -r` build-essential > >> mkdir /usr/local/src/dvb > >> cd /usr/local/src/dvb > >> wget http://mercurial.intuxication.org/hg/s2-liplianin/archive/tip.zip > >> unzip s2-liplianin-0b7d3cc65161.zip > >> cd s2-liplianin-0b7d3cc65161 > >> make CONFIG_DVB_FIREDTV:=n > >> make install > >> > >> Can you help with this? This hardware is a very cheap and works well > >> for HD channels but, I don't know why sometimes has pixeled images. > >> > >> Thanks for your help, best regards. > > Thanks Jose Alberto, I search on google for pid filters but I don't > find any interesting info. > > How can I limit bandwidth on dvb? > > Thanks for your help, I have two dual devices waiting for this fix on my > HTPC. > > Best regards. If the driver has pid filters you can enable it with the parameter force_pid_filter_usage=1 of dvb-usb. Jose Alberto -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
2011/8/16 Jose Alberto Reguero : > I have problems with a dual usb tuner. I limit the bandwith using pid filters > and the problem was gone. > > Jose alberto > > On Lunes, 15 de Agosto de 2011 15:34:20 Josu Lazkano escribió: >> Hello, I have a problem with the KWorld USB Dual DVB-T TV Stick (DVB-T >> 399U): >> http://www.linuxtv.org/wiki/index.php/KWorld_USB_Dual_DVB-T_TV_Stick_(DVB- >> T_399U) >> >> I am using it on MythTV with Debian Squeeze (2.6.32). It is a dual >> device, sometimes the second adapter works great, but sometimes has a >> pixeled images. The first adapter always has pixeled images, I don't >> know how to describe the pixeled images, so here is a mobile record: >> http://dl.dropbox.com/u/1541853/kworld.3gp >> >> I have this firmware: >> http://palosaari.fi/linux/v4l-dvb/firmware/af9015/5.1.0.0/dvb-usb-af9015.fw >> >> I read on the linuxtv wiki and there are some problems with dual mode, >> there is some links for how to patch the similar driver (Afatech/ITE >> IT9135), but I am not good enough to understand the code. >> >> I check the kernel messages: >> >> Aug 15 13:53:58 htpc kernel: [ 516.285369] af9013: I2C read failed >> reg:d2e6 Aug 15 13:54:29 htpc kernel: [ 547.407504] af9013: I2C read >> failed reg:d330 Aug 15 13:54:44 htpc kernel: [ 561.902710] af9013: I2C >> read failed reg:d2e6 >> >> It looks I2C problem, but I don't know how to debug it deeper. >> >> I don't know if this is important, but I compile the s2-liplianin for >> other devices this way: >> >> apt-get install linux-headers-`uname -r` build-essential >> mkdir /usr/local/src/dvb >> cd /usr/local/src/dvb >> wget http://mercurial.intuxication.org/hg/s2-liplianin/archive/tip.zip >> unzip s2-liplianin-0b7d3cc65161.zip >> cd s2-liplianin-0b7d3cc65161 >> make CONFIG_DVB_FIREDTV:=n >> make install >> >> Can you help with this? This hardware is a very cheap and works well >> for HD channels but, I don't know why sometimes has pixeled images. >> >> Thanks for your help, best regards. > Thanks Jose Alberto, I search on google for pid filters but I don't find any interesting info. How can I limit bandwidth on dvb? Thanks for your help, I have two dual devices waiting for this fix on my HTPC. Best regards. -- Josu Lazkano -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013
I have problems with a dual usb tuner. I limit the bandwith using pid filters and the problem was gone. Jose alberto On Lunes, 15 de Agosto de 2011 15:34:20 Josu Lazkano escribió: > Hello, I have a problem with the KWorld USB Dual DVB-T TV Stick (DVB-T > 399U): > http://www.linuxtv.org/wiki/index.php/KWorld_USB_Dual_DVB-T_TV_Stick_(DVB- > T_399U) > > I am using it on MythTV with Debian Squeeze (2.6.32). It is a dual > device, sometimes the second adapter works great, but sometimes has a > pixeled images. The first adapter always has pixeled images, I don't > know how to describe the pixeled images, so here is a mobile record: > http://dl.dropbox.com/u/1541853/kworld.3gp > > I have this firmware: > http://palosaari.fi/linux/v4l-dvb/firmware/af9015/5.1.0.0/dvb-usb-af9015.fw > > I read on the linuxtv wiki and there are some problems with dual mode, > there is some links for how to patch the similar driver (Afatech/ITE > IT9135), but I am not good enough to understand the code. > > I check the kernel messages: > > Aug 15 13:53:58 htpc kernel: [ 516.285369] af9013: I2C read failed > reg:d2e6 Aug 15 13:54:29 htpc kernel: [ 547.407504] af9013: I2C read > failed reg:d330 Aug 15 13:54:44 htpc kernel: [ 561.902710] af9013: I2C > read failed reg:d2e6 > > It looks I2C problem, but I don't know how to debug it deeper. > > I don't know if this is important, but I compile the s2-liplianin for > other devices this way: > > apt-get install linux-headers-`uname -r` build-essential > mkdir /usr/local/src/dvb > cd /usr/local/src/dvb > wget http://mercurial.intuxication.org/hg/s2-liplianin/archive/tip.zip > unzip s2-liplianin-0b7d3cc65161.zip > cd s2-liplianin-0b7d3cc65161 > make CONFIG_DVB_FIREDTV:=n > make install > > Can you help with this? This hardware is a very cheap and works well > for HD channels but, I don't know why sometimes has pixeled images. > > Thanks for your help, best regards. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Jelle de Jong wrote: > Antti Palosaari wrote: >> Hei Devin and Jelle, >> >> On 07/11/2009 12:12 AM, Antti Palosaari wrote: I'm not the maintainer for this demod, so I'm not the best person to make such a fix. I spent four hours and debugged the issue as a favor to Jelle de Jong since he loaned me some hardware a couple of months ago. I guess I can make the fix, but it's just going to take away from time better spent on things I am more qualified to work on. Devin >>> I will fix that just right now. I think I will change demodulator from >>> "return error invalid value" to "force detect transmission parameters >>> automatically" in case of broken parameters given. >> It is fixed now as I see best way. >> >> For reason or other my MPlayer didn't give garbage and I never seen any >> of those debugs added. I added just similar channels.conf line as Jelle >> but changed freq and PIDs used here. Maybe garbage fields are filled "0" >> which corresponds AUTO. >> Anyhow, here it is. Could you test? >> http://linuxtv.org/hg/~anttip/af9013/ >> >> regards >> Antti > > I tried to test it but it did not work, i tried to get some more > information with printk i am sure but not much luck there. Al test where > done on the test system, you can login and see for yourself. > > Best regards, > > Jelle > > cd > hg clone http://linuxtv.org/hg/~anttip/af9013/ > cd af9013/ > make -j3 > sudo make install > sudo make unload > sudo modprobe dvb_usb_af9015 > mplayer -nolirc -nojoystick -dvbin card=1 -dvbin timeout=10 > dvb://"3FM(Digitenne)" > # did not work > I keep doing test and the debug i got showed it was in auto mode, so i did a tzap -a 0 -c ~/.tzap/channels.conf -r "3FM(Digitenne)" no lock :D that other bug was teasing me again... :D I manually replugged the device and mplayer works perfect. So patch confirmed to build and work. Thank you very much! Best regards, Jelle -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Antti Palosaari wrote: > Hei Devin and Jelle, > > On 07/11/2009 12:12 AM, Antti Palosaari wrote: >>> I'm not the maintainer for this demod, so I'm not the best person to >>> make such a fix. I spent four hours and debugged the issue as a favor >>> to Jelle de Jong since he loaned me some hardware a couple of months >>> ago. I guess I can make the fix, but it's just going to take away >>> from time better spent on things I am more qualified to work on. >>> >>> Devin >> I will fix that just right now. I think I will change demodulator from >> "return error invalid value" to "force detect transmission parameters >> automatically" in case of broken parameters given. > > It is fixed now as I see best way. > > For reason or other my MPlayer didn't give garbage and I never seen any > of those debugs added. I added just similar channels.conf line as Jelle > but changed freq and PIDs used here. Maybe garbage fields are filled "0" > which corresponds AUTO. > Anyhow, here it is. Could you test? > http://linuxtv.org/hg/~anttip/af9013/ > > regards > Antti I tried to test it but it did not work, i tried to get some more information with printk i am sure but not much luck there. Al test where done on the test system, you can login and see for yourself. Best regards, Jelle cd hg clone http://linuxtv.org/hg/~anttip/af9013/ cd af9013/ make -j3 sudo make install sudo make unload sudo modprobe dvb_usb_af9015 mplayer -nolirc -nojoystick -dvbin card=1 -dvbin timeout=10 dvb://"3FM(Digitenne)" # did not work -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Hei Devin and Jelle, On 07/11/2009 12:12 AM, Antti Palosaari wrote: I'm not the maintainer for this demod, so I'm not the best person to make such a fix. I spent four hours and debugged the issue as a favor to Jelle de Jong since he loaned me some hardware a couple of months ago. I guess I can make the fix, but it's just going to take away from time better spent on things I am more qualified to work on. Devin I will fix that just right now. I think I will change demodulator from "return error invalid value" to "force detect transmission parameters automatically" in case of broken parameters given. It is fixed now as I see best way. For reason or other my MPlayer didn't give garbage and I never seen any of those debugs added. I added just similar channels.conf line as Jelle but changed freq and PIDs used here. Maybe garbage fields are filled "0" which corresponds AUTO. Anyhow, here it is. Could you test? http://linuxtv.org/hg/~anttip/af9013/ regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
On 07/10/2009 06:16 PM, Devin Heitmueller wrote: On Fri, Jul 10, 2009 at 8:09 AM, Antti Palosaari wrote: af9013 is correct in my mind. af9013 will return -EINVAL (error invalid value) in case of first garbage value met (maybe better to switch auto mode when garbage value meet and print debug log?). Of course there should be at least debug printing to inform that... but fix you suggest is better for compatibility. You can do that, it is ok for me. From a purist standpoint, I agree that the application at fault, and if it were some no-name application I would just say "fix the broken application". Except it's not a no-name application - it's mplayer. Are you familiar with Postel's Law? No :) http://en.wikipedia.org/wiki/Postel%27s_Law Saying "this demod is not going to work properly with all versions of one of the most popular applications", especially when other demods handle the condition gracefully, is the sort of thing that causes real problems for the Linux community. I'm not the maintainer for this demod, so I'm not the best person to make such a fix. I spent four hours and debugged the issue as a favor to Jelle de Jong since he loaned me some hardware a couple of months ago. I guess I can make the fix, but it's just going to take away from time better spent on things I am more qualified to work on. Devin I will fix that just right now. I think I will change demodulator from "return error invalid value" to "force detect transmission parameters automatically" in case of broken parameters given. thanks, Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
On Fri, Jul 10, 2009 at 11:40 AM, Jelle de Jong wrote: > Antti if you can fix this issue and help in the future to make some > signal strength API for application, like w_scan, you can keep the > Realtek based dvb-t device I sent to you as a gift, some credits for me > in patches would also be nice since it takes up a lot of time and money > on my side to :D I would *really* like to get the strength/SNR situation straightened out, since it effects all applications, including just the end user's ability to get some idea of the strength in Kaffeine (something that should be relatively simple). I am continuing to brainstorm ideas some for of solution that won't be considered ridiculous to some percentage of the demod maintainers. I did make an effort to credit you for the patches based on your hardware so far: http://www.kernellabs.com/hg/~dheitmueller/em28xx-terratec-zl10353/rev/274eda5953b4 > I tolled the mplayer people maybe 5 month's ago about this issue. They > were quite simple I had 4 devices that worked with mplayer one did not > the problem was with the device, they did not want to listen to the idea > something was wrong with there mplayer. If somebody want to convince > them with this new prove/research please do so, I let it rest. In fairness, I can appreciate why the mplayer developers' initial impression would be that this is a device-level problem since the software works with many other devices. I did definitely confirm it to be a bug though, and now that we know *exactly* what is wrong, getting a fix upstream into mplayer shouldn't be very hard (it should be a ten line patch). I cannot possibly see them suggesting that sending garbage values from the stack in an ioctl() call is appropriate behavior. :-) If you want, do a cvs checkout of the latest mplayer source, get it to successfully compile and work in your environment, and I will see about logging in next week to cook up a patch we can submit upstream. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
On Fri, Jul 10, 2009 at 11:40 AM, Jelle de Jong wrote: > Antti if you can fix this issue and help in the future to make some > signal strength API for application, like w_scan, you can keep the > Realtek based dvb-t device I sent to you as a gift, some credits for me > in patches would also be nice since it takes up a lot of time and money > on my side to :D I would *really* like to get the strength/SNR situation straightened out, since it effects all applications, including just the end user's ability to get some idea of the strength in Kaffeine (something that should be relatively simple). I am continuing to brainstorm ideas some for of solution that won't be considered ridiculous to some percentage of the demod maintainers. I did make an effort to credit you for the patches based on your hardware so far: http://www.kernellabs.com/hg/~dheitmueller/em28xx-terratec-zl10353/rev/274eda5953b4 > I tolled the mplayer people maybe 5 month's ago about this issue. They > were quite simple I had 4 devices that worked with mplayer one did not > the problem was with the device, they did not want to listen to the idea > something was wrong with there mplayer. If somebody want to convince > them with this new prove/research please do so, I let it rest. In fairness, I can appreciate why the mplayer developers' initial impression would be that this is a device-level problem since the software works with many other devices. I did definitely confirm it to be a bug though, and now that we know *exactly* what is wrong, getting a fix upstream into mplayer shouldn't be very hard (it should be a ten line patch). I cannot possibly see them suggesting that sending garbage values from the stack in an ioctl() call is appropriate behavior. :-) If you want, do a cvs checkout of the latest mplayer source, get it to successfully compile and work in your environment, and I will see about logging in next week to cook up a patch we can submit upstream. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Devin Heitmueller wrote: > On Fri, Jul 10, 2009 at 8:09 AM, Antti Palosaari wrote: >> af9013 is correct in my mind. af9013 will return -EINVAL (error invalid >> value) in case of first garbage value met (maybe better to switch auto mode >> when garbage value meet and print debug log?). >> >> Of course there should be at least debug printing to inform that... but fix >> you suggest is better for compatibility. You can do that, it is ok for me. > > From a purist standpoint, I agree that the application at fault, and > if it were some no-name application I would just say "fix the broken > application". Except it's not a no-name application - it's mplayer. > > Are you familiar with Postel's Law? > > http://en.wikipedia.org/wiki/Postel%27s_Law > > Saying "this demod is not going to work properly with all versions of > one of the most popular applications", especially when other demods > handle the condition gracefully, is the sort of thing that causes real > problems for the Linux community. > > I'm not the maintainer for this demod, so I'm not the best person to > make such a fix. I spent four hours and debugged the issue as a favor > to Jelle de Jong since he loaned me some hardware a couple of months > ago. I guess I can make the fix, but it's just going to take away > from time better spent on things I am more qualified to work on. > > Devin > I agree with the arguments, I believe Antti did also and said to me he will try to work something out next week. Antti if you can fix this issue and help in the future to make some signal strength API for application, like w_scan, you can keep the Realtek based dvb-t device I sent to you as a gift, some credits for me in patches would also be nice since it takes up a lot of time and money on my side to :D I tolled the mplayer people maybe 5 month's ago about this issue. They were quite simple I had 4 devices that worked with mplayer one did not the problem was with the device, they did not want to listen to the idea something was wrong with there mplayer. If somebody want to convince them with this new prove/research please do so, I let it rest. Many thanks to Devin and Antti, Best regards, Jelle -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
On Fri, Jul 10, 2009 at 8:09 AM, Antti Palosaari wrote: > af9013 is correct in my mind. af9013 will return -EINVAL (error invalid > value) in case of first garbage value met (maybe better to switch auto mode > when garbage value meet and print debug log?). > > Of course there should be at least debug printing to inform that... but fix > you suggest is better for compatibility. You can do that, it is ok for me. >From a purist standpoint, I agree that the application at fault, and if it were some no-name application I would just say "fix the broken application". Except it's not a no-name application - it's mplayer. Are you familiar with Postel's Law? http://en.wikipedia.org/wiki/Postel%27s_Law Saying "this demod is not going to work properly with all versions of one of the most popular applications", especially when other demods handle the condition gracefully, is the sort of thing that causes real problems for the Linux community. I'm not the maintainer for this demod, so I'm not the best person to make such a fix. I spent four hours and debugged the issue as a favor to Jelle de Jong since he loaned me some hardware a couple of months ago. I guess I can make the fix, but it's just going to take away from time better spent on things I am more qualified to work on. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
hei Devin, Thank you for debugging this issue. Devin Heitmueller wrote: Thanks to Jelle providing an environment to debug the issue in, I isolated the problem. This is actually a combination of bugs in mplayer and the af9013 driver not handling the condition as gracefully as some other demods. First the bugs in mplayer: The following is the line from the channels.conf where tuning failed: Frequency in question: 3FM(Digitenne):72200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:0:7142:1114 Mplayer does not support "TRANSMISSION_MODE_AUTO", "GUARD_INTERVAL_AUTO" and "QAM_AUTO" (for the constellation). In the case of the transmission mode and constellation, mplayer does not populate the field at all in the struct sent to the ioctl(), so you get whatever garbage is on the stack. For the guard interval field, it defaults to GUARD_INTERVAL_1_4 if it is an unrecognized value. I confirmed the mplayer behavior with the version Jelle has, as well as checking the source code in the svn trunk for the latest mplayer. So, why does it work with some tuners but not the af9013? Well, some demodulators check to see if *any* of the fields are "_AUTO" and if any of them are, then it puts the demod into auto mode and disregards whatever is in the other fields. However, the af9013 looks at each field, and if any of them are an unrecognized value, the code bails out in af9013_set_ofdm_params(). As a result, the tuning never actually happens. The behavior should be readily apparent if you were to put the above line into your channels.conf and try to tune (note I had to add printk() lines to af9013_set_ofdm_params() to see it bail out in the first switch statement. Anitti, do you want to take it from here, or would you prefer I rework the routine to put the device into auto mode if any of the fields are auto? af9013 is correct in my mind. af9013 will return -EINVAL (error invalid value) in case of first garbage value met (maybe better to switch auto mode when garbage value meet and print debug log?). Of course there should be at least debug printing to inform that... but fix you suggest is better for compatibility. You can do that, it is ok for me. Devin Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Devin Heitmueller wrote: > On Fri, Jul 3, 2009 at 12:01 PM, Jelle de Jong > wrote: >> Antti Palosaari wrote: >>> On 06/26/2009 11:07 AM, Jelle de Jong wrote: Hi all, Because i now use a new kernel and new mplayer versions I did some testing again on one of my long standing issues. My Afatech AF9015 DVB-T USB2.0 stick does not work with mplayer, other em28xx devices do work with mplayer. Would somebody be willing to do some tests and see if mplayers works on your devices? Debian 2.6.30-1 /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"3FM(Digitenne)" See the attachments for full details. >>> For me, this works. I tested this with MT2060 tuner device, as you have >>> also. If I remember correctly it worked for you also when channel is >>> selected by using tzap. I don't know what mplayer does differently. >>> >>> Do the television channels in that same multiplex work with mplayer? >>> /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"TELEVISION CHANNEL" >>> >>> I added some delay for demod to wait lock. Could you try if this helps? >>> http://linuxtv.org/hg/~anttip/af9015_delay/ >>> >>> regards >>> Antti >> Hi Antti, >> >> I will get back to this next week, its a lot of work for me to compile >> the drivers but I will see if i can get it running. (a pre-compiled >> driver and some insmod for the 686 2.9.30 kernel would be an fast track >> option if you want to test it a.s.a.p.) >> >> Thanks in advance, >> >> Jelle de Jong >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-media" in >> the body of a message to majord...@vger.kernel.org >> More majordomo info at �http://vger.kernel.org/majordomo-info.html >> > > Antti, > > Thanks to Jelle providing an environment to debug the issue in, I > isolated the problem. This is actually a combination of bugs in > mplayer and the af9013 driver not handling the condition as gracefully > as some other demods. > > First the bugs in mplayer: > > The following is the line from the channels.conf where tuning failed: > > Frequency in question: > 3FM(Digitenne):72200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:0:7142:1114 > > Mplayer does not support "TRANSMISSION_MODE_AUTO", > "GUARD_INTERVAL_AUTO" and "QAM_AUTO" (for the constellation). In the > case of the transmission mode and constellation, mplayer does not > populate the field at all in the struct sent to the ioctl(), so you > get whatever garbage is on the stack. For the guard interval field, > it defaults to GUARD_INTERVAL_1_4 if it is an unrecognized value. > > I confirmed the mplayer behavior with the version Jelle has, as well > as checking the source code in the svn trunk for the latest mplayer. > > So, why does it work with some tuners but not the af9013? Well, some > demodulators check to see if *any* of the fields are "_AUTO" and if > any of them are, then it puts the demod into auto mode and disregards > whatever is in the other fields. However, the af9013 looks at each > field, and if any of them are an unrecognized value, the code bails > out in af9013_set_ofdm_params(). As a result, the tuning never > actually happens. > > The behavior should be readily apparent if you were to put the above > line into your channels.conf and try to tune (note I had to add > printk() lines to af9013_set_ofdm_params() to see it bail out in the > first switch statement. > > Anitti, do you want to take it from here, or would you prefer I rework > the routine to put the device into auto mode if any of the fields are > auto? > > Devin > Hi Antti, if you want access to the test environment just give me an email, it is interesting because currently the Afatech AF9013 DVB-T is in that weird lock down mode I talked you about! It would be very nice if you can detect if it is a software or hardware issue, because the devices doesn't tune anymore but seems to respond to other stuff. Best regards, Jelle de Jong -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
On Fri, Jul 3, 2009 at 12:01 PM, Jelle de Jong wrote: > Antti Palosaari wrote: >> On 06/26/2009 11:07 AM, Jelle de Jong wrote: >>> Hi all, >>> >>> Because i now use a new kernel and new mplayer versions I did some >>> testing again on one of my long standing issues. >>> >>> My Afatech AF9015 DVB-T USB2.0 stick does not work with mplayer, other >>> em28xx devices do work with mplayer. >>> >>> Would somebody be willing to do some tests and see if mplayers works on >>> your devices? >>> >>> Debian 2.6.30-1 >>> >>> /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"3FM(Digitenne)" >>> >>> See the attachments for full details. >> >> For me, this works. I tested this with MT2060 tuner device, as you have >> also. If I remember correctly it worked for you also when channel is >> selected by using tzap. I don't know what mplayer does differently. >> >> Do the television channels in that same multiplex work with mplayer? >> /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"TELEVISION CHANNEL" >> >> I added some delay for demod to wait lock. Could you try if this helps? >> http://linuxtv.org/hg/~anttip/af9015_delay/ >> >> regards >> Antti > > Hi Antti, > > I will get back to this next week, its a lot of work for me to compile > the drivers but I will see if i can get it running. (a pre-compiled > driver and some insmod for the 686 2.9.30 kernel would be an fast track > option if you want to test it a.s.a.p.) > > Thanks in advance, > > Jelle de Jong > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Antti, Thanks to Jelle providing an environment to debug the issue in, I isolated the problem. This is actually a combination of bugs in mplayer and the af9013 driver not handling the condition as gracefully as some other demods. First the bugs in mplayer: The following is the line from the channels.conf where tuning failed: Frequency in question: 3FM(Digitenne):72200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:0:7142:1114 Mplayer does not support "TRANSMISSION_MODE_AUTO", "GUARD_INTERVAL_AUTO" and "QAM_AUTO" (for the constellation). In the case of the transmission mode and constellation, mplayer does not populate the field at all in the struct sent to the ioctl(), so you get whatever garbage is on the stack. For the guard interval field, it defaults to GUARD_INTERVAL_1_4 if it is an unrecognized value. I confirmed the mplayer behavior with the version Jelle has, as well as checking the source code in the svn trunk for the latest mplayer. So, why does it work with some tuners but not the af9013? Well, some demodulators check to see if *any* of the fields are "_AUTO" and if any of them are, then it puts the demod into auto mode and disregards whatever is in the other fields. However, the af9013 looks at each field, and if any of them are an unrecognized value, the code bails out in af9013_set_ofdm_params(). As a result, the tuning never actually happens. The behavior should be readily apparent if you were to put the above line into your channels.conf and try to tune (note I had to add printk() lines to af9013_set_ofdm_params() to see it bail out in the first switch statement. Anitti, do you want to take it from here, or would you prefer I rework the routine to put the device into auto mode if any of the fields are auto? Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Antti Palosaari wrote: > On 06/26/2009 11:07 AM, Jelle de Jong wrote: >> Hi all, >> >> Because i now use a new kernel and new mplayer versions I did some >> testing again on one of my long standing issues. >> >> My Afatech AF9015 DVB-T USB2.0 stick does not work with mplayer, other >> em28xx devices do work with mplayer. >> >> Would somebody be willing to do some tests and see if mplayers works on >> your devices? >> >> Debian 2.6.30-1 >> >> /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"3FM(Digitenne)" >> >> See the attachments for full details. > > For me, this works. I tested this with MT2060 tuner device, as you have > also. If I remember correctly it worked for you also when channel is > selected by using tzap. I don't know what mplayer does differently. > > Do the television channels in that same multiplex work with mplayer? > /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"TELEVISION CHANNEL" > > I added some delay for demod to wait lock. Could you try if this helps? > http://linuxtv.org/hg/~anttip/af9015_delay/ > > regards > Antti Hi Antti, I will get back to this next week, its a lot of work for me to compile the drivers but I will see if i can get it running. (a pre-compiled driver and some insmod for the 686 2.9.30 kernel would be an fast track option if you want to test it a.s.a.p.) Thanks in advance, Jelle de Jong -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
On 07/02/2009 11:43 AM, Jelle de Jong wrote: Some extra information about the lockups of my AF9015, this is a serious blocker issue for me. It happens when I watch a channel with totem-xine and switch to an other channel, the device is then unable to lock to the new channel, and totem-xine hangs. There are no messages in dmesg. Rebooting the system does not help getting the device working again, the only way i found is to replug the usb device and this is not an option for my systems because the usb devices are hidden. I have seen that also with Totem-xine few times. Totem-xine hags totally and it must be killed. But after that my device starts working without replug (if I remember correctly). One thing could be power issue. If you have possibility to test with powered USB -hub please do. Is there an other USB DVB-T device that works out of the box with the 2.9.30 kernel? Could somebody show me a link or name of this device so I can buy and test it? DibCOM based sticks are usually good choice. There is many models from many vendors, TerraTec, Artec (Artec T14BR is sold here in Finland 20-30e). DibCOM also uses big USB block size which seems to reduce system load. Look examples from here: http://www.linuxtv.org/wiki/index.php/User:Hlangos Could someone explain why USB block size have so big effect to load? regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
On 06/26/2009 11:07 AM, Jelle de Jong wrote: Hi all, Because i now use a new kernel and new mplayer versions I did some testing again on one of my long standing issues. My Afatech AF9015 DVB-T USB2.0 stick does not work with mplayer, other em28xx devices do work with mplayer. Would somebody be willing to do some tests and see if mplayers works on your devices? Debian 2.6.30-1 /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"3FM(Digitenne)" See the attachments for full details. For me, this works. I tested this with MT2060 tuner device, as you have also. If I remember correctly it worked for you also when channel is selected by using tzap. I don't know what mplayer does differently. Do the television channels in that same multiplex work with mplayer? /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"TELEVISION CHANNEL" I added some delay for demod to wait lock. Could you try if this helps? http://linuxtv.org/hg/~anttip/af9015_delay/ regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
On Thu, Jul 2, 2009 at 4:51 PM, Jelle de Jong wrote: > Devin Heitmueller wrote: >> On Thu, Jul 2, 2009 at 4:43 AM, Jelle de Jong >> wrote: >>> Is there an other USB DVB-T device that works out of the box with the >>> 2.9.30 kernel? Could somebody show me a link or name of this device so I >>> can buy and test it? >> >> You might want to check out the WinTV-Ministick, which is both >> currently available for sale and supported in Linux. >> >> http://www.hauppauge.co.uk/site/products/data_ministickhd.html >> >> Devin >> > > Hi Devin, > > Thanks for your response, I am kind of hitting a deadline next Tuesday. > I must a kind of working dvb-t system here. The af9013 will be a backup > plan. > > So this is my local supplier. Can I ask you to just make a list of > product ids (ArtNr) and I will order them, if they do not work I will > sent them out to developers that volunteer: > > http://www.informatique.nl/cgi-bin/iqshop.cgi?M=ART&G=167 > > I am only interested in USB DVB-T devices. I will try to make the order > tomorrow morning. > > Thanks in advance, > > Cheers, > > Jelle Jelle, Well, before I offer any suggestions, bear in mind that I actually don't use DVB-T and I don't have these products, so I cannot claim that they work from my own experience. Looking at the DVB-T USB entries in list you sent: the ASUS U3000 works according to the Wiki: http://linuxtv.org/wiki/index.php/ASUS_My_Cinema-U3000_Mini >From the Hauppauge list, the any HVR-900 you would buy today would almost certainly be an "HVR-900 R2", which is known to not be supported in the current tree. >From the Pinnacle list, I can tell you that both versions of the 340e are not supported (I am actively developing the xc4000 driver required for them this week). According to the wiki, both the 72e and 73e do work: http://linuxtv.org/wiki/index.php/Pinnacle_PCTV_72e http://linuxtv.org/wiki/index.php/Pinnacle_PCTV_nano_Stick_%2873e%29 I'm not familiar with the products from Plextor and Technisat. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Devin Heitmueller wrote: > On Thu, Jul 2, 2009 at 4:43 AM, Jelle de Jong > wrote: >> Is there an other USB DVB-T device that works out of the box with the >> 2.9.30 kernel? Could somebody show me a link or name of this device so I >> can buy and test it? > > You might want to check out the WinTV-Ministick, which is both > currently available for sale and supported in Linux. > > http://www.hauppauge.co.uk/site/products/data_ministickhd.html > > Devin > Hi Devin, Thanks for your response, I am kind of hitting a deadline next Tuesday. I must a kind of working dvb-t system here. The af9013 will be a backup plan. So this is my local supplier. Can I ask you to just make a list of product ids (ArtNr) and I will order them, if they do not work I will sent them out to developers that volunteer: http://www.informatique.nl/cgi-bin/iqshop.cgi?M=ART&G=167 I am only interested in USB DVB-T devices. I will try to make the order tomorrow morning. Thanks in advance, Cheers, Jelle -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
On Thu, Jul 2, 2009 at 4:43 AM, Jelle de Jong wrote: > Is there an other USB DVB-T device that works out of the box with the > 2.9.30 kernel? Could somebody show me a link or name of this device so I > can buy and test it? You might want to check out the WinTV-Ministick, which is both currently available for sale and supported in Linux. http://www.hauppauge.co.uk/site/products/data_ministickhd.html Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Jelle de Jong wrote: > Jelle de Jong wrote: >> Hi all, >> >> Because i now use a new kernel and new mplayer versions I did some >> testing again on one of my long standing issues. >> >> My Afatech AF9015 DVB-T USB2.0 stick does not work with mplayer, other >> em28xx devices do work with mplayer. >> >> Would somebody be willing to do some tests and see if mplayers works on >> your devices? >> >> Debian 2.6.30-1 >> >> /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"3FM(Digitenne)" >> >> See the attachments for full details. >> >> Best regards, >> >> Jelle de Jong >> > > I am going to give this thread a ping, because I believe this is one of > the few out of the box supported usb dvb-t devices. And I would like to > have at least one device that I can currently buy and that works. So > could somebody with a AF9015 device test if it works with mplayer? > > Also please test the stability. When I use my device with totem it has > issues getting video, I have to replug the device to get it working > again, no dmesg error messages and dvb-t signal is very strong. > > I need to be able to just boot the system start totem or mplayer let it > run stable until the system gets shutdown by the user. (like as a normal > TV or a DVB-T system with Apple OSX stability) Some extra information about the lockups of my AF9015, this is a serious blocker issue for me. It happens when I watch a channel with totem-xine and switch to an other channel, the device is then unable to lock to the new channel, and totem-xine hangs. There are no messages in dmesg. Rebooting the system does not help getting the device working again, the only way i found is to replug the usb device and this is not an option for my systems because the usb devices are hidden. Is there an other USB DVB-T device that works out of the box with the 2.9.30 kernel? Could somebody show me a link or name of this device so I can buy and test it? Thanks in advance, Jelle -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Jelle de Jong wrote: > Hi all, > > Because i now use a new kernel and new mplayer versions I did some > testing again on one of my long standing issues. > > My Afatech AF9015 DVB-T USB2.0 stick does not work with mplayer, other > em28xx devices do work with mplayer. > > Would somebody be willing to do some tests and see if mplayers works on > your devices? > > Debian 2.6.30-1 > > /usr/bin/mplayer -identify -v -dvbin timeout=10 dvb://"3FM(Digitenne)" > > See the attachments for full details. > > Best regards, > > Jelle de Jong > I am going to give this thread a ping, because I believe this is one of the few out of the box supported usb dvb-t devices. And I would like to have at least one device that I can currently buy and that works. So could somebody with a AF9015 device test if it works with mplayer? Also please test the stability. When I use my device with totem it has issues getting video, I have to replug the device to get it working again, no dmesg error messages and dvb-t signal is very strong. I need to be able to just boot the system start totem or mplayer let it run stable until the system gets shutdown by the user. (like as a normal TV or a DVB-T system with Apple OSX stability) Best regards, Jelle -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
