Filters not working (when root folder contains accented characters ?) about shotcut HOT 5 CLOSED

I am not able to reproduce it using my desktop running LANG=en_US.UTF-8 by copying and pasting the text "Téléchargements" from this page to make a folder in my $HOME. I do not know why. Maybe if I create the directory by manually entering extended characters, or maybe I need to run a different locale.

Another developer (not a Shotcut developer, but a competent one with KDE background) reported the same problem, and he could not figure out either thinking it might be a Qt bug.

from shotcut.

I just made a test after learning how to input special accent characters from the keyboard, and that succeeded as well.

from shotcut.

Thanks Dan for your investigation of the problem.

This is strange... I've tried creating a "éé" folder right into my /home, copying Shotcut in it, and the filters don't show. Just renaming "éé" to "ee" makes shotcut work normaly again. My locale is fr_FR.UTF-8, so we're both in UTF8.

I've tried the windows version installed into an self created (non alias) accented folder (Win7) and the filters do show up, no problem.

It's probably unrelated, but I tried to render a video which source resources where into paths containing accents and spaces, and it failed with a short "INVALID" video (looking on the web showed me it was related to resource path, so i changed all the paths to simpler, non accented, no spaces, absolute paths in the mlt file and it worked all right).

Working on bug-fixing is not fun, and if you cannot reproduce it, very frustrating so I suggest I'll try to investigate further to try narrowing down the problem and will post my findings here in the next few weeks.

Regards,
Ed

from shotcut.

Hi again,

I've tried spaces in the path -> all is OK, so it's just about accented characters. BTW I hadn't noticed, but the timeline is affected too : neither the effects or the timeline do show up.
Upon launch, every effect loading, instead of showing :

[Debug  ] <void FilterController::loadFilterMetadata()> reading filter metadata "audio_balance" "meta.qml"
[Debug  ] <FiltersDock::FiltersDock(MetadataModel*, AttachedFiltersModel*, QWidget*)> begin
[Debug  ] <FiltersDock::FiltersDock(MetadataModel*, AttachedFiltersModel*, QWidget*)> end
[Debug  ] <void FilterController::loadFilterMetadata()> added filter "Balance"

Shows :

[Debug  ] <void FilterController::loadFilterMetadata()> reading filter metadata "audio_balance" "meta.qml"
[Warning] <QObject* QQmlComponentPrivate::beginCreate(QQmlContextData*)> QQmlComponent: Component is not ready
[Warning] <void FilterController::loadFilterMetadata()> "file:///home/edouard/Bureau/Shotécut/Shotcut.app/share/shotcut/qml/filters/audio_balance/meta.qml:1 module "QtQuick" is not installed
"

Plus, at the end, a bunch of lines like :

[Warning] <> file:///home/edouard/Bureau/Shotécut/Shotcut.app/share/shotcut/qml/timeline/timeline.qml:21:1: module "QtQuick.Controls" is not installed
     import QtQuick.Controls 1.0
     ^

about the 2 following files :

• /share/shotcut/qml/timeline/timeline.qml
• share/shotcut/qml/views/filter/filterview.qml
  and complaining about the fact that xxx is not installed, xxx being :
• QtQuick.Controls
• QtQuick
• QtGraphicalEffects
• QtQml.Models
• QtQuick.Layouts

Maybe, the reason why you don't see the problem on your computer is that QtQuick is in your path somehow, and the fact Shotcut cannot use the bundled one makes it use the default one in your path ?
Maybe you could try in a virtual machine with a "fresh" out of the box Ubuntu VM ?
Again, I'm not a developper but maybe the way you call QtQuick's path is not UTF8-safe ? Or it may be a bug with QtQuick itself, but a Google search did'nt return any clue about such a bug.

I've seen at the beggining of the launch log :

<Application::Application(int&, char**)> install dir = "/home/edouard/Bureau/Shotcut/Shotcut.app/bin"

Maybe if you use this variable to define QtQuick's path, the char type stores it in ASCII instead of UTF8 ?

Anyway, If you need me to try something don't hesitate to ask.

Regards,
Ed

from shotcut.

This was fixed in the launch script as of 15.05.

from shotcut.