I have this weird error or thing in my video editing.

BickerySebastian wrote on 4/17/2020, 7:15 PM

I'm not sure what to describe but I have this weird error and it's better to show you WHAT it is, rather describing it with words.

This didn't occur when I installed the program, but I didn't have this today. Does anyone have a solution to this? Does this happen because of some hardware setup?

Comments

vkmast wrote on 4/18/2020, 12:48 AM

Some of the users have been able to solve the issues of this kind trying the suggestions in links like mentioned here. (See e.g. the following comment there.) It's also possible that you may need to change display settings

 

BickerySebastian wrote on 4/18/2020, 12:33 PM

Some of the users have been able to solve the issues of this kind trying the suggestions in links like mentioned here. (See e.g. the following comment there.) It's also possible that you may need to change display settings

 

I tried them, and it didn't work.
Changing the "SSERIFE.FON" to "SSERIFER.FON?" It doesn't work.
Changing the Windows Layout to the default layout? DOESN'T work.
And my display is 1980 x 1080, my system is Windows 10, and the version I'm using is the Movie Studio 15.0, Build 146.

vkmast wrote on 4/18/2020, 12:48 PM

Changing the "fon" was only one of the suggestions in the links referred to. There were several. But I guess you need to Ask Support then. Click "Support New" at the top of this page. Then use this advice.

BickerySebastian wrote on 4/18/2020, 1:51 PM

Changing the "fon" was only one of the suggestions in the links referred to. There were several. But I guess you need to Ask Support then. Click "Support New" at the top of this page. Then use this advice.

GUESS WHAT.
I FIXED IT but it's not by your instructions.
It's because of MY LOCALE, which is Japanese (Because certain Japanese games don't work if your system's locale isn't Japanese. Don't ask.), and the beta option to support multiple Unicode languages, so I switched it to American English and unchecked the beta option, and now it works.

vkmast wrote on 4/18/2020, 2:29 PM

Great. Thanks for coming back and telling us the solution that worked for you. I had no idea your "locale" was Japanese.

FayFen wrote on 6/22/2020, 7:16 AM

You just helped me also solve this issue on my VMS16 on W10.

The solution is just unticking the beta option to support multiple Unicode languages, the locale can stay as needed.

**This also helped me on my other NLE that now support Hebrew and not gibberish...

I guess MS beta isn't working.