Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support all audio files recognized by GNOME's GIO #102

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

OlekMazur
Copy link

  1. Remove built-in white lists of supported MIME types
    (apart from playlists, which need special handling)
  2. Don't discard files without tags recognized by taglib

This should cover all future issues similar to #58.

const gchar *mime_asf[] = {"video/x-ms-asf", "audio/x-ms-wma", "application/x-ext-wma", NULL};
const gchar *mime_mp4 [] = {"audio/x-m4a", "application/x-ext-m4a", NULL};
const gchar *mime_ape [] = {"application/x-ape", "audio/ape", "audio/x-ape", NULL};
const gchar *mime_tracker[] = {"audio/x-mod", "audio/x-xm", "application/x-ext-mod", NULL};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although not 100% supported, you should leave this for Windows... You can only detect audio files by extensions... application/x-ext-???

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, probably I should leave an array of supported mimetypes which don't begin with "audio/"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍
As codecs are also distributed in the installer, perhaps we can restrict it better...

@matiasdelellis
Copy link
Contributor

Hi @wymiatacz
It is a welcome change.. 😃

It is a change that I've been thinking a while.. But the problem to solve is that every time that save a tag change pragha try to save tags using taglib regardless if support it or if it is a CD or an MTP device where not work.. Let me see as a complement to solve this too .... 😉

Thanks for all,
Regards,

This allows playing files supported by GStreamer regardless
of whether their MIME type is present in Pragha's internal
white lists and even if unsupported by taglib
@OlekMazur
Copy link
Author

Hi @matiasdelellis
Let me know what do you think about new version of the change.
Regards

@matiasdelellis
Copy link
Contributor

Hi @wymiatacz
Sorry for the delay in answering, and the slow progress in the development.. 😞
You're right.. I have few excuses to do this .. Even more taking in account the advances in Ampache or mtp..
I have to differentiate the files that can edit taglib, and the read only services... 😉

@OlekMazur
Copy link
Author

I just uploaded a new version of the change a few days ago and asked you for a comment. This time the change proposal is much less, let's say, invasive than the original one. If you tell me what's wrong with it, I can try to improve it further.

With my change, the "Edit track information" option is still available and shows the tag edition dialog even if the track is unsupported by taglib (therefore clicking OK has no effect). The error in saving tags is silently ignored. Is this the only problem, or do you see others? Do you have a proposal how it should behave? Graying out this option for files unsupported by taglib?

@matiasdelellis
Copy link
Contributor

matiasdelellis commented Jan 4, 2018

Hi @wymiatacz
Excuse me again, between being busy, I lost my computer with a lot of information, and now I'm coming back..
Your proposal in principle is correct, but for the future release of pragha probably falls short.. 😉

I just wanted to plan a more comprehensive proposal:

  • That the database and the PraghaMusicobjet have the information if it can be edited..
  • If one or more selected songs can not be edited, show some warning in the dialog. (If you edit these files when update/analyzing the collection, they may be lost), or perhaps not allow editing..
  • If can edit, that each PraghaProvider (MTP, can be editable, Ampache theoretically the administardador could edit, but the users can not. CDROM not..) is responsible for modifying its files.
  • ..

But in principle, adding an option to "Allow partially supported files" as a warning, would be enough to accept your proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants