StaxRip 2.0 Support Thread

[jonrodrigos]

@jonrodrigos

Maybe it's because you don't have a custom path to the included portable python.


would it be this? if everything is already pointing to the internal portable
and I had uninstalled the installs
I also did it on a clean windows installation, pointing only to the portable
https://i.postimg.cc/VdwNdKmC/2020-05-15-4.png (https://postimg.cc/VdwNdKmC)

[VirulentPip]

For a while now I've been using Turing Nvenc my encodes (1080p) I have just got a Ryzen 3900x and was wondering if there's any settings out there I can use that would get me the same quality output but for potentially less bitrate/file sizes?

This is what I use for 1080p Blurays

--vbrhq 4400 --codec h265 --preset quality --profile main10 --level 5.1 --output-depth 10 --max-bitrate 4400 --aq --aq-temporal --bref-mode each --bframes 5 --ref 15 --gop-len 240 --lookahead 32 --output-buf 32 --vpp-unsharp radius=2,weight=0.65,threshold=20 --vpp-edgelevel strength=6.0,threshold=16.0,black=0,white=0

And this for older Blurays with a lot of noise

--vbrhq 4400 --codec h265 --preset quality --profile main10 --level 5.1 --output-depth 10 --max-bitrate 4400 --aq --aq-temporal --bref-mode each --bframes 5 --ref 15 --gop-len 240 --lookahead 32 --output-buf 32 --vpp-knn --vpp-unsharp radius=2,weight=0.65,threshold=20 --vpp-edgelevel strength=6.0,threshold=16.0,black=0,white=0

Should I change over to x265 or continue with Nvenc and is there anything I should change?

If anyone could point me in the right direction that would be great :)

[colinhunt]

Could someone provide me with some pointers on how to enable FFV1 version 3 encoding (-c:v ffv1 -level 3) in Staxrip, using ffmpeg of course? I can't figure out how to add it to encoding options. Using beta 2.1.1.1, btw. Thanks.

[Patman]

updated some tools for staxrip...

[Patman]

Could someone provide me with some pointers on how to enable FFV1 version 3 encoding (-c:v ffv1 -level 3) in Staxrip, using ffmpeg of course? I can't figure out how to add it to encoding options. Using beta 2.1.1.1, btw. Thanks.

Currently this is only possible with the command line.

[colinhunt]

Currently this is only possible with the command line.
Okay, thanks. No wonder I couldn't figure it out :)

[almanteka]

updated some tools for staxrip...

whats the difference between an msvc version and gcc? method of compiling? same results? thanks!

[Arkana]

staxrip recognized the location? go to apps > manage > on the left list avisynth > KNLMeansCL > status OK? the same for vapoursynth: apps > manage > on the left list vapoursynth> KNLMeansCL > status OK? if not, then go to path > browse and locate the file manually for avisynth and vapoursynth
StaxRip folder\Apps\Plugins\Dual\KNLMeansCL\KNLMeansCL.dll

both status are OK

[stax76]

@Arkana

Which GPU is in use?

[colinhunt]

Staxrip 2.1.1.1 beta stops processing on an error before writing a single frame when trying to output ProRes. Same job works fine in 2.0.8.0 Stable (edit: after it prompted to install Avisynth). I'll add what little information I can gather of the crash shortly.

Job: deinterlacing and IVTC'ing a music video.
TFM()
TDecimate(cycle=25,cycleR=5)
DeBlock QED (defaults)
VagueDeNoiser (defaults)

Output to ProRes normal profile.

update: Figured out why 2.1.1.1 beta throws in the towel. Avisynth+ was not installed. Odd though, I have done perhaps two dozen jobs on 2.1.1.1 and it never complained about Avisynth missing. I ran 2.0.8.0 the first time on this PC today; it told me to install Avisynth, and once I did that, 2.1.1.1 began outputting ProRes as well.

(Sidetrack: Could someone shed some light on why the CPU load remains at 4% for the job mentioned above? I get 10fps out of StaxRip with that 4%. Would be awesome to get the job done faster; where's the bottleneck?)

[Patman]

whats the difference between an msvc version and gcc? method of compiling? same results? thanks!MSVC (Microsoft Visual C) and GCC (GNU Compiler Collection) are different compilers. You are right with the statement that the methods of compiling are different. As a result, there are performance differences in the builds.

[stax76]

@colinhunt

2.1.1.3 is portable, I've not installed avisynth or fftw, tried all your configuration and it worked fine.

[Khun_Doug]

Staxrip 2.1.1.1 beta stops processing on an error before writing a single frame when trying to output ProRes. Same job works fine in 2.0.8.0 Stable (edit: after it prompted to install Avisynth). I'll add what little information I can gather of the crash shortly.

(Sidetrack: Could someone shed some light on why the CPU load remains at 4% for the job mentioned above? I get 10fps out of StaxRip with that 4%. Would be awesome to get the job done faster; where's the bottleneck?)

A lot of AVISynth filters perform really well when using PreFetch. Look through the menus and for the MT Mode stuff and you should find the option to set the number of threads (that's the prefetch). If you have 8 threads on your CPU, try setting PreFetch to 4, or 6, or even 8. You can really get a remarkable speed bump this way.

One note: I have an AMD 3950X with 16 cores / 32 threads. I found the sweet spot to be between 12 and 16 threads when using X265. Just because you have a lot of threads does not mean you will get a speed bump beyond a certain point.

[Atak_Snajpera]

If you have 8 threads on your CPU, try setting PreFetch to 4, or 6, or even 8. You can really get a remarkable speed bump this way.
The rule is simple. Always use value equal to number of physical cores not virtual ones. With higher value than number of cores you will notice choking effect. (cpu usage drops constantly)

[jlw_4049]

@stax76 is there anyway to setup the program to where the video bitrate is tied to (x264/x265) preset instead of the template? Similar to how the CRF value is tied to it?

[stax76]

@stax76 is there anyway to setup the program to where the video bitrate is tied to (x264/x265) preset instead of the template? Similar to how the CRF value is tied to it?

In the x265 dialog the Custom tab can be used for this, custom switches override GUI switches.

[jlw_4049]

In the x265 dialog the Custom tab can be used for this, custom switches override GUI switches.

Thank you for this information! :)

@stax76 - I know you are busy with tons of stuff. IDK if you would want to do this, but could you add a way to setup more then just 2 audio tracks. For those rare films/etc where there is 3 or 4 of them?

Also is there anyway you could add a DTS down mix to core option for the audio section? You can do this with ffmpeg via a command like this "-c:v copy -bsf:a dca_core -c:a copy" and I know there is a way to do it with mkv.

Thanks!

[stax76]

@stax76 - I know you are busy with tons of stuff. IDK if you would want to do this, but could you add a way to setup more then just 2 audio tracks. For those rare films/etc where there is 3 or 4 of them?

If you are not batch processing you can add more audio tracks in the Container Options, it has an audio Tab.

Also is there anyway you could add a DTS down mix to core option for the audio section? You can do this with ffmpeg via a command like this "-c:v copy -bsf:a dca_core -c:a copy" and I know there is a way to do it with mkv.

For that I would need more info, ideally on the issue tracker, mediainfo for the input file, command line and mediainfo for the output file.

[jlw_4049]

If you are not batch processing you can add more audio tracks in the Container Options, it has an audio Tab.



For that I would need more info, ideally on the issue tracker, mediainfo for the input file, command line and mediainfo for the output file.


Added to tracker as requested with everything you said you would need.

https://github.com/staxrip/staxrip/issues/198

I have found a potential work around that seems to work fine. It's updated in the comment section of the tracker.

[44vince44]

I saw the workaround, well, if it's working, then this is a real solution, not just a "workaround" (and congrats for that).
You seem to have created a profile with it, so it should be very handy, isn't it ?

[jlw_4049]

I saw the workaround, well, if it's working, then this is a real solution, not just a "workaround" (and congrats for that).
You seem to have created a profile with it, so it should be very handy, isn't it ?

Yes it works perfectly so far. However, it would be nice to have it implemented into the GUI.

and thanks! :)

[Atlantis]

This DTS-HDMA / DTS-HD to DTS core was something I mentioned some pages ago. I suggested if it is possible the best place is when the demux window opens.

So the term reduce is not correct, extract is better. MakeMKV or MeGUI can do this. At the very beginning, instead of demuxing DTS-HDMA, would be great to demux only the DTS core.

You do it with eac3to and the option -core.

[jlw_4049]

This DTS-HDMA / DTS-HD to DTS core was something I mentioned some pages ago. I suggested if it is possible the best place is when the demux window opens.

So the term reduce is not correct, extract is better. MakeMKV or MeGUI can do this. At the very beginning, instead of demuxing DTS-HDMA, would be great to demux only the DTS core.

You do it with eac3to and the option -core.

I knew there was a way to do it with eac3to. I generally try to stay away from using eac3to where I can, since it hasn't had support in many years. I do most of the work that I can with mkvmerge/ffmpeg.

With that said I would like this feature. My work around that I posted earlier does work though.

[44vince44]

@jlw_4049 this is a great find. The logic of the UI makes it difficult to to create an option to check/uncheck such option in the "Audio Settings" (the standard audio settings window related to an encoder) because as you can see, this "Audio Settings" is for decode>encode operations, where a decoding operation has to take place. So there is no way that the DTS Core extraction option could fit in that window since when extracting DTS core, there is no decoding taking place.
I guess what you found here is the only way it can work.
Maybe @Stax76 can integrate that profile you created in the default profiles, since this operation is very much used !

I have a question: I was wondering why you put wav as file type, shouldn,t it be dts? or it simply doesn't matter because it doesn't affect the script in any way.

[44vince44]

And you shouldn't say "workaround" ;-)))) because it is not a workaround, it is a REAL solution, created with the regular options in Staxrip. Staxrip is designed to be customizable, so what you did is simply add a new feature.

Please @Stax76 if you are reading this, consider updating the default audio profiles with that new one!! Thanks for both of you!

[jlw_4049]

@jlw_4049 this is a great find. The logic of the UI makes it difficult to to create an option to check/uncheck such option in the "Audio Settings" (the standard audio settings window related to an encoder) because as you can see, this "Audio Settings" is for decode>encode operations, where a decoding operation has to take place. So there is no way that the DTS Core extraction option could fit in that window since when extracting DTS core, there is no decoding taking place.
I guess what you found here is the only way it can work.
Maybe @Stax76 can integrate that profile you created in the default profiles, since this operation is very much used !

I have a question: I was wondering why you put wav as file type, shouldn,t it be dts? or it simply doesn't matter because it doesn't affect the script in any way.

If you don't put wav the audio "encode" actually will error out. I'll explain further.

Decoding (extracting the core is technically the proper term for this) a dtshd file to a .wav file is correct. As far as I know that's how ffmpeg and mkvmerge does it, they just do it without a two step process, it does the same thing with 1 command. You just never actually see the .wav file being extracted.

(Someone can correct me if I'm wrong)

If you use some older programs to manually do it, it goes to a .wav first then back to the dts core. Maybe if stax76 implements this it'll work in one step.

He can add it in the audio options correctly and he will be able to add it in the demux window when you do a manual work flow. An option like reduce to core similiar to mkvtoolnix would work great. (The audio profile could work both with ffmpeg and eac3to, the later isn't updated ever so i never use it, the demux section could use mkvmerge) it could even be done in the final muxing stage with mkvmerge

Until then my custom profile works perfectly

Stax76 is pretty good at keeping up with this and responding. I wish I knew how to do more then write scripts.

I'm glad it worked out for you Vince!

Sent from my Pixel 3a using Tapatalk

[44vince44]

@jlw_4049, I am doing tests to confirm several things, trying to tweak, and this whole work revealed missing features in the command line edit window:
Working of course on the ffmpeg solution

1) .dts is a known and valid extension for dts streams that are unpadded, and it should be used here (wav has no meaning unless you are preparing your stream to be burned on an audio DTS CD)
unpadded streams (dts, ac3 etc) are the proper streams used by ffmpeg and all encoders/decoders/muxers. Wav has nothing to do here, except if you intend to burn a cd.

TEST CONFIRMATION : Successful, so you should put dts instead of wav (it didn't crash nor fail)

2) In the command line, you must not have this: -disposition:a default -metadata:s:a language=eng
those have no effect at this stage. you can select the language in the drop down box "language".
currently you can set language with this drop-down, but you can't select if default of forced track. And this is the missing feature (you can try it, use -metadata:s:a language=fre or ara of whatever, you'll see the resulting file will not carry this info. Also -disposition:a default will have no effect, you won't have the default status, check it with mediainfo).

This is the output-file mediainfo audio section:
Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.82 MiB (62%)
Language : English
Default : No
Forced : No


and this is the original before processing

ID : 2
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Variable
Channel(s) : 6 channels
Channel(s)_Original : 8 channels
ChannelLayout_Original : C L R LFE Lsr Rsr Lss Rss
Sampling rate : 96.0 kHz
Frame rate : 187.500 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Language : English
Default : Yes
Forced : No
Duration_Source : General_Duration

3) The way you've done it and I've re-done it is already a one step, I don't undertsand what we need more, except that it is should be a default profile, and that the missing features are added for the command line window: missing features are : default and forced statuses.

[jlw_4049]

@jlw_4049, I am doing tests to confirm several things, trying to tweak, and this whole work revealed missing features in the command line edit window:
Working of course on the ffmpeg solution

1) .dts is a known and valid extension for dts streams that are unpadded, and it should be used here (wav has no meaning unless you are preparing your stream to be burned on an audio DTS CD)
unpadded streams (dts, ac3 etc) are the proper streams used by ffmpeg and all encoders/decoders/muxers. Wav has nothing to do here, except if you intend to burn a cd.

TEST CONFIRMATION : Successful, so you should put dts instead of wav (it didn't crash nor fail)

2) In the command line, you must not have this: -disposition:a default -metadata:s:a language=eng
those have no effect at this stage. you can select the language in the drop down box "language".
currently you can set language with this drop-down, but you can't select if default of forced track. And this is the missing feature (you can try it, use -metadata:s:a language=fre or ara of whatever, you'll see the resulting file will not carry this info. Also -disposition:a default will have no effect, you won't have the default status, check it with mediainfo).

This is the output-file mediainfo audio section:
Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.82 MiB (62%)
Language : English
Default : No
Forced : No


and this is the original before processing

ID : 2
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Variable
Channel(s) : 6 channels
Channel(s)_Original : 8 channels
ChannelLayout_Original : C L R LFE Lsr Rsr Lss Rss
Sampling rate : 96.0 kHz
Frame rate : 187.500 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Language : English
Default : Yes
Forced : No
Duration_Source : General_Duration

3) The way you've done it and I've re-done it is already a one step, I don't undertsand what we need more, except that it is should be a default profile, and that the missing features are added for the command line window: missing features are : default and forced statuses.I'll do some more testing when I get back to my computer in a little bit.

However in the meantime try disposition:a:0 default
And
-metadata:s:a:0 language=eng
And tell me if that works.

Sent from my Pixel 3a using Tapatalk

[44vince44]

I just tried it, it is in my previous post, see by yourself


Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.82 MiB (62%)
Language : English
Default : No
Forced : No

So "disposition:a:0 default " doesn't work as you can see above, and there is no way it can work at this stage because this is metadata for the container. Here we are at a stream level.
and neither -metadata:s:a:0 language=eng will work for the same reason! Language is passed through to muxer from the value you've selected in the Language box.

I made a new bug report so that we can have default and Forced flags selection checkboxes, as it is in all other audio edit settings.

[jlw_4049]

I just tried it, it is in my previous post, see by yourself


Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 49 s 56 ms
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 8.82 MiB (62%)
Language : English
Default : No
Forced : No

So "disposition:a:0 default " doesn't work as you can see above, and there is no way it can work at this stage because this is metadata for the container. Here we are at a stream level.
and neither -metadata:s:a:0 language=eng will work for the same reason! Language is passed through to muxer from the value you've selected in the Language box.

I made a new bug report so that we can have default and Forced flags selection checkboxes, as it is in all other audio edit settings.That makes perfect sense. I didn't think about it that way.

Grab latest BETA here
https://staxrip.readthedocs.io/introduction.html#beta

Sent from my Pixel 3a using Tapatalk

[stax76]

There is a new beta that addresses some issues (announced in the other staxrip thread (https://forum.doom9.org/showthread.php?t=172068&page=171)).

[jlw_4049]

There is a new beta that addresses some issues (announced in the other staxrip thread (https://forum.doom9.org/showthread.php?t=172068&page=171)).

wooow! I didn't know there was another staxrip thread haha. So should we take all discussions about staxrip over there then?

[stax76]

Problem with this thread is, first post don't point to https://github.com/staxrip/staxrip

[colinhunt]

@colinhunt

2.1.1.3 is portable, I've not installed avisynth or fftw, tried all your configuration and it worked fine.
Okay. Well, here Prores export worked only after I installed Avisynth. I dunno what else to tell you. But it works now, so all's well that ends well, yeah?

[jlw_4049]

Problem with this thread is, first post don't point to https://github.com/staxrip/staxripI will take my discussion over there from now on. Thanks sir!



Sent from my Pixel 3a using Tapatalk

[colinhunt]

A lot of AVISynth filters perform really well when using PreFetch. Look through the menus and for the MT Mode stuff and you should find the option to set the number of threads (that's the prefetch). If you have 8 threads on your CPU, try setting PreFetch to 4, or 6, or even 8. You can really get a remarkable speed bump this way.

One note: I have an AMD 3950X with 16 cores / 32 threads. I found the sweet spot to be between 12 and 16 threads when using X265. Just because you have a lot of threads does not mean you will get a speed bump beyond a certain point.
Thanks, I'll look into PreFetch/MT stuff!

[44vince44]

@Patman, I see you have now separate builds for AVX and AVX2. Didn't the "regular" builds check for available instruction sets on your hardware and use them ?

[44vince44]

and btw @Patman, I saw also you have compiled ffmpeg with gcc10, that must have been quite some work !!! Thanks !!!

[44vince44]

wooow! I didn't know there was another staxrip thread haha. So should we take all discussions about staxrip over there then?

Well it's better to discuss things here, and report bugs there...

[jlw_4049]

I will take my discussion over there from now on. Thanks sir!



Sent from my Pixel 3a using TapatalkI mean this thread is Ravens and the other is the official staxrip thread.

But yes I know what you mean

Sent from my Pixel 3a using Tapatalk

[Patman]

@Patman, I see you have now separate builds for AVX and AVX2. Didn't the "regular" builds check for available instruction sets on your hardware and use them ?

Hi vince,

the regular builds check for available instructions and use them. It was a request ;)

[Arkana]

@Arkana

Which GPU is in use?

I'm using Windows server. Seems like no dedicated GPU at all

[44vince44]

Hi vince,

the regular builds check for available instructions and use them. It was a request ;)
Thanks Patman, so please confirm, if my processor is AVX2, If I use the regular M build GCC11, and the "AVX2" M build GCC11, the performance and result is the same ? Please confirm !
And again thanks for everything.:thanks:

(BTW I'm new here, but the same Vince at github)

[JKyle]

@Patman

It seems like your build of FFmpeg, ffmpeg-N-97806-g883c48190f-g1ead7ed5bf-gcc10.1.7z has a problem with a text file input that's encoded in UTF-8, CR/LF(Windows).

In order to concatenate two wmv files into one mkv, I made the following txt file named mylist.txt (UTF-8, CR/LF):

file 'test 1.wmv'
file 'test 2.wmv'



Then I ran the following command to join those two wmv files:
(Windows 10 x64 2004)

ffmpeg -hide_banner -f concat -safe 0 -i mylist.txt -c copy -y 'test.mkv'

But your FFmpeg binary yields this error message:

[concat @ 00000147d0463300] Impossible to open 'mtest 1.wmv'
mylist.txt: No such file or directory

On the other hand, Zeranoe's build (4.2.2 static) runs OK.

I can't figure out why there's an unnecessary letter m in the filename in the error message.
My guess is that maybe it's related to the text encoding method your ffmpeg binary employs when it takes the text input file.

Any idea?

[stax76]

@Patman

JKyle uses CP 949 if I remember right.


I'm using Windows server. Seems like no dedicated GPU at all.

KNLMeansCL uses OpenCL which your system probably don't support due to lack of GPU driver.

[Arkana]

@Patman

JKyle uses CP 949 if I remember right.




KNLMeansCL uses OpenCL which your system probably don't support due to lack of GPU driver.

any suggestion for denoise filter on windows server?

[SaboraPie]

Hi!! a bug opening in Video Comparison:


---------------------------- System Environment ----------------------------

StaxRip : 2.1.1.4
Windows : Windows 10 Pro 1809
Language : Spanish (Spain, International Sort)
CPU : Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz
GPU : NVIDIA GeForce GTX 670
Resolution : 1920 x 1200
DPI : 96

-------------------------------- Exception --------------------------------

System.OverflowException: La operación aritmética ha provocado un desbordamiento.
en StaxRip.VideoComparisonForm.VideoTab.Draw() en D:\Projekte\VB\staxrip\Forms\VideoComparisonForm.vb:línea 342
en StaxRip.VideoComparisonForm.VideoTab.OnPaint(PaintEventArgs e) en D:\Projekte\VB\staxrip\Forms\VideoComparisonForm.vb:línea 409
en System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
en System.Windows.Forms.Control.WmPaint(Message& m)
en System.Windows.Forms.Control.WndProc(Message& m)
en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[44vince44]

any suggestion for denoise filter on windows server?

did you try DFTTEST it's one of the most popular denoisers.

[Khun_Doug]

any suggestion for denoise filter on windows server?

It depends on the type of noise you want to remove. Is this an SD or HD source? Old movie that has been digitized? B&W or color?

Take a look at SMDegrain and mClean.

[JKyle]

@Patman

JKyle uses CP 949 if I remember right.

Thanks for remembering, but after talking with you about mpv/mpv.net failing to read a non-single-byte language named avs file on a non-UTF8 codepage system, I changed the codepage to UTF8 (https://forum.doom9.org/showpost.php?p=1903673&postcount=1496).


PS D:\Work\temp\test> Get-Culture; Get-UICulture; Get-WinSystemLocale; Get-WinDefaultInputMethodOverride; [Text.Encoding]::Default | select EncodingName,CodePage

LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)
1033 en-US English (United States)
1042 ko-KR Korean (Korea)

InputMethodTip : 0412:{A028AE76-01B1-46C2-99C4-ACD9858AE02F}{B5FE1F02-D5F2-4445-9C03-C568F23C99A1}
Description : Korean (Korea) - Microsoft IME


EncodingName : Unicode (UTF-8)
CodePage : 65001

:)