Re: [mythtv-users] 0.17 kernel 2.6.11 problem

[Nick]

On 4/13/05, Troy Roberts <[EMAIL PROTECTED]> wrote:
> I have a single backend driving 2 frontends - all debian based.  I
> recently updated them al to the 2.6.11 kernel
> kernel-image-2.6.11-1-686  I now have a significant amount of
> 'stutter' druing playback on both frontends
> 
> Each frontend has a slightly different hardware config (mobo, audio,
> cpu speed) but the same video card (nvidia), intel procs, etc.
> 
> The backend is capturing everything fine because if I copy the .nuv
> file over to a windows box or to my videos dir they play fine
> (including in mplayer), it is just during myth playback that the
> problem seems to exist.
> 
> I have tried the following:
> 
> - renice the mythfrontend process
> - renice the mythbackend process
> - set use video as timebase
> - set agressive audio buffering
> - monitored my local lan (100Mb FDX) to look for network congestion
> 
> Does anyone have any suggestions as to what may be causing this? Is it
> a myth problem, or a linux kernel problem?
> 
> FWIW, I captured a number of prebuffering messages in the mythfrontend log:
> 
> 2005-04-07 23:36:45.567 WriteAudio: Preparing 4096 bytes (1024 frames)
> 2005-04-07 23:36:45.567 audio waiting for space on soundcard: have 368 need 
> 4096
> 2005-04-07 23:36:45.574 audio waiting for space on soundcard: have 1676 need 
> 409
> 6
> 2005-04-07 23:36:45.581 audio waiting for space on soundcard: have 3020 need 
> 409
> 6
> 2005-04-07 23:36:45.588 Broadcasting free space avail
> 2005-04-07 23:36:45.588 WriteAudio: Preparing 4096 bytes (1024 frames)
> 2005-04-07 23:36:45.588 audio waiting for buffer to fill: have 512 want 4096
> 2005-04-07 23:36:45.588 Broadcasting free space avail

 

> Thanks in advance - any help would be muchly appreciated
> Troy

Are you using the latest ALSA release, or have you manually compiled
ALSA after having installed the new kernel? A number of people have
found that by upgrading to the latest ALSA the pauses have been
solved.

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

Re: [mythtv-users] 0.17, DVB-T & channels ?

[Mika Saari]

Hello,

  Thanks for the answer :) I started to hazzle with SQL databases but
couldn't get the channels to be tuned yet.

> You should be able to edit and update the channels table directly in
> the mythconverg database. 

  Do you mean dvb_channel, dvb_pids & channel tables ? I read from
somewhere that dvb_* aren't used anymore 0.17, is this misunderstanding
from my side ?

  I dvbscanned the channels and e.g. my TV 1 channel is serviceid=17.
But if I put that to channel table, the backend claims that it can not
find some options for it. I added all dvb_pids & dvb_channel info from
0.16 database and options warnings are gone but the channel 17 can not
still be tuned :/ (Verified once more that xine is able to show the
channel 17 / TV 1 here)

> If you run dvbscan and dump the results into a file, you can then use
> the channel settings (or just insert the settings contained in your
> old pre-0.17 db) and the new channels should then be usable.

  I think I did pretty much this (dvb_channel, dvb_pids) not sure if I
am still missing something.

  There are some new attributes in channel table, could one/few of those
new ones cause probably the tuning problem ?

  Thank you so much once again,
-Mika

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

Re: [mythtv-users] 0.17, DVB-T & channels ?

[Nick]

On Tue, 29 Mar 2005 04:39:41 +0300, Mika Saari <[EMAIL PROTECTED]> wrote:
> Hi,
> 
>   Done this so far: Dropped the mythconverg database, compiled the 0.17
> (CVS) and ran the myth-setup. In the myth-setup I managed to run the
> Full Search for channels (didn't find all of the channels but few of
> them from one of the channel chunks). To verify the hw & driver
> functionality I tested dvbscan & xine dvb:// combination -> all channels
> were found and watchable.
> 
>   Channels the 0.17 myth-setup found are fully watchable, but the ones
> it didn't find I can not add by hand (not with myth-setup). Any tips how
> I could add those missing channels to 0.17 by hand ?
> 
>   Thank you very much for the information,
> -Mika

Mika,

You should be able to edit and update the channels table directly in
the mythconverg database. I would recommend using a web-based database
frontend (for each of use) such as phpMySQL to edit the database - it
will also let you save and restore the database or individual tables
in case you run into problems.

If you run dvbscan and dump the results into a file, you can then use
the channel settings (or just insert the settings contained in your
old pre-0.17 db) and the new channels should then be usable.

When changes are made to the database manually, remember you should
restart the backend process so that the changes can take effect.

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

Re: [mythtv-users] 0.17, DVB-T & channels ?

[dave]

 I found, after the initial scan, a re-scan of each individual transport
picked up some further channels.  (Option under Channel Setup)

 Alternatively you can direct the output from dvbscan to a file.  Then
insert the various settings (QAM, FEC, etc, etc) into the channel setup
manually.

The channel scan in Myth 0.17 certainly doesn't seem as reliable as
dvbscan, but it is a lot better than 0.16!


> Hi,
>
>   Done this so far: Dropped the mythconverg database, compiled the 0.17
> (CVS) and ran the myth-setup. In the myth-setup I managed to run the
> Full Search for channels (didn't find all of the channels but few of
> them from one of the channel chunks). To verify the hw & driver
> functionality I tested dvbscan & xine dvb:// combination -> all channels
> were found and watchable.
>
>   Channels the 0.17 myth-setup found are fully watchable, but the ones
> it didn't find I can not add by hand (not with myth-setup). Any tips how
> I could add those missing channels to 0.17 by hand ?
>
>
>   Thank you very much for the information,
> -Mika
>
>
> ___
> 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] 0.17 Recordings Keep Switching to Tuner 0

[John Kondis]

In case it helps anyone, after trying several things,
what finally worked was clearing all the card settings
when starting mythtv/setup, setting up the PVR 350
card data again, and resetting the input connection
for my Cable TV source.  Myth now records properly
using the S-Video input and doesn't change the setting
back to the tuner.

It does seem strange, though, that you have to reset
the card settings to change the input source on the
PVR 350.

--- John Kondis <[EMAIL PROTECTED]> wrote:
> Oops my bad.  My myth machine is combined
> frontend/backend, using a Hauppauge PVR 350 for both
> TV in (encoder) and TV out (decoder).  SuSE Linux
> 9.2
> on a Celeron 566.  Using ivtv 0.1.9 rc3.
> 
> Thanks.
> 
> --- John Kondis <[EMAIL PROTECTED]> wrote:
> > MythTV keeps changing the input source to the
> tuner
> > (Tuner 0) every time a scheduled recording starts.
> 
> > The backend is set up to take input from the
> S-Video
> > input.  I've triple-checked that mythtv/setup has
> > the
> > card set to S-video, but the problem persists.
> > 
> > When I reboot and go to live TV everything is
> fine;
> > it
> > shows the video from the S-Video input.  Whenever
> a
> > scheduled recording starts, it switches to tuner 0
> > and
> > I get nothing but snow for my recordings.  Now,
> when
> > I
> > go back to live TV (say, after killing the
> recording
> > or letting it finish), it remains on Tuner 0
> (snow)
> > until I reboot again.
> > 
> > How do I fix this?  This is very annoying as now
> > I've
> > been missing all my scheduled recordings and have
> to
> > reboot frequently.  Any help is appreciated,
> though
> > no
> > one ever seems to have an answer to my questions
> on
> > this mailing list.
> > 
> > Note that I recently changed from using the tuner
> > input to using S-video because the quality is
> better
> > if I avoid the mod/demod to channel 3.
> > > ___
> > 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] 0.17 Recordings Keep Switching to Tuner 0

[John Kondis]

Oops my bad.  My myth machine is combined
frontend/backend, using a Hauppauge PVR 350 for both
TV in (encoder) and TV out (decoder).  SuSE Linux 9.2
on a Celeron 566.  Using ivtv 0.1.9 rc3.

Thanks.

--- John Kondis <[EMAIL PROTECTED]> wrote:
> MythTV keeps changing the input source to the tuner
> (Tuner 0) every time a scheduled recording starts. 
> The backend is set up to take input from the S-Video
> input.  I've triple-checked that mythtv/setup has
> the
> card set to S-video, but the problem persists.
> 
> When I reboot and go to live TV everything is fine;
> it
> shows the video from the S-Video input.  Whenever a
> scheduled recording starts, it switches to tuner 0
> and
> I get nothing but snow for my recordings.  Now, when
> I
> go back to live TV (say, after killing the recording
> or letting it finish), it remains on Tuner 0 (snow)
> until I reboot again.
> 
> How do I fix this?  This is very annoying as now
> I've
> been missing all my scheduled recordings and have to
> reboot frequently.  Any help is appreciated, though
> no
> one ever seems to have an answer to my questions on
> this mailing list.
> 
> Note that I recently changed from using the tuner
> input to using S-video because the quality is better
> if I avoid the mod/demod to channel 3.
> > ___
> 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] 0.17-97 install problem

[Robin Smith]

And indeed it is fixed... thanks Jarod.

On Sun, 6 Mar 2005 09:47:32 -0800, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> On Saturday 05 March 2005 12:02, Robin Smith wrote:
> > I am on FC2, setup vi Jarod's old FC2 guide.
> >
> > I am using synaptic to try to install some Myth 0.17-97 releses that
> > showed up today.
> >
> > When I pick some of the packages, Synaptic says:
> >
> > To be upgraded
> > libraw1394_8
> >
> > Then gives the following error and won't let me install:
> >
> > mythtv-backend:
> >  Depends: config(mythtv-backend) (= 0.17-97.rhfc2.at)
> >  Depends: libiec61883.so.0  but it is not installable
> >
> > What's the deal? Any help would be appreciated.
> 
> Should be fixed now. I think you hit the repo mid-update, and libiec61883
> hadn't been pushed out yet. Its a new dependency for FireWire recording
> support, which is built in to the latest ATrpms Myth packages.
> 
> --
> Jarod Wilson
> [EMAIL PROTECTED]
> 
> Got a question? Read this first...
>  http://catb.org/~esr/faqs/smart-questions.html
> MythTV, Fedora Core & ATrpms documentation:
>  http://wilsonet.com/mythtv/
> MythTV Searchable Mailing List Archive
>  http://www.gossamer-threads.com/lists/mythtv/
> 
> 
> ___
> 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] 0.17-97 install problem

[Jarod Wilson]

On Saturday 05 March 2005 12:02, Robin Smith wrote:
> I am on FC2, setup vi Jarod's old FC2 guide.
>
> I am using synaptic to try to install some Myth 0.17-97 releses that
> showed up today.
>
> When I pick some of the packages, Synaptic says:
>
> To be upgraded
> libraw1394_8
>
> Then gives the following error and won't let me install:
>
> mythtv-backend:
>  Depends: config(mythtv-backend) (= 0.17-97.rhfc2.at)
>  Depends: libiec61883.so.0  but it is not installable
>
> What's the deal? Any help would be appreciated.

Should be fixed now. I think you hit the repo mid-update, and libiec61883 
hadn't been pushed out yet. Its a new dependency for FireWire recording 
support, which is built in to the latest ATrpms Myth packages.

-- 
Jarod Wilson
[EMAIL PROTECTED]

Got a question? Read this first...
 http://catb.org/~esr/faqs/smart-questions.html
MythTV, Fedora Core & ATrpms documentation:
 http://wilsonet.com/mythtv/
MythTV Searchable Mailing List Archive
 http://www.gossamer-threads.com/lists/mythtv/


pgpFkqhVY9auL.pgp
Description: PGP signature
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 mythstreamtv works but no audio

[David Whyte]

Did you compile it right?  From memory, you have to compile it with
the correct options enabled.

The best I can offer is that you look through the archives for when
the project was released about 2 months ago.  There was some
information about it then.

Cheers,
Whytey


On Sun, 27 Feb 2005 01:06:04 -0500, Drew Bomhof <[EMAIL PROTECTED]> wrote:
> I'm running 0.17 on an Athlon 2000+  PVR-250 256MB RAM:  Debian
> Unstable.  I recently installed mythstreamtv which streams video
> fantastic.  However I can not seem to get any audio?  I know the
> recordings are fine as I have  watched them on my xbox frontend. I'm
> trying to watch the streamed recordings on a Dell d600 laptop.  All
> other apps (Itunes, etc..) including WMP 10 produce audio when I play
> audio trackes. Anyone else run in to this?
> 
> Thanks
> 
> Drew
> 
> 
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 
> 
> 


-- 
GMAIL is 'da bomb babyYEAH

I have GMail invites, if you want one, email me direct.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 observations

[Risto Treksler]

> I have also seen this.  I decided to enable comm flagging for "That
> '70s Show" lastnight.  While viewing, the frontend froze with roughly
> 1 minute remaining. 

if you let it sit long enough without pressing anything
does it come back alive?
is the hard drive light blinking fast and furious while it's frozen?

> It seems to be related to comm flagging as I have 
> never seen this problem prior to enabling it.  I will see if I can get
> some log info tonight.  I'm assuming that turning off the commercial
> auto skip will prevent this, but is there another known workaround?

ok try this to see if we are having the exact same problem

1) -play the problem recording
-hit "e" (or  "m" and choose edit recording) to get into the editor
-hit "z" to load the cutlist
- there should be a red block right at the end
  starting at the point where it freezes, going right to the end
-hit "page down"  a few times to get to the end of the recording
-hit "enter" and choose "delete this cutpoint" 
(at this point  the freeze is fixed for me)

-optionally hit "enter" again and choose "delete before this frame"
-hit "page up" a couple of times followed by "esc"
-now watch the ending, for me -> no more freezing


-- 
Risto Treksler
Elkhorn Lodge
Banff, Alberta, Canada
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 observations

[Bubba Slash]

On Thu, 17 Feb 2005 18:26:39 -0600, Michael S. Keller
<[EMAIL PROTECTED]> wrote:
> > 1. When watching a recording, as you approach the end (Final 15 seconds or
> > so) playback becomes very jittery, almost freezing during the last few
> > seconds before sending you back to the "Watch Recordings" screen.
> 
> I get this.
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 

I have also seen this.  I decided to enable comm flagging for "That
'70s Show" lastnight.  While viewing, the frontend froze with roughly
1 minute remaining.  It seems to be related to comm flagging as I have
never seen this problem prior to enabling it.  I will see if I can get
some log info tonight.  I'm assuming that turning off the commercial
auto skip will prevent this, but is there another known workaround?
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17: frontend crashing out on livetv, backend won't change channels all of a sudden

[Neil Bird]

Around about 22/02/05 13:20, Neil Bird typed ...
- livetv crashes out after a brief hang
- backend won't change channels, but does seem capable of recording
- Relevent error(?) :
ChannelBase: Could not find input: S-Video 0 on card when setting 
channel 102
  For completeness, here's my 'fix' [unexplained].  Following the hint 
of the above error, I went through mysttvsetup again prodding it so it 
re-saved the config. back to mySQL.

  Restarted backend & frontend and all seem snow well.  Not sure why it 
stuff up;  I'll have to watch it.

--
[EMAIL PROTECTED] ~]# rm -f .signature
[EMAIL PROTECTED] ~]# ls -l .signature
ls: .signature: No such file or directory
[EMAIL PROTECTED] ~]# exit
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 Frontend crashing

[Christopher Ruppel]

--- Kelly Reed Schuerman
<[EMAIL PROTECTED]> wrote:

> I am having a problem on a frontend only machine
> running 0.17.
> 
> Anytime I stop watching a show whether it is the end
> of the show or if I
> stop playback the frontend crashes.
> 
> This is what is in my mythfrontend.log:
> 
> 2005-02-20 14:19:37.655 Using protocol version 14
> 2005-02-20 14:20:14.423 Opening audio device
> '/dev/dsp'.
> 2005-02-20 14:20:14.424 Opening OSS audio device
> '/dev/dsp'.
> 2005-02-20 14:20:14.556 Using XV port 61
> 2005-02-20 14:20:15.692 Changing from None to
> WatchingPreRecorded
> 2005-02-20 14:20:15.695 Realtime priority would
> require SUID as root.
> 2005-02-20 14:20:15.721 Video timing method: USleep
> with busy wait
> *** glibc detected *** free(): invalid next size
> (normal): 0x088d3338 ***
> 
> 
> Any ideas?
> 
> Thanks,
> 
> Sherm   <><
> 
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
>
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 

I'm seeing the exact same thing with the final line of
output after the frontend crashes being the same as
above:
*** glibc detected *** free(): invalid next size
(normal)...
I'm running FC3 on my frontend.  If I can find the
time I'll recompile mythtv with debug enabled if
anyone thinks that will help diagnose the problem.

Chris

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 Frontend crashing

[Sasha Z]

I have the same issue, and upgrading to CVS hasn't resolved it like a
thread with the same problem indicated. Anybody have thoughts on this?
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 Frontend crashing

[Steve Yokanovich]

Kelly Reed Schuerman wrote:
I am having a problem on a frontend only machine running 0.17.
Anytime I stop watching a show whether it is the end of the show or if I
stop playback the frontend crashes.
This is what is in my mythfrontend.log:
2005-02-20 14:19:37.655 Using protocol version 14
2005-02-20 14:20:14.423 Opening audio device '/dev/dsp'.
2005-02-20 14:20:14.424 Opening OSS audio device '/dev/dsp'.
2005-02-20 14:20:14.556 Using XV port 61
2005-02-20 14:20:15.692 Changing from None to WatchingPreRecorded
2005-02-20 14:20:15.695 Realtime priority would require SUID as root.
2005-02-20 14:20:15.721 Video timing method: USleep with busy wait
*** glibc detected *** free(): invalid next size (normal): 0x088d3338 ***

I've had the same problem since upgrading to 0.17 last week, although my 
log output varies. An example from mine is:

Changing from WatchingPreRecorded to None
Changing from None to None
Then a black screen and no keyboard response.
I can start a show, ff almost to the end and the show will end fine and 
return to the menu. If I play the same show from the beginning to the 
end it will hang up with a black screen at the end.

I also have a similar problem when I leave a prerecorded show paused for 
10 or 15 minutes. When I resume playback, mythfrontend will hang.

I have started running mythfrontend from a command shell window so I can 
Ctrl-C it when it happens.

Running Fedora Core 3, Kernel 2.6.10-1.741_FC3 and Mythtv 0.17
Steve Yokanovich
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 disable tv_grab_sn?

[Mathias Wennberg]

Thanks Tony, it work

However, now when I realised the swedb project I have registered for an 
account there instead. I will switch to this project instead to show my 
support. I can't understand how I could have missed the information about 
this project earlier!

/Matias

On lördagen den 19 februari 2005 18.34, Tony Clark wrote:
> On Saturday 19 February 2005 15:11, Mathias Wennberg wrote:
> > Hello
> >
> > Recently upgraded to 0.17.
> > However, after this mythfilldatabase don't seams to want to run.
> >
> > I have a hacked tv_grab_sn so I know this works. However, it seams that
>
> synmlink it to tv_grab_se_swedb
>
> That works for me after choosing that in setup
>
> tony
> ___
> 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] 0.17 disable tv_grab_sn?

[Tony Clark]

On Saturday 19 February 2005 15:11, Mathias Wennberg wrote:
> Hello
>
> Recently upgraded to 0.17.
> However, after this mythfilldatabase don't seams to want to run.

> I have a hacked tv_grab_sn so I know this works. However, it seams that

synmlink it to tv_grab_se_swedb

That works for me after choosing that in setup

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

Re: [mythtv-users] 0.17 - Duplicate detection not working

[Martin Ebourne]

On Tue, 2005-02-15 at 17:01 -0500, Jack Trout wrote:
> On Tue, 15 Feb 2005 18:32:52 +, Martin Ebourne <[EMAIL PROTECTED]> wrote:
> > I've recently upgraded to 0.17 (atrpms, previously using cvs from xmas),
> > and now the duplicate detection on recordings doesn't seem to be
> > working. Any recordings set to 'record at any time on this channel',
> > 'record at any time on any channel' etc, list all repeats as set to
> > record.
> Well if your using the DVB Guide information vs XMLTV the default
> duplicate detection checks for episode name + description, so it can
> have the same name, but if the description is different this is still
> considered a new show and will be recorded, So if the EPG data is
> formated differently than whatever your xmltv source was, the database
> is gonna see them as different shows

Thanks for the ideas, but unfortunately that's not it. In these cases
the name, subtitle, and description are all identical. Also I've always
been using the DVB guide data (previously with tv_grab_dvb) and this was
working before, except for some of the BBC shows where they seem to like
to re-write the description every time they show a repeat. Or even
better, add '[repeat]' on the end. Nice one, thanks guys! Must write a
patch to remove that at some point.

Anyhow, seems like I'm the only person here with broken duplicate
detection so I'll just have to get in there and debug it.

Cheers,

Martin.

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

Re: [mythtv-users] 0.17 transcoding to remove commercials fubars ffwd

[Chris Pinkham]

> Problem: 
> If I cut commercials, and transcode to remove them from the recording,
> it will mess up fastforward and rewind functionality on playback.  If
> played back without ffwd/rew, it plays OK, but when you press ffwd, it
> will freeze, and then it will exit to the main menu.

I believe this was due to some enhancements in the A/V syncing code not
agreeing with the way that timecodes were kludged in transcoded files.
When the trancoder cuts out the video in the cutlist, it did not fixup
the timecodes to make them sequential again.  There are big jumps in
the timecodes at each cut point.  This has been partially fixed in
current CVS.  It's fixed for transcodes from MPEG2->(MPEG-4|RTJPEG), but
it is not fixed for transcodes that do not reencode video (such as just
cutting the cutlist out of a MPEG4 file and generating a new MPEG-4 file).
I believe I know of a way I can fix this completely but need to code it
up and test it.

Might get that into CVS a little later tonight.

-- 

Chris

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

Re: [mythtv-users] 0.17 observations

[Dave]

>2. When watching a recording, having it chuck you out in the middle with the
>"You have finished watching" when you haven't actually reached the end.
> 
I've been getting this intermittantly (1 out of 10 viewings or so) with  .16 
Sounds like it hasn't been fixed in .17

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

Re: [mythtv-users] 0.17 observations

[Michael S. Keller]

1. When watching a recording, as you approach the end (Final 15 seconds or
so) playback becomes very jittery, almost freezing during the last few
seconds before sending you back to the "Watch Recordings" screen.
I get this.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 backend segfaults

[Antti Siiskonen]

On Thu, Feb 17, 2005 at 09:03:07AM +, Tom Hughes wrote:
> In message <[EMAIL PROTECTED]>
> Nick Craig-Wood <[EMAIL PROTECTED]> wrote:
> 
> > On Wed, Feb 16, 2005 at 03:34:08PM +0200, Antti Siiskonen wrote:
> >> debugged with njamd or most tools so I can't find the real reason for
> >> this segfault. Any help still appreciated.
> >
> > sorts of nasties.  Unfortunately I'm not sure valgrind works very well
> > with threaded programs.
> 
> It should work fine with threaded programs. The CVS code might be
> better as it uses the system threading library instead of replacing

It seems that I can't repeat the same spontaneous segfault under 
valgrind. However after some fiddling with live tv valgrind said:


==22813== Thread 9:
==22813== Mismatched free() / delete / delete []
==22813==at 0x1B903579: operator delete(void*) 
(vg_replace_malloc.c:156)
==22813==by 0x1BD59AC6: DVBRecorder::~DVBRecorder() 
(dvbrecorder.cpp:100)
==22813==by 0x1BD0AB9E: TVRec::TeardownRecorder(bool) 
(tv_rec.cpp:752)
==22813==by 0x1BD09E92: TVRec::HandleStateChange() (tv_rec.cpp:629)
==22813==  Address 0x1D4E1E58 is 0 bytes inside a block of size 188 
alloc'd
==22813==at 0x1B903246: operator new[](unsigned) 
(vg_replace_malloc.c:139)
==22813==by 0x1BD5949F: DVBRecorder::DVBRecorder(DVBChannel*) 
(dvbrecorder.cpp:88)
==22813==by 0x1BD0A2CA: TVRec::SetupRecorder(RecordingProfile&) 
(tv_rec.cpp:688)
==22813==by 0x1BD095E7: TVRec::HandleStateChange() (tv_rec.cpp:555)


Also mythtv log says a lot of these

2005-02-17 17:39:45.007 DVB#0 ERROR - Reading Section.
  (75) Value too large for defined data type

which I didn't see before (without valgrind).


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

RE: [mythtv-users] 0.17 broke my DVB setup :(

[Krunoslav Pisacic]

> Everyone's situation is different so it's probably hard to 
> make something that will work for everyone but if you figure 
> out a way to do it please share it with the list. And don't 
> forget to backup your db before messing with this... :)
> 
> 

I have had some success with migrating old DVB channel setup to new table 
structures. These were the steps i used - maybe it helps
some too. 
It is paint to do it, but it can be done. I dont know if this has some bad 
effects on system (Jesper?)

- this is done mostly in mysql, i have used Toad for MySQL from www.quest.com 
from windows machine to make things easier for me.


0. In contract to other reports my install of 0.17 with atrpms packages did not 
brop old dvb_* tables - but is is good to have their
backup:
create table dvb_channel_bck as select * from dvb_channel;
create table dvb_pids_bck as select * from dvb_pids;

1. look at table videosource to see what id have a video source that is 
connected to DVB device. DVB channel scanner will create
chanid-s with this SOURCEID*1000. 

2. Check that you existing  CHANNEL table does not have chanid in this 
SOURCEID*1000 span:
select * from channel where chanid between SOURCEID*1000 and 
(SOURCEID+1)*1000;
-- replace SOURCEID with mumber from your setup.
There shouldn't be any records. If there are - which is bad, you could try to 
define new videosource (mythtvsetup will give it first
next ID)

3. Next you must populate dvt_multiplex table. I have done it with channel 
scan, but i belive it could be also done by selecting
distinct frequencies from dvb_channel - the only information missing in 
old-style tables is SERVICEVERSION - and i dnot know what is
this and if this could be left null or 0.
After you have run scan, new channels will be create too - you can leave them 
as they are, or delete them later on.

4. Now the "clever" part, run following query:

select concat("update channel set sourceid=", dtv_multiplex.sourceid, 
",mplexid=", dtv_multiplex.mplexid,
",serviceid=",dvb_channel.serviceid," where chanid=",channel.chanid)
from channel, dvb_channel, dtv_multiplex 
where channel.chanid = dvb_channel.chanid 
and channel.serviceid is null 
and dtv_multiplex.sourceid=SOURCEID and dvb_channel.satid=SATID
and (dtv_multiplex.transportid=dvb_channel.transportid OR 
( dtv_multiplex.frequency=dvb_channel.frequency
AND dtv_multiplex.polarity=dvb_channel.polarity  
)
  ) 
order by channel.channum;

-- replace SOURCEID with SOURCEID of DVB input connection, and SATID with id 
from satelite if you receive more that one satelite
position. 
-If you receive more than one sat (diseq switch), i think you need to create 
separate videosource and input connection for each
diseq port.
-it will give you a bunch update sql statements which update apropriate fields 
(most important SERVICEID) in CHANNEL table.
-if it return less then number of channels you want to migrate, you could try 
changing
"dtv_multiplex.frequency=dvb_channel.frequency" to 
"(SUBSTRING(dtv_multiplex.frequency,1,5)=substring(dvb_channel.frequency,1,5)" 
or
even 
"(SUBSTRING(dtv_multiplex.frequency,1,4)=substring(dvb_channel.frequency,1,4)" 
- this reduces precision of matching frequencies
from old tables to new table to 5 and 4 first digits.

5. You can now delete newly created channels:
delete from channel where chanid between SOURCEID*1000 and 
(SOURCEID+1)*1000;
, or keep than on some high channum:
update channel set channum=chanid+2 where chanid between 
SOURCEID*1000 and (SOURCEID+1)*1000;


and yes - as Jasper said: DON'T FORGET TO BACKUP YOUR DB BEFORE MESSING WITH 
THIS.


br,

k.

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

Re: [mythtv-users] 0.17 backend segfaults

[Tom Hughes]

In message <[EMAIL PROTECTED]>
Nick Craig-Wood <[EMAIL PROTECTED]> wrote:

> On Wed, Feb 16, 2005 at 03:34:08PM +0200, Antti Siiskonen wrote:
>> I compiled libmysqlclient with debug symbols on and did some more
>> digging with various debugging tools and google and to me it seems that
>> someone is calling free() twice. Mythbackend is too large to be
>> debugged with njamd or most tools so I can't find the real reason for
>> this segfault. Any help still appreciated.
>
> You could try valgrind.  I valgrind-ed our largest product at work (a
> few hundred thousand lines of C++) which nothing has ever been able to
> do before.  It didn't run very quickly but it did work and I found all
> sorts of nasties.  Unfortunately I'm not sure valgrind works very well
> with threaded programs.

It should work fine with threaded programs. The CVS code might be
better as it uses the system threading library instead of replacing
it.

Tom

-- 
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 backend segfaults

[Nick Craig-Wood]

On Wed, Feb 16, 2005 at 03:34:08PM +0200, Antti Siiskonen wrote:
> I compiled libmysqlclient with debug symbols on and did some more
> digging with various debugging tools and google and to me it seems that
> someone is calling free() twice. Mythbackend is too large to be
> debugged with njamd or most tools so I can't find the real reason for
> this segfault. Any help still appreciated.

You could try valgrind.  I valgrind-ed our largest product at work (a
few hundred thousand lines of C++) which nothing has ever been able to
do before.  It didn't run very quickly but it did work and I found all
sorts of nasties.  Unfortunately I'm not sure valgrind works very well
with threaded programs.

-- 
Nick Craig-Wood <[EMAIL PROTECTED]> -- http://www.craig-wood.com/nick
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 backend segfaults

[Antti Siiskonen]

On Mon, Feb 14, 2005 at 11:24:44AM +0200, Antti Siiskonen wrote:
> On Sun, Feb 13, 2005 at 04:07:48PM -0500, Chris Pinkham wrote:
> > "bt" isn't enough because it doesn't show all threads.  Look at the
> > HOWTO for necessary steps to get a good backtrace.
> 
> Ok, new quite lengthy trace attached. While I have basic understanding 

I compiled libmysqlclient with debug symbols on and did some more
digging with various debugging tools and google and to me it seems that
someone is calling free() twice. Mythbackend is too large to be
debugged with njamd or most tools so I can't find the real reason for
this segfault. Any help still appreciated.


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

Re: [mythtv-users] 0.17 scanning issue

[Mattia Martinello]

I'm sorry... I solved it...
It was a DVB Driver related problem... :-(
Thank you very much anymore!
Bye
Mattia
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 scanning issue

[Eyal Lebedinsky]

Mattia Martinello wrote:
Hi,
I tried to install Mythtv 0.17 with Fedora Core 3 and an Hauppauge WinTV 
Nova CI.
I cannot scanning DVB channels with "Full Scanning or "Existing 
transports scan" functions. The scanning seems to hang at 5% or 10% and 
it never continue (I wait for many minutes)...
I had a similar issue. I finally added all the transports with mythtv-setup
using the Advanced menu, and then scanned the existing transports. This
worked for me. Naturally, I had the details for the transports. I am not
sure if saying 'auto' for everything (except the frequency) will pick
the correct parameters.
--
Eyal Lebedinsky ([EMAIL PROTECTED]) 
attach .zip as .dat
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 - Duplicate detection not working

[Dmitri Colebatch]

Jack Trout wrote:

  On Tue, 15 Feb 2005 18:32:52 +, Martin Ebourne <[EMAIL PROTECTED]> wrote:
  
  
I've recently upgraded to 0.17 (atrpms, previously using cvs from xmas),
and now the duplicate detection on recordings doesn't seem to be
working. Any recordings set to 'record at any time on this channel',
'record at any time on any channel' etc, list all repeats as set to
record.

I've tried fiddling with the various detection options, and cancelling
and recreating the recording, no difference.

I'm using DVB in the UK. I let myth delete all capture cards and
channels, and then let the autodetection run. All seems to work fine,
including the EPG (though I did have to repeat the channel scan because
some channels were missed first time).

Anyone else seeing anything similar? Anything obvious I've missed?

  
  Well if your using the DVB Guide information vs XMLTV the default
duplicate detection checks for episode name + description, so it can
have the same name, but if the description is different this is still
considered a new show and will be recorded, So if the EPG data is
formated differently than whatever your xmltv source was, the database
is gonna see them as different shows

This is nice for some series' where a 2 part episode has the same
name, and only the description differs it from part one to part 2
  

I found the opposite, but being a newbie and still learning my way
around I've got a few more important things to fix.  But using xmltv
melbourne freetoair guide info I tried to set it up to tape ER - this
Thursday there are two episode, but I seem to have multiple entries for
them (it appears I still have duplicate channel info in the guide) so I
selected record this once, and it skipped the next episode as well,
which had a different subtitle but same title.

Does that match with other people's experiences?

While I'm here - thanks to those who've helped me already with this,
very happy with it and I can see that it'll completely change my life
(o:

cheers
dim


##DISCLAIMER:This 
email and any attachment may contain confidential information.If you are not 
the intended recipient you are not authorized to copyor disclose all or any 
part of it without the prior written consentof Toyota.
Opinions expressed in this email and any attachments are those of 
thesender and not necessarily the opinions of Toyota.Please scan this 
email and any attachment(s) for viruses.Toyota does not accept any 
responsibility for problems caused byviruses, whether it is Toyota's fault 
or 
not.##


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

RE: [mythtv-users] 0.17 frontend crash caused by mythphone (NOTFestival)

[Paul Volkaerts]

> 
> #0  0x021798da in SipFsm::DetermineNatAddress() (this=0x897ef60)
> at sipfsm.cpp:699
> 699 hostIp.setAddress(ntohl(*(long *)h->h_addr));
> 
> I suddenly realised that my ISP was down, so I changed the NAT setting 
> from auto to manual and hey presto it stopped crashing.
> 
> One for Paul Volkaerts ... ?

Certainly is!  Thanks :-)

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

Re: [mythtv-users] 0.17 - Duplicate detection not working

[Jack Trout]

On Tue, 15 Feb 2005 18:32:52 +, Martin Ebourne <[EMAIL PROTECTED]> wrote:
> I've recently upgraded to 0.17 (atrpms, previously using cvs from xmas),
> and now the duplicate detection on recordings doesn't seem to be
> working. Any recordings set to 'record at any time on this channel',
> 'record at any time on any channel' etc, list all repeats as set to
> record.
> 
> I've tried fiddling with the various detection options, and cancelling
> and recreating the recording, no difference.
> 
> I'm using DVB in the UK. I let myth delete all capture cards and
> channels, and then let the autodetection run. All seems to work fine,
> including the EPG (though I did have to repeat the channel scan because
> some channels were missed first time).
> 
> Anyone else seeing anything similar? Anything obvious I've missed?

Well if your using the DVB Guide information vs XMLTV the default
duplicate detection checks for episode name + description, so it can
have the same name, but if the description is different this is still
considered a new show and will be recorded, So if the EPG data is
formated differently than whatever your xmltv source was, the database
is gonna see them as different shows

This is nice for some series' where a 2 part episode has the same
name, and only the description differs it from part one to part 2
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 DB update problems

[Bruce Markey]

Caleb wrote:
2005-02-15 10:36:08.593 Upgrading to schema version 1069
2005-02-15 10:36:08.594 DB Error (Performing database upgrade):
Query was: ALTER TABLE recorded ADD COLUMN deletepending TINYINT(1) NOT 
NULL DEFAULT 0;

Error was: Driver error was [2/1060]:
1)
mysql -u mythtv -pmythtv mythconverg
2)
ALTER TABLE recorded DROP COLUMN deletepending;
quit
3)
mythbackend
--  bjm
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 - Can view live TV, but cannot record. [solved]

[Steffen]

On Mon, 14 Feb 2005, Steffen wrote:
> recording stopped working after upgrading from 0.16 to 0.17.
> I am able to view live TV, and pause live TV just fine, but recording 
> fails for some reason. Anyone else seen similar behaviour?
> 
> here's the verbose mythbackend log
> 
> 2005-02-14 18:46:17.258 Scheduled 13 items in 0.9 = 0.03 match + 0.85 place
> 2005-02-14 18:46:17.273 Recording starts soon, AUTO-Startup assumed
> 2005-02-14 18:46:17.290 Started recording "Mythbusters" on channel: 2 on 
> cardid: 1, sourceid 1
> 2005-02-14 18:46:17.296 Channel(/dev/video0)::SwitchToInput(in 1)
> 2005-02-14 18:46:17.299 Channel(/dev/video0)::SwitchToInput() setting video 
> mode to NTSC
> 2005-02-14 18:46:17.323 Channel(/dev/video0)::TuneTo(SE10): 
> curList[23].freq(168250)
> 2005-02-14 18:46:17.326 Channel(/dev/video0)::TuneToFrequency(2692)
> 2005-02-14 18:46:17.469 Changing from None to RecordingOnly
> 2005-02-14 18:46:17.545 Using profile 'Default' to record
> 2005-02-14 18:46:17.588 Channel(/dev/video0)::CheckSignalFull(): input = 1
> 2005-02-14 18:46:17.624 Using Sample Spacing of 4 horizontal & 4 vertical 
> pixels.
> 2005-02-14 18:46:17.631 CommDetect::ClearAllMaps()
> VIDIOCSYNC: Input/output error
> [snip]
> VIDIOCSYNC: Input/output error
> VIDIOCSYNC: Input/output error
> 2005-02-14 18:46:22.642 NVR: Multiple bttv errors, further messages supressed
> 
> How come it says 'setting video mode to NTSC' there? I'm using PAL-BG..

I'm happy to say that I solved it. Don't know why this bug occured, but 
deleting my card settings and all channels fixed the problem. 

So, when upgrading from 0.16 to 0.17 (at least with gentoo ebuilds), 
something might happen, which might fsck up the channel settings. 
Therefore I'd advise anyone with similar problems to answer yes to the 
first two questions in mythsetup, after upgrading to 0.17.

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

Re: [mythtv-users] 0.17 choppy video, artifacting and random drop to black frame during playback...

[Josh Dalcher]

OK, I'm getting somewhere... I figured that playback could possibly be 
affected by other software outside of myth, so I did an apt-get dist-upgrade 
and that has gotten me to buttery smooth playback.  The only thing left 
remaining is that the picture still drops to a black frame after about 
thirty seconds to a minute of playback.

I'm still seeing no anomolies in the logs, nor do I have any screensaver or 
power mode settings turned on.  Any help I could get to fix this last issue 
would be appreciated.

- Original Message - 
From: "Josh Dalcher" <[EMAIL PROTECTED]>
To: "Discussion about mythtv" 
Cc: 
Sent: Monday, February 14, 2005 5:48 PM
Subject: Re: [mythtv-users] 0.17 choppy video,artifacting and random drop to 
black frame during playback...


Here is the output of my frontend when running -v playback.  Does anyone 
see anything out of the ordinary?  Thanks for the help! 

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

Re: [mythtv-users] 0.17 choppy video, artifacting and random drop to black frame during playback...

[Josh Dalcher]

Here is the output of my frontend when running -v playback.  Does anyone see 
anything out of the ordinary?  Thanks for the help!

2005-02-14 17:34:59.650 mythfrontend version: 0.17.20050130-1 www.mythtv.org
2005-02-14 17:34:59.651 Enabled verbose msgs : important general playback
2005-02-14 17:35:00.386 Switching to square mode (G.A.N.T.)
2005-02-14 17:35:01.080 Joystick disabled.
2005-02-14 17:35:01.156 Registering Internal as a media playback plugin.
2005-02-14 17:35:01.190 Registering MythDVD DVD Media Handler as a media 
handler

2005-02-14 17:35:01.190 Registering MythDVD VCD Media Handler as a media 
handler

2005-02-14 17:35:01.684 Registering MythMusic Media Handler as a media 
handler

SIP listening on IP Address 192.168.0.10:5060 NAT address 192.168.0.10
SIP: Cannot register; proxy, username or password not set
2005-02-14 17:35:02.155 Mediamonitor: Adding /dev/cdrom
2005-02-14 17:35:02.159 Starting media monitor.
2005-02-14 17:35:02.167 Media status changed... New status is: 
MEDIASTAT_OPEN old status was MEDIASTAT_NOTMOUNTED

2005-02-14 17:35:23.041 All Programs
2005-02-14 17:35:23.576 Connecting to backend server: 127.0.0.1:6543 (try 1 
of 5)

2005-02-14 17:35:23.584 Using protocol version 14
2005-02-14 17:35:24.978 detectInterlace(Ignore Scan, Detect Scan, 29.97, 
480) ->Ignore Scan

2005-02-14 17:35:24.979 Interlaced: Ignore Scan video_height: 480 fps: 29.97
2005-02-14 17:35:24.979 Estimated bitrate = 8000
2005-02-14 17:35:25.187 Position map filled from DB to: 3587
2005-02-14 17:35:25.188 SyncPositionMap prerecorded, from DB: 3588 entries
2005-02-14 17:35:25.188 Position map found
2005-02-14 17:35:25.194 Opening audio device '/dev/dsp'.
2005-02-14 17:35:25.194 Opening OSS audio device '/dev/dsp'.
2005-02-14 17:35:25.197 Using resampler. From: 0 to 1000
2005-02-14 17:35:25.207 Over/underscan. V: 0.08, H: 0.08, XOff: 40, YOff: 0
2005-02-14 17:35:25.210 Image size. dispxoff 0, dispyoff: 0, dispwoff: 720, 
disphoff: 480

2005-02-14 17:35:25.210 Image size. imgx 18, imgy: 38, imgw: 605, imgh: 403
Using the PVR-350 decoder/TV-out
2005-02-14 17:35:25.845 Changing from None to WatchingPreRecorded
2005-02-14 17:35:25.845 Using realtime priority.
2005-02-14 17:36:12.968 Changing from WatchingPreRecorded to None
2005-02-14 17:36:12.989 Changing from None to None
2005-02-14 17:36:13.686 AVFD
2005-02-14 17:36:13.686 AVFD: Opening Stream #0: codec id 2
2005-02-14 17:36:13.686 detectInterlace(Detect Scan, Detect Scan, 29.97, 
480) ->Interlaced Scan

2005-02-14 17:36:13.686 Interlaced: Interlaced Scan video_height: 480 fps: 
29.97

2005-02-14 17:36:13.686 AVFD: Looking for decoder for 2
2005-02-14 17:36:13.687 AVFD
2005-02-14 17:36:13.687 AVFD: Opening Stream #1: codec id 86016
2005-02-14 17:36:13.687 AVFD: Looking for decoder for 86016
2005-02-14 17:36:13.689 Estimated bitrate = 6384
2005-02-14 17:36:13.730 Image size. dispxoff 0, dispyoff: 0, dispwoff: 0, 
disphoff: 0

2005-02-14 17:36:13.730 Image size. imgx 0, imgy: 38, imgw: 403, imgh: 403
2005-02-14 17:36:13.731 waiting for prebuffer...
2005-02-14 17:36:13.732 positionMap[ 0 ] == 38.
2005-02-14 17:36:13.798 positionMap[ 1 ] == 372774.
2005-02-14 17:36:13.868 HandleGopStart: gopset not set, syncing positionMap
2005-02-14 17:36:13.868 SyncPositionMap prerecorded, from DB: 2 entries
2005-02-14 17:36:13.868 Stream initial keyframedist: 15.
2005-02-14 17:36:13.869 positionMap[ 2 ] == 794662.
2005-02-14 17:36:14.201 positionMap[ 3 ] == 1212454.
- Original Message - 
From: "Josh" <[EMAIL PROTECTED]>
To: "Discussion about mythtv" 
Cc: 
Sent: Monday, February 14, 2005 10:42 AM
Subject: [mythtv-users] 0.17 choppy video,artifacting and random drop to 
black frame during playback...


Hello,
I recently upgraded from a working version of 0.16 to 0.17 and I am having
playback issues.  I see choppy playback, artifacting, and after about 
thirty
seconds of video playback (both recordings and LiveTV) I get a black 
screen
that will go away if I use the remote.  The playback still remains choppy
after this fact.

I have re-added suid root for mythfrontend, mythtv, and I have recently
restarted both the backend and frontend.  I'm seeing no anomolies in the 
logs
at all.

Could this be an ivtv issue, or is there something in my configuration 
that
needs to change?  I just did an apt-get install mythtv-suite and 
everything
appears to be kosher except for this playback problem.  The rest of my 
MythTV
settings did not change from my previously working 0.16 installation.

Here is the output of rpm -qa | grep ivtv
ivtv-firmware-dec-2.02.023-4.at
kernel-module-ivtv-2.6.8-1.521-0.1.10-48.3_pre2_ck100zz.rhfc2.at
ivtv-0.1.10-48.3_pre2_ck100zz.rhfc2.at
ivtv-firmware-enc-2.04.024-4.at
ivtv-firmware-1.8a-4.at
perl-Video-ivtv-0.13-6.rhfc2.at
My kernel version is: 2.6.8-1.521 running Fedora Core 2.
Thank you for the assistance, my wife is going crazy with this not 
working!
If you need any additional information to help me troubleshoot this 
problem,
please reply to [EMAIL 

Re: [mythtv-users] 0.17 - Can view live TV, but cannot record. Weird.

[starv-mythtv]

On Mon, 14 Feb 2005, Bruce Markey wrote:
> Steffen wrote:
> 
> > How come it says 'setting video mode to NTSC' there? I'm using PAL-BG..
> > That might be a possible reason for this, right?
> > But how come watching live tv works?
> 
> Go to TV Settings->Recording Profiles and maye sure the profile
> for "Default" is sane. Make it the same as the working "Live TV"
> if nothing else.

Tried that. The Default profile seemes to be exactly the same as the live 
TV profile. Tried recording a show with the live tv profile too, and got 
the same problem.

There isn't anywhere in the recording profiles where it could be set to 
NTSC instead of PAL anyway, as far as I can find?

Where in the mythconverg database are recording profiles stored?

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

Re: [mythtv-users] 0.17 DVB scan fails ...

[Dmitri Colebatch]

Hamish Moffatt wrote:

  On Sun, Feb 13, 2005 at 06:01:17PM +1100, Chris Edwards wrote:
  
  
Hamish Moffatt wrote:


  In my scans in Melbourne, none of the networks give any network
information for any other network. All of VHF stations list only their
own frequency for Melbourne, except SBS which lists half a dozen
different frequencies.

So I had to manually enter 5 multiplexes.
  

Yup, that's exactly what I had to do (I'm in Melbourne too). What's the 
deal with those SBS ones? I'm guessing they're probably the other 
stations in Sydney or something, judging from the way SBS usually 

  
  
Yup I think they're for interstate.

  
  
operates! Also, all the SBS channels seem to add themselves two or three 
times, with the same channel number each time. It's quite annoying.

  
  I didn't notice that. I was annoyed by Channel Ten though which has
defined 4-5 channels which are identical, with numbers such as 1.
The main SBS channel came up as 3. I spent some time in the editor
straightening this out.
  

Hi guys,

I'm also in Melbourne and am fumbling my way through getting this
setup.  When I initially did the autoscan I found a whole bunch of
channels, including the HD ones (which seemed to make the frontend
segfault).  I've deleted those manually from the channel table, and
seem to have things working so-so now, although I have several
duplicate channels.  I'm deleting them by hand, but am concerned that
maybe I've missed something and that I shouldn't really need to any
suggestions as to anything I might have missed to cause this behaviour,
or is what I'm doing (deleting by hand) a reasonable.

cheers
dim



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

RE: [mythtv-users] 0.17 observations

[Tom Clark]

 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Brad Templeton
> Sent: 13 February 2005 20:07
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] 0.17 observations
> 
> On Sun, Feb 13, 2005 at 03:04:38PM -0500, David George wrote:
> > On 02/13/2005 02:28 PM, Tom Clark wrote:
> > Amazingly this just started happening to me a week or two 
> ago.  I have 
> > always run from /usr/local, and I hadn't changed anything 
> in my config.
> > So I was at a loss as to why it happened.  Anyway, I am running FC2 
> > and the init scripts set a path when they are run.  I had 
> to fix this 
> > by adding the following before the start() function in 
> /etc/init.d/mythbackend:
> > 
> > if ! strstr "$PATH" "/usr/local/bin" ; then  
> PATH=$PATH:/usr/local/bin 
> > fi
> > 
> 
> yes, this works, though in theory you might want to keep your local
> config changes in /etc/sysconfig/myththbackend which is where they
> properly go.
> 
> Or write a patch for mythtv, since it knows the "prefix" it gets
> installed to, to add PREFIX/bin to the path it tries when executing
> commands, so users don't have to do any extra config.
> 

I've just made the suggested change to my rc.mythbackend file (I'm running
Slack 10) and it's now flagging commercials as expected.

Regards,
Tom Clark
[EMAIL PROTECTED]

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

RE: [mythtv-users] 0.17 observations

[Tom Clark]

 
> -Original Message-
> From: Risto Treksler [mailto:[EMAIL PROTECTED] 
> Sent: 14 February 2005 18:28
> To: Tom Clark
> Cc: mythtv-users@mythtv.org
> Subject: RE: [mythtv-users] 0.17 observations
> 
> 
> 
> Tom Clark <[EMAIL PROTECTED]> said:
> 
> > 
> > Just tried your suggestions and got the following results hit esc 
> > while it's frozen - does it lock up? No
> 
> hey, can you try hitting "esc" or "p" a couple of times, 
> maybe even tapping it the screen goes blank and the frontend 
> has to be killed ... at least for me
> 
> 
> > hit 99 while it is frozen - does it segfault? Yes
> 
> I submitted a backtrace about this last night
> 
> 
> > does the hard drive light ever go crazy while it is frozen 
> > for the 5 or ten seconds before it goes back to the list of 
> > recordings? No
> 
> for me it doesn't happen with every show
> this seems to only happen when commercial auto skip is trying 
> to skip through
> the last commercial which is at the very end of the show 
> 
> Of course there could be something else going on

I had an issue until just now where mythcommflag was not running, so none of
the shows I've recorded since 0.17 have had a flaglist.
Perhaps this is related?

I've since fixed my issue with mythcommflag and have requeued all of the
jobs. I'll repeat the tests and see if there's any difference.


> 
> > do you see messages like these in the frontend logs?
> > - Waited 2 seconds for data to become available, waiting again...
> 
> seems to be linked to the short freezing at the very end of every show
> and usually prints once or twice
> 
> > - Waited too long for decoder to pause
> 
> prints if the frontend hangs
> and it prints over and over and over again
> 
> --
> Risto
> 
> 

Regards,
Tom Clark
[EMAIL PROTECTED]

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

Re: [mythtv-users] 0.17 - Can view live TV, but cannot record. Weird.

[Bruce Markey]

Steffen wrote:
How come it says 'setting video mode to NTSC' there? I'm using PAL-BG..
That might be a possible reason for this, right?
But how come watching live tv works?
Go to TV Settings->Recording Profiles and maye sure the profile
for "Default" is sane. Make it the same as the working "Live TV"
if nothing else.
--  bjm
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

RE: [mythtv-users] 0.17 observations

[Risto Treksler]

Tom Clark <[EMAIL PROTECTED]> said:

> 
> Just tried your suggestions and got the following results
> hit esc while it's frozen - does it lock up? No

hey, can you try hitting "esc" or "p" a couple of times, 
maybe even tapping it
the screen goes blank and the frontend has to be killed ... at least for me


> hit 99 while it is frozen - does it segfault? Yes

I submitted a backtrace about this last night


> does the hard drive light ever go crazy while it is frozen 
> for the 5 or ten seconds before it goes back to the list of 
> recordings? No

for me it doesn't happen with every show
this seems to only happen when commercial auto skip is trying to skip through
the last commercial which is at the very end of the show 

Of course there could be something else going on


> do you see messages like these in the frontend logs?
> - Waited 2 seconds for data to become available, waiting again...

seems to be linked to the short freezing at the very end of every show
and usually prints once or twice

> - Waited too long for decoder to pause

prints if the frontend hangs
and it prints over and over and over again

--
Risto

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

RE: [mythtv-users] 0.17 observations

[Tom Clark]

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Clark
> Sent: 14 February 2005 18:05
> To: [EMAIL PROTECTED]; 'Discussion about mythtv'
> Subject: RE: [mythtv-users] 0.17 observations
> 
>  
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On Behalf Of Risto Treksler
> > Sent: 13 February 2005 23:58
> > To: Discussion about mythtv
> > Subject: Re: [mythtv-users] 0.17 observations
> > 
> > On Sunday 13 February 2005 02:15 pm, Andrew McNabb wrote:
> > > On Sun, Feb 13, 2005 at 07:28:44PM -, Tom Clark wrote:
> > > > Has anyone else experienced the following?
> > > >
> > > > 1. When watching a recording, as you approach the end (Final 15 
> > > > seconds or so) playback becomes very jittery, almost
> > freezing during
> > > > the last few seconds before sending you back to the
> > "Watch Recordings" screen.
> > >
> > > I'm having the same problem.  It's not the most critical
> > problem ever,
> > > but it can be pretty annoying.  I've had it wait five or
> > ten seconds
> > > on a black screen, and just before you have a chance to hit 
> > > ctrl-alt-backspace it returns to the program listing.
> > >
> > > I don't know how to troubleshoot it, though.
> > 
> > I reported something very similar to the myth-dev list under:
> > [mythtv] 0.17 - mythfrontend freezing at end of recordings
> > 
> > does that sound familiar?
> >  
> > please try this out
> > - hit esc while it's frozen - does it lock up?
> > - hit 99 while it is frozen - does it segfault?
> > 
> > does the hard drive light ever go crazy while it is frozen 
> for the 5 
> > or ten seconds before it goes back to the list of recordings?
> > 
> > 
> > do you see messages like these in the frontend logs?
> > 
> > - Waited 2 seconds for data to become available, waiting again...
> > - Waited too long for decoder to pause
> > 
> > -- 
> > Risto Treksler
> > Elkhorn Lodge
> > Banff, Alberta, Canada
> > ___
> > mythtv-users mailing list
> > mythtv-users@mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > 
> 
> Just tried your suggestions and got the following results
> hit esc while it's frozen - does it lock up? No
> hit 99 while it is frozen - does it segfault? Yes
> 
> does the hard drive light ever go crazy while it is frozen 
> for the 5 or ten seconds before it goes back to the list of 
> recordings? No
> 
> do you see messages like these in the frontend logs?
> - Waited 2 seconds for data to become available, waiting again...
> - Waited too long for decoder to pause
> 
> I get the following:
> 2005-02-14 18:03:27.775 prebuffering pause
> 2005-02-14 18:03:30.466 prebuffering pause
> 2005-02-14 18:03:34.001 prebuffering pause
> 2005-02-14 18:03:37.034 prebuffering pause
> 2005-02-14 18:03:39.815 prebuffering pause
> 2005-02-14 18:03:40.047 Waited 2 seconds for data to become available,
> waiting again...
> 2005-02-14 18:03:42.951 Waited 2 seconds for data to become available,
> waiting again...
> 2005-02-14 18:03:44.079 Changing from WatchingPreRecorded to None
> 2005-02-14 18:03:44.178 Changing from None to None
> 
> Any help to anyone?
> 
> Regards,
> Tom Clark
> [EMAIL PROTECTED]
> 
> 

Oh, and the "prebuffering pause" messages coincide precisely with when the
video freezes.

Regards,
Tom Clark
[EMAIL PROTECTED]

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

RE: [mythtv-users] 0.17 observations

[Tom Clark]

 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Risto Treksler
> Sent: 13 February 2005 23:58
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] 0.17 observations
> 
> On Sunday 13 February 2005 02:15 pm, Andrew McNabb wrote:
> > On Sun, Feb 13, 2005 at 07:28:44PM -, Tom Clark wrote:
> > > Has anyone else experienced the following?
> > >
> > > 1. When watching a recording, as you approach the end (Final 15 
> > > seconds or so) playback becomes very jittery, almost 
> freezing during 
> > > the last few seconds before sending you back to the 
> "Watch Recordings" screen.
> >
> > I'm having the same problem.  It's not the most critical 
> problem ever, 
> > but it can be pretty annoying.  I've had it wait five or 
> ten seconds 
> > on a black screen, and just before you have a chance to hit 
> > ctrl-alt-backspace it returns to the program listing.
> >
> > I don't know how to troubleshoot it, though.
> 
> I reported something very similar to the myth-dev list under:
> [mythtv] 0.17 - mythfrontend freezing at end of recordings
> 
> does that sound familiar?
>  
> please try this out
> - hit esc while it's frozen - does it lock up?
> - hit 99 while it is frozen - does it segfault?
> 
> does the hard drive light ever go crazy while it is frozen 
> for the 5 or ten seconds before it goes back to the list of 
> recordings?
> 
> 
> do you see messages like these in the frontend logs?
> 
> - Waited 2 seconds for data to become available, waiting again...
> - Waited too long for decoder to pause
> 
> -- 
> Risto Treksler
> Elkhorn Lodge
> Banff, Alberta, Canada
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 

Just tried your suggestions and got the following results
hit esc while it's frozen - does it lock up? No
hit 99 while it is frozen - does it segfault? Yes

does the hard drive light ever go crazy while it is frozen 
for the 5 or ten seconds before it goes back to the list of 
recordings? No

do you see messages like these in the frontend logs?
- Waited 2 seconds for data to become available, waiting again...
- Waited too long for decoder to pause

I get the following:
2005-02-14 18:03:27.775 prebuffering pause
2005-02-14 18:03:30.466 prebuffering pause
2005-02-14 18:03:34.001 prebuffering pause
2005-02-14 18:03:37.034 prebuffering pause
2005-02-14 18:03:39.815 prebuffering pause
2005-02-14 18:03:40.047 Waited 2 seconds for data to become available,
waiting again...
2005-02-14 18:03:42.951 Waited 2 seconds for data to become available,
waiting again...
2005-02-14 18:03:44.079 Changing from WatchingPreRecorded to None
2005-02-14 18:03:44.178 Changing from None to None

Any help to anyone?

Regards,
Tom Clark
[EMAIL PROTECTED]

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

Re: Playlists (was: Re: [mythtv-users] 0.17)

[Joseph A. Caputo]

On Friday 11 February 2005 15:39, Brad Templeton wrote:
> Not that I don't think this is a fine ability to have when dumping to
> VHS tape, but the question that comes up in my mind is, why would you
> want to dump to VHS tape when blank DVDs are only about 30 cents?

Umm, how about because not everyone has a DVD burner, and exporting to 
(S)VCD is sometimes less desirable than VHS.

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

Re: [mythtv-users] 0.17 DVB scan fails ...

[Hamish Moffatt]

On Sun, Feb 13, 2005 at 06:01:17PM +1100, Chris Edwards wrote:
> Hamish Moffatt wrote:
> >In my scans in Melbourne, none of the networks give any network
> >information for any other network. All of VHF stations list only their
> >own frequency for Melbourne, except SBS which lists half a dozen
> >different frequencies.
> >
> >So I had to manually enter 5 multiplexes.
> 
> Yup, that's exactly what I had to do (I'm in Melbourne too). What's the 
> deal with those SBS ones? I'm guessing they're probably the other 
> stations in Sydney or something, judging from the way SBS usually 

Yup I think they're for interstate.

> operates! Also, all the SBS channels seem to add themselves two or three 
> times, with the same channel number each time. It's quite annoying.

I didn't notice that. I was annoyed by Channel Ten though which has
defined 4-5 channels which are identical, with numbers such as 1.
The main SBS channel came up as 3. I spent some time in the editor
straightening this out.

Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 backend segfaults

[Antti Siiskonen]

On Sun, Feb 13, 2005 at 04:07:48PM -0500, Chris Pinkham wrote:
> "bt" isn't enough because it doesn't show all threads.  Look at the
> HOWTO for necessary steps to get a good backtrace.

Ok, new quite lengthy trace attached. While I have basic understanding 
of gdb and debugging I can't make heads or tails of this, I hope someone 
can. If you need more information please just ask, I'll do what I can. 

I did "gdb mythbackend" followed by "run -l 
/usr/local/mythtv/var/log/myth.log -p /usr/local/mythtv/var/run/myth.pid 
-v all", the backend started, ran for about 5 minutes or so and then 
died.


-- 
//Antti
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 11276 (LWP 12514)]
0x4192d642 in chunk_alloc (ar_ptr=0x419dfca0, nb=48) at malloc.c:2878
2878malloc.c: No such file or directory.
in malloc.c
(gdb) thread apply all bt full

Thread 19 (Thread 17426 (LWP 12520)):
#0  0x418df9b6 in __sigsuspend (set=0xbd7ff9ac)
at ../sysdeps/unix/sysv/linux/sigsuspend.c:45
set = (sigset_t *) 0x419e17d0
resultvar = 3179280812
#1  0x4179ed45 in __pthread_wait_for_restart_signal (self=0xbd7ffc00)
at pthread.c:978
mask = {__val = {0, 0, 4294967295, 1098518462, 4294967295, 
4294967295, 
4294967295, 4294967295, 4294967295, 4294967295, 4294967295, 
1098517354, 
4294967295, 4294967295, 4294967295, 1098518462, 0, 1103161796, 0, 
1098518462, 0, 0, 0, 1098559228, 3179281408, 1103161780, 3179280964, 
1098559228, 1103161780, 0, 3179280964, 1098502864}}
#2  0x4179aee4 in pthread_cond_wait (cond=0x41c0e9d8, mutex=0x41c0e9b4)
at restart.h:34
cond = (pthread_cond_t *) 0x0
self = 0xbd7ffc00
extr = {pu_object = 0x41c0e9d8, 
  pu_extricate_func = 0x4179b4b4 }
already_canceled = 0
spurious_wakeup_count = 0
self = 0xbd7ffc00
extr = {pu_object = 0x41c0e9d8, 
  pu_extricate_func = 0x4179b4b4 }
already_canceled = 0
#3  0x413aa967 in QWaitCondition::wait(QMutex*, unsigned long) (
this=0x41c0e978, mutex=0x41c0e970, time=4294967295)
at tools/qwaitcondition_unix.cpp:303
ret = 134643203
#4  0x0808bd93 in ProcessRequestThread::run() (this=0x41c0e960)
at mainserver.cpp:69
No locals.
#5  0x40fd8624 in QThreadInstance::start(void*) (_arg=0x41c0e98c)
at kernel/qthread_unix.cpp:119
_buffer = {__routine = 0x40fd8642 
, 
  __arg = 0x41c0e988, __canceltype = 0, __prev = 0x0}
arg = (void **) 0x41c0e98c
#6  0x4179bf87 in pthread_start_thread (arg=0xbd7ffc00) at manager.c:284
self = 0xbd7ffc00
request = {req_thread = 0x0, req_kind = REQ_CREATE, req_args = {
create = {attr = 0x0, fn = 0, arg = 0x0, mask = {__val = {0, 0, 0, 
0, 0, 
  0, 0, 0, 0, 0, 1098559228, 1, 1098532416, 3179281380, 
1098516827, 
  3179281408, 0, 0, 1098517118, 0, 0, 0, 12, 1, 0, 0, 
1098559228, 
  3179281408, 3179281700, 3179281396, 1098501145, 1098532416}}}, 
free = {thread_id = 0}, exit = {code = 0}, post = 0x0}}
outcome = (void *) 0xfffc

Thread 18 (Thread 16401 (LWP 12519)):
#0  0x418df9b6 in __sigsuspend (set=0xbd9ff9ac)
at ../sysdeps/unix/sysv/linux/sigsuspend.c:45
set = (sigset_t *) 0x419e17d0
resultvar = 3181377964
#1  0x4179ed45 in __pthread_wait_for_restart_signal (self=0xbd9ffc00)
at pthread.c:978
mask = {__val = {0, 0, 4294967295, 1098518462,
4294967295 , 1098518462, 4294967295, 1103161636, 
0, 0,
0, 0, 0, 0, 0, 0, 0, 1098559228, 1103161620, 0, 3181378116, 
1098502864}}
#2  0x4179aee4 in pthread_cond_wait (cond=0x41c0e750, mutex=0x41c0e914)
at restart.h:34
cond = (pthread_cond_t *) 0x0
self = 0xbd9ffc00
extr = {pu_object = 0x41c0e750,
  pu_extricate_func = 0x4179b4b4 }
already_canceled = 0
spurious_wakeup_count = 0
self = 0xbd9ffc00
extr = {pu_object = 0x41c0e750,
  pu_extricate_func = 0x4179b4b4 }
already_canceled = 0
#3  0x413aa967 in QWaitCondition::wait(QMutex*, unsigned long) (
this=0x41c0e8d8, mutex=0x41c0e8d0, time=4294967295)
at tools/qwaitcondition_unix.cpp:303
ret = 1094360488
#4  0x0808bd93 in ProcessRequestThread::run() (this=0x41c0e8c0)
at mainserver.cpp:69
No locals.
#5  0x40fd8624 in QThreadInstance::start(void*) (_arg=0x41c0e8ec)
at kernel/qthread_unix.cpp:119
_buffer = {__routine = 0x40fd8642 
,
  __arg = 0x41c0e8e8, __canceltype = 0, __prev = 0x0}
arg = (void **) 0x41c0e8ec
#6  0x4179bf87 in pthread_start_thread (arg=0xbd9ffc00) at manager.c:284
self = 0xbd9ffc00
request = {req_thread = 0x0, req_kind = REQ_CREATE, req_args = {
create = {attr = 0x0, fn = 0, arg = 0x0, mask = {__val = {0, 0, 0, 
0, 0,
  0, 0, 0, 0, 0, 1098559228, 1, 1098532400, 3181378532, 
1098516827,
  3181378560, 0, 0, 1098517118, 0, 0, 0, 12, 1, 0, 0, 
1098559228,
  3181378560, 3181378852, 3181378548, 1098501145, 1098532400}}},
free = {thread_id = 0}, exit

Re: [mythtv-users] 0.17 observations

[Risto Treksler]

On Sunday 13 February 2005 02:15 pm, Andrew McNabb wrote:
> On Sun, Feb 13, 2005 at 07:28:44PM -, Tom Clark wrote:
> > Has anyone else experienced the following?
> >
> > 1. When watching a recording, as you approach the end (Final 15 seconds
> > or so) playback becomes very jittery, almost freezing during the last few
> > seconds before sending you back to the "Watch Recordings" screen.
>
> I'm having the same problem.  It's not the most critical problem ever,
> but it can be pretty annoying.  I've had it wait five or ten seconds on
> a black screen, and just before you have a chance to hit
> ctrl-alt-backspace it returns to the program listing.
>
> I don't know how to troubleshoot it, though.

I reported something very similar to the myth-dev list under:
[mythtv] 0.17 - mythfrontend freezing at end of recordings

does that sound familiar?
 
please try this out
- hit esc while it's frozen - does it lock up?
- hit 99 while it is frozen - does it segfault?

does the hard drive light ever go crazy while it is frozen for the 5 or ten 
seconds before it goes back to the list of recordings?


do you see messages like these in the frontend logs?

- Waited 2 seconds for data to become available, waiting again...
- Waited too long for decoder to pause

-- 
Risto Treksler
Elkhorn Lodge
Banff, Alberta, Canada
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 observations

[MacNean C. Tyrrell]

Andrew McNabb wrote:
On Sun, Feb 13, 2005 at 07:28:44PM -, Tom Clark wrote:
 

Has anyone else experienced the following?
1. When watching a recording, as you approach the end (Final 15 seconds or
so) playback becomes very jittery, almost freezing during the last few
seconds before sending you back to the "Watch Recordings" screen.
   

I'm having the same problem.  It's not the most critical problem ever,
but it can be pretty annoying.  I've had it wait five or ten seconds on
a black screen, and just before you have a chance to hit
ctrl-alt-backspace it returns to the program listing.
I don't know how to troubleshoot it, though.
 


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

This does this to me for the last 3-5 seconds, almost like it reached 
the end, wants to go back, plays another second, repeat process either 
1-3 times before finally kicking back to watch recordings screen, all in 
all the 3-5 seconds takes about 15 seconds total, not too bad but no 
other version did that with me.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 upgrade -> backend crashes

[Brad Benson]

On Sun, 13 Feb 2005 16:00:59 -0500 (EST), Chris Pinkham
<[EMAIL PROTECTED]> wrote:
> > > Interestingly, here's a snippet from mythbackend.log from immediately
> > > after the above select statement was run:
> > > 2005-02-12 20:34:52.770 Starting Commercial Flagging for "Everybody
> > > Loves Raymond" recorded from channel 1031 at Fri Feb 11 19:30:00 2005.
> > > 2005-02-12 20:34:52.910 commflag: Commercial Flagging Starting
> > > QTime::setHMS Invalid time 28:12:01.000
> > > QDate::setYMD: Invalid date 2935-93-02
> > > 2005-02-12 20:37:49.989 MainServer::HandleAnnounce Playback
> 
> These "Invalid time/date" messages are the reason that you have multiple
> jobs firing off I believe.  I'm thinking that because of those, the
> jobqueue field probably isn't getting updated to say that the commercial
> flagging successfully started, so the jobqueue is firing off another
> copy.
> 
> Are you sure the mythcommflag  you are running is the latest version?  Can
> you do a "make distclean" and remake to see if it was perhaps compiled against
> an old library version or something.  The command line in your 'ps' output
> is correct, so I don't see why the flagger would be getting errors (whether
> the error is being generated in the flagger, jobqueue, or programinfo code).
> 
> > > Accidentally replied off-list so I'm forwarding this message to the
> > > list this time.
> 
> This was my fault, your Reply-To is set to your email address and my email
> program replied to you originally instead of to the list.
> 
> --
> 
> Chris
> 
> 
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 
> 
> 

Well, I think I've figured out and fixed the problem.  It appears that
when I removed the 0.16 rpms I forgot to remove libmyth.  I'm betting
that there were some old pieces of 0.16 lying around that were causing
those problems.  I've now gone through and removed all old rpms as
well as manually removing all the pieces I installed from source.  I
then reinstalled 0.17 using Axel's new rpms and everything seems to be
running along just perfectly.  It's been up for about 4 hours now with
no crashes, no out-of-control commflagging and the sluggishness I was
seeing on the menus and during playback is now gone.  I'm pretty
confident that everything is good to go now, but if something else
comes up I'll post back to this thread again.

Thanks for your help Chris!  Too bad the problem was that I'm an idiot. ;)


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

Re: [mythtv-users] 0.17 observations

[Andrew McNabb]

On Sun, Feb 13, 2005 at 07:28:44PM -, Tom Clark wrote:
> Has anyone else experienced the following?
>  
> 1. When watching a recording, as you approach the end (Final 15 seconds or
> so) playback becomes very jittery, almost freezing during the last few
> seconds before sending you back to the "Watch Recordings" screen.

I'm having the same problem.  It's not the most critical problem ever,
but it can be pretty annoying.  I've had it wait five or ten seconds on
a black screen, and just before you have a chance to hit
ctrl-alt-backspace it returns to the program listing.

I don't know how to troubleshoot it, though.

-- 
Andrew McNabb
http://www.mcnabbs.org/andrew/
PGP Fingerprint: 8A17 B57C 6879 1863 DE55  8012 AB4D 6098 8826 6868


pgp3rEvWF5jii.pgp
Description: PGP signature
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 observations

[Chris Pinkham]

> BTW, I also found in order to run the commercial flag jobs over (once I 
> fixed the path), I could set the status in jobqueue to 1.  Here is the 
> sql command I used:
> 
> update jobqueue set status = 1 where status = 304;

You could also just go to the INFO popup menu on the Watch Recordings
screen and tell it to rerun commercial flagging from there.  The old jobs
in the queue get cleaned out periodically, so your command won't work if
the recording is older.

-- 

Chris

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

Re: [mythtv-users] 0.17 backend segfaults

[Chris Pinkham]

> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 12301 (LWP 16440)]
> 0x in ?? ()
> Current language:  auto; currently c
> (gdb) bt
> #0  0x in ?? ()
> #1  0x41240392 in QGList::append(void*) () from 
> /usr/local/qt/lib/libqt-mt.so.3

"bt" isn't enough because it doesn't show all threads.  Look at the
HOWTO for necessary steps to get a good backtrace.

-- 

Chris

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

Re: [mythtv-users] 0.17 upgrade -> backend crashes

[Chris Pinkham]

> > Interestingly, here's a snippet from mythbackend.log from immediately
> > after the above select statement was run:
> > 2005-02-12 20:34:52.770 Starting Commercial Flagging for "Everybody
> > Loves Raymond" recorded from channel 1031 at Fri Feb 11 19:30:00 2005.
> > 2005-02-12 20:34:52.910 commflag: Commercial Flagging Starting
> > QTime::setHMS Invalid time 28:12:01.000
> > QDate::setYMD: Invalid date 2935-93-02
> > 2005-02-12 20:37:49.989 MainServer::HandleAnnounce Playback

These "Invalid time/date" messages are the reason that you have multiple
jobs firing off I believe.  I'm thinking that because of those, the
jobqueue field probably isn't getting updated to say that the commercial
flagging successfully started, so the jobqueue is firing off another
copy.

Are you sure the mythcommflag  you are running is the latest version?  Can
you do a "make distclean" and remake to see if it was perhaps compiled against
an old library version or something.  The command line in your 'ps' output
is correct, so I don't see why the flagger would be getting errors (whether
the error is being generated in the flagger, jobqueue, or programinfo code).
 
> > Accidentally replied off-list so I'm forwarding this message to the
> > list this time.

This was my fault, your Reply-To is set to your email address and my email
program replied to you originally instead of to the list.

-- 

Chris

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

Re: [mythtv-users] 0.17 LCD backlight?

[Cory Papenfuss]

Is the backlight never turned on by myth? It should at least be turned
on when the frontend is started. In the settings menu, I have all
options tagged except for 'always on'. Instead I have the 'pop-up time'
set to 60 seconds.
I am running lcdproc 0.4.5 and mythtv cvs from about 2 weeks ago.
	That's correct... it's never turned on by myth.  I'll check my 
lcdproc version when I get home later.

-Cory
*
* Cory Papenfuss*
* Electrical Engineering candidate Ph.D. graduate student   *
* Virginia Polytechnic Institute and State University   *
*
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 LCD backlight?

[Leo Weppelman]

On Sun, Feb 13, 2005 at 12:47:22PM -0500, Cory Papenfuss wrote:
>   Hey all... I just rolled the new tarballs onto my machine at home, 
> but the most important feature in the new release doesn't work... the LCD 
> backlight!  ;)
> 
>   The backlight works and is toggled when I run 'lcdproc M' to a 
> running LCDd daemon.  The mythfrontend displays the text on the LCD as I 
> scroll through the menu, but no backlight is on.
> 
>   Is there anything weird that needs to be selected at compile time? 
> The Setup screen says, "Run backlight always" or whatever... it just 
> doesn't.

This is weird... It works for me.
Is the backlight never turned on by myth? It should at least be turned
on when the frontend is started. In the settings menu, I have all
options tagged except for 'always on'. Instead I have the 'pop-up time'
set to 60 seconds.
I am running lcdproc 0.4.5 and mythtv cvs from about 2 weeks ago.

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

Re: [mythtv-users] 0.17 observations

[Brad Templeton]

On Sun, Feb 13, 2005 at 03:04:38PM -0500, David George wrote:
> On 02/13/2005 02:28 PM, Tom Clark wrote:
> Amazingly this just started happening to me a week or two ago.  I have 
> always run from /usr/local, and I hadn't changed anything in my config.  
> So I was at a loss as to why it happened.  Anyway, I am running FC2 and 
> the init scripts set a path when they are run.  I had to fix this by 
> adding the following before the start() function in /etc/init.d/mythbackend:
> 
> if ! strstr "$PATH" "/usr/local/bin" ; then
>  PATH=$PATH:/usr/local/bin
> fi
> 

yes, this works, though in theory you might want to keep your local
config changes in /etc/sysconfig/myththbackend which is where they
properly go.

Or write a patch for mythtv, since it knows the "prefix" it gets
installed to, to add PREFIX/bin to the path it tries when executing
commands, so users don't have to do any extra config.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 observations

[Cory Papenfuss]

	A little OT, but has anyone who's made 0.17 work notice that 
watching with the time shrink factor makes you want to talk like an 
auctioneer?  :)

	Very interesting feature... watching a 1-hour show without 
commercials at 1.3x lets you watch it in 1/2 hour (plus the auctioneer 
psyche).

-Cory
*
* Cory Papenfuss*
* Electrical Engineering candidate Ph.D. graduate student   *
* Virginia Polytechnic Institute and State University   *
*
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 observations

[David George]

On 02/13/2005 02:28 PM, Tom Clark wrote:
1. When watching a recording, as you approach the end (Final 15 seconds or
so) playback becomes very jittery, almost freezing during the last few
seconds before sending you back to the "Watch Recordings" screen.
 

Haven't had this problem.
2. When watching a recording, having it chuck you out in the middle with the
"You have finished watching" when you haven't actually reached the end.
 

Haven't had this problem either.
3. Queued commercial flagging jobs failing with message "ERROR: Unable to
find mythcommflag." when mythcommflag is present under /usr/local/bin/ with
the rest of the binaries.
 

Amazingly this just started happening to me a week or two ago.  I have 
always run from /usr/local, and I hadn't changed anything in my config.  
So I was at a loss as to why it happened.  Anyway, I am running FC2 and 
the init scripts set a path when they are run.  I had to fix this by 
adding the following before the start() function in /etc/init.d/mythbackend:

if ! strstr "$PATH" "/usr/local/bin" ; then
 PATH=$PATH:/usr/local/bin
fi
After making this change, I stopped and restarted the backend so it 
would have the new path.  This goes for slave backends also.

BTW, I also found in order to run the commercial flag jobs over (once I 
fixed the path), I could set the status in jobqueue to 1.  Here is the 
sql command I used:

update jobqueue set status = 1 where status = 304;
HTH,
David
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

RE: [mythtv-users] 0.17 observations

[Tom Clark]

>Maybe.  I had some problems with similar issues related to differing
prefixes, etc.  Couldn't hurt to do it to make sure.

>Kevin

OK, thanks for the tip, I'll recompile tomorrow and report back.

Regards,
Tom Clark
[EMAIL PROTECTED]

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

Re: [mythtv-users] 0.17 observations

[Kevin Kuphal]

Tom Clark wrote:
Always been under there. I built from source, but I didn't do a distclean,
could this omission be the culprit?
Maybe.  I had some problems with similar issues related to differing 
prefixes, etc.  Couldn't hurt to do it to make sure.

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

RE: [mythtv-users] 0.17 observations

[Tom Clark]

>Have you always had your files in /usr/local/bin? Did you build from source
and do a make distclean on all the folders and modules before installing or
>is this a packaged install?

>Kevin

Always been under there. I built from source, but I didn't do a distclean,
could this omission be the culprit?

Regards,
Tom Clark
[EMAIL PROTECTED]


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

Re: [mythtv-users] 0.17 observations

[Kevin Kuphal]

Tom Clark wrote:
What is the output if you run mythcommflag manually as mythtv user?
   

 

Kevin
   

What I assume to be normal output, I've never run it manually before.
[EMAIL PROTECTED]:~$ mythcommflag 
2005-02-13 19:47:23.988 mythcommflag version: 0.17.20050130-1 www.mythtv.org
2005-02-13 19:47:23.989 Enabled verbose msgs :important

MythTV Commercial Flagger, started at Sun Feb 13 19:47:23 2005
Flagging commercial breaks for:
ALL Un-flagged programs
ChanID  Start Time  Title  Breaks
10012004122820  Second World War in Colour
29%/145fps
I've probably made a config error somewhere along the line, but it was
working fine under 0.16.
 

Have you always had your files in /usr/local/bin?  Did you build from 
source and do a make distclean on all the folders and modules before 
installing or is this a packaged install?

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

Re: [mythtv-users] 0.17 backend segfaults

[Tim Berger]

I'm still using cvs.  I also saw regular segfaults every few days with
an smp kernel.  After swtiching to a non-smp kernel, it's solid.

Backend with fc3, 2-PVR250's.

On Sun, 13 Feb 2005 16:07:30 +0200, Antti Siiskonen
<[EMAIL PROTECTED]> wrote:
> Hello,
> 
> after upgrading from 0.16 to 0.17 I'm seeing backend
> segfaults after ~5 minutes of running. Gdb trace is attached.
> 
> I'm running backend on a SMP system with two dvb-c cards and the
> frontend on xbox. qt-3.3.2, gcc-3.4.3 and mysql-3.23.58.
> 
> --
> //Antti
> 
> 
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 
> 
> 
> 


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

RE: [mythtv-users] 0.17 observations

[Tom Clark]

>What is the output if you run mythcommflag manually as mythtv user?

>Kevin

What I assume to be normal output, I've never run it manually before.

[EMAIL PROTECTED]:~$ mythcommflag 
2005-02-13 19:47:23.988 mythcommflag version: 0.17.20050130-1 www.mythtv.org
2005-02-13 19:47:23.989 Enabled verbose msgs :important

MythTV Commercial Flagger, started at Sun Feb 13 19:47:23 2005

Flagging commercial breaks for:
ALL Un-flagged programs
ChanID  Start Time  Title  Breaks
10012004122820  Second World War in Colour
29%/145fps


I've probably made a config error somewhere along the line, but it was
working fine under 0.16.

Regards,
Tom Clark
[EMAIL PROTECTED]


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

Re: [mythtv-users] 0.17 observations

[Kevin Kuphal]

Tom Clark wrote:
Yep!
[EMAIL PROTECTED]:~$ echo $PATH
/usr/local/bin:/bin:/usr/bin
 

What is the output if you run mythcommflag manually as mythtv user?
Kevin
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

RE: [mythtv-users] 0.17 observations

[Tom Clark]

Yep!
[EMAIL PROTECTED]:~$ echo $PATH
/usr/local/bin:/bin:/usr/bin

Regards,
Tom Clark
[EMAIL PROTECTED]
 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin Kuphal
Sent: 13 February 2005 19:37
To: Discussion about mythtv
Subject: Re: [mythtv-users] 0.17 observations

Tom Clark wrote:

>3. Queued commercial flagging jobs failing with message "ERROR: Unable 
>to find mythcommflag." when mythcommflag is present under 
>/usr/local/bin/ with the rest of the binaries.
>  
>
Is /usr/local/bin in your path? Just because they're phsyically in the same
folder doesn't mean that it can be found when spawning the commflag thread.
Test it by trying to run "mythcommflag" logged in as your mythtv user from a
directory other than /usr/local/bin

Kevin
___
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] 0.17 observations

[Kevin Kuphal]

Tom Clark wrote:
3. Queued commercial flagging jobs failing with message "ERROR: Unable to
find mythcommflag." when mythcommflag is present under /usr/local/bin/ with
the rest of the binaries.
 

Is /usr/local/bin in your path? Just because they're phsyically in the 
same folder doesn't mean that it can be found when spawning the commflag 
thread.  Test it by trying to run "mythcommflag" logged in as your 
mythtv user from a directory other than /usr/local/bin

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

Re: [mythtv-users] 0.17 Mythphone segfaults frontend

[Mike Choy]

OK
This looks like a prob with the 
ATRPM's
Axel is rebuilding these as of 
13th/02/05
 
Cheers
 

  - Original Message - 
  From: 
  Mike Choy 

  To: mythtv-users@mythtv.org 
  Sent: Sunday, February 13, 2005 3:21 
  PM
  Subject: [mythtv-users] 0.17 Mythphone 
  segfaults frontend
  
  This seems to be a problem
  used synaptic to remove mythphone.
  Frontend now comes up
   
  Mike Choy
   
  
  

  ___mythtv-users mailing 
  listmythtv-users@mythtv.orghttp://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] 0.17 DVB-T Mythtvsetup hangs

[Mike Choy]

Cheers Team

That looks like solution. Alt-Tab (Works in KDE also)  and I can see the
terminal asking for input.
When I answer then goes back to setup menu.

There was an option not to use the tv-grab_rt , cause I've been using
the guide data being broadcast over the the DVB stream. I assume the guide
data being populated is therefore
coming from the RT website ?

Mike Choy

- Original Message - 
From: "Andy Whitworth" <[EMAIL PROTECTED]>
To: "Discussion about mythtv" 
Sent: Sunday, February 13, 2005 4:23 PM
Subject: Re: [mythtv-users] 0.17 DVB-T Mythtvsetup hangs


> On Sun, 13 Feb 2005 16:11:04 -, Mike Choy <[EMAIL PROTECTED]> wrote:
> > Lukas
> >
> > How do I see this when Mythtvsetup is in fullscreen?
> >
> > Mike Choy
> >
>
> ALT-Tab in Gnome.(a la Windows)
>






___
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] 0.17 DVB-T Mythtvsetup hangs

[Andy Whitworth]

On Sun, 13 Feb 2005 16:11:04 -, Mike Choy <[EMAIL PROTECTED]> wrote:
> Lukas
> 
> How do I see this when Mythtvsetup is in fullscreen?
> 
> Mike Choy
> 

ALT-Tab in Gnome.(a la Windows)
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 DVB-T Mythtvsetup hangs

[Mike Choy]

Lukas

How do I see this when Mythtvsetup is in fullscreen?

Mike Choy

- Original Message - 
From: "Lukas Kasprowicz" <[EMAIL PROTECTED]>
To: "Discussion about mythtv" 
Sent: Sunday, February 13, 2005 3:31 PM
Subject: Re: [mythtv-users] 0.17 DVB-T Mythtvsetup hangs


> Hi Mike,
>
> Have you checked, if the tv_grab_uk_* is waiting for interaction on the
> console, from where you startet the mythsetup?
>
> If you used the tv_grab_uk_* before it should ask, for overwriting the
> file
> ~/.xmltv/tv_grab_uk_*.conf
>
> greets Lukas
>
>
> On Sun, 2005-02-13 at 15:11 +, Mike Choy wrote:
> > Hi
> >
> > on clean install of 0.17 from atrpm.
> > DVB-T in the UK. This system worked fine in 0.16
> > Dropped the old mythconverge database so i'm starting fresh.
> > I wanted to see how the new DVB Scan function works.
> >
> > Mythtvsetup goes fine until I get to the Video Souce Setup.
> > I type in "Freeview"
> > XMLTV listing grabber is =Unite kingdom(alternative)
> > Channel frequency table =default
> > Hit "Finish"
> > System then hangs with a 50% horizontal bar.
> >
> > Anyone else see this.
> >
> > Mike Choy
> >
> > ___
> > 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] 0.17 and DVB woes unable to complete scan

[Andy Whitworth]

On Sun, 13 Feb 2005 10:34:24 -, mail.com <[EMAIL PROTECTED]> wrote:
> Alex
> 
> I'm having problems with mythtv setup just after the input connections page
> when I come out of this it locks up with a 50% bar on the screen.
> 
> Can you post the steps you went through to get your UK DVB -T under 0.17
> working.
> 
> Mike Choy
> 

Mike,

When this happens, check the window you're running the frontend from,
you might find that it''s sitting there asking you to confirm
something about the uk_rt listings grabber!  I get
this whenever I go into input connections, I just flip to the command
window, press enter
and off you go again.

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

Re: [mythtv-users] 0.17 DVB-T Mythtvsetup hangs

[Lukas Kasprowicz]

Hi Mike,

Have you checked, if the tv_grab_uk_* is waiting for interaction on the
console, from where you startet the mythsetup?

If you used the tv_grab_uk_* before it should ask, for overwriting the
file
~/.xmltv/tv_grab_uk_*.conf

greets Lukas


On Sun, 2005-02-13 at 15:11 +, Mike Choy wrote:
> Hi
>  
> on clean install of 0.17 from atrpm.
> DVB-T in the UK. This system worked fine in 0.16
> Dropped the old mythconverge database so i'm starting fresh.
> I wanted to see how the new DVB Scan function works. 
>  
> Mythtvsetup goes fine until I get to the Video Souce Setup.
> I type in "Freeview" 
> XMLTV listing grabber is =Unite kingdom(alternative)
> Channel frequency table =default
> Hit "Finish"
> System then hangs with a 50% horizontal bar.
>  
> Anyone else see this.
>  
> Mike Choy
>  
> ___
> 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] 0.17 DVB-T Mythtvsetup hangs-work around

[Mike Choy]

Quick update.
 
I "control alt del" the hung session. came back to 
the Fedora core 3 log in screen.
Logged back in, ran MythTV setup. TheVideo source 
seems to be there, but did
not hit the finish key. 
Just escaped out back to the main options 
screen.
Then set up the video input. 
Went to channels setup and did DVB scan. 

Input 50580 for the Frequency
setup some of the parameters for BBC1  using 
info from previous(0.16) channels.conf
file. (i'm in the Crystal Palace transmitter 
area)
Systems did a full scan loaded, and live TV now 
streaming into the house.
 
Mike Choy
 

  - Original Message - 
  From: 
  Mike Choy 

  To: mythtv-users@mythtv.org 
  Sent: Sunday, February 13, 2005 3:11 
  PM
  Subject: [mythtv-users] 0.17 DVB-T 
  Mythtvsetup hangs
  
  Hi
   
  on clean install of 0.17 from atrpm.
  DVB-T in the UK. This system worked fine in 
  0.16
  Dropped the old mythconverge database so i'm 
  starting fresh.
  I wanted to see how the new DVB Scan function 
  works. 
   
  Mythtvsetup goes fine until I get to the Video 
  Souce Setup.
  I type in "Freeview" 
  XMLTV listing grabber is =Unite 
  kingdom(alternative)
  Channel frequency table =default
  Hit "Finish"
  System then hangs with a 50% horizontal 
  bar.
   
  Anyone else see this.
   
  Mike Choy
   
  
  

  ___mythtv-users mailing 
  listmythtv-users@mythtv.orghttp://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] 0.17 and DVB woes unable to complete scan

[mail.com]

Alex

I'm having problems with mythtv setup just after the input connections page
when I come out of this it locks up with a 50% bar on the screen.

Can you post the steps you went through to get your UK DVB -T under 0.17
working.

Mike Choy

- Original Message - 
From: "Alex Hazlewoood" <[EMAIL PROTECTED]>
To: 
Sent: Sunday, February 13, 2005 1:59 AM
Subject: Re: [mythtv-users] 0.17 and DVB woes unable to complete scan


> Andy Whitworth wrote:
>
> >>Enter the frequency you have in channels.conf for BBC1 + all the other
> >>parameters!
> >>
> >>I just tried entering the frequency field for my transmitter (Crystal
> >>Palace) and the
> >>card wouldn't lock on.  Had to specify the other tuning fields also,
> >>works fine then!
> >>
> >>Andy.
> >>
> >>
> >>
> Yep that worked,  Thanks for that pointer
>
> Alex
>
>
> ___
> 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] 0.17 mythfrontend gentoo ebuild

[Paul Wheeler]

That has worked thanks lots.

Paul


On Sat, 12 Feb 2005 12:16:06 -0700, David Madsen <[EMAIL PROTECTED]> wrote:
> I had the same problem.  I debugged it, and the problem is that there
> is no ChangeLog file in the tarball and the gentoo ebuild is expecting
> there to be one.  You can fix this temporarily (until you sync your
> portage tree) by editing
> 
> /usr/portage/media-tv/mythtv-0.17.ebuild
> 
> and changing this line
> 
>  myth_src_install || die "failed to install"
> 
> to just
> 
>  myth_src_install
> 
> --Dave Madsen
> 
> On Sat, 12 Feb 2005 10:30:37 -0500, Tom Dombrosky <[EMAIL PROTECTED]> wrote:
> > I think I see what you're talking about now.  I'm getting an error
> > with no output after it installs all the i18n stuff.
> >
> > Tom
> >
> >
> > ___
> > 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] 0.17 upgrade -> backend crashes

[Brad Benson]

rently allocated


Anyone got any ideas what might be going on?  If you need more info
please let me know.

Thanks,
Brad





On Sat, 12 Feb 2005 21:28:35 -0500, Brad Benson <[EMAIL PROTECTED]> wrote:
> On Sat, 12 Feb 2005 21:24:30 -0500, Brad Benson <[EMAIL PROTECTED]> wrote:
> > -- Forwarded message ------
> > From: Brad Benson <[EMAIL PROTECTED]>
> > Date: Sat, 12 Feb 2005 20:49:37 -0500
> > Subject: Re: [mythtv-users] 0.17 upgrade -> backend crashes
> > To: Chris Pinkham <[EMAIL PROTECTED]>
> >
> > On Sat, 12 Feb 2005 20:03:46 -0500 (EST), Chris Pinkham
> > <[EMAIL PROTECTED]> wrote:
> > > > I upgraded from 0.16 to 0.17 late Thursday night/early Friday morning.
> > > >  Ever since then I've been seeing some strange behavior from the box.
> > > What's in your jobqueue table?  You can also limit the number of jobs
> > > that myth will run at one time, the default is 1 I believe, so I'm
> > > not sure why it's running multiple jobs unless you bumped up the
> > > JobQueueMaxSimultaneousJobs setting.
> > >
> >
> > When I run setup it tells me that I already have the backend limited
> > to 1 simultaneous job, CPU usage is set to Medium, Job Queue check
> > frequency is set to 60 seconds, Run Jobs only on original recording
> > host is unchecked, and I have allowed this backend to run any jobs in
> > the queue (commflag, user 1, user 2, user 3 and user 4).
> >
> > > Can you do a "select * from jobqueue order by id;" and post the
> > > output?  This should indicate if there are multiple entries in the
> > > table for a single show.  The code should prevent that though.
> > >
> >
> > Here's the output from "select * from jobqueue order by id;":
> > +++-+-+--+--+---++-++--+-+
> > | id | chanid | starttime   | inserttime  | type |
> > cmds | flags | status | statustime  | hostname   | args |
> > comment |
> > +++-+-+--+--+---++-++--+-+
> > |  1 |   1030 | 2005-02-11 15:59:00 | 2005-02-11 17:03:00 |2 |
> > 0 | 0 |272 | 2005-02-11 18:43:47 | bivomaster |  |
> > Finished, 0 break(s) found. |
> > |  3 |   1052 | 2005-02-11 22:58:00 | 2005-02-11 23:32:00 |2 |
> > 0 | 0 |  1 | 2005-02-12 20:23:05 | bivomaster |  |
> > |
> > |  4 |   1009 | 2005-02-11 20:53:00 | 2005-02-12 16:04:35 |2 |
> > 4 | 0 |272 | 2005-02-12 16:07:42 | bivomaster |  |
> > Finished, 0 break(s) found. |
> > |  5 |   1024 | 2005-02-11 18:28:00 | 2005-02-12 16:06:16 |2 |
> > 0 | 0 |272 | 2005-02-12 20:40:23 | bivomaster |  | 60%
> > Completed @ 60 fps.
> >  |
> > |  6 |   1031 | 2005-02-11 19:30:00 | 2005-02-12 16:06:21 |2 |
> > 0 | 0 |  4 | 2005-02-12 20:40:22 | bivomaster |  | 80%
> > Completed @ 60 fps. |
> > +++-+-+--+--+---++-++--+-+
> > 5 rows in set (0.00 sec)
> >
> > Interestingly, here's a snippet from mythbackend.log from immediately
> > after the above select statement was run:
> > 2005-02-12 20:34:52.770 Starting Commercial Flagging for "Everybody
> > Loves Raymond" recorded from channel 1031 at Fri Feb 11 19:30:00 2005.
> > 2005-02-12 20:34:52.910 commflag: Commercial Flagging Starting
> > QTime::setHMS Invalid time 28:12:01.000
> > QDate::setYMD: Invalid date 2935-93-02
> > 2005-02-12 20:37:49.989 MainServer::HandleAnnounce Playback
> > 2005-02-12 20:37:50.055 adding: bivomaster as a client (events: 0)
> > 2005-02-12 20:37:50.249 Reloading backend settings
> > 2005-02-12 20:37:50.370 MainServer::HandleAnnounce Playback
> > 2005-02-12 20:37:50.380 adding: bivomaster as a client (events: 1)
> > QTime::setHMS Invalid time 28:12:02.000
> > QDate::setYMD: Invalid date 2935-93-02
> > 2005-02-12 20:38:53.065 Starting Commercial Flagging for "Everybody
> > Loves Raymond" recorded from channel 1031 at Fri Feb 11 19:30:00 2005.
> > QTime::setHMS Invalid time 28:12:02.000
> > QDate::setYMD: Invalid date 2935-93-02
> > 2005-02-12 20:42:12.339 Waited 2 seconds for data to become available,
> > waiting again...
> > 2005-02-1

Re: [mythtv-users] 0.17 DVB scan fails ...

[Chris Edwards]

Hamish Moffatt wrote:
In my scans in Melbourne, none of the networks give any network
information for any other network. All of VHF stations list only their
own frequency for Melbourne, except SBS which lists half a dozen
different frequencies.
So I had to manually enter 5 multiplexes.
Yup, that's exactly what I had to do (I'm in Melbourne too). What's the 
deal with those SBS ones? I'm guessing they're probably the other 
stations in Sydney or something, judging from the way SBS usually 
operates! Also, all the SBS channels seem to add themselves two or three 
times, with the same channel number each time. It's quite annoying.

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

Re: [mythtv-users] 0.17 DVB scan fails ...

[Hamish Moffatt]

On Sat, Feb 12, 2005 at 09:23:24PM +1100, Rob Hillis wrote:
> Chris Edwards wrote:
> 
> >Not sure where you are, but make sure you set the bandwidth correctly. 
> >That's 7MHz if you're in Australia. I had to provide a frequency too. 
> >Actually, i had to provide all the frequencies, one by one.
> 
> You normally shouldn't need to do that if you did a "Full Transport 
> Scan" - the DVB code will check the stream for other network information 
> and watch those frequencies too.  (In my case, this resulted in too many 
> transports since I'm on a local UHF repeater and the network scan gave 
> me all the UHF frequencies in addition to the VHF ones)

In my scans in Melbourne, none of the networks give any network
information for any other network. All of VHF stations list only their
own frequency for Melbourne, except SBS which lists half a dozen
different frequencies.

So I had to manually enter 5 multiplexes.

Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 upgrade -> backend crashes

[Brad Benson]

On Sat, 12 Feb 2005 21:24:30 -0500, Brad Benson <[EMAIL PROTECTED]> wrote:
> -- Forwarded message --
> From: Brad Benson <[EMAIL PROTECTED]>
> Date: Sat, 12 Feb 2005 20:49:37 -0500
> Subject: Re: [mythtv-users] 0.17 upgrade -> backend crashes
> To: Chris Pinkham <[EMAIL PROTECTED]>
> 
> On Sat, 12 Feb 2005 20:03:46 -0500 (EST), Chris Pinkham
> <[EMAIL PROTECTED]> wrote:
> > > I upgraded from 0.16 to 0.17 late Thursday night/early Friday morning.
> > >  Ever since then I've been seeing some strange behavior from the box.
> > What's in your jobqueue table?  You can also limit the number of jobs
> > that myth will run at one time, the default is 1 I believe, so I'm
> > not sure why it's running multiple jobs unless you bumped up the
> > JobQueueMaxSimultaneousJobs setting.
> >
> 
> When I run setup it tells me that I already have the backend limited
> to 1 simultaneous job, CPU usage is set to Medium, Job Queue check
> frequency is set to 60 seconds, Run Jobs only on original recording
> host is unchecked, and I have allowed this backend to run any jobs in
> the queue (commflag, user 1, user 2, user 3 and user 4).
> 
> > Can you do a "select * from jobqueue order by id;" and post the
> > output?  This should indicate if there are multiple entries in the
> > table for a single show.  The code should prevent that though.
> >
> 
> Here's the output from "select * from jobqueue order by id;":
> +++-+-+--+--+---++-++--+-+
> | id | chanid | starttime   | inserttime  | type |
> cmds | flags | status | statustime  | hostname   | args |
> comment |
> +++-+-+--+--+---++-++--+-+
> |  1 |   1030 | 2005-02-11 15:59:00 | 2005-02-11 17:03:00 |2 |
> 0 | 0 |272 | 2005-02-11 18:43:47 | bivomaster |  |
> Finished, 0 break(s) found. |
> |  3 |   1052 | 2005-02-11 22:58:00 | 2005-02-11 23:32:00 |2 |
> 0 | 0 |  1 | 2005-02-12 20:23:05 | bivomaster |  |
> |
> |  4 |   1009 | 2005-02-11 20:53:00 | 2005-02-12 16:04:35 |2 |
> 4 | 0 |272 | 2005-02-12 16:07:42 | bivomaster |  |
> Finished, 0 break(s) found. |
> |  5 |   1024 | 2005-02-11 18:28:00 | 2005-02-12 16:06:16 |2 |
> 0 | 0 |272 | 2005-02-12 20:40:23 | bivomaster |  | 60%
> Completed @ 60 fps.
>  |
> |  6 |   1031 | 2005-02-11 19:30:00 | 2005-02-12 16:06:21 |2 |
> 0 | 0 |  4 | 2005-02-12 20:40:22 | bivomaster |  | 80%
> Completed @ 60 fps. |
> +++-+-+--+--+---++-++--+-+
> 5 rows in set (0.00 sec)
> 
> Interestingly, here's a snippet from mythbackend.log from immediately
> after the above select statement was run:
> 2005-02-12 20:34:52.770 Starting Commercial Flagging for "Everybody
> Loves Raymond" recorded from channel 1031 at Fri Feb 11 19:30:00 2005.
> 2005-02-12 20:34:52.910 commflag: Commercial Flagging Starting
> QTime::setHMS Invalid time 28:12:01.000
> QDate::setYMD: Invalid date 2935-93-02
> 2005-02-12 20:37:49.989 MainServer::HandleAnnounce Playback
> 2005-02-12 20:37:50.055 adding: bivomaster as a client (events: 0)
> 2005-02-12 20:37:50.249 Reloading backend settings
> 2005-02-12 20:37:50.370 MainServer::HandleAnnounce Playback
> 2005-02-12 20:37:50.380 adding: bivomaster as a client (events: 1)
> QTime::setHMS Invalid time 28:12:02.000
> QDate::setYMD: Invalid date 2935-93-02
> 2005-02-12 20:38:53.065 Starting Commercial Flagging for "Everybody
> Loves Raymond" recorded from channel 1031 at Fri Feb 11 19:30:00 2005.
> QTime::setHMS Invalid time 28:12:02.000
> QDate::setYMD: Invalid date 2935-93-02
> 2005-02-12 20:42:12.339 Waited 2 seconds for data to become available,
> waiting again...
> 2005-02-12 20:42:16.380 commflag: Last message repeated 1 times
> 2005-02-12 20:42:16.458 commflag: Commercial Flagging Finished
> 2005-02-12 20:42:16.631 Finished, 1 break(s) found.
> 
> There is definitely only a single jobqueue entry for the show with a
> start time of 02/11/2004:19:30:00, but the log clearly shows two
> separate instances of commercial flagging being run for that show.
> Here's another sample taken from the same log file:
> 
> 2005-02-12 20:42:53.525 Starting Commercial Flagging for "Best Week
> Ever" recor

Re: [mythtv-users] 0.17 and DVB woes unable to complete scan

[Alex Hazlewoood]

Andy Whitworth wrote:
Enter the frequency you have in channels.conf for BBC1 + all the other
parameters!
I just tried entering the frequency field for my transmitter (Crystal
Palace) and the
card wouldn't lock on.  Had to specify the other tuning fields also,
works fine then!
Andy.
   

Yep that worked,  Thanks for that pointer
Alex
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 and DVB woes unable to complete scan

[Andy Whitworth]

On Sat, 12 Feb 2005 23:11:40 +, Alex Hazlewoood <[EMAIL PROTECTED]> wrote:
> After upgrading to 0.17 fro 0.16 I am unable to get my channels back :-(
> 
> The auto scan does not complete and gets to 39% and then cycles through
> the unlock signal /  lock status but does not progress any further..
> Plus the channels that it is picking up are from another transmitter in
> my area[craigkelly] The aerial is not putting towards this so 90% of the
> picture is broken up
> 
> I am not sure if I understand this new DVB scan app, what should I be
> entering to generate the "full Scan" ?
> I entered the Freq of one of my old channels [0.16 data] 57000 Hz
> .. Should I be entering the data from the uk-blackhill.conf file or
> should I be leaving it blank?
> 
> I am using the Black Hill transmitter if anyone can help I can keep it
> installed otherwise it is downgrade time to 0.16 :-(
> 
> Thanks
> 
> Alex
> 

Enter the frequency you have in channels.conf for BBC1 + all the other
parameters!

I just tried entering the frequency field for my transmitter (Crystal
Palace) and the
card wouldn't lock on.  Had to specify the other tuning fields also,
works fine then!

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

Re: [mythtv-users] 0.17 mythfrontend gentoo ebuild

[David Madsen]

I had the same problem.  I debugged it, and the problem is that there
is no ChangeLog file in the tarball and the gentoo ebuild is expecting
there to be one.  You can fix this temporarily (until you sync your
portage tree) by editing

/usr/portage/media-tv/mythtv-0.17.ebuild 

and changing this line

 myth_src_install || die "failed to install" 

to just

 myth_src_install


--Dave Madsen

On Sat, 12 Feb 2005 10:30:37 -0500, Tom Dombrosky <[EMAIL PROTECTED]> wrote:
> I think I see what you're talking about now.  I'm getting an error
> with no output after it installs all the i18n stuff.
> 
> Tom
> 
> 
> ___
> 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: Subject: RE: [mythtv-users] 0.17 broke my DVB setup :(

[Taylor Jacob]

Quoting belcampo <[EMAIL PROTECTED]>:
> Shouldn't the upgrade at least keep existing channels working ? And that
> scanning only would add so called 'new' found channels?
> In a perfect world current system would work, but scanning in my case fails
> to
> detect BBC 2 England from Astra 28.2E, where dvbscan does.
> As far as I can see there is no way, other than changing the dbtables
> directly, to get BBC 2 added. Manual adding in setup of channels ain't
> possible anymore.

No the upgrade doesn't keep ANY of your previous channels.  They are all meant
to be re-scanned..

Can you send me a dvbsnoop dump of your SDT tables on the service in question? 
Also when scaning does BBC 2 actually show up in the list, but is rejected for 
some reason (I.E. Does it say "Skipping BBC 2 - Not a Television Service", or
something similar?

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

Re: [mythtv-users] 0.17 mythfrontend gentoo ebuild

[Tom Dombrosky]

I think I see what you're talking about now.  I'm getting an error
with no output after it installs all the i18n stuff.

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

Re: [mythtv-users] 0.17 broke my DVB setup :(

[Jesper Sörensen]

Krunoslav Pisacic skrev:
I can convert the data from the old dvb channel tables into the 
new tables so I dont have to set all my channels up again?
 

You don't need to convert the data. All you need to do is run the 
setup program and scan for channels and it should find 
them all and 
   

But migration from old dvb tables to new should be simple "insert into select [some fields] from dvb_channel, dvb_pids where ..." -
shouldn't it?
 

The database structure with regards to DVB has been completely changed 
(and it's now much more logical). This was needed to simplify things and 
to allow many of the new DVB features (channel scanning, autopid, guide 
data etc.) and will also hopefully make it possible in the future to 
record multiple programs simultaneously from the same transport.

The new structure is completely different and some info is missing in 
the "old" db so unfortunately there is no easy way to automatically 
migrate the data. It should however be possible to salvage some of the 
data with some manual work. You will probably need to work out the 
details yourself but I think something like this could work:

-create temporary table dvb_temp select chanid,channum,serviceid,icon... 
from channel join dvb_channel...
-truncate channels and repopulate the db with the scanner in setup
-update channels,dvb_temp set channels.channum=dvb_temp.channum... where 
channels.serviceid=dvb_temp.serviceid (this requires serviceid to be 
properly set in your old data, or that you have some other good "key" to 
use to map the data)
-update recordings,recordedmarkup (?) and maybe some more tables to use 
the new channel IDs.

Everyone's situation is different so it's probably hard to make 
something that will work for everyone but if you figure out a way to do 
it please share it with the list. And don't forget to backup your db 
before messing with this... :)

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

RE: Subject: RE: [mythtv-users] 0.17 broke my DVB setup :(

[Andrew Ingram]

> Shouldn't the upgrade at least keep existing channels working 
> ? And that scanning only would add so called 'new' found channels?
> In a perfect world current system would work, but scanning in 
> my case fails to detect BBC 2 England from Astra 28.2E, where 
> dvbscan does. 
> As far as I can see there is no way, other than changing the 
> dbtables directly, to get BBC 2 added. Manual adding in setup 
> of channels ain't possible anymore.
> 
> Henk Schoneveld

Nope, the new system disregards the old dvb tables (I think dvb_channel,
dvb_pids and dvb_sat). In future versions these tables will be dropped in
the DB upgrade so it's best you back up that information now as it might
come in useful later on.

Andrew

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

RE: [mythtv-users] 0.17 broke my DVB setup :(

[Krunoslav Pisacic]

> > > > I can convert the data from the old dvb channel tables into the 
> > > > new tables so I dont have to set all my channels up again?
> > > 
> > > You don't need to convert the data. All you need to do is run the 
> > > setup program and scan for channels and it should find 
> > > them all and 

But migration from old dvb tables to new should be simple "insert into select 
[some fields] from dvb_channel, dvb_pids where ..." -
shouldn't it?

can someone please post structure of new table (i belive dt[something]) - i 
would like to give it a try.

i too have preety much complete setup of single DVB-S card with all 
Astra+Hotbird channels i WANT, i wouldn't want to do everything
(icons, chanel numbers, custom tv programs) all over again.


br,

k.

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

Subject: RE: [mythtv-users] 0.17 broke my DVB setup :(

[belcampo]

Hi all,

Shouldn't the upgrade at least keep existing channels working ? And that 
scanning only would add so called 'new' found channels?
In a perfect world current system would work, but scanning in my case fails to 
detect BBC 2 England from Astra 28.2E, where dvbscan does. 
As far as I can see there is no way, other than changing the dbtables 
directly, to get BBC 2 added. Manual adding in setup of channels ain't 
possible anymore.

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

Re: [mythtv-users] 0.17 DVB scan fails ...

[Rob Hillis]

Chris Edwards wrote:
Not sure where you are, but make sure you set the bandwidth correctly. 
That's 7MHz if you're in Australia. I had to provide a frequency too. 
Actually, i had to provide all the frequencies, one by one.
You normally shouldn't need to do that if you did a "Full Transport 
Scan" - the DVB code will check the stream for other network information 
and watch those frequencies too.  (In my case, this resulted in too many 
transports since I'm on a local UHF repeater and the network scan gave 
me all the UHF frequencies in addition to the VHF ones)

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.7 - Release Date: 10/02/2005
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 DVB scan fails ...

[Chris Edwards]

Mark Blair wrote:
When trying to scan with a known Freq It's failing.  Using tzap from the 
DVB utils get's a FE_LOCK just fine.  But the logging from setup reports 
no lock, any ideas what is going wrong ?
Not sure where you are, but make sure you set the bandwidth correctly. 
That's 7MHz if you're in Australia. I had to provide a frequency too. 
Actually, i had to provide all the frequencies, one by one.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 mythfrontend gentoo ebuild

[Tom Dombrosky]

Apparently the ebuild looks for the mythfrontend stuff in
mythfrontend-0.17 instead of mythtv-0.17.  If you untar the
mythtv-0.17.bz2 file, move everything to mythfrontend-0.17, then tar
it back up again, it should work.

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

Re: Playlists (was: Re: [mythtv-users] 0.17)

[Chris Pinkham]

> > This was the exact reason that I wrote the playlist code.  I got
> > tired of having to come back to Myth to start a new program playing
> > every 45 minutes while dubbing some episodes onto VHS tape.  Now I
> > can create cutlists for a bunch, add them to the playlist, start
> > playing, and come back hours later with a full tape.  Then, delete
> > them all with the press of a button.
> 
> Not that I don't think this is a fine ability to have when dumping to
> VHS tape, but the question that comes up in my mind is, why would you
> want to dump to VHS tape when blank DVDs are only about 30 cents?

Because my wife's 70+ year old Grandmother in a nursing home with a VCR
doesn't have a DVD player and probably wouldn't want one if I gave her one. :)

Personally, I record everything at 352x480 (except the stuff coming off my
air2pc card) so that I can just remux and burn to DVD if I feel like it.

> If you're just making the DVDs for yourself (to play on a computer like
> your mythbox) this is easy to do and faster to boot.   If
> you want to make DVDs for others to play on dvd players, it is currently
> a bit more work.  

This is easy, probably a 20-30 line script to remux, run through dvdauthor,
and burn.  It's a whole lot easier when you encode at one of the DVD spec
resolutions.  I used to record at 480x480 so I could burn SVCDs, but now I
use DVD resolution.

> Of course if wanting to play the show somewhere there
> is no computer or DVD player is your goal, then dump to VHS is all
> that's left but it seems that should be a rare case.

I had an itch and I scratched it.

> I always figured the playlists were for the babysitting function.  :-)

Nope, that was the reason I put my patch in CVS, so others could use it
for this, because I could have just kept it to myself. :)

-- 

Chris

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

Re: [mythtv-users] 0.17 Scheme Update Error! Please help?

[Maverick]

> > I had the same problem and took those steps but those colums never got
> > created on mine (not sure why probably a fluke) can someone give me the
> > details of those columns to I can create them correctly?
> 
> The point is that if it didn't upgrade to 1066 or whatever, backing
> out the partial changes means that it will try again the next
> time and should succeed.
> 
> That said, if you "fluke" caused the version number to increment
> without having these changes you can look in the file dbcheck.cpp
> to find the SQL lines to add them.

I just restored mythconverg from a mysqldump I did prior to installing
0.17 and it worked successfully on the second try. I believe the fluke
I experienced was both myth frontend and backend running at the same
time, or something like that... maybe they where both doing BD
changes, and that didn't work so well. :) Used your advice and just
let mythbackend do the updates, and it was fine.

In my opinion, part of the auto-db-update process should be backing up
the DB before it touches it. Seems like the problem could be ugly if
someone didn't have a backup?... Although, I'm not sure how intensive
the db changes are and what things could go wrong. I just prefer to be
safer than sorrier. Then again, I suppose where not talking mission
critical data... ;)

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

Re: Dumping the DB before upgrade Re: [mythtv-users] 0.17

[Maverick]

> > If in doubt, mysqldump the db before doing the upgrade.
> >
> > mysqldump -umythtv -pmythtv -hlocalhost mythconverg | bzip2 -9 >
> > mythtv16.backup.bz2
> 
> The heck with "if in doubt": DO THIS.  Even if you only upgrade at
> new-release time, make this step a standard part of your upgrade
> process.  If you maintain documentation explaining to people how to do
> upgrades, please make this step part of your instructions.
> 
> IF YOU HAVE TO ROLLBACK, AND YOU DIDN'T DO THIS, YOU WILL HATE YOURSELF.

I actually wanted to thank you all for the how-to backup, seeing as I
had to use it to restore the DB because somehow I messed up the
upgrade/firewire column stuff. Anyway, I agree, this should be started
"How to Upgrade MythTV" material.

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

RE: [mythtv-users] 0.17 broke my DVB setup :(

[Tom Hughes]

In message <[EMAIL PROTECTED]>
  "Andrew Ingram" <[EMAIL PROTECTED]> wrote:

> > In message <[EMAIL PROTECTED]>
> > Andrew Ingram <[EMAIL PROTECTED]> wrote:
> 
> > That looks like you haven't populated the new DVB tuning tables yet.
> > 
> > > I know there were a lot of DVB changes for .17 so is there anyway I
> > > can convert the data from the old dvb channel tables into the new
> > > tables so I dont have to set all my channels up again?
> > 
> > You don't need to convert the data. All you need to do is run
> > the setup program and scan for channels and it should find
> > them all and add them without any further intervention from
> > you. That's one of the main advantages of the new system - it
> > can find the channels without all that laborious typing of
> > tuning details ;-)
> 
> Thanks for the advice Tom. But won't using the setup utility mess up the
> carefully assigned channel id's etc that took me ages to set up previously
> (ie to make channels overlap with some of the pvr250 channels)? I'm asking
> this now since I'm away from my mythbox at the moment so I wont be able to
> try this until tomorrow.

I'm not sure - if the name/callsign of the existing channels don't
match what is broadcast over the air then it you might wind up with
duplicates. In the long term you'll probably want to change everthing
to the names that come in over the air or it might keep re-adding
the channels.

I only have DVB cards so I just threw everything out and started fresh.

Tom

-- 
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 Scheme Update Error! Please help?

[Bruce Markey]

Bryan Halter wrote:
I had the same problem and took those steps but those colums never got
created on mine (not sure why probably a fluke) can someone give me the
details of those columns to I can create them correctly?
The point is that if it didn't upgrade to 1066 or whatever, backing
out the partial changes means that it will try again the next
time and should succeed.
That said, if you "fluke" caused the version number to increment
without having these changes you can look in the file dbcheck.cpp
to find the SQL lines to add them.
--  bjm
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: Playlists (was: Re: [mythtv-users] 0.17)

[Brad Templeton]

On Fri, Feb 11, 2005 at 01:41:37PM -0500, Chris Pinkham wrote:
> > My sister makes the excellent point that if you're inclined to dump
> > programs to tape, the playlist feature is probably going to be handy
> > for that: cue 8 hours of programming, hit play, go to work.
> 
> This was the exact reason that I wrote the playlist code.  I got
> tired of having to come back to Myth to start a new program playing
> every 45 minutes while dubbing some episodes onto VHS tape.  Now I
> can create cutlists for a bunch, add them to the playlist, start
> playing, and come back hours later with a full tape.  Then, delete
> them all with the press of a button.

Not that I don't think this is a fine ability to have when dumping to
VHS tape, but the question that comes up in my mind is, why would you
want to dump to VHS tape when blank DVDs are only about 30 cents?

If you're just making the DVDs for yourself (to play on a computer like
your mythbox) this is easy to do and faster to boot.   If
you want to make DVDs for others to play on dvd players, it is currently
a bit more work.  Of course if wanting to play the show somewhere there
is no computer or DVD player is your goal, then dump to VHS is all
that's left but it seems that should be a rare case.

I always figured the playlists were for the babysitting function.  :-)
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: Dumping the DB before upgrade Re: [mythtv-users] 0.17

[Jay R. Ashworth]

On Fri, Feb 11, 2005 at 11:36:39AM -0700, Risto Treksler wrote:
> backing up the database is very important,
> but using the above command it is needlessly difficult to roll it back
> 
> I use d
> 
> mysqldump --opt --allow-keywords --all-databases -uroot > mysqldump-0.16.sql
> gzip  mysqldump-0.16.sql

Alas, this can be needlessly difficult in another direction.

I recommend against using "--all-databases" -- at least some, and
possibly many, people are using the MySQL install on their box for
other things; you don't want *that* stuff to roll back at the same
time.

Cheers,
-- jra
-- 
Jay R. Ashworth[EMAIL PROTECTED]
Designer  Baylink RFC 2100
Ashworth & AssociatesThe Things I Think'87 e24
St Petersburg FL USA  http://baylink.pitas.com +1 727 647 1274

  If you can read this... thank a system adminstrator.  Or two.  --me
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] 0.17 Scheme Update Error! Please help?

[Bryan Halter]

Bruce Markey wrote:
Maverick wrote:
I finally got the libqt3c102-mt-mysql package installed, ran through
myth-setup to make sure everything is ok, now starting mythfrontend I
am getting:
2005-02-11 14:14:32.678 Upgrading to schema version 1066
2005-02-11 14:14:32.681 DB Error (Performing database upgrade):
Query was: ALTER TABLE capturecard ADD COLUMN firewire_port INT
UNSIGNED NOT NUL
L DEFAULT 0;
Error was: Driver error was [2/1060]:
QMYSQL3: Unable to execute query
Database error was:
Duplicate column name 'firewire_port'
new version: 1066
2005-02-11 14:14:32.681 Couldn't upgrade database to new schema,
exiting.

1)
mysql -u mythtv -pmythtv mythconverg
2)
DELETE FROM profilegroups WHERE name = 'FireWire Input';
ALTER TABLE capturecard DROP COLUMN firewire_port;
ALTER TABLE capturecard DROP COLUMN firewire_node;
ALTER TABLE capturecard DROP COLUMN firewire_speed;
ALTER TABLE capturecard DROP COLUMN firewire_model;
quit
3)
Don't worry if any of these complain. One or more should.
4)
mythbackend . Do not start two different myth programs at this
time and do not inturrupt it while it is doing it's updates.
5)
Continue on with the rest of your life =).
--  bjm
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
I had the same problem and took those steps but those colums never got
created on mine (not sure why probably a fluke) can someone give me the
details of those columns to I can create them correctly?
Bryan
--
Bryan Halter
[EMAIL PROTECTED]
PGP 0x55AB8EA4


signature.asc
Description: OpenPGP digital signature
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users