Looking for someone with the time and knowledge of the MythTV source code to chase down this LiveTV ringbuffer issue. Since most of the devs do not use LiveTV, this bug is not high on their priority lists. I am still renting two cable boxes until this is resolved. The bug involves a deadlock that occurs when the backend attempts to transition the frontend from one LiveTV ringbuffer to the next on a program boundary. The frontend times out because the transition never completes.
On Mon, Jun 18, 2012 at 12:22 PM, two.bits.11 <tombo...@gmail.com> wrote:
> Looking for someone with the time and knowledge of the MythTV source code
> to chase down this LiveTV ringbuffer issue. Since most of the devs do not
> use LiveTV, this bug is not high on their priority lists. I am still
> renting two cable boxes until this is resolved. The bug involves a deadlock
> that occurs when the backend attempts to transition the frontend from one
> LiveTV ringbuffer to the next on a program boundary. The frontend times out
> because the transition never completes.
I would strongly suggest raising a bug in Trac about this. Whether or
not we use LiveTV, we do consider it to be an important feature, and
if it's borked, we will look at getting it fixed.
I do appreciate this response. It is good to hear that you do consider LiveTV important. I will certainly raise this on torc after searching if it exists already. I am willing to provide any logs or data possible.
-Tom
On Jun 18, 2012, at 6:01 PM, Gavin Hurlbut <gjhur...@gmail.com> wrote:
> On Mon, Jun 18, 2012 at 12:22 PM, two.bits.11 <tombo...@gmail.com> wrote:
>> Looking for someone with the time and knowledge of the MythTV source code
>> to chase down this LiveTV ringbuffer issue. Since most of the devs do not
>> use LiveTV, this bug is not high on their priority lists. I am still
>> renting two cable boxes until this is resolved. The bug involves a deadlock
>> that occurs when the backend attempts to transition the frontend from one
>> LiveTV ringbuffer to the next on a program boundary. The frontend times out
>> because the transition never completes.
> I would strongly suggest raising a bug in Trac about this. Whether or
> not we use LiveTV, we do consider it to be an important feature, and
> if it's borked, we will look at getting it fixed.
> I do appreciate this response. It is good to hear that you do consider
> LiveTV important. I will certainly raise this on torc after searching if
> it exists already. I am willing to provide any logs or data possible.
> -Tom
> On Jun 18, 2012, at 6:01 PM, Gavin Hurlbut <gjhur...@gmail.com> wrote:
> > On Mon, Jun 18, 2012 at 12:22 PM, two.bits.11 <tombo...@gmail.com>
> wrote:
> >> Looking for someone with the time and knowledge of the MythTV source
> code
> >> to chase down this LiveTV ringbuffer issue. Since most of the devs do
> not
> >> use LiveTV, this bug is not high on their priority lists. I am still
> >> renting two cable boxes until this is resolved. The bug involves a
> deadlock
> >> that occurs when the backend attempts to transition the frontend from
> one
> >> LiveTV ringbuffer to the next on a program boundary. The frontend
> times out
> >> because the transition never completes.
> > I would strongly suggest raising a bug in Trac about this. Whether or
> > not we use LiveTV, we do consider it to be an important feature, and
> > if it's borked, we will look at getting it fixed.
> Umm, trac, not torc. We don't work bugs in whatever tracking system they use.
> On Jun 18, 2012 4:50 PM, "Tom Bongiorno" <t...@bongohut.com> wrote:
> I do appreciate this response. It is good to hear that you do consider LiveTV important. I will certainly raise this on torc after searching if it exists already. I am willing to provide any logs or data possible.
> -Tom
> On Jun 18, 2012, at 6:01 PM, Gavin Hurlbut <gjhur...@gmail.com> wrote:
> > On Mon, Jun 18, 2012 at 12:22 PM, two.bits.11 <tombo...@gmail.com> wrote:
> >> Looking for someone with the time and knowledge of the MythTV source code
> >> to chase down this LiveTV ringbuffer issue. Since most of the devs do not
> >> use LiveTV, this bug is not high on their priority lists. I am still
> >> renting two cable boxes until this is resolved. The bug involves a deadlock
> >> that occurs when the backend attempts to transition the frontend from one
> >> LiveTV ringbuffer to the next on a program boundary. The frontend times out
> >> because the transition never completes.
> > I would strongly suggest raising a bug in Trac about this. Whether or
> > not we use LiveTV, we do consider it to be an important feature, and
> > if it's borked, we will look at getting it fixed.
On Mon, Jun 18, 2012 at 5:29 PM, Tom Bongiorno <t...@bongohut.com> wrote:
> That is funny!!! That is what I meant. Hope I didn't offend. That was an
> odd slip of the tongue considering I have never used it.
