Search the Community

Setup: - Live TV m3u HDHR3-US network dual tuner - Live TV NextPVR plugin connected to a different computer on the network (1gbps link) - Emby Beta 3.2.5.7 Problem: - Recordings start but end prematurely - Mostly with the NextPVR plugin -- I'm going to check the logs on on NextPVR to see if anything unusual happened - Recordings fail to start and the following error is thrown *** Error Report *** Version: 3.2.5.7 Command line: C:\Users\media\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1 64-Bit OS: True 64-Bit Process: True Processor count: 8 Program data path: C:\Users\media\AppData\Roaming\MediaBrowser-Server Application directory: C:\Users\media\AppData\Roaming\MediaBrowser-Server\System System.NotImplementedException: La méthode ou l'opération n'est pas implémentée. à Emby.Server.Implementations.LiveTv.EmbyTV.EmbyTV.<GetChannelStreamMediaSources>d__89.MoveNext() I have shared the full logs with @@Luke in private to hide potentially sensitive data from the general public.

For some time my emby server dosnt record anymore. It shows LiveTV fine, but recordings fails. My serverlog shows: 2017-02-26 19:11:21.5226 Info HttpClient: HttpClientManager GET: https://www.thetvdb.com/api/GetSeries.php?seriesname=Yakari&language=da 2017-02-26 19:11:22.2534 Info HttpClient: HttpClientManager GET: https://www.thetvdb.com/api/B89CE93890E9419B/series/84458/all/da.zip 2017-02-26 19:11:23.9707 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/tv/find/84458?api_key=f6bd687ffa63cd282b6ff2c6877f2669&external_source=tvdb_id 2017-02-26 19:11:24.5561 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/configuration?api_key=f6bd687ffa63cd282b6ff2c6877f2669 2017-02-26 19:11:24.6562 Info App: MovieDbProvider: Finding id for item: Yakari 2017-02-26 19:11:24.8565 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/search/tv?api_key=f6bd687ffa63cd282b6ff2c6877f2669&query=Yakari&language=da 2017-02-26 19:11:25.1582 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/tv/61071?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=credits,images,keywords,external_ids,videos,content_ratings&language=da&include_image_language=da,null,en 2017-02-26 19:11:25.5715 Info App: MovieDbSeriesProvider couldn't find meta for language da. Trying English... 2017-02-26 19:11:25.5715 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/tv/61071?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=credits,images,keywords,external_ids,videos,content_ratings&language=en&include_image_language=da,null,en 2017-02-26 19:11:26.1439 Info HttpClient: HttpClientManager GET: https://webservice.fanart.tv/v3/tv/84458?api_key=5c6b04c68e904cfed1e6cbc9a9e683d4 2017-02-26 19:11:26.2598 Info App: Recording timer fired. 2017-02-26 19:11:26.2754 Info App: Streaming Channel m3u_151b2088ea4e326a8761c94dfdf73376dcd5d6162f92e29205cc9cda8bd09e0e 2017-02-26 19:11:26.2754 Info App: Returning mediasource streamId 3c2a4186c6f54a52ad689d1287f3e5b4aa8088582bb16344e3198ff05e7941f1, mediaSource.Id d5470e6673e94302b98097cc00d56fc7_aa8088582bb16344e3198ff05e7941f1, mediaSource.LiveStreamId 2017-02-26 19:11:26.2754 Info App: Beginning recording. Will record for 18.5620752166667 minutes. 2017-02-26 19:11:26.2754 Info App: Writing file to path: E:\SERIES\Yakari\Yakari 2017-02-26.mp4 2017-02-26 19:11:26.2754 Info App: Opening recording stream from tuner provider 2017-02-26 19:11:26.2754 Info App: C:\Users\admin\AppData\Roaming\Emby-Server\ffmpeg\20160410\ffmpeg.exe -fflags +genpts -async 1 -vsync -1 -analyzeduration 5000000 -i "http://dr05-lh.akamaihd.net/i/dr05_0@147058/master.m3u8?b=2000-20000"-t 00:18:33.724 -map 0 -ignore_unknown -codec:v:0 copy -map_metadata -1 -threads 0 -codec:a copy -sn -y "E:\SERIES\Yakari\Yakari 2017-02-26.mp4" 2017-02-26 19:11:26.2910 Info App: ffmpeg recording process started for E:\SERIES\Yakari\Yakari 2017-02-26.mp4 2017-02-26 19:11:26.3067 Info HttpClient: HttpClientManager GET: https://www.omdbapi.com/?i=tt0416439&plot=full&tomatoes=true&r=json 2017-02-26 19:11:26.9112 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/tv/61071?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=credits,images,keywords,external_ids,videos,content_ratings&language=da&include_image_language=da,null,en 2017-02-26 19:11:27.0487 Info App: MovieDbSeriesProvider couldn't find meta for language da. Trying English... 2017-02-26 19:11:27.2126 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/tv/61071?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=credits,images,keywords,external_ids,videos,content_ratings&language=en&include_image_language=da,null,en 2017-02-26 19:11:29.8338 Info App: FFMpeg recording exited with code 1 for E:\SERIES\Yakari\Yakari 2017-02-26.mp4 2017-02-26 19:11:29.8338 Error App: Error recording to E:\SERIES\Yakari\Yakari 2017-02-26.mp4 *** Error Report *** Version: 3.2.4.0 Command line: C:\Users\admin\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe -service Operating system: Microsoft Windows NT 6.2.9200.0 64-Bit OS: True 64-Bit Process: True Processor count: 4 Program data path: C:\Users\admin\AppData\Roaming\Emby-Server Application directory: C:\Users\admin\AppData\Roaming\Emby-Server\System System.Exception: Recording for E:\SERIES\Yakari\Yakari 2017-02-26.mp4 failed. Exit code 1 ved System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) ved System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) ved Emby.Server.Implementations.LiveTv.EmbyTV.EncodedRecorder.<Record>d__19.MoveNext() --- Afslutningen på staksporingen fra den tidligere placering, hvor undtagelsen blev udløst --- ved System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) ved System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) ved System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) ved Emby.Server.Implementations.LiveTv.EmbyTV.EmbyTV.<RecordStream>d__96.MoveNext() System.Exception ved System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) ved System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) ved Emby.Server.Implementations.LiveTv.EmbyTV.EncodedRecorder.<Record>d__19.MoveNext() --- Afslutningen på staksporingen fra den tidligere placering, hvor undtagelsen blev udløst --- ved System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) ved System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) ved System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) ved Emby.Server.Implementations.LiveTv.EmbyTV.EmbyTV.<RecordStream>d__96.MoveNext() 2017-02-26 19:11:29.8338 Info App: Live stream d5470e6673e94302b98097cc00d56fc7_aa8088582bb16344e3198ff05e7941f1 consumer count is now 0 2017-02-26 19:11:29.8338 Info App: Closing live stream d5470e6673e94302b98097cc00d56fc7_aa8088582bb16344e3198ff05e7941f1 2017-02-26 19:11:29.8338 Info App: Live stream d5470e6673e94302b98097cc00d56fc7_aa8088582bb16344e3198ff05e7941f1 closed successfully 2017-02-26 19:11:29.8338 Info App: Retrying recording in 60 seconds. 2017-02-26 19:11:29.8505 Info App: Creating recording timer for e6ea869ac4404de4a0dd11ddea1c1257, Yakari. Timer will fire in 0.999722521666667 minutes 2017-02-26 19:11:32.4636 Info App: Emby.Kodi.SyncQueue: Starting Library Sync... 2017-02-26 19:11:32.4636 Info App: Emby.Kodi.SyncQueue: "LIBRARYSYNC" Added 0 items: 2017-02-26 19:11:32.4790 Info App: Emby.Kodi.SyncQueue: "LIBRARYSYNC" Updated 1 items: d52daa5d1234ec345c7d63f591c7a3a6 2017-02-26 19:11:32.4790 Info App: Emby.Kodi.SyncQueue: "LIBRARYSYNC" Removed 0 items: 2017-02-26 19:11:32.4790 Info App: Emby.Kodi.SyncQueue: Finished Library Sync Taking 00:00:00.0154007 And record-transcode log is attached. Any Idea why recording dosnt work ? record-transcode-130f5bbd-848c-44a5-907b-86fa1c3e6a97.txt

Updated to 3.2.4.0 this morning. Show that was set to record failed to record. Went nuts. There Are several files in the recording folder. Several logs of the same thing from the transcode....all form the same minute in time....like it tried to start recording several times but failed. Output looks similar to another thread posted here. Edit: Reverted Server to 3.2.1.0 Recording works fine. No issues. So.....must be something in the update that is borked. Logserver.txt Logtrans.txt

The problem appears to be remuxing but it appears to me there is no reason for it to be remuxing. It skips, it is annoying. Works fine on Windows (because no remuxing). Confirmed on: ​-Leelbox MXQ Pro (Amlogic S905) -Leelbox Master (Amlogic S905X) -NVIDIA SHIELD TV (newest version) Server: -Intel Xeon E3-1230V3 (4c/8t, 3.3 GHz) -8 GiB DDR3 -10/100/1000 NIC -RAID1 SSDs OS/transcoding temp/Emby Server install location ​-3 TB 7200 RPM HDD for recordings ​-Windows Server 2012 R2 TV Tuners: -HDHomeRun EXTEND -HDHomeRun EXTEND -HDHomeRun EXTEND Network: ​-gigabit everywhere -the entire path is wired (server, HDHomeRuns, Android TV boxes) -Only part that isn't gigabit is the HDHomeRun and Amlogic boxes (because 10/100 NIC standard) Channel: Laff 9.3 ​-Container: MPEG, I think. I attached 1 MiB of the stream downloaded via IE11 from the HDHomeRun EXTEND (stream_snippet.zip). There's no clear headers in here from what I can tell. Including this because it might be the cause of the problem. -Video: MPEG4 Video (H264) 704x480 (4:3) 29.97fps [V: h264 high L4.0, yuv420p, 704x480] -Audio: Dolby AC3 48000Hz stereo 192kbps [A: English [eng] (ac3, 48000 Hz, stereo, 192 kb/s)] Software: -Emby Server: 3.2.0.0 -Emby for Android TV: 1.3.20g I can't remember subchannels ever not being a problem with Emby for Android TV (either because of transcoding with HDHomeRun CONNECT or remuxing HDHomeRun EXTEND). I believe they work fine using the HDHomeRun beta app on the same devices. This applies to all of the subchannels, live TV or playing back a recording from a subchannel. Attached logs (remux.zip) from today showing the remuxing on NVIDIA SHIELD TV. remux.zip stream_snippet.zip

I am a relatively new Emby user. There are several things that I find confusing when I try to record shows from Live TV. Due to my lack of understanding it's frustrating not to be able to do scheduled recordings reliably. When this feature works for me, it works really well, but it doesn't always work! It's a very good product and potentially a great product but I need help in understanding what's going on. Here are a few of the issues that confuse me: On one night I may use the Guide to schedule a recording and it behaves as expected (i.e. the recorded program shows up the next day in Recorded TV or in TV Recordings with appropriate metadata images, it replays correctly, etc.) The next day, I may repeat the exact same process and the program fails to record. Tuners were available in both cases, Emby was up and running, no network problems, etc. I am confused by the two very similar menu tabs on the Emby console Live TV screen – TV Recordings and Recorded TV. Some of my recorded content shows up in one place, and some in the other, but the content is not always the same in both places. What is the difference in these two menu tabs? It appears that metadata displayed for recorded content in these locations does not update immediately, but usually appears several hours later when a scheduled refresh occurs. Sometimes doing a manual refresh will populate the folders with metadata, and other times it does not. When I set up my PC a few months ago, I installed a solid-state hard drive and used it for the operating system (currently Windows 10). I intended to separate my user data from OS data and place it on the original hard drive that came with the computer – re-assigned to drive letter "E". I set up a folder for Emby on the "E" drive for recorded TV because I didn't want multi-gigabytes of recorded data stored on the system drive. However, when I updated to the latest Emby server the location apparently got changed back to the default location on the system drive (C:\Users|<name>\AppData\Roaming\Emby-Server\data\livetv\recordings\...). I added the second location back in Emby (E:\Recorded TV\TV\Series\...) and now I can't predict which location the recorded ".ts" files will be saved in. "Sometimes they're in one location, other times in the other location.) Do my TV recordings really need to be stored on the system drive? I would appreciate your advice and suggestions on how to simplify things and increase reliability.

This has occurred on two separate days for two separate recordings. Here's a snippet of Thursday's "Pure Genius:" ​ 2016-11-17 20:59:59.8814 Info App: Recording timer fired. 2016-11-17 20:59:59.8814 Info HttpClient: HttpClientManager GET: http://192.168.0.223/lineup.json 2016-11-17 20:59:59.9283 Info HttpClient: HttpClientManager GET: http://192.168.0.224/lineup.json 2016-11-17 20:59:59.9751 Info HttpClient: HttpClientManager GET: http://192.168.0.225/lineup.json 2016-11-17 21:00:00.0220 Info HttpClient: Checking for cache file C:\Users\Lee\AppData\Roaming\Emby-Server\cache\httpclient\a0ef2e0b7b00583fcf8fa1cd6c50be9d 2016-11-17 21:00:00.0220 Info HttpClient: HttpClientManager GET: http://192.168.0.223/tuners.html 2016-11-17 21:00:00.0533 Info HttpClient: Checking for cache file C:\Users\Lee\AppData\Roaming\Emby-Server\cache\httpclient\a0ef2e0b7b00583fcf8fa1cd6c50be9d 2016-11-17 21:00:00.0533 Info App: Streaming Channel hdhr_14.1_7b8bfe52571255b9d7d0bcae0d2516a2 2016-11-17 21:00:00.0533 Info App: Live stream f2abed16761f412fb66a130d8065c26cnative_9c346459c7938e25dbe2deb2a76861a8 consumer count is now 2 2016-11-17 21:00:00.0533 Info App: Beginning recording. Will record for 59.9991112616667 minutes. 2016-11-17 21:00:00.0533 Info App: Writing file to path: E:\Recordings\Pure Genius\Season 1\Pure Genius S01E04 Not Your Grandmother's Robotic Surgery.ts 2016-11-17 21:00:00.0533 Info App: Opening recording stream from tuner provider 2016-11-17 21:00:00.0533 Info HttpClient: HttpClientManager GET: http://127.0.0.1:8096/LiveTv/LiveStreamFiles/6587ca29114449ee82cf020afa3746ad/stream.ts 2016-11-17 21:00:00.0689 Info HttpServer: HTTP GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/6587ca29114449ee82cf020afa3746ad/stream.ts. UserAgent: 2016-11-17 21:00:01.2565 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-17 21:00:01.2565 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-17 21:00:04.2880 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-17 21:00:04.2880 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-17 21:00:07.3820 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-17 21:00:07.3820 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-17 21:00:10.4291 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-17 21:00:10.4291 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-17 21:00:13.4762 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-17 21:00:13.5075 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-17 21:00:16.5546 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-17 21:00:16.5546 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-17 21:00:19.6173 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-17 21:00:19.6173 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-17 21:00:20.0549 Error HttpClient: Error getting response from http://127.0.0.1:8096/LiveTv/LiveStreamFiles/6587ca29114449ee82cf020afa3746ad/stream.ts *** Error Report *** Version: 3.0.8500.0 Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe -service Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 8 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe One or more errors occurred. System.AggregateException at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() InnerException: System.Net.WebException The request was aborted: The request was canceled. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) 2016-11-17 21:00:20.0549 Error App: Error recording to E:\Recordings\Pure Genius\Season 1\Pure Genius S01E04 Not Your Grandmother's Robotic Surgery.ts *** Error Report *** Version: 3.0.8500.0 Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe -service Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 8 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe One or more errors occurred. MediaBrowser.Model.Net.HttpException at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsync>d__17.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Server.Implementations.LiveTv.EmbyTV.DirectRecorder.<Record>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at MediaBrowser.Server.Implementations.LiveTv.EmbyTV.EmbyTV.<RecordStream>d__86.MoveNext() InnerException: System.AggregateException One or more errors occurred. at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() InnerException: System.Net.WebException The request was aborted: The request was canceled. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) 2016-11-17 21:00:20.0549 Info App: Live stream f2d5f2744df9494c9cb6ba7b1fe18e4f_native_9c346459c7938e25dbe2deb2a76861a8 consumer count is now 1 2016-11-17 21:00:20.0549 Info App: Retrying recording in 60 seconds. 2016-11-17 21:00:20.0549 Info App: Creating recording timer for 9f92fbd175f89ad9ef315d8ba40afd4d, Pure Genius. Timer will fire in 1 minutes Here's a snippet of Friday's "Hawaii Five-0:" 2016-11-18 19:59:59.9190 Info App: Writing file to path: E:\Recordings\Hawaii Five-0\Season 7\Hawaii Five-0 S07E09 Elua La Ma Nowemapa.ts 2016-11-18 19:59:59.9190 Info App: Opening recording stream from tuner provider 2016-11-18 19:59:59.9190 Info HttpClient: HttpClientManager GET: http://127.0.0.1:8096/LiveTv/LiveStreamFiles/6587ca29114449ee82cf020afa3746ad/stream.ts 2016-11-18 19:59:59.9346 Info HttpServer: HTTP GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/6587ca29114449ee82cf020afa3746ad/stream.ts. UserAgent: 2016-11-18 20:00:02.6849 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-18 20:00:02.6849 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-18 20:00:02.7943 Info App: Recording timer fired. 2016-11-18 20:00:02.7943 Warn App: Recording timer fired for updatedTimer MacGyver, Id: 039ae924232849c9c50dd7dc9f6d50ac, but the program has already ended. 2016-11-18 20:00:05.7320 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-18 20:00:05.7320 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-18 20:00:05.8101 Info App: Recording timer fired. 2016-11-18 20:00:05.8257 Info HttpClient: Checking for cache file C:\Users\Lee\AppData\Roaming\Emby-Server\cache\httpclient\a0ef2e0b7b00583fcf8fa1cd6c50be9d 2016-11-18 20:00:05.8257 Info HttpClient: HttpClientManager GET: http://192.168.0.223/tuners.html 2016-11-18 20:00:05.8570 Info HttpClient: Checking for cache file C:\Users\Lee\AppData\Roaming\Emby-Server\cache\httpclient\a0ef2e0b7b00583fcf8fa1cd6c50be9d 2016-11-18 20:00:05.8570 Info App: Streaming Channel hdhr_44.1_a44bbe0e2e449b50c3f7057c40d97b44 2016-11-18 20:00:05.8570 Info App: Live stream f2abed16761f412fb66a130d8065c26cnative_4311fd9e9eee9f2ce0114f3e2230e1d9 consumer count is now 2 2016-11-18 20:00:05.8570 Info App: Beginning recording. Will record for 0.902382555 minutes. 2016-11-18 20:00:05.8570 Info App: Writing file to path: E:\Recordings\Hell's Kitchen\Season 16\Hell's Kitchen S16E08 Dancing With the Chefs.ts 2016-11-18 20:00:05.8570 Info App: Opening recording stream from tuner provider 2016-11-18 20:00:05.8570 Info HttpClient: HttpClientManager GET: http://127.0.0.1:8096/LiveTv/LiveStreamFiles/f7578475c6324ec9ba311978b6dadc12/stream.ts 2016-11-18 20:00:05.8570 Info HttpServer: HTTP GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/f7578475c6324ec9ba311978b6dadc12/stream.ts. UserAgent: 2016-11-18 20:00:08.7635 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-18 20:00:08.7791 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-18 20:00:11.8106 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-18 20:00:11.8106 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-18 20:00:14.8733 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-18 20:00:14.8733 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-18 20:00:17.9205 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J) 2016-11-18 20:00:17.9205 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 2016-11-18 20:00:19.9206 Error HttpClient: Error getting response from http://127.0.0.1:8096/LiveTv/LiveStreamFiles/6587ca29114449ee82cf020afa3746ad/stream.ts *** Error Report *** Version: 3.0.8500.0 Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe -service Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 8 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe One or more errors occurred. System.AggregateException at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() InnerException: System.Net.WebException The request was aborted: The request was canceled. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) 2016-11-18 20:00:19.9206 Error App: Error recording to E:\Recordings\Hawaii Five-0\Season 7\Hawaii Five-0 S07E09 Elua La Ma Nowemapa.ts *** Error Report *** Version: 3.0.8500.0 Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe -service Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 8 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe One or more errors occurred. MediaBrowser.Model.Net.HttpException at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsync>d__17.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Server.Implementations.LiveTv.EmbyTV.DirectRecorder.<Record>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at MediaBrowser.Server.Implementations.LiveTv.EmbyTV.EmbyTV.<RecordStream>d__86.MoveNext() InnerException: System.AggregateException One or more errors occurred. at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() InnerException: System.Net.WebException The request was aborted: The request was canceled. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) 2016-11-18 20:00:19.9206 Info App: Live stream 63cd62cd15fa42a7b2aaacdbf17ad45b_native_9c346459c7938e25dbe2deb2a76861a8 consumer count is now 1 2016-11-18 20:00:19.9206 Info App: Retrying recording in 60 seconds. 2016-11-18 20:00:19.9206 Info App: Creating recording timer for ac775b8ea5d51bffbe4cc690a949dd4d, Hawaii Five-0. Timer will fire in 1 minutes Attached full logs. logs.zip

Hello, I've been noticing duplicate recordings of PBS shows for my kids. I'm attaching the logfile that includes the duplicate recording for "Peg Plus Cat S01E07". What I've noticed is that one of the resolution is 1080 and the other is 720 and am wondering if that is the root cause of the duplicates. I'm attaching logfiles, and the file properties for review. If that's the cause, is there any resolution (no pun intended) not to get the dups. Thanks Log.txt

Is there a way to record the same series on 2 separate channels, but not on all channels? I am catching runs of The Big Bang Theory on a local Fox station have it set to One channel, but would like to record the new episodes from CBS, but it seems to be limited to one or the other or all channels Unless I schedule the new episodes individually. Thanks for reading and any help!

My series recording schedule has picked up some problems. I deleted a series recording schedule but the series still shows up in the list of scheduled recordings. Checking the logs, there is an entry showing the attempt to delete the series schedule was attempted but could not complete because the root entry was missing. I would like to know how to clear out the entire list of scheduled recordings so I can set up a new list of recordings from a fresh start. A recording schedule "reset button" would be nice but I don't think that's been put in place yet. Log file attached. server-63612035666.txt

We were able to identify 3 out of 4 agriculture/business/news programs that always say "repeat" so any series set up to record them never will even though they're new daily or weekly. I'm not entirely sure what makes that distinction but, here's the programs and their genre: AgDay Newsmagazine This Week in AgriBusiness Bus./financial / Agriculture Agweek TV Public affairs As far as I know, these episodes are always new. They're like local news broadcasts...but specialized.

Hello there Emby Team, Using my HDHomerun Extend, the option to "Automatically convert recordings to a streaming friendly format" used with the option "Preserve original audio when converting recordings (when possible)" creates a file, either mp4 or mkv, with the original ac3 (dolby digital) audio track. This file usually needs transcoding if sending to a player without ac3 capabilities. What I'm proposing is what I used to do for my AppleTV/iOS files. Basically have two audio tracks in the file. One being a converted aac 2-channel track as well as the original ac3 track from the HDHomerun. That way we can maybe avoid some transcoding as the server would choose which audio track to play based on the output capabilities? If ac3 capable, choose the ac3 track, if not ac3 compatible like on web browsers, ios and some players, choose the 2-ch aac track. Does this sound like a possible feature? Thanks for your time. Marc

Recordings are suddenly failing or are incomplete. I had a few programs set to record and all the files are less than 4 min. I restarted the computer and server, cleared the record que and bad recordings and set a test recording on a different channel. It too only recorded for 3 min then it stops. Also looks a bit corrupted videoplayback. My last successful recording was 2 days ago 7-30-16 at 10:30am. The server has updated beta versions a few times since then i believe. Edit: also noticed that live tv streaming was failing. I noticed Intel Quick Sync was set in the Transcode settings for Hardware acceleration(has been enabled for sometime with no issues), Set it to none, restarted...and i got live to tv to stream in Chrome again. I set a random test recording...will see if that works. Edit: One 30 min recording worked fine, but a 1hr program stopped at 37min. server-63605658987.txt server-63605652966.txt remux 1.txt remux2.txt

It would be great if the record series ability was accessible from the menu button on the series poster/picture see attached. Thanks for reading and considering!

I am trying to use Emby as a DVR solution, after recording some shows as tests, everything worked fine. I have the convert to mp4 option checked. However this weekend, all of the shows I record only recorded for 4 seconds. below is from the server Log file: I have also attached the corresponding record 2016-03-26 13:59:48.8819 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 36ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:00:00.0679 Info App: Recording timer fired. 2016-03-26 14:00:00.2294 Info App: Streaming Channel hdhr_791_3c2850c70a0d49988d0e212b1210ff4b 2016-03-26 14:00:00.2540 Info HttpClient: HttpClientManager GET: http://192.168.1.207/lineup.json 2016-03-26 14:00:00.3075 Info HttpClient: HttpClientManager GET: http://192.168.1.99/lineup.json 2016-03-26 14:00:00.4806 Info HttpClient: HttpClientManager GET: http://192.168.1.207/tuners.html 2016-03-26 14:00:00.5862 Info App: GetChannelStream: channel id: hdhr_791_3c2850c70a0d49988d0e212b1210ff4b. stream id: 2016-03-26 14:00:00.7287 Info HttpClient: HttpClientManager POST: http://www.mb3admin.com/admin/service/registration/validate 2016-03-26 14:00:00.9329 Info App: Beginning recording. Will record for 59.9902243666667 minutes. 2016-03-26 14:00:00.9329 Info App: Writing file to path: /media/Recorded_TV/Series/See No Evil/See No Evil S02E05 Watching Dru.mp4 2016-03-26 14:00:00.9329 Info App: Opening recording stream from tuner provider 2016-03-26 14:00:00.9577 Info App: /usr/pbi/emby-amd64/bin/ffmpeg -fflags +genpts -async 1 -vsync -1 -i "http://192.168.1.207:5004/auto/v791" -t 00:59:59.413 -sn -codec:v:0 libx264 -force_key_frames expr:gte(t,n_forced*5) -vf "yadif=0:-1:0" -pix_fmt yuv420p -preset superfast -crf 23 -b:v 25000000 -maxrate 25000000 -bufsize (25000000*2) -vsync vfr -profile:v high -level 41 -map_metadata -1 -threads 0 -codec:a:0 aac -strict experimental -ab 320000 -y "/media/Recorded_TV/Series/See No Evil/See No Evil S02E05 Watching Dru.mp4" 2016-03-26 14:00:19.1182 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:00:19.1504 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 32ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:00:49.1576 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:00:49.1873 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 30ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:01:19.4286 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:01:19.4609 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 32ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:01:49.4679 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:01:49.5001 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 32ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:02:19.7391 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:02:19.7776 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 38ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:02:49.7858 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:02:49.8176 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 32ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:03:18.0608 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:03:18.0996 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 39ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:03:48.1107 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:03:48.1400 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 29ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:04:01.7316 Info HttpServer: HTTP SUBSCRIBE http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/connectionmanager/events. UserAgent: DLNADOC/1.51 SEC_HHP_[Mobile]Krystal Schlaht (Galaxy Note4)/1.0 2016-03-26 14:04:01.7329 Info HttpServer: HTTP Response 200 to 192.168.1.86. Time: 1ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/connectionmanager/events 2016-03-26 14:04:02.7817 Info HttpServer: HTTP SUBSCRIBE http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/contentdirectory/events. UserAgent: DLNADOC/1.51 SEC_HHP_[Mobile]Krystal Schlaht (Galaxy Note4)/1.0 2016-03-26 14:04:02.7869 Info HttpServer: HTTP Response 200 to 192.168.1.86. Time: 5ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/contentdirectory/events 2016-03-26 14:04:18.3717 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:04:18.4177 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 46ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:04:48.4273 Info HttpServer: HTTP GET http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml. UserAgent: UPnP/1.0 2016-03-26 14:04:48.4760 Info HttpServer: HTTP Response 200 to 192.168.1.161. Time: 49ms. http://192.168.1.6:8096/dlna/64c20dc96904d561182102a04b57ce0e/description.xml 2016-03-26 14:05:12.6803 Info App: FFMpeg exited with code 0 2016-03-26 14:05:12.7696 Info App: Recording completed: /media/Recorded_TV/Series/See No Evil/See No Evil S02E05 Watching Dru.mp4 record-transcode-ee2f7f7c-165d-454a-84ba-6f9fc19a84ff.txt

I wasn't able to find any information about this so I apologize if this has been answered before. I have now done 2 re-installations of emby windows server due to hardware and OS changes. My TV recordings folder is still full of TS files but they no longer show up in emby. I figured it would just auto detect the files in there, but it does not. Is there a way that I can have these files accessible again from inside emby?

Hi--I had a nicely working OSX server on a Mac Mini but since the most recent update, I can't seem to schedule recordings. I am able to get through the guide and set up the record series, but then my "Scheduled Recordings" tab remains empty. The series all show up in the series tab. I initially thought that I might just need to wait for the schedule to refresh or until closer to the recording date, but the recordings I had scheduled did not record. Everything else seems to be working. Any thoughts? Thanks.

When choosing series record on a tv show (any time, any days, same channel & new or old) duplicate episodes are recorded. I.e. the first showing of an episode may be on Monday with a second chance viewing on the weekend. Both episodes appear in the schedule and both are recorded. Is there anything I can do to stop this? I would like the catch up episode to record only if the first failed.

Sorry if I keep asking very basic things but I'm totally new to EmbyTV and also to TVHeadend so thanks in advance for your patience. Having said that my setup is composed of TVHeadend 4.0.8, a HDHR Connect (DVB-T) tuner and Emby 3.0.5786 (latest stable). After dealing with some configuration mistakes I made I managed to understand more or less how the tvh plugin interacts with Emby and TVH. I did a couple of recordings and while watching them I noticed that trick modes are not available. I mean I can pause playback but I cannot fast forward, rewind or resume (after stopping playback) a recorded video. Is this the way it works or I have another configuration issue somewhere (probably on the TVH side)? To add more information, in TVH the recordings are saved in a TS file. MKV is also available, I didn't try to change the configuration yet, but switching from TS to MKV would give me access to trick modes? Any reason not to switch to MKV? Thanks.

Hello all, Odd thing started happening this past week. Emby has been recording my live TV shows through an HDhomerun tuner. I have series set to record and it had been doing a great job of catching them... until this past week when my wife asked why one of her shows wasn't recording. I've checked that the HDhomerun is configures in the system and the guide is updating. I see the series listed, but nothing is showing as scheduled to record. advTHANKSance

Recordings are no longer working. Excerpt from server log: (The rest before is nothing but a million lines about browser logins etc) 2015-10-28 23:30:06.1622 Info - Main: Emby Command line: C:\Users\Simba\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 4 64-Bit OS: True 64-Bit Process: False Program data path: C:\Users\Simba\AppData\Roaming\Emby-Server Application Path: C:\Users\Simba\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe 2015-10-28 23:30:06.6465 Info - App: Application version: 3.0.5768.7 ........ 2015-10-28 23:56:12.5531 Info - HttpServer: HTTP POST http://192.168.0.20:8096/mediabrowser/Sync/Data?format=json Ip: 192.168.0.108:46336. Headers: X-MediaBrowser-Token=dedb93cafdf44fc0871ec2f1bdd2c138,X-Emby-Authorization=MediaBrowser Client="Emby for Android", DeviceId="8860e60c-6f87-f472-3524-520637621489", Device="VS985 4G", Version="2.4.30", UserId="012f9ee120204661a36a41346c06d0b1",Content-Type=application/json,User-Agent=Dalvik/2.1.0 (Linux; U; Android 5.1.1; VS985 4G Build/LMY47V),Host=192.168.0.20:8096,Connection=Keep-Alive,Accept-Encoding=gzip,Content-Length=123 2015-10-28 23:56:12.5687 Info - HttpServer: HTTP Response 200 to 192.168.0.108. Response time: 15.5969 ms. Url: http://192.168.0.20:8096/mediabrowser/Sync/Data?format=json 2015-10-28 23:56:54.8037 Info - App: IntervalTrigger fired for task: Cache file cleanup 2015-10-28 23:56:54.8037 Info - App: Queueing task DeleteCacheFileTask 2015-10-28 23:56:54.8037 Info - App: Executing Cache file cleanup 2015-10-28 23:56:54.9286 Info - App: IntervalTrigger fired for task: Download missing subtitles 2015-10-28 23:56:54.9286 Info - App: Queueing task SubtitleScheduledTask 2015-10-28 23:57:11.4288 Info - App: Cache file cleanup Completed after 0 minute(s) and 16 seconds 2015-10-28 23:57:11.5538 Info - App: Executing Download missing subtitles 2015-10-28 23:57:11.5538 Info - App: Download missing subtitles Completed after 0 minute(s) and 0 seconds 2015-10-28 23:59:00.0083 Info - App: Recording timer fired. 2015-10-28 23:59:00.0239 Error - App: Error recording stream *** Error Report *** Version: 3.0.5768.7 Command line: C:\Users\Simba\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 4 64-Bit OS: True 64-Bit Process: False Program data path: C:\Users\Simba\AppData\Roaming\Emby-Server Application Path: C:\Users\Simba\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Program with Id EP018603210007T635816916600000000C860 not found System.InvalidOperationException at MediaBrowser.Server.Implementations.LiveTv.EmbyTV.EmbyTV.<RecordStream>d__7f.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Server.Implementations.LiveTv.EmbyTV.EmbyTV.<_timerProvider_TimerFired>d__74.MoveNext() 2015-10-29 00:00:00.0090 Info - App: DailyTrigger fired for task: Start new log file 2015-10-29 00:00:00.0090 Info - App: Queueing task ReloadLoggerFileTask 2015-10-29 00:00:00.0090 Info - App: Executing Start new log file This is happening on any recording I set.....any channel...any time. Last successful recording toke place 4 days ago (10-25). I have rebooted the server program, and the computer it is running on (Intel NUC i5 model).

Hi all, Some of my OTA recordings are full of glitches, and I think it's not about the signal or antenna. I want to try recording via something else than WMC's built in recording function. Same channel that glitches always looks nice using SiliconDust quick TV viewer. I'm a long time emby/MB user. I've got the server and MBC on the HTPC. In addition to Emby it also records TV OTA via WMC. My HTPC is a bit dated (circa 2009 AMD X2 Kuma processor), though the OS is on a newer SSD and I've got an adequate Radeon 5670 graphics card. Two SiliconDust boxes (an older 2009 one, and a newer smaller one from 2011). Gigabit wired network throughout the house. I've changed antennas, optimized which tuner for which channel, etc.. but I often get glitches, mostly on one channel but sometimes on others. Never when just viewing the channel with the SiliconDust software. I think the problem may relate to the computer being a bit overloaded (recording time of day often conflicts with viewing time of day), but I'ld like to try software changes first. Can somebody please point me to a primer on what software for recording OTA works well with Emby? And any recommendations about which solutions are good are always appreciated. Thanks! Marc

Hi, I'm running MediaBrowser for Win7x64 and I use Media Center TV with set-top-boxes. It's great to be able to log in to media browser outside of my home and watch live tv or older recordings from a web browser. The only thing that bugs me is when I watch active recordings. I cannot seek. Like right now I'm recording a live tv sports event and it's a 360 minute recording and the only way for me to watch the active recording is to start from the beginning. If I stop and want to start again later, I have to start from the beginning. It's impossible to seek into the active recording. Once the recording has finished It's just like a normal video file and I can seek but I often I would like to watch when recordings are active. For me this is almost an unusable feature to use. Would it be possible to make seeking available feature for active tv recordings (WMC) ? Best regards, Arni Thor

On many (but not all) of the shows that are being recorded (wtv), the transcoder will fail to process the file while attempting to play it via the web browser interface. There seems to be two issues at work here (the transcoder tries two different output formats), but both fail for different reason. First, conversion to mp4 fails because it attempts to use libvo_aacenc to encode the audio. Everything I've read indicates that this is the worst and least supported AAC audio encoder that ffmpeg allows, and should not be used. Second, conversion to webm fails because it chokes on the eia_608 subtitles. I do not know why. ffmpeg-381a255a-6630-46a0-8969-59c3d0ca768c.txt ffmpeg-93e39394-0955-4a7a-9f19-7ff7441ea1ec.txt

Hi! I do alot of tv recording and there seems to be a glitch when reading file info for tv recordings. I created a collection/folder that points to my Windows Media Center - "Recorded TV" folder. When browsing through the list, some of the info is incorrect like recording length, date and preview (screenshot). This seems to be random. For instance I recorded the attached file "MB3 - tv rec sample 5.png" last night and It has a screenshot and info but incorrect length. But when I open the file properties in windows explorer the correct info is there. Could it be that MB3 server is trying to read the info while Media Center is recording (writing to the file) and get's the incorrect data? I've tried (from web interface) the refresh button for one file and also for the parent folder with refresh child items checked but it does not fix the issue. It would be nice to see the air date and/or recording date and maybe have a sort option for that. Reg, Arni Thor