Forum: Subtitling
Topic: Any recommendation for a non-cloud proprietary subtitling/captioning software written in .NET?
Poster: Michel Virasolvy
Post title: 2 Options: (1) Back to the Windows or (2) Explore the Linux Seas
[quote]Novian Cahyadi wrote:
[…]
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.
[…][/quote]
I'm just throwing my two cents here but of course, others are welcome to back me up or refute me on this.
First, if a client turns you down because you're using FOSS for subtitling, it's already a yellow flag. It means that company does not know anything about the professional subtitling industry, and they most likely never worked with professional translators, at all. Best case scenario, they had a bad experience with some scammer and they infered from that single experience that all language service providers must have 8K€ softwares to produce the 100% text files that are subtitle files.
Second, the fact they demand you to use a proprietary software, and you accepting, means you're okay with them bossing you around like trash before discarding you. If you're freelance, you're the one setting the rules, your client, not matter the size, is your client. If you say you use FOSS to work and they don't want to work with you, it's their loss, not yours. You have the skills and experience, it's only fair they agree to your terms of service… and rates. That here is a red flag for me.
On a side note, if you subtitle a work of fiction, you are also considered an author and your client is therefore expected to sign a collective contract to pay you first the commission (for the work itself) and royalties (every 6 months, for exploitation). I'm mentioning this here because a number of VOD companies are still trying their absolute best to lobby their way out of royalties. If you weren't aware, now, you know.
Third, even assuming you do find a good proprietary .NET software to reassure your potential clients, if you don't already have some background experience or a valid ISO 17100 certification to show them you're worth the money, they may still deny you any kind of collaboration. Worse, if your current, paying client just doesn't have any more text to send your way, you're in for a ride because these days, proprietary softwares are monetized ‘as a service’, meaning you'll have to keep paying to use them or go back to SE anyway.
For these minor, questionable reasons, I suggest you either stand your grounds as a Linux-based professional, or get to Windows in the hope to find clients able to pay you the software you seek and cover your licence fees.
Now, I'll be honest, SE does have a couple of drawbacks for pro subtitlers like me:
— No glossary management.
— No active CPL (to prevent the lines from getting too long).
— No management for multiple sound tracks of source files (if you want to mute the background noise and just get the sampled voices, for instance).
To some extent, I would appreciate if SE had a FOSS competitor. But to go proprietary for the sake of having 1 or 2 clients who will treat you like a worthless commodity? That's like accepting to be handcuffed to a typewriter and thrown down a well. Who in their right mind would agree to that?
Just a reminder, though: that's only my take on the matter. If Novian can find his typew… I mean, his proprietary subtitling software, good for him.
Topic: Any recommendation for a non-cloud proprietary subtitling/captioning software written in .NET?
Poster: Michel Virasolvy
Post title: 2 Options: (1) Back to the Windows or (2) Explore the Linux Seas
[quote]Novian Cahyadi wrote:
[…]
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.
[…][/quote]
I'm just throwing my two cents here but of course, others are welcome to back me up or refute me on this.
First, if a client turns you down because you're using FOSS for subtitling, it's already a yellow flag. It means that company does not know anything about the professional subtitling industry, and they most likely never worked with professional translators, at all. Best case scenario, they had a bad experience with some scammer and they infered from that single experience that all language service providers must have 8K€ softwares to produce the 100% text files that are subtitle files.
Second, the fact they demand you to use a proprietary software, and you accepting, means you're okay with them bossing you around like trash before discarding you. If you're freelance, you're the one setting the rules, your client, not matter the size, is your client. If you say you use FOSS to work and they don't want to work with you, it's their loss, not yours. You have the skills and experience, it's only fair they agree to your terms of service… and rates. That here is a red flag for me.
On a side note, if you subtitle a work of fiction, you are also considered an author and your client is therefore expected to sign a collective contract to pay you first the commission (for the work itself) and royalties (every 6 months, for exploitation). I'm mentioning this here because a number of VOD companies are still trying their absolute best to lobby their way out of royalties. If you weren't aware, now, you know.
Third, even assuming you do find a good proprietary .NET software to reassure your potential clients, if you don't already have some background experience or a valid ISO 17100 certification to show them you're worth the money, they may still deny you any kind of collaboration. Worse, if your current, paying client just doesn't have any more text to send your way, you're in for a ride because these days, proprietary softwares are monetized ‘as a service’, meaning you'll have to keep paying to use them or go back to SE anyway.
For these minor, questionable reasons, I suggest you either stand your grounds as a Linux-based professional, or get to Windows in the hope to find clients able to pay you the software you seek and cover your licence fees.
Now, I'll be honest, SE does have a couple of drawbacks for pro subtitlers like me:
— No glossary management.
— No active CPL (to prevent the lines from getting too long).
— No management for multiple sound tracks of source files (if you want to mute the background noise and just get the sampled voices, for instance).
To some extent, I would appreciate if SE had a FOSS competitor. But to go proprietary for the sake of having 1 or 2 clients who will treat you like a worthless commodity? That's like accepting to be handcuffed to a typewriter and thrown down a well. Who in their right mind would agree to that?
Just a reminder, though: that's only my take on the matter. If Novian can find his typew… I mean, his proprietary subtitling software, good for him.