Nabble - taglib-devel

small grammar fix for front page

2009-12-06T16:01:00Z

Here's a small grammar fix for front page:

TagLib is extensible - TagLib does not implement every feature of ID3v2, but does instead mades it possible for application authors to extend TagLib to support the specific features that they need in their applications.

replace "mades" with "makes"

Cheer's,
Pierre

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Creating FileRef object from QString

2009-12-06T03:08:15Z

I guess that's the correct fix to the existing QStringToTString() function.
But FileRef cannot take a TString object as an argument. So, I cannot use that function itself.

Instead, I'm using what is given in the function itself, i.e. s.toUtf8().data() which works perfectly as an argument to FileRef.

Thanks,
Plasty.

2009/12/6 Ιντζόγλου Θεόφιλος <int.teo@...>

I can't really remember where I got it from but I have the above lines in a
header file:

/*!
* \relates TagLib::String
*
* Converts a TagLib::String to a QString without a requirement to link to Qt.
*/
#define Q4StringToTString(s) TagLib::String(s.toUtf8().data(),
TagLib::String::UTF8)

So all you need to use is Q4StringToTString(). It works just fine here. Hope ti
helps!

Theofilos Intzoglou

Στις Κυριακή 06 Δεκεμβρίου 2009 12:39:37 Plasty Grove γράψατε:

> You're right about FileRef taking only const char *, and yes
> QStringToTString doesn't help. But in addition, the function doesn't work.
> I don't know if it's with the new qt libraries (I'm using 4.5.2). I took a
> look at the macro definition for the function and it looks outdated. viz.
>
> #define QStringToTString(s) TagLib::String(s.utf8().data(),
> TagLib::String::UTF8)
>
> QString no longer has a utf8() function.
>
> But there is one thing I took away from this function that seems to work in
> addition to toAscii() and that's toUtf8().data().
>
> For some reason toUtf8().constData() doesn't work, but toUtf8().data()
> works.
>
> i.e.
>
> TagLib::FileRef tagFile(qstr.toUtf8().data());
>
> Would this be a more preferable way to do it than toAscii()?
>
> Thanks,
> Plasty.
>
> PS: I also noticed that both Qt and taglib support utf16, but I tried it
> and it didn't work and also I don't know much about UTF.
>
>
> 2009/12/6 Lukáš Lalinský <lalinsky@...>
>
> > On Sat, Dec 5, 2009 at 10:29 PM, Michael Pyne <mpyne@...> wrote:
> > > On Saturday 05 December 2009 15:25:13 Plasty Grove wrote:
> > >> That makes sense, but even the following doesn't work:
> > >>
> > >> QString qstr = "/home/mydir/music/song.mp3";
> > >> QByteArray qbArray = qstr.toLocal8Bit();
> > >> const char* str = qbArray.constData();
> > >> TagLib::FileRef tagFile(str);
> > >>
> > >> In this case, I've got a local object which stores the value returned
> > >> by toLocal8Bit() and which is in scope when I'm using str. Does
> > >> qbArray get destroyed whenever constData() is called on it? When I'm
> > >> debugging, I
> >
> > can
> >
> > >> still see str holding a value when it goes to the next step.
> > >
> > > Perhaps an encoding issue if you don't use straight US-ASCII for your
> >
> > file
> >
> > > names? In that case if "local8Bit" is not the encoding Taglib is
> >
> > expecting
> >
> > > you'll get weirdness.
> > >
> > > The KDE JuK music manager uses taglib and has TString/QString
> > > conversion
> >
> > code
> >
> > > (and I'm sure Amarok has the same thing) if you want to see how those
> >
> > projects
> >
> > > do it.
> >
> > TagLib::String will not help in this case, because it also represents
> > Unicode string, like QString. FileRef's filename parameter on
> > non-Windows platforms is char*, so you need the actual encoded bytes.
> > In Qt you can use QFile::encodeName(string) to encode the filename the
> > same way Qt does it for file dialogs or other places that interact
> > with the filesystem. This can still fail in some cases (different
> > mounted filesystems using different encodings), but it's the best you
> > can do if you store filenames as Unicode strings.
> >
> > --
> > Lukas Lalinsky
> > lalinsky@...
> > _______________________________________________
> > taglib-devel mailing list
> > taglib-devel@...
> > https://mail.kde.org/mailman/listinfo/taglib-devel
>
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Creating FileRef object from QString

2009-12-06T02:50:43Z

I can't really remember where I got it from but I have the above lines in a
header file:

/*!
* \relates TagLib::String
*
* Converts a TagLib::String to a QString without a requirement to link to Qt.
*/
#define Q4StringToTString(s) TagLib::String(s.toUtf8().data(),
TagLib::String::UTF8)

So all you need to use is Q4StringToTString(). It works just fine here. Hope ti
helps!

Theofilos Intzoglou

Στις Κυριακή 06 Δεκεμβρίου 2009 12:39:37 Plasty Grove γράψατε:

> You're right about FileRef taking only const char *, and yes
> QStringToTString doesn't help. But in addition, the function doesn't work.
> I don't know if it's with the new qt libraries (I'm using 4.5.2). I took a
> look at the macro definition for the function and it looks outdated. viz.
>
> #define QStringToTString(s) TagLib::String(s.utf8().data(),
> TagLib::String::UTF8)
>
> QString no longer has a utf8() function.
>
> But there is one thing I took away from this function that seems to work in
> addition to toAscii() and that's toUtf8().data().
>
> For some reason toUtf8().constData() doesn't work, but toUtf8().data()
> works.
>
> i.e.
>
> TagLib::FileRef tagFile(qstr.toUtf8().data());
>
> Would this be a more preferable way to do it than toAscii()?
>
> Thanks,
> Plasty.
>
> PS: I also noticed that both Qt and taglib support utf16, but I tried it
> and it didn't work and also I don't know much about UTF.
>
>
> 2009/12/6 Lukáš Lalinský <lalinsky@...>
>
> > On Sat, Dec 5, 2009 at 10:29 PM, Michael Pyne <mpyne@...> wrote:
> > > On Saturday 05 December 2009 15:25:13 Plasty Grove wrote:
> > >> That makes sense, but even the following doesn't work:
> > >>
> > >> QString qstr = "/home/mydir/music/song.mp3";
> > >> QByteArray qbArray = qstr.toLocal8Bit();
> > >> const char* str = qbArray.constData();
> > >> TagLib::FileRef tagFile(str);
> > >>
> > >> In this case, I've got a local object which stores the value returned
> > >> by toLocal8Bit() and which is in scope when I'm using str. Does
> > >> qbArray get destroyed whenever constData() is called on it? When I'm
> > >> debugging, I
> >
> > can
> >
> > >> still see str holding a value when it goes to the next step.
> > >
> > > Perhaps an encoding issue if you don't use straight US-ASCII for your
> >
> > file
> >
> > > names? In that case if "local8Bit" is not the encoding Taglib is
> >
> > expecting
> >
> > > you'll get weirdness.
> > >
> > > The KDE JuK music manager uses taglib and has TString/QString
> > > conversion
> >
> > code
> >
> > > (and I'm sure Amarok has the same thing) if you want to see how those
> >
> > projects
> >
> > > do it.
> >
> > TagLib::String will not help in this case, because it also represents
> > Unicode string, like QString. FileRef's filename parameter on
> > non-Windows platforms is char*, so you need the actual encoded bytes.
> > In Qt you can use QFile::encodeName(string) to encode the filename the
> > same way Qt does it for file dialogs or other places that interact
> > with the filesystem. This can still fail in some cases (different
> > mounted filesystems using different encodings), but it's the best you
> > can do if you store filenames as Unicode strings.
> >
> > --
> > Lukas Lalinsky
> > lalinsky@...
> > _______________________________________________
> > taglib-devel mailing list
> > taglib-devel@...
> > https://mail.kde.org/mailman/listinfo/taglib-devel
>

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Creating FileRef object from QString

2009-12-06T02:39:37Z

You're right about FileRef taking only const char *, and yes QStringToTString doesn't help. But in addition, the function doesn't work. I don't know if it's with the new qt libraries (I'm using 4.5.2). I took a look at the macro definition for the function and it looks outdated. viz.

#define QStringToTString(s) TagLib::String(s.utf8().data(), TagLib::String::UTF8)

QString no longer has a utf8() function.

But there is one thing I took away from this function that seems to work in addition to toAscii() and that's toUtf8().data().

For some reason toUtf8().constData() doesn't work, but toUtf8().data() works.

i.e.

TagLib::FileRef tagFile(qstr.toUtf8().data());

Would this be a more preferable way to do it than toAscii()?

Thanks,
Plasty.

PS: I also noticed that both Qt and taglib support utf16, but I tried it and it didn't work and also I don't know much about UTF.

2009/12/6 Lukáš Lalinský <lalinsky@...>

On Sat, Dec 5, 2009 at 10:29 PM, Michael Pyne <mpyne@...> wrote:
> On Saturday 05 December 2009 15:25:13 Plasty Grove wrote:
>> That makes sense, but even the following doesn't work:
>>
>> QString qstr = "/home/mydir/music/song.mp3";
>> QByteArray qbArray = qstr.toLocal8Bit();
>> const char* str = qbArray.constData();
>> TagLib::FileRef tagFile(str);
>>
>> In this case, I've got a local object which stores the value returned by
>> toLocal8Bit() and which is in scope when I'm using str. Does qbArray get
>> destroyed whenever constData() is called on it? When I'm debugging, I can
>> still see str holding a value when it goes to the next step.
>
> Perhaps an encoding issue if you don't use straight US-ASCII for your file
> names? In that case if "local8Bit" is not the encoding Taglib is expecting
> you'll get weirdness.
>
> The KDE JuK music manager uses taglib and has TString/QString conversion code
> (and I'm sure Amarok has the same thing) if you want to see how those projects
> do it.

TagLib::String will not help in this case, because it also represents
Unicode string, like QString. FileRef's filename parameter on
non-Windows platforms is char*, so you need the actual encoded bytes.
In Qt you can use QFile::encodeName(string) to encode the filename the
same way Qt does it for file dialogs or other places that interact
with the filesystem. This can still fail in some cases (different
mounted filesystems using different encodings), but it's the best you
can do if you store filenames as Unicode strings.

--
Lukas Lalinsky
lalinsky@...

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Creating FileRef object from QString

2009-12-06T00:12:43Z

On Sat, Dec 5, 2009 at 10:29 PM, Michael Pyne <mpyne@...> wrote:

> On Saturday 05 December 2009 15:25:13 Plasty Grove wrote:
>> That makes sense, but even the following doesn't work:
>>
>> QString qstr = "/home/mydir/music/song.mp3";
>> QByteArray qbArray = qstr.toLocal8Bit();
>> const char* str = qbArray.constData();
>> TagLib::FileRef tagFile(str);
>>
>> In this case, I've got a local object which stores the value returned by
>> toLocal8Bit() and which is in scope when I'm using str. Does qbArray get
>> destroyed whenever constData() is called on it? When I'm debugging, I can
>> still see str holding a value when it goes to the next step.
>
> Perhaps an encoding issue if you don't use straight US-ASCII for your file
> names? In that case if "local8Bit" is not the encoding Taglib is expecting
> you'll get weirdness.
>
> The KDE JuK music manager uses taglib and has TString/QString conversion code
> (and I'm sure Amarok has the same thing) if you want to see how those projects
> do it.

TagLib::String will not help in this case, because it also represents
Unicode string, like QString. FileRef's filename parameter on
non-Windows platforms is char*, so you need the actual encoded bytes.
In Qt you can use QFile::encodeName(string) to encode the filename the
same way Qt does it for file dialogs or other places that interact
with the filesystem. This can still fail in some cases (different
mounted filesystems using different encodings), but it's the best you
can do if you store filenames as Unicode strings.

--
Lukas Lalinsky
lalinsky@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Creating FileRef object from QString

2009-12-05T23:30:27Z

On Saturday 05 December 2009 23:56:58 Plasty Grove wrote:
> Thanks so much Michael. That's exactly what was needed, straight ASCII
> conversion.
>
> This is what works:
>
> QString qstr = "/home/mydir/music/song.mp3";
> TagLib::FileRef tagFile(qstr.toAscii());
>
> Apologies, I didn't take note of the toAscii() function.

Please keep in mind that this is still broken in like 92% of the world or so.
You will in general need to use /some/ encoding, you just need to make sure
TagLib is using the same one.

I'd recommend UTF8 as it's supported by both TagLib and Qt.

Indeed, I finally took a look at the TagLib String API reference
(http://developer.kde.org/~wheeler/taglib/api/classTagLib_1_1String.html) and
noted that the function you want is already defined:

QStringToTString(s) (in the Related Functions section).

So don't reinvent the wheel, just use QStringToTString

Regards,
- Michael Pyne

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

signature.asc (853 bytes) Download Attachment

Re: Creating FileRef object from QString

2009-12-05T20:56:58Z

Thanks so much Michael. That's exactly what was needed, straight ASCII conversion.

This is what works:

QString qstr = "/home/mydir/music/song.mp3";
TagLib::FileRef tagFile(qstr.toAscii());

Apologies, I didn't take note of the toAscii() function.

Regards,
Abhiram.

On Sun, Dec 6, 2009 at 2:59 AM, Michael Pyne <mpyne@...> wrote:

On Saturday 05 December 2009 15:25:13 Plasty Grove wrote:
> That makes sense, but even the following doesn't work:
>
> QString qstr = "/home/mydir/music/song.mp3";
> QByteArray qbArray = qstr.toLocal8Bit();
> const char* str = qbArray.constData();
> TagLib::FileRef tagFile(str);
>
> In this case, I've got a local object which stores the value returned by
> toLocal8Bit() and which is in scope when I'm using str. Does qbArray get
> destroyed whenever constData() is called on it? When I'm debugging, I can
> still see str holding a value when it goes to the next step.

Perhaps an encoding issue if you don't use straight US-ASCII for your file
names? In that case if "local8Bit" is not the encoding Taglib is expecting
you'll get weirdness.

The KDE JuK music manager uses taglib and has TString/QString conversion code
(and I'm sure Amarok has the same thing) if you want to see how those projects
do it.

If it's not encoding I'm not sure what to try other than stepping through
FileRef in the debugger to see where the logic goes astray.

Regards,
- Michael Pyne

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Creating FileRef object from QString

2009-12-05T13:29:08Z

On Saturday 05 December 2009 15:25:13 Plasty Grove wrote:

> That makes sense, but even the following doesn't work:
>
> QString qstr = "/home/mydir/music/song.mp3";
> QByteArray qbArray = qstr.toLocal8Bit();
> const char* str = qbArray.constData();
> TagLib::FileRef tagFile(str);
>
> In this case, I've got a local object which stores the value returned by
> toLocal8Bit() and which is in scope when I'm using str. Does qbArray get
> destroyed whenever constData() is called on it? When I'm debugging, I can
> still see str holding a value when it goes to the next step.

Perhaps an encoding issue if you don't use straight US-ASCII for your file
names? In that case if "local8Bit" is not the encoding Taglib is expecting
you'll get weirdness.

The KDE JuK music manager uses taglib and has TString/QString conversion code
(and I'm sure Amarok has the same thing) if you want to see how those projects
do it.

If it's not encoding I'm not sure what to try other than stepping through
FileRef in the debugger to see where the logic goes astray.

Regards,
- Michael Pyne

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

signature.asc (853 bytes) Download Attachment

Re: Creating FileRef object from QString

2009-12-05T12:25:13Z

That makes sense, but even the following doesn't work:

QString qstr = "/home/mydir/music/song.mp3";
QByteArray qbArray = qstr.toLocal8Bit();
const char* str = qbArray.constData();

TagLib::FileRef tagFile(str);

In this case, I've got a local object which stores the value returned by toLocal8Bit() and which is in scope when I'm using str. Does qbArray get destroyed whenever constData() is called on it? When I'm debugging, I can still see str holding a value when it goes to the next step.

Thanks,
Plasty.

On Sun, Dec 6, 2009 at 1:18 AM, Michael Pyne <mpyne@...> wrote:

On Saturday 05 December 2009 13:59:35 Plasty Grove wrote:
> Hi,
>
> I'm developing using qt and have a situation where I have to create a
> FileRef object from a QString object.
>
> --------------------------------------------------
> TagLib::FileRef tagFile("/home/mydir/music/song.mp3") //---> Works fine
> --------------------------------------------------
> QString qstr = "/home/mydir/music/song.mp3";
> const char* str = qstr.toLocal8Bit().constData();
> TagLib::FileRef tagFile(str); //---> Doesn't work, shows as empty in
> debugger and segfaults when I try to access
> --------------------------------------------------
>
> What am I doing wrong here?

QString::toLocal8Bit returns a QByteArray, not a const char *.
That QByteArray is destructed once .constData() returns (since there's no
reason for C++ to keep it around).

So now your const char * pointer is dangling in the middle of freed memory,
and you get a crash.

Regards,
- Michael Pyne

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Creating FileRef object from QString

2009-12-05T11:48:05Z

On Saturday 05 December 2009 13:59:35 Plasty Grove wrote:

> Hi,
>
> I'm developing using qt and have a situation where I have to create a
> FileRef object from a QString object.
>
> --------------------------------------------------
> TagLib::FileRef tagFile("/home/mydir/music/song.mp3") //---> Works fine
> --------------------------------------------------
> QString qstr = "/home/mydir/music/song.mp3";
> const char* str = qstr.toLocal8Bit().constData();
> TagLib::FileRef tagFile(str); //---> Doesn't work, shows as empty in
> debugger and segfaults when I try to access
> --------------------------------------------------
>
> What am I doing wrong here?

QString::toLocal8Bit returns a QByteArray, not a const char *.
That QByteArray is destructed once .constData() returns (since there's no
reason for C++ to keep it around).

So now your const char * pointer is dangling in the middle of freed memory,
and you get a crash.

Regards,
- Michael Pyne

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

signature.asc (853 bytes) Download Attachment

Creating FileRef object from QString

2009-12-05T10:59:35Z

Hi,

I'm developing using qt and have a situation where I have to create a FileRef object from a QString object.

--------------------------------------------------
TagLib::FileRef tagFile("/home/mydir/music/song.mp3") //---> Works fine
--------------------------------------------------
QString qstr = "/home/mydir/music/song.mp3";
const char* str = qstr.toLocal8Bit().constData();
TagLib::FileRef tagFile(str); //---> Doesn't work, shows as empty in debugger and segfaults when I try to access
--------------------------------------------------

What am I doing wrong here?

Thanks,
Plasty.

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

about taglib 1.6.1

2009-12-03T18:47:29Z

hi!

there an error when I install the /usr/port/audio/taglib after I update
the ports tree.

===> Checking if audio/taglib already installed
cd: can't cd to /usr/ports/audio/taglib/work/taglib-1.6.1
*** Error code 2

there's the dirs &files under /usr/port/audio/taglib/work/

. .build_done.taglib._usr_local
.. .PLIST.mktmp
taglib-1.5 .PLIST.flattened
.extract_done.taglib._usr_local .PLIST.setuid
.patch_done.taglib._usr_local .PLIST.writable
.configure_done.taglib._usr_local .PLIST.objdump

How to solve it?

Thank you so much :-)

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Extracting embedded picture from FLAC file

2009-12-02T07:43:07Z

I'm interested in this feature too, is there any news on this? I checked
the recent commits but didn't find anything related.

Maybe I should create a feature request in the bug tracker?

Tim De Baets

Peter van Hardenberg wrote:

> We have that implemented here with a patch I'd like to upstream.
>
> I suspect it needs a little bit of tweaking to match upstream style. I'll talk to my coworker who wrote that patch and try to get it posted tomorrow.
>
> -pvh
>
> ----- "Atti" <atti86@...> wrote:
>
>
>> Hey,
>> I'm trying to read the picture block from a .flac file using TagLib,
>> but so far no luck. I've read the FLAC format specs, but I don't know
>> how to access it via TagLib. Is it possible?
>>
>> Thanks,
>> Atti.
>>
>> _______________________________________________
>> taglib-devel mailing list
>> taglib-devel@...
>> https://mail.kde.org/mailman/listinfo/taglib-devel
>>
> _______________________________________________
> taglib-devel mailing list
> taglib-devel@...
> https://mail.kde.org/mailman/listinfo/taglib-devel
>
>

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Strange File

2009-12-02T06:26:54Z

Hi,

when I try to open the following file

http://feeds.feedburner.com/~r/PasteCultureClub/~5/171770886/6.12.07-Paste_Culture_Club.m4a

with MP4Read() I just get back MP4_INVALID_FILE_HANDLE (the file is locally downloaded first, of course).
There's really something strange going on with that file, because the (Mac OS X) Finder just crashes when trying to show the preview for this file.
But iTunes and QuickTime Player do not seem to have any problems with this file, they play it fine and display the tag information.

Maybe there can be found a workaround to handle this type of "suspicious" file in taglib?

(This file is Episode "June 12, 2007" from the Paste Culture Club Podcast available on http://www.pastecultureclub.com/podcasts/m4a/PMCCm4a.xml. Other episodes from this podcast seem to work fine.)

Regards,
Mani

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Changing MP4::Tag ItemListMap

2009-11-29T13:58:16Z

2009/11/28 Новичков А.А. <novichko@...>:

>> Take a look at the MP4::Tag source code. The usual way is something >
>> like:
>>
>> file->tag()->itemListMap()["aART"] = TagLib::StringList("Album artist");
>> file->tag()->itemListMap()["\251wrt"] = TagLib::StringList("Composer");
>>
>> Or, if you want to write a new free-form tag:
>>
>> file->tag()->itemListMap()["----:com.apple.iTunes:foo"] =
>> TagLib::StringList("Some custom tag");
>
> I tried
> map.insert("some key",TagLib::MP4::Item(TagLib::StringList("value")));
> but nothing happened.

What specifically is "some key". Is it a valid MP4 atom name?

> Is it possible to modify MP4::Tag itemListMap taken by reference?

I don't see why not.

> And what does the save() method in the MP4::Tag public methods do?

Saves tags to the file.

> Another problem: when trying to save tags in MP4 file with TagLib extras v.0.1.? (in Ubuntu Jaunty)
> my program crashes with segfault even if I do just
> TagLib::MP4::File *f=new TagLib::MP4::File(filename);
> f->save();

Can you try with plain TagLib? To debug the issue, it's necessary to
see the backtrace.

--
Lukas Lalinsky
lalinsky@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

aac/m4a chapter markers

2009-11-29T12:01:41Z

Hi,

i would like to extract the chapter markers from an m4a file. Is this supported
by taglib?

Thanks.

KR,
Frank
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: taglib with qt-creator

2009-11-28T05:39:37Z

On Nov 28, 2009, at 1:57 PM, Plasty Grove wrote:

> How does this work? Is it similar for other external libraries that
> I'd like to include as well?

It reads the pkgconfig file that's installed along with the library.
Most libraries these days install one in /usr/{local/}lib/pkgconfig/

-Scott
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: taglib with qt-creator

2009-11-28T04:57:07Z

Very cool. It inserted the include lines in the Makefile by itself. How does this work? Is it similar for other external libraries that I'd like to include as well?

Thanks,
Plasty

On Sat, Nov 28, 2009 at 6:09 PM, Scott Wheeler <wheeler@...> wrote:

On Nov 28, 2009, at 8:15 AM, Plasty Grove wrote:

>
> In qt-creator, these values can be set by editing the .pro file of
> your project and adding in the following variables:
>
> QMAKE_CXXFLAGS += -I /usr/include/taglib -I /usr/include/taglib-extras
> QMAKE_LIBS += -ltag

I hadn't really messed with Qt Creator, so I didn't know how it was
set up -- but actually if it just uses .pro files it's even easier:

CONFIG += link_pkgconfig
PKGCONFIG += taglib taglib-extras

-Scott
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: taglib with qt-creator

2009-11-28T04:39:14Z

On Nov 28, 2009, at 8:15 AM, Plasty Grove wrote:

>
> In qt-creator, these values can be set by editing the .pro file of
> your project and adding in the following variables:
>
> QMAKE_CXXFLAGS += -I /usr/include/taglib -I /usr/include/taglib-extras
> QMAKE_LIBS += -ltag

I hadn't really messed with Qt Creator, so I didn't know how it was
set up -- but actually if it just uses .pro files it's even easier:

CONFIG += link_pkgconfig
PKGCONFIG += taglib taglib-extras

-Scott
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: taglib with qt-creator

2009-11-27T23:15:33Z

Ok, I seem to have got this figured out. We need to include the location of the header files in the compiler options. Effectively we need to have something like

g++ something something -I /usr/include/taglib yada yada.

i.e. in the Makefile. We also need to have -ltag included as a link.

Effectively, in the Makefile, this is what it translates to:

CXXFLAGS = -pipe -I /usr/include/taglib -I /usr/include/taglib-extras -g -D_REENTRANT -Wall -W $(DEFINES)
LIBS = $(SUBLIBS) -L/usr/lib -ltag -lQtGui -lQtCore -lpthread

(note the -ltag in the LIBS variable, taglib-extras in CXXFLAGS might not be required)

and if you compile it now with make, you'll find everything compiling fine.

In qt-creator, these values can be set by editing the .pro file of your project and adding in the following variables:

QMAKE_CXXFLAGS += -I /usr/include/taglib -I /usr/include/taglib-extras
QMAKE_LIBS += -ltag

This will make the necessary modifications to the Makefile when you build the project.

I hope someone finds this useful. It took me a day of googling, searching on ubuntu forums and a helpful dev at #qt-creator on freenode to figure this out.

Cheers!
Plasty

On Fri, Nov 27, 2009 at 12:22 AM, Plasty Grove <plasty.grove@...> wrote:

Hi all,

I'm unable to figure out how to set the taglib include directory with my project in qt-creator. I've tried setting the CXXFLAGS option to -I /usr/include/taglib and also tried CFLAGS under the build config. But it's just refusing to build. Can someone please help me out with this?

Thanks!
Plasty

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Changing MP4::Tag ItemListMap

2009-11-27T23:04:24Z

> Take a look at the MP4::Tag source code. The usual way is something >
> like:
>
> file->tag()->itemListMap()["aART"] = TagLib::StringList("Album artist");
> file->tag()->itemListMap()["\251wrt"] = TagLib::StringList("Composer");
>
> Or, if you want to write a new free-form tag:
>
> file->tag()->itemListMap()["----:com.apple.iTunes:foo"] =
> TagLib::StringList("Some custom tag");

I tried
map.insert("some key",TagLib::MP4::Item(TagLib::StringList("value")));
but nothing happened.

Is it possible to modify MP4::Tag itemListMap taken by reference?
And what does the save() method in the MP4::Tag public methods do?

Another problem: when trying to save tags in MP4 file with TagLib extras v.0.1.? (in Ubuntu Jaunty)
my program crashes with segfault even if I do just
TagLib::MP4::File *f=new TagLib::MP4::File(filename);
f->save();

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Changing MP4::Tag ItemListMap

2009-11-27T08:57:34Z

2009/11/27 Новичков А.А. <novichko@...>:
> Hi, I have a question. How can I write some non-standard tag into mp4
> file? The class MP4::Tag doesn't have any methods for it.

Take a look at the MP4::Tag source code. The usual way is something like:

file->tag()->itemListMap()["aART"] = TagLib::StringList("Album artist");
file->tag()->itemListMap()["\251wrt"] = TagLib::StringList("Composer");

Or, if you want to write a new free-form tag:

file->tag()->itemListMap()["----:com.apple.iTunes:foo"] =
TagLib::StringList("Some custom tag");

--
Lukas Lalinsky
lalinsky@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Changing MP4::Tag ItemListMap

2009-11-27T08:03:47Z

Hi, I have a question. How can I write some non-standard tag into mp4
file? The class MP4::Tag doesn't have any methods for it.

Alex

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

taglib with qt-creator

2009-11-26T10:52:35Z

Hi all,

I'm unable to figure out how to set the taglib include directory with my project in qt-creator. I've tried setting the CXXFLAGS option to -I /usr/include/taglib and also tried CFLAGS under the build config. But it's just refusing to build. Can someone please help me out with this?

Thanks!
Plasty
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Album Art using Taglib

2009-11-26T01:17:31Z

On Nov 26, 2009, at 6:59 AM, pranay prateek wrote:

> Hi all
> I am trying to use TagLib to extract album art from audio files. I
> am building this app for WINCE 6.0 using c++ and Visual Studio 2005
> IDE. [...]

I just ran your code on a couple hundred files and it worked fine.
From what I can tell there are one of two possibilities:

- This is a misconfiguration in your compiler / tool-chain, which you
probably won't get much help with here since the overwhelming majority
of the people on this list work on Linux or Mac.

- You've run into some files which are triggering taglib bugs. If
you've got one file that always crashes taglib, feel free to send it
to me privately and I'll see if I can reproduce the issue.

-Scott
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Album Art using Taglib

2009-11-25T22:15:33Z

In continuation to the previous mail,

i forgot to mention that my code crashes in the first line itself,

TagLib::MPEG::File mpegFile("\\Storage Card\\YeDooriyan.mp3");

i.e. it is not able to create an object of the type MPEG::File.

On Thu, Nov 26, 2009 at 11:29 AM, pranay prateek <pranay.iitm@...> wrote:

Hi all
I am trying to use TagLib to extract album art from audio files. I am building this app for WINCE 6.0 using c++ and Visual Studio 2005 IDE.

As of now, i am just trying to test it on mp3 files. If i include all the files from mpeg, toolkit and ape folders, i am able to compile my project.
But, at runtime it gives an unhandled exception error for some mp3 files, while it runs fine for other mp3 files.

The unhandled exception occurs at

ref() function in RefCounter class

called by

ByteVector::ByteVector(const ByteVector &v) : d(v.d)

{
   d->ref();
}

It seems the this pointer in the ref function called is NULL which is seemingly causing the problem.

My main issue is how is this working for some MP3 files while not working for others? Does it depend upon some parameter present in MP3

files which may not be present in other MP3 files?
Also, i searched the documentation but couldn't find out what actually is the RefCounter class doing. Why is it being called so many times?

Can somebody give me pointers on how this issue could be resolved?
Thanks.

Regards
Pranay

My code is something like this:

int main()
{

static const char *IdPicture = "APIC" ;

TagLib::MPEG::File mpegFile("\\Storage Card\\YeDooriyan.mp3");

TagLib::ID3v2::Tag *id3v2tag = mpegFile.ID3v2Tag();
TagLib::ID3v2::FrameList Frame ;

TagLib::ID3v2::AttachedPictureFrame *PicFrame ;
void *RetImage = NULL, *SrcImage ;

unsigned long Size ;

FILE *jpegFile;
fopen_s(&jpegFile,"FromId3.jpg","wb");

  if ( id3v2tag )
  {
   // picture frame
   Frame = id3v2tag->frameListMap()[IdPicture] ;

   if (!Frame.isEmpty() )
   {
   // find cover art
for(TagLib::ID3v2::FrameList::ConstIterator it = Frame.begin(); it !=
Frame.end(); ++it)
   {
PicFrame = (TagLib::ID3v2::AttachedPictureFrame *)(*it) ;
   if ( PicFrame->type() == TagLib::ID3v2::AttachedPictureFrame::FrontCover)

   {
   // extract image (in it's compressed form)
   Size = PicFrame->picture().size() ;
   SrcImage = malloc ( Size ) ;
   if ( SrcImage )

   {
   memcpy ( SrcImage, PicFrame->picture().data(), Size ) ;
fwrite(SrcImage,Size,1, jpegFile);
fclose(jpegFile);


   free( SrcImage ) ;
   }
   if ( RetImage )
   break ;
   }

   }
   }
  }
return(0);

}

--
"You aren't remembered for doing what is expected of you."

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Album Art using Taglib

2009-11-25T21:59:57Z

Hi all

I am trying to use TagLib to extract album art from audio files. I am building this app for WINCE 6.0 using c++ and Visual Studio 2005 IDE.

As of now, i am just trying to test it on mp3 files. If i include all the files from mpeg, toolkit and ape folders, i am able to compile my project.

But, at runtime it gives an unhandled exception error for some mp3 files, while it runs fine for other mp3 files.

The unhandled exception occurs at

ref() function in RefCounter class

called by

ByteVector::ByteVector(const ByteVector &v) : d(v.d)

{

d->ref();

}

It seems the this pointer in the ref function called is NULL which is seemingly causing the problem.

My main issue is how is this working for some MP3 files while not working for others? Does it depend upon some parameter present in MP3

files which may not be present in other MP3 files?

Also, i searched the documentation but couldn't find out what actually is the RefCounter class doing. Why is it being called so many times?

Can somebody give me pointers on how this issue could be resolved?

Thanks.

Regards

Pranay

My code is something like this:

int main()

{

static const char *IdPicture = "APIC" ;

TagLib::MPEG::File mpegFile("\\Storage Card\\YeDooriyan.mp3");

TagLib::ID3v2::Tag *id3v2tag = mpegFile.ID3v2Tag();

TagLib::ID3v2::FrameList Frame ;

TagLib::ID3v2::AttachedPictureFrame *PicFrame ;

void *RetImage = NULL, *SrcImage ;

unsigned long Size ;

FILE *jpegFile;

fopen_s(&jpegFile,"FromId3.jpg","wb");

if ( id3v2tag )

{

// picture frame

Frame = id3v2tag->frameListMap()[IdPicture] ;

if (!Frame.isEmpty() )

{

// find cover art

for(TagLib::ID3v2::FrameList::ConstIterator it = Frame.begin(); it !=

Frame.end(); ++it)

{

PicFrame = (TagLib::ID3v2::AttachedPictureFrame *)(*it) ;

if ( PicFrame->type() == TagLib::ID3v2::AttachedPictureFrame::FrontCover)

{

// extract image (in it's compressed form)

Size = PicFrame->picture().size() ;

SrcImage = malloc ( Size ) ;

if ( SrcImage )

{

memcpy ( SrcImage, PicFrame->picture().data(), Size ) ;

fwrite(SrcImage,Size,1, jpegFile);

fclose(jpegFile);

free( SrcImage ) ;

}

if ( RetImage )

break ;

}

return(0);

}

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Using TagLib with VS2005

2009-11-22T23:25:03Z

On Nov 22, 2009, at 9:35 PM, pranay prateek wrote:

> In tlist.h, its written that tlist.tcc is included only because
> there is no export function in gcc. Since, i am using VS2005 is it
> possible that
> i can do without the .tcc? If you people have nay suggestion, kindly
> reply.Am bit of stuck on this.

Virtually no compiler (Visual Studio included) supports the feature
that's required there; at the time I wrote that comment I didn't
realize that.

-Scott
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Using TagLib with VS2005

2009-11-22T12:35:40Z

Hi all

I am trying to use TagLib to extract album art from audio files. I am building this app for WINCE 6.0 using c++ and Visual Studio 2005 IDE.

As of now, i am just trying to test it on an mp3 file. If i include all the files from mpeg, toolkit and ape folders, i am able to compile my project.

But, at runtime the it gives an unhandled exception error.

My main code is simply:

int main()

{

TagLib::FileRef f("\\Storage Card\\YeDooriyan.mp3");

return(0);

}

On closer look it seems that the error actually occurs in create function of FileRef.

The code crashes on this line:

List<const FileTypeResolver *>::ConstIterator it = FileRefPrivate::fileTypeResolvers.begin();

It seems the detach() function in tlist.tcc is being called without being initialised in the first place.

In tlist.h, its written that tlist.tcc is included only because there is no export function in gcc. Since, i am using VS2005 is it possible that

i can do without the .tcc? If you people have nay suggestion, kindly reply.Am bit of stuck on this.

I am newbie in c++ programming, hence am not very converse with the technicalities of compiler.

Regards

Pranay

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Some questions regarding Album Art picture field

2009-11-20T09:51:04Z

Hi, it seems that taglib supports read/write the album art metadata fields and I wonder what are the supported types ( linked or embedded ?).

Is is possible to use taglib to extract pictures from an audio file which has embedded album art?

I have read the document and I know that the TagLib::ID3v2::AttachedPictureFrame Class should be used for the handling of ID3v2 album art fields,
but what about the other metadata types (e.g apev2, wma, mpeg4), what are the corresponding fields?
I have done some simple tests, the Windows Media Player seems to use the "WM/Picture" field.

Please give some suggestions.

--
Best Regards

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: [Fwd: [Bug 200596] [Patch] id3v1 japanese characters encoding]

2009-11-16T10:52:53Z

On 2009-11-15 1:58 PM, Jeff Mitchell wrote:

> Hello,
>
> We've had some trouble with character set detection that Cesar has
> managed to narrow down to TagLib stripping the Unicode BOM from its
> strings -- see the attached message, and if you need more background the
> last few comments of the associated bug report. Would it be possible to
> provide one of these two solutions?
>
> Thanks,
> Jeff
>
>

For reference, Songbird has a local patch to do B) - it exposes whether
the string was constructed with the Latin1 or one of the Unicode types.
That's an API change, of course, so it probably wouldn't be valid for
upstream until 2.0.

TagLib::String::isLatin1() can be used for now, but will still get you
false positives because it _is_ valid to have metadata that happens to
be Unicode, contains non-ASCII Latin1, and will be misdetected. At
least, I don't trust my charset detector that much :)

(The patch is http://timeline.songbirdnest.com/vendor/changeset/10855
which doesn't make much sense until you realize we had a previous patch
in http://timeline.songbirdnest.com/vendor/changeset/10852 which felt
suckier.)

--
Mook
mook@songbirdnest
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

[Fwd: [Bug 200596] [Patch] id3v1 japanese characters encoding]

2009-11-15T13:58:01Z

Hello,

We've had some trouble with character set detection that Cesar has
managed to narrow down to TagLib stripping the Unicode BOM from its
strings -- see the attached message, and if you need more background the
last few comments of the associated bug report. Would it be possible to
provide one of these two solutions?

Thanks,
Jeff

https://bugs.kde.org/show_bug.cgi?id=200596

--- Comment #31 from Cesar Garcia <cesarg9 gmail com> 2009-11-15 18:05:11 ---
I dont know really if the problem is more of taglib or amarok. Seeing the code
of the ::prepare func in taglib/toolkit/tstring.cpp, it strips the unicode BOM
if it finds one, making the charset-detector useless (because it needs the BOM
to identify the string as UTF) then returning a random encoding. The solution
IMO is:

A) making taglib to return the untouched version of the string tag (with the
BOM if it have one) to make the charset-detector more reliable (probably not
the best solution as this changes the expected behaviour in other apps than
uses taglib)

B) that taglib provides a function to check if the original string was an UTF
one (8 or 16) so amarok can skip the charset-detector when isnt needed. I am
already doing this with the patch that i provided: the isLatin1 func of taglib
merely tests if the string isnt unicode (all chars < 256), so amarok can choose
to skip the charset-detector.

P.D.: there is a almost duplicate code of the collectionbrowser in
src/meta/file/File_p.h (around line 227) that i dont know if it can trigger
this bug in another part of amarok.

Sorry for my english.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

signature.asc (203 bytes) Download Attachment

Re: Issue copying IDv2 TCON frames with a v1 genre reference

2009-11-13T16:01:02Z

Op 13 nov 2009, om 23:33 heeft Michael Smith het volgende geschreven:

>> I'm building my own TagLib framework, but I've done nothing special to disable the iTunes hacks. Or should I actively enable them? I'll look into it.
>
> I believe they're on by default.

The iTunes hack in TagLib didn't help me because it is in the setGenre() accessor. My copy routine moves frames directy between tags, bypassing the accessor. I'll keep using setGenre() now until the day iTunes gets fixed...

Thanks to everyone who chimed in, it's very much appreciated :-)

patrick
--
Patrick Machielse
Hieper Software

http://www.hieper.nl
info@...
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Issue copying IDv2 TCON frames with a v1 genre reference

2009-11-13T14:38:22Z

On Nov 13, 2009, at 11:33 PM, Michael Smith wrote:

> I've done that already. I think they marked it as a duplicate, which
> means it disappears into never-to-be-seen-again land. Still, more
> people complaining won't hurt.

I did as well -- years ago, I think.

-Scott
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Re: Issue copying IDv2 TCON frames with a v1 genre reference

2009-11-13T14:33:17Z

On Fri, Nov 13, 2009 at 2:25 PM, patrick machielse <patrick@...> wrote:

> Op 13 nov 2009, om 23:00 heeft Lukáš Lalinský het volgende geschreven:
>
>>> TCON (42)
>>>
>>> When copied to a new v2 tag, the frame is written out like this:
>>>
>>> TCON 42
>>>
>>> Which is interpreted as a custom genre "42".
>>
>> It shouldn't be interpretted as a genre "42" by TagLib or any
>> application that supports ID2v2.4. The conversion it does is correct
>> -- TCON with a value "(42)" is the way to write ID3v1-style genres in
>> ID3v2.3, "42" is the way to do it in ID3v2.4. Writing "(42)" to a
>> ID3v2.4 frame would be incorrect (TagLib can only write ID3v2.4 tags).
>
> Blast, it seems you're right. I only looked up the v2.3 specs... So, in sum: TagLib is doing the right thing and iTunes (latest version) seems to map numeric values in 2.4/TCON incorrectly (or not at all).
>
> Mike wrote:
>
>> Note that itunes can't handle v2.4-style numeric genres. Taglib, as of
>> 1.6 I think, won't write out a numeric genre ever (well, unless you
>> disable the itunes hacks), it'll always expand them to the string
>> form.
>
> Hmm, I'll submit a report to Apple's bugreporter. Well, it can't hurt...

I've done that already. I think they marked it as a duplicate, which
means it disappears into never-to-be-seen-again land. Still, more
people complaining won't hurt.

>
> I'm building my own TagLib framework, but I've done nothing special to disable the iTunes hacks. Or should I actively enable them? I'll look into it.

I believe they're on by default.

Mike
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel