Re: Structure of DiSEqC Command

2011-08-10 Thread DUBOST Brice
On 08/08/2011 19:06, Nima Mohammadi wrote:
 Hi folks,
 I was reading the source code of various dvb related utilities and I
 was wondering about forming up the message which instructs the DiSEqC
 switch. But I found out that different programs produce the command
 differently.
 The confusing thing is that according to the DiSEqC specification
 documents that I've read, the least significant bit (lsb) must
 indicate the band (low/high), not the polarity (ver/hor), but as you
 see it only applies to some of these programs:
 
 getstrean abd dvbstream:
 int i = 4 * switch_pos + 2 * hiband + (voltage_18 ? 1 : 0);
 
 szap and mplayer:
 (((sat_no * 4)  0x0f) | (hi_lo ? 1 : 0) | (polv ? 0 : 2));
 
 scan:
 4 * switch_pos + 2 * hiband + (voltage_18 ? 1 : 0)
 
 gstdvbsrc:
 (((sat_no * 4)  0x0f) | (tone == SEC_TONE_ON ? 1 : 0) | (voltage ==
 SEC_VOLTAGE_13 ? 0 : 2));
 
 


Hello

I'm the upstream author of MuMuDVB (http://mumudvb.braice.net)

The diseqc related code is here
http://gitweb.braice.net/gitweb?p=mumudvb;a=blob;f=src/tune.c

On the document

http://www.eutelsat.com/satellites/pdf/Diseqc/associated%20docs/applic_info_LNB_switchers.pdf

Page 7 (page 10 of the PDF) the band is the LSB and the table
is organized in increasing binary data

But in
http://www.eutelsat.com/satellites/pdf/Diseqc/associated%20docs/update_recomm_for_implim.pdf

page 33 (35 in the PDF)

The LSB SEEMS to be the polarization, but it's still the band, the table
is just organized in a strange way

If you look deeply into the code of scan
 http://www.linuxtv.org/hg/dvb-apps/file/36a084aace47/util/scan/diseqc.c

You'll see that the table is organized as in the second document and the
code addresses the table for making the message but there is no mistake
in the real data since it's f0,f2,f1 etc ...

So the difference is if the diseqc data is wrote directly (as in
MuMuDVB) or taken from a table organised as in the specification (as in
scan)

Hope it's clear and it helps

Regards

-- 
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
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: [libdvben50221] stack leaks resources on non-MMI session reconnect.

2010-11-02 Thread DUBOST Brice

On 08/08/2010 23:53, DUBOST Brice wrote:

On 15/07/2010 15:20, Stephan Trebels wrote:


The issue was, that LIBDVBEN50221 did not allow a CAM to re-establish
the session holding non-MMI resources if using the lowlevel interface.
The session_number was recorded on open, but not freed on close (which
IMO is an bug in the code, I attach the scaled down hg changeset). With
this change, the SMIT CAM with a showtime card works fine according to
tests so far.

The effect was, that the CAM tried to constantly close and re-open the
session and the LIBDVBEN50221 kept telling it, that the resource is
already allocated to a different session. Additionally this caused the
library to use the _old_ session number in communications with the CAM,
which did not even exist anymore, so caused all writes of CA PMTs to
fail with EINTR.

Stephan



Hello

Just to inform that this patch solves problems with CAM PowerCAM v4.3,
so I think it can interest more people.

Before gnutv -cammenu (and other applications using libdvben50221) was
returning ti;eout (-3) errors constantly after the display of the system
IDs.

Now, the menu is working flawlessly

I cannot test the descrambling for the moment but it improved quite a
lot the situation (communication with th CAM is now possible).

One note concerning the patch itself, the last else if (resource_id ==
EN50221_APP_MMI_RESOURCEID) is useless.

Best regards





Hello


After more testing this Patches allow several CAM models to work and 
don't seem to make any regression.


Is there anything to be improved/tested for having it included upstream ?

Thank you

Regards

--
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
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: [libdvben50221] stack leaks resources on non-MMI session reconnect.

2010-08-08 Thread DUBOST Brice

On 15/07/2010 15:20, Stephan Trebels wrote:


The issue was, that LIBDVBEN50221 did not allow a CAM to re-establish
the session holding non-MMI resources if using the lowlevel interface.
The session_number was recorded on open, but not freed on close (which
IMO is an bug in the code, I attach the scaled down hg changeset). With
this change, the SMIT CAM with a showtime card works fine according to
tests so far.

The effect was, that the CAM tried to constantly close and re-open the
session and the LIBDVBEN50221 kept telling it, that the resource is
already allocated to a different session.  Additionally this caused the
library to use the _old_ session number in communications with the CAM,
which did not even exist anymore, so caused all writes of CA PMTs to
fail with EINTR.

Stephan



Hello

Just to inform that this patch solves problems with CAM PowerCAM v4.3, 
so I think it can interest more people.


Before gnutv -cammenu (and other applications using libdvben50221) was 
returning ti;eout (-3) errors constantly after the display of the system 
IDs.


Now, the menu is working flawlessly

I cannot test the descrambling for the moment but it improved quite a 
lot the situation (communication with th CAM is now possible).


One note concerning the patch itself, the last else if (resource_id == 
EN50221_APP_MMI_RESOURCEID) is useless.


Best regards


--
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
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: Mumudvb Transcoding error

2010-03-07 Thread DUBOST Brice
Aslam Mullapilly a écrit :
 Hi,
 
 I'm trying to run mumudvb with transcoding. Please see my error.
 
 Input #0, mpegts, from 'stream':
   Duration: N/A, start: 28021.001044, bitrate: 15128 kb/s
   Program 2801 Alarabiya
   Program 2802 MBC1
   Program 2803 MBC4
   Program 2804 MBC2
   Program 2805 MBC3
   Program 2806 CITRUSS TV
   Program 2807 HAWAS TV
   Program 2810 AD Emarat
   Program 2811 ZEE AFLAM
   Program 2812 MBC Action
   Program 2813 Al Eqtisadia TV
   Program 2814 MBC MAX
 [Transcode] Couldn't find audio encoder.
 [Transcode] Couldn't find video encoder.
 [Transcode] Failed to initialize transcoding.
 
 
 Hence, I installed libavcodec-dev libavformat-dev libswscale-dev
 
 But still I can't find the stream.
 
 
 Regards,
 


Hello

You must give more information, like the configuration file used, and
the output of

ffmpeg -formats

Regards

-- 
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
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


problem with libdvben50221 and powercam pro V4 [almost solved]

2010-01-24 Thread DUBOST Brice
Hello

Powercam just made a new version of their cam, the version 4

Unfortunately this CAM doesn't work with gnutv and applications based on
libdvben50221

This cam return TIMEOUT errors (en50221_stdcam_llci_poll: Error reported
by stack:-3) after showing the supported ressource id.


I found out that this cam works with the test application of the
libdvben50221

The problem is that this camreturns two times the list of supported ids
(as shown in the log) this behavior make the llci_lookup_callback
(en50221_stdcam_llci.c line 338)  failing to give the good ressource_id
at the second call because there is already a session number (in the
test app the session number is not tested)

I solved the problem commenting out the test for the session number as
showed in the joined patch (against the latest dvb-apps, cloned today)

Since I'm not an expert of the libdvben50221, I'm asking the list if
there is better way to solve this problem and improve my patch so it can
be integrated upstream.

Thank you

-- 
Brice DUBOST

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
diff -r 61b72047a995 lib/libdvben50221/en50221_stdcam_llci.c
--- a/lib/libdvben50221/en50221_stdcam_llci.c	Sun Jan 17 17:03:27 2010 +0100
+++ b/lib/libdvben50221/en50221_stdcam_llci.c	Sun Jan 24 20:56:05 2010 +0100
@@ -334,8 +334,8 @@
 	return -3;
 break;
 			case EN50221_APP_CA_RESOURCEID:
-if (llci-stdcam.ca_session_number != -1)
-	return -3;
+//if (llci-stdcam.ca_session_number != -1)
+//	return -3;
 break;
 			case EN50221_APP_MMI_RESOURCEID:
 if (llci-stdcam.mmi_session_number != -1)
Found a CAM on adapter1... waiting...
en50221_tl_register_slot
slotid: 0
tcid: 1
Press a key to enter menu
00:Host originated transport connection 1 connected
00:Public resource lookup callback 1 1 1
00:CAM connecting to resource 00010041, session_number 1
00:CAM successfully connected to resource 00010041, session_number 1
00:test_rm_reply_callback
00:test_rm_enq_callback
00:Public resource lookup callback 2 1 1
00:CAM connecting to resource 00020041, session_number 2
00:CAM successfully connected to resource 00020041, session_number 2
00:test_ai_callback
  Application type: 01
  Application manufacturer: 02ca
  Manufacturer code: 3000
  Menu string: PCAM V4.1
00:Public resource lookup callback 3 1 1
00:CAM connecting to resource 00030041, session_number 3
00:CAM successfully connected to resource 00030041, session_number 3
00:test_ca_info_callback
  Supported CA ID: 4aa1
  Supported CA ID: 0100
  Supported CA ID: 0500
  Supported CA ID: 0600
  Supported CA ID: 0601
  Supported CA ID: 0602
  Supported CA ID: 0603
  Supported CA ID: 0604
  Supported CA ID: 0606
  Supported CA ID: 0608
  Supported CA ID: 0614
  Supported CA ID: 0620
  Supported CA ID: 0622
  Supported CA ID: 0624
  Supported CA ID: 0626
  Supported CA ID: 0628
  Supported CA ID: 0668
  Supported CA ID: 0619
  Supported CA ID: 1702
  Supported CA ID: 1722
  Supported CA ID: 1762
  Supported CA ID: 0b00
  Supported CA ID: 0b01
  Supported CA ID: 0b02
  Supported CA ID: 0d00
  Supported CA ID: 0d01
  Supported CA ID: 0d02
  Supported CA ID: 0d03
  Supported CA ID: 0d04
  Supported CA ID: 0d05
  Supported CA ID: 0d06
  Supported CA ID: 0d07
  Supported CA ID: 0d08
  Supported CA ID: 0d0c
  Supported CA ID: 0d0f
  Supported CA ID: 0d22
  Supported CA ID: 0d70
  Supported CA ID: 4aa0
00:Connection to resource 00030041, session_number 3 closed
00:Public resource lookup callback 3 1 1
00:CAM connecting to resource 00030041, session_number 3
00:CAM successfully connected to resource 00030041, session_number 3
00:test_ca_info_callback
  Supported CA ID: 4aa1
  Supported CA ID: 0100
  Supported CA ID: 0500
  Supported CA ID: 0600
  Supported CA ID: 0601
  Supported CA ID: 0602
  Supported CA ID: 0603
  Supported CA ID: 0604
  Supported CA ID: 0606
  Supported CA ID: 0608
  Supported CA ID: 0614
  Supported CA ID: 0620
  Supported CA ID: 0622
  Supported CA ID: 0624
  Supported CA ID: 0626
  Supported CA ID: 0628
  Supported CA ID: 0668
  Supported CA ID: 0619
  Supported CA ID: 1702
  Supported CA ID: 1722
  Supported CA ID: 1762
  Supported CA ID: 0b00
  Supported CA ID: 0b01
  Supported CA ID: 0b02
  Supported CA ID: 0d00
  Supported CA ID: 0d01
  Supported CA ID: 0d02
  Supported CA ID: 0d03
  Supported CA ID: 0d04
  Supported CA ID: 0d05
  Supported CA ID: 0d06
  Supported CA ID: 0d07
  Supported CA ID: 0d08
  Supported CA ID: 0d0c
  Supported CA ID: 0d0f
  Supported CA ID: 0d22
  Supported CA ID: 0d70
  Supported CA ID: 4aa0

00:Public resource lookup callback 64 1 1
00:CAM connecting to resource 00400041, session_number 4
00:CAM successfully connected to resource 00400041, session_number 4
00:test_mmi_display_control_callback
  cmd_id: 01
  mode: 01
00:test_mmi_menu_callback
  title: PCAM V4.1
  sub_title: 
  bottom: 
  item 1: English
  item 2: French
  item 3: Spanish
  item 4: German
  item 5: 

Re: problem with libdvben50221 and powercam pro V4 [almost solved]

2010-01-24 Thread DUBOST Brice
Manu Abraham a écrit :
 Hi Brice,
 
 On Mon, Jan 25, 2010 at 12:09 AM, DUBOST Brice
 dub...@crans.ens-cachan.fr wrote:
 Hello

 Powercam just made a new version of their cam, the version 4

 Unfortunately this CAM doesn't work with gnutv and applications based on
 libdvben50221

 This cam return TIMEOUT errors (en50221_stdcam_llci_poll: Error reported
 by stack:-3) after showing the supported ressource id.


 I found out that this cam works with the test application of the
 libdvben50221

 The problem is that this camreturns two times the list of supported ids
 (as shown in the log) this behavior make the llci_lookup_callback
 (en50221_stdcam_llci.c line 338)  failing to give the good ressource_id
 at the second call because there is already a session number (in the
 test app the session number is not tested)

 I solved the problem commenting out the test for the session number as
 showed in the joined patch (against the latest dvb-apps, cloned today)

 Since I'm not an expert of the libdvben50221, I'm asking the list if
 there is better way to solve this problem and improve my patch so it can
 be integrated upstream.
 
 
 
 Very strange that, it responds twice on the same session.
 Btw, What DVB driver are you using ? budget_ci or budget_av ?

Hello

The card is a DVB: registering new adapter (TT-Budget S2-3200 PCI) and
the driver used is budget_ci

Do you want me to run some more tests ?

Regards

-- 
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
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: [linux-dvb] SheevaBox as a media Server and a Fit-PC as a streaming client?

2010-01-01 Thread DUBOST Brice
Markus Rechberger a écrit :
 Hi,
 
 On Wed, Dec 16, 2009 at 4:12 PM, Lothar Behrens
 lothar.behr...@lollisoft.de wrote:
 Hi,

 I am new here and start with a setup question.

 The media or NAS server I think about: http://plugcomputer.org/

 It has a high speed USB 2.0 port and a gigabit Lan.

 
 http://support.sundtek.com/index.php/topic,179.0.html (english)
 http://support.sundtek.com/index.php/topic,178.0.html (german)
 
 This might be interesting for you.
 
 Markus
 

hello

MuMuDVB is reported to work fine on a sheevaplug

Best regards

-- 
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
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: S2API and DVB-T tuning [Solved]

2009-10-20 Thread DUBOST Brice
DUBOST Brice a écrit :
 DUBOST Brice a écrit :
 Hello,

 I have some problems with DVB-T tuning under s2-api/DVB API 5

 To run these tests I use scan-s2-7effc68db255

 My machine runs the following kernel (uname -a)
 Linux fixe_barcelone 2.6.31-13-generic #42-Ubuntu SMP Thu Oct 8 20:03:54
 UTC 2009 x86_64 GNU/Linux

 And I own 3 DVB-T devices :
 1:
 01:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
  Subsystem: Technotrend Systemtechnik GmbH Device 1012
  Flags: bus master, medium devsel, latency 64, IRQ 21
  Memory at fa6ffc00 (32-bit, non-prefetchable) [size=512]
  Kernel driver in use: budget_ci dvb
  Kernel modules: budget-ci
 2:
 Bus 001 Device 010: ID 2040:7070 Hauppauge

 3:
 Bus 001 Device 011: ID 07ca:a815 AVerMedia Technologies, Inc.

 All three devices tune well and work flawlessly with scan (dvb api v3)
 But when I use scan-s2, only the AVerMedia is able to lock

 I use the dvb-t/es-Collserola as an initial tuning file.

 I thought the S2API shouldn't change the tuning behavior.

 I tried to search the Mailing list archives via google I unfortunately
 found nothing. I'm sorry if this subject was discussed before.

 What can I do to investigate more on this issue ?

 
 Hello
 
 One more information, if I change
 
 51400 8MHz 2/3 AUTO QAM64 8k 1/4 NONE
 
 by
 
 51400 8MHz 2/3 AUTO AUTO 8k 1/4 NONE
 
 it works with scan-s2
 
 With old scan it works for both
 
 Hope this will help to find the issue
 


Hello

After playing a bit more with S2API, I understood that the S2API is
using DVB API v3 for DVB-T. So I investigated a bit more this issue.

The problem came from the fact that scan-s2 was not giving all the
parameters needed for DVB-T to the new API

By making scan-s2 setting the following parameters, it works
DTV_DELIVERY_SYSTEM
DTV_FREQUENCY
DTV_MODULATION
DTV_GUARD_INTERVAL
DTV_CODE_RATE_HP
DTV_CODE_RATE_LP
DTV_TRANSMISSION_MODE
DTV_HIERARCHY
DTV_BANDWIDTH_HZ


Problem solved :D

Best regards

-- 
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
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


S2API and DVB-T tuning

2009-10-12 Thread DUBOST Brice
Hello,

I have some problems with DVB-T tuning under s2-api/DVB API 5

To run these tests I use scan-s2-7effc68db255

My machine runs the following kernel (uname -a)
Linux fixe_barcelone 2.6.31-13-generic #42-Ubuntu SMP Thu Oct 8 20:03:54
UTC 2009 x86_64 GNU/Linux

And I own 3 DVB-T devices :
1:
01:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Technotrend Systemtechnik GmbH Device 1012
Flags: bus master, medium devsel, latency 64, IRQ 21
Memory at fa6ffc00 (32-bit, non-prefetchable) [size=512]
Kernel driver in use: budget_ci dvb
Kernel modules: budget-ci
2:
Bus 001 Device 010: ID 2040:7070 Hauppauge

3:
Bus 001 Device 011: ID 07ca:a815 AVerMedia Technologies, Inc.

All three devices tune well and work flawlessly with scan (dvb api v3)
But when I use scan-s2, only the AVerMedia is able to lock

I use the dvb-t/es-Collserola as an initial tuning file.

I thought the S2API shouldn't change the tuning behavior.

I tried to search the Mailing list archives via google I unfortunately
found nothing. I'm sorry if this subject was discussed before.

What can I do to investigate more on this issue ?

PS : I join the debug output for the sucessful and unsucessful tuning

Thanks

-- 
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
Oct 12 13:02:28 fixe_barcelone kernel: [228614.407730] DiB7000P: setting output 
mode for demod 880139055000 to 0
Oct 12 13:02:28 fixe_barcelone kernel: [228614.416623] DiB0070: Tuning for 
Band: 2 (514000 kHz)
Oct 12 13:02:28 fixe_barcelone kernel: [228614.448106] DiB0070: HFDIV code: 5
Oct 12 13:02:28 fixe_barcelone kernel: [228614.448112] DiB0070: VCO = 1
Oct 12 13:02:28 fixe_barcelone kernel: [228614.448115] DiB0070: VCOF in kHz: 
6168000 ((6*514000)  1))
Oct 12 13:02:28 fixe_barcelone kernel: [228614.448120] DiB0070: REFDIV: 1, 
FREF: 12000
Oct 12 13:02:28 fixe_barcelone kernel: [228614.448124] DiB0070: FBDIV: 85, 
Rest: 43520
Oct 12 13:02:28 fixe_barcelone kernel: [228614.448127] DiB0070: Num: -22016, 
Den: 255, SD: 1
Oct 12 13:02:28 fixe_barcelone kernel: [228614.513606] DiB0070: CAPTRIM=64; ADC 
= 905 (ADC)  1590mV
Oct 12 13:02:28 fixe_barcelone kernel: [228614.513613] DiB0070: CAPTRIM=64 is 
closer to target (505/3000)
Oct 12 13:02:28 fixe_barcelone kernel: [228614.534355] DiB0070: CAPTRIM=32; ADC 
= 35 (ADC)  61mV
Oct 12 13:02:28 fixe_barcelone kernel: [228614.534362] DiB0070: CAPTRIM=32 is 
closer to target (365/505)
Oct 12 13:02:28 fixe_barcelone kernel: [228614.554356] DiB0070: CAPTRIM=48; ADC 
= 34 (ADC)  59mV
Oct 12 13:02:28 fixe_barcelone kernel: [228614.574981] DiB0070: CAPTRIM=56; ADC 
= 141 (ADC)  247mV
Oct 12 13:02:28 fixe_barcelone kernel: [228614.574988] DiB0070: CAPTRIM=56 is 
closer to target (259/365)
Oct 12 13:02:28 fixe_barcelone kernel: [228614.594356] DiB0070: CAPTRIM=60; ADC 
= 285 (ADC)  500mV
Oct 12 13:02:28 fixe_barcelone kernel: [228614.594363] DiB0070: CAPTRIM=60 is 
closer to target (115/259)
Oct 12 13:02:28 fixe_barcelone kernel: [228614.614357] DiB0070: CAPTRIM=62; ADC 
= 420 (ADC)  738mV
Oct 12 13:02:28 fixe_barcelone kernel: [228614.614364] DiB0070: CAPTRIM=62 is 
closer to target (20/115)
Oct 12 13:02:28 fixe_barcelone kernel: [228614.634484] DiB0070: CAPTRIM=61; ADC 
= 343 (ADC)  602mV
Oct 12 13:02:29 fixe_barcelone kernel: [228614.759111] DiB7000P: SPLIT 
880139055000: 176
Oct 12 13:02:29 fixe_barcelone kernel: [228614.790742] DiB7000P: using default 
timf
Oct 12 13:02:29 fixe_barcelone kernel: [228615.090748] DiB7000P: updated 
timf_frequency: 20452445 (default: 20452225)
Oct 12 13:02:29 fixe_barcelone kernel: [228615.090756] DiB7000P: relative 
position of the Spur: 2000k (RF: 514000k, XTAL: 12000k)
Oct 12 13:02:29 fixe_barcelone kernel: [228615.091871] DiB7000P: PALF COEF: 0 
re: 25 im: 124
Oct 12 13:02:29 fixe_barcelone kernel: [228615.095246] DiB7000P: PALF COEF: 1 
re: -103 im: 43
Oct 12 13:02:29 fixe_barcelone kernel: [228615.098618] DiB7000P: PALF COEF: 2 
re: -52 im: -79
Oct 12 13:02:29 fixe_barcelone kernel: [228615.101995] DiB7000P: PALF COEF: 3 
re: 54 im: -53
Oct 12 13:02:29 fixe_barcelone kernel: [228615.105368] DiB7000P: PALF COEF: 4 
re: 45 im: 30
Oct 12 13:02:29 fixe_barcelone kernel: [228615.108745] DiB7000P: PALF COEF: 5 
re: -11 im: 28
Oct 12 13:02:29 fixe_barcelone kernel: [228615.112995] DiB7000P: PALF COEF: 6 
re: -5 im: 0
Oct 12 13:02:29 fixe_barcelone kernel: [228615.116373] DiB7000P: PALF COEF: 7 
re: 0 im: 19
Oct 12 13:02:29 fixe_barcelone kernel: [228615.120871] DiB7000P: using updated 
timf
Oct 12 13:02:29 fixe_barcelone kernel: [228615.124493] DiB7000P: setting output 
mode for demod 880139055000 to 5
Oct 12 13:02:29 fixe_barcelone kernel: [228615.129290] function : 
dvb_dmxdev_filter_set
Oct 12 13:02:29 fixe_barcelone kernel: [228615.129514] function : 
dvb_dmxdev_filter_set

Oct 12 13:01:55 fixe_barcelone kernel: [228581.408427] DiB7000P: setting output 

Re: S2API and DVB-T tuning

2009-10-12 Thread DUBOST Brice
DUBOST Brice a écrit :
 Hello,
 
 I have some problems with DVB-T tuning under s2-api/DVB API 5
 
 To run these tests I use scan-s2-7effc68db255
 
 My machine runs the following kernel (uname -a)
 Linux fixe_barcelone 2.6.31-13-generic #42-Ubuntu SMP Thu Oct 8 20:03:54
 UTC 2009 x86_64 GNU/Linux
 
 And I own 3 DVB-T devices :
 1:
 01:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
   Subsystem: Technotrend Systemtechnik GmbH Device 1012
   Flags: bus master, medium devsel, latency 64, IRQ 21
   Memory at fa6ffc00 (32-bit, non-prefetchable) [size=512]
   Kernel driver in use: budget_ci dvb
   Kernel modules: budget-ci
 2:
 Bus 001 Device 010: ID 2040:7070 Hauppauge
 
 3:
 Bus 001 Device 011: ID 07ca:a815 AVerMedia Technologies, Inc.
 
 All three devices tune well and work flawlessly with scan (dvb api v3)
 But when I use scan-s2, only the AVerMedia is able to lock
 
 I use the dvb-t/es-Collserola as an initial tuning file.
 
 I thought the S2API shouldn't change the tuning behavior.
 
 I tried to search the Mailing list archives via google I unfortunately
 found nothing. I'm sorry if this subject was discussed before.
 
 What can I do to investigate more on this issue ?
 

Hello

One more information, if I change

51400 8MHz 2/3 AUTO QAM64 8k 1/4 NONE

by

51400 8MHz 2/3 AUTO AUTO 8k 1/4 NONE

it works with scan-s2

With old scan it works for both

Hope this will help to find the issue

Regards

-- 
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
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


MuMuDVB 1.6

2009-10-07 Thread DUBOST Brice
Hello

I think this could interest some persons on this list

MuMuDVB 1.6 is out. MuMuDVB is a DVB streaming software with low memory
and CPU footprint.

The main goal of MuMuDVB is to split a full transponder over several
Mulitcast Group (each one correspondig to one channel/service)

MuMuDVB is able to stream in Multicast or in HTTP unicast. It supports
scrambled channels via CAM modules (using the libdvben50221), it is able
to find automatically the channels in the transponder. It is also able
to rewrite the PAT PID for better compatibility with set top boxes.

This version is the first to include the support for HTTP unicast and
improves the overall stability.

All ideas/comments are welcome (mumudvb at braice dot net)

MuMuDVB main site : http://mumudvb.braice.net

Regards

-- 
Brice

A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
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