comment on

After some discussion in the CB, let's look at the facts...

$mp3->set_v1tag() returns true
$mp3->error() is returning {album => 2 }
$mp3->get_v1tag() returns an empty hashref

Looking at the doc's for MP3::Mplib, there are various constants used for the error codes, which are available in mplib.h. From this define,

#define MP_EFNF 2
[download]

the modules saying that "album" is not a valid tag for v1. A look at the XS code for the module give the answer pretty quickly.

         if (strcmp(key, "ALBUM") == 0) {
            content = mp_assemble_text_content(val, enc);
            if ((err = mp_set_content(new_tag, MP_ALBUM, content)) != 
+0)
                sv_catpvf(mp3_lib_err, "%s\034%i", "ALBUM", err);
            continue;
        }
[download]

Try switching your tags to uppercase and see what happens. The code is looking for all uppercase hash keys and there doesn't seem to be any code attempting to uppercase the hash keys at all.

In reply to Re: Re: Re: Cannot write changes to file using MP3::Mplib through CGI by Steve_p
in thread Cannot write changes to file using MP3::Mplib through CGI by Ryszard

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks