Reading GEOB?

Etz · July 20, 2015, 8:11am

Is there any way to display specific GEOB fields in "Columns view"?

GEOB size=361 MIME="application/octet-stream" File="" Descr="Serato Markers_" Binary data size=318 Content: ".......................0........P............2.......`...............L.....:N............3..............................................................
................................................................................
.
................................................................................
.
...." (02 05 00 00 00 0e 00 00 00 12 10 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 06 30 00 00 01 00 00 00 01 05 50 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 06 32 10 00 01 00 00 00 03 60 0f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 01 4c 01 00 00 00 06 3a 4e 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 06 33 18 00 01 00 00 00 07 2e 0e 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 03 18 00 01 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 00 00 03 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 00 00 03 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 00 00 03 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 00 00 03 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 00 00 03 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 00 00 03 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 00 00 03 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 00 00 03 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 00 7f 7f 7f 7f 7f 00 00 00 00 03 00 00 00 00 00), GEOB size=357 MIME="application/octet-stream" File="" Descr="Serato Markers2" Binary data size=314 Content: "..AQFDVUUAAAAAFQAAAAAJEADMAAAAAEVuZXJneSAzAENVRQAAAAAVAAEAAELQAMyIAAAARW5lcm
d5IDUAQ1VFAAAAABUAAgAA8A8AAADMAABFbmVyZ3kgNwBDVUUAAAAAFQADAAGdTgDMzAAAAEVuZXJneS
A
0AENVRQAAAAAVAAQAAdcOAADMAAAARW5lcmd5IDcAQ1VFAAAAABUABQACEM4AzADMAABFbmVyZ3kgNQB
D
VUUAAAAAFQAGAAJKjQAAzMwAAEVuZXJneSA3AENVRQAAAAAVAAcAAvfMAIgAzAAARW5lcmd5IDcA" (01 01 41 51 46 44 56 55 55 41 41 41 41 41 46 51 41 41 41 41 41 4a 45 41 44 4d 41 41 41 41 41 45 56 75 5a 58 4a 6e 65 53 41 7a 41 45 4e 56 52 51 41 41 41 41 41 56 41 41 45 41 41 45 4c 51 41 4d 79 49 41 41 41 41 52 57 35 6c 63 6d 64 35 49 44 55 41 51 31 56 46 41 41 41 41 41 42 55 41 41 67 41 41 38 41 38 41 41 41 44 4d 41 41 42 46 62 6d 56 79 5a 33 6b 67 4e 77 42 44 56 55 55 41 41 41 41 41 46 51 41 44 41 41 47 64 54 67 44 4d 7a 41 41 41 41 45 56 75 5a 58 4a 6e 65 53 41 30 41 45 4e 56 52 51 41 41 41 41 41 56 41 41 51 41 41 64 63 4f 41 41 44 4d 41 41 41 41 52 57 35 6c 63 6d 64 35 49 44 63 41 51 31 56 46 41 41 41 41 41 42 55 41 42 51 41 43 45 4d 34 41 7a 41 44 4d 41 41 42 46 62 6d 56 79 5a 33 6b 67 4e 51 42 44 56 55 55 41 41 41 41 41 46 51 41 47 41 41 4a 4b 6a 51 41 41 7a 4d 77 41 41 45 56 75 5a 58 4a 6e 65 53 41 33 41 45 4e 56 52 51 41 41 41 41 41 56 41 41 63 41 41 76 66 4d 41 49 67 41 7a 41 41 41 52 57 35 6c 63 6d 64 35 49 44 63 41)

Specifically fields with description: Descr="Serato Markers_ and Descr="Serato Markers2"
Both include binary data (base64 encoded)...no wish to actually decode it, but just show it.
Also, somehow export it if needed?

If it is not possible to show it, how to indicate if it is present in file, or not?

Would it be even possible with MP3Tag?

DetlevD · July 20, 2015, 8:54am

This question is directed to the Mp3tag developer himself.

You may find and read some informations about the ID3 frame GEOB ...
http://id3.org/id3v2.3.0
... search for "4.16. General encapsulated object".

You may find and read some informations about the ID3 frame GEOB within the Mp3tag forum ...
https://www.google.de/search?q=site%3Aforums.mp3tag.de+GEOB

As I understand ... the ID3 frame GEOB is not supported by Mp3tag.

You may try out "FFmpeg" ...
https://www.ffmpeg.org/
http://ffmpeg.zeranoe.com/builds/
http://jonhall.info/how_to/setup_and_use_ffmpeg_on_windows
http://jonhall.info/how_to/dump_and_load_m...ata_with_ffmpeg

DD.20150720.1324.CEST

Etz · July 20, 2015, 9:27am

Then it does not modify it either?
Even if _TAG or _ALL (bad practice, not reccomended, I know) is used in Actions processing?

DetlevD · July 20, 2015, 9:36am

As I understand ... the pseudo tagfields _TAG and _ALL ...
are defined by the Mp3tag developer himself for the usage within Mp3tag, ...
and you can expect and rely on, ...
that these special placeholders support only those tag fields, ...
which Mp3tag is able to handle.

DD.20150720.1336.CEST

Etz · July 20, 2015, 9:50am

This can be actually tested, you can dump that info with mp3diag,
do some pseudo field action (or even remove all tags) and after that dump contents with mp3diag again and compare results.

Will try that later...just for interest and report here, what would actually happen, as a backlog.

Etz · July 20, 2015, 10:02am

OK, removing Tag`s will definately delete those GEOB fields as well (it removes absolutely everything).

Case conversion (using pseoudo tag _TAG) for example, seems to have no effect at all on those. (which is actually good and desirable behaviour).

So IMHO we can conclude, that pseudotag _TAG at least does not include any GEOB fields.

Oblio · July 23, 2015, 7:57am

Exiftool can read and extract binary tags from mp3 files and has some process control built in e.g.

-if EXPR

Specify a condition to be evaluated before processing each FILE. EXPR is a Perl-like logic expression containing tag names prefixed by $ symbols. It is evaluated with the tags from each FILE in turn, and the file is processed only if the expression returns true. Unlike Perl variable names, tag names are not case sensitive and may contain a hyphen. As well, tag names may have a leading group names separated by colons, and/or a trailing # character to disable print conversion. The expression $GROUP:all evaluates to 1 if any tag exists in the specified GROUP, or 0 otherwise (see note 2 below). When multiple -if options are used, all conditions must be satisfied to process the file. Returns an exit status of 1 if all files fail the condition. Below are a few examples:

    # extract shutterspeed from all Canon images in a directory
    exiftool -shutterspeed -if '$make eq "Canon"' dir

    # add one hour to all images created on or after Apr. 2, 2006
    exiftool -alldates+=1 -if '$CreateDate ge "2006:04:02"' dir

    # set EXIF ISO value if possible, unless it is set already
    exiftool '-exif:iso<iso' -if 'not $exif:iso' dir

    # find images containing a specific keyword (case insensitive)
    exiftool -if '$keywords =~ /harvey/i' -filename dir<!--sizec--></span><!--/sizec-->

You may be able to make it do what you want.

http://www.sno.phy.queensu.ca/~phil/exifto...cessing_control

Oblio · July 24, 2015, 12:01pm

This will output the GEOB frame to a similarly named text file for each mp3 file in MyDir matching the condition

exiftool -ID3_GEOB -if "$ID3_GEOB =~ /Serato Markers/" -b -U -ext mp3 -w .txt -r MyDir .

Many more things are possible with Exiftool.

ryerman · July 24, 2015, 1:43pm

But editing tags for audio files is not one of them.

Etz · July 26, 2016, 4:57am

Still, maybe Florian could make it possible to display somehow in columns view that file has GEOB data?
For example "GEOB" True/False style...

Etz · March 9, 2018, 7:14pm

Does removing id3v1 only removes GEOB too?

I discovered interesting issue, I have some files which cannot be played back with Sennheiser Captune: https://play.google.com/store/apps/details?id=com.sennheiser.captune

They play back fine on every other player/device.
Removing id3v1 with mp3tag somehow fixes the issue, still investigating the reason.

Only Captune and this batch of files seem to have the issue, when files are checked with MP3Diag, it says: "invalid characters in id3v1 tag".

Etz · April 20, 2018, 7:07pm

Maybe @Florian can comment on this?

Florian · April 21, 2018, 9:22am

Not sure what the question is, but removing ID3v1 doesn't remove ID3v2 GEOB frames. This only happens if you remove ID3v2.

Etz · April 21, 2018, 9:39am

Thx @Florian, that actually was the question.
How to get rid GEOB, if needed, using Mp3Tag.

Florian · April 21, 2018, 10:13am

You could cut the whole tag from the file using Ctrl + X and paste it back using Ctrl + V.

Background: Mp3tag omits unsupported fields when writing fresh tags — if you simply update an existing tag, also unsupported fields are preserved.

Oblio · May 18, 2018, 8:40am

@Florian
It would be useful to have this Ctrl+X + Ctrl+V combination available as an action, so it can be performed on many files, one file at a time.

For a large file set that would be much safer than cutting all tags at once and pasting them all back separately i.e. if anything goes wrong during the paste you will lose information!

Please accept this as a feature request.