Pocket Monsters: Best Wishes - 84

uSalt2

New Member
For some reason, my external harddrive keeps randomly corrupting random files, killing about 16mb of the file each time. This is the second time it's happened, and I'm not sure what's the cause.
Hope you don't have anything important there...
 

uSalt2

New Member
Also, if you plan to release a V2, you might also want to make changes to the typesetting. It's typeset to the BT.709 colorspace, but since VSFilter outputs subtitles in BT.601 only, you get this.

Hint: Go to [URL]http://plorkyeran.com/aegisub/[/url] and download the latest build. Then on the menu bar, go to View > Options > Advanced > Video > Force BT.601.
In addition, the trunk builds will also add "YCbCr Matrix: TV.601" to the ass file, allowing subtitle renderers that support both BT.601 and BT.709 (like xy-VSFilter) to determine which one to output, maintaining compatibility.

Also, I'd recommend creating vector drawings to mask stuff instead of typing "BLAHBLAHBLAH" and using {\clip}, so that way, you can use {\blur} to soften the edges of the mask and make it look more like it's part of the show, kinda like this.
 

uSalt2

New Member
I'm not sure what's been causing it. It's entirely all fansub stuff, though. It's a pretty new external harddrive too :(
Hopefully nothing important to DATS...
Also, I'd ask more info about your drive, but I know nothing about hard drives. :p
Anyway, to bring this back on topic, what's the status of BW85-86?
 

Skr

Ishvalastrator
Staff member
Also, if you plan to release a V2, you might also want to make changes to the typesetting. It's typeset to the BT.709 colorspace, but since VSFilter outputs subtitles in BT.601 only, you get this.

Hint: Go to http://plorkyeran.com/aegisub/ and download the latest build. Then on the menu bar, go to View > Options > Advanced > Video > Force BT.601.
In addition, the trunk builds will also add "YCbCr Matrix: TV.601" to the ass file, allowing subtitle renderers that support both BT.601 and BT.709 (like xy-VSFilter) to determine which one to output, maintaining compatibility.

Also, I'd recommend creating vector drawings to mask stuff instead of typing "BLAHBLAHBLAH" and using {\clip}, so that way, you can use {\blur} to soften the edges of the mask and make it look more like it's part of the show, kinda like this.
Well, thank you.

I never really thought about using the vector tools for some reason, but totally makes sense ;D
 

Skr

Ishvalastrator
Staff member
Hopefully nothing important to DATS...
Also, I'd ask more info about your drive, but I know nothing about hard drives. :p
Anyway, to bring this back on topic, what's the status of BW85-86?
85 is basically done. I was thinking about splitting the episode, but decided against it.

86 is still a work in progress D: Trying to work as quickly as I can since BW2 01 is now out. Will get to work on that shortly too.
 

uSalt2

New Member
85 is basically done. I was thinking about splitting the episode, but decided against it.

86 is still a work in progress D: Trying to work as quickly as I can since BW2 01 is now out. Will get to work on that shortly too.
Okay. :D Thanks!
 

Skr

Ishvalastrator
Staff member
Also, if you plan to release a V2, you might also want to make changes to the typesetting. It's typeset to the BT.709 colorspace, but since VSFilter outputs subtitles in BT.601 only, you get this.

Hint: Go to http://plorkyeran.com/aegisub/ and download the latest build. Then on the menu bar, go to View > Options > Advanced > Video > Force BT.601.
In addition, the trunk builds will also add "YCbCr Matrix: TV.601" to the ass file, allowing subtitle renderers that support both BT.601 and BT.709 (like xy-VSFilter) to determine which one to output, maintaining compatibility.
So I asked someone else about this, and was told that it would probably be easier to just use an avs in aegisub with converttorgb(matrix="Rec601"). Would this suffice too? Since VSFilter only outputs to 601, what's the point in doing a 709 colorspace?
 

uSalt2

New Member
So I asked someone else about this, and was told that it would probably be easier to just use an avs in aegisub with converttorgb(matrix="Rec601"). Would this suffice too? Since VSFilter only outputs to 601, what's the point in doing a 709 colorspace?
There really isn't a point of doing it in BT.709. In fact, there isn't a difference. It's really just VSFilter's fault. xy-VSFilter can output in BT.709, but not everyone uses that fork, so doing it in BT.601 is more for compatibility.

Also, why not use 3.0.0 (trunk builds)? Aegisub 3.0.0 removes the need to commit changes, making it much more convenient (except if you make a typo and type {\blur2000}). Plus, Aegisub 3.0.0 is necessary for scripts like Aegisub-Motion, which imports tracking data from programs like Mocha to do frame-by-frame movement and sizing. But loading an avs script that converts the colorspace works too; I'm just too lazy to do that / need the newer features.
 

Skr

Ishvalastrator
Staff member
There really isn't a point of doing it in BT.709. In fact, there isn't a difference. It's really just VSFilter's fault. xy-VSFilter can output in BT.709, but not everyone uses that fork, so doing it in BT.601 is more for compatibility.

Also, why not use 3.0.0 (trunk builds)? Aegisub 3.0.0 removes the need to commit changes, making it much more convenient (except if you make a typo and type {\blur2000}). Plus, Aegisub 3.0.0 is necessary for scripts like Aegisub-Motion, which imports tracking data from programs like Mocha to do frame-by-frame movement and sizing. But loading an avs script that converts the colorspace works too; I'm just too lazy to do that / need the newer features.

I'm surprised someone that knows about this is in the Pokemon community... Thanks for your input.
I'll try out Aegis 3.0.0 and fix the typesetting for 85-86 :D
 

uSalt2

New Member
I'm surprised someone that knows about this is in the Pokemon community... Thanks for your input.
I'll try out Aegis 3.0.0 and fix the typesetting for 85-86 :D
You're welcome. Just ensure you watch what you typing, or else you'll end up crashing Aegisub 3 by accidently typing {\blur9001}, {\fax9001}, {\fay9001} or something. Newer builds have mechanisms to prevent crashing (probably by removing the {\blur} override tag, but it can still crash (such as when you realize you made the mistake and try backspacing from 9001 to 900). Fortunately, it saves your work to a temp directory and tells you where it is if you accidentally crash it.

EDIT: I accidentally typed {\fsp600}. NOT a good idea. (my whole computer lagged.)
 
Top