I have some mp3 files burned on cds and dvds (some zipped or rared) then don't have tags. there's a way to make it aspect to be an tagged file, to improve the playlist esthetics, even then I use UI Panels, and non-taged files makes lot of '?' on screen.
I remember then it was possible with fb2k 0.8.3, when I change tags from a read-only file, or an packed file, the playlist take taged, but the files stayed untouched.
sorry for my poor english
Thanks anything.
Full Version: "Tag" files without modify files
I already have it, but I dont knew then it would make it, but how I configure it to do what I want.
Thanks
Edit: I tried it here, but appear dont work for %TITLE% and dont work when file already have a tag for that field. I've succeed with %WWW%, %ARTIST% and %ALBUM% fields.
Thanks
Edit: I tried it here, but appear dont work for %TITLE% and dont work when file already have a tag for that field. I've succeed with %WWW%, %ARTIST% and %ALBUM% fields.
Yes, this was possible in 0.8, requested for 0.9 countless times, and there is no sign will come back.
I cannot help you with foo_custominfo, but you could try $meta(title).
I cannot help you with foo_custominfo, but you could try $meta(title).
dont work too
This is the reason why i still use 0.8.3. Don't know why 'block tag update operation' was excluded from 0.9. Very useful feature for me.
As it has been explained many times, it was a bug, not a feature.
When you modified tags in 0.8, changes were always written to foobar2000's database even if the files had not been updated successfully, for example due to "Block tag updates" being enabled, or the files being read-only. Some people misleadingly perceived this as a "database tags" feature.
Edit: Found a post by Peter about why he is not going to add an option to block tag updates:
When you modified tags in 0.8, changes were always written to foobar2000's database even if the files had not been updated successfully, for example due to "Block tag updates" being enabled, or the files being read-only. Some people misleadingly perceived this as a "database tags" feature.
Edit: Found a post by Peter about why he is not going to add an option to block tag updates:
QUOTE(Peter @ Mar 1 2006, 00:08) 
Adding a tag update block option won't prevent malicious / badly written components from altering your files anyway, at least as long as all components are native code and not sandboxed inside a .NET virtual machine or something like that (which won't happen anytime soon for multiple reasons).
Adding a special switch to keep users from shooting themselves in the foot is a step backwards; people's components should be designed in a way that makes it obvious at which point tag updates take place, and give an option to cancel the operation before any harm is done.
Adding a special switch to keep users from shooting themselves in the foot is a step backwards; people's components should be designed in a way that makes it obvious at which point tag updates take place, and give an option to cancel the operation before any harm is done.
I think then it's the best bug ever 
, can someone make a plugin to simulate that bug.
, can someone make a plugin to simulate that bug.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.