SageTV V4.1.14 Release Candidate Is Available

[bcjenkins]

When I looked at SystemInformation it states the Sage version is 4.1.13.87 STV is 4.1.14.0.

Just me?

B

[michelkenny]

Originally Posted by k9k9

What's the difference between Placeshifting and the Webserver functions?

I know placeshifting requires another license, but I'm thinking more along the lines of functionality...

The Placeshifter is a full client interface designed to reencode the data dynamically for use over the Internet.

[michelkenny]

Originally Posted by Narflex

Extender Updates
1. Fixed bug where the STV selection wasn't getting remembered for the MVP or Placeshifter (we mean it this time)

Well I upgraded to 4.1.14 and I can say that I don't get this problem anymore. Good job

[Opus4]

Originally Posted by bcjenkins

When I looked at SystemInformation it states the Sage version is 4.1.13.87 STV is 4.1.14.0.

It is v4.1.14; sometimes minor things like a version number change get missed.

- Andy

[Hector]

What constitutes a Release Candidate is largely a matter of semantics depending on the (development) shop.It's not a really a matter of being bug free or even thinking they're bug free. Sage developers are not so naive as to think such a huge project on so many disparate machines/cards/stbs is going to be bug free, it just means issues they can live with in a product release. Sage plays a lot looser with the term 'Release Candidate than say our shop does but I honestly don't think they believe their first RC to be an ACTUAL release candidate, I think to them its more of a way of determining which issues need to be set to the side and which need to be addressed before release. When you say you're planning to release something believe me the you'll find out where the current pain is. Regardless of how they label the deliverables of their development cycle, they are an excellent shop.

[ToxMox]

Did anything change in the conflict resolution in this version? I experienced a conflict for the first time in forever with my 6 encoders. Strange thing is that it could have (and previously would have) resolved itself. The weirdest part is that the conflict didn't appear until 30 minutes before the conflict was about to happen. Back when I didn't have as many tuners the conflict icon would pop up at least a week beforehand. The conflict tonight could have easily resolved itself in a number of ways with repeat airings of at least two shows it was recording all of which are in the guide data already. Two of them within 6 hours of the conflict were being repeated. I then tried to resolve the conflict by telling it to record one show over the other then the conflict changed to another show at the same time and then I fixed that one at which point it finally fixed itself and is recording one of those repeat airings on later tonight.

Just thought it was strange. I have no logs for this.

[Narflex]

ToxMox (love the new avatar, LOL...if it's not new, then this is the first time I finally looked at it closely)

Nothing changed in conflict resolution lately. There are extreme cases when the scheduler may not be able to fit everything in even though it is possible; but as you noticed they are extremely rare. I'm not going to get into any theory about that because it's proprietary as you'd imagine.

[ToxMox]

Originally Posted by Narflex

ToxMox (love the new avatar, LOL...if it's not new, then this is the first time I finally looked at it closely)

Nothing changed in conflict resolution lately. There are extreme cases when the scheduler may not be able to fit everything in even though it is possible; but as you noticed they are extremely rare. I'm not going to get into any theory about that because it's proprietary as you'd imagine.

Thanks about the avatar Not new though...had it since shortly after creating my account and noticed all the cat avatars (EDIT: I guess shortly isn't right. According to the file date on the avatar I saved it in August of 2004)

I'll report more about the conflict stuff if it happens again. I'm only concerned that it only gave me about 20 minutes to fix the conflict.

[Narflex]

It may have only given you 20 minutes because that might have been all it had. The data could have changed at that point due to an EPG download so it may have had to re-evaluate the schedule at that point.

[ToxMox]

I checked that. The EPG update happened around 5pm and the conflict appeared around 8:30pm

[Para]

Originally Posted by Narflex

Placeshifter Updates
1. Optimization to the placeshifter transcoder

One step forward..two steps back

I wonder if the optimization broke my MVP transcoding?

The VOB transcoding to the MVP was working in 4.1.11 , broken in 4.1.12 , fixed in 4.1.13 , and now is out of sync with the video in 4.1.14 .

All of my VOBs appear to have a 3 to 4 second delay in the audio when being transcoded to the MVP. FF/RW will ocasionally get it in sync, but rarely.

Anyone else?

EDIT: 4.1.13 was checked again and was also out of sync

[Polypro]

email betatest at sagetv.com



P

[Para]

Originally Posted by Polypro

email betatest at sagetv.com



P

That was done already.

I was interested if I was the only one who had noticed that problem?

[edbmdave]

When ever I try to abring up the options menu (ESC or Cntrl+O) the Placeshifting client just ends.

Also for the transcoded video to the extenders, is there a way to have it respect source aspect ratio? ie instead of reformating a 16x9 to fit 4:3 and having it expand the vertical portion, just have it fit to width and leave the vertical portion unexpanded, filling the delta with black or something???

I love the sage extenders but watching a 16:9 movie that is letterboxed even at 16:9 reformated and expanded for 4:3 is hard. everything is really elongated.

[antplugger]

Is anyone using this version with DVB-T - Is it OK to upgrade from 4.1.12 ?

Thanks

[peterjb]

Originally Posted by antplugger

Is anyone using this version with DVB-T - Is it OK to upgrade from 4.1.12 ?

Thanks

I've tested the DVB-T support in 4.1.14 using both a Nova-T ( pre Aug 2004 ) and a FusionHDTV DVB-T USB device. Thanks to the efforts of Qian ( ) and various other people beta testing their butts off - It works very well!

I'm not sure why DVB-T support is still classified as beta.. Other than you still have to edit the frq file by hand

Cheers

Peter

[Lucas]

Originally Posted by antplugger

Is anyone using this version with DVB-T - Is it OK to upgrade from 4.1.12 ?

Thanks

I had DVB-T working fine with 4.1.12.

I skipped 4.1.13 since there was a warning that DVB-T would not work.
Installed 4.1.14 and DVB-T is not working (2x Technotrend 1300 DVB-T).
When I select a DVB-T channel I get a "No Signal" Message Box.

Rolled back to 4.1.12 and everything was fine...

Now that I am thinking about it, I may check to make sure that the 4.1.14 install does not ovewrite the .frq files.....

[nielm]

Originally Posted by Hector

What constitutes a Release Candidate is largely a matter of semantics depending on the (development) shop

With Sage, I believe it means no more new features, only bug-fixing...

[peterjb]

Originally Posted by Lucas

I had DVB-T working fine with 4.1.12.

I skipped 4.1.13 since there was a warning that DVB-T would not work.
Installed 4.1.14 and DVB-T is not working (2x Technotrend 1300 DVB-T).
When I select a DVB-T channel I get a "No Signal" Message Box.

Rolled back to 4.1.12 and everything was fine...

Now that I am thinking about it, I may check to make sure that the 4.1.14 install does not ovewrite the .frq files.....

The problem that you had with 4.1.14 was probably due to the change in format of the frq files. They now need to look something like the one below:

#DVBT channel setup table ver 2.0, country:
loaded predefined freq table: 0 channel freq
total_channel:12
#ch:index onid tsid program_id freq band 0 ctrl_bits(1:enable; 0:disable)

ch:1 0 0 529 205625 7 0 1 # ABC
ch:2 0 0 530 205625 7 0 1 # ABC2
ch:3 0 0 528 205625 7 0 1 # ABC HD
ch:4 0 0 2374 226500 7 0 1 # Prime
ch:5 0 0 2400 226500 7 0 1 # Prime HD
ch:6 0 0 1 219500 7 0 1 # WIN
ch:7 0 0 10 219500 7 0 1 # WIN HD
ch:8 0 0 2055 177500 7 0 1 # SC10
ch:9 0 0 2087 177500 7 0 1 # SC10 HD
ch:10 0 0 849 543500 7 0 1 # SBS Digital 1
ch:11 0 0 850 543500 7 0 1 # SBS Digital 2
ch:12 0 0 848 543500 7 0 1 # SBS HD

I had a similar issue myself when I installed 4.1.13

Cheers

Peter

[antplugger]

Excellent news on the DVB support again - You guys rock - Thanks a bunch -