pyrekordbox 0.2.1__tar.gz → 0.2.2__tar.gz

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/.github/workflows/pypi-publish.yml

@@ -34,26 +34,28 @@ jobs:
     - name: Set up Python
       uses: actions/setup-python@v4
       with:
-        python-version: "3.9"
+        python-version: "3.11"
 
     - name: Install dependencies
       run: |
         python -m pip install --upgrade pip
-        pip install twine
-        pip install .[build]
+        pip install --upgrade build
+        pip install --upgrade twine
 
-    - name: Build and publish distribution 📦 to Test PyPI
+    - name: Build distribution 📦
+      run: |
+        python -m build
+
+    - name: Publish distribution 📦 to Test PyPI
       env:
         TWINE_USERNAME: ${{ secrets.TEST_PYPI_USERNAME }}
         TWINE_PASSWORD: ${{ secrets.TEST_PYPI_PASSWORD }}
       run: |
-        python setup.py sdist bdist_wheel
         twine upload --repository testpypi dist/*
 
-    - name: Build and publish distribution 📦 to PyPI
+    - name: Publish distribution 📦 to PyPI
       env:
         TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
         TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
       run: |
-        python setup.py sdist bdist_wheel
         twine upload dist/*

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/.github/workflows/tests.yml

@@ -43,7 +43,7 @@ jobs:
     strategy:
       matrix:
         os: [windows-latest, macos-latest]
-        python-version: ["3.7", "3.11"]  # check oldest and latest supported version
+        python-version: ["3.7", "3.12"]  # check oldest and latest supported version
         other-os: [true]
 
     runs-on: ${{ matrix.os }}
@@ -66,6 +66,7 @@ jobs:
     - name: Build and install
       run: |
         python -m pip install --upgrade pip
+        pip install setuptools
         pip install .[test]
 
     - name: Get package version

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/.pre-commit-config.yaml

@@ -13,7 +13,7 @@ repos:
           - id: check-yaml
 
     - repo: https://github.com/psf/black
-      rev: 23.9.1
+      rev: 23.10.0
       hooks:
         - id: black
           args: [ --safe ]

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/.readthedocs.yaml

@@ -10,6 +10,7 @@ build:
 
 sphinx:
   builder: html
+  configuration: docs/source/conf.py
 
 python:
   install:

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/CHANGELOG.md

@@ -1,6 +1,42 @@
 # What's New
 
 
+<a name="0.2.2"></a>
+## [0.2.2] - 2023-10-26
+
+### New Features
+
+- **add new albums to the RBv6 db**  
+  New entries can now be added to the `DjmdAlbum` table.
+- **add new genres to the RBv6 db**  
+  New entries can now be added to the `DjmdGenre` table.
+- **add new artists to the RBv6 db**  
+  New entries can now be added to the `DjmdArtist` table.
+- **add new labels to the RBv6 db**  
+  New entries can now be added to the `DjmdLabel` table.
+- **support renamed Rekordbox application directory**  
+  The user can now specify the directory name of the Rekordbox application directory. 
+  This supports multiple Rekordbox installations of the same major version.
+
+### Improvements/Bug Fixes
+
+- **don't raise error if key is in cache**  
+  This fixes an issue when using the database handler for Rekordbox>6.6.5 with the cached key.
+- **de-obfuscate PSSI tag data on exported ANLZ files**  
+  The PSSI tag data of ANLZ files that rekordbox 6 *exports* is garbled with an XOR mask.
+  If the first few known fields of the PSSI tag are not valid values this indicates a garbled tag
+  and the data is de-obfuscated. 
+  Thank you [@troyhacks](https://github.com/troyhacks) for the de-obfuscation.
+- **add disabled context manager to the RBv6 `RekordboxAgentRegistry`**  
+- **only re-enable RBV6 USN tracking if it was enabled**
+
+### Documentation
+
+- **add missing documentation of the PSSI tag of ANLZ files**  
+- **Fix typo in djmdCue table documentation**  
+- **update quickstart documentation**  
+
+
 <a name="0.2.1"></a>
 ## [0.2.1] - 2023-10-20
 
@@ -430,7 +466,8 @@ This release contains documentation fixes.
 - **add missing djmd tables to `master.db` database documentation**
 
 
-[Unreleased]: https://github.com/dylanljones/pyrekordbox/compare/0.2.1...HEAD
+[Unreleased]: https://github.com/dylanljones/pyrekordbox/compare/0.2.2...HEAD
+[0.2.2]: https://github.com/dylanljones/pyrekordbox/compare/0.2.1...0.2.2
 [0.2.1]: https://github.com/dylanljones/pyrekordbox/compare/0.2.0...0.2.1
 [0.2.0]: https://github.com/dylanljones/pyrekordbox/compare/0.1.8...0.2.0
 [0.1.8]: https://github.com/dylanljones/pyrekordbox/compare/0.1.7...0.1.8

{pyrekordbox-0.2.1/pyrekordbox.egg-info → pyrekordbox-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pyrekordbox
-Version: 0.2.1
+Version: 0.2.2
 Summary: Inofficial Python package for interacting with the library of Pioneers Rekordbox DJ software.
 Author-email: Dylan Jones <dylanljones94@gmail.com>
 License: MIT License
@@ -50,19 +50,14 @@ License-File: LICENSE
 Requires-Dist: bidict>=0.21.0
 Requires-Dist: blowfish>=0.6.0
 Requires-Dist: construct>=2.10.0
-Requires-Dist: hypothesis>=6.0.0
 Requires-Dist: numpy>=1.19.0
 Requires-Dist: packaging
-Requires-Dist: pytest>=6.2.0
 Requires-Dist: psutil>=5.9.0
-Requires-Dist: setuptools>=60.0.0
-Requires-Dist: setuptools-scm[toml]>=4
 Requires-Dist: sqlalchemy>=2.0.0
-Provides-Extra: build
-Requires-Dist: wheel>=0.37.0; extra == "build"
 Provides-Extra: test
+Requires-Dist: hypothesis>=6.0.0; extra == "test"
+Requires-Dist: pytest>=6.2.0; extra == "test"
 Requires-Dist: pytest-cov; extra == "test"
-Requires-Dist: wheel>=0.37.0; extra == "test"
 
 
 <p align="center">
@@ -88,7 +83,7 @@ Pioneers Rekordbox DJ Software. It currently supports
 - Analysis files (ANLZ)
 - My-Setting files
 
-Tested Rekordbox versions: ``5.8.6 | 6.5.3``
+Tested Rekordbox versions: ``5.8.6 | 6.5.3 | 6.7.7``
 
 
 |⚠️| This project is still under development and might contain bugs or have breaking API changes in the future.   |
@@ -112,7 +107,7 @@ where `VERSION` is a release, tag or branch name.
 
 Unlocking the new Rekordbox 6 `master.db` database file requires [SQLCipher][sqlcipher].
 Pyrekordbox makes no attempt to download/install SQLCipher, as it is a
-pure Python package - whereas the SQLCipher/pysqlcipher3 installation is
+pure Python package - whereas the SQLCipher/sqlcipher3 installation is
 platform-dependent and can not be installed via ``pip``.
 
 #### Windows
@@ -205,7 +200,7 @@ So far only a few tables support adding or deleting entries:
 - ``DjmdSongPlaylist``: Songs in a playlist
 
 Starting from Rekordbox version ``6.6.5`` Pioneer obfuscated the ``app.asar`` file
-contents, breaking the key extraction (see [this issue](https://github.com/dylanljones/pyrekordbox/issues/64) for more details).
+contents, breaking the key extraction (see [this discussion](https://github.com/dylanljones/pyrekordbox/discussions/97) for more details).
 If you are using a later version of Rekorbox and have no cached key from a previous
 version, the database can not be unlocked automatically.
 The command line interface of ``pyrekordbox`` provides a command for downloading
@@ -304,6 +299,8 @@ sync = mysett.get("sync")
 quant = mysett.get("quantize")
 ````
 
+The `DEVSETTING.DAT` file is still not supported
+
 
 ## 💡 File formats
 
@@ -323,6 +320,9 @@ If you encounter an issue or want to contribute to pyrekordbox, please feel free
 `pyrekordbox` and the commit-message style can be found in
 [CONTRIBUTING].
 
+For general questions or discussions about Rekordbox, please use [GitHub Discussions][discussions]
+instead of opening an issue.
+
 Pyrekordbox is tested on Windows and MacOS, however some features can't be tested in
 the CI setup since it requires a working Rekordbox installation.
 
@@ -374,6 +374,7 @@ the CI setup since it requires a working Rekordbox installation.
 [mysettings-doc]: https://pyrekordbox.readthedocs.io/en/stable/formats/mysetting.html
 
 [new-issue]: https://github.com/dylanljones/pyrekordbox/issues/new/choose
+[discussions]: https://github.com/dylanljones/pyrekordbox/discussions
 [CONTRIBUTING]: https://github.com/dylanljones/pyrekordbox/blob/master/CONTRIBUTING.md
 [CHANGELOG]: https://github.com/dylanljones/pyrekordbox/blob/master/CHANGELOG.md
 [INSTALLATION]: https://github.com/dylanljones/pyrekordbox/blob/master/INSTALLATION.md

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/README.md

@@ -22,7 +22,7 @@ Pioneers Rekordbox DJ Software. It currently supports
 - Analysis files (ANLZ)
 - My-Setting files
 
-Tested Rekordbox versions: ``5.8.6 | 6.5.3``
+Tested Rekordbox versions: ``5.8.6 | 6.5.3 | 6.7.7``
 
 
 |⚠️| This project is still under development and might contain bugs or have breaking API changes in the future.   |
@@ -46,7 +46,7 @@ where `VERSION` is a release, tag or branch name.
 
 Unlocking the new Rekordbox 6 `master.db` database file requires [SQLCipher][sqlcipher].
 Pyrekordbox makes no attempt to download/install SQLCipher, as it is a
-pure Python package - whereas the SQLCipher/pysqlcipher3 installation is
+pure Python package - whereas the SQLCipher/sqlcipher3 installation is
 platform-dependent and can not be installed via ``pip``.
 
 #### Windows
@@ -139,7 +139,7 @@ So far only a few tables support adding or deleting entries:
 - ``DjmdSongPlaylist``: Songs in a playlist
 
 Starting from Rekordbox version ``6.6.5`` Pioneer obfuscated the ``app.asar`` file
-contents, breaking the key extraction (see [this issue](https://github.com/dylanljones/pyrekordbox/issues/64) for more details).
+contents, breaking the key extraction (see [this discussion](https://github.com/dylanljones/pyrekordbox/discussions/97) for more details).
 If you are using a later version of Rekorbox and have no cached key from a previous
 version, the database can not be unlocked automatically.
 The command line interface of ``pyrekordbox`` provides a command for downloading
@@ -238,6 +238,8 @@ sync = mysett.get("sync")
 quant = mysett.get("quantize")
 ````
 
+The `DEVSETTING.DAT` file is still not supported
+
 
 ## 💡 File formats
 
@@ -257,6 +259,9 @@ If you encounter an issue or want to contribute to pyrekordbox, please feel free
 `pyrekordbox` and the commit-message style can be found in
 [CONTRIBUTING].
 
+For general questions or discussions about Rekordbox, please use [GitHub Discussions][discussions]
+instead of opening an issue.
+
 Pyrekordbox is tested on Windows and MacOS, however some features can't be tested in
 the CI setup since it requires a working Rekordbox installation.
 
@@ -308,6 +313,7 @@ the CI setup since it requires a working Rekordbox installation.
 [mysettings-doc]: https://pyrekordbox.readthedocs.io/en/stable/formats/mysetting.html
 
 [new-issue]: https://github.com/dylanljones/pyrekordbox/issues/new/choose
+[discussions]: https://github.com/dylanljones/pyrekordbox/discussions
 [CONTRIBUTING]: https://github.com/dylanljones/pyrekordbox/blob/master/CONTRIBUTING.md
 [CHANGELOG]: https://github.com/dylanljones/pyrekordbox/blob/master/CHANGELOG.md
 [INSTALLATION]: https://github.com/dylanljones/pyrekordbox/blob/master/INSTALLATION.md

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/docs/source/formats/anlz.md

@@ -247,7 +247,7 @@ Rekordbox Performance Mode, but starting with Rekordbox version 6 it also gets
 exported to external media so CDJ-3000 players can use it to control lighting looks.
 
 ```{note}
-The version that Rekordbox 6 exports is garbled with an XOR mask to make it
+The version that Rekordbox 6 **exports** is garbled with an XOR mask to make it
 more difficult to access the data. All bytes after `len_e` are XOR-masked with a
 pattern that is generated by adding the value of `len_e` to each byte of the following
 base pattern:
@@ -270,14 +270,16 @@ entries are present in the tag. Each entry represents one recognized phrase.
 
 The value `mood` specifies the overall type of phrase structure that rekordbox chose to
 represent the song, based on its analysis of the audio.
-The value 1 is a “high” mood
-where the phrase types consist of “Intro”, “Up”, “Down”, “Chorus”, and “Outro”.
-Other values in each phrase entry cause the intro, chorus, and outro phrases to have
-their labels subdivided into styes “1” or “2” (for example, “Intro 1”), and “up” is
-subdivided into style “Up 1”, “Up 2”, or “Up 3”. See the table below for an expanded
-version of this description.
+
+The value 1 is a “high” mood where the phrase types consist of “Intro”, “Up”, “Down”,
+“Chorus”, and “Outro”. Other values in each phrase entry cause the intro, chorus, and
+outro phrases to have their labels subdivided into styes “1” or “2”
+(for example, “Intro 1”), and “up” is subdivided into style “Up 1”, “Up 2”, or “Up 3”.
+See the table below for an expanded version of this description.
+
 The value 2 is a “mid” mood where the phrase types are labeled “Intro”, “Verse 1”
 through “Verse 6”, “Chorus”, “Bridge”, and “Outro”.
+
 And value 3 is a “low” mood where the phrase types are labeled “Intro”, “Verse 1”,
 “Verse 2”, “Chorus”, “Bridge”, and “Outro”. There are three different phrase type
 values for each of “Verse 1” and “Verse 2”, but rekordbox makes no distinction between
@@ -301,6 +303,175 @@ Each phrase entry has the structure shown below:
 Song structure entry.
 ```
 
+The first two bytes of each song structure entry hold `index`, which numbers each phrase,
+starting at one and incrementing with each entry. That is followed by beat,
+a two-byte value that specifies the beat at which this phrase begins in the track.
+It continues until either the beat number of the next phrase, or the beat identified
+by end in the tag header if this is the last entry.
+
+`kind` specifies what kind of phrase rekordbox has identified here.
+The interpretation depends on the value of mood in the tag header, as is detailed the
+table below. In the case of the “high” mood, there are numbered variations for some
+of the phrases displayed in rekordbox that are not reflected in kind, but depend on the
+values of three flag bytes `k1` through `k3` in a complicated way shown in its own table.
+
+We also noticed that when `mood`, `kind` and the `k` flags indicate a phrase of type
+“Up 3”, additional beat numbers (which all fall within the phrase) are present in the
+entry. These may indicate points within the phrase at which lighting changes would look good;
+more investigation is required to make sense of them.
+The number of beats that will be listed seems to depend on the value of the flag `b`:
+if this has the value 0, there will be a single beat found in `beat2`, and if `b` has
+the value 1 there will be three different beat numbers present, with increasing values,
+in `beat2`, `beat3` and `beat4`.
+
+`fill` is a flag that indicates whether there are fill (non-phrase) beats at the end of
+the phrase. If it is non-zero, then ``beat fill`` holds the beat number at which the
+fill begins. When fill-in is present, it is indicated in rekordbox by little dots on the
+full waveform. The manual says:
+
+
+    [Fill in] is a section that provides improvisational changes at the end of phrase.
+    [Fill in] is detected at the end of Intro, Up, and Chorus (up to 4 beats).
+
+
+
+```{eval-rst}
+.. list-table:: Phrase labels in each mood.
+   :header-rows: 1
+
+   * - Phrase ID
+     - Low Label
+     - Mid Label
+     - High Label
+   * - 1
+     - Intro
+     - Intro
+     - Intro n
+   * - 2
+     - Verse 1
+     - Verse 1
+     - Up n
+   * - 3
+     - Verse 1
+     - Verse 2
+     - Down
+   * - 4
+     - Verse 1
+     - Verse 3
+     -
+   * - 5
+     - Verse 2
+     - Verse 4
+     - Chorus n
+   * - 6
+     - Verse 2
+     - Verse 5
+     - Outro n
+   * - 7
+     - Verse 2
+     - Verse 6
+     -
+   * - 8
+     - Bridge
+     - Bridge
+     -
+   * - 9
+     - Chorus
+     - Chorus
+     -
+   * - 10
+     - Outro
+     - Outro
+     -
+```
+
+```{eval-rst}
+.. list-table:: High mood phrase variants.
+   :header-rows: 1
+
+   * - Phrase ID
+     - k1
+     - k2
+     - k3
+     - Expanded Label
+   * - 1
+     - 1
+     -
+     -
+     - Intro 1
+   * - 1
+     - 0
+     -
+     -
+     - Intro 2
+   * - 2
+     -
+     - 0
+     - 0
+     - Up 1
+   * - 2
+     -
+     - 0
+     - 1
+     - Up 2
+   * - 2
+     -
+     - 1
+     - 0
+     - Up 3
+   * - 3
+     -
+     -
+     -
+     - Down 1
+   * - 5
+     - 1
+     -
+     -
+     - Chorus 2
+   * - 5
+     - 0
+     -
+     -
+     - Chorus 1
+   * - 6
+     - 1
+     -
+     -
+     - Outro 1
+   * - 6
+     - 0
+     -
+     -
+     - Outro 2
+```
+
+```{eval-rst}
+.. list-table:: Track banks.
+   :header-rows: 1
+
+   * - Bank ID
+     - Label
+   * - 0
+     - Default (treated as Cool)
+   * - 1
+     - Cool
+   * - 2
+     - Natural
+   * - 3
+     - Hot
+   * - 4
+     - Subtle
+   * - 5
+     - Warm
+   * - 6
+     - Vivid
+   * - 7
+     - Club 1
+   * - 8
+     - Club 2
+```
+
 ### PWAV: Waveform Preview Tag
 
 Seen in `.DAT` analysis files. This kind of section holds a fixed-width monochrome

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/docs/source/formats/db6.md

@@ -489,7 +489,7 @@ around 1/75th of a second (13.333ms) per frame, i.e. about half the granularity
      - `0` if not a loop or VBR/ABR MPEG file
    * - `Kind`
      - Type of cue point
-     - Cue= `0` , Fade-In= `0` , Fade-Out= `0` , Load= `3` , Loop= `4`
+     - Cue= `0` , Fade-In= `1` , Fade-Out= `2` , Load= `3` , Loop= `4`
    * - `Color`
      - The color ID of the cue point
      - `-1` if no color

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/docs/source/index.md

@@ -28,11 +28,7 @@ Pioneer's Rekordbox DJ Software. It currently supports
 - Analysis files (ANLZ)
 - My-Settings files
 
-Tested Rekordbox versions: `5.8.6 | 6.5.3`
-
-Starting from version `6.6.5` Pioneer obfuscated the `app.asar` file contents, breaking
-the key extraction (see [this issue][issue] and the Rekordbox 6 database section for
-more details).
+Tested Rekordbox versions: `5.8.6 | 6.5.3 | 6.7.7`
 
 ```{warning}
 This project is still under development and might contain bugs or
@@ -59,10 +55,10 @@ maxdepth: 2
 caption: File formats
 ---
 
+formats/db6
 formats/xml
 formats/anlz
 formats/mysetting
-formats/db6
 ```
 
 ```{toctree}

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/docs/source/quickstart.md

@@ -25,18 +25,6 @@ from pyrekordbox import show_config
 
 show_config()
 ````
-
-which, for example, will print
-````
-Pioneer:
-   app_dir =      C:\Users\user\AppData\Roaming\Pioneer
-   install_dir =  C:\Program Files\Pioneer
-Rekordbox 5:
-   app_dir =      C:\Users\user\AppData\Roaming\Pioneer\rekordbox
-   install_dir =  C:\Program Files\Pioneer\rekordbox 5.8.6
-   ...
-````
-
 If for some reason the configuration fails the values can be updated by providing the
 paths to the directory where Pioneer applications are installed (`pioneer_install_dir`)
 and to the directory where Pioneer stores the application data  (`pioneer_app_dir`)
@@ -45,12 +33,65 @@ from pyrekordbox.config import update_config
 
 update_config("<pioneer_install_dir>", "<pioneer_app_dir>")
 ````
-
 Alternatively the two paths can be specified in a configuration file under the section
 `rekordbox`. Supported configuration files are pyproject.toml, setup.cfg, pyrekordbox.toml,
 pyrekordbox.cfg and pyrekordbox.yaml.
 
 
+## Rekordbox 6 database
+
+Rekordbox 6 now uses a SQLite database for storing the collection content.
+Unfortunatly, the new `master.db` SQLite database is encrypted using
+[SQLCipher][sqlcipher], which means it can't be used without the encryption key.
+However, since your data is stored and used locally, the key must be present on the
+machine running Rekordbox.
+
+Pyrekordbox can unlock the new Rekordbox `master.db` SQLite database and provides
+an easy interface for accessing the data stored in it:
+
+````python
+from pyrekordbox import Rekordbox6Database
+
+db = Rekordbox6Database()
+
+for content in db.get_content():
+    print(content.Title, content.Artist.Name)
+
+playlist = db.get_playlist()[0]
+for song in playlist.Songs:
+    content = song.Content
+    print(content.Title, content.Artist.Name)
+````
+Fields in the Rekordbox database that are stored without linking to other tables
+can be changed via the corresponding property of the object:
+````python
+content = db.get_content()[0]
+content.Title = "New Title"
+````
+Some fields are stored as references to other tables, for example the artist of a track.
+Check the [documentation](#db6-format) of the corresponding object for more information.
+So far only a few tables support adding or deleting entries:
+- ``DjmdPlaylist``: Playlists/Playlist Folders
+- ``DjmdSongPlaylist``: Songs in a playlist
+
+````{important}
+Starting from Rekordbox version ``6.6.5`` Pioneer obfuscated the ``app.asar`` file
+contents, breaking the key extraction (see [this discussion](https://github.com/dylanljones/pyrekordbox/discussions/97) for more details).
+If you are using a later version of Rekorbox and have no cached key from a previous
+version, the database can not be unlocked automatically.
+The command line interface of ``pyrekordbox`` provides a command for downloading
+the key from known sources and writing it to the cache file:
+```shell
+python -m pyrekordbox download-key
+```
+Once the key is cached the database can be opened without providing the key.
+The key can also be provided manually:
+```python
+db = Rekordbox6Database(key="<insert key here>")
+```
+````
+
+
 ## Rekordbox XML
 
 The Rekordbox XML database is used for importing (and exporting) Rekordbox collections
@@ -107,6 +148,17 @@ Changing and creating the Rekordbox analysis files is planned as well, but for t
 full structure of the analysis files has to be understood.
 
 
+```{note}
+Some ANLZ tags are still unsupported:
+  - PCOB
+  - PCO2
+  - PSSI
+  - PWV6
+  - PWV7
+  - PWVC
+```
+
+
 ## Rekordbox My-Settings
 
 Rekordbox stores the user settings in `*SETTING.DAT` files, which get exported to USB
@@ -126,37 +178,8 @@ sync = mysett.get("sync")
 quant = mysett.get("quantize")
 ````
 
-
-## Rekordbox 6 database
-
-Rekordbox 6 now uses a SQLite database for storing the collection content.
-Unfortunatly, the new `master.db` SQLite database is encrypted using
-[SQLCipher][sqlcipher], which means it can't be used without the encryption key.
-However, since your data is stored and used locally, the key must be present on the
-machine running Rekordbox.
-
-Pyrekordbox can unlock the new Rekordbox `master.db` SQLite database and provides
-an easy interface for accessing the data stored in it:
-
-````python
-from pyrekordbox import Rekordbox6Database
-
-db = Rekordbox6Database()
-
-for content in db.get_content():
-    print(content.Title, content.Artist.Name)
-
-playlist = db.get_playlist()[0]
-for song in playlist.Songs:
-    content = song.Content
-    print(content.Title, content.Artist.Name)
-````
-Adding new rows to the tables of the database is not supported since it is not yet known
-how Rekordbox generates the UUID/ID's. Using wrong values for new database entries
-could corrupt the library. This feature will be added after some testing.
-Changing existing entries like the title, artist or file path of a track in the database
-should work as expected.
-
-
+```{note}
+The `DEVSETTING.DAT` file is still not supported
+```
 
 [sqlcipher]: https://www.zetetic.net/sqlcipher/open-source/

{pyrekordbox-0.2.1 → pyrekordbox-0.2.2}/pyproject.toml

@@ -32,23 +32,17 @@ dependencies = [
     "bidict>=0.21.0",
     "blowfish>=0.6.0",
     "construct>=2.10.0",
-    "hypothesis>=6.0.0",
     "numpy>=1.19.0",
     "packaging",
-    "pytest>=6.2.0",
     "psutil>=5.9.0",
-    "setuptools>=60.0.0",
-    "setuptools-scm[toml]>=4",
     "sqlalchemy>=2.0.0",
 ]
 
 [project.optional-dependencies]
-build = [
-    "wheel>=0.37.0",
-]
 test = [
+    "hypothesis>=6.0.0",
+    "pytest>=6.2.0",
     "pytest-cov",
-    "wheel>=0.37.0",
 ]
 
 [project.urls]
@@ -61,8 +55,8 @@ Tracker = "https://github.com/dylanljones/pyrekordbox/issues"
 
 [build-system]
 requires = [
-    "setuptools >= 60.0.0",
-    "setuptools_scm[toml] >= 4, <6",
+    "setuptools >= 61.0.0",
+    "setuptools_scm[toml] >= 4",
     "setuptools_scm_git_archive",
     "wheel >= 0.37.0",
 ]