Pre-subs Awareness in the Segging Process

I sort of spam it when I get a chance, and thanks to me writing every time segmenting is discussed we have been able to get more oldies back lately.

3 Likes

Is there a badge for the refresher course?

1 Like

No, but they get a card that you can add to your profile some students has done so already.

3 Likes

Hi everyone!
Sorry to see everyone is going through a difficult situation on Viki lately.
To be honest, we know nothing about what is going on and what is going to happen to us volunteers at some point.
Is it only me? or Viki has lost its uniqueness in the last years.

Viki was the only site on the internet that “used to have”

  • Subbing team members in different languages for all channels, translating in real time (No robots, I mean human beings. Come on, they do make the difference)
  • Korean scripts as reference available for Korean learners. (That was super awesome, now it’s gone with the wind)
  • Designation of vikiers as channel managers. It seems it’s coming to an end?
  • Qualified Segmenters (Vikiers who took the time to learn the basics to help, no robots)
  • Super segmenters status (A feature for Gold QC vikiers, willing to help anywhere without doing any harm at all)
  • Page Designers (Enthusiastic vikiers willing to decorate the pages of the channels)

What else is gone?
To be honest the actual new improvements are doing more harm than good to Viki. I have noticed that many of us are coming and going and some are never coming back again unfortunately. And that’s a pity.

I just hope you guys stay strong and united!
Fighting to everyone for what’s to come!

8 Likes

Personally, I have already made mistakes as a segmenter and only noticed them at the end. When that happens, I prefer to mention it in our team discussion with the CS, so the situation can be checked or fixed if needed.

I think human mistakes can happen to anyone, especially when there is a lot of work and several languages to take into account. And if the mistake is not noticed right away, that can happen too. There is nothing to be ashamed of. In my opinion, the important thing is to report it and fix it as soon as it is spotted.

However, since more and more channels are coming with many pre-subbed languages, I have been checking even more carefully than before, because a simple segmentation change can sometimes affect subtitles that were already there.

Something that could also help would be a feature visible directly in the segmentation editor, showing the completion percentage for each pre-subbed language. For example, if a language is at 99%, it would be easier to notice that a subtitle may have been forgotten or emptied after segmentation.

This would still require extra vigilance from us, especially on channels with several pre-subbed languages.
(Of course, I am mainly speaking from the little experience I have had with segmentation, as well as from the mistakes I have made myself, and there have been quite a few haha.)

2 Likes

I haven’t been segging for a while and I’m thinking of finding a project again soon to help out. But
 Are we segmenters supposed to change all the presubbed languages when we adjust a segment? Like when we split a segment in 2 are segmenters expected to change all presubbed languages accordingly? If so I think it’s best for me to not pick a new project. Viki already took away a lot of joy for me when they started the whole presubbing and now we segmenters are supposed to fix a lot of subs on top of that?

I understand it’s annoying and such that after some changes the subs are not correct or even missing but that’s a lot of work.

2 Likes

The percentage doesn’t make sense there because it doesn’t tell you how many subtitles might be missing. 99% could mean one or more. It’s calculated based on the total number of segments.

You’ll only notice missing subtitles in bulk if you compare the number of subtitles in the presub languages, and even that won’t tell you if there’s only half a subtitle in the segment because the second one from the segment you combined is missing. Only empty segments and those with subtitles are counted.

The CS has access to all languages, and the most reliable method is to look up the segmenters’ IDs in the English subtitles, then search for that segment in all languages and check if the subtitle is complete.
But even then, errors can occur if the segmenter realized something was wrong and switched it back to the previous version in bulk. Then the English subtitles will show “Viki” as the ID, and you won’t check that in the other presubs.

2 Likes

Yes, the Segger does the same thing with all the presub languages as with the English subtitles.

You should take a refresher course first. For this, contact Maria (@maria_lavendula_77 )

1 Like

Ok, then there is no more segmenting for me sadly
 to much work and that takes away all the fun for me.

1 Like

I see, it’s still pretty complex after all!

2 Likes

That can only be done after unlocking the editor, though


1 Like

That’s the CS’s job, not Segger’s! And the CS opens the episode after QC!

1 Like

I never said it was!!!

So that would mean that the checking method you mentioned can’t happen until after QC.

1 Like

Hi @dudie Dudie! Join one of my teams
 We’ve been assisting many seasoned segmenters with the new requirements. I will help you with anything you need a refresher on.

We’ve been testing a character counter in several shows. The formula bar is pasted into the upper 3 lines of the backup subtitle’s spreadsheet.
Once we get the bugs worked out, we will roll it out to every segmenting team that wants to use it. AND I will post the template in VCC.

How it is used: Place the first segment’s sub into the spreadsheet, and it wil fetch the second segment’s sub. Then it will give you the character count for all presubbed languages.

This tool, created by Trang, allows us to see ahead of time if a potential combo will be under the 100-character limit per segment BEFORE we waste time manually testing every language in bulk.

It has saved us a ton of time on these 13 to 17 language shows!

We’ve had issues with people in different regions being unable to use the formula when they copied the original template we made into their region’s spreadsheet, but ts_Lambrini found the answer for us! Who knew the formula would be different in various regions! I always thought math was math, but NOPE! Google spreadsheets have regional math!

Anyway
 Any CS who wants to help us test-drive and bug-check this character-counting template, please contact me. @porkypine

3 Likes

Yes, when else should it be done? Before I release the episode to the other teams, I check the presubs. And I do that after the QC.
If another CS wants to do it at a different time, the episode can be opened beforehand, that’s the CS’s decision.

1 Like

I wonder how beneficial it really is to point out to Viki the very things that could be used as yet another argument to reduce our presence. The trend already seems to be moving toward projects with less and less room for seggers, and perhaps even for English teams.
That’s why, in my opinion, it’s best not to publicly highlight anyone’s mistakes, especially at this time, or bring up topics and issues that, directly or indirectly, intentionally or not, may end up putting one specific role in the spotlight, whatever that role may be.
Not only because we all make mistakes regardless of our role (subbers, seggers, TEs, CEs, Mods, CMs, and CSs), but also because these are matters that call for support, training, and internal discussion, not necessarily public exposure. Dirty laundry should be washed at home, and I believe there are other spaces where certain issues should be addressed without further weakening the community’s position.
Right now, maybe we should focus on what this community does best: quality, collaboration, experience, attention to detail, and the ability to work together.
We can’t force Viki to do things the way we think they should be done. But we can show, intelligently and united, where we are still indispensable.
Maybe this is the time to listen more carefully to where things are heading and look for realistic solutions, rather than giving Viki more reasons to cut us out. In my opinion, the real question should be: how can we remain useful, credible, and necessary in this new context?

9 Likes

Another tool that I sometimes find useful is to set Activities so that it shows the only the segments that have been deleted. (This also shows the subtitles that have been ‘deleted’ – which means that the subs have been modified by someone and replaced the previous ones.)

To show deletions, the Activities window needs setting as shown on the image below. Clicking on an option will deselect (gray) that option. This information can also be filtered using the segmenter’s on-screen name (the filtering is case sensitive).

If a segger has ‘deleted’ a sub (and a segment at the same location), it means that it is most likely due to a new sub created by the segger when combining two subs into a single segment. If the segger has split a sub but not transferred the subtitle, this will show up as an empty segment (unless they have used some kind of character such as the ♫♫ for lyrics).

It can also be useful to review the ‘Create’ list as well and see which segments a segger has created.

8 Likes

Many thanks to all those who shared their tips and tricks so far!

It’s nice to see that Viki still has responsible and involved contributors. Despite the increasing number of pre-subbed languages, you are even more ambitious and smart enough to find solutions for easing your work.

This is actually what Viki is going to see from this topic: that there are still mature and trustworthy contributors who don’t run from the reality of this platform, but instead face everything and point out any problems that need to be addressed and corrected on time. They will see that we don’t pretend to be responsible contributors, but we actually are by finding solutions and sharing them with the entire contributor community to make all of us better. They are going to see a community that is not afraid to put everything about their work on the table without hiding what they don’t like or don’t consider beneficial for them, the community. This shows respect for both parties, especially in our situation where we contribute on their platform, so they are very aware of our work and can detect all the time when something is not done properly; and sometimes the viewers are the actual ones making them aware of some situations.

This is something I always appreciated about the Segging community, that even though it wasn’t mandatory, they still made it mandatory, and no one had an issue with this. Probably it would have been the same with subbing if people were driven more by quality, and less by hiding and defending weak contributors for whatever reasons or agenda they had. Or running or attacking whenever someone tried to actually change something. We learn our entire life, and the most healthy way to do it is by facing everything with courage and the mind that in each of our day life we still don’t learn everything.

Viki always had their plans despite what we wanted and believed, so there was never the right moment to talk about anything. But being responsible and addressing issues is not about a specific moment, but about being oriented toward responsibility and quality.

Thank you once again for sharing your solutions, and to all those still unsure about sharing them, just don’t be worried about anything. Share and let those in need decide what can be helpful for them. I’m sure that any little tip will be useful at some point.

6 Likes