Hello Everyone!
As you all remember when our beloved Beverley /@bjhonsonwong was around she noticed that things were changing so she put together an amazing team of skilled sensei, and started working. Beverley, @Mazza , @manganese and @porkypine did an amazing job and now it’s finally here. Even if Beverley isn’t with us any more I’m sure she would be as happy as I am that the guide is updated. I want to thank everyone that was involved in creating the new guide, you are all amazing.
https://nssaofficial.â– â– â– â– â– â– â– â– â– â– â– â– /p/segging-guide.html
Congrats to everyone!
Another proof of what the contributors can do to improve their work and the final product for the viewers. I hope Viki is still around to appreciate this and reward the contributor community with more involvement.
That must have been a lot of work, but it’ll be a great help for new (and old) segmenters
.
Personally I find the Replay method a a bit questionable. Why? Because I’ve noticed several times that the cursor (the green line) sometimes doesn’t stop right at the edge of the segment line (the yellow line). It goes up to 0.1 seconds over it! And you can only see this if you click away to another segment so the segment guides don’t block your view. And this happens even if you replay it several times, and sometimes the cursor stops at different places too
.
Oh, it can sometimes go up to a whole lot further than that! ![]()
It generally works if you replay it 3 times and otherwise, you can notice in the next segment that something is wrong. But you are right: we have always had this bug.
I don’t use the replay method but I think it’s a good method just like the other ones. As seggers we tend to find the ways that works best for us because let’s be honest we all work slightly different than eachother.
I use the Replay Method regularly and I find it valuable. I have a feeling that in past versions of the segmenting software, the Replay Method wasn’t as reliable as it is today.
I’ve just tested it on around 20 random segments. In every case, when I let playback of the previous segment stop, and I click on a remote segment to deselect the segment being used with the Replay Method, the cursor was stopped at one of the two positions shown by Images 1 and 2. Both of these positions are described in the revised Segmenting Guide as “0.1s late” positions. In other words, if the first-hint of voice is consistently being heard with the Replay Method, then the segment that is being tested is definitely 0.1 late.

Image 1: The previous segment was used to test segment 3:39. After the replay of the previous segment stops and the location of the playback (as shown by the green cursor) is checked, there is a slight hint of the segment’s orange edge on the left-hand side of the cursor. Chief Segmenter @bjohnsonwong always treated this as 0.1s late.

Image 2: The previous segment was used to test segment 3:04. After the replay of the previous segment stops and the location of playback is checked, the segment’s orange edge is fully covered by the cursor. This is 0.1s late.
Sometimes, though, Image 1 can potentially be a well-timed segment if it meets all three criteria that the Segmenter’s Guide calls The Rule of Three. In these special “Image 1” cases, the first hint of voice is not heard when the Replay Method is used. Occasionally, though, if the left edge of the segment being tested is cut very close to the first hint of voice (within approximately 0.05s or less), it’s possible that sometimes the first hint of voice is heard and then, when it’s replayed again, the first hint of voice is not heard. This is because the segment is right on the border of being well-timed and 0.1s late. Since the segment’s edge can only be adjusted in 0.1s jumps, it is not possible to exactly fix the timing of a segment that is around 0.05s late. In these cases, it is better to treat the segment as 0.1 late.
Where I find the Replay Method limited is working out whether or not I’m hearing the first hint of voice (FHOV) or something else. When I’m looking for the FHOV, I always play the first two or three syllables of dialogue so that I have it clear in my mind what sound I am aiming for when hunting for it. This is not so easily accomplished when using the Replay Method by itself. I use the Replay Method when I am not certain that a segment is well timed and I have already timed it using the FHOV approach (so I know what sound I’m homing in on).
The new guide doesn’t seem to be explaining how to handle multisubs. Shouldn’t that be a core feature in modern-day segmenting? ![]()
The new guide doesn’t seem to be explaining how to handle multisubs. Shouldn’t that be a core feature in modern-day segmenting?
I agree. This is an area in which the document is lacking.
At the time the document was being assembled, Viki’s position in relation to multi-subs as well as Viki’s position on unsegmented shows were in a state of change. It is now clear that all shows arrive on Viki pre-segmented. This is why there is more detailed information on A&C in the 2026 guide. As soon as it becomes clear what Viki is doing in relation to multi-subs, and what the company expects from its volunteers in this area, such a section definitely needs to be included in the revised guide. This will be easily done. In the meantime, if you (or segmenters who read this) have any thoughts on what to include in such a section, please list those thoughts in this conversation for future reference.
One of my sensei once told me to replay it up to 4-5 times to be extra sure and I did notice the cursor usually tends to stop at the right place by then… but not always
.
Do you mean 0.1 late?
I admit these segments were the ones I struggled the longest with to learn and understand if they’re either late or early.
I do indeed! Thank you for spotting the mistake! It was 2:00 a.m. when I wrote that last night and I guess my brain wasn’t as accurate as I thought it was! I appreciate your letting me know
(I’ve made the correction now.)
No problem
. I liked your explanation and I think I might use the replay method in the future to get these kind of segments well-timed.

Thank you guys!
I always wondered why I felt the segment was right the first time, then wrong, corrected it, to find it was wrong again a few minutes later when I checked again after a break, lol! ![]()
Now I know…
![]()
As a newbie (at least for many of us) we tend to second guess ourselves and correct good segments or get stuck on segments for I dont know. Thankfully everyone gets better and more relaxed and in the end doesn’t correct “until the cows come home”. ![]()
Sure.
Hahaha, “until the cows come home”!
![]()
You make me laugh so much! ![]()
I need to use this one again & again!
I think this was also my problem in the Sandbox, where the sensei always saw something else than I did and told me to read the segmenting guide over and over again, which at that point taught me nothing I didn’t know yet and only got me more confused about all the secrets those insiders seemed to know and I didn’t.
Ah, I see.
Well, I got lucky to have very patient and supportive senseis, because between the language misunderstanding first (on my side), the lack of confidence as well as a very old computer plus a bad connection, I never thought I could even finish my trainings, not to mention passing graduation, lol. ![]()
And look at you now! ![]()
Hehehe.
Thank you.
I could not have imagined to be part of a real team one day!
But I’ve had the chance to meet amazing CSs.
I’m really grateful. ![]()