Dev build 191

[Abobader 3464]

Also with Vimeo, the poster view not good.

[Luke 42077]

That wall of Twit images looks pretty cool though.

[Abobader 3464]

Indeed buddy

[Yogi 367]

Also 1 more thing with the dev build,I have assigned a primary image to the channel but iti is not showing in MBC on the EHS.

[Sharmy 9]

Yogi. Did you put the image in the Inagesbyname folder? Working fine for me. Only issue I have is that the channels RAL is blank.

Edited June 8, 2014 by Sharmy

[Yogi 367]

With Vimeo as well:

 

 

This is happening with all channels and trailers will not play as well.

 

WMC Log:

wmc.txt

 

MBC Log:

MBClassic-8620143760f71cb150420fa25cc71715a46ad1.log

[ebr 16169]

Only issue I have is that the channels RAL is blank.

 

This is by design as there is no efficient way to get recent items out of channels right now.

 

I can't reproduce the crashes so will have to try and hunt that down.

[DGMayor 90]

So joining the fray here.   EBR gave me 173 yesterday and it fixed my issues of 163 not loading with the newer beta server. 

 

Then the server updated again to 3.0.5271.29451 and it broke MBC again ><

 

, I can select my user, but when it's showing the splash and starting to load is when it crashes now.   

 

The error doesn't show up in the logs, but on screen I see:

 

Entrypoint Error:

 

Media Browser could not launch.  Please be sure the server is running, awake and available on the network..

System.ArgumentNullException: Value cannot be null.

 

Parameter name: prefsld

 

at (and it grays out and just has the OK button after that)

Edited June 8, 2014 by DGMayor

[ebr 16169]

Something has obviously changed with channels that I need to adjust to.  I'll get to it later today.

[Abobader 3464]

Something has obviously changed with channels that I need to adjust to.  I'll get to it later today.

 

Well done buddy.

[DGMayor 90]

Also, the new item notification displays during playback.  EBR mentioned that this was by design.  I think it should at least be an option to turn on/off.  Wife and I were watching tv last night and I was updating some MP3 ID3 tags from my laptop...every few minutes the notification would pop up and take 1/3rd of the screen.  Needless to say the wife was annoyed.   

 

If it could be smaller and/or have less information during playback, that could work, otherwise I think on/off would be the best option if possible.

Edited June 8, 2014 by DGMayor

[ebr 16169]

Good day,

 

I confirm Yogi issue as well.

 

 

My best

 

 

I think I know what this is now... At the last minute before full release yesterday, the channel API was changed to use the "fields" parameter like the normal api.  This means I'm not getting the same information back from the responses that I was before and the display prefs ID is one of those items.

 

I couldn't reproduce it because I already made the adjustment to send the fields in my development version of MBC.  I'll put out a new dev release right now and, if I'm right, that should fix it for you guys.

 

Please let me know.

[Latchmor 584]

I think I know what this is now... At the last minute before full release yesterday, the channel API was changed to use the "fields" parameter like the normal api.  This means I'm not getting the same information back from the responses that I was before and the display prefs ID is one of those items.

 

I couldn't reproduce it because I already made the adjustment to send the fields in my development version of MBC.  I'll put out a new dev release right now and, if I'm right, that should fix it for you guys.

 

Please let me know.

 

It did 

[flexage 125]

@@ebr - Nice one dude!

 

I had just installed my VM as promised, and just after I'd started testing with Dev173 you pushed out 174 and all seems to work awesomely!

 

Still seeing the Null agrument Exception for the null "id" parameter in the server logs, but channel playback works just fine now

 

Don't know if you're already aware of the server logging an error on MBC trying to access Special Features on channels (when there are none), so didn't want to post a log if it's an issue you already know/don't care about/moot, lol

 

Great work and muchos gratitude in your direction

[Abobader 3464]

I think I know what this is now... At the last minute before full release yesterday, the channel API was changed to use the "fields" parameter like the normal api.  This means I'm not getting the same information back from the responses that I was before and the display prefs ID is one of those items.

 

I couldn't reproduce it because I already made the adjustment to send the fields in my development version of MBC.  I'll put out a new dev release right now and, if I'm right, that should fix it for you guys.

 

Please let me know.

 

 

Well done Ebr!

 

Build 174 fix the issue.

[ebr 16169]

Still seeing the Null agrument Exception for the null "id" parameter in the server logs, but channel playback works just fine now

 

You mean on the "Context" websocket message?  If so, I posted a request in the dev area for Luke to think about suppressing that or, at least, making it a warning or information message.

 

MBC reports context for each item as it gains focus.  The problem is, some of those items in MBC don't exist on the server.  Thus - the ID cannot be found when the server tries to process the message.  It is an innocuous situation but can litter the logs a bit.

 

 

Don't know if you're already aware of the server logging an error on MBC trying to access Special Features on channels (when there are none), so didn't want to post a log if it's an issue you already know/don't care about/moot, lol 

 

I did not know about that.  I'll take a look.  Thanks.

[flexage 125]

You mean on the "Context" websocket message?  If so, I posted a request in the dev area for Luke to think about suppressing that or, at least, making it a warning or information message.

Yep, that's the one, cool stuff.

 

did not know about that.  I'll take a look.  Thanks.

Ok, no problem... here's the particular server log message to be looking out for, with a few extra debug lines for a bit of context

2014-06-08 21:21:50.1944 Debug - HttpServer: HTTP GET http://192.168.180.128:8096/mediabrowser/Users/22cf0934-c31a-064b-46ef-d2ec71688202/Items/a6c8b363-0f2f-b996-79c3-28b7431bc55e?format=Json
2014-06-08 21:21:50.1944 Debug - HttpServer: HTTP Response 200 to 192.168.180.128:49526. Response time: 2.0001 ms
	Url: http://192.168.180.128:8096/mediabrowser/Users/22cf0934-c31a-064b-46ef-d2ec71688202/Items/a6c8b363-0f2f-b996-79c3-28b7431bc55e?format=Json
2014-06-08 21:21:50.1944 Debug - HttpServer: HTTP GET http://192.168.180.128:8096/mediabrowser/Localization/ParentalRatings?format=Json
2014-06-08 21:21:50.2054 Debug - HttpServer: HTTP Response 200 to 192.168.180.128:49526. Response time: 1.0001 ms
	Url: http://192.168.180.128:8096/mediabrowser/Localization/ParentalRatings?format=Json
2014-06-08 21:21:58.6849 Debug - HttpServer: HTTP GET http://192.168.180.128:8096/mediabrowser/Localization/ParentalRatings?format=Json
2014-06-08 21:21:58.6849 Debug - HttpServer: HTTP Response 200 to 192.168.180.128:49526. Response time: 1.0001 ms
	Url: http://192.168.180.128:8096/mediabrowser/Localization/ParentalRatings?format=Json
2014-06-08 21:21:58.9339 Debug - HttpServer: HTTP GET http://192.168.180.128:8096/mediabrowser/Localization/ParentalRatings?format=Json
2014-06-08 21:21:58.9339 Debug - HttpServer: HTTP Response 200 to 192.168.180.128:49526. Response time: 1.0001 ms
	Url: http://192.168.180.128:8096/mediabrowser/Localization/ParentalRatings?format=Json
2014-06-08 21:22:02.3671 Debug - HttpServer: HTTP GET http://192.168.180.128:8096/mediabrowser/Users/22cf0934-c31a-064b-46ef-d2ec71688202/Items/7adebc63-b2a6-f9b1-fa45-00762a6af9fb/SpecialFeatures?format=Json
2014-06-08 21:22:02.3671 Error - DtoUtils: ServiceBase<TRequest>::Service Exception
	The item does not support special features
	System.ArgumentException
	   at MediaBrowser.Api.UserLibrary.UserLibraryService.GetAsync(GetSpecialFeatures request)
	   at lambda_method(Closure , Object , Object )
	   at ServiceStack.Host.ServiceRunner`1.Execute(IRequest request, Object instance, TRequest requestDto)
	
2014-06-08 21:22:02.3671 Error - HttpServer: Error processing request for /mediabrowser/Users/22cf0934-c31a-064b-46ef-d2ec71688202/Items/7adebc63-b2a6-f9b1-fa45-00762a6af9fb/SpecialFeatures?format=Json
	The item does not support special features
	ServiceStack.HttpError
	No Stack Trace Available
	
2014-06-08 21:22:02.3671 Debug - HttpServer: HTTP Response 400 to 192.168.180.128:49526. Response time: 3.0002 ms
	Url: http://192.168.180.128:8096/mediabrowser/Users/22cf0934-c31a-064b-46ef-d2ec71688202/Items/7adebc63-b2a6-f9b1-fa45-00762a6af9fb/SpecialFeatures?format=Json

[Luke 42077]

This won't help mbc at the moment, but i'll update the server not to throw an error. there's no reason to arbitrarily decide if an item can have special features or not.

 

however - you should use the SpecialFeatureCount property to avoid making the call in the first place. if it's 0, or null, there are no special features.

[ebr 16169]

Has anyone tried out the new player interface on the 360?

 

Got a report that it didn't work well.  If that is the case, I may need to disable it for extenders.

[ebr 16169]

175 will eliminate the specials error on the server and hopefully handle rapid skipping better.

 

It also adds something that will allow Radeon to fix the theme backdrops (I hope).

[flexage 125]

@@ebr - Great work, that was fast!!

 

Tested out, can confirm the server error message no longer shows using latest "release" server build

[Yogi 367]

I think I know what this is now... At the last minute before full release yesterday, the channel API was changed to use the "fields" parameter like the normal api.  This means I'm not getting the same information back from the responses that I was before and the display prefs ID is one of those items.

 

I couldn't reproduce it because I already made the adjustment to send the fields in my development version of MBC.  I'll put out a new dev release right now and, if I'm right, that should fix it for you guys.

 

Please let me know.

 

 

All fixed and working,good stuff ebr.

[coolspot 22]

I used the new interface on the 360 and it worked well and I quite preferred it...on build 173.  Trying to figure out why I can't get into MBC on 176 though on computer or 360.

 

Nevermind.  Got a blue screen the first time or two I went in...but it seems to be working now.

Edited June 9, 2014 by coolspot

[Sharmy 9]

The default WMC screensaver does not kick in with 176 release.

 

Edit. It just kicked in but not honouring the WMC timeout setting. Testing again now.

 

Please disregard. Restarted machine and all working fine. Not sure what held it up the first time.

Edited June 9, 2014 by Sharmy

[Yogi 367]

175 will eliminate the specials error on the server and hopefully handle rapid skipping better.

 

It also adds something that will allow Radeon to fix the theme backdrops (I hope).

Ebr the theme backdrops are now working as normal with .176.Whatever you added has fixed this.