Forum: Subtitling
Topic: Any recommendation for a non-cloud proprietary subtitling/captioning software written in .NET?
Poster: Novian Cahyadi
Post title: The reasons
[quote]Michel Virasolvy wrote:
I've been working with SE for nearly 10+ years as a professional on Linux, and so far the very few clients that demanded me to use a proprietary software were using very exotic formats, some of them even dating as far as WW2. So… any particular reason you need the software to be both proprietary and developed in .NET? Just out of curiosity. [/quote]
Thank you for replying. :-)
Anyway, that's the exact reason. On very rare occasions, some clients required me to work on their projects using a proprietary subtitling software, didn't matter which one. When I mentioned that I mostly use SE and Aegisub, they immediately turned me down. I'd like to have it ready just in case something like that would ever happen again.
As for the .NET requirement, as I mentioned in my original post, because I'm running SE through Mono and it has been running flawlessly on my Linux system. SE is written in .NET, so naturally I'd prefer to use another software in the same programming language. Running a subtitling software written in any other than .NET probably would need to be done through Wine, which I'm really trying to avoid. I find it to be rather bloated.
Topic: Any recommendation for a non-cloud proprietary subtitling/captioning software written in .NET?
Poster: Novian Cahyadi
Post title: The reasons
[quote]Michel Virasolvy wrote:
I've been working with SE for nearly 10+ years as a professional on Linux, and so far the very few clients that demanded me to use a proprietary software were using very exotic formats, some of them even dating as far as WW2. So… any particular reason you need the software to be both proprietary and developed in .NET? Just out of curiosity. [/quote]
Thank you for replying. :-)
Anyway, that's the exact reason. On very rare occasions, some clients required me to work on their projects using a proprietary subtitling software, didn't matter which one. When I mentioned that I mostly use SE and Aegisub, they immediately turned me down. I'd like to have it ready just in case something like that would ever happen again.
As for the .NET requirement, as I mentioned in my original post, because I'm running SE through Mono and it has been running flawlessly on my Linux system. SE is written in .NET, so naturally I'd prefer to use another software in the same programming language. Running a subtitling software written in any other than .NET probably would need to be done through Wine, which I'm really trying to avoid. I find it to be rather bloated.