Does anyone have an idea getting the sound of pinnacle usb2 working? Input:PAL I tryed all the things:. I couldn't update dvb-kernel from cvs - is this perhaps causing problem? The problem I had was with mplayer and mencoder not being able to get the audio stream even with the sox command running. As it turns out, as mentioned above the audio channel was muted, and mplayer doesn't turn the mute off.
The following commands worked for me in getting audio through mplayer, and recording audio using mencoder:. Notes: The important thing here is that the tv options match what you use for mplayer. Then you should be able to record with audio. Now I can try and get freevo working with mplayer since I couldn't get tvtime to work , and recording should hopefully work too. If you want the mplayer command all in one line, then try:.
After download the package, do I need just to compile it or it is a patch to be applied on my kernel source or v4l source? I have a msi vox usb 2. When i modprobe em28xx my usb tv card its recognized and seted up.
But when i run xawtv, aatv, tvtime, or whatever My running kernel is 2. The MSI Vox isn't completly supported at the moment, I'll try to fix it during the next few days only problem is I don't have that device and because of that I have to wait for others to test it. I got only static from the three channels above note that if I try the same channels on Windows they tune ok.
Looking at the output from mplayer I see this:. So I figure out that it was because of the frequency. On my Windows app, I have an option to select if the source from tuner is from Cable or Antenna.
To be allowed to tune the channels on Windows I have to select "Antenna". Do you think the problem could be this? I noticed that the only channels I can tune are: 11 12 66 68 69 88 tvtime.
Hey guys, I'm totally new to these Wiki things, and Linux itself. However, there is no audio. I was reading the main page and was confused as to if it works or not. I checked out the usb audio section, and did this bit:. Except, my card had different information, obviously. So I was wondering if there is a way to make the audio work via usb. Tv picture is very fine but no sound. The mixer is correct:. I have the same problem. When I am not running tvtime, it shows only a white screen.
I think Lorenzo found my problem. I've completely forgot that here in Brazil all open-channels are UHF at least in my city so I think that's why I can't tune channels. Thanks a lot and sorry for disturbing you.. I tried all the channels in both direction but none of them worked for me. The v4l kernel has it's own tveeprom module. Markus, I'll double check the process of intalling the driver, but I don't think this is a reason. I did try to restart the computer few times , I did try to not modprobe the tveeprom module first, but I didn't succeed either.
With loading the tveeprom first was a wild card - I thought perhaps it is missing something "Unknown symbol in module, or unknown parameter" from the tveeprom module I think that the problem could be in following lines:.
I met simillar problem before while tryed to install commercial OSS sound driver , they send me another "no regparm" version of their drivers and it did work well partially The em28xx module just glues some other things together which we didn't want to write again. You also need the tveeprom module from the v4l-kernel project. You could get around that by installing a completly custom kernel for sure. I also use tvtime with my Pinnacle pctv usb2 card.
I can see the images, but my sound doesn't work too. Why is my tv-card not listed? Shouldn't the tvcard be the dsp1? I use FC4. In the soundcard-detection, the pinnacle tv card is listed, and when I select test device, then I can hear a test sound.
Does anybode can give me some advice? I tryed now hours to solve the problem. Then I don't receive anymore the message no sound, but I still can't hear the sound.
I receive the message:. With the option -ao sdl I don't receive this message any more but my sound still doesn't work. What else can I try now? I also can't hear anymore the testsound in the soundcard detection of gnome. When my soundcard wasn't in the cards list, I heard this sound. Now I have another question: I use tvtime. I can't tune correctly some channels. With finetune, the best audio quality is at another place than the best video quality, so I can watch these channels, either with a good sound or good images, but both together doesn't work.
Other channels are perfect. In windows all the channels work. I was only able to get sound with xawtv using the sox "redir" above. If there are technical reasons to have two drivers it's Ok, but if the reasons are political Multiple drivers are easily accepted as temporary solution, but then someone must merge support for other hardware - and then we have "reiserfs situation" where developer works for it's own feature and against all others Is it actually a requirement for driver inclusion that future support be lined up?
That seems to be the opposite of the open source process. Rather, a developer puts code into the mainline so that the whole rest of the world can maintain it. In particular, users of the code — people with a material interest in it — maintain it. If the code doesn't get maintained and becomes unusable, we just drop it back out. The article mentions the confusion factor of having two similar drivers.
I can think of another drawback: division of development and test effort. All of these are weak. Mauro doesn't explain his reason for not wanting both. He just says: Both upstream and the 4 duplicated drivers have similar functionality. Also, the upstream driver is actively maintained. So, there's no sense on accepting those duplicated drivers. That's non sequitur to me. The reason for the big patch has always been that the code had to be rebased because the maintainer basically didn't care about anything there.
Ok I acknowledge that is what's wanted and how it should be done. Only then would I be in favor of merging the empia driver. Until now I have seen no attempts to make these changes, alas.
It's all a very sad story, especially compared with the success stories in v4l in the recent years: ivtv, gpsca, uvcvideo just to name a few were all added without any problem and in good harmony.
They fight for at least three years now and they still don't have a useful infrastructure to support DVB-S2 devices. It's all connected, including multiple flamewars. Now one group the v4l group has taken over without taking other dvb people who managed the project before as a small group before It's all about friendship there, A likes B instead of C even if C has better stuff and supporters, so A will wait till B completes his stuff, and C will be pushed away as long as possible without clean reviews or something else, this is just the way how it works out.
Basically there are too many good people involved already. The project is moreover looking for lower skilled people who can be taught what to do do it as A or B says otherwise they'll run against C. It's not a project for innovative people to work on own ideas that for other open operating systems are better in that case. Cliques are a hard problem to beat and generally impossible , we can see so many examples of this screwing projects over.
In this case it's bloody disgusting that code was put on the backburner in favour of waiting for somebody else to complete their alternative solution just because A liked B better than C. Meanwhile, the other developer added the main required feature support for hybrid analog-digital tuners to the Video4Linux code in roughly the same way as they'd proposed earlier, but written from scratch, and this was accepted.
It also eventually lead to some nice code cleanups. Well, Marcus' userspace stuff was rejected, due to a duplicating existing code in a way that'd make life difficult for developers and b the only real "benefit" being the ability to have closed-source blobs in drivers.
Messages to me from Markus threatening to take his code closed-source if he didn't get his way didn't exactly encourage me to support it either. There were code quality issues too, of course, but I'm not sure anyone got as far as looking at those. In the end, some of the developers decided to just improve the version of the driver currently in-kernel rather than continuing to deal with Markus.
Only after this effort was well underway did Markus begin developing yet another in-kernel driver. This one also seemed to fail to meet kernel code quality standards last time I checked, mainly due to incorporating large chunks of third-party code.
This was one possibility yes, but I also pointed out that the already available i2c-dev infrastructure could directly be used with the driver for setting up chips. It can do some setup steps which the API currently cannot handle.
So in order to avoid that someone has to disallow the usbfs and i2c-dev interface. Back then Greg Kroah pointed out that binary drivers could use that interface, it was accepted because he basically didn't clash with another developer.
So binary drivers here or there is basically the same. This was basically my try to make development liberal and not driven by one single person. The userspace drivers used a couple of self written drivers. The drivers which everything was about are still not available in the kernel, it basically was about Micronas chips back then.
The approach aimed to have some compatibility level to the available BSD tuning modules. Building a virtual front between developers who actually supported linux for a long time isn't healthy. But well that way I don't see any chance in officially supporting and telling people to use video on linux unless they want to depend on the video4linux Maintainer. This will be my last comment about everything unless someone starts to think clear about the whole situation.
I never dropped off anyone contributing to that project, rather helped them to get further into it and the code authors as well as the support mailinglist are a proof of that. No possibility they are the same person, is it? Same disagreements, same tone, same part of the kernel..
Can't a higher-up maintainer intervene? User: Password:. The sad story of the em28xx driver. By Jonathan Corbet November 11, Best would be to replace you as a maintainer since you don't have any respect of others work either. In my opinion it's pretty much hopeless trying to convert the current em28xx driver into what you have. The sad story of the em28xx driver Posted Nov 12, UTC Wed by JoeF subscriber, [ Link ] Well, politics and clashes of personalities happen in every organization, even in a loosely organized community like an open source development group.
Obviously, this hasn't worked out very well in this instance. Maybe Jon's article can be the crystallization point for everybody to take a step back and go on a path of compromise instead of confrontation hope springs eternal, I know You can check that the new driver is loaded by looking at dmesg output please post this too.
Mcentral's driver doesn't need the firmware file xcv After this, makepkg can be started. As You can see have been loaded the original drivers. Please note the marked readreg error, always present in my tests. Ciao Pietro, ok it seems that the "code" tag doesn't do what I expected, because it modified the patch I tried copy from the browser and paste to vi, I got a different file. Hope this works. If it doesn't work feel free to email me using the forum. Ciao Giuseppe, Having applied the change suggested, after reboot, video is good and audio works fine.
I think the problem is resolved. Thank you very much for the assistance you have given me. A buon rendere. Ciao Pietro. Atom topic feed. Arch Linux.
0コメント