Re: Firewire+PVR on same cablebox? WAS [Re: [mythtv-users] Firewire and DCT-6200]

2005-10-20 Thread Peter Judge
On Wed, 2005-10-19 at 16:09 -0400, Steve Adeff wrote:
snip
 I got HD working. but no ESPNHD, TNTHD, etc. ugh.
 I also notice that the only channels I can get are the OTA and basic
 cable 
 package channels. So no digital cable, no spanish package channels (no
 Fox 
 Sports Espanol, AR!) and no Sports Package channels.

Some cable providers do provide everything through the Firewire port
(like RCN in Boston); some don't (like Comcast in Boston).

 Could I setup Myth to use some channels via firewire and some via a
 PVR card 
 for the same cable box?

Good question. I've been struggling with this on and off for some time
now, with no real success. You can set up multiple video sources (one
for firewire and one for the PVR) and prioritise one of them higher than
the other, but you're left with the chance that Myth will (correctly)
schedule both tuners to record something simultaneously. It's also easy
to mess up a recording if you watch LiveTv while recording, and change
channels doing so.

At the moment I've decided just to use the PVR (since that gets
everything but the HD stuff). The firewire is still very useful for
channel change stuff.

Regards,
Peter



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-19 Thread Steve Adeff
So I got my DCT-6200 the other day, bought a firewire cable, connected them 
got it running so I can capture streams, compiled 6200ch and can change 
channels. Its amazing how painless my MythTV experience has been, props to 
all involved.

now on to why I responded to this thread...

How do I set the speed from 400mbps to 100mbps? Is there any plugctl 
documentation? I can't seem to find any.

also, I notice my box is on node 2, it works and all, and I see many people 
have this setup. I'm hoping anyone that does, if they encountered any issues 
that I should be aware of?

I'd like to make sure it all works and check channels before going through the 
MythTV process, so any help in this is appreciated!

Thanks!
Steve

On Sunday 16 October 2005 21:00, Alex Brekken wrote:
 Wow!! Big improvement for me. As I posted earlier, my firewire reliability
 was only around 60% (at best). Since running these commands I'm batting
 100% so far. It's only been a day, but I've tested it quite a bit and
 haven't had any false starts from either live tv or recordings from
 firewire. I also changed from point-to-point to broadcast, and changed the
 speed from 400 mbps to 100 mbps as suggested. I doubt these were the reason
 for the change since I've played with those settings quite a bit before
 with no improvement in reliability.

 Question: since I have no idea what these plugctl commands really do, I'm
 wondering if they need to be re-run anytime the machine is rebooted...?

 Thanks Curtis for the great find! I know there's quite a few other Firewire
 users who have the same reliability problems, so I hope they give this a
 try.

 On 10/14/05, Curtis Stanford [EMAIL PROTECTED] wrote:
  OK, I think I've found something that helps with this firewire stuff.
  See this message:
 
  http://www.netzwerk-aktiv.com/pub/doc/newsletters/linux1394-user/html/
  2344.html
 
  I followed the advice in the first paragraph and typed:
 
  plugctl -n 1 opcr[0].channel=63
  plugctl -n 1 opcr[0].bcast_connection=1
 
  Then I set the firewire connection to broadcast, 100Mbps in mythtv-
  setup.
 
  Now, the test-mpeg2 command works EVERY time (don't use the -r 1
  argument, just test-mpeg2). Also, mythtv Watch TV command works
  EVERY time where before it worked maybe 50% of the time or hung.
 
  I have yet to see if it helps with my recordings being cut short but
  I'll let the list know how it goes.
 
  If anyone else benefits from this, please post your results.
 
  Thanks
 
  Curtis
 
 
 
  ___
  mythtv-users mailing list
  mythtv-users@mythtv.org
  http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-19 Thread Curtis Stanford

Congrats! My box is on Node 1 but I don't think that matters much.

You don't need to set the speed with plugctl. I just set it to 100 in  
the mythtv-setup GUI and the backend sets it for me. I don't think it  
matters that much what it's set to but 100 is plenty fast enough (not  
sure about HD??)


I'm still having problems with some recordings being cut a bit short,  
even though there are no errors on the backend. Otherwise, working  
great! Next stop is to try some HD!


Have fun.

Curtis

On Oct 19, 2005, at 11:40 AM, Steve Adeff wrote:

So I got my DCT-6200 the other day, bought a firewire cable,  
connected them
got it running so I can capture streams, compiled 6200ch and can  
change
channels. Its amazing how painless my MythTV experience has been,  
props to

all involved.

now on to why I responded to this thread...

How do I set the speed from 400mbps to 100mbps? Is there any plugctl
documentation? I can't seem to find any.

also, I notice my box is on node 2, it works and all, and I see  
many people
have this setup. I'm hoping anyone that does, if they encountered  
any issues

that I should be aware of?

I'd like to make sure it all works and check channels before going  
through the

MythTV process, so any help in this is appreciated!

Thanks!
Steve

On Sunday 16 October 2005 21:00, Alex Brekken wrote:

Wow!! Big improvement for me. As I posted earlier, my firewire  
reliability
was only around 60% (at best). Since running these commands I'm  
batting

100% so far. It's only been a day, but I've tested it quite a bit and
haven't had any false starts from either live tv or recordings from
firewire. I also changed from point-to-point to broadcast, and  
changed the
speed from 400 mbps to 100 mbps as suggested. I doubt these were  
the reason
for the change since I've played with those settings quite a bit  
before

with no improvement in reliability.

Question: since I have no idea what these plugctl commands really  
do, I'm
wondering if they need to be re-run anytime the machine is  
rebooted...?


Thanks Curtis for the great find! I know there's quite a few other  
Firewire
users who have the same reliability problems, so I hope they give  
this a

try.

On 10/14/05, Curtis Stanford [EMAIL PROTECTED] wrote:

OK, I think I've found something that helps with this firewire  
stuff.

See this message:

http://www.netzwerk-aktiv.com/pub/doc/newsletters/linux1394-user/ 
html/

2344.html

I followed the advice in the first paragraph and typed:

plugctl -n 1 opcr[0].channel=63
plugctl -n 1 opcr[0].bcast_connection=1

Then I set the firewire connection to broadcast, 100Mbps in mythtv-
setup.

Now, the test-mpeg2 command works EVERY time (don't use the -r 1
argument, just test-mpeg2). Also, mythtv Watch TV command works
EVERY time where before it worked maybe 50% of the time or hung.

I have yet to see if it helps with my recordings being cut short but
I'll let the list know how it goes.

If anyone else benefits from this, please post your results.

Thanks

Curtis



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Firewire+PVR on same cablebox? WAS [Re: [mythtv-users] Firewire and DCT-6200]

2005-10-19 Thread Steve Adeff
On Wednesday 19 October 2005 15:14, Curtis Stanford wrote:
 Congrats! My box is on Node 1 but I don't think that matters much.

 You don't need to set the speed with plugctl. I just set it to 100 in
 the mythtv-setup GUI and the backend sets it for me. I don't think it
 matters that much what it's set to but 100 is plenty fast enough (not
 sure about HD??)

 I'm still having problems with some recordings being cut a bit short,
 even though there are no errors on the backend. Otherwise, working
 great! Next stop is to try some HD!

 Have fun.

 Curtis

I got HD working. but no ESPNHD, TNTHD, etc. ugh.
I also notice that the only channels I can get are the OTA and basic cable 
package channels. So no digital cable, no spanish package channels (no Fox 
Sports Espanol, AR!) and no Sports Package channels.

this kinda makes the firewire thing pointless as I could just as easily 
connect to a PVR-150 at a minor (if any) loss in quality.

Could I setup Myth to use some channels via firewire and some via a PVR card 
for the same cable box?

Steve
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: Firewire+PVR on same cablebox? WAS [Re: [mythtv-users] Firewire and DCT-6200]

2005-10-19 Thread Steve Adeff
On Wednesday 19 October 2005 16:09, Steve Adeff wrote:
 On Wednesday 19 October 2005 15:14, Curtis Stanford wrote:
  Congrats! My box is on Node 1 but I don't think that matters much.
 
  You don't need to set the speed with plugctl. I just set it to 100 in
  the mythtv-setup GUI and the backend sets it for me. I don't think it
  matters that much what it's set to but 100 is plenty fast enough (not
  sure about HD??)
 
  I'm still having problems with some recordings being cut a bit short,
  even though there are no errors on the backend. Otherwise, working
  great! Next stop is to try some HD!
 
  Have fun.
 
  Curtis

 I got HD working. but no ESPNHD, TNTHD, etc. ugh.
 I also notice that the only channels I can get are the OTA and basic cable
 package channels. So no digital cable, no spanish package channels (no Fox
 Sports Espanol, AR!) and no Sports Package channels.

 this kinda makes the firewire thing pointless as I could just as easily
 connect to a PVR-150 at a minor (if any) loss in quality.

 Could I setup Myth to use some channels via firewire and some via a PVR
 card for the same cable box?

 Steve

Hate responding to my own threads but I found this:

http://www.indigita.com/products/pdf/iND60C32.pdf

it would be nice if the pcHDTV guys made a card with one along with some 
firewire ports that would allow us to really make use of our cable box.

Steve
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-16 Thread Alex Brekken
Wow!! Big improvement for me. As I posted earlier, my
firewire reliability was only around 60% (at best). Since running
these commands I'm batting 100% so far. It's only been a day, but
I've tested it quite a bit and haven't had any false starts from
either live tv or recordings from firewire. I also changed from
point-to-point to broadcast, and changed the speed from 400 mbps to 100
mbps as suggested. I doubt these were the reason for the change
since I've played with those settings quite a bit before with no
improvement in reliability. 

Question: since I have no idea what these plugctl commands really
do, I'm wondering if they need to be re-run anytime the machine is
rebooted...? 

Thanks Curtis for the great find! I know there's quite a few other
Firewire users who have the same reliability problems, so I hope they
give this a try. 
On 10/14/05, Curtis Stanford [EMAIL PROTECTED] wrote:
OK, I think I've found something that helps with this firewire stuff.See this message:http://www.netzwerk-aktiv.com/pub/doc/newsletters/linux1394-user/html/
2344.htmlI followed the advice in the first paragraph and typed:plugctl -n 1 opcr[0].channel=63plugctl -n 1 opcr[0].bcast_connection=1Then I set the firewire connection to broadcast, 100Mbps in mythtv-
setup.Now, the test-mpeg2 command works EVERY time (don't use the -r 1argument, just test-mpeg2). Also, mythtv Watch TV command worksEVERY time where before it worked maybe 50% of the time or hung.
I have yet to see if it helps with my recordings being cut short butI'll let the list know how it goes.If anyone else benefits from this, please post your results.ThanksCurtis
___mythtv-users mailing listmythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-16 Thread Curtis Stanford

Yes, the commands need to be run after a reboot. I'm glad that helped.

Curtis

On Oct 16, 2005, at 7:00 PM, Alex Brekken wrote:

Wow!!  Big improvement for me.  As I posted earlier, my firewire  
reliability was only around 60% (at best).  Since running these  
commands I'm batting 100% so far.  It's only been a day, but I've  
tested it quite a bit and haven't had any false starts from  
either live tv or recordings from firewire.  I also changed from  
point-to-point to broadcast, and changed the speed from 400 mbps to  
100 mbps as suggested.  I doubt these were the reason for the  
change since I've played with those settings quite a bit before  
with no improvement in reliability.


Question:  since I have no idea what these plugctl commands really  
do, I'm wondering if they need to be re-run anytime the machine is  
rebooted...?


Thanks Curtis for the great find! I know there's quite a few other  
Firewire users who have the same reliability problems, so I hope  
they give this a try.



On 10/14/05, Curtis Stanford [EMAIL PROTECTED] wrote:  
OK, I think I've found something that helps with this firewire stuff.

See this message:

http://www.netzwerk-aktiv.com/pub/doc/newsletters/linux1394-user/html/
2344.html

I followed the advice in the first paragraph and typed:

plugctl -n 1 opcr[0].channel=63
plugctl -n 1 opcr[0].bcast_connection=1

Then I set the firewire connection to broadcast, 100Mbps in mythtv-
setup.

Now, the test-mpeg2 command works EVERY time (don't use the -r 1
argument, just test-mpeg2). Also, mythtv Watch TV command works
EVERY time where before it worked maybe 50% of the time or hung.

I have yet to see if it helps with my recordings being cut short but
I'll let the list know how it goes.

If anyone else benefits from this, please post your results.

Thanks

Curtis



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users




___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


RE: [mythtv-users] Firewire and DCT-6200

2005-10-14 Thread tgate
 Firewire: No Input in 15 seconds [P:0 N:1] (select)Just a thought, but do you get full time reception if you're not using myth?Does the dropout happen always or only at certain times of the day?I'm wondering if you could be experiencing "fading" issues (http://www.hdtvprimer.com/ANTENNAS/glossaryA.html#fading)___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-14 Thread Curtis Stanford
OK, I think I've found something that helps with this firewire stuff.  
See this message:


http://www.netzwerk-aktiv.com/pub/doc/newsletters/linux1394-user/html/ 
2344.html


I followed the advice in the first paragraph and typed:

plugctl -n 1 opcr[0].channel=63
plugctl -n 1 opcr[0].bcast_connection=1

Then I set the firewire connection to broadcast, 100Mbps in mythtv- 
setup.


Now, the test-mpeg2 command works EVERY time (don't use the -r 1  
argument, just test-mpeg2). Also, mythtv Watch TV command works  
EVERY time where before it worked maybe 50% of the time or hung.


I have yet to see if it helps with my recordings being cut short but  
I'll let the list know how it goes.


If anyone else benefits from this, please post your results.

Thanks

Curtis

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-13 Thread Steve Adeff
On Thursday 13 October 2005 01:09, Curtis Stanford wrote:
 On Oct 12, 2005, at 11:04 PM, Donald Oakes wrote:
  Curtis Stanford wrote:
  On Oct 12, 2005, at 2:35 PM, Todd Greene wrote:
  For what its worth, I use the DCT-6200 and Firewire reliably.
  However, I can't give you my system specifics, since my root
  partition of my HD crashed yesterday, and I can't boot the
  system.   However, it took a while to get it to work right, and
  each system  reboot (which thankfully wasn't often) required a
  manual process.   I was using the firewire port built-in to the
  Foxconn motherboard.
 
  (1) Run plugreport: .  Each time I rebooted, the DCT would show
  up  either in node 0 or node 1 (often changing per reboot).  So,
  for  each reboot, I would have to re-run mythtvsetup and change
  the  DCT-6200 node if it had changed.  There seemed to be no
  rhyme or  reason as to why it keeps changing nodes on reboots.
 
  (2) Get test-mpeg2 to work:  On each reboot, I would need to run
  test-mpeg2 -r [NODE#]  mutiple times (This step is KEY!!) until
  I  get some output.  You'll know when you get output, its
  basically a  stream of binary junk to stdout.  If you don't see
  output after 1  second, press ctrl-c and try again.  With 10
  tries, you'll get it  to work.
 
  (3) Now start mythbackend, and it should work reliably until
  the  next reboot.
 
  Hope this is helpful.  Once I rebuilt my machine with a new HD,
  I'll be happy to answer specific config questions...
 
  -- Todd
 
  Yes, I do all of these things as well. However, it doesn't work
  reliably for me even after these steps. Thanks Todd
 
  Curtis
 
  I have the same difficulty as you, Curtis.  I've even written a
  program to automatically run test-mpeg2 until success each time the
  channel is changed.  Recording is still about 50% reliable via
  firewire.
 
  - Donald

 So what's the difference between us and the people who seem to have
 it working 100% ? I'm still thinking it may be the card or perhaps
 the linux driver. I'm hoping anyone who is having success with this
 mail in with their configurations.

 Curtis

I was going to ask the same thing, I'm getting a firewire cable box soon and 
hope to get it working. I don't run Fedora, so I won't be using the ATrpms 
people talk about, but it would be interesting to get further information on 
this, if its the firewire chipset, the compilation of MythTV, the DCT box 
itself, etc

I'll be able to throw my 2cents in when I get my card.

Steve
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-13 Thread Devan Lippman
On 10/13/05, Steve Adeff [EMAIL PROTECTED] wrote:

On Thursday 13 October 2005 01:09, Curtis Stanford wrote: So what's the difference between us and the people who seem to have
 it working 100% ? I'm still thinking it may be the card or perhaps the linux driver. I'm hoping anyone who is having success with this mail in with their configurations. Curtis
I was going to ask the same thing, I'm getting a firewire cable box soon andhope to get it working. I don't run Fedora, so I won't be using the ATrpmspeople talk about, but it would be interesting to get further information on
this, if its the firewire chipset, the compilation of MythTV, the DCT boxitself, etcI'll be able to throw my 2cents in when I get my card.Steve___
mythtv-users mailing listmythtv-users@mythtv.orghttp://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

I run from source but I'm able to record with 100% reliability over firewire. It probably should be noted that I only use the old analog channels (below 100) and not any of the digital channels.

00:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)

I have libiec61883 installed (no idea the version, its all source and relatively old)
libraw1394-1.2.0
libavc1394-0.5.0
gscanbus-0.7.1
kernel 2.6.8.1

You shouldn't need all of that but its working so I haven't done any house cleaning. I do remember that I had to change my node ID manually when I first started using MythTV with firewire, but that seems to have been fixed.

-- Devan Lippman devan at lippman dot net 
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-13 Thread Big Wave Dave
On 10/13/05, Devan Lippman [EMAIL PROTECTED] wrote:
On 10/13/05, Steve Adeff [EMAIL PROTECTED]
 wrote:

On Thursday 13 October 2005 01:09, Curtis Stanford wrote:
 So what's the difference between us and the people who seem to have
 it working 100% ? I'm still thinking it may be the card or perhaps the linux driver. I'm hoping anyone who is having success with this mail in with their configurations. Curtis

I was going to ask the same thing, I'm getting a firewire cable box soon andhope to get it working. I don't run Fedora, so I won't be using the ATrpmspeople talk about, but it would be interesting to get further information on
this, if its the firewire chipset, the compilation of MythTV, the DCT boxitself, etcI'll be able to throw my 2cents in when I get my card.Steve___
mythtv-users mailing listmythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

I run from source but I'm able to record with 100% reliability
over firewire. It probably should be noted that I only use the
old analog channels (below 100) and not any of the digital channels.

00:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)

I have libiec61883 installed (no idea the version, its all source and relatively old)
libraw1394-1.2.0
libavc1394-0.5.0
gscanbus-0.7.1
kernel 2.6.8.1

You shouldn't need all of that but its working so I haven't done
any house cleaning. I do remember that I had to change my node ID
manually when I first started using MythTV with firewire, but that
seems to have been fixed.

-- Devan Lippman devan at lippman dot net 


Perhaps the ATrpms, are missing some updates that improve FireWire performance?!

Dave

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Jarod Wilson

On Oct 11, 2005, at 20:23, Curtis Stanford wrote:

Is anyone seriously using firewire input with a dct-6200 receiver  
reliably?


/me raises hand.

I just got mine working a few days ago and when it's working, it's  
great. However, more often than not, recordings come up short or  
the channel doesn't change. It hasn't made it through an hour long  
recording yet without the backend saying:


Firewire: No Input in 15 seconds [P:0 N:1] (select)

Then the recording stops. If anyone has any experience with this,  
I'd appreciate a pointer to the component that may be giving me  
problems. Is it the receiver, mythtv, linux, or my cheap firewire  
card?


My money would be on the firewire card. Your symptoms sound similar  
to those I saw with the onboard firewire on one of my systems. A  
different FireWire card (WD one bundled with a drive that I got ages  
ago) and the FW port on my Audigy sound cards all work great though  
(currently using the Audigy's port in production).


--
Jarod Wilson
[EMAIL PROTECTED]




PGP.sig
Description: This is a digitally signed message part
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Curtis Stanford
Great! Good to know someone is having success with this. Thanks for  
the response. That was my guess too.


Do you happen to know what firewire chipset the good cards use? I'd  
like to buy one that works. What does 'lspci' say about your firewire  
card?


On Oct 12, 2005, at 12:32 AM, Jarod Wilson wrote:


On Oct 11, 2005, at 20:23, Curtis Stanford wrote:


Is anyone seriously using firewire input with a dct-6200 receiver  
reliably?




/me raises hand.


I just got mine working a few days ago and when it's working, it's  
great. However, more often than not, recordings come up short or  
the channel doesn't change. It hasn't made it through an hour long  
recording yet without the backend saying:


Firewire: No Input in 15 seconds [P:0 N:1] (select)

Then the recording stops. If anyone has any experience with this,  
I'd appreciate a pointer to the component that may be giving me  
problems. Is it the receiver, mythtv, linux, or my cheap firewire  
card?




My money would be on the firewire card. Your symptoms sound similar  
to those I saw with the onboard firewire on one of my systems. A  
different FireWire card (WD one bundled with a drive that I got  
ages ago) and the FW port on my Audigy sound cards all work great  
though (currently using the Audigy's port in production).


--
Jarod Wilson
[EMAIL PROTECTED]


___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Big Wave Dave
On 10/11/05, Jarod Wilson [EMAIL PROTECTED] wrote:
On Oct 11, 2005, at 20:23, Curtis Stanford wrote: Is anyone seriously using firewire input with a dct-6200 receiver reliably?/me raises hand. I just got mine working a few days ago and when it's working, it's
 great. However, more often than not, recordings come up short or the channel doesn't change. It hasn't made it through an hour long recording yet without the backend saying: Firewire: No Input in 15 seconds [P:0 N:1] (select)
 Then the recording stops. If anyone has any experience with this, I'd appreciate a pointer to the component that may be giving me problems. Is it the receiver, mythtv, linux, or my cheap firewire
 card?My money would be on the firewire card. Your symptoms sound similarto those I saw with the onboard firewire on one of my systems. Adifferent FireWire card (WD one bundled with a drive that I got ages
ago) and the FW port on my Audigy sound cards all work great though(currently using the Audigy's port in production).--Jarod Wilson[EMAIL PROTECTED]

Was this using Myth from src?... or running the lastest RPMs posted on ATrpms?

I'm running the latest stable (non-bleeding) RPMs, and have the same problems as Curtis. 

My FireWire card:
Kouwell Model KW-1582V - (aka BTC 1394 PCI Card)
http://www.kouwell.com.tw/pr-m3.htm#1582v

If I recall correctly, it was listed in linux1394.org compatibility list at the time I bought it.


Thanks,
Dave

--Are Your Friends Lemmings? -- http://www.lemmingshirts.com
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Big Wave Dave
Was this using Myth from src?... or running the lastest RPMs posted on ATrpms?


I'm running the latest stable (non-bleeding) RPMs, and have the same problems as Curtis. 

My FireWire card:
Kouwell Model KW-1582V - (aka BTC 1394 PCI Card)

http://www.kouwell.com.tw/pr-m3.htm#1582v

If I recall correctly, it was listed in linux1394.org compatibility list at the time I bought it.


Thanks,
Dave
Since it will likely be asked:
[EMAIL PROTECTED] mythtv]# rpm -qa | grep myth
mythweb-0.18-67.at
mythbrowser-0.18.1-112.rhfc3.at
mythtv-theme-purplegalaxy-0.20031214-3.at
myththemes-0.18-104.at
mythtv-0.18.1-113.rhfc3.at
mythweather-0.18.1-112.rhfc3.at
mythtv-theme-MythCenter-0.17-1.at
mythtv-theme-photo-4-6.at
mythtv-suite-0.18.1-55.at
mythtv-themes-0.18.1-113.rhfc3.at
mythtv-backend-0.18.1-113.rhfc3.at
mythtv-setup-0.18.1-113.rhfc3.at
mythgame-0.18.1-112.rhfc3.at
mythtv-theme-isthmus-0.20040804-1.at
mythtv-theme-visor-0.16.2-5.at
mythmusic-0.18.1-112.rhfc3.at
mythnews-0.18.1-112.rhfc3.at
mythmkmovie-1.1.4-4.rhfc3.at
mythtv-theme-MediaCenter-0.17-4.at
mythtv-theme-abstract-0.20040910-2.at
mythtv-frontend-0.18.1-113.rhfc3.at
mythphone-0.18.1-112.rhfc3.at
mythplugins-0.18.1-112.rhfc3.at
mythtv-theme-sleek-0.35-2.at
libmyth-0.18.1-113.rhfc3.at
mythvideo-0.18.1-112.rhfc3.at
mythgallery-0.18.1-112.rhfc3.at
mythdvd-0.18.1-112.rhfc3.at

Dave

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Todd Greene




For what its worth, I use the DCT-6200 and Firewire reliably. However,
I can't give you my system specifics, since my root partition of my HD
crashed yesterday, and I can't boot the system. However, it took a
while to get it to work right, and each system reboot (which thankfully
wasn't often) required a manual process. I was using the firewire port
built-in to the Foxconn motherboard.

(1) Run plugreport: . Each time I rebooted, the DCT would show up
either in node 0 or node 1 (often changing per reboot). So, for each
reboot, I would have to re-run mythtvsetup and change the DCT-6200 node
if it had changed. There seemed to be no rhyme or reason as to why it
keeps changing nodes on reboots.

(2) Get test-mpeg2 to work: On each reboot, I would need to run
"test-mpeg2 -r [NODE#]" mutiple times (This step is KEY!!) until I get
some output. You'll know when you get output, its basically a stream
of binary junk to stdout. If you don't see output after 1 second,
press ctrl-c and try again. With 10 tries, you'll get it to work.

(3) Now start mythbackend, and it should work "reliably" until the next
reboot.

Hope this is helpful. Once I rebuilt my machine with a new HD, I'll be
happy to answer specific config questions...

-- Todd




Big Wave Dave wrote:

  
  

Was this using Myth from src?... or running the lastest RPMs
posted on ATrpms?


I'm running the latest "stable" (non-bleeding) RPMs, and have the same
problems as Curtis. 

My FireWire card:
Kouwell Model
KW-1582V - (aka BTC 1394 PCI Card)
http://www.kouwell.com.tw/pr-m3.htm#1582v

If I recall correctly, it was listed in linux1394.org
compatibility list at the time I bought it.


Thanks,
Dave

  
  
Since it will likely be asked:
[EMAIL PROTECTED] mythtv]# rpm -qa | grep myth
  mythweb-0.18-67.at
  mythbrowser-0.18.1-112.rhfc3.at
  mythtv-theme-purplegalaxy-0.20031214-3.at
  myththemes-0.18-104.at
  mythtv-0.18.1-113.rhfc3.at
  mythweather-0.18.1-112.rhfc3.at
  mythtv-theme-MythCenter-0.17-1.at
  mythtv-theme-photo-4-6.at
  mythtv-suite-0.18.1-55.at
  mythtv-themes-0.18.1-113.rhfc3.at
  mythtv-backend-0.18.1-113.rhfc3.at
  mythtv-setup-0.18.1-113.rhfc3.at
  mythgame-0.18.1-112.rhfc3.at
  mythtv-theme-isthmus-0.20040804-1.at
  mythtv-theme-visor-0.16.2-5.at
  mythmusic-0.18.1-112.rhfc3.at
  mythnews-0.18.1-112.rhfc3.at
  mythmkmovie-1.1.4-4.rhfc3.at
  mythtv-theme-MediaCenter-0.17-4.at
  mythtv-theme-abstract-0.20040910-2.at
  mythtv-frontend-0.18.1-113.rhfc3.at
  mythphone-0.18.1-112.rhfc3.at
  mythplugins-0.18.1-112.rhfc3.at
  mythtv-theme-sleek-0.35-2.at
  libmyth-0.18.1-113.rhfc3.at
  mythvideo-0.18.1-112.rhfc3.at
  mythgallery-0.18.1-112.rhfc3.at
  mythdvd-0.18.1-112.rhfc3.at
  
Dave

  
  
  

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
  



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Big Wave Dave
Big Wave Dave wrote:

  
  

Was this using Myth from src?... or running the lastest RPMs
posted on ATrpms?


I'm running the latest stable (non-bleeding) RPMs, and have the same
problems as Curtis. 

My FireWire card:
Kouwell Model
KW-1582V - (aka BTC 1394 PCI Card)
http://www.kouwell.com.tw/pr-m3.htm#1582v

If I recall correctly, it was listed in linux1394.org
compatibility list at the time I bought it.


Thanks,
Dave

  
  
Since it will likely be asked:
[EMAIL PROTECTED] mythtv]# rpm -qa | grep myth
  mythweb-0.18-67.at
  mythbrowser-0.18.1-112.rhfc3.at
  mythtv-theme-purplegalaxy-0.20031214-3.at
  myththemes-0.18-104.at
  mythtv-0.18.1-113.rhfc3.at
  mythweather-0.18.1-112.rhfc3.at
  mythtv-theme-MythCenter-0.17-1.at
  mythtv-theme-photo-4-6.at
  mythtv-suite-0.18.1-55.at
  mythtv-themes-0.18.1-113.rhfc3.at
  mythtv-backend-0.18.1-113.rhfc3.at
  mythtv-setup-0.18.1-113.rhfc3.at
  mythgame-0.18.1-112.rhfc3.at
  mythtv-theme-isthmus-0.20040804-1.at
  mythtv-theme-visor-0.16.2-5.at
  mythmusic-0.18.1-112.rhfc3.at
  mythnews-0.18.1-112.rhfc3.at
  mythmkmovie-1.1.4-4.rhfc3.at
  mythtv-theme-MediaCenter-0.17-4.at
  mythtv-theme-abstract-0.20040910-2.at
  mythtv-frontend-0.18.1-113.rhfc3.at
  mythphone-0.18.1-112.rhfc3.at
  mythplugins-0.18.1-112.rhfc3.at
  mythtv-theme-sleek-0.35-2.at
  libmyth-0.18.1-113.rhfc3.at
  mythvideo-0.18.1-112.rhfc3.at
  mythgallery-0.18.1-112.rhfc3.at
  mythdvd-0.18.1-112.rhfc3.at
  
DaveI should clarify that mine DOES work about 60-70% of the time. I would obviously like to improve that though. :-)

Dave

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Alex Brekken
As another data point, I'm running 18.1 on FC3 and have been using
FireWire on a DCT-6200 for a few months now. I've got a Belkin
FireWire card. The main issue I have is the same that I've seen
many other Firewire users complain about, which is often times when
starting a recording (or LiveTV) it doesn't actually capture
anything. So you get either a zero-size file, or it just times
out. If you keep trying it will work, but I would say that
roughly 40% of the time it doesn't. Once it DOES start capturing
it's great, but it's nowhere near reliable enough for me to use it as
anything more than as an experimental thing. Channel-changing,
however, does work flawlessly all the time. On 10/12/05, Big Wave Dave [EMAIL PROTECTED] wrote:

Big Wave Dave wrote:

  
  

Was this using Myth from src?... or running the lastest RPMs
posted on ATrpms?


I'm running the latest stable (non-bleeding) RPMs, and have the same
problems as Curtis. 

My FireWire card:
Kouwell Model
KW-1582V - (aka BTC 1394 PCI Card)
http://www.kouwell.com.tw/pr-m3.htm#1582v

If I recall correctly, it was listed in linux1394.org
compatibility list at the time I bought it.


Thanks,
Dave

  
  
Since it will likely be asked:
[EMAIL PROTECTED] mythtv]# rpm -qa | grep myth
  mythweb-0.18-67.at
  mythbrowser-0.18.1-112.rhfc3.at
  mythtv-theme-purplegalaxy-0.20031214-3.at
  myththemes-0.18-104.at
  mythtv-0.18.1-113.rhfc3.at
  mythweather-0.18.1-112.rhfc3.at
  mythtv-theme-MythCenter-0.17-1.at
  mythtv-theme-photo-4-6.at
  mythtv-suite-0.18.1-55.at
  mythtv-themes-0.18.1-113.rhfc3.at
  mythtv-backend-0.18.1-113.rhfc3.at
  mythtv-setup-0.18.1-113.rhfc3.at
  mythgame-0.18.1-112.rhfc3.at
  mythtv-theme-isthmus-0.20040804-1.at
  mythtv-theme-visor-0.16.2-5.at
  mythmusic-0.18.1-112.rhfc3.at
  mythnews-0.18.1-112.rhfc3.at
  mythmkmovie-1.1.4-4.rhfc3.at
  mythtv-theme-MediaCenter-0.17-4.at
  mythtv-theme-abstract-0.20040910-2.at
  mythtv-frontend-0.18.1-113.rhfc3.at
  mythphone-0.18.1-112.rhfc3.at
  mythplugins-0.18.1-112.rhfc3.at
  mythtv-theme-sleek-0.35-2.at
  libmyth-0.18.1-113.rhfc3.at
  mythvideo-0.18.1-112.rhfc3.at
  mythgallery-0.18.1-112.rhfc3.at
  mythdvd-0.18.1-112.rhfc3.at
  
DaveI should clarify that mine DOES work about 60-70% of the time. I would obviously like to improve that though. :-)

Dave


___mythtv-users mailing listmythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Curtis Stanford


On Oct 12, 2005, at 2:35 PM, Todd Greene wrote:

For what its worth, I use the DCT-6200 and Firewire reliably.   
However, I can't give you my system specifics, since my root  
partition of my HD crashed yesterday, and I can't boot the system.   
However, it took a while to get it to work right, and each system  
reboot (which thankfully wasn't often) required a manual process.   
I was using the firewire port built-in to the Foxconn motherboard.


(1) Run plugreport: .  Each time I rebooted, the DCT would show up  
either in node 0 or node 1 (often changing per reboot).  So, for  
each reboot, I would have to re-run mythtvsetup and change the  
DCT-6200 node if it had changed.  There seemed to be no rhyme or  
reason as to why it keeps changing nodes on reboots.


(2) Get test-mpeg2 to work:  On each reboot, I would need to run  
test-mpeg2 -r [NODE#]  mutiple times (This step is KEY!!) until I  
get some output.  You'll know when you get output, its basically a  
stream of binary junk to stdout.  If you don't see output after 1  
second, press ctrl-c and try again.  With 10 tries, you'll get it  
to work.


(3) Now start mythbackend, and it should work reliably until the  
next reboot.


Hope this is helpful.  Once I rebuilt my machine with a new HD,  
I'll be happy to answer specific config questions...


-- Todd


Yes, I do all of these things as well. However, it doesn't work  
reliably for me even after these steps. Thanks Todd


Curtis

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Donald Oakes

Curtis Stanford wrote:



On Oct 12, 2005, at 2:35 PM, Todd Greene wrote:

For what its worth, I use the DCT-6200 and Firewire reliably.   
However, I can't give you my system specifics, since my root  
partition of my HD crashed yesterday, and I can't boot the system.   
However, it took a while to get it to work right, and each system  
reboot (which thankfully wasn't often) required a manual process.   I 
was using the firewire port built-in to the Foxconn motherboard.


(1) Run plugreport: .  Each time I rebooted, the DCT would show up  
either in node 0 or node 1 (often changing per reboot).  So, for  
each reboot, I would have to re-run mythtvsetup and change the  
DCT-6200 node if it had changed.  There seemed to be no rhyme or  
reason as to why it keeps changing nodes on reboots.


(2) Get test-mpeg2 to work:  On each reboot, I would need to run  
test-mpeg2 -r [NODE#]  mutiple times (This step is KEY!!) until I  
get some output.  You'll know when you get output, its basically a  
stream of binary junk to stdout.  If you don't see output after 1  
second, press ctrl-c and try again.  With 10 tries, you'll get it  to 
work.


(3) Now start mythbackend, and it should work reliably until the  
next reboot.


Hope this is helpful.  Once I rebuilt my machine with a new HD,  I'll 
be happy to answer specific config questions...


-- Todd



Yes, I do all of these things as well. However, it doesn't work  
reliably for me even after these steps. Thanks Todd


Curtis



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
 

I have the same difficulty as you, Curtis.  I've even written a program 
to automatically run test-mpeg2 until success each time the channel is 
changed.  Recording is still about 50% reliable via firewire.


- Donald
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Firewire and DCT-6200

2005-10-12 Thread Curtis Stanford


On Oct 12, 2005, at 11:04 PM, Donald Oakes wrote:


Curtis Stanford wrote:




On Oct 12, 2005, at 2:35 PM, Todd Greene wrote:


For what its worth, I use the DCT-6200 and Firewire reliably.
However, I can't give you my system specifics, since my root   
partition of my HD crashed yesterday, and I can't boot the  
system.   However, it took a while to get it to work right, and  
each system  reboot (which thankfully wasn't often) required a  
manual process.   I was using the firewire port built-in to the  
Foxconn motherboard.


(1) Run plugreport: .  Each time I rebooted, the DCT would show  
up  either in node 0 or node 1 (often changing per reboot).  So,  
for  each reboot, I would have to re-run mythtvsetup and change  
the  DCT-6200 node if it had changed.  There seemed to be no  
rhyme or  reason as to why it keeps changing nodes on reboots.


(2) Get test-mpeg2 to work:  On each reboot, I would need to run   
test-mpeg2 -r [NODE#]  mutiple times (This step is KEY!!) until  
I  get some output.  You'll know when you get output, its  
basically a  stream of binary junk to stdout.  If you don't see  
output after 1  second, press ctrl-c and try again.  With 10  
tries, you'll get it  to work.


(3) Now start mythbackend, and it should work reliably until  
the  next reboot.


Hope this is helpful.  Once I rebuilt my machine with a new HD,   
I'll be happy to answer specific config questions...


-- Todd




Yes, I do all of these things as well. However, it doesn't work   
reliably for me even after these steps. Thanks Todd


Curtis

- 
---


___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


I have the same difficulty as you, Curtis.  I've even written a  
program to automatically run test-mpeg2 until success each time the  
channel is changed.  Recording is still about 50% reliable via  
firewire.


- Donald


So what's the difference between us and the people who seem to have  
it working 100% ? I'm still thinking it may be the card or perhaps  
the linux driver. I'm hoping anyone who is having success with this  
mail in with their configurations.


Curtis

___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


[mythtv-users] Firewire and DCT-6200

2005-10-11 Thread Curtis Stanford
Is anyone seriously using firewire input with a dct-6200 receiver  
reliably? I just got mine working a few days ago and when it's  
working, it's great. However, more often than not, recordings come up  
short or the channel doesn't change. It hasn't made it through an  
hour long recording yet without the backend saying:


Firewire: No Input in 15 seconds [P:0 N:1] (select)

Then the recording stops. If anyone has any experience with this, I'd  
appreciate a pointer to the component that may be giving me problems.  
Is it the receiver, mythtv, linux, or my cheap firewire card?


An exhaustive net search brought back similar problems and suggested  
using broadcast instead of point-to-point, which I did. No improvement.


Thanks

Curtis

Mythtv: latest SVN version
Linux: 2.6.13
Motorola DCT-6200
Firewire card with VIA chipset ($20 card)


___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users