The BSI scheme includes an explicit IALB INFO tag for “Album” whereas the RIFF standard has to use the IPRD (Product) or related tags for “Album”.įrom this I deduct that my tags should be in-fact non-default ID3 tags, because nothing else (which is “non-default” tag) is preserved. Some players or applications that support WAV metadata may use an alternative de facto “standard” promoted by Broadcast Software International (BSI) in addition to or instead of ID3 tags. Non-default ID3 tags can be exported but they all use the generic “TXXX” frame so may not be seen by all players. Non-default LIST INFO tags (other than “Copyright” and “Software”) are not supported. Yet, at the wiki of Audacity, there is this statement: I’ve run this which doesn’t list anything: I don’t think my custom tags are encoded as ID3 tags. Kid3 (an app I found for bulk edit of meta tags) identifies my custom tags as ID3v2.4.0 tags. Is this correct (those can’t be decoded/read)? And, of course, if someone has hit that and handled it - your advice is much appreciated. They are custom property names, and the format reader seems to be decoding only specific default properties from a few other specs (standards?) like BWAV, INFO, acid, etc.īasically, what I need and seems to not be supported by JUCE, right now, are custom-named meta properties on Wav files. Reading on the different types of meta encoded in the format, I think these are ID3v2 chunks. wav file containing meta data that doesn’t seem to be readable through the WavAudioFormat. Kid3-cli -c "set picture:'D:/Everclear/World of Noise/folder.jpg' 'Front cover'" "D:/Everclear/World of Noise/08 Sparkle.I have a. So, the final working command line that worked for me (typed at the Windows cmd prompt) is as follows. (3) Finally, double quotes should surround the last parameter, being the path to the audio file. That is: (1) double quotes around the command string that follows -c but (2) parameters within the command string should be surrounded by single quotes. Thirdly, at the risk of labouring the point, the precise use of single and double quotes as shown in mightcpa's answer appears mandatory. "D:/Everclear/World of Noise/08 Sparkle.flac". The same substitution is required for the path to the audio file that is to be placed at the end of the entire command line but note that this is surrounded by double quotes e.g. That is, backslashes become forward slashes and the path is surrounded by single quotes. That should be expressed as 'D:/Everclear/World of Noise/Folder.jpg' in the command string. In Windows, the path typically exposed by the operating system would be (for example) 'D:\Everclear\World of Noise\Folder.jpg'. Secondly, the sample path "path/to/x12345.jpg" might usefully be explained. I note that my observations were made upon testing on my installation of kid3-cli version 3.9.3 on a Windows 10 desktop so the differences (given the passage of time) could be version related.įirst, there needs to be a colon between the set picture command and the path to the picture, not a space as appears in mightcpa's answer. Mightcpa's answer is largely correct but it may assist others if I make explicit three details in respect of the set picture command string. APIC,METADATA_BLOCK_PICTURE: Picture = x12345.jpgġ) what is the correct syntax for the command line to tag each (meaning one) file with this information?ģ) how do I choose which encoding scheme to use?Ĥ) can that track tag have anything other than a digit in it?ĥ) what goes on with that picture? is it just a name? a link? an embedded image?.TRCK,TRACKNUMBER: Track Number = x12345 (can this be done? I need an x or a - or something other than a digit).TYER,DATE: Date = (or year 2014 is fine, inevitable I guess).COMM,COMMENT: Comment = now is the time for all good men to.It just has to run on Windows command line. I'm using kid3-cli, but I'd be willing to use something else. Try as I might, I can't seem to get the right syntax. However, I need to do the files one at a time. I'm trying to tag some mp3 and ogg files from the windows command prompt.
0 Comments
Leave a Reply. |