All Activity

What example are we focusing on in these log files?

What do you mean by same old locations?

Ok yes now I found it, it’s available only when I use “TV mode”, but still the horizontal problem persists, it’s not in everything but mainly still the same old locations .

I apologize for the delay. The emby server is up2date and I was having no issue with the truehd7.1 until I updated the shield emby app. Issue remains with only truehd7.1 audio codec. When I change to another codec, no problem. Emby is still awesome. Thank you. NOTE: when I updated the app it gave the option to try another emby app android interface. I did not wish to push my luck like if I did not like it could I go back, but now I wonder. I will also endeavor to return to the previous app on the shield. I appreciate your effort. Thank you. To tidy things up a bit, please close the thread.

i added log in first post but here are some others not sure what one it would be in now. these are from the 5/6th embyserver-63921571200.txt embyserver-63921657600.txt embyserver-63921589611.txt

I’m sorry but still I can’t find it, here’s what I see ..

I appreciate the clarification from everyone. To be clear, yes, EmbyCredits was the starting point in the sense that it was the existing project I wanted to remain compatible with. That was the reason for using it as a reference point — so the new services could work alongside it and be useful to existing users, including users who may want to migrate slowly to another solution if they have AV1 content or other specific needs like I do. It was never intended to imply that the entire concept of credit detection belongs to one project. Detecting credits in media is a general problem, and different implementations can approach it in different ways. The reason I created this was to build a different architecture with the features I wanted: dedicated OCR services, CPU/GPU editions, Docker-based backend services, new detection engines, expanded configuration, and a more flexible workflow. I also want to emphasize that compatibility was part of the goal from the beginning. The OCR services can be used with EmbyCredits, and users can run both projects side-by-side if they choose. I appreciate the questions because it gives me a chance to clarify the relationship properly. That said, I think I have explained the history and intentions clearly, so I will be stepping back from further discussion on this thread. I’ll continue focusing on development and supporting users through the appropriate channels.

The ones thing this needs is to be able to use discogs or music brainz for identifying the media. Instead of the movie database, tvdb, IMDb, or be able to switch between the metadata sites.

Piracy was also one of the reasons they stated as being part of this. The amount of dmca requests they probably had to deal with on a daily basis must be staggering. Some legitimate, some bogus, all requiring paid attorneys to review and respond. I know it because we deal with it and we don't even provide content. To not have to deal with that anymore was one of their stated goals.

They already had this before, it's just that the whole system was hard for them to work with and maintain because it wasn't theirs. Yes, they used the Android OS to get a head start and build market share, but eventually the relationship ran it's course and they decided it was no longer sustainable. They need to be able to control internal policies, api's, etc, and they can't do that with somebody else's OS. I don't think they intended to punish the small segment of enthusiasts with custom launchers. I think that just became casualty in order for them to solve their bigger problems.

I just disagree, which is fine "It wasn't about money" ignores Amazon's entire revenue strategy. Amazon doesn't make profit selling $30 streaming sticks. They profit off the home screen real estate, sponsored ad banners, and transaction fees from inside the ecosystem. On Fire OS, custom launchers and ad-blockers allowed users to bypass that entire monetized pipeline. Replacing Android with Vega OS permanently seals those financial leaks. They waited because they needed Android's app library to build market share and defeat early competitors like Roku. Once they achieved dominant market position, they pulled the ladder up behind them. Using open Android to build a user base and then locking it down once established is a classic tech platform play.

It works. Thank you.

If our app gets pulled from the store, I don't think google would accept the explanation that our users were running in developer mode.

WOuld it be possible, that if the android device is in "developer mode" then it would show all?

Yes of course. The loss of sideloading is a negative. But what I listed as the reasons for change are still true and that this wasn't about money. They started depending on android in 2014, so to go 12 years and then pull the rug out is really hard and going to upset a lot of people. If they had done this say, 8 years ago, the impact would have been smaller, by now they'd have a large catalog of apps, and who knows, with enough user pressure over time they may have brought back some form of sideloading.

Like many, I’d never buy a Vega device: Because Vega OS isn't built on Android, it can’t run standard .apk files. Amazon intentionally locked the system down, completely eliminating the "Install from Unknown Sources" toggle. For the enthusiast community, losing the ability to sideload apps or customize the software environment is an absolute dealbreaker. Vega OS exists primarily to give Amazon total control over the hardware. Third-party home screen launchers, deep system tweaks, and custom background services are completely blocked. For anyone who wants an ad-free interface or full control over their home theater hardware, Vega OS is just too restrictive and tied to Amazon’s ad ecosystem.

Why would this matter here? Keeping it left makes more sense, because you are using a remote to navigate your Apple TV. Having as few clicks as possible is a better user experience in my opinion.

That is not true. They did to free themselves of an operating system designed by another company, and to not be controlled by Google's licensing policies and update timelines. Their new OS should perform better as it doesn't come with any android bloat, has a lower memory footprint and faster navigation. The reasons for doing it are good, but obviously change is hard.

This is kinda irrelevant since this for the Apple TV and not a touch display. I'm assuming the reasoning to have it on the left side is so it can be easier to navigate to with the remote, rather than having to go all the way right to get to the letters. I think having a setting to choose between having it on the right or left would satisfy everyone.

HI there, can you please provide a specific example? How to Report a Problem Thanks !

Just to be 110% clear!! People can do what ever they want with my plugins, they can even call it their own and start taking money for it if they want. I was just curious if it was based on EmbyCredits, nothing else! I know @Neminemdoes nothing but help people on this forum, he just made a miscalculated joke. @EncryptedCityNot that you need it, but you have my permission to build upon EmbyCredits. It's also MIT license so everyone can do what ever they want. I'm extremely happy when something i made can be used by others in what ever way they like. My TimeMarkEdit is also build upon a nother plugin (ChapterAPI) so i know how it feels to want to improve something. That should hopefully clear everything up.

Yes as this is the FireTV sub. Amazon really did a disservice to their customers by releasing this product. It's all about greed, nothing more. No one should be buying these new devices.

I just came to realize that the web /browser version of emby is substantially cleaner than theater/app. Images are crisper and less compressed. Is there a setting somewhere in theater that can improve it? I don't really like watching through a browser.

Here's evidence:

@EncryptedCity I read @yocker's questions as being polite and respectful; I honestly didn't read it as an accusation (which implies a level of impropriety) but more as a fair question given they're the dev behind EmbyCredits and there are similarities to both. I also think that @Neminemwas just being playful. I'm new here, don't know anyone, and am looking forward to trying both plugins out.