Day one features

[davidb]

Question 1:
I am trying to do just what you asked to start watching on Sage, and continue on IOS(Ipad or Iphone), and restart on Sage and keep the watched time.

I have this working on TV shows that have been recorded, but it is not working on DVDs. I can get the watched spot in milliseconds into the movie, but all attempts to SetWatchedTimes like I use, that works properly on a TV Show, does not set the time on the DVDs, it jumps off the end and sets it as watched. It may be moving the watched spot, but I have not been able to come up with parameters for DVDs that will actually set the watched spot at a certain point in a DVD.
Has anyone used this, or possibly have any code snippets that work to set the watched time on a DVD to a certain spot??

// Use these two object instances
Object mediafile = MediaFileAPI.GetMediaFileForID(IDOfShowOrDVDHere);
Object airing = MediaFileAPI.GetMediaFileAiring(mediafile);

Here is how I currently get the information for a TV showWorking)

long whereToRestartAtHowManyMS = whereToRestart - AiringAPI.GetAiringStartTime(Airing); //works on tv

long whereToRestartAtHowManySeconds = whereToRestartAtHowManyMS / 1000;
long RealStartTime = AiringAPI.GetRealWatchedStartTime(Airing); //works on TV

Here is how I currently set the information for a TV showWorking)

// to set an Absolute Time in seconds into the TV show
AiringAPI.SetWatchedTimes(Airing, AiringAPI.GetAiringStartTime(Airing)+(AbsoluteTimeinSeconds*1000), RealStartTime);

//Here is how I currently set the information for a TV Show To bump up by //xx seconds into the TV show from the watched spot

AiringAPI.SetWatchedTimes(Airing, AiringAPI.GetAiringStartTime(Airing)+(whereToRestartAtHowManySeconds * 1000)+BumpUpTimeinSeconds*1000, RealStartTime); //tv shows works

NOTE: The following IS different than the TV Show, as the watched information comes back very differently from the same API calls:

Here is how I currently get the information for a DVD: (Working)
long whereToRestartD = AiringAPI.GetWatchedEndTime(Airing);
long whereToRestartDAtHowManyMS = AiringAPI.GetWatchedEndTime(Airing);
long whereToRestartDAtHowManySeconds = whereToRestartD / 1000;
Here is how I tried to set the information for a DVD: (NOT working)
for Absolute set to position:
AiringAPI.SetWatchedTimes(Airing, AiringAPI.GetAiringStartTime(Airing)+(AbsoluteTimeinSeconds*1000), RealStartTime);

for Bump up by xx seconds:
AiringAPI.SetWatchedTimes(Airing, AiringAPI.GetAiringStartTime(Airing)+AiringAPI.GetWatchedDuration(Airing)+BumpUpTimeinSeconds*1000, AiringAPI.GetAiringStartTime(Airing));

The following works to determine If it is a TVShow
if (MediaFileAPI.IsTVFile(Airing) == true)

The following works to determine IF it is a DVD
if (MediaFileAPI.IsDVD(Airing) == true)
------------------------------------------------------------------------------
Question 2:
I couldn't find anything in the API to get the length of a DVD. But I did find it stored in the properties file, in RunningTime.
Do all Sage7 installs use the .properties file for media, or is this only available on some? Can I assume there will be a .properties file for each recording and DVD?

Thanks for any help.

Originally Posted by Slugger

For #2, I'm pretty sure you can already read and write the watched times of an airing:

http://download.sage.tv/api/sage/api/AiringAPI.html

Have a look at GetWatchedDuration, GetWatchedEndTime, GetWatchedStartTime, and SetWatchedTimes.

Based on those api calls, it should already be possible for another source (i.e. Plex) to read and write this data back to Sage. In theory, Plex could read this data to implement the "start watching on Sage in the living room and finish watching on your tablet from where you left off". And vice versa: Watch a recording in Plex and Plex reports back to Sage what you watched; Sage then picks up where you left off. From what I've read about the Plex plugin here in the past is that the hard part is getting Plex to talk to Sage's API -- just not all that easy, which is why the Plex plugin never even managed to sync watched status, much less this kind of data. But it doesn't seem to be Sage preventing this kind of thing from happening.

[stanger89]

I'm pretty sure that stuff doesn't work on DVDs. DVDs don't have a "length" since there are menus that loop, different titles, etc, they're effectively of infinite/variable length.

[LWM4P]

After just general updating of the application... my vote is the following:

- Touchscreen interface. I can install sage on a windows tablet, but no touchscreen. I guess any mobile client would be ok here...
- Lots of work needs to be done on the music interface. We use sage on the main TV for viewing, but we also have a tablet mounted in the kitchen. In the kitchen, we do watch some TV (or bring up recipes etc..), but we mostly play music! This same tablet is connected to the speakers on the back porch too. This could include music streaming services, but also just general updating of usability in the UI.
- There was a cool program a while back called TASageTV. That was pretty cool, but always a little finicky, so I stopped using it. I would love for the mobile client to have the ability to change the music on my tablet in the kitchen, while I am sitting outside having a beer (since the kitchen tablet drives the outdoor speakers).

[Fuzzy]

Originally Posted by LWM4P

After just general updating of the application... my vote is the following:

- Touchscreen interface. I can install sage on a windows tablet, but no touchscreen. I guess any mobile client would be ok here...
- Lots of work needs to be done on the music interface. We use sage on the main TV for viewing, but we also have a tablet mounted in the kitchen. In the kitchen, we do watch some TV (or bring up recipes etc..), but we mostly play music! This same tablet is connected to the speakers on the back porch too. This could include music streaming services, but also just general updating of usability in the UI.
- There was a cool program a while back called TASageTV. That was pretty cool, but always a little finicky, so I stopped using it. I would love for the mobile client to have the ability to change the music on my tablet in the kitchen, while I am sitting outside having a beer (since the kitchen tablet drives the outdoor speakers).

None of these things in any way are affected by SageTV being open source. That is all in the realm of what has been possible since SageTV v4.

[LWM4P]

Originally Posted by Fuzzy

None of these things in any way are affected by SageTV being open source. That is all in the realm of what has been possible since SageTV v4.

That is great man... sounds like the problem is execution. Who cares if it was possible, someone has to make it happen. I thought that was the point of this thread... and I am totally on board! I am trying to get some ideas going on what is next

[stanger89]

Not to be too pedantic, but there's really only one "Day One" feature that's needed possible, and that's installers with the licensing code removed. Hopefully that's what Jeff will give us but either way, those are blocking problems, without which there's nothing to build on.

After that, Day 2, etc development and new features can start. It's not like people have been working on this from behind the scenes to where at launch there will be completed features to use.

[mrsupport]

Originally Posted by stanger89

Not to be too pedantic, but there's really only one "Day One" feature that's needed possible, and that's installers with the licensing code removed. Hopefully that's what Jeff will give us but either way, those are blocking problems, without which there's nothing to build on.

After that, Day 2, etc development and new features can start. It's not like people have been working on this from behind the scenes to where at launch there will be completed features to use.

+1

[tmiranda]

I wonder if Jeff will open source the server side code that runs the plugin manager. There's been lots of talk about when/if the EPG data ends but nothing about the plugin manager. I know we can edit the plugin file but losing the plugin manager would be bummer.

I'd also like the ability to use multiple plugin repositories instead of one.

[Fuzzy]

all the plugin manager really needs is a web presence it seems. As far as I can tell, the entire 'plugin service' is a single XML file hosted on an HTTP server.

[tmiranda]

Originally Posted by Fuzzy

all the plugin manager really needs is a web presence it seems. As far as I can tell, the entire 'plugin service' is a single XML file hosted on an HTTP server.

The trick is figuring out what's in that XML file

The plugin manager does several things including:

1. Verifies manifests and does some basic sanity checking before accepting them.
2. Makes sure only the owner of a plugin updates it.
3. Merges the plugin manifest into the plugins XML file. (Removing the old manifest too in the case of an updated plugin.)
4. Serves up the plugin XML file every time somebody navigates to the plugin manager menu.

It probably does other things as well I can't think of off the top of my head. None of this is rocket science and it all can be reproduced, but what a waste of time. It would be a lot easier if the code was released.

[Fuzzy]

Right, that's all basic database management tasks, and relatively simple. You can see what's in the XML file if you're intersted, it's in your SageTV folder, called SageTVPlugins.xml

[tmiranda]

Originally Posted by Fuzzy

Right, that's all basic database management tasks, and relatively simple. You can see what's in the XML file if you're intersted, it's in your SageTV folder, called SageTVPlugins.xml

I know exactly what's in there I'm talking about the code that gets it in there.

[sdsean]

Man just logged on to check in, and found out about this news. . . so stoked!

Any way for me there is lots of stuff I want, but the very 1st thing IMHO that should be done is get a build working for 64Bit JVMs (even if it is Java 7), so that we can have a larger memory heap.

So simple. . and will solve / remove quite a few headaches :P

[Pumpkinhead]

Well, the same one feature I've been wanting for several years, it would be great if it makes it to Open SageTV.

Removing the "junk" from the regular Program Guide:

http://forums.sagetv.com/forums/showthread.php?t=21651

And of course, the free EPG service.

[Fuzzy]

Originally Posted by sdsean

Man just logged on to check in, and found out about this news. . . so stoked!

Any way for me there is lots of stuff I want, but the very 1st thing IMHO that should be done is get a build working for 64Bit JVMs (even if it is Java 7), so that we can have a larger memory heap.

So simple. . and will solve / remove quite a few headaches :P

It's discussed, but it's not as simple switch. It will likely break most native code that calls to 32 bit libraries, like directshow payback, and internal tuners. Google Fiber, instead of going to 64 bit, breaks each client instance into its own 32 bit JVM, which I'd likely what we'd do here.

[Fuzzy]

Originally Posted by Pumpkinhead

Well, the same one feature I've been wanting for several years, it would be great if it makes it to Open SageTV.

Removing the "junk" from the regular Program Guide:

http://forums.sagetv.com/forums/showthread.php?t=21651

And of course, the free EPG service.

nothing about sage going open source will affect UI changes any differently. That feature could be made just as easily right now, without sage every going open source, just no one has taken the time to do it.

[bigbill]

It would be great if their new encoding could be recorded by SageTV!! The 6-7 Gigs per hour are getting very old.

[wayner]

Originally Posted by Fuzzy

Google Fiber, instead of going to 64 bit, breaks each client instance into its own 32 bit JVM, which I'd likely what we'd do here.

If that happens then how much memory would you want to have if you wanted to run 8 extenders. Would you want 8GB just for JVMs (8X1GB) or would you be able to get by with something like 512MB for each JVM as it only needs to support one extender?

[Fuzzy]

Originally Posted by wayner

If that happens then how much memory would you want to have if you wanted to run 8 extenders. Would you want 8GB just for JVMs (8X1GB) or would you be able to get by with something like 512MB for each JVM as it only needs to support one extender?

The footprint of each extender host instance would have the same duties and responsibilities as an instance of SageTVClient. My main use client, with gemstone and many other features, and about 8 weeks of uptime right now, is using 701MB of JVM. I see no reason not to set 1GB for each of the JVM's, if chunks aren't used, windows will swap them out to disk anyway. If you aren't using all the extenders at the same time, then the unused instances will be swapped out. In any case, RAM is ridiculously cheap these days, and I haven't built a machine with <12GB in a very long time.

[wayner]

Ok, I will plan on 16 GB for my next generation Sage server.