[14:34] <adam_112> Setup a new .25 mythtv frontend / backend.  Been trying to get it to work for a month or so.  Having problems.   The machine is a dual core with an  Homerun prime CC tuner.   Livetv starts, run for 5 10 secs on some channels and then fails.  It works on others......   Just working on SD right now.
[14:52] <rhpot1991> adam_112: so updating to .25 didn't help?
[14:52] <rhpot1991> and define SD
[14:52] <adam_112> standard Def.
[14:53] <rhpot1991> so it works with SD but not HD?
[14:53] <adam_112> no.  I  am able to run vlc with the prime gui no problems.
[14:54] <rhpot1991> well that and the fact that your recordings work, rule out the tuner
[14:54] <rhpot1991> did you try getting verbose frontend logs like I said?
[14:55] <adam_112> Yes.  I posted yesterday http://pastebin.com/BW6BXe8Z
[14:55] <Zinn> [pastebin.com] Gathered following logs [15:12] <skd5aner> adam_112: a ton of bugs related to live tv are known and being addressed by the developers prior to releasing 0.25
[15:13] <adam_112> okay.  I've download the current 0.25.  Maybe I'll get lucky and it will be fixed in the next day or two.
[15:15] <tgm4883> our of curiosity, if you schedule a recording, can you watch it?
[15:15] <adam_112> yes i can
[15:16] <foxbuntu> adam_112, these two lines in the logs seem to indicate your issues:
[15:16] <foxbuntu> (WaitForReadsAllowed) RingBuf(/var/lib/mythtv/livetv/1102_20120404225642.mpg): Taking too long to be allowed to read..
[15:16] <foxbuntu> ..and Apr  4 22:56:42 croom mythfrontend[1889]: E CoreContext filtermanager.cpp:243 (LoadFilters) FilterManager: Failed to load filter 'vpdaubuffersize', no such filter exists
[15:16] <adam_112> okay. why.
[15:16] <foxbuntu> not sure if the second one matters but the first one seems to
[15:16] <foxbuntu> thats where your time out occurs
[15:17] <adam_112> The second one is a param i tried to add.
[15:17] <foxbuntu> did you check the permissions on that directory?
[15:17] <adam_112> Livetv plays for a bit then terms  so I assume the it has write perms to it.
[15:18] <skd5aner> adam_112: http://www.gossamer-threads.com/lists/mythtv/dev/510632
[15:18] <Zinn> [www.gossamer-threads.com] 0.25 final -- Delayed until approximately April 9th | MythTV | Dev
[15:19] <foxbuntu> adam_112, could be the buffer playing
[15:19] <skd5aner> The second error is harmless (vdpaubuffersize)
[15:19] <foxbuntu> adam_112, I would check the perms
[15:19] <adam_112> Will do.
[15:19] <skd5aner> that attribute has been removed as the buffer size is now dynamic.  If it's in the config line, the parser will just ingore it, and it is not an "error"
[15:19] <foxbuntu> skd5aner, figured as much
[15:20] <skd5aner> it is recommended to remove it from your settings though - just to keep it clean
[15:20] <adam_112> That was left over from when I was on 0.24
[15:20] <adam_112> It didn't help anyways :)
[15:20] <skd5aner> yes
[15:29] <rhpot1991> vpdaubuffersize changed in 0.25
[15:29] <rhpot1991> its something else now
[15:29] <rhpot1991> check the wiki its addressed in the release notes I think
[15:32] <rhpot1991> adam_112: verify if /var/lib/mythtv/livetv/1102_20120404225642.mpg exists?
[15:44] <skd5aner> rhpot1991: yes, it "changed" - but the point is, the change really isn't being communicated because the buffer size is now dynamically set and shouldn't really need to be overridden
[15:44] <skd5aner> (and I'm the guy who wrote the release notes ;) )
[15:46] <rhpot1991> skd5aner: I thought that was the case, too busy to go find the release notes though, thanks for clearing it up
[15:47] <skd5aner> np :)
[16:56] <adam_112> any other ideas?  The  livetv folder is owned by myth.
[18:25] <skd5aner> admin_112: have you asked danielk in #mythtv
[18:26] <skd5aner> adam_112: normally, I would never ask a user to go in to #mythtv to bug the devs, but he's specifically trying to fix a bunch of livetv issues within the next 2 days
[18:26] <skd5aner> s/admin_112/adam_112
[18:27] <skd5aner> adam_112: it may actually be helpful, in this case, to actually bring up the fact that you are running a very recent copy of 0.25 and can provide logs and details about some livetv issues and see if he needs the details or not... he may tell you he's aware and thy're being taken care of
[18:33] <rhpot1991> skd5aner: its worth noting that he had the exact same issues in 0.24.2 and tried upgrading to 0.25 to fix it
[18:36] <skd5aner> yea, but several long standling Live TV bugs have been targetted in the last month... and there's been a few regressions as well
[18:36] <skd5aner> but it is good info to provide
[18:41] <superm1> yeah even with 0.24 i always cringed when people were over and wanting to watch "live tv" in case problems would arise
[18:41] <superm1> i'm glad to hear it's a focal point for fixing in 0.25
[18:42] <skd5aner> me too
[18:42] <skd5aner> my wife uses live tv daily
[18:42] <rhpot1991> I only use it on one box, but yes it causes issues for my wife sometimes
[19:25] <adam_112> Will do.
[19:26] <adam_112> Excuse the long copy but I got this from another user -
[19:26] <adam_112> 	adam_112	If I could get it narrowed down to that it might give me something to go on.
[19:26] <adam_112> 	wagnerrp	the diagnostic page on your HDHR says the cablecard is paired properly?
[19:26] <adam_112> 	adam_112	Yes. I can use the card with WMC
[19:26] <adam_112> 	wagnerrp	this bit in the backend where it complains about the channel being encrypted, and trying to apply some PID filer, makes no sense
[19:26] <adam_112> 	wagnerrp	the Prime is supposed to handle all that internally using its virtual channel table
[19:26] <adam_112> 	wagnerrp	mythtv is supposed to be ignorant of any such information
[19:26] <adam_112> 	adam_112	Okay. You are talking above my head here.
[19:26] <adam_112> 	wagnerrp	23:00:05
[19:26] <adam_112> 	wagnerrp	the PMT table and PID filter is what is used to denote multiple streams (multiple channels) in a digital multiplex
[19:26] <adam_112> 	wagnerrp	you tune the multiplex, and can capture multiple channels out of it simultaneously
[19:26] <adam_112> 	wagnerrp	using the filter to specify specifically which ones you want
[19:26] <adam_112> 	adam_112	Okay. I think I understand.
[19:26] <adam_112> 	wagnerrp	but that only should happen when operating in ATSC/ClearQAM mode
[19:26] <adam_112> 	wagnerrp	in cablecard mode, mythtv should be using a completely different mechanism for tuning
[19:27] <adam_112> 	wagnerrp	passing the virtual channel number into the HDHR, and letting it handle all that
[19:32] <adam_112> Log file - http://pastebin.com/BW6BXe8Z
[19:32] <Zinn> [pastebin.com] Gathered following logs [19:35] <rhpot1991> adam_112: should have pastebin'd that
[19:44] <Batshua> Is 11.10 LTS or not LTS?
[19:49] <tgm4883> Batshua, it is not
[19:49] <Batshua> Is it otherwise stable and sane?
[19:49] <rhpot1991> yes
[19:49] <tgm4883> why wouldn't it be?
[19:49] <Batshua> In the past I've stuck to LTS releases because once I did a non-LTS update and it broke everything.
[19:49] <Batshua> Alright, I'll chance it, since 12.04 ain't out yet. Thanks.
[19:49] <rhpot1991> your odds are upgrade breakage should be the same lts or not
[19:50] <rhpot1991> we don't do anything special for lts
[19:50] <Batshua> <-- is rebuilding PVR almost entirely from scratch.
[19:50] <Batshua> Oh.
[19:50] <Batshua> Really?!
[19:50] <Batshua> I thought that meant it was like, more stable or more tested or more /something/.
[19:50] <rhpot1991> its supported longer
[19:50] <rhpot1991> same testing goes into each release
[19:53] <tgm4883> common misconception
[19:53] <tgm4883> LTS = Long Term Support
[19:53] <tgm4883> not Long Term Stability
[20:01] <Batshua> AHA!
[20:01] <Batshua> Well, that doesn't matter so much, then, because I like to keep up to date.
[20:03] <tgm4883> Batshua, why?
[20:04] <Batshua> I like new stuff?
[20:04] <tgm4883> You are bored a lot?
[20:04] <Batshua> I'm not always bleeding edge or anything (I prefer KDE3 to KDE4, for example), but the shiny of the new is an attraction for me, like many folk.
[20:04] <Batshua> Well, I do have copious spare time these days…
[20:05] <tgm4883> Batshua, Do you use your frontend as a desktop?
[20:06] <Batshua> Uhm, sometimes.
[20:06] <Batshua> Mostly I ssh tunnel into it when my laptop is feeling overtaxed.
[20:06] <tgm4883> so what shiny new things do you need from a new Ubuntu release?
[20:08] <Batshua> Not need. Just want.
[20:08] <Batshua> I remember sound broke one time. I sure as heck want sound working.
[20:08] <Batshua> I can't remember when I last used my box if sound was functional or not
[20:08] <tgm4883> Batshua, what I'm trying to get at, is why do you upgrade the entire OS, and not just use -repos?
[20:08] <tgm4883> !repos
[20:08] <Zinn> The Mythbuntu team provides updates for MythTV and Mythbuntu package using the Mythbuntu Repos http://mythbuntu.org/repos
[20:08] <Batshua> Usually I use repos
[20:08] <Batshua> but my computer done got hosed
[20:09] <Batshua> and so I may need to do a totally fresh install
[20:09] <Batshua> Hence wanting to burn a liveCD.
[20:10] <Batshua> 'cause I don't know what the damage is.
[20:10] <tgm4883> ok
[20:10] <Batshua> 3/5 of my drives won't mount.
[20:10] <Batshua> 1 has a bad bearing.
[20:10] <Batshua> the other two drives may have bad blocks, or may be dying.
[20:10] <Batshua> so … yeah.
[20:10] <Batshua> This is not a regular bit of maintenance.
[20:16] <Batshua> My PVR crossed the country at least twice via FedEx, and by the time I got it, it needed a new everything, pretty much.
[20:16] <Batshua> I'm trying to salvage the drives and so it's … an adventure.
[22:10] <Batshua> I'm on the liveCD and I've got Problems.
[22:11] <Batshua> "Unable to load a failsafe session"
[22:28] <Shadow__X> foxbuntu: ok what logs should i post for the script error
[23:24] <foxbuntu> Shadow__X, just post everything
[23:26] <Shadow__X> for this which log should i be looking at run-parts: /etc/cron.hourly/mythtv-backend exited with return code 2