Search the Community

Request: curl -X "POST" "http://localhost:8096/emby/System/Ping" Response: HTTP/1.1 200 OK Date: Sat, 15 Jun 2019 18:16:25 GMT Connection: close Content-Length: 11 Server: h2o-dev Access-Control-Allow-Headers: Accept, Accept-Language, Authorization, Cache-Control, Content-Disposition, Content-Encoding, Content-Language, Content-Length, Content-MD5, Content-Range, Content-Type, Date, Host, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, Origin, OriginToken, Pragma, Range, Slug, Transfer-Encoding, Want-Digest, X-MediaBrowser-Token, X-Emby-Token, X-Emby-Authorization Access-Control-Allow-Methods: GET, POST, PUT, DELETE, PATCH, OPTIONS Access-Control-Allow-Origin: * Content-Type: application/json; charset=utf-8 Emby Server The response header Content-Type incorrectly defines the body type, text/plain. No biggie, just thought I'd send it

Hi Emby team, If I have two EPG sources, and some channels are present in both, then how do I prioritize / choose between them when merging? Also, daylight saving time seems to be different in UK and DK, so for periods in spring and fall, English channels are off-set by 1 hour when watching in DK. Is there a way to compensate the EPG (which then is 1 hour off)?

Hi Everyone, I'd like to report what seems to be a glitch/bug. I've been trying to set up the camera upload section for our mobile devices and everything was going great until I tried to set a custom path for each of the devices. According to the Camera Upload WIKI, there should be a place in the Devices section that allows me specify a path for the camera upload for each of the devices, but that option does not exist. I've attached screenshots to show what my server is displaying, I can set the base path under Sync -> Camera Upload, but the device itself under the device settings does not have an option for a specific path. I am currently running version 3.1.2.0 on Windows 8.1, and my mobile devices are running Android 6 and 7 In order to make my setup work for the moment, I edited the device.json file for the devices that have the feature enabled and changed the following line: From: "CameraUploadPath":"" To: "CameraUploadPath":"Drive:/Folder/Device1" After making the changes to the files and restarting the service, I re-checked the device in the Devices tab and all I see still is the name change option and nothing else. Camera upload is working fine so far, but there is no way to edit the specific path as described in the WIKI through the server interface nor the android app.

I made a KODI remote that works on an iPad. All data displayed on the iPad is fetched trough the XBMC JSON RCP. So to get information for all movies I am using the following command: {"jsonrpc":"2.0","method":"VideoLibrary.GetMovies","params":{"properties":["thumbnail"]},"id":2} This will give me all movies in the database of the Kodi client. One of the responses is the image path of the thumbnail. Because i let the system save the image in the folders of the movies I would expect that response would be something similar like: image://smb//server/movies/moviedir/coverwithmoviename.jpg That is also exactly what i got before using the emby server as movie manager. But now when i fetch a thumb i get: image://http%3a%2f%2f172.16.65.31%3a8096%2femby%2fItems%2f036ed9eb3863c9ddfd23a944557b2cca%2fImages%2fPrimary%2f0%3fMaxWidth%3d10000%26MaxHeight%3d10000%26Format%3doriginal%26Tag%3d59fa47e518f240a4bde9cd3fe52f6653/ This looks like the location of the emby webserver which I am finding strange because the posters are saved in the movie folder. Now this should not be a problem, but my system can not work with image strings longer then 256 characters (don't ask me why, the program environment is just stupid). I have tried to save the image path in the *.nfo and that is save correct but when i query Kodi whe the JSON command it still fetches the http server location and not the smb location. Is there something I could easily edit in some sort of xml file or make a change in the Emby settings or is this a bug?

Hi, I have been running NextPVR for a couple of years and it's working perfectly. I have been tryign to get this plugin to work but I just can't. Everything is setup good except that Live TV stream doesn't wanna play. This works: Status: OK Update Guide Create recordings Watch recordings See all channels and icons and whats on When I try to play ny channel this is what the Media browser log looks like: 2014-04-12 15:58:08.3520 Info - App: Client connected from 127.0.0.1:52636 2014-04-12 15:58:08.8824 Info - App: ScheduledTasksWebSocketListener Begin transmitting over websocket to 127.0.0.1:52636 2014-04-12 15:58:09.2256 Warn - StringMapTypeDeserializer: Property 'id' does not exist on type 'MediaBrowser.WebDashboard.Api.GetDashboardResource' 2014-04-12 15:58:09.4284 Info - App: HttpClientManager POST: http://192.168.1.107:8866/public/ManageService/Get/SortedFilteredList?sid=76e1b81467d24051af69e61413ba15f7 2014-04-12 15:58:31.5337 Info - App: Opening channel stream from Next Pvr, external channel Id: 7164 2014-04-12 15:58:31.6117 Info - App: C:\Users\Windows7\AppData\Roaming\MediaBrowser-Server\ffmpeg\20140304\ffmpeg.exe -fflags genpts -async 1 -vsync -1 -re -i "http://192.168.1.107:8866/live?channeloid=7164&client=MB3.1" -vcodec libvpx -force_key_frames expr:if(isnan(prev_forced_t),gte(t,.1),gte(t,prev_forced_t+5)) -vf "yadif=0:-1:0,scale=min(iw\,1280):-1" -speed 16 -quality good -profile:v 1 -slices 8 -crf 18 -maxrate:v 1372000 -bufsize:v (1372000*2) -b:v 1372000 -vsync vfr -map_metadata -1 -threads 2 -acodec libvorbis -ac 2 -ab 128000 -af "adelay=1,aresample=async=1000" "C:\Users\Windows7\AppData\Roaming\MediaBrowser-Server\transcoding-temp\3d219ca8-3db9-a8a9-3e45-2b1fe0183728.webm" 2014-04-12 15:58:35.6365 Info - App: HttpClientManager GET: http://bot.whatismyipaddress.com/ 2014-04-12 15:58:35.9173 Info - App: Closing live stream from Next Pvr, stream Id: 1 2014-04-12 15:58:35.9173 Info - App: FFMpeg exited with code 1 for C:\Users\Windows7\AppData\Roaming\MediaBrowser-Server\transcoding-temp\3d219ca8-3db9-a8a9-3e45-2b1fe0183728.webm 2014-04-12 15:58:41.1433 Info - App: Opening channel stream from Next Pvr, external channel Id: 7164 2014-04-12 15:58:41.1433 Info - App: C:\Users\Windows7\AppData\Roaming\MediaBrowser-Server\ffmpeg\20140304\ffmpeg.exe -fflags genpts -async 1 -vsync -1 -re -i "http://192.168.1.107:8866/live?channeloid=7164&client=MB3.2" -vcodec libx264 -force_key_frames expr:if(isnan(prev_forced_t),gte(t,.1),gte(t,prev_forced_t+5)) -vf "yadif=0:-1:0,scale=min(iw\,1280):trunc(ow/a/2)*2" -preset ultrafast -crf 23 -maxrate 1372000 -bufsize 2744000 -vsync vfr -map_metadata -1 -threads 0 -acodec aac -strict experimental -ac 2 -ab 128000 -af "adelay=1,aresample=async=1000" -f mp4 -movflags frag_keyframe+empty_moov "C:\Users\Windows7\AppData\Roaming\MediaBrowser-Server\transcoding-temp\01ba665e-b77a-b3db-62d2-abfb15d5db3b.mp4" 2014-04-12 15:58:42.1573 Info - App: Deleting partial stream file(s) C:\Users\Windows7\AppData\Roaming\MediaBrowser-Server\transcoding-temp\3d219ca8-3db9-a8a9-3e45-2b1fe0183728.webm 2014-04-12 15:58:51.7964 Info - App: Killing ffmpeg process for C:\Users\Windows7\AppData\Roaming\MediaBrowser-Server\transcoding-temp\01ba665e-b77a-b3db-62d2-abfb15d5db3b.mp4 2014-04-12 15:58:51.7964 Info - App: Closing live stream from Next Pvr, stream Id: 2 2014-04-12 15:58:51.7964 Info - App: FFMpeg exited with code -1 for C:\Users\Windows7\AppData\Roaming\MediaBrowser-Server\transcoding-temp\01ba665e-b77a-b3db-62d2-abfb15d5db3b.mp4 2014-04-12 15:58:51.7964 Info - App: Deleting partial stream file(s) C:\Users\Windows7\AppData\Roaming\MediaBrowser-Server\transcoding-temp\01ba665e-b77a-b3db-62d2-abfb15d5db3b.mp4 Any ideas on what can be wrong? I will attach the full log also.You can also see the two ffmpeg logfiles created on each try. mb3_log.txt mb3_ffmpeg_log1.txt mb3_ffmpeg_log2.txt

Hi Everyone, One thing I have not heard much about is how all these different clients can be controlled remotely. Is there a plan for some level of TCP communication - websockets for instance? Or maybe similar to XBMC with a JSON API?