1202: reference libFLAC added to wrong fields BUG#5034

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: 1202: reference libFLAC added to wrong fields BUG#5034

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Chambered » Tue Jul 07, 2009 10:39 am

I am a newbie in MM. But I face the same problem with Ver 3.1

I have save the tag and cover in MM. Seems it is ok if I played with MM but I cannot get the tag information when I play the file in player. I cannot delete the information in the "Encoder: reference libFLAC 1.2.1 20071117" it seems have been locked. Because I cannot edit the tag with my players software (my player is iriver). BTW, my file format is FLAC. Can anyone teach me how to get back my tag info in the player. Thanks a lot.

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Dirhael » Tue Jan 06, 2009 10:14 am

Teknojnky wrote:
Dirhael wrote:
Dirhael wrote:So this problem, only with M4A's instead of FLAC, still remains with build 1207...
...and again in 1208. Suppose I'll have to create a new topic, because nobody can possibly be looking at this one considering that there have been nothing done with this problem yet...not even a post saying that it's being worked on.
Hi, there is no need for new topic unless a different issue.

On first post is link to mantis bug tracker. This is primarily where you will find any developer comments and the current status of the issue.

For your convenience, here it is again.

http://www.ventismedia.com/mantis/view.php?id=5034
I did check mantis, but seeing as this bug have had a status as resolved for a couple of builds now I didn't think anything was being done about it. However, reading a comment on the bug tracker by jiri, made today, it looks like something is finally being done about this so thanks for reminding me to check again :)

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Teknojnky » Tue Jan 06, 2009 10:00 am

Dirhael wrote:
Dirhael wrote:So this problem, only with M4A's instead of FLAC, still remains with build 1207...
...and again in 1208. Suppose I'll have to create a new topic, because nobody can possibly be looking at this one considering that there have been nothing done with this problem yet...not even a post saying that it's being worked on.
Hi, there is no need for new topic unless a different issue.

On first post is link to mantis bug tracker. This is primarily where you will find any developer comments and the current status of the issue.

For your convenience, here it is again.

http://www.ventismedia.com/mantis/view.php?id=5034

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Dirhael » Tue Jan 06, 2009 7:56 am

Dirhael wrote:So this problem, only with M4A's instead of FLAC, still remains with build 1207...
...and again in 1208. Suppose I'll have to create a new topic, because nobody can possibly be looking at this one considering that there have been nothing done with this problem yet...not even a post saying that it's being worked on.

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Dirhael » Fri Jan 02, 2009 7:21 am

So this problem, only with M4A's instead of FLAC, still remains with build 1207...

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Peke » Wed Dec 24, 2008 9:42 pm

NOTE: This is not related with bug from topic but like nohitter151 pointed regarding other bug in MM.

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by nohitter151 » Wed Dec 24, 2008 9:30 am

Lowlander wrote:That method is giving some very weird results.

1) Select composer
2) F2
3) Hit delete
4) Click other composer

result is that other composer disappears as well. It also seems that only the first delete sticks as I was eventually able to delete the libFlac composers.
I saw the same thing with the Genre node, perhaps it's affecting other nodes as well -
http://www.ventismedia.com/mantis/view.php?id=5043

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Lowlander » Tue Dec 23, 2008 10:00 pm

That method is giving some very weird results.

1) Select composer
2) F2
3) Hit delete
4) Click other composer

result is that other composer disappears as well. It also seems that only the first delete sticks as I was eventually able to delete the libFlac composers.

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Teknojnky » Tue Dec 23, 2008 8:59 pm

when I click them they don't display any tracks (empty track list), I press f2 then delete to clear them, they are gone until I re-expand the conductor/composer tree's.

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Lowlander » Tue Dec 23, 2008 8:57 pm

What do you do to get the libFlac values back? I deleted them, restarted MediaMonkey and rescanned the tracks, but the values didn't show up for me.

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Teknojnky » Tue Dec 23, 2008 8:32 pm

I noticed I still have reference libflac in my conductor & composer tree's that keep coming back after I try to remove. I've tried maintaining library multiple times as well.

anyone else still finding these in their library?

I am guessing my database is out of wack somehow.

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Dirhael » Mon Dec 22, 2008 6:22 pm

Teknojnky wrote:
Owyn wrote:1203 is released. Is this fixed now?
seems to me like it is, I didn't see anything added now.
It appears to be fixed for FLAC, but the problem remains with MP4's...

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Teknojnky » Thu Dec 18, 2008 10:57 am

Owyn wrote:1203 is released. Is this fixed now?
seems to me like it is, I didn't see anything added now.

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Owyn » Thu Dec 18, 2008 6:24 am

1203 is released. Is this fixed now?

Re: 1202: reference libFLAC added to wrong fields BUG#5034

by Owyn » Tue Dec 16, 2008 2:00 pm

Teknojnky wrote:Any idea when 1203+ will be posted? Working around/fixing this issue is becoming quite a chore.
Hopefully soon. There is another nasty regression (5037) which has just been fixed.

Top