ext/lame/gstlame.*: Contrary to what the const char in the lame API might suggest...
authorTim-Philipp Müller <tim@centricular.net>
Mon, 23 Jan 2006 18:37:16 +0000 (18:37 +0000)
committerTim-Philipp Müller <tim@centricular.net>
Mon, 23 Jan 2006 18:37:16 +0000 (18:37 +0000)
commitd99d2bc9c217f4780cbe3e271e3c4c7b890bac3b
treeb3d582bb13788c648cd4d9908166870f416d53ad
parent1bea0573bb3b15d8b7e3cad7136789e88833985d
ext/lame/gstlame.*: Contrary to what the const char in the lame API might suggest, lame expects us to keep the string...

Original commit message from CVS:
* ext/lame/gstlame.c: (gst_lame_finalize), (gst_lame_class_init),
(gst_lame_init), (add_one_tag), (gst_lame_set_metadata):
* ext/lame/gstlame.h:
Contrary to what the const char in the lame API might suggest,
lame expects us to keep the strings we pass to id3tag_set_foo()
around; it doesn't free them either though, so we have to store
them somewhere and free them later when we can be sure lame
doesn't need them any longer.
ext/lame/gstlame.c
ext/lame/gstlame.h