Mailing List Archive: MythTV: Users

(no subject)

Index | Next | Previous | View Threaded

t00cool2001 at yahoo

Sep 22, 2006, 2:40 PM

Post #1 of 4 (1278 views)
Permalink

(no subject)

I'm sorry if I sound silly but I'm only a student with no experiece
with MythTv, I was wondering if some one would be able to give me a
step by step of how to install it on a XBOX, bearing in mind I have
no experience with the program?
Cheers

---------------------------------
All-new Yahoo! Mail - Fire up a more powerful email and get things done faster.

dsmolka at gmail

Sep 22, 2006, 5:11 PM

Post #2 of 4 (1185 views)
Permalink

Re: (no subject) [In reply to]

Not sure if this is what you want to hear, but the Xbox is really only
useful as a Myth frontend. There's no way to get a capture device into
it, so recording TV with an Xbox is not possible.

Instructions on how to set up an Xbox as a frontend are on the wiki:
http://www.mythtv.org/wiki/index.php/Xbox_Frontend

Base requirements for a Myth backend are pretty modest, and with some
effort you can likely find a capable system for free or close to it. A
P3 700 is enough to run an SD setup, and machines stronger than this
are frequently doorstops these days. Have a look at freecycle.org --
you might get lucky.

However, you'll most likely have to spend some cash on a
hardware-encoding capture card (eg Hauppage PVR 150); you may need to
buy a capable video card (nvidia gf4 or better); you may need to boost
your RAM (256 will work, but you'll really want 512); and you'll need
a big HDD -- I wouldn't recommend anything less than 200 GB.

Good luck.

PS -- make sure you put in a subject next time -- messages without
subjects are often ignored.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

list-mythtv at bluecamel

Sep 23, 2006, 2:18 PM

Post #3 of 4 (1172 views)
Permalink

(no subject) [In reply to]

Greets.

For one of the local OTA ATSC stations here (Raleigh / Durham NC
area, the station is WTVD 11.1) I'm seeing audio cut in and out 100%
of the time. If I run mythfrontend -v audio the output shows buffer
under runs, and lots of them. But wait! This same exact stream plays
perfectly fine with both xine and mplayer. By this I mean I can
either run mplayer dvb:// and tune the stream directly OR I can use
mplayer and xine to playback a stream that was recorded by MythTV.
The playback sounds fine with mplayer and xine.

So, I'm thinking there must be something "special" about the audio
track on this one OTA ATSC station. Using mplayer -v to view a
previously recorded show from this station I see lots of the
following when decoding the "broken" stream. Notice the "ERROR,
descriptor len is too long, skipping" coming from mplayer: (But
still, even with this, the stream sounds fine!)

COLLECT_SECTION, start: 64, size: 184, collected: 184% 3% 0.8% 0 0
SKIP: 0+1, TID: 0, TLEN: 13, COLLECTED: 184
PARSE_PAT: section_len: 13, section 0/0
PROG: 1 (1-th of 1), PMT: 48
COLLECT_SECTION, start: 64, size: 184, collected: 184
SKIP: 0+1, TID: 2, TLEN: 86, COLLECTED: 184
FILL_PMT(prog=1), PMT_len: 184, IS_START: 64, TS_PID: 48, SIZE=184, M=0,
ES_CNT=2, IDX=0, PMT_PTR=0x8805300
PROG DESCR, TAG=5, LEN=4(4)
PROG DESCR, TAG=5, LEN=4(4)
PROG DESCR, TAG=5, LEN=4(4)
PROG DESCR, TAG=5, LEN=4(4)
PROG DESCR, TAG=5, LEN=4(4)
PROG DESCR, TAG=5, LEN=4(4)
ERROR, descriptor len is too long, skipping
...descr id: 0x2, len=3
...descr id: 0x6, len=1
PARSE_PMT(1 INDEX 0), STREAM: 0, FOUND pid=0x31 (49), type=0x10000002,
ES_DESCR_LENGTH: 8, bytes left: 28
...descr id: 0x5, len=4
...descr id: 0x81, len=6
...descr id: 0xa, len=4
Language Descriptor: eng
...descr id: 0x6, len=1
PARSE_PMT(1 INDEX 1), STREAM: 1, FOUND pid=0x34 (52), type=0x2000,
ES_DESCR_LENGTH: 23, bytes left: 0

Compare this to the stream from a different OTA ATSC station that
MythTV has no problems playing back. No obvious ERRORs here.

COLLECT_SECTION, start: 64, size: 184, collected: 184% 4% 1.0% 0 0
SKIP: 0+1, TID: 0, TLEN: 13, COLLECTED: 184
PARSE_PAT: section_len: 13, section 0/0
PROG: 1 (1-th of 1), PMT: 48
COLLECT_SECTION, start: 64, size: 184, collected: 184
SKIP: 0+1, TID: 2, TLEN: 79, COLLECTED: 184
FILL_PMT(prog=1), PMT_len: 184, IS_START: 64, TS_PID: 48, SIZE=184, M=0,
ES_CNT=3, IDX=0, PMT_PTR=0x8805300
PROG DESCR, TAG=5, LEN=4(4)
...descr id: 0x11, len=1
...descr id: 0x10, len=6
...descr id: 0x6, len=1
...descr id: 0x86, len=7
PARSE_PMT(1 INDEX 0), STREAM: 0, FOUND pid=0x31 (49), type=0x10000002,
ES_DESCR_LENGTH: 23, bytes left: 32
...descr id: 0x5, len=4
...descr id: 0x81, len=8
...descr id: 0xa, len=4
Language Descriptor: eng
PARSE_PMT(1 INDEX 1), STREAM: 1, FOUND pid=0x34 (52), type=0x2000,
ES_DESCR_LENGTH: 22, bytes left: 5
PARSE_PMT(1 INDEX 2), STREAM: 2, FOUND pid=0x3a (58), type=0xffffffff,
ES_DESCR_LENGTH: 0, bytes left: 0

My signal strength is fine on this channel and the above problem is
present on _every_ show for this channel. Any thoughts? Is this
simply a case of a broken audio stream that MythTV isn't handling well?

Thanks for the help!

--
Scott
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jacob at steenhagen

Oct 3, 2006, 1:49 PM

Post #4 of 4 (1161 views)
Permalink

(no subject) [In reply to]

> Don't the spiders just follow links? Someone posted urls Google
> had found for MythWeb installations running on non-standard ports,
> but how do you suppose Google found them? It's probably because
> people put MythWeb on a non-standard port and then put a convenient
> link to the non-standard port from their server's normal pages.

That's one very real possibility. They could also have clicked a link w/in
mythweb to a site that had publicly accessible weblogs (a bad idea in
itself), bookmarked it using a third party service that makes bookmarks
publicly available or a few other things.

> [...] the least you could do is NOT put a link to your MythWeb
> installation out there where the bots can find it....

Yep. That can be on a non-standard port or just at a non-standard URL...
they are actually both equally effective (eg,
http://myth.mycomputer.ext/s3cr3t). The key is to not let the URL become
pubicly known. However, that's all just secuirty through obscurity and can
be quite easily comprimised by even accidently doing one of the above
actions.

The best bet is to actually secure your install with a password of some
sort. I'd bet if you thought about it long enough, you could probably come
up with the URL to my install (no, it's not www.steenhagen.us/mythweb, but
it's not super-obscure either). But once you found it, you'd be greated
with a password dialog (after the non-trusted SSL cert warning). I'm not
saying it's hack proof, very few things are, but it's good enough (TM).

--
http://www.steenhagen.us/~jake/blog/
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads