OpenSubtitles-Uploader (Windows/Linux/OSX)

[vankasteelj]

[START Edit by SmallBrother]
You can translate this application online, using Transifex: https://www.transifex.com/vankasteelj/opensubtitles-uploader-nwjs/
To join the translators team, create a free account and ask to join the "vankasteelj/OpenSubtiltes-Uploader" project in your language. After approval, you can add your translations.
[END Edit by SmallBrother]

I've used my free time this past week to make an application for OpenSubtitles. The goal was to provide an easy app to upload subtitles, since the Java-thing never worked for me.

Software is out, download it on GitHub!

Youtube video "how to" tutorial: https://youtu.be/jrIgL8kwBdI

So, what is it? For now, it's called "OpenSubtitles-Uploader" because of the lack of inspiration. It's a node.js/html5 application, portable, and running on multiplatforms (windows, linux, osx).

What are the features? Everything you'd expect from an uploading app: take a look at the UI, it's all there:


The aim is to provide the most easy and efficient way of uploading subtitles. For this, I automated almost everything. The hashes are calculated on the fly, the fps, framecount and total runtime (in ms) are extracted automatically, and it features a search for imdb if not found on its own. It also uses osdb protocol to automatically populate OpenSubtitles database.

Behind the curtains, it's just javascript/html5/css and jquery, bundled in nwjs (node-webkit) to enjoy the power of node. I also support (only on windows & debian derivatives atm) MediaInfo, to gather data about the files dropped in there.

A gif is worth a thousand words, so here you see it in action:



Now, I have to polish that, the UI is not finished (read the readme on github for the "todo", link below). I also might have to find another name, as "OpenSubtitles-Uploader" makes it look a little like "official". And I need a UserAgent, I'm playing with OSTestUserAgent right now, which is bad. But to request an UA, I need a name^^

The end goal behind this app? Nothing. I just wanted to see if I could (and I'm glad I can )


Please share any thoughts!

Github link:https://github.com/vankasteelj/opensubtitles-uploader
There is no released version yet, so if you want to try it, you'll have to have Node.JS installed, then:

Code: Select all

npm install -g grunt-cli npm install grunt setup

And open the app with:

Code: Select all

grunt dev

[MarcoTC]

That's awesome!
Impressive. Very cool!

[oss]

this is great. I hope one day it will be available on opensubtitles

[SmallBrother]

Looks VERY nice.

Until recently I always uploaded manually through the web site, because (for whatever reasons) I didn't like all the other methods. Bad side is that a hash code was always missing. I recently found the upload plugin for SE, which is my solution now. Otherwise your application would be it.

Few remarks:
- IMDb ID: I can imagine something goes wrong with automatic detection, due to similar or even the same movie names. For that reason I think it would be good to have some manual checking method. Maybe have the IMDb title displayed.
- Release name: Maybe movie release name can be automatically extracted form the subtitle file name? Or (maybe better) with a mouse click ("same as subtitle file" or so). And maybe stripping trailing language stuff like ".eng" and ".nl" and the 'duplicate copy' specific " (2)", " (3)".
And if this field remains empty, maybe have the video file size in bytes and/or duration displayed, to have at least SOME identification info.
- Translator: There is no input field for Translator. This is a relatively new field, so far only available with web upload.
- Comment: Would be nice to have a bit more (vertical) space, I mean a box rather than a line.

[vankasteelj]

thanks all!

@SmallBrother:

- IMDb ID: I can imagine something goes wrong with automatic detection, due to similar or even the same movie names. For that reason I think it would be good to have some manual checking method. Maybe have the IMDb title displayed.

Mmmh, let me think about that, not a bad idea and would probably be easy to make.

- Release name: Maybe movie release name can be automatically extracted form the subtitle file name? Or (maybe better) with a mouse click ("same as subtitle file" or so). And maybe stripping trailing language stuff like ".eng" and ".nl" and the 'duplicate copy' specific " (2)", " (3)".

Is that the release name? Looks like the filename to me, no? I do not know what "release name" is exactly, I thought it was like: "LOL" or "SHAANIG".

And if this field remains empty, maybe have the video file size in bytes and/or duration displayed, to have at least SOME identification info.

That's already the case, isn't it? I'm not sure I get the link between releasename and bytesize/duration. Here is what a sub uploaded with that tool looks like: http://www.opensubtitles.org/en/subtitl ... chmaker-fr

- Translator: There is no input field for Translator. This is a relatively new field, so far only available with web upload.

Is that on the API too? If yes, it's easy to add, i'll do it directly in opensubtitles-api module.

- Comment: Would be nice to have a bit more (vertical) space, I mean a box rather than a line.

*gmbl* that's work because I need to switch from <input> to <textarea> and make css for it

[SmallBrother]

- Release name: Maybe movie release name can be automatically extracted form the subtitle file name? Or (maybe better) with a mouse click ("same as subtitle file" or so). And maybe stripping trailing language stuff like ".eng" and ".nl" and the 'duplicate copy' specific " (2)", " (3)".

Is that the release name? Looks like the filename to me, no? I do not know what "release name" is exactly, I thought it was like: "LOL" or "SHAANIG".

Well, not necessarily. Not every LOL or ETRG or whatever is the same (WebDl or Bluray or etc). And also people could have renamed the video file - and subsequently the subtitle file name.
Release name is the exact name of the video file as it was published. For example MovieName.1970.720p.BRRip.x264.MYEGO.mp4
Typically the subtitle file name will have the same name (MovieName.1970.720p.BRRip.x264.MYEGO.srt) - because it's the most elementary way to use this file while playing. That's the connection between subtitle file name and release name.
BUT
Sometimes people rename the video file (MovieName.Horror.720p). Or they use a subtitle file for another release which was resync'ed to thier release. And they just drag it into VLC player to use it, instead of renaming it.
See the connection - and the problem?

And if this field remains empty, maybe have the video file size in bytes and/or duration displayed, to have at least SOME identification info.

That's already the case, isn't it? I'm not sure I get the link between releasename and bytesize/duration. Here is what a sub uploaded with that tool looks like: http://www.opensubtitles.org/en/subtitl ... chmaker-fr

Again - not necessarily
In your example there is nowhere mentioned what is the file size or duration. Not needed, if there is a releasename (which is correct) and a hash code. But I mean when there is nothing, when the uploader decides to leave it empty, or when the video file was renamed to a pretty generic MovieName.mp4 (and he doenst remember anymore what the release name was).
In that case it would be nice to have some 'strict' identification. File size (in bytes, NOT kilobytes) is then a method.

- Translator: There is no input field for Translator. This is a relatively new field, so far only available with web upload.

Is that on the API too? If yes, it's easy to add, i'll do it directly in opensubtitles-api module.

I dont get it
I am an admin, but I know ZILCH (nada, zero, nothing) about API...

- Comment: Would be nice to have a bit more (vertical) space, I mean a box rather than a line.

*gmbl* that's work because I need to switch from <input> to <textarea> and make css for it

Sorry about that
And yes, that one pixel difference in IE an FF and OMG ....
But yes, often a lot of stuff is written. Textarea would really make sense.

[vankasteelj]

In your example there is nowhere mentioned what is the file size or duration.

wait, what?! The file size, I see it myself on the example... But about duration... eh that's a bug in the API! @oss here's what I send:



----------------------

About releasename: then it's too risky, people will hit "send" even if the wrong releasename was set, they won't care (I know how people are... Trust me I work in communications). Better let them fill that in if they know what it is.

----------------------

it would be nice to have some 'strict' identification.

You must have missed the mandatory "filesize" field then. I always send moviebytesize, along with hash.

----------------------

That "translator" is not described in the API docs. Either it's not documented (in which case, please @oss what's the exact string you expect?) or it's simply not present at all.

[SmallBrother]

Haha, look at an API and a web guy talking...

In your example there is nowhere mentioned what is the file size or duration.

wait, what?! The file size, I see it myself on the example...

You are right. I meant (and was only focused on) file size as release name (if it's absent). Because now it's there, but only as part of the hash code data:



If it is 'release name' and written in a human style (183,484,298 bytes) it would be visible and recognizable when doing a web search:



But now I am thinking that maybe this shouldn't be done on your side yet...

About releasename: then it's too risky, people will hit "send" even if the wrong releasename was set,

You are right. Better have it empty - this will happen, trust me than have it wrong.

it would be nice to have some 'strict' identification.

You must have missed the mandatory "filesize" field then. I always send moviebytesize, along with hash.

Yeah, no, I meant 'human readable', see above.

That "translator" is not described in the API docs. Either it's not documented (in which case, please @oss what's the exact string you expect?) or it's simply not present at all.

Oss...?

[oss]

I am around and reading what you are writing guys. I can add Translator field to API, not a biggie. Other things - works like charm. But one have to realise this will be not on opensubtitles.org website (or any other internet website), because it is local thing. Similar like you download and install and run executable...

[vankasteelj]

well, I'm almost done, as soon as I have a useragent, i'll release a test version

[oss]

'subtranslator' added in Upload() XML-RPC

[vankasteelj]

'subtranslator' integrated both in opensubtitles-api and OpenSubtitles Uploader.

I've also cracked OSX mediainfo binary (well... cracked... how it works, I mean, it's open-source), so all OS are now covered.

I think I've done everything requested and more. I'm almost done, I need to:
- add a small 'about'
- find out how to build a .dmg or .app (maybe .pkg) for osx release
- build releases and installers

Then we're good to go public.

[vankasteelj]

Good news everyone,

Version 1.0.0 is out, download it on GitHub!

Please test it and use it. All feedback is welcome

[oss]

great news, I have to try it

[oss]

I can test on OSX. So for me, when I download, extract and doubleclick app, nothing happens. It is possible to run it in some debug mode, so I can have access to log files ?