<div class="gmail_quote">On Mon, Mar 19, 2012 at 1:20 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 03/18/2012 08:00 PM, Scott & Nicole Harris wrote:<br>
>>> I'm running 0.25 from about a week ago. Today I discovered a case<br>
>>> where livetv consistently won't work if I start on a particular<br>
>>> channel. If I start on another channel and switch to that channel, it<br>
>>> works fine. However if I start on that channel it hangs for about 10<br>
>>> seconds before dumping back to the menu with the "error opening<br>
>>> jumpfile" message. However, I've noticed that even though it doesn't<br>
>>> playback, the 10 second file is created, and if I go into the<br>
>>> "recorded programs" screen and switch to the livetv group, the<br>
>>> recording is there and it plays fine. I also did some testing with<br>
>>> mplayer, where as soon as I start mythtv in livetv and it's waiting<br>
>>> for the video to start, I quickly switch to mplayer and begin to play<br>
>>> the mpg file, and the file works fine. So it's not a case where the<br>
>>> data isn't making into the file (or the data isn't being flushed) in a<br>
>>> timely manner, because mplayer is seeing it just fine at the same time<br>
>>> that myth can't.<br>
>> I did some more debugging on this. Turning off the AlwaysStreamFiles<br>
>> setting files seems to let playback work on this channel. I couldn't<br>
>> find that setting in the setup screens (was it removed in 0.25?) so I<br>
>> just disabled in the database and that took care of it. Still don't<br>
>> know why it's just that one channel that fails for streaming. Any<br>
>> ideas?<br>
> That's interesting. I have one FE that will not play live TV without<br>
> AlwaysStreamFiles turned ON (it just hangs at a blank screen for ~10<br>
> seconds, then the "error opening jumpfile") and have never figured out why.<br>
<br>
Almost definitely NFS misconfiguration, as Daniel mentioned.<br>
<a href="http://www.mythtv.org/docs/mythtv-HOWTO-23.html#ss23.8" target="_blank">http://www.mythtv.org/docs/mythtv-HOWTO-23.html#ss23.8</a> (specifically the<br>
actimeo option).<br>
<br>
> About the only thing I can think of is this FE is also a SBE (though that is<br>
> now turned off in favor of mythjobqueue) and it has identical folders<br>
> mounted to the the MBE to allow it to do transcodes. Maybe something to do<br>
> with that?<br>
><br>
> It's also a little concerning that the setting itself has been removed from<br>
> Myth settings screens (I believe it was gone in 0.24 too,but don't quote me<br>
> on that), but it still seems to have a pretty big impact.<br>
<br>
The setting was removed because it's a broken setting that was used to<br>
work around system misconfiguration.<br>
<br>
If you want mythbackend to stream files, you should ensure the file<br>
system on which those files exist is not mounted locally. If you want<br>
mythfrontend to read files "locally", you should ensure the file system<br>
on which those files exist is mounted locally.<br>
<br>
Or, put another way, if you want to use NFS, use NFS. If not, don't.<br>
<br>
There is absolutely no reason to mount a file system locally using NFS<br>
if you don't have mythfrontend reading files for playback over NFS.<br>
<br>
If you think there's a reason, then there's some other problem with your<br>
configuration that you're not fixing that make you think so. And, when<br>
fixed, your system will work properly without having to force a value<br>
for the setting.<br>
<br>
Mike</blockquote><div><br></div><div>Is there still the playing ISO over Storage Group issue? </div></div>