chill wrote: > Well that was the theory. But I haven't been able to find a combination > of switches that successfully writes v2 tags to the lame output, such > that VLC or id3v2 understand them. So I've resorted to using id3v2 to > write the v2 tags to the lame output. So my script does what I want it > to, but I'm slightly bugged that I can't get lame to do the v2 tags. > > And I'd still be interested to know why only v2 tags are preferred. Is > it because using both v1 and v2 in the same file can cause problems? If > so, then since I'm looking for maximum compatibility with in-car > players, would 'only v1' avoid the problems of having both types, > assuming I can live with the tag length limitations? Is v1 deprecated > to the point that newer players may not understand them? I use --add-id3v2 and the various --tx metadata flags with lame and have never had issues with id3v2 or vlc interpreting them.
For LMS having both v1 and v2 in the same file can cause strange collation behaviour when browsing local music if the tags are not identical. id3v2 can convert v1 tags to v2 making it easy to have just the later in the file. For car players I would expect v1 to be the best choice for maximum compatibility. Ralphy *1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio 'Squeezebox client builds' (https://sourceforge.net/projects/lmsclients/files/) 'donations' (https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted) always appreciated. ------------------------------------------------------------------------ ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484 View this thread: http://forums.slimdevices.com/showthread.php?t=111997 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
