-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing Glue #1
Comments
This has now been re-implemented as "Emby.Server.Unix", need to look at application data logic and lib directory logic. Also need to figure out why it's trying to implement native sql instead of SQLite.Net.Core-PCL. 1 or 2 other bugs persist. |
Hi @dcrdev , Are you still trying to clean up this 're-implementation'? I am willing to help with your efforts here. At least with developer feedback and testing out your changes...... |
Hi, to be honest it's done - bar the runtime downloading of external libraries. I had put this on the back-burner for a while due to external commitments. I really want to finish this off though - so hopefully will resume working on it this weekend. |
Any news here? |
yea any news |
Any of you willing to help out? |
What help do you need?
Thanks,
Vasily
ср, 10 окт. 2018 г., 22:09 Dominic Robinson <notifications@github.com>:
… Any of you willing to help out?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA9vRvXlP5kQZJohYNCTm47W3b4bVTF2ks5ujkX-gaJpZM4TLUzq>
.
|
Hate to be that person, but I really don't want this to die out, and am beginning to face issues with emby-unlocked due to Chrome updates. Any chance you could push the project files so others can take a look and try squash bugs too? I understand there are alternatives such as https://github.com/JustAMan/Emby, but they derive quite significantly from the original repo. |
@zacharyrs |
@JustAMan, saw that and linked it. Unfortunately your source seems to derive significantly from the original. I was hoping to keep my tree closer, to enable easy porting over. Plus there's that very large commit by stefen (if I remember correctly), that I'd rather not browse through and try to comprehend... |
I do not know well enough how much is the difference, as I took @h3ge repo as a base. I do not care much, though, as what I wanted was to have source code to be able to investigate and fix stuff if it breaks while running at my home :) There're also a few binary blobs still in there which I want to eventually replace with compiled versions. What exactly "porting over" you want to achieve? Maybe we can join forces somewhere? |
I did look a little into it, but it was a bit much to read. For now I'm just using 3.4.0.0, with patched css to fix bugs etc. By porting over, I meant just making it easy to merge any future changes to the main repo. Honestly I think I might try writing a basic program in python or rust to handle video identifying, transcoding and streaming. Probably inspired by github.com/nvllsvm/maelstrom, but with a much prettier webapp frontend. That'll have to be over the christmas break... |
Emby is mature enough to be too hard to replicate all the features in a week or two, IMHO. That sounds like Streama, which is under active development for quite a while and is very much not on par with Emby yet, at least for my use case (having WebOS TV, Tizen TV and laptops with browsers and wanting to watch content using any of these). If you want to go that route I'll certainly follow your progress anyway :) Merging from upstream is something I'd like to try eventually as well. |
Yeah, that's why I've stuck with emby so far. |
It appears as though the upstream netcore package not only does not have the updated project files published, but also there is also a application host project that's not being published in the repository.
That project "EmbyServer" needs to be re implemented, in order to run Emby. It's going to take some time to do this.
The text was updated successfully, but these errors were encountered: