John Andersen wrote:
I was under the impression that ext3 was ext2 under the skin and was
2gig max. But the last time I used it was a gazillion years ago
so what do I know... ;-)
Yeah, it must have been a gazillion years ago... ;)
With 1KiB blocksize, ext2/ext3 gives a maximum 16GiB file
Jake wrote:
i think that if the video dir is mounted locally myth will try to use
that first and stream over the myth protocol as a last resort. i seem
to remember reading about this in the past but maybe i'm way off.
Nope. You're not way off. :) (Your statement is correct.)
Mike
__
> I have mine mounted so I can use nuvexport on both machines.
>
> I thought Myth always did it's own streaming, regardless of whether the
> backend drive is mounted somehow. Unless there's something I don't know,
> the filesize limits shouldn't be an issue, right?
i think that if the video dir
On 12/11/05, Jordack <[EMAIL PROTECTED]> wrote:
I don't remember why. I set it all up a while ago andI think there was a reason. It was only a minornuisance so I never tried to play with it.Guess Ill take another look at it, if I can ever getthe girlfriend to stop watching her Buffy recordings
--
I don't remember why. I set it all up a while ago and
I think there was a reason. It was only a minor
nuisance so I never tried to play with it.
Guess Ill take another look at it, if I can ever get
the girlfriend to stop watching her Buffy recordings
--- Jake <[EMAIL PROTECTED]> wrote:
> On 1
On 12/11/05, Jordack <[EMAIL PROTECTED]> wrote:
> I have been having the same problem for a long time
> now. Luckily most of my recordings are only an hour
> but it is still frustrating.
>
> It only happens on the remote front end. If I play
> the recording on the back-end I don't have the
> prob
I have been having the same problem for a long time
now. Luckily most of my recordings are only an hour
but it is still frustrating.
It only happens on the remote front end. If I play
the recording on the back-end I don't have the
problem.
I'm mounting the /video volume on the front end with
I was under the impression that ext3 was ext2 under the skin and was2gig max. But the last time I used it was a gazillion years ago
so what do I know... ;-)That would be news to me! I'm using ext3 on my LVM partition and have plenty of large files:/dev/mapper/vg-myth ext3 441G 42
On 12/11/05, John Andersen <[EMAIL PROTECTED]> wrote:
I was under the impression that ext3 was ext2 under the skin and was2gig max. But the last time I used it was a gazillion years agoso what do I know... ;-)
Okay but still, it's not live tv (so no ring buffer), it works fine on
the local fronte
On 12/10/05, Andrew Freeman <[EMAIL PROTECTED]> wrote:
> I see where you're going
> with this and no, I don't see how it could be a file size limitation
> problem.
I was under the impression that ext3 was ext2 under the skin and was
2gig max. But the last time I used it was a gazillion years ago
On 12/10/05, John Andersen <[EMAIL PROTECTED]> wrote:
Isn't that about the time the ringbuffer approaches 2gig?What is your ring buffer size in mythtv-setup?What filesystem?
Isn't the ring buffer for live tv? This is happening with
pre-recorded programs. The filesystem on the backend is
ext3. I
On 12/10/05, Andrew Freeman <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Like the subject line says, it just doesn't work. It will change the
> displayed time index but the running video does not change at all, apart
> from some artifacting.
Isn't that about the time the ringbuffer approaches 2gig?
Hello,
Like the subject line says, it just doesn't work. It will change
the displayed time index but the running video does not change at all,
apart from some artifacting. Although the video will continue on,
essentially "in the background", while it's garbling up the screen for
that second or t
13 matches
Mail list logo
