Theme: blue neon night

[speechles 2055]

@@speechles

 

I am running server 3.1.0.0

 

I restarted the server process and still no content. Even restarted the Ultra.

Looked in the debug log and got a headache.

 

This may just work itself out for me as yours is working, no biggie.

 

The x265 is isolated to that batch of content.

I figured that would be the case.

I am still running 3.0.8200.0 .. lol

 

Let me update to the newest flavor.

 

Okay, I am now on 3.1.0.0 and updated lots of plugins. My continue watching is still the same. Populates the same items as did before.

 

@@Luke is there a difference updating from 3.0.8200 directly to 3.1.0? Is there an update in between I missed that makes a difference here? Seems weird it works for me, and not mikeraburn. I am confused now.. lol

 

Sent from my Nexus 7 using Tapatalk

[speechles 2055]

@@mikeraburn

    if Ty = 0
        query.AddReplace("filters", "IsResumable")
        query.AddReplace("sortby", "DatePlayed,SortName")
        query.AddReplace("sortorder", "Descending")
    else if Ty = 1
        query.AddReplace("filters", "IsFavorite")
        query.AddReplace("sortby", "SortName")
        query.AddReplace("sortorder", "Ascending")
    else
        query.AddReplace("ExcludeLocationTypes", "Virtual")
        query.AddReplace("sortby", "DateCreated,SortName")
        query.AddReplace("sortorder", "Descending")
    end if
    query.AddReplace("fields", "ItemCounts,Overview,PrimaryImageAspectRatio")

Ty = type

0 = Continue Watching (aka resume)

1 = Favorites

2 = Latest

 

This is always used with an "&IncludeItemType=XXX" (where XXX is "movie", "episode", "series", etc) to group rows by type, along with "&recursive=true" to flatten each item in the row. Does your favorites tile work and populate all the items?

Edited December 20, 2016 by speechles

[mikeraburn 71]

Yes favorites "tile" at library AND the Zelda heart populate.

 

I tossed in both because I am not sure what you mean by "tile".

[mikeraburn 71]

Don't worry about this.

It is not a big deal, really.

 

TapTalk

[speechles 2055]

Haw.. if it doesnt work it is an issue. For every one person reports the problem, assume others have the same problem, but arent reporting it. So it is more than just you, sir. It is just you are "super cool like that" and tend to help play "spot the bugs". I appreciate your input when things work, and especially when they dont.

 

This might be related to the merging of userdata into the main library db? It is weird because if your favorites "zelda heart" works it should also work for continue watching. The only difference between the two is the isFavorite vs isResumable and the sort-order/sort-by. You are like the sounding board and right now its not sounding good.. lol

 

So please bear with me through all this. You may need to use the "clean database" task and let it finish. Maybe there is something holding up resumables from showing up. Aftet the db clean, rescan the full library to 100%. After this if you still have an issue with it, please come back and say so. I want everything in the app to work for everybody. Thanks.

 

Sent from my Nexus 7 using Tapatalk

Edited December 20, 2016 by speechles

[mikeraburn 71]

You realize who you are talking to.

Clean database isn't jumping out at me.

I need a shove in that direction, plz.

 

 

TapTalk

[mikeraburn 71]

Found it in scheduled tasks.

One ran 23 hours ago taking 4 secs

 

TapTalk

[mikeraburn 71]

Running it now.

 

Took 36 secs

 

TapTalk

Edited December 20, 2016 by mikeraburn

[mikeraburn 71]

All done with the rescan.

 

No joy.

 

Maybe a full uninstall and reinstall of the server program won't hurt.

Stuff happens after a while and gets goofed up.

 

 

Remember the images you all were taking about in ULTRA?

I've never had those.

 

---------

 

 

It didn't want to uninstall easy but it was pryed out.

 

 

Reinstalled and running the dreaded library's scan....

Edited December 20, 2016 by mikeraburn

[speechles 2055]

@@mikeraburn I wish I knew what was causing it. Does the "resume" toggle on the Movies and TV rows show items? This toggle is using the exact same http call as continue watching makes. It would be interesting to know if one works and the other doesnt.

 

Is anyone else experience problems when using the "continue watching" button on the options row?

 

Sent from my Nexus 7 using Tapatalk

[mikeraburn 71]

The only thing that wasn't working was the continue watching button on the options row.

 

I'll let you know if a fresh server install worked.

 

My money is on me having a goofed up old install.

 

TapTalk

[mikeraburn 71]

My fresh install seems to have corrected my issue with continue watching on the options bar. So far

 

TapTalk

Edited December 21, 2016 by mikeraburn

[mikeraburn 71]

How to I get rid of the FOLDERS section now???

 

TapTalk

[Happy2Play 9780]

How to I get rid of the FOLDERS section now???

 

TapTalk

 

On the Server go to Dashboard-Library-Display.

[mikeraburn 71]

On the Server go to Dashboard-Library-Display.

Thanks, I was in the user profile trying EVERYTHING.

 

TapTalk

[mikeraburn 71]

I think I may be confused.

 

Is continue watching suppose to behave as suggested?

 

If NOT, then there was never an issue.

[speechles 2055]

I think I may be confused.

 

Is continue watching suppose to behave as suggested?

 

If NOT, then there was never an issue.

Suggested is different, yep. *DOH!*

 

For movies suggested is using the /recommendations (aka because you..) endpoint. For TV suggested uses the /nextup api call. These are the only library types that allow these endpoints.

 

Continue watching uses /items with a filter=isResumable. This is supposed to be a "one stop" screen for all items in your library that can be resumed. It sorts them by date watched in descending order so the items shown are in reverse chronological order. So the last items you have partially watched will start off at front of the row.

 

I can whip up a suggested screen, to go along with the others(favorites,continue watching,latest). This would show suggestions based on "because you..." for movies. There would be 6 categories of 25 items. Each category its own row. Then below this are rows for each TV library you have and these display the nextup of each. This would make it quicker to get to, so you dont always have to move the toggles around.

Edited December 21, 2016 by speechles

[mikeraburn 71]

Sorry about the drama!

 

I swear that the continue watching WAS acting as a suggested in my goofed up system.

It was following the series that I was watching. No episodes were partially viewed either.

[doonze 30]

I was so excited when I learned about this app, however once it installed the first thing it did was to tell me login invalid the second I clicked on any of my users. I even did a manual server connection. Same. So I did the whole emby connect thing. Now it just says can't update capabilities or whatever the message is when it can't let the server know what it can do. And back or OK just crashes to home screen.... Help? Can't do nothing now.

 

Oh, this is a Roku TV, you know with a Roku built in....

Edited January 12, 2017 by doonze

[speechles 2055]

I was so excited when I learned about this app, however once it installed the first thing it did was to tell me login invalid the second I clicked on any of my users. I even did a manual server connection. Same. So I did the whole emby connect thing. Now it just says can't update capabilities or whatever the message is when it can't let the server know what it can do. And back or OK just crashes to home screen.... Help? Can't do nothing now.

 

Oh, this is a Roku TV, you know with a Roku built in....

You need to remove the app, to clear the app registry. Then add it back, this will make it ask you to set it up again. A clean slate.

 

Make sure to use "skip" on the connect/pin screen, then choose "add new server" if your server isnt listed. If your server is listed, choose it. After you pick a user it might say, "Failed to get user profile". Once it does this, press the HOME button on the remote. Now start the app again, and it should let you choose your server and user again. This time it will work. The app defaults to remember user. I never figured out why it sometimes fails to authenticate on first try.

 

The fact it cannot update capabilities means the session is invalid. This is why it would crash, the app depends on a session id to allow other users to join your session using "also watching". If you press HOME to exit the app and restart it this should fix it. On restart the app gets a valid session id with its device id.

 

If you use the pin/connect method do not use "sign out" to change users. The pin/connect method is tied to a single user only. You must use "change server" to change users if using pin/connect. Just FYI.

Edited January 12, 2017 by speechles

[doonze 30]

You need to remove the app, to clear the app registry. Then add it back, this will make it ask you to set it up again. A clean slate.

 

Make sure to use "skip" on the connect/pin screen, then choose "add new server" if your server isnt listed. If your server is listed, choose it. After you pick a user it might say, "Failed to get user profile". Once it does this, press the HOME button on the remote. Now start the app again, and it should let you choose your server and user again. This time it will work. The app defaults to remember user. I never figured out why it sometimes fails to authenticate on first try.

 

The fact it cannot update capabilities means the session is invalid. This is why it would crash, the app depends on a session id to allow other users to join your session using "also watching". If you press HOME to exit the app and restart it this should fix it. On restart the app gets a valid session id with its device id.

 

If you use the pin/connect method do not use "sign out" to change users. The pin/connect method is tied to a single user only. You must use "change server" to change users if using pin/connect. Just FYI.

Ok, so I uninstalled and reinstalled. I can get back in the app now, however I have the same problem.

 

It has no problem finding my server, it shows all my users on startup. However, I still get "Authentication Error! Invalid username or password" I click ok and it says "Login Failed Invalid username or password. Please try again."

 

When this happens I see this in the log (Just the important parts I think, I can post the entire log if you like)

 

System.ArgumentNullException: Value cannot be null.

    Parameter name: appName

     at Emby.Server.Implementations.Session.SessionManager+<LogSessionActivity>c__async1.MoveNext () [0x00037] in <94cb9849d4534920b1b6cc233e9f2dbd>:0

    --- End of stack trace from previous location where exception was thrown ---

     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <8f2c484307284b51944a1a13a14c0266>:0

     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <8f2c484307284b51944a1a13a14c0266>:0

     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <8f2c484307284b51944a1a13a14c0266>:0

 

 

Seems the app isn't sending it's name? 

[ebr 16178]

Ok, so I uninstalled and reinstalled. I can get back in the app now, however I have the same problem.

 

It has no problem finding my server, it shows all my users on startup. However, I still get "Authentication Error! Invalid username or password" I click ok and it says "Login Failed Invalid username or password. Please try again."

 

When this happens I see this in the log (Just the important parts I think, I can post the entire log if you like)

 

System.ArgumentNullException: Value cannot be null.

    Parameter name: appName

     at Emby.Server.Implementations.Session.SessionManager+c__async1.MoveNext () [0x00037] in :0

    --- End of stack trace from previous location where exception was thrown ---

     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in :0

     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in :0

     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in :0

 

 

Seems the app isn't sending it's name? 

 

 

Hmmm.... exact same problem as here - also on a Roku TV.  What is your exact firmware version?

[doonze 30]

Software version WAS 7.5.0.4101. When looking for it, it found a new update (I had checked the day I posted about my issue, so it's brand new) the new version is now 7.5.0.4111. Problem is still there. 

 

In other news, the official Emby app is now freezing and causing a reboot of the TV when playing music. But I'll post that over in the app thread.

 

Also, here's some more log info:

 

2017-01-19 15:48:44.7234 Info App: Udp message sent to 192.168.0.9:32934
2017-01-19 15:48:44.8932 Info HttpServer: HTTP GET http://192.168.0.111:8096/emby/system/info/public?format=json. UserAgent: Roku/DVP-7.50 (087.50E04111A)
2017-01-19 15:48:44.8966 Info HttpServer: HTTP Response 200 to 192.168.0.9. Time: 4ms. http://192.168.0.111:8096/emby/system/info/public?format=json
2017-01-19 15:48:45.1246 Info HttpServer: HTTP GET http://192.168.0.111:8096/emby/Users/Public. UserAgent: Roku/DVP-7.50 (087.50E04111A)
2017-01-19 15:48:45.1276 Info HttpServer: HTTP Response 200 to 192.168.0.9. Time: 3ms. http://192.168.0.111:8096/emby/Users/Public
2017-01-19 15:48:49.8745 Info HttpServer: HTTP POST http://192.168.0.111:8096/emby/Users/AuthenticateByName?format=json. UserAgent: Roku/DVP-7.50 (087.50E04111A)
2017-01-19 15:48:49.9290 Info UserManager: Authentication request for Justin has succeeded.
2017-01-19 15:48:49.9298 Info SessionManager: Reissuing access token: 2938894bce95413ab68202508b704792
2017-01-19 15:48:49.9353 Error HttpServer: Error processing request
    *** Error Report ***
    Version: 3.1.2.0
    Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -restartpath /usr/lib/emby-server/restart.sh
    Operating system: Unix 3.16.0.4
    64-Bit OS: True
    64-Bit Process: True
    Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 20:21:32 UTC 2016)
    Processor count: 2
    Program data path: /var/lib/emby-server
    Application directory: /usr/lib/emby-server/bin
    System.ArgumentNullException: Value cannot be null.
    Parameter name: appName
     at Emby.Server.Implementations.Session.SessionManager+<LogSessionActivity>c__async1.MoveNext () [0x00037] in <94cb9849d4534920b1b6cc233e9f2dbd>:0
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <8f2c484307284b51944a1a13a14c0266>:0
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <8f2c484307284b51944a1a13a14c0266>:0
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <8f2c484307284b51944a1a13a14c0266>:0 

 

I marked the part I found interesting in red. Seems it IS authenticateing fine, issuing a token, then getting an error? 

 

 

EDIT: 

I'm sure you can figure out from the logs, but I'm running on Linux, Debian Jessie, up to date.

Edited January 19, 2017 by doonze

[ebr 16178]

I think we've discovered this is related to an unusual character in the device name...

[doonze 30]

Is the fix in Emby, or BNN? Since I can't use BNN theme at this time, think I'm gonna try the Beta, seems I'm getting lots of practice in bug hunting right now anyway