Re: [mythtv] [mythtv-commits] Ticket #1079: frame corruption in preview playbackbox

2006-01-26 Thread Jim Westfall
both worked great on my linuxppc. I wasnt able to see much difference speed/cpu wise. jim MythTV [EMAIL PROTECTED] wrote [01.26.06]: #1079: frame corruption in preview playbackbox +--- Reporter: [EMAIL PROTECTED] |

Re: [mythtv] SVN 8625 Firewire capture glitching while test-mpeg2 doesn't

2006-01-23 Thread Jim Westfall
Steve Adeff [EMAIL PROTECTED] wrote [01.23.06]: here's the log output from a crash, it occured while in edit mode: 2006-01-21 10:13:14.099 59520 bytes free on soundcard 2006-01-21 10:13:14.099 WriteAudio: Preparing 6144 bytes (1536 frames) 2006-01-21 10:13:14.107 54912 bytes free on

Re: [mythtv] [mythtv-commits] Ticket #1071: completely wrong colors in preview window of Watch Recordings

2006-01-19 Thread Jim Westfall
so the C version of the yuv2rgb is broken? I get the same behavior on my linuxppc box. jim MythTV [EMAIL PROTECTED] wrote [01.19.06]: #1071: completely wrong colors in preview window of Watch Recordings -+-- Reporter:

Re: [mythtv] Firewire troubles WAS Re: add to Trac?

2006-01-17 Thread Jim Westfall
Steve Adeff [EMAIL PROTECTED] wrote [01.17.06]: scratch that, channel changing just doesn't work. On the plus side, telling Myth to use broadcast has allowed me to create any 0byte recordings. Sometimes the channel is wrong, but it always gets a stream. I posted to the user list the

Re: [mythtv] Firewire troubles WAS Re: add to Trac?

2006-01-17 Thread Jim Westfall
Steve Adeff [EMAIL PROTECTED] wrote [01.17.06]: I was using this before I switched to capturing via firewire and had the box connected to my PVR150(which is now connected to a regular digital cablebox). I can say my success rate was much higher, ~95%, I had to play with the plugctl to set

Re: [mythtv] add to Trac?

2006-01-12 Thread Jim Westfall
Steve Adeff [EMAIL PROTECTED] wrote [01.12.06]: I'm getting A LOT of mpeg pixelation on the HD channels, which I wasn't getting last night that is not showing on the Component output. I have already had 1 channel mischange. I'll let you know when I encounter when the box stops

Re: [mythtv] add to Trac?

2006-01-11 Thread Jim Westfall
Can you provide more info on what problem you are having, your mythtv firewire config settings, and plugctl output. thanks jim Steve Adeff [EMAIL PROTECTED] wrote [01.11.06]: I want to add the following as a ticket to Trac, but since theres no patch attached, its more of a bug report with a

Re: [mythtv] add to Trac?

2006-01-11 Thread Jim Westfall
Steve Adeff [EMAIL PROTECTED] wrote [01.11.06]: Jim, read the email I linked to. On top of that, its not just me, its just about everyone using the DCT64xx machines that I've talked to. What happens is the pc can't receive a stream from the cablebox over the firewire and ends up creating

Re: [mythtv] Refactored OSX backend firewire patch

2006-01-11 Thread Jim Westfall
That fixed it. I was able to get a test backend setup on my mactop and verified it could change channel and record without any issue. jim David Abrahams [EMAIL PROTECTED] wrote [01.11.06]: David Abrahams [EMAIL PROTECTED] writes: Argh, another missing file! Please put the enclosed in the

Re: [mythtv] Refactored OSX backend firewire patch

2006-01-11 Thread Jim Westfall
DCT-6200 on my p2p one. I will try my other DCT-6200 tonight which only works right with broadcast in linux. jim David Abrahams [EMAIL PROTECTED] wrote [01.11.06]: Jim Westfall [EMAIL PROTECTED] writes: That fixed it. I was able to get a test backend setup on my mactop and verified

Re: [mythtv] add to Trac?

2006-01-11 Thread Jim Westfall
Steve Adeff [EMAIL PROTECTED] wrote [01.11.06]: the problem is that you can't control how the dct62xx comes up, some will allow for broadcast connection, some will only work with p2p. I have it setup as a firewire capture card, Cable Box Model DCT-6200, Connection Type Point to Point,

Re: [mythtv] Refactored OSX backend firewire patch

2006-01-10 Thread Jim Westfall
David Abrahams [EMAIL PROTECTED] wrote [01.10.06]: And here is the complete patch with Jim's fixes included. Thanks again, Jim! I tried building the OSX part of the patch last night on my mactop but it looks like you forgot to include selectavcdevice.[h|cpp]? $ grep selectavc

Re: [mythtv] Refactored OSX backend firewire patch

2006-01-09 Thread Jim Westfall
David Abrahams [EMAIL PROTECTED] wrote [01.09.06]: I've tried to address Isaac's code structure concerns by factoring out the common parts of firewire support for MacOS and linux. Unfortunately, not having a Linux MythTV installation here it surely means I've broken something. I'd be

Re: [mythtv] Refactored OSX backend firewire patch

2006-01-09 Thread Jim Westfall
Jim Westfall [EMAIL PROTECTED] wrote [01.09.06]: David Abrahams [EMAIL PROTECTED] wrote [01.09.06]: I've tried to address Isaac's code structure concerns by factoring out the common parts of firewire support for MacOS and linux. Unfortunately, not having a Linux MythTV installation here

Re: [mythtv] commflag debugging

2006-01-02 Thread Jim Westfall
Daniel Chassot [EMAIL PROTECTED] wrote [01.02.06]: When editing the show in mythtv, it is not (everywhere) seekable, the displayed size of the movie is wrong. Yeah as part of my testing I tried to --rebuild the postitionMap to see if it would fix it being short 15K frames, but it just made

Re: [mythtv] commflag debugging

2006-01-02 Thread Jim Westfall
to a frame #. jim Daniel Chassot [EMAIL PROTECTED] wrote [01.02.06]: On 1/2/06, Jim Westfall [EMAIL PROTECTED] wrote: This fixed the map for me and made the commflag breaks match up right when playing. Happy that it helps. Now the question is how to fix this properly? Any idea

Re: [mythtv] commflag debugging

2006-01-01 Thread Jim Westfall
Chris Pinkham [EMAIL PROTECTED] wrote [01.01.06]: I would like to look into some commflag debugging. I see there are already bits in place to display/dump frames, but the support functions for them dont resolve. I suspect they are defined in commercial_debug.h, which is commented out

[mythtv] commflag debugging

2005-12-31 Thread Jim Westfall
Hi I would like to look into some commflag debugging. I see there are already bits in place to display/dump frames, but the support functions for them dont resolve. I suspect they are defined in commercial_debug.h, which is commented out in ClassicCommDetector.cpp but doesnt exist within

Re: [mythtv] Debugging Unreliable DCT-6200 Recording

2005-09-23 Thread Jim Westfall
it solves it for more than just me. Josh. On Sep 22, 2005, at 8:16 PM, Jim Westfall wrote: Hi Josh I have this issue as well on one of my dct-6200's. I havent had time to see what the exact cause it, but the following work around gets it working 100% for me. make sure your firewire

Re: [mythtv] Debugging Unreliable DCT-6200 Recording

2005-09-22 Thread Jim Westfall
Hi Josh I have this issue as well on one of my dct-6200's. I havent had time to see what the exact cause it, but the following work around gets it working 100% for me. make sure your firewire connection type is set to broadcast in mythsetup. run 'test-mpeg2 -r 1 test.ts' over and over until

Re: [mythtv] ivtv support classes and deviceIsMpegFile

2005-06-16 Thread Jim Westfall
I would check out the firewire recorder/channel classes, they are pretty basic. jim Unit3 [EMAIL PROTECTED] wrote [06.16.05]: On Thu, 2005-06-16 at 17:13 -0400, Chris Pinkham wrote: deviceIsMpegFile was put in primarily to aid in development so that I could work on mythbackend from my

Re: [mythtv] 6200ch vendor codes

2005-06-13 Thread Jim Westfall
Hi Brian I didnt include the bits to checks the vendor/model id's in the internal channel changing code. So long as you set the model type in setup to DCT-6200 it will attempt to send the commands. You will need to update 6200ch.c to add your vendor/model ids for it to work. jim Brian C.

[mythtv] [patch] firewire mpeg2ts sync bugfix

2005-05-03 Thread Jim Westfall
patch will ignore any mpeg2ts packet that doesnt have a valid sync byte. should fix an issue reported on the users mailing list about the first couple packets on a new recording being all zeros. jim Index: libs/libmythtv/firewirerecorder.cpp

Re: [mythtv] [patch] firewire internal channel change for dct-6200

2005-05-02 Thread Jim Westfall
could I get this applied. thanks jim Jim Westfall [EMAIL PROTECTED] wrote [04.18.05]: Hi patch adds support for internal channel changing via firewire for DCT-6200 and friends. This adds a new library requirement of libavc1394 for firewire. To enable you will need to set the firewire

[mythtv] [patch] firewire internal channel change for dct-6200

2005-04-19 Thread Jim Westfall
Hi patch adds support for internal channel changing via firewire for DCT-6200 and friends. This adds a new library requirement of libavc1394 for firewire. To enable you will need to set the firewire model in setup to DCT-6200 and unset the external channel changer option. jim Index:

Re: [mythtv] [patch] firewire broadcast connection

2005-03-11 Thread Jim Westfall
what set top box do you have? jim Jeremy Muhlich [EMAIL PROTECTED] wrote [03.11.05]: I'm not sure it's mythtv's fault, as the test_mpeg tool from the linux1394/iec61883 package exhibits the same problems. (I think it's test_mpeg; I don't have access to my myth box right now and the

Re: [mythtv] [patch] firewire broadcast connection

2005-03-11 Thread Jim Westfall
From what I have seen and delt with, 6200s that come up as node 1 on firewire work best using a broadcast connections, and node 2's like p2p connection. If you have a node 1, you should try doing the following and see if the last command is consistent in dumping mpeg2 from the 6200. - run

[mythtv] crash mythfrontend (OSDTypeEditSlider::Reinit)

2005-03-05 Thread Jim Westfall
The crash is in frame #10 (gdb) f 10 #10 0xb7c75d1c in OSDTypeEditSlider::Reinit(float, float, float, float) ( this=0xb41faad0, wchange=inf, hchange=inf, wmult=3, hmult=2.25) at osdtypes.cpp:1223 1223m_drawMap = new unsigned char[m_drawwidth + 1]; (gdb) print m_drawwidth $2 =

Re: [mythtv] crash mythfrontend (OSDTypeEditSlider::Reinit)

2005-03-05 Thread Jim Westfall
Attached is a patch that fixes the problem. It holds off creating the osd object until width/height are non-zero and fps/aspect are non-nan. jim Jim Westfall [EMAIL PROTECTED] wrote [03.05.05]: The crash is in frame #10 (gdb) f 10 #10 0xb7c75d1c in OSDTypeEditSlider::Reinit(float, float

[mythtv] mythcommflag crash (VideoOutputNull::DeleteNullBuffers)

2005-02-27 Thread Jim Westfall
Hi crash I have been seeing. Its also the same location of the crash I get when attempting to generate a png file for mythweb. (gdb) set args --force -f 1105_2005022622_2005022623.nuv (gdb) run Starting program: /usr/local/bin/mythcommflag --force -f

[mythtv] mythfilldatabase crash (~MDBManager)

2005-02-24 Thread Jim Westfall
mythfilldatabase is crashing when its calling the ~MDBManager destructor. here is a backtrace. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 23953)] 0x0f574ab0 in ~MDBManager (this=0x10061e50) at mythdbcon.cpp:111 111 delete m_sem; (gdb) thread

Re: [mythtv] backend dying while mythweb is creating previews for recorded programs

2005-02-23 Thread Jim Westfall
I found some additional information on my test x86 backend box. It appears that connectionClosed() signal is not always getting triggered when a client disconnects. There ends up being dead sockets in playbackList and fileTransferList. attached is a patch that adds additional logging to the

Re: [mythtv] backend dying while mythweb is creating previews for recorded programs

2005-02-22 Thread Jim Westfall
I also ran into this yesterday. It segfaults everytime on my linuxppc backend. I was able to narrow down where its happening, but havent had time to figure out why. In the destructor of VideoOutputNull it calls Exit(), which calls VideoOutputNull::DeleteNullBuffers(). The segfault for me

[mythtv] [patch] mythbackend MainServer::getFreeSpace

2005-02-16 Thread Jim Westfall
These are the current calculations for getting totalspace and usedspace, which get reported to the frontend. totalspace = (statbuf.f_blocks - (statbuf.f_bfree - statbuf.f_bavail)) / (1024*1024/statbuf.f_bsize); usedspace = (statbuf.f_blocks - statbuf.f_bavail) /

[mythtv] [patch] firewire broadcast connection

2005-02-15 Thread Jim Westfall
Hi With the help of ddennedy over at linux1394 it was determined that not all STB's are stable or dont even work when making a peer to peer connection. This patch adds a new option that lets you pick the connection type to make with the STB, p2p or broadcast. Its been tested with a couple

[mythtv] frontend not handling audio sample rate changes

2005-02-12 Thread Jim Westfall
Hi I finally got a frontend box fast enough to handle HD mpeg2 via firewire and have notice that the frontend isnt handling audio sample rate changes. When I switch from HD - SD the sample rate usually goes from 48000Hz to 32000Hz on the mpeg stream. When this change happens its detected by

Re: [mythtv] Firewire: How to test input?

2005-02-09 Thread Jim Westfall
[02.09.05]: On Tue, 8 Feb 2005, Jim Westfall wrote: are you able to capture on channel 0 on your windows box? No; just channel 1. I'm manually tuning the box to ch1 when I run test-mpeg2; I did think it was kind of weird that it said it was tuning to channel 0. Am I doing something wrong? (Well

Re: [mythtv] Firewire: How to test input?

2005-02-09 Thread Jim Westfall
Nate Carlson [EMAIL PROTECTED] wrote [02.09.05]: On Wed, 9 Feb 2005, Jim Westfall wrote: sorry I think we are talking about different meanings of channel. There is the channel on your tv/cablebox and the communication channel in firewire. The firewire utils/libs know nothing about which

Re: [mythtv] Firewire: How to test input?

2005-02-08 Thread Jim Westfall
I am not a firewire expert, but I have always been under the impression that node 0 is always your firewire card. I would plug in your 3250HD box then run gscanbus to figure out what node its on. also test-mpeg2 dumps the mpeg2 to stdout, so make sure to redirect to a file when you run it.

Re: [mythtv] Firewire: How to test input?

2005-02-08 Thread Jim Westfall
are you able to capture on channel 0 on your windows box? jim Nate Carlson [EMAIL PROTECTED] wrote [02.08.05]: On Tue, 8 Feb 2005, Jim Westfall wrote: k I am not a firewire expert, but I have always been under the impression that node 0 is always your firewire card. I would plug in your

Re: [mythtv] New ieee1394 code and DCT-6200

2005-02-07 Thread Jim Westfall
and libiec61883 as well as the latest version of libavc1394. I'm assuming that if I have to upgrade the firewire drivers that its going to take a kernel rebuild? -Todd -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Westfall Sent: Monday

Re: [mythtv] [patch] linuxppc

2005-02-04 Thread Jim Westfall
Looks good. Builds ok and it sets the QMAKE_CXXFLAGS_RELEASE right. thanks jim Jeremiah Morris [EMAIL PROTECTED] wrote [02.04.05]: On Feb 4, 2005, at 12:50 AM, Jim Westfall wrote: small patch that makes it possible to compile mythtv on linuxppc. Thanks, I've committed this with one

[mythtv] [patch] linuxppc

2005-02-03 Thread Jim Westfall
hi small patch that makes it possible to compile mythtv on linuxppc. jim diff -ur mythtv.orig/filters/linearblend/filter_linearblend.c mythtv/filters/linearblend/filter_linearblend.c --- mythtv.orig/filters/linearblend/filter_linearblend.c2005-01-21 11:17:29.0 -0800 +++

Re: [mythtv] firewire mpeg2ts input

2005-02-02 Thread Jim Westfall
Can you give the output of gscanbus and 6200ch? Every DCT-6200 device I have seen thus far has been node 2. jim DavidB [EMAIL PROTECTED] wrote [02.02.05]: Jim, First off, Great Work! I am trying to get the firewire working and have not had any success. Here is what I have done to this

Re: [mythtv] firewire mpeg2ts input

2005-02-02 Thread Jim Westfall
looks ok. can you try running the following for 10-20 seconds and see if it puts any data into test.ts. The util is part of libiec61183. test-mpeg2 -r 1 test.ts thanks jim DavidB [EMAIL PROTECTED] wrote [02.02.05]: -Original Message- From: Jim Westfall [mailto:[EMAIL

[mythtv] [patch] firewire mpeg2ts input

2005-02-01 Thread Jim Westfall
, but most everything (livetv/recording/ff/etc) else should be working. thanks Jim Westfall diff -urN --exclude='config.*' --exclude='Makefile*' --exclude='*.o' --exclude='*.so' --exclude='moc*' mythtv.orig/libs/libmythtv/dbcheck.cpp mythtv/libs/libmythtv/dbcheck.cpp --- mythtv.orig/libs

Re: [mythtv] [patch] firewire mpeg2ts input

2005-02-01 Thread Jim Westfall
Yeah the thought crossed my mind. Getting the mpeg2 to the tv wouldnt be that hard, but dealing with the osd/ui would be a hassle. It sounds like alot of work for something I couldnt use. My hdtv doesnt have 1394 input. If you want to play with sending mpeg data to your tv, there is a util