Version 0.7 on Ibex

In short, yes, but it's probably easier if you just use this ... https://edge.launchpad.net/~lamothe/+archive.

Advantages: No memory leaks, more stable because it's loosely coupled to xine (i.e. a xine crash won't bring down the app), easier to set up, signal strength meter, channel editor.

Disadvantages: No support for ATSC or DVB-S, no Conditional Access device support, poor support for multiple audio streams/languages.

Thanks,

Michael

Thank you, I was able to upgrade with the new source list, however when I now start Me-Tv I get:
Me TV 0.7.2
11/08/2008 09:52:08: No frontend available
11/08/2008 09:52:08: Me TV terminated

I am using DVB-C not DVB-S. Does the lack of support for DVB-S include Cable as well?

Thanks

1. Do you have another application that is using the device?
2. Does /dev/dvb/adapter0 exist?

Try the --verbose option to see what it says.

Here is the verbose output:
Me TV 0.7.2
11/08/2008 11:11:30: Removing /apps/me-tv/profiles
11/08/2008 11:11:30: Scanning DVB devices ...
11/08/2008 11:11:30: Opening frontend device: /dev/dvb/adapter0/frontend0
11/08/2008 11:11:36: Frontend not supported
11/08/2008 11:11:36: Exception: No frontend available
11/08/2008 11:11:36: No frontend available
11/08/2008 11:11:36: Me TV terminated

How would I confirm your question #2? Me-TV 0.5 works fine, when I upgrade, I get the above, I can downgrade back and it works again.

If this is helpful, here's dmesg output:

[ 16.747886] tveeprom 2-0050: Hauppauge model 72001, rev B3F0, serial# 3399251
[ 16.747890] tveeprom 2-0050: MAC address is 00-0D-FE-33-DE-53
[ 16.747892] tveeprom 2-0050: tuner model is Xceive XC5000 (idx 150, type 4)
[ 16.747894] tveeprom 2-0050: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
[ 16.747896] tveeprom 2-0050: audio processor is AU8522 (idx 44)
[ 16.747897] tveeprom 2-0050: decoder processor is AU8522 (idx 42)
[ 16.747898] tveeprom 2-0050: has no radio, has IR receiver, has no IR transmitter
[ 16.747900] hauppauge_eeprom: hauppauge eeprom: model=72001
[ 16.821387] xc5000: Successfully identified at address 0x61
[ 16.821390] xc5000: Firmware has not been loaded previously
[ 16.821393] DVB: registering new adapter (au0828)
[ 16.821395] DVB: registering frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
[ 16.821799] Registered device AU0828 [Hauppauge HVR950Q]

That looks to be an ATSC card or are there multiple DVB devices on that card?

It's this card:
http://www.hauppauge.com/site/products/data_hvr950q.html

It supports ATSC, NTSC and Cable.

All of my channels are QAM256 channels.

Ahhh, ok. I believe that Clear QAM is not standard DVB-C, it uses a special modulation I think. Jeff and I had a discussion about this a little while back ... https://answers.edge.launchpad.net/me-tv/+question/30257.

I see. So I should just stick with .05 then?

I assume that 0.5 is using the ATSC part of your device. I have no idea now to support Clear CAM.

Here's a sample of my channels.conf

MeTV works perfectly with this device using ClearQAM on 0.5 I don't know why this would be considered ATSC over DVB-C....

2 PBS WGBHDT2 HD:747000000:QAM_256:51:53:1

2 PBS WGBXDT2 SD:753000000:QAM_256:49:52:1

2 PBS WGBXDT4 SD:753000000:QAM_256:57:58:2

2 PBS WGBXDT3 SD:753000000:QAM_256:51:54:3

2 PBS WGBH SD:729000000:QAM_256:271:272:2

3 NECN SD:729000000:QAM_256:225:226:3

3 NECN SD:741000000:QAM_256:511:512:26

4 CBS WBZDT HD:645000000:QAM_256:3921:3922:2

4 CBS WBZ SD:729000000:QAM_256:233:234:4

5 ABC WCVBDT HD:651000000:QAM_256:3905:3906:1

5 ABC WCVB SD:729000000:QAM_256:243:244:5

6 FOX WFXTDT HD:645000000:QAM_256:3907:3905:1

6 FOX WFXT SD:729000000:QAM_256:241:242:6

7 NBC WHDHDT HD:651000000:QAM_256:3921:3922:2

7 NBC WHDH SD:729000000:QAM_256:239:240:7

8 CW WLVIDT HD:747000000:QAM_256:39:40:2

8 CW WLVIDT SD:729000000:QAM_256:235:236:8

9 PBS WSBE SD:729000000:QAM_256:269:270:9

10 Leased Access LEAC010 SD:729000000:QAM_256:237:238:10

11 PBS WGBX SD:723000000:QAM_256:245:248:11

12 QVC SD:723000000:QAM_256:249:250:12

15 NBC WJAR SD:741000000:QAM_256:509:510:23

15 Govt Access GOAC23 SD:741000000:QAM_256:513:514:24

That's very interesting. I really don't know much about it, that's why I'm waiting for someone who knows about it, with an appropriate device to implement it. Is that you?

Thanks,

Michael

I can try, but by no means am I an expert in this realm!! ;)

I will do whatever I can to help out.

We should continue this conversion offline. Send me your email? Do you have any development experience? ATSC shouldn't be hard to implement, it's one of the easiest to do. I can give you lots of support. All I'm looking for is someone to look into any issues that ATSC users might have, specifically ATSC (or Clear QAM if you want to support that).

Sure thing:
Sean gorman at zenbe dot com

remove the space between the first and last name.

I'm having this same problem, with OTA signals

Me TV 0.7 does not support ATSC. The last message I got from camoto was that he was going to ask his friend to look into it.

but atsc works fine in 0.5

And does not work in 0.7.

Just out of curiosity why was ATSC support dropped from me-tv? Will it get re-incorporated?

Sure, that's a valid question. 0.7 has it's own scanner, I did this because there are still a few issues the scan appliation that comes with dvb-utils. I end up fielding a lot of questions about `scan` and why it doesn't work for people, or they can't work it out. I knew enough to build my own scanner so I did. But of course I can only really do this on a device that I have, fortunately DVB-C is very easy to implement if you've already implemented DVB-T.

Unlike DVB, ATSC uses Virtual Channel Tables (VCT) to deliver its channel information and I have no way to build against it without a device and without being in an ATSC region. Everything else from ATSC should still work, you just need to get your channels in the database.

As I have always said, I'm more than happy to include any updates from any person that actually feels like helping.

Thanks,

Michael

Last time I tested ME-TV, I dont recall the version, both VSB and QAM work well (us-atsc).

I used my own channels.conf file generated from recent w_scan (with my ATSC/QAM modifications included). EPG didn't work at all, but all I cared about is moving pictures with audio and good lip sync.

Me too, after upgrade to latest me-tv I am experiencing a "no frontend available" error.
Previous version worked fine. Unfortunately I don't know the version number (shame on me...)

output of uname -a
Linux ubuntu 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

output of tail /var/log/messages
Jan 2 21:03:15 ubuntu kernel: [42265.023876] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Jan 2 21:03:15 ubuntu kernel: [42265.024099] DVB: registering new adapter (DVBWorld DVB-S 2102 USB2.0)
Jan 2 21:03:15 ubuntu kernel: [42265.228851] dw2102: Attached stv0299!
Jan 2 21:03:15 ubuntu kernel: [42265.228856]
Jan 2 21:03:15 ubuntu kernel: [42265.230502] DVB: registering frontend 0 (ST STV0299 DVB-S)...
Jan 2 21:03:15 ubuntu kernel: [42265.234816] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.7/usb1/1-4/input/input12
Jan 2 21:03:15 ubuntu kernel: [42265.280578] dvb-usb: schedule remote query interval to 150 msecs.
Jan 2 21:03:15 ubuntu kernel: [42265.280594] dvb-usb: DVBWorld DVB-S 2102 USB2.0 successfully initialized and connected.

output of lsmod |grep dvb
dvb_pll 18824 1
dvb_usb_dw2102 18692 1
dvb_usb 27276 1 dvb_usb_dw2102
dvb_core 99628 2 stv0299,dvb_usb
i2c_core 36128 5 dvb_pll,stv0299,dvb_usb_dw2102,dvb_usb,nvidia
usbcore 175376 6 dvb_usb_dw2102,dvb_usb,uvcvideo,uhci_hcd,ehci_hcd

output of me-tv --verbose
~$ /usr/bin/me-tv --verbose
Me TV 0.7.6
02/01/2009 21:55:06: Removing /apps/me-tv/profiles
02/01/2009 21:55:06: Scanning DVB devices ...
02/01/2009 21:55:06: Opening frontend device: /dev/dvb/adapter0/frontend0
02/01/2009 21:55:06: Frontend not supported
02/01/2009 21:55:06: Exception: No frontend available
02/01/2009 21:55:06: No frontend available
02/01/2009 21:55:06: Me TV terminated

thanks for any help
marco

Hi Marco,

Maybe I've missed something, but what did you need help with?

Thanks,

Michael

Hi Michael
Thanks for the quick answer (and for me-tv too!)

As I said "Me too, after upgrade to latest me-tv I am experiencing a "no frontend available" error", while before it worked...

Any hint ?

(btw version 0.6.4 finds the frontend, but I have problems to let it read the channels.conf. too bad!)

I was just reading https://answers.launchpad.net/me-tv/+question/46081 as well as device_manager.cc line 99 )more or less)
it seems not to be dvb-s support in 0.7+ versions!!!!!!!!!!!!!!
gulp!
too bad.
thanks anyway

Hi Marco,

Well, 0.7.8 has a channels.conf file importer. Me TV's scanner cannot do ATSC, which has been holding ATSC back, but you should be able to use the channels.conf importer. I can easily modify the channels.conf parser to support an ATSC channels.conf file.

It should just work if you're interested in giving it a go. Can you build from source? Email me directly if you can.

Thanks,

Michael