hermann pitton | 1 Aug 01:44 2006
Picon

Re: fmtools and auto-mute on application exit (with kernel 2.6.16)

Am Montag, den 31.07.2006, 10:44 +0200 schrieb Matthias Ringwald: 
> Hi Hermann, Ben and others?
> 
> let me try to recap what we've learned so far.
> 
> * the current v4l(one) drivers try to mute/standby the radio
> when there is no running application.
> there is currently no API / IOCTL call which would change this.
> * For my single tv/radio card I can disable this behavior, but that's
> not very practical for a broad audience
> * the v4l(one) interface is deprecated and will disappear soon
> * radio support in v4l(two) has just been finished and could be used,
> if one waits for some months (aka next ubuntu version etc) or install 
> the Mercurial version
> 
> so, how is / will be the situation in v42(two)?
> Is it possible to keep the radio running when _no_ application
> with an open /dev/radio or /dev/video device is running?
> 
> where's a good place to collect the details ( I guess v4l2.h wouldn't be 
> the worst place to start)
> 
> So, assuming there's a way to do it properly in v4l(two), then moving
> /adding v4l(two) support looks promising. :)
> 
> Cheers
>   Matthias
> 
> p.s. personally I'm disatisfied with the radio quality of the
> terractec cinergy 600 as the noise level is quite high and will
(Continue reading)

bino_oetomo | 1 Aug 04:17 2006

migrate from BroadLogic PCI to TwinHan with V4L

Dear All.

Currently I use Broadlogic PCI card for our DVB-IP service.
I need to find alternative to this card, since :
- Hard to find
- Binary only driver specific to some linux distro, while I want to have a
small (LEAF-based) DVB-IP router.

Years ago I realize that there is new card from Twinhan, but at that day
this card is not yet supported by V4L community for IP traffic reception.

I just realize that currently this card is supported by the community for IP
traffic usage.

When I use broadlogic, I need to set some variable :
- Satellite Freq
- LNB Lo Freq
- FEC (1/2 , 3/4 , or 7/8)
- Symrate
- PID (dec or Hex)
- Polarization

I serach the web, and find the "PlanetSky" web site have a good stright
explanation on how to set twhinhan card for this.
They also give a channels.conf example for connecting to their service.
the contents looks like :

PlanetSky:11170:h:0:27692:512:512:512

I know that :
(Continue reading)

Nickolay V. Shmyrev | 1 Aug 06:57 2006
Picon

Re: [patch] add std fixups for saa7134-sound

В Пнд, 31/07/2006 в 23:58 +0200, Hartmut Hackmann пишет:
> Hi, Nickolay
> 
> Nickolay V. Shmyrev wrote:
> <snip>
> > 
> > Hello Hartmut and Stas and all.
> > 
> > It's rather interesting discussion, but let me interrupt you a bit, for
> > now I don't see the reason of the problem except quite hackish patch.
> > Secam-d is used to work some time ago, it was broken for a little period
> > of time but now it should work as well.
> > 
> > Why the patch is needed? Stas, can you describe the problem more
> > precisely and paste here the log of tunning on some channel with
> > audio_debug=9?
> > 
> There basically are 2 issues
> - The current SAA7134 code does not detect the primary sound standard
>    well. So the situation can occur that the chip does not detect a
>    system D sound carrier (6.5 MHz FM) and falls back to the default -
>    not absolutely sure but should be system B/G (5.5 MHz FM). The result
>    is no sound.

We know that's purely tuner problem, during autodetection process we
should try to setup standard on a multi-standard tuner as well on
saa7134. I wonder if someone should try it and how much this will slow
up detection process. We should just add a client call into
tvaudio_checkcarrier or in tvaudio_thread. This won't work for saa7135
at all and I it would be very interesting to know, how saa7135 should
(Continue reading)

Nickolay V. Shmyrev | 1 Aug 07:20 2006
Picon

Bug tracking system for v4l-dvb

Hello all

Yes, it's all about the same, v4l-dvb project needs issue tracking
system. Just like to help Hermann and others with their wonderful
support we need to setup and __use__ one. Mailing list is certainly not
so appropriate to handle 1000 requests per month.

For me it's seems rather natural to track bugs in kernel bugzilla
(http://bugzilla.kernel.org) partially because newbies sometimes fill
bugs there already, partially because that will free us from support
tasks. 

We could ask for "V4L-DVB Drivers" category with the following list of
components: general, api, saa71xx, cx88, bttv, em28xx and so on. I am
adding CC of bugzilla admin as well and like to hear your opinions.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Fabian Sturm | 1 Aug 07:57 2006

Status of the hvr1300 driver

        Hi there!

        I would like to query for the status of the hvr1300 driver.
        Steve is working on it and he asked some time ago about testers
        for the alpha driver.

        http://marc.theaimsgroup.com/?l=linux-video&m=114183371013406&w=2

        So I wonder if he still needs some, or if there is anything else
        I 
        could help with to get this driver running?

        Thanks a lot, Fabian

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Michel Bardiaux | 1 Aug 10:27 2006
Picon

Re: Horizontal white stripes in picture when using multiple BT878 Boards

Peter Missel wrote:
> On Monday 31 July 2006 18:54, Daniel Glöckner wrote:
>> There is a PCI Express version of that card.
> 
> ... which will have the exact same problem, given that the described bus 
> contention problem very possibly occurs on the card's local parallel PCI bus.
> 
> The BT8xx chips cannot do 66 MHz PCI, hence, no improvement will be achieved 
> by the switch to PCIE for the external bus.

Thanks for the tip, which is absolutely not obvious when you read card 
specs (I mean the ! <at> #$-poor descriptions you find on vendor sites).

> 
> You'll get better results with native PCIE cards, 

Such as? Does the cx88 support 66MHz?

> or with cards that bring 
> compression hardware.
> 
> regards,
> Peter
> 
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list

--

-- 
(Continue reading)

Daniel Glöckner | 1 Aug 12:45 2006
Picon
Picon

Re: Horizontal white stripes in picture when using multiple BT878 Boards

On Tue, Aug 01, 2006 at 10:27:59AM +0200, Michel Bardiaux wrote:
> >You'll get better results with native PCIE cards, 
> 
> Such as? Does the cx88 support 66MHz?

The CX23880/1/2/3 are 33MHz PCI chips.
The CX23885/6/7/8 are PCIe chips (this is not 66MHz PCI).
The PCI-SIG lists SAA7162 (dual A/V decoder)
and SAA7160/SAA7161 (multimedia A/V bridge) as PCIe devices.

I don't know if any of those PCIe devices is supported by V4L.

  Daniel

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

linuxteam | 1 Aug 12:57 2006
Picon

Re: Horizontal white stripes in picture when using multiple BT878 Boards

There is a proprietary Windows driver made by Matrix-Vision for the SIGMA-SQ
Card. Using this driver in a Windows environment, you can display and record
the 4 channels simultaneously at 720x576 / 25fps and select the chroma format.
With YUV422 the picture quality is really excellent. There is no other 
hardware
on the card than the 4 BT-Chips, a video crossbar, the local PCI-Bus and a
PCI-to-PCI Bridge.

So why does it run on Windows perfectly, while the Linux results are so poor
with multiple BT878?

Matrix-Vision also cooks with water, so there must be some tuning parameters,
that are not optimal hit by bttv. The problems occur when you use 4 singular
grabber boards, too. This problem is not card specific but seems to persist
always when using multiple BT878 chips. Obviously there is a general
optimization lack in the bttv driver. Maybe changing the DMA Trigger Point
helps. We will do some tests and in circuit analysis next week.

Best regards

Sascha S. Haenel

Quoting Peter Missel <peter.missel <at> onlinehome.de>:

> On Monday 31 July 2006 18:54, Daniel Glöckner wrote:
>> There is a PCI Express version of that card.
>
> ... which will have the exact same problem, given that the described bus
> contention problem very possibly occurs on the card's local parallel PCI bus.
>
(Continue reading)

Stas Sergeev | 1 Aug 13:14 2006
Picon

Re: [patch] add std fixups for saa7134-sound

Hello.

Nickolay V. Shmyrev wrote:
> Why the patch is needed?
Wasn't it you who told me a year ago that the problem
is known? :)

> Secam-d is used to work some time ago, it was broken for a little period
> of time but now it should work as well.
What is now? I am testing on 2.6.18-rc2-mm1.
As for used to work before - well, this is very
questionable. Yes, it used to work sometimes, i.e.
I could get sound by switching to the same channel
for 3-10 times, and now it doesn't work completely.
But reverting to the old state won't help. Switching
the channels over and over until you suddenly get sound,
was very annoying. For that I'd say, it never worked before.

> Stas, can you describe the problem more
> precisely and paste here the log of tunning on some channel with
> audio_debug=9?
OK, problem: sound works on the ORT channel, which
uses nicam. Others do not work.
Log is attached. As you can see, first it takes
SECAM-L NICAM, as it was ORT. Then I switch to other
channels, and it takes SECAM-L MONO, which doesn't work.

Aug  1 15:01:27 lin2 kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
(Continue reading)

Stas Sergeev | 1 Aug 13:24 2006
Picon

Re: [patch] add std fixups for saa7134-sound

Hello.

Hartmut Hackmann wrote:
>> OK, I'm looking forward for that. :) Next challenge for me would be
>> to find out how to get the sound also from the radio part of the board...
> Whats your exact board type? which tuner is on your board?
I posted the log in the nearby message - that info
should be there. But I wouldn't mix also the radio
issues in that thread. When the video problems are
resolved, I'll post back with that too.
A quick description however:
- Radio used to work a year ago.
- Then the channel detection was broken, so the manual
searching became a due.
- Then and till now - no sound at all.
So it erroded slowly and spectacularly.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list


Gmane