HD HomeRun Connect Spinning Wheel

[blue65 2]

Hi, 

 

Have HD Homerun Connect (with latest Firmware) running Latest version of Emby Server (4.2.1.0)

 

If I watch via the HD HomeRun software App, all channels are displayed every time.

 

When running via Chrome (on latest version) on my Large Screen TV or on my laptop, the HD channels get a spinning wheel but frustratingly from a debug point of view, not always. Roughly I'd say it fails 8-9 times out of 10. Can't replicate the scenario when it did work.

 

The SD channels display every time.

 

When its failing, if I look on the Dashboard, it says there are no active devices. If I watch an SD channel, I can see an active device.  

 

I have attached the log file for the few minutes when I did a HD Channel request (channel 70) until I killed it off.

 

If I watch on my iPhone via the Emby App or via Chrome, the channels are displayed without issue.

 

Any ideas? Thanks.

[Luke 37046]

Hi there, can we please look at an example? Please attach the information requested in how to report a media playback issue. thanks !

[blue65 2]

I have attached todays log file.

embyserver.txt

 

 

I attempted to watch LiveTv at around 7:16am on Channel 70 (HD Channel)  and I got the spinning wheel on the screen that goes for a couple minutes before I close it down (refer video clip)

Spinning Wheel Demo.MOV

 

 

If I looked at the Dashboard, I could see no "Active Devices" present (refer pic 1)

 

 

At around 7:18am I tried Channel 71 (an SD channel) and I saw the TV show. When referring to dashboard and "Active Device", I could see teh TV session appearing (See Pic 2)

 

 

I tried the HD channel (70) again at around 7:19am with no picture appearing.

 

I tried to watch the HD channel on my laptop at around 7:20am, and no picture again.

[Luke 37046]

Hi, was there an ffmpeg log? Can you please attach that too? Thanks.

[blue65 2]

I've attached the ffmpeg logs for that whole day.

ffmpeg-remux-33ee92f1-60c9-4f55-ace7-ca0cc19d0b1f_1.txt

ffmpeg-remux-71b177cc-c08a-4ea1-a748-961f806c0d0d_1.txt

ffmpeg-remux-a4a96e01-c641-448f-99d4-4b93cb4f6a58_1.txt

ffmpeg-remux-a448fe77-8bd3-48ed-9848-e75ee1ed441c_1.txt

ffmpeg-remux-a5535f6b-ee55-4989-9a25-41f9e7404ff5_1.txt

ffmpeg-remux-e41859ec-f954-4e5a-a351-7497c46c53e5_1.txt

ffmpeg-remux-e451945c-b6d7-4843-87e6-8b8e42a7a06e_1.txt

ffmpeg-remux-e6668168-4fd0-473a-ac5a-8f95beadb9ee_1.txt

ffmpeg-remux-ef6d0926-bcf4-41e7-8c17-d0ac06bcbb1a_1.txt

ffmpeg-transcode-4e912473-bd71-4c73-b4c3-7965bc96f0cd_1.txt

ffmpeg-transcode-8006f405-4431-4e5e-9992-24e1415a6cc9_1.txt

ffmpeg-transcode-ad01b063-b2f3-4665-9580-86a7a95282d0_1.txt

[blue65 2]

Hi, Just wondering if any ideas about this one ?   

Thanks

[Luke 37046]

@@blue65, unfortunately I don't see anything obvious here. There are live tv related fixes in the upcoming 4.3 release so you could try again with that.

 

I do notice one thing in your server log:

System.IO.IOException: System.IO.IOException: The filename, directory name, or volume label syntax is incorrect : 'M:\Emby\cache\audiodb-artist\b0295e0d-9ae7-4bcc-962a-bf5895e562d7
	

Is this a mapped network drive, or some drive that becomes unavailable after a period of time? If yes then this will almost certainly cause a problem. Thanks.

[blue65 2]

Thanks for the update

 

The M: drive is local.

 

Hopefully Rls 4.3 will bring me some joy.

[Luke 37046]

If the server can't access your M: drive then the 4.3 release will not be able to resolve this:

System.IO.IOException: System.IO.IOException: The filename, directory name, or volume label syntax is incorrect : 'M:\Emby\cache\audiodb-artist\b0295e0d-9ae7-4bcc-962a-bf5895e562d7

Are you sure it has write access to this folder? It's not a mapped network drive, is it?

[blue65 2]

Its a 100GB partition on an internally attached hard drive (2TB) which has 90% capacity remaining