| Thursday, July 14th, 2016, 00:49 UTC | ||
| [00:49:46] | jheizer (jheizer!~jheizer@2601:246:8201:9dbf:3dc2:83ec:12e5:a2a8) has joined #mythtv | |
| [00:56:27] | SteveGoodey (SteveGoodey!~steve@host86-132-138-229.range86-132.btcentralplus.com) has joined #mythtv | |
| [01:31:42] | knightr_ (knightr_!~knightr@69-165-170-178.dsl.teksavvy.com) has joined #mythtv | |
| [01:31:42] | knightr_ (knightr_!~knightr@69-165-170-178.dsl.teksavvy.com) has quit (Changing host) | |
| [01:31:42] | knightr_ (knightr_!~knightr@mythtv/developer/knightr) has joined #mythtv | |
| [01:31:42] | knightr (knightr!~knightr@mythtv/developer/knightr) has quit (Read error: Connection reset by peer) | |
| [02:49:58] | SteveGoodey (SteveGoodey!~steve@host86-132-138-229.range86-132.btcentralplus.com) has quit (Quit: Konversation terminated!) | |
| [02:50:31] | peper03_ (peper03_!~peper03@mythtv/developer/peper03) has joined #mythtv | |
| [02:50:34] | peper03 (peper03!~peper03@mythtv/developer/peper03) has quit (Ping timeout: 272 seconds) | |
| [02:50:34] | peper03_ is now known as peper03 | |
| [03:34:15] | arescorpio (arescorpio!~arescorpi@120-41-16-190.fibertel.com.ar) has joined #mythtv | |
| [04:01:25] | gigem: | jpabq: Sounds good. |
| [04:49:34] | peper03_ (peper03_!~peper03@mythtv/developer/peper03) has joined #mythtv | |
| [04:49:38] | peper03 (peper03!~peper03@mythtv/developer/peper03) has quit (Ping timeout: 272 seconds) | |
| [04:49:38] | peper03_ is now known as peper03 | |
| [05:08:05] | arescorpio (arescorpio!~arescorpi@120-41-16-190.fibertel.com.ar) has quit (Quit: Leaving.) | |
| [05:17:30] | peper03 (peper03!~peper03@mythtv/developer/peper03) has quit (Ping timeout: 272 seconds) | |
| [05:17:34] | peper03_ (peper03_!~peper03@mythtv/developer/peper03) has joined #mythtv | |
| [05:17:41] | peper03_ is now known as peper03 | |
| [06:01:33] | knightr_ (knightr_!~knightr@mythtv/developer/knightr) has quit (Read error: Connection reset by peer) | |
| [06:01:42] | knightr_ (knightr_!~knightr@69-165-170-178.dsl.teksavvy.com) has joined #mythtv | |
| [06:01:42] | knightr_ (knightr_!~knightr@69-165-170-178.dsl.teksavvy.com) has quit (Changing host) | |
| [06:01:42] | knightr_ (knightr_!~knightr@mythtv/developer/knightr) has joined #mythtv | |
| [06:59:03] | peper03 (peper03!~peper03@mythtv/developer/peper03) has quit (Ping timeout: 244 seconds) | |
| [07:00:08] | peper03 (peper03!~peper03@mythtv/developer/peper03) has joined #mythtv | |
| [07:30:01] | knightr_ (knightr_!~knightr@mythtv/developer/knightr) has quit (Read error: Connection reset by peer) | |
| [07:40:57] | SteveGoodey (SteveGoodey!~steve@host86-132-138-229.range86-132.btcentralplus.com) has joined #mythtv | |
| [08:47:37] | Merlin83b (Merlin83b!~Daniel@office.34sp.com) has joined #mythtv | |
| [09:17:32] | xris (xris!~xris@mythtv/developer/xris) has quit (Ping timeout: 272 seconds) | |
| [09:33:00] | xris (xris!~xris@xris.forevermore.net) has joined #mythtv | |
| [09:33:00] | xris (xris!~xris@xris.forevermore.net) has quit (Changing host) | |
| [09:33:00] | xris (xris!~xris@mythtv/developer/xris) has joined #mythtv | |
| [09:40:35] | xris (xris!~xris@mythtv/developer/xris) has quit (Ping timeout: 244 seconds) | |
| [09:41:13] | xris (xris!~xris@xris.forevermore.net) has joined #mythtv | |
| [09:41:13] | xris (xris!~xris@mythtv/developer/xris) has joined #mythtv | |
| [09:41:13] | xris (xris!~xris@xris.forevermore.net) has quit (Changing host) | |
| [11:04:24] | Merlin83b2 (Merlin83b2!~Daniel@office.34sp.com) has joined #mythtv | |
| [11:04:24] | Merlin83b (Merlin83b!~Daniel@office.34sp.com) has quit (Read error: Connection reset by peer) | |
| [12:07:06] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has joined #mythtv | |
| [12:46:51] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has quit (Remote host closed the connection) | |
| [12:49:41] | dblain (dblain!~dblain@mythtv/developer/dblain) has joined #mythtv | |
| [12:53:09] | dblain (dblain!~dblain@mythtv/developer/dblain) has quit (Read error: Connection reset by peer) | |
| [13:25:09] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has joined #mythtv | |
| [13:36:08] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has quit (Remote host closed the connection) | |
| [13:42:04] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has joined #mythtv | |
| [13:47:58] | peper03 (peper03!~peper03@mythtv/developer/peper03) has quit (Ping timeout: 272 seconds) | |
| [13:50:18] | peper03 (peper03!~peper03@mythtv/developer/peper03) has joined #mythtv | |
| [14:00:06] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has quit (Remote host closed the connection) | |
| [14:13:15] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has joined #mythtv | |
| [14:29:51] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has quit (Remote host closed the connection) | |
| [14:50:00] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has joined #mythtv | |
| [15:42:24] | Roklobster (Roklobster!~Dirkka@ppp118-209-148-192.lns20.mel8.internode.on.net) has quit (Quit: Leaving) | |
| [16:03:23] | HeXiLeD: | question about encrypted signal https://forums.gentoo.org/viewtopic-p-7944026.html#7944026 |
| [16:05:00] | stuartm: | HeXiLeD: might ask in #mythtv-users |
| [16:05:44] | stuartm: | afraid I can't help as I'm in the UK where it's not permitted to capture Cable (we use Satellite and Terrestrial), so I've not idea on the hardware side |
| [16:06:59] | HeXiLeD: | so you cant use a tv card to get cable signal ? |
| [17:02:56] | gigem: | Yesterday, dekarl1 asked about raising the maximum number of simultaneous recordings from 5 now that schedgroup is available. The main reason for schedgroup is so the max can be set high without negatively impacting scheduling. 5 is more than enough for my clear QAM and cable card setup. I imagine some of you DVB-S users could use more, though. Does anyone else care to comment? |
| [17:12:49] | warpme (warpme!~piotro@89-67-153-39.dynamic.chello.pl) has joined #mythtv | |
| [17:14:33] | warpme: | gigem: regarding Your Q about reclimit value: before answering my view I want to understand better use-case when given virtual tuner will record more that 1 program on DVB-S. Is it possible at all? |
| [17:15:24] | warpme: | that->than |
| [17:18:09] | Merlin83b2 (Merlin83b2!~Daniel@office.34sp.com) has quit (Quit: Leaving) | |
| [17:22:15] | warpme (warpme!~piotro@89-67-153-39.dynamic.chello.pl) has quit (Quit: BitchX: now with 74 percent fewer calories!) | |
| [17:22:50] | warpme (warpme!~warpme@89-67-153-39.dynamic.chello.pl) has joined #mythtv | |
| [18:34:17] | gigem (gigem!~david@mythtv/developer/gigem) has quit (Quit: WeeChat 1.5) | |
| [18:36:59] | gigem (gigem!~david@mythtv/developer/gigem) has joined #mythtv | |
| [18:44:15] | gigem: | Warped: I don't really understand your question. It's still plain, old, multirec at heart. That means if two or more programs are on the same multiplex (or channel in the case of cable card), then MythTV is capable of recording them all on a single, physical input. In the case of schedgroup, the scheduler can do its job more efficiently because it has fewer possibilities to consider with the caveat that it |
| [18:44:17] | gigem: | can oversubscribe an input if not enough virtual inputs are configured. |
| [18:51:27] | warpme: | gigem: this is how I understand schedgroup improvement. So how exactly I should interpret „maximum number of simultaneous recordings†in DVB-S world? |
| [18:53:14] | warpme: | for me it is equal to number of virtual inputs (virtual tuners) |
| [18:56:45] | warpme: | isn’t it is that if I have 4 virtual tuners per single phy.tuner then reclimit should be 4? |
| [18:58:32] | warpme: | I was thinking that overlapping recordings may need to increase reclimit over this number – but it looks it is not needed as my system placing overlaping recordings on separate virtual tuners... |
| [19:30:44] | gigem: | warpme: "Maximum number of simultaneous recordings", "reclimit" and "number of virtual tuners" are all synonymous. How many do you need? I don't know, only you can decide that. I'll give an example. Let's say you have a multiplex with 4 channels on it and you often record from all of the channels. If you never use start-early/end-late and don't care about pre/post-roll, you can probably get by with just |
| [19:30:45] | gigem: | 4 virtual tuners. However, if you do use start-early/end-late or care about pre/post-roll, then you probably want more. My suggestion is to have at least twice as many virtual tuners as chennels you expect to record. |
| [19:45:09] | warpme: | gigem: exactly. I got it exactly as You said regarding virtual tuners setup guidline – and I’m using exactly such rule when I was configuring my system. I think reclimit rule is simple in such case: reclimit (on parent phy. tuner) should be equal to number virtual tuners defined for this phy.tuner (4 in my case). Setting reclimit to higher value will make sense only when myth will be able to record more that 1 program in virtual tuner – ant |
| [19:45:10] | warpme: | this is NOT possible in DVB world. Am I right? |
| [19:45:44] | warpme: | ant->and |
| [20:11:04] | gigem: | warpme: I think you are still confused. While I had originally hoped to make a bigger change where a single input could record an unlimited number or programs simultaneously, that wasn't in the cards (pun intended). Instead I settled on reusing the existing multirec capabilities where a virtual input can record 1 and only 1 program at a time. The number of virtual inputs per physical input, however, is |
| [20:11:06] | gigem: | completely arbitrary. |
| [20:11:12] | gigem: | The question at hand is should the current limit of 5 virtual inputs per physical input be raised, and if so, to what value. While the cost of virtual inputs has been lowered with schedgroup, it is not zeo, so there should probably be some practical limit. |
| [20:11:15] | gigem: | I can easily live with the current limit. It sounds like you are happy with 4, though, I suspect I could easily comes up with scenarios where you would want more. There waa a guy from New Zealand a while back on the mailing list. I believe he had 3 multiplexes on DVB-T, each with 5 channels. I could easily see him wanting 8–10 virtual inputs. |
| [20:18:11] | dekarl (dekarl!~dekarl@mythtv/developer/dekarl) has joined #mythtv | |
| [20:19:04] | warpme: | gigem: I’m in 100% understanding. we are on the same page. Now regarding upper limit of virtual inputs per phy input: I think it shoul be equal to all channels user subscribes from most dense mplex. In my case it is DVB-T with SD channels: 9 channels. So limit should be 9–10 i my case. |
| [20:21:03] | dekarl1 (dekarl1!~dekarl@mythtv/developer/dekarl) has quit (Ping timeout: 240 seconds) | |
| [20:24:34] | warpme: | and of course I should have my dvb-t phy tuner with 9 virtual tuners…. |
| [20:34:47] | SteveGoodey (SteveGoodey!~steve@host86-132-138-229.range86-132.btcentralplus.com) has quit (Quit: Konversation terminated!) | |
| [20:43:24] | warpme (warpme!~warpme@89-67-153-39.dynamic.chello.pl) has quit (Quit: warpme) | |
| [21:02:09] | Hydr0p0nX (Hydr0p0nX!~hydr@66-191-154-200.dhcp.mtgm.al.charter.com) has quit (Ping timeout: 246 seconds) | |
| [21:02:48] | Hydr0p0nX (Hydr0p0nX!~hydr@66-191-154-200.dhcp.mtgm.al.charter.com) has joined #mythtv | |
| [21:04:32] | amessina (amessina!~amessina@unaffiliated/amessina) has joined #mythtv | |
| [21:13:25] | joki (joki!~joki@p54860C74.dip0.t-ipconnect.de) has quit (Ping timeout: 252 seconds) | |
| [21:13:54] | stuartm: | gigem: in the UK you might have upwards of a dozen channels on a single multiplex (including audio-only 'radio' channels), and 7–8 multiplexes in total |
| [21:14:21] | amessina (amessina!~amessina@unaffiliated/amessina) has quit (Read error: Connection reset by peer) | |
| [21:14:53] | stuartm: | but realistically 99% of people aren't going to be recording from more than 5–6 channels per multiplex at a time. Special case, power or commercial users can change that limit in the source if they need |
| [21:15:13] | stuartm: | (and they do) |
| [21:16:43] | stuartm: | the limits are more about preventing users shooting themselves in the foot, since there will always be the mentality with a certain portion of the population that more === better, and if they then run into trouble with performance or failed recordings, they don't see that as their fault but the applications |
| [21:19:43] | stuartm: | I'd say 6–7 at most, though I have no issues with the current limit of 5. multi-tuner recorders are plentiful if that's not enough. I personally have a 2xDVB-S2 card and a 2xDVB-T2 card, with multirec and repeats I've not missed a recording due to lack of tuners for years |
| [21:20:32] | joki (joki!~joki@p54860C74.dip0.t-ipconnect.de) has joined #mythtv | |
| [21:22:06] | amessina (amessina!~amessina@unaffiliated/amessina) has joined #mythtv | |
| [21:28:00] | joki (joki!~joki@p54860C74.dip0.t-ipconnect.de) has quit (Read error: No route to host) | |
| [21:30:32] | joki (joki!~joki@p54860C74.dip0.t-ipconnect.de) has joined #mythtv | |
| [21:48:10] | ShapeShifter499 (ShapeShifter499!~ShapeShif@unaffiliated/shapeshifter499) has joined #mythtv | |
| [22:00:04] | joki (joki!~joki@p54860C74.dip0.t-ipconnect.de) has quit (Ping timeout: 240 seconds) | |
| [22:05:35] | joki (joki!~joki@p548601BA.dip0.t-ipconnect.de) has joined #mythtv | |
| [22:13:30] | MythBuild: | build #173 of master-debian-jessie-rpi2 is complete: Success [3build successful] Build details are at http://code.mythtv.org/buildbot/builders/mast . . . 2/builds/173 |
| [22:41:48] | gigem: | stuartm: With QAM, we have lots of multiplexes, but typically only 2 or 3 HD channels per each. For SD channels, there can be 10–13 and for music, many more, but as you said, realistically, nobody records that many of those. It sounds like 10 would be a good, new max. High enough to handle most real users, but not too ridiculous. |
| [22:52:37] | dekarl: | 5–6 channels * 2 for overlap sounds like "enough for everyone". We could make this the "default value when schedulegroup is enabled" leaving the option to fiddle with it via code patches / database manipulation |
| [23:56:51] | dym (dym!~patrick@xstd.de) has quit (Ping timeout: 240 seconds) | |
IRC Logs collected by
BeirdoBot.
Please use the above link to report any bugs.