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
Afatech AF9013 DVB-T not working with mplayer radio streams
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 $ dmesg [ 1179.756075] usb 1-2: new high speed USB device using ehci_hcd and address 7 [ 1179.892943] usb 1-2: New USB device found, idVendor=15a4, idProduct=9016 [ 1179.892958] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1179.892969] usb 1-2: Product: DVB-T [ 1179.892978] usb 1-2: Manufacturer: Afatech [ 1179.893314] usb 1-2: configuration #1 chosen from 1 choice [ 1179.917431] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware [ 1179.917458] usb 1-2: firmware: requesting dvb-usb-af9015.fw [ 1179.955337] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' [ 1180.029702] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. [ 1180.029843] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 1180.030323] DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) [ 1180.445189] af9013: firmware version:4.95.0 [ 1180.450068] DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)... [ 1180.453854] MT2060: successfully identified (IF1 = 1220) [ 1180.923942] dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. [ 1180.942283] Afatech DVB-T: Fixing fullspeed to highspeed interval: 16 -> 8 [ 1180.943283] input: Afatech DVB-T as /devices/pci:00/:00:1d.7/usb1/1-2/1-2:1.1/input/input11 [ 1180.943730] generic-usb 0003:15A4:9016.0004: input,hidraw0: USB HID v1.01 Keyboard [Afatech DVB-T] on usb-:00:1d.7-2/input1 $ sudo lsusb -v -d 15a4:9016 Bus 001 Device 007: ID 15a4:9016 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x15a4 idProduct 0x9016 bcdDevice2.00 iManufacturer 1 Afatech iProduct2 DVB-T iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 71 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 1 Keyboard iInterface 0 ** UNRECOGNIZED: 09 2
