Search the Community
Showing results for tags 'firefox'.
-
Hi there, I installed the emby plugin in openmediavault (2.1.8) (debian wheezy 7.8) on my HP N40L (8 GB) (details seen in the following pics) and I'm quite impressed :-) One thing is bothering me: I can open on my "photos" and see all my indexed albums. When I click on one specific album, I see the following: When I point on an individual photo and click on the dots and then on "metadata info" I see So far, so good. Even when I click on "phoito info" I get, what I expect: But when I click on the photo right from the album view, I get a (nearly) blank screen (even after waiting minutes, although wired through 1 gigabit). I can not see any corresponding entries within the logfile. So what can I do? Any helpful recommendations are quiet welcome. Thanks in advance.
-
Playto "Edge" shows spinning dot in center that keeps going around and around and around... its like watching a little bug crawling on my monitor. Using Windows 10 Home w/Edge browser and playing to it from FireFox. I do this so that I can keep it full screen on my second monitor while not messing with my browsing in FireFox. Sadly I no longer have WMC w/external MPC and Emby Theater is so unstable it is not an option. Any idea on how NOT to see this dot (pixel) going around in circles or another alternative? I do see in the server config, that this file is transcoding. Is that why there is a spinning dot?
- 3 replies
-
- Edge
- Windows 10
-
(and 2 more)
Tagged with:
-
I recently installed MediaBrowser on my Mac (which is now running Yosemite). After the installation completed, the setup wizard automatically launched in my default browser, which is Chrome. After completing the setup wizard, I went to take a look at my media, but I was greeted with a blank screen with absolutely no graphics. Even my photo that I had uploaded for my profile was missing. Thinking that the server was still processing everything, I decided to give it a while and just check back later. When I came back a few hours, I was greeted with the same blank screen devoid of any graphics. I deleted the cache and browsing history in Chrome, but still nothing showed up. For some stranger reason, I decided to try to access the server using Firefox. A few minutes later I was looking at a screen full of movie posters. Even my uploaded photo was present at the top of the screen. A quick check of Opera and Safari yielded the same result...everything looks fine in those. So I decided to move on to the mobile clients. I downloaded Mark's MediaBrowser Android Client, and was unfortunately met with the same lack of graphics that I had on my Mac when using Chrome. However when I try BubbleUPnP or MediaHouse-Pro on the same Android device, everything seems to work just fine and all of the graphics are there. I moved on to my iPhone and tried the Media Browser for iOS client, then on to my iPad where I tried the Media Browser Client and all appears to be working fine there. My frustration is that Chrome is my default browser on my computer, and my Android phone is my primary device (and I want to use Mark's MediaBrowser Android Client as my default Android app). I rarely carry my iPhone with me, and I don't want to have to take my iPad with me every time I think I might want to watch a video. I want to be able to watch movies on my Mac using Chrome and use the MediaBrowser Android Client to push my movies to Chromecast when I'm away from home. Any suggestions? I've already tried a fresh installation, following the steps listed on Page 2 of the installation faq, but I'm still getting the same issue. I'm at a loss. Hopefully one of you can shed some light on the situation. Post includes screen shots illustrating what I've described. Log files from the new install done today are located in the attached zip file. Chris ServerLogs.zip
-
Has anyone else had an issue with the newest firefox update? After the update I am no longer able to hear sound even when using direct method through media browser, although I still get sound from streaming sites like hulu. It works fine in chrome still.