Are we ever going to get rid of the "pause"? YES WE DID!

[matt91]

Originally Posted by evilpenguin

From Geektonic on v7
We can finally lay this nitpicking... I mean, very, very, very important topic to rest

Guess I should go vote in the poll now...

[sdsean]

WOOOO HOOOOO!!!! I'm so exicted!!

[stanger89]

What's everyone going to talk about now?

[MeInMaui]

Hey! Where did my pause go?!?! I preferred the old style and I have no need for this flashy no-pause thing. I better be able to disable this new "feature".

[stanger89]

Yeah:

"How do I know when the show ended now, nothing happens!?"

[OneOfMany]

Geez, now when is me and the wife gonna talk?

Grant

[Brent]

I'll miss that anticipation the crowd at my house gets when it pauses during that one, key play in the Superbowl game...

[reggie14]

Originally Posted by evilpenguin

From Geektonic on v7
We can finally lay this nitpicking... I mean, very, very, very important topic to rest

Out of curiosity, did this come at a cost? Namely, does commercial skipping still work on live TV recordings?

[peternm22]

Any idea how eliminating the pause works with network encoders like the R5000?

[bialio]

Comskip works fine. In fact its even a bit more accurate than it used to be thanks to some other V7 changes.

btl.

[stanger89]

Originally Posted by peternm22

Any idea how eliminating the pause works with network encoders like the R5000?

I think it depends on how the network encoder is coded. IIRC there's some specific stuff that it needs to support for it to work. My recollection is it's not terribly likely to work but that said, I've got an R5000 and haven't noticed a pause since the feature was added. Though I can't say with certainty I've actually run into a show change with my R5000 ( I really don't do much Live and Sage seems to prefer to use my HD PVR).

[wrems]

Does anyone know how they tackled the pause? I mean, from what I gathered it was a permanent and basically necessary evil based on the whole client server architecture. I know much talk was around implementation of circular buffers and such, but does anyone know for sure what they ended up doing to change this???

[stanger89]

They haven't changed the recording engine or anything, not functionality wise. I don't know what they did as far as like code goes, but the effect is that the switch between files for back to back recordings is now instant.

[peternm22]

Originally Posted by stanger89

I've got an R5000 and haven't noticed a pause since the feature was added.

With the R5000, whenever a new recording starts it typically takes a few seconds for it to "acquire" the stream. Do you see this happening in the R5000 app?

Thanks.

[Fuzzy]

really would depend on the way sage talks to the network encoders now. It used to just tell the encoder what channel to tune to, and what file to write too. for the new system, it would have to tell it to write to a temporary file that sage then split up.

[stanger89]

Originally Posted by peternm22

With the R5000, whenever a new recording starts it typically takes a few seconds for it to "acquire" the stream.

That's inevitable, it takes a moment for the STB to switch satellites/transponders. I never watch the R5000 app, but yes it takes a moment for the stream to start the first time.

Like I said, I've not payed enough attention to confirm that the R5000 network encoder supports the seamless splitting.

[sleonard]

Originally Posted by Geektonic

Increased stability of Hauppauge HD-PVR - Enhancements to workaround Hauppauge HDPVR instabilities on Windows

I hope this also includes some sort of explanation (however brief) of what the actual issues are with the HD-PVRs and how they (Sage and/or Hauppauge) have overcome them. I'm assuming they know a lot more about it than what's in our postings in the hardware forum.

S

[babgvant]

Originally Posted by wrems

Does anyone know how they tackled the pause? I mean, from what I gathered it was a permanent and basically necessary evil based on the whole client server architecture. I know much talk was around implementation of circular buffers and such, but does anyone know for sure what they ended up doing to change this???

The problem isn't rooted in the C/S arch.

Originally Posted by babgvant

My guess is that they approach the issue with their custom source filter, feeding it a "playlist" of the different segments and it concatenates the bits from multiple files into a "virtual file" before feeding it to the demultiplexor similar to how a DVD navigator "merges" vob files for seamless playback.

The source filter was extended to handle new files as part of the same stream.

Originally Posted by babgvant

If my guess is correct, this is a technical barrier to eliminating pauses in live tv not only because of the differences in codecs (h.264/aac/ac-3/mpeg2/mpa) and containers (mpeg-ps, mpeg-ts) supported by the different types of tuners Sage uses, but also because different channels of the same type (i.e. ATSC) can present the data streams differently. All of the components, many of which are not Sage controlled, would need support these kinds of changes to work in this scenario. Keep in mind you can't swap decoders and keep the same graph running.

The pause only goes away for recordings that don't violate these rules.

[mmanville]

Originally Posted by evilpenguin

From Geektonic on v7
We can finally lay this nitpicking... I mean, very, very, very important topic to rest

Thank god SageTV is more is more interested in customer feedback & satisfaction than you are, that they don't just dismiss what a very large majority of what their users tell them with snide comments about how its the CUSTOMER that's the problem, not their application.

Way to go SageTV! Evilpenguin? Not so much.

[babgvant]

Originally Posted by mmanville

Thank god SageTV is more is more interested in customer feedback & satisfaction than you are, that they don't just dismiss what a very large majority of what their users tell them with snide comments about how its the CUSTOMER that's the problem, not their application.

Way to go SageTV! Evilpenguin? Not so much.

Was that really necessary? Why don't you extend the same anecdotal overlay of preference (which you obviously embrace) to those who disagree on the severity of "the pause".