MDK90
My current tagging setup uses two custom frames within tags:
<ALBUM> #tag1 #tag2 #tag3 / other information
where / is the delimiter for tags
<SPLIT> #tag1; #tag2 (
where the tag is multivalue, some tagging libraries only read first value, others with delimiter (mostly ;)
Is there some way to persuade virtualdj to use frame <ALBUM> for tags like it currently does with <COMMENT>? I didnt really understand the userfields, thought if I'd rename those maybe that would work, but those seem to be database only, dont they?
<ALBUM> #tag1 #tag2 #tag3 / other information
where / is the delimiter for tags
<SPLIT> #tag1; #tag2 (
where the tag is multivalue, some tagging libraries only read first value, others with delimiter (mostly ;)
Is there some way to persuade virtualdj to use frame <ALBUM> for tags like it currently does with <COMMENT>? I didnt really understand the userfields, thought if I'd rename those maybe that would work, but those seem to be database only, dont they?
Inviato Wed 13 Nov 24 @ 10:21 am
Benz Werner
MDK90 wrote :
My current tagging setup uses two custom frames within tags:
<ALBUM> #tag1 #tag2 #tag3 / other information
where / is the delimiter for tags
<SPLIT> #tag1; #tag2 (
where the tag is multivalue, some tagging libraries only read first value, others with delimiter (mostly ;)
Is there some way to persuade virtualdj to use frame <ALBUM> for tags like it currently does with <COMMENT>? I didnt really understand the userfields, thought if I'd rename those maybe that would work, but those seem to be database only, dont they?
<ALBUM> #tag1 #tag2 #tag3 / other information
where / is the delimiter for tags
<SPLIT> #tag1; #tag2 (
where the tag is multivalue, some tagging libraries only read first value, others with delimiter (mostly ;)
Is there some way to persuade virtualdj to use frame <ALBUM> for tags like it currently does with <COMMENT>? I didnt really understand the userfields, thought if I'd rename those maybe that would work, but those seem to be database only, dont they?
What you write here nobody understands ! Can you explain this in more detail ?
Inviato Wed 13 Nov 24 @ 1:00 pm
PhantomDeejay
No. Comment field is DESIGNED to be able to hold multiple "entries" (multiple comments) and therefore described as such on id3 tag standards.
On the other hand, "Album" field is supposed to be unique entry field.
VirtualDJ complies as best as possible with id3 standards. Therefore it reads the Album frame as ONE entry.
On the other hand, "Album" field is supposed to be unique entry field.
VirtualDJ complies as best as possible with id3 standards. Therefore it reads the Album frame as ONE entry.
Inviato Wed 13 Nov 24 @ 2:06 pm
MDK90
@Benz: Tags like ID3 are separated by frames, you have some default like <ALBUM>, <ARTIST> but there are also TXXX-Frames which you can name yourself. So I am using <ALBUM> in the specified format (#tags / other text, like riddim etc) and have a helping TXXX-Frame named <SPLIT> for my library management where multiple values are set. Coming from Traktor this allowed me to search my tags as <ALBUM> is indexed and used Foobar 2000 to set up an itunes-like selector where I could scroll the tags in hierarchy where the multiple values are needed.
@Phantomeejay: I am totally fine with the <ALBUM> frame to be single only, I'd just like to know if I can scan the <ALBUM> for tags instead of the <COMMENT> as my tagging workflow relies on that. Mentioning my <SPLIT> is only for the unexpected case that I could use it.
@Phantomeejay: I am totally fine with the <ALBUM> frame to be single only, I'd just like to know if I can scan the <ALBUM> for tags instead of the <COMMENT> as my tagging workflow relies on that. Mentioning my <SPLIT> is only for the unexpected case that I could use it.
Inviato Wed 13 Nov 24 @ 6:29 pm