[GH-ISSUE #716] Reading lyrics from id3 medadata #509

Closed
opened 2026-02-26 02:33:24 +03:00 by kerem · 39 comments
Owner

Originally created by @chawker21 on GitHub (Jan 31, 2018).
Original GitHub issue: https://github.com/koel/koel/issues/716

I am trying to figure out the best way to sync a text file containing the written text of the audio file in the lyrics section for the track.

I see in the code in Media.php

class Media
{
/**
* All applicable tags in a media file that we cater for.
* Note that each isn't necessarily a valid ID3 tag name.
*
* @var array
*/
protected $allTags = [
'artist',
'album',
'title',
'length',
'track',
'disc',
'lyrics',
'cover',
'mtime',
'compilation',
];

which looks like it will search for the lyrics in the ID3 section of the metadata but I put the text in the metadata and it does not show up in the lyrics.

The other way I am thinking of doing this is somehow searching the directory for the corresponding text file that belongs with the song file, They differ only by the word mp3 in the file name. I am having difficulty understanding how this would work.

Are there any ideas on how I can make this work whether there is a way it should be done or how I can implement a fix to make it work?

Originally created by @chawker21 on GitHub (Jan 31, 2018). Original GitHub issue: https://github.com/koel/koel/issues/716 I am trying to figure out the best way to sync a text file containing the written text of the audio file in the lyrics section for the track. I see in the code in Media.php class Media { /** * All applicable tags in a media file that we cater for. * Note that each isn't necessarily a valid ID3 tag name. * * @var array */ protected $allTags = [ 'artist', 'album', 'title', 'length', 'track', 'disc', 'lyrics', 'cover', 'mtime', 'compilation', ]; which looks like it will search for the lyrics in the ID3 section of the metadata but I put the text in the metadata and it does not show up in the lyrics. The other way I am thinking of doing this is somehow searching the directory for the corresponding text file that belongs with the song file, They differ only by the word mp3 in the file name. I am having difficulty understanding how this would work. Are there any ideas on how I can make this work whether there is a way it should be done or how I can implement a fix to make it work?
kerem closed this issue 2026-02-26 02:33:24 +03:00
Author
Owner

@chawker21 commented on GitHub (Jan 31, 2018):

after messing with it a little more It seems uploading lyrics from id3 might be broken altogether, not sure if anyone else is having trouble but I cant seem to get lyrics uploaded through metadata at all, I can other metadata though like album and title.

<!-- gh-comment-id:362007166 --> @chawker21 commented on GitHub (Jan 31, 2018): after messing with it a little more It seems uploading lyrics from id3 might be broken altogether, not sure if anyone else is having trouble but I cant seem to get lyrics uploaded through metadata at all, I can other metadata though like album and title.
Author
Owner

@chawker21 commented on GitHub (Feb 1, 2018):

Got it to work by fixing the label that had a comment saying tag name is misspelled for unsynchronised__lyric.

public function getInfo()
{
$info = $this->getID3->analyze($this->path);
// log::info($info);
if (isset($info['error']) || !isset($info['playtime_seconds'])) {
$this->syncError = isset($info['error']) ? $info['error'][0] : 'No playtime found';

        return [];
    }

    // Copy the available tags over to comment.
    // This is a helper from getID3, though it doesn't really work well.
    // We'll still prefer getting ID3v2 tags directly later.
    // Read on.
    getid3_lib::CopyTagsToComments($info);

    $track = 0;

    // Apparently track number can be stored with different indices as the following.
    $trackIndices = [
        'comments.track',
        'comments.tracknumber',
        'comments.track_number',
    ];

    for ($i = 0; $i < count($trackIndices) && $track === 0; $i++) {
        $track = array_get($info, $trackIndices[$i], [0])[0];
    }

    $props = [
        'artist' => '',
        'album' => '',
        'compilation' => false,
        'title' => basename($this->path, '.'.pathinfo($this->path, PATHINFO_EXTENSION)), // default to be file name
        'length' => $info['playtime_seconds'],
        'track' => (int) $track,
        'disc' => (int) array_get($info, 'comments.part_of_a_set.0', 1),
        'lyrics' => 'hello',
        'cover' => array_get($info, 'comments.picture', [null])[0],
        'path' => $this->path,
        'mtime' => $this->mtime,
    ];

    if (!$comments = array_get($info, 'comments_html')) {
        return $props;
    }

    $propertyMap = [
        'artist' => 'artist',
        'albumartist' => 'band',
        'album' => 'album',
        'title' => 'title',
        'lyrics' => 'unsynchronised_lyric', // this tag name is misspelled 'unsychronised_lyric'
        'compilation' => 'part_of_a_compilation',
    ];
<!-- gh-comment-id:362144524 --> @chawker21 commented on GitHub (Feb 1, 2018): Got it to work by fixing the label that had a comment saying tag name is misspelled for unsynchronised__lyric. public function getInfo() { $info = $this->getID3->analyze($this->path); // log::info($info); if (isset($info['error']) || !isset($info['playtime_seconds'])) { $this->syncError = isset($info['error']) ? $info['error'][0] : 'No playtime found'; return []; } // Copy the available tags over to comment. // This is a helper from getID3, though it doesn't really work well. // We'll still prefer getting ID3v2 tags directly later. // Read on. getid3_lib::CopyTagsToComments($info); $track = 0; // Apparently track number can be stored with different indices as the following. $trackIndices = [ 'comments.track', 'comments.tracknumber', 'comments.track_number', ]; for ($i = 0; $i < count($trackIndices) && $track === 0; $i++) { $track = array_get($info, $trackIndices[$i], [0])[0]; } $props = [ 'artist' => '', 'album' => '', 'compilation' => false, 'title' => basename($this->path, '.'.pathinfo($this->path, PATHINFO_EXTENSION)), // default to be file name 'length' => $info['playtime_seconds'], 'track' => (int) $track, 'disc' => (int) array_get($info, 'comments.part_of_a_set.0', 1), 'lyrics' => 'hello', 'cover' => array_get($info, 'comments.picture', [null])[0], 'path' => $this->path, 'mtime' => $this->mtime, ]; if (!$comments = array_get($info, 'comments_html')) { return $props; } $propertyMap = [ 'artist' => 'artist', 'albumartist' => 'band', 'album' => 'album', 'title' => 'title', 'lyrics' => 'unsynchronised_lyric', // this tag name is misspelled 'unsychronised_lyric' 'compilation' => 'part_of_a_compilation', ];
Author
Owner

@phanan commented on GitHub (Feb 2, 2018):

So in the end what tag name did you use?

<!-- gh-comment-id:362556236 --> @phanan commented on GitHub (Feb 2, 2018): So in the end what tag name did you use?
Author
Owner

@chawker21 commented on GitHub (Feb 2, 2018):

My metadata uses Lyrics, I was trying to figure out if capitalization matters which it seems to not matter whether its Lyrics lryics or LYRICS, when I used

$info = $this->getID3->analyze($this->path);
// log::info($info);
if (isset($info['error']) || !isset($info['playtime_seconds'])) {

log::infor($info); it showed every metadata key value in the logs and from there I could see that my lyrics where showing under unsynchronised_lyric and so I corrected the spelling in the code and it worked.

<!-- gh-comment-id:362648749 --> @chawker21 commented on GitHub (Feb 2, 2018): My metadata uses Lyrics, I was trying to figure out if capitalization matters which it seems to not matter whether its Lyrics lryics or LYRICS, when I used $info = $this->getID3->analyze($this->path); // log::info($info); if (isset($info['error']) || !isset($info['playtime_seconds'])) { log::infor($info); it showed every metadata key value in the logs and from there I could see that my lyrics where showing under unsynchronised_lyric and so I corrected the spelling in the code and it worked.
Author
Owner

@chawker21 commented on GitHub (Feb 2, 2018):

This is in File.php by the way.

<!-- gh-comment-id:362649011 --> @chawker21 commented on GitHub (Feb 2, 2018): This is in File.php by the way.
Author
Owner

@chawker21 commented on GitHub (Feb 2, 2018):

$propertyMap = [
'artist' => 'artist',
'albumartist' => 'band',
'album' => 'album',
'title' => 'title',
'lyrics' => 'unsychronised_lyric', // this tag name is misspelled
'compilation' => 'part_of_a_compilation',
];
this is how the code is in File.php in the app/models. I dont know if it is intentional or not, it has a comment that it is misspelled and that was my problem.

<!-- gh-comment-id:362649860 --> @chawker21 commented on GitHub (Feb 2, 2018): $propertyMap = [ 'artist' => 'artist', 'albumartist' => 'band', 'album' => 'album', 'title' => 'title', 'lyrics' => 'unsychronised_lyric', // this tag name is misspelled 'compilation' => 'part_of_a_compilation', ]; this is how the code is in File.php in the app/models. I dont know if it is intentional or not, it has a comment that it is misspelled and that was my problem.
Author
Owner

@phanan commented on GitHub (Feb 2, 2018):

Hmm. Indeed, it was "unsynchronised_lyric" in the beginning (just like what you have now) and was changed because of a bug, as documented. Weird.

<!-- gh-comment-id:362664547 --> @phanan commented on GitHub (Feb 2, 2018): Hmm. Indeed, it was "unsynchronised_lyric" in the beginning (just like what you have now) and was changed because of a bug, as documented. Weird.
Author
Owner

@chawker21 commented on GitHub (Feb 2, 2018):

I’m glad, I learned a lot about using ID3 with Laravel. I really like how you can scan a directory and input to dB. Many projects I end up imputing each data object individually because I didn’t know you could do that.

<!-- gh-comment-id:362697347 --> @chawker21 commented on GitHub (Feb 2, 2018): I’m glad, I learned a lot about using ID3 with Laravel. I really like how you can scan a directory and input to dB. Many projects I end up imputing each data object individually because I didn’t know you could do that.
Author
Owner

@phanan commented on GitHub (Apr 14, 2018):

It seems the getID3 library corrected this bug https://github.com/JamesHeinrich/getID3/issues/136. Will fix it in Koel. Thanks!

<!-- gh-comment-id:381360144 --> @phanan commented on GitHub (Apr 14, 2018): It seems the getID3 library corrected this bug https://github.com/JamesHeinrich/getID3/issues/136. Will fix it in Koel. Thanks!
Author
Owner

@phanan commented on GitHub (Apr 14, 2018):

On second check, the change hasn't landed to a stable version of getID3, so I don't know how you encountered this issue (unless you somehow got a dev/master version of getID3). I've reverted the (broken) fix.

<!-- gh-comment-id:381361096 --> @phanan commented on GitHub (Apr 14, 2018): On second check, the change hasn't landed to a stable version of getID3, so I don't know how you encountered this issue (unless you somehow got a dev/master version of getID3). I've reverted the (broken) fix.
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

The error I had was not with the getID3 at all, it was a misspelling in the source code of the Koel master that I had downloaded. unSynchronized lyric was UnSychronised

<!-- gh-comment-id:381429042 --> @chawker21 commented on GitHub (Apr 15, 2018): The error I had was not with the getID3 at all, it was a misspelling in the source code of the Koel master that I had downloaded. unSynchronized lyric was UnSychronised
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

I fixed the spelling in the Koel code inside the file.php file and everything worked. even if it is misspelled in getID3 fixing it in Koel solved the problem.
unsync

<!-- gh-comment-id:381429497 --> @chawker21 commented on GitHub (Apr 15, 2018): I fixed the spelling in the Koel code inside the file.php file and everything worked. even if it is misspelled in getID3 fixing it in Koel solved the problem. ![unsync](https://user-images.githubusercontent.com/19377063/38782180-9ec4485a-40ac-11e8-8339-47791e6cc1dc.jpg)
Author
Owner

@phanan commented on GitHub (Apr 15, 2018):

That's getID3, as shown in the attached issue.

<!-- gh-comment-id:381429502 --> @phanan commented on GitHub (Apr 15, 2018): That's getID3, as shown in the attached issue.
Author
Owner

@phanan commented on GitHub (Apr 15, 2018):

That's very weird.

<!-- gh-comment-id:381429546 --> @phanan commented on GitHub (Apr 15, 2018): That's very weird.
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

it is file.php

<!-- gh-comment-id:381429570 --> @chawker21 commented on GitHub (Apr 15, 2018): it is file.php
Author
Owner

@phanan commented on GitHub (Apr 15, 2018):

I know. Indeed, changing the tag fixed the issue with lyrics not being read. I'll look deeper into this.

<!-- gh-comment-id:381429670 --> @phanan commented on GitHub (Apr 15, 2018): I know. Indeed, changing the tag fixed the issue with lyrics not being read. I'll look deeper into this.
Author
Owner

@phanan commented on GitHub (Apr 15, 2018):

It's very weird that running the integration tests with "unsynchronised_lyric" (correct spelling) will fail.

<!-- gh-comment-id:381429971 --> @phanan commented on GitHub (Apr 15, 2018): It's very weird that running the integration tests with "unsynchronised_lyric" (correct spelling) will _fail_.
Author
Owner

@phanan commented on GitHub (Apr 15, 2018):

@chawker21 If you open vendor/james-heinrich/getid3/getid3/write.id3v2.php at line 1982 and 2057, what do you see?

<!-- gh-comment-id:381431495 --> @phanan commented on GitHub (Apr 15, 2018): @chawker21 If you open `vendor/james-heinrich/getid3/getid3/write.id3v2.php` at line 1982 and 2057, what do you see?
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

It is not just getid3 that uses unsynchronised lyric, when you put the metadata into the audio file with a program that is where "unsynchronised" comes from, getID3 is a middleman.

<!-- gh-comment-id:381443025 --> @chawker21 commented on GitHub (Apr 15, 2018): It is not just getid3 that uses unsynchronised lyric, when you put the metadata into the audio file with a program that is where "unsynchronised" comes from, getID3 is a middleman.
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

From my experience debugging this, the id3 tag comes from the program you input the metadata in with, I use adobe audition. when you do a dump on the id3 data it is that data that the metadata is assigned to. getID3 analyzes the metadata but I dont think that the strings you see in that id3v2 table are actually meaningful to the program they are just sort of a directory of common keys. the real tag is assigned to the file itself.

<!-- gh-comment-id:381443486 --> @chawker21 commented on GitHub (Apr 15, 2018): From my experience debugging this, the id3 tag comes from the program you input the metadata in with, I use adobe audition. when you do a dump on the id3 data it is that data that the metadata is assigned to. getID3 analyzes the metadata but I dont think that the strings you see in that id3v2 table are actually meaningful to the program they are just sort of a directory of common keys. the real tag is assigned to the file itself.
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

when doing a pdf i can assign any key value tag I want to using adobe acrobat. but it is tied to the file not the package I use to analyze it.

<!-- gh-comment-id:381443597 --> @chawker21 commented on GitHub (Apr 15, 2018): when doing a pdf i can assign any key value tag I want to using adobe acrobat. but it is tied to the file not the package I use to analyze it.
Author
Owner

@phanan commented on GitHub (Apr 15, 2018):

Yeah, I noticed that as well. Looks like different applications write tags
differently (I tried iTunes and kid3 personally). Maybe we should check
both.

chawker21 notifications@github.com schrieb am Mo. 16. Apr. 2018 um 00:34:

From my experience debugging this, the id3 tag comes from the program you
input the metadata in with, I use adobe audition. when you do a dump on the
id3 data it is that data that the metadata is assigned to. getID3 analyzes
the metadata but I dont think that the strings you see in that id3v2 table
are actually meaningful to the program they are just sort of a directory of
common keys. the real tag is assigned to the file itself.


You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/716#issuecomment-381443486, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHrt0smJtjxPk5T3fAcB1wvWoAyur9EIks5to8sGgaJpZM4R0Nky
.

<!-- gh-comment-id:381443643 --> @phanan commented on GitHub (Apr 15, 2018): Yeah, I noticed that as well. Looks like different applications write tags differently (I tried iTunes and kid3 personally). Maybe we should check both. chawker21 <notifications@github.com> schrieb am Mo. 16. Apr. 2018 um 00:34: > From my experience debugging this, the id3 tag comes from the program you > input the metadata in with, I use adobe audition. when you do a dump on the > id3 data it is that data that the metadata is assigned to. getID3 analyzes > the metadata but I dont think that the strings you see in that id3v2 table > are actually meaningful to the program they are just sort of a directory of > common keys. the real tag is assigned to the file itself. > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub > <https://github.com/phanan/koel/issues/716#issuecomment-381443486>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AHrt0smJtjxPk5T3fAcB1wvWoAyur9EIks5to8sGgaJpZM4R0Nky> > . >
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

it is a spelling error in getid3 no doubt but it is irrelevant other than you have used their spelling.

<!-- gh-comment-id:381443702 --> @chawker21 commented on GitHub (Apr 15, 2018): it is a spelling error in getid3 no doubt but it is irrelevant other than you have used their spelling.
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

yes Id3 is not nearly all the metadata either, there are a lot of other metadata types. getid3 is mainly for audio tags, for PDF I have to use smalot/pdfparser for those tags, it works similar but there is no way for me to assign lyrics to a pdf, I have to include an audio file with different getid3 tags.

<!-- gh-comment-id:381443988 --> @chawker21 commented on GitHub (Apr 15, 2018): yes Id3 is not nearly all the metadata either, there are a lot of other metadata types. getid3 is mainly for audio tags, for PDF I have to use smalot/pdfparser for those tags, it works similar but there is no way for me to assign lyrics to a pdf, I have to include an audio file with different getid3 tags.
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

I cant use getid3 to read pdf tags.

<!-- gh-comment-id:381444061 --> @chawker21 commented on GitHub (Apr 15, 2018): I cant use getid3 to read pdf tags.
Author
Owner

@chawker21 commented on GitHub (Apr 15, 2018):

Lyrics is a nice tag because I can save a whole text file in it.

<!-- gh-comment-id:381444320 --> @chawker21 commented on GitHub (Apr 15, 2018): Lyrics is a nice tag because I can save a whole text file in it.
Author
Owner

@kevincaradant commented on GitHub (Dec 9, 2021):

Hi

I recently added musics with lyrics using beets. I can see via VLC the metadata with lyrics:

image

But I don't see any lyrics on Koel :(

image

Of the course I realized a scan / sync but nothing :/

Do you any idea why ?

Thank you

<!-- gh-comment-id:989345836 --> @kevincaradant commented on GitHub (Dec 9, 2021): Hi I recently added musics with lyrics using beets. I can see via VLC the metadata with lyrics: ![image](https://user-images.githubusercontent.com/6093175/145313397-6153d7f9-a10a-4d21-9489-cdc7d115b671.png) But I don't see any lyrics on Koel :( ![image](https://user-images.githubusercontent.com/6093175/145313669-e7e29d2e-3099-46fc-a5d1-97197718eb1e.png) Of the course I realized a scan / sync but nothing :/ Do you any idea why ? Thank you
Author
Owner

@phanan commented on GitHub (Dec 10, 2021):

@kevincaradant can you send me the song in question?

<!-- gh-comment-id:990779648 --> @phanan commented on GitHub (Dec 10, 2021): @kevincaradant can you send me the song in question?
Author
Owner

@kevincaradant commented on GitHub (Dec 10, 2021):

Hi
This is the example: https://gofile.io/d/WlQnAi
Regards

Edit: @phanan did you try ? :)

<!-- gh-comment-id:991243442 --> @kevincaradant commented on GitHub (Dec 10, 2021): Hi This is the example: https://gofile.io/d/WlQnAi Regards Edit: @phanan did you try ? :)
Author
Owner

@phanan commented on GitHub (Dec 27, 2021):

@kevincaradant Sorry, holiday time over here :P But yeah, turns out it was a very stupid bug introduced recently with my "refactoring."

<!-- gh-comment-id:1001772725 --> @phanan commented on GitHub (Dec 27, 2021): @kevincaradant Sorry, holiday time over here :P But yeah, turns out it was a very stupid bug introduced recently with my "refactoring."
Author
Owner

@phanan commented on GitHub (Dec 27, 2021):

@kevincaradant Tagged a new release: https://github.com/koel/koel/releases/tag/v5.1.11.

<!-- gh-comment-id:1001782484 --> @phanan commented on GitHub (Dec 27, 2021): @kevincaradant Tagged a new release: https://github.com/koel/koel/releases/tag/v5.1.11.
Author
Owner

@kevincaradant commented on GitHub (Dec 29, 2021):

@phanan , ok thank you :D, but it is possible to have the docker updated with your release ?
https://hub.docker.com/r/hyzual/koel/tags

Thank you

<!-- gh-comment-id:1002329566 --> @kevincaradant commented on GitHub (Dec 29, 2021): @phanan , ok thank you :D, but it is possible to have the docker updated with your release ? https://hub.docker.com/r/hyzual/koel/tags Thank you
Author
Owner

@phanan commented on GitHub (Dec 29, 2021):

Pinging @Hyzual

<!-- gh-comment-id:1002354722 --> @phanan commented on GitHub (Dec 29, 2021): Pinging @Hyzual
Author
Owner

@Hyzual commented on GitHub (Dec 30, 2021):

Hi, I was about to bump the docker image but I run into #1397 for both v5.1.10 and v5.1.11. koel crashes to error 500 immediately because it cannot find mix-manifest.json file (and the related frontend assets) in the public/ folder.
@phanan could you please publish a v5.1.12 including the frontend assets ? I'll push a new docker image version with it.

<!-- gh-comment-id:1003079832 --> @Hyzual commented on GitHub (Dec 30, 2021): Hi, I was about to bump the docker image but I run into #1397 for both v5.1.10 and v5.1.11. koel crashes to error 500 immediately because it cannot find `mix-manifest.json` file (and the related frontend assets) in the `public/` folder. @phanan could you please publish a v5.1.12 including the frontend assets ? I'll push a new docker image version with it.
Author
Owner

@phanan commented on GitHub (Dec 30, 2021):

Will do once I get home ;)

On Thu 30. Dec 2021 at 16:37 Joris MASSON @.***> wrote:

Hi, I was about to bump the docker image but I run into #1397
https://github.com/koel/koel/issues/1397 for both v5.1.10 and v5.1.11.
koel crashes to error 500 immediately because it cannot find
mix-manifest.json file (and the related frontend assets) in the public/
folder.
@phanan https://github.com/phanan could you please publish a v5.1.12
including the frontend assets ? I'll push a new docker image version with
it.


Reply to this email directly, view it on GitHub
https://github.com/koel/koel/issues/716#issuecomment-1003079832, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5O3UUDWDJ6PP2SQJIKVWTUTR4CRANCNFSM4EOQ3EZA
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:1003087281 --> @phanan commented on GitHub (Dec 30, 2021): Will do once I get home ;) On Thu 30. Dec 2021 at 16:37 Joris MASSON ***@***.***> wrote: > Hi, I was about to bump the docker image but I run into #1397 > <https://github.com/koel/koel/issues/1397> for both v5.1.10 and v5.1.11. > koel crashes to error 500 immediately because it cannot find > mix-manifest.json file (and the related frontend assets) in the public/ > folder. > @phanan <https://github.com/phanan> could you please publish a v5.1.12 > including the frontend assets ? I'll push a new docker image version with > it. > > — > Reply to this email directly, view it on GitHub > <https://github.com/koel/koel/issues/716#issuecomment-1003079832>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB5O3UUDWDJ6PP2SQJIKVWTUTR4CRANCNFSM4EOQ3EZA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@phanan commented on GitHub (Dec 30, 2021):

@Hyzual et al., can you try https://github.com/koel/koel/releases/tag/v5.1.12?

<!-- gh-comment-id:1003151907 --> @phanan commented on GitHub (Dec 30, 2021): @Hyzual et al., can you try https://github.com/koel/koel/releases/tag/v5.1.12?
Author
Owner

@Hyzual commented on GitHub (Dec 30, 2021):

Thanks for the new release, it runs but while testing I stumbled upon a database issue when syncing music, I've filled an issue at #1400

<!-- gh-comment-id:1003183604 --> @Hyzual commented on GitHub (Dec 30, 2021): Thanks for the new release, it runs but while testing I stumbled upon a database issue when syncing music, I've filled an issue at #1400
Author
Owner

@Hyzual commented on GitHub (Dec 30, 2021):

The error was due to my environment. The docker image build for v5.1.12 is running, should be pushed shortly

<!-- gh-comment-id:1003200197 --> @Hyzual commented on GitHub (Dec 30, 2021): The error was due to my environment. The docker image build for v5.1.12 is running, should be pushed shortly
Author
Owner

@kevincaradant commented on GitHub (Jan 2, 2022):

It's working thank you

<!-- gh-comment-id:1003732070 --> @kevincaradant commented on GitHub (Jan 2, 2022): It's working thank you
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#509
No description provided.