[Bug 46055] FL Studio 20: Built-in file browser incorrectly shows image files alongside plugins in plugin database

wine-bugs at winehq.org wine-bugs at winehq.org
Fri Jul 5 21:00:05 CDT 2019


https://bugs.winehq.org/show_bug.cgi?id=46055

ajduck at outlook.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from ajduck at outlook.com ---
I have figured out the cause of this.

It turns out this isn't a Wine bug. Wine is working correctly. It's to do with
Windows/DOS file attributes.

----

So basically what I was doing was adding my own .png files and putting them in
the plugin database folder. Partially this was out of necessity, because some
plugins don't correctly get screenshotted in FL Studio's plugin picture making
feature (namely ones that use the graphics acceleration, this I believe is
possibly a Wine bug) and so I had to make my own screenshots of them and then
crop them.

FL Studio's own plugin picture making feature takes a screenshot of the plugin
and creates a .png of it. But what it does when it saves that picture is not
immediately apparent: it adds DPI information to the png attributes and it also
adds Archive and Hidden attributes to the file.

The first one I found out because when I was adding my own manually
screenshotted and edited images to the plugin database folder my images were
showing up way too big in the plugin database compared to the already included
images with a similar resolution.

But the second one was not as apparent because by the time I realised the issue
with the images not hiding in the browser I had already applied the
"workaround" I stated in the last comment (using a separate Images folder and
then hiding it). I realised there was possibly some missing attribute when I
used FL's "Add [plugin] to plugin database" feature which automatically
screenshots a plugin and adds it into the plugin database/browser and the .png
FL created was appearing correctly. Eventually (thanks to using exa as a
replacement for ls) I found out about extended attributes and that there was
extended attributes to the files FL was creating.

As said earlier, FL adds the Windows attributes "Archive" and "Hidden" to the
.png file. Wine/GNU+Linux environments represent this using extended
attributes: 

    user.DOSATTRIB="0x22"

With "0x20" being Archive and "0x2" being Hidden. If the .png file doesn't have
this attribute it will show up in FL's browser.

----

So if you're doing something similar to me, making manual screenshots of
plugins in order to workaround the FL screenshot bug with graphically
accelerated plugins, you need to add this extended attribute to the file (the
escaping of the quotes is necessary as the value needs to be a string):

    setfattr -n user.DOSATTRIB -v '"0x22"' File.png

To check the file now has the attribute:

    getfattr -n user.DOSATTRIB File.png

Anyway, this issue is not a Wine bug. It's a weird thing FL does that's not
obvious, especially in a Wine environment. Mystery solved.

Thank you to the Wine team for your ongoing work!

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list