Skip to contentSkip to conversation

saa7134_empress standard vs input

DISCUSSION Gordon Smith 2 participants 5 messages Sep 3, 2008 – Sep 6, 2008 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

Greetings -

I have a RTD Technologies VFG7350 (saa7134 based, two channel, hardware encoder per channel, no tuner) running current v4l-dvb in 2.6.25-gentoo-r7.

Short form question: Is it necessary to do something to connect an input standard to an MPEG encoder?

I seem to have a disconnect between input signal and the MPEG encoder. In this case, there is a NTSC camera signal on the input. Raw data and input selection are on video0. Raw data can be read from and input selected on video0. MPEG encoder output is on video2. MPEG data can be read from video2, but it looks like PAL aspect with NTSC data (extra lines at bottom of image repeat uppermost lines).

$ v4l2-ctl --get-standard --device /dev/video0
Video Standard = 0x0000b000
        NTSC-M/M-JP/M-KR
$ v4l2-ctl --get-standard --device /dev/video2
Video Standard = 0x000000ff
        PAL-B/B1/G/H/I/D/D1/K

The input standard is automatically selected by the hardware. Is there something that needs to be set to match the standard between input and encoder?

Thanks,
Gordon

--
video4linux-list mailing list
Unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

#1 lore raw
Quoted 25 lines · On Wednesday 03 September 2008 23:48:39 Gordon Smith wrote:

Greetings -

I have a RTD Technologies VFG7350 (saa7134 based, two channel, hardware encoder per channel, no tuner) running current v4l-dvb in 2.6.25-gentoo-r7.

Short form question: Is it necessary to do something to connect an input standard to an MPEG encoder?

I seem to have a disconnect between input signal and the MPEG encoder. In this case, there is a NTSC camera signal on the input. Raw data and input selection are on video0. Raw data can be read from and input selected on video0. MPEG encoder output is on video2. MPEG data can be read from video2, but it looks like PAL aspect with NTSC data (extra lines at bottom of image repeat uppermost lines).

$ v4l2-ctl --get-standard --device /dev/video0
Video Standard = 0x0000b000
        NTSC-M/M-JP/M-KR
$ v4l2-ctl --get-standard --device /dev/video2
Video Standard = 0x000000ff
        PAL-B/B1/G/H/I/D/D1/K
Quoted 3 lines

The input standard is automatically selected by the hardware. Is there something that needs to be set to match the standard between input and encoder?

I suspect I know what is wrong. After loading the driver run 'v4l2-ctl -s ntsc-m' and see if the capture now works. Ignore the standard as reported by video2: it's bogus and is unused.

What I believe is happening is that the saa6752 is never told that the standard is NTSC when it is loaded the first time. But if you set it explicitly afterwards, then it probably works.

Let me know what happens. If it is indeed a bug then I'll fix it.

Regards,

Hans

--
video4linux-list mailing list
Unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

#2 lore raw
Quoted 35 lines · Hans Verkuil
Quoted 25 lines · On Wednesday 03 September 2008 23:48:39 Gordon Smith wrote:

Greetings -

I have a RTD Technologies VFG7350 (saa7134 based, two channel, hardware encoder per channel, no tuner) running current v4l-dvb in 2.6.25-gentoo-r7.

Short form question: Is it necessary to do something to connect an input standard to an MPEG encoder?

I seem to have a disconnect between input signal and the MPEG encoder. In this case, there is a NTSC camera signal on the input. Raw data and input selection are on video0. Raw data can be read from and input selected on video0. MPEG encoder output is on video2. MPEG data can be read from video2, but it looks like PAL aspect with NTSC data (extra lines at bottom of image repeat uppermost lines).

$ v4l2-ctl --get-standard --device /dev/video0
Video Standard = 0x0000b000
        NTSC-M/M-JP/M-KR
$ v4l2-ctl --get-standard --device /dev/video2
Video Standard = 0x000000ff
        PAL-B/B1/G/H/I/D/D1/K
Quoted 3 lines

The input standard is automatically selected by the hardware. Is there something that needs to be set to match the standard between input and encoder?

I suspect I know what is wrong. After loading the driver run 'v4l2-ctl -s ntsc-m' and see if the capture now works. Ignore the standard as reported by video2: it's bogus and is unused.

Quoted 5 lines

What I believe is happening is that the saa6752 is never told that the standard is NTSC when it is loaded the first time. But if you set it explicitly afterwards, then it probably works.

Let me know what happens. If it is indeed a bug then I'll fix it.

I set the standard as above as well as just "ntsc" on another attempt, but the the capture is still PAL size.

{{{

$ v4l2-ctl -s ntsc-m --device /dev/video0
Standard set to 00001000
}}}
Quoted 4 lines

Regards,

Hans

--
video4linux-list mailing list
Unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

#3 lore raw
Quoted 1 line · On Friday 05 September 2008 00:06:00 Gordon Smith wrote:

On Thu, Sep 4, 2008 at 12:22 AM, Hans Verkuil <[email protected]>

Quoted 41 lines · wrote:
Quoted 35 lines · On Wednesday 03 September 2008 23:48:39 Gordon Smith wrote:
Quoted 26 lines

Greetings -

I have a RTD Technologies VFG7350 (saa7134 based, two channel, hardware encoder per channel, no tuner) running current v4l-dvb in 2.6.25-gentoo-r7.

Short form question: Is it necessary to do something to connect an input standard to an MPEG encoder?

I seem to have a disconnect between input signal and the MPEG encoder. In this case, there is a NTSC camera signal on the input. Raw data and input selection are on video0. Raw data can be read from and input selected on video0. MPEG encoder output is on video2. MPEG data can be read from video2, but it looks like PAL aspect with NTSC data (extra lines at bottom of image repeat uppermost lines).

$ v4l2-ctl --get-standard --device /dev/video0
Video Standard = 0x0000b000
        NTSC-M/M-JP/M-KR
$ v4l2-ctl --get-standard --device /dev/video2
Video Standard = 0x000000ff
        PAL-B/B1/G/H/I/D/D1/K
Quoted 3 lines

The input standard is automatically selected by the hardware. Is there something that needs to be set to match the standard between input and encoder?

I suspect I know what is wrong. After loading the driver run 'v4l2-ctl -s ntsc-m' and see if the capture now works. Ignore the standard as reported by video2: it's bogus and is unused.

Quoted 5 lines

What I believe is happening is that the saa6752 is never told that the standard is NTSC when it is loaded the first time. But if you set it explicitly afterwards, then it probably works.

Let me know what happens. If it is indeed a bug then I'll fix it.

Quoted 7 lines

I set the standard as above as well as just "ntsc" on another attempt, but the the capture is still PAL size.

{{{

$ v4l2-ctl -s ntsc-m --device /dev/video0
Standard set to 00001000
}}}

Hmm, I'd expected that to work. I'll have to test this myself during the weekend.

Regards,

Hans

--
video4linux-list mailing list
Unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

#4 lore raw
In reply to Gordon Smith
Quoted 1 line · On Friday 05 September 2008 00:06:00 Gordon Smith wrote:

On Thu, Sep 4, 2008 at 12:22 AM, Hans Verkuil <[email protected]>

Quoted 41 lines · wrote:
Quoted 35 lines · On Wednesday 03 September 2008 23:48:39 Gordon Smith wrote:
Quoted 26 lines

Greetings -

I have a RTD Technologies VFG7350 (saa7134 based, two channel, hardware encoder per channel, no tuner) running current v4l-dvb in 2.6.25-gentoo-r7.

Short form question: Is it necessary to do something to connect an input standard to an MPEG encoder?

I seem to have a disconnect between input signal and the MPEG encoder. In this case, there is a NTSC camera signal on the input. Raw data and input selection are on video0. Raw data can be read from and input selected on video0. MPEG encoder output is on video2. MPEG data can be read from video2, but it looks like PAL aspect with NTSC data (extra lines at bottom of image repeat uppermost lines).

$ v4l2-ctl --get-standard --device /dev/video0
Video Standard = 0x0000b000
        NTSC-M/M-JP/M-KR
$ v4l2-ctl --get-standard --device /dev/video2
Video Standard = 0x000000ff
        PAL-B/B1/G/H/I/D/D1/K
Quoted 3 lines

The input standard is automatically selected by the hardware. Is there something that needs to be set to match the standard between input and encoder?

I suspect I know what is wrong. After loading the driver run 'v4l2-ctl -s ntsc-m' and see if the capture now works. Ignore the standard as reported by video2: it's bogus and is unused.

Quoted 5 lines

What I believe is happening is that the saa6752 is never told that the standard is NTSC when it is loaded the first time. But if you set it explicitly afterwards, then it probably works.

Let me know what happens. If it is indeed a bug then I'll fix it.

Quoted 7 lines

I set the standard as above as well as just "ntsc" on another attempt, but the the capture is still PAL size.

{{{

$ v4l2-ctl -s ntsc-m --device /dev/video0
Standard set to 00001000
}}}

Hi Gordon,

I've just tested it and I found out that setting the standard works fine as long as the tuner is selected as input. If composite or S-Video is selected as input then the mpeg encoder was never updated. Since you have no tuner input that makes it a bit hard on you :-)

I've fixed that in the code so you can use my tree for now:

http://www.linuxtv.org/hg/~hverkuil/v4l-dvb

I've also fixed that you can set/get the standard from the video1 device as well.

Note that once this fix is in the master v4l-dvb repository I recommend that you switch to that one.

Regards,

Hans

--
video4linux-list mailing list
Unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list