-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Legacy iTunes Integration (XML) #9688
Comments
Commented by: esbrandt Upgrading to macOS 10.15 Catalina (due in 2019-10) will break Mixxx´ iTunes integration. |
Commented by: uklotzde https://djtechtools.com/2019/09/15/will-the-end-of-itunes-break-dj-software-in-macos-10-15-catalina/ |
Commented by: ywwg Similarly, a lot of DJs use the XML export function from iTunes to get their tracks into other DJ programs. Maybe we should add support for that? We currently only export M3U/CSV/Text. (Should that be a separate feature request?) |
Commented by: uklotzde The XML export is history with the introduction of Apple Music and this is what this bug report is all about. |
Commented by: ywwg Right. I'm proposing we add xml export so that people who used to organize their libraries with itunes could now organize their libraries with mixxx instead. |
Commented by: ywwg (that seems obviously off topic now, sorry, disregard) |
Commented by: ferranpujolcamins So if we want to use this new apple api we must write a client in swift or objc. We could write this client and integrate it into mixxx somehow. But I think this will cause headaches. What about writing a simple standalone swift client that talks to aoide? |
Commented by: uklotzde All tracks could be imported and added to a separate aoide collection, i.e. "iTunesLibrary @timestamp" in a first step.
I'm already thinking about how to add support for playlists as one of the last missing features that is required to allow lossless import of external libraries. |
Commented by: uklotzde You can provide a hierarchical structure for those imported queries by generating a JSON file with prepared queries that could be loaded into Mixxx: https://github.com/uklotzde/mixxx/blob/dev_aoide/res/aoide/example_prepared_queries.json Each leaf node is a query for a playlist tag:
You need to ensure that the playlist names are unique. The internal playlist names in the tag could differ from the visible names in this file. |
Commented by: foss-4 Cross-linking Discourse thread: https://mixxx.discourse.group/t/itunes-integration/19871 |
Commented by: uklotzde Any progress? Otherwise let's reset the status and assignment. |
Commented by: ferranpujolcamins No. I won't work on it anymore since I don't own a mac. It's everything on
|
So assume you're in favor of marking this issue as fixed? |
@Swiftb0y Sure. Mark issues as fixed eagerly. Assigning a release milestone for documentation purposes is helpful to identify the (upcoming) release. Remaining bugs or open issues could then be tracked by new issues. |
Closing since the |
Reported by: uklotzde
Date: 2019-07-09T06:58:50Z
Status: Confirmed
Importance: High
Launchpad Issue: lp1835876
Tags: library
Apple is gradually dropping support for exporting the iTunes database as an XML file. In newer versions exporting the XML file is no longer enabled by default ("Share iTunes Library XML with other applications"), and this option won't be available in the new Apple Music app.
See also: https://djtechtools.com/2019/04/14/an-itunes-breakup-is-probably-coming-will-this-impact-djs/
The number of bug reports from users that are not able to import their iTunes library is already increasing.
As a replacement Apple offers the database with the iTunesLibrary framework: https://developer.apple.com/documentation/ituneslibrary. Development of a new iTunes integration is limited to macOS due to Apples restrictive practices.
The text was updated successfully, but these errors were encountered: