culinko: thanks for your bug reports and feedback in the forums
culinko: sorry, I missed you messages yesterday. I frequently fail at synchroneous communication :D
culinko
no problem, you are the one we should be thanking though :P amazing work on picard!
outsidecontext
I think the issues 1 and 2 should be fixed with the patches, but I will test the reload issue again with your new information. we might have multiple causes for this
culinko
you mean 1 and 3, right?
2 is a bug in mp3tag
outsidecontext
sorry, yes, 1 and 3 I meant (reload issue and cover art naming)
culinko
i have no clue how the \n slipped into my CA save settings
outsidecontext
yes, that mp3tag behavior is unexpected. I always used "Extended tags...", and this cause it to write all uppercase
culinko
probably a unintentional whitespace that has been converted by going from Picard 1.4 to 2.0?
outsidecontext
regarding the \n: I could reproduce this partly, copying and pasting a newline to the field preserved it. but for me this did not cause issues on saving, it just was not present in the files. this is on win10
culinko
im on win7 so it might be that
outsidecontext
but anyway, the patch fixes this. actually we already dealt with this for file naming of the audio files, it was just that we used different code for cover art files. that is now the same
PICARD-1101: Read & write the ID3 tag fields in all caps
culinko
is it correct for acoustid tag to be TXXX:Acoustid Id and not TXXX:ACOUSTID ID?
and is this an official mb tag or not? i mean i know acoustid has always been closely tied to mb but it's its own service
so the tag is being used in other software etc.
basically i am wondering if i should report it to mp3tag as well
because they use the mb tags correctly in mixed case, but acoustid tag in all caps
outsidecontext
Yes, it should be TXXX:Acoustid Id . My guess is that for other MB specific tags MP3Tag knows about them and treats them special (instead of uppercasing everything as it usually does)
antlarr has quit
culinko: Although there is no official documentation from the AcoustId side on this tag naming the tag was defined and implemented in Picard by luks, the AcoustId developer. So I guess the Picard tag mapping can be seen as official documentation in this regard
culinko
and you don't plan to make it into all caps in the near future, right? :)
outsidecontext
no. as I wrote in the ticket this and the MBID specific tags won't be touched. there is too much software relying on this naming
i just found 3 more mb tags in id3 that aren't properly mapped in mp3tag, will mention them there as well ;)
thefar8[m]
CatQuest: no, it's not (it's a new one)
and I'm no longer able to pick any task anymore :p
CatQuest
:D
thefar8[m]
I was pretty bored while waiting for the interview, so i decided to just add an instrument :D
CatQuest
well it's awesome that oyu're making more instrument tickets outside of gci (you're laso welcoem to reseach any ticket yo usee that is open (if you see an instrument in MusicBrainz that seems it has little information on it - you cna make a "imporove this or that isntrument"))
thefar8[m]
okay
CatQuest
it's cool!
we definitly need more insturments for mindonesia and africa so it's welcome!
from indonesia*
thefar8[m]
anyway, the interview was pretty shocking hahaha
CatQuest
:O
did it go ok?
thefar8[m]
pretty much
CatQuest
oh good!
thefar8[m]
they did ask me about my GPA and my ranking in my school
CatQuest
what was shocking?
thefar8[m]
that one
lol
I got bad ranking on my school
CatQuest
oh no!
thefar8[m]
because my competition in my school is just too difficult
like in span of 50 ranks, the point of difference is only like 1.xx like that xD
CatQuest
that sounds mad
thefar8[m]
at least I'm honest to them xD
yeah it is
CatQuest
honesty is something that it good. for interviews.. cna go boh ways :DD
thefar8[m]
yeah :D
and since I have last year google code in in my CV's achievements, I have to explain what is GCI to them lol
all in all, it's pretty good since it is my first interview :p