INTERACT FORUM
More => Old Versions => JRiver Media Center 23 for Windows => Topic started by: Matt on January 26, 2017, 08:00:35 am
-
Hi everyone,
I'd really like to switch everyone to the new tag window eventually.
Right now you get into it by holding shift while opening. And you get out of it the same way.
I've been using it quite a bit and really like it.
What I'm wondering is if there are any remaining problems that we need to address before making the switch?
Thanks.
-
It's awesome, the old window is long dead to me
The only issues I personally have is occasionally when typing onto a field, then choosing the 'best match' from the list, it gets briefly frozen and the tag change doesn't stick. Closing the tag window and reopening always fixes it.
its not overly frequent so I can't say exact steps, I'll try and do it though for the data point.
-
Looks good...
-
What I'm wondering is if there are any remaining problems that we need to address before making the switch?
it has a bright white background when using modern cards dark
-
it has a bright white background when using modern cards dark
It's using this chunk from the skin:
<TAGWINDOW>
<Entry Name="Group" Bitmap="TagWindow_Group.png" NumberImages="2" Margins="22,1,0,1" TextColor="484e59" />
<Entry Name="Field" Bitmap="TagWindow_Field.png" NumberImages="2" />
<Entry Name="FieldLabel" Bitmap="TagWindow_FieldLabel.png" NumberImages="1" />
</TAGWINDOW>
Most don't have it so it uses the default chunk.
ModernCards Grey does have it. Not sure if the same should be copied to the ModernCards Dark?
-
Yeah, I don't think Dirhael is/was aware of the experimental tag window. I didn't know it could be skinned either until marko told me about it. If you can fix it in the dark skin, go for it I say! :P
I put it in the Grey skin as I was made aware of it.
-
This post, and the one after it are still issues:
http://yabb.jriver.com/interact/index.php/topic,101448.msg705653.html#msg705653
Also, this post... (same thread)
http://yabb.jriver.com/interact/index.php/topic,101448.msg735583.html#msg735583
and this:
http://yabb.jriver.com/interact/index.php/topic,101448.msg735905.html#msg735905
The only other things I miss (or grate) are:
The artwork in the old AW can be clicked, and it opens in its own window. Not a biggie as I don't use it that often.
In the new AW, if it could better remember the expanded/collapsed state of each group, that would be great. Right now, there seems to be no rhyme nor reason to what currently happens. This can be quite frustrating.
-
For me, the old Tag Window opens instantly while the new one takes 3 to 4 (!!) seconds to open. For this time MC doesn't respond to any interaction.
-
The only other things I miss (or grate) are:
The artwork in the old AW can be clicked, and it opens in its own window. Not a biggie as I don't use it that often.
Clicking the artwork in the new tag window gives a menu of choices with a way to view the image right at the top.
That's the expression:
Custom(Image)
It's possible that should be one of the "Add..." choices because it's a little buried.
-
I've been using the new tagging window for ages now. Works fine for me..
-
Hi everyone,
I'd really like to switch everyone to the new tag window eventually.
Right now you get into it by holding shift while opening. And you get out of it the same way.
I've been using it quite a bit and really like it.
What I'm wondering is if there are any remaining problems that we need to address before making the switch?
Thanks.
Matt, I reported on severe problems using the new tag window in this old thread.
http://yabb.jriver.com/interact/index.php/topic,100751.msg698897.html#msg698897 (http://yabb.jriver.com/interact/index.php/topic,100751.msg698897.html#msg698897)
I was spending 1-2 hours a night tagging photos on our Australia trip. I soon discovered that the tags were badly screwed up. I was still finding wrong tags months later back at home.
I went back to using the old tag window and have not seen a similar problem.
I did not try to reproduce the problem because it would like have required hours and hours to find a reproducible sequence of steps that showed the problem. It also requires that I create a test library with isolated media files. I am not going to take chances with the music files and the associated MC library that I've spent 10+ years making. I'm not risking years of photos either.
If you are dead set on eliminating the current default tag window, I have three choices: see if I can reproduce the bug, stick with MC 21 forever or start looking for a replacement for MC all ripping and tagging media files.
I'm willing to put in some time trying to reproduce the problem now because of your intention to eliminate the old tag window. However, I won't go on forever trying.
-
For me, the old Tag Window opens instantly while the new one takes 3 to 4 (!!) seconds to open. For this time MC doesn't respond to any interaction.
For some reason Matt may have my library, so perhaps you could just give it a try: load it and open the new tag window to see whats happening! Still 3 to 4 seconds for me.
-
One thing I was using pretty heavily over the last couple of days was the 'Filename Path' tag in the classic view. Am I just missing it or does that not exist in the new tagging window?
Edit: Nevermind - just figured out how to add it...
-
I've found a few isolated things that I like to use the old tag window for... having a hard time remembering right now.
But here's a suggestion: Since some people have issues with the new tag window, why not reverse the behavior? That is, make the NEW tag window the default and let anyone who wants to, use the old tag window using the <shift>-Tag sequence that we now use to toggle to the new tag window.
That way new users get the new tag window off the bat, but old users that want specific things from the old tag window can switch back and forth at will.
Or is there some compelling reason (other than satisfaction) to eliminate the older tag window?
Brian.
-
if i mess up a tag, and use ctrl z to undo, the tag field highlights (as it should) but it will reliably not accept any further input. closing the tag window and reopening works
-
I now *almost* exclusively use the new tag window. If you make the new tag system the default, please leave the old tag method accessible until all issues are resolved... I'm pretty sure there I times I have to switch back to the old method, but cannot recall any reasons off the top of my head.
-
I now *almost* exclusively use the new tag window.
That's our plan.
-
I end up using both, but the new tag window as the default works for me.
-
For some reason Matt may have my library, so perhaps you could just give it a try: load it and open the new tag window to see whats happening! Still 3 to 4 seconds for me.
Hopefully we'll have this fixed next build:
Changed: The tag action window could be slow to open when it was showing playlists. Now it's much faster.
Feedback welcome.
-
How about enabling the up and down keys to move in the respective directions between tag fields?
Or is it a case of [Tab] / Shift-[Tab] performs that function?
What key stroke enables navigation between tag groups (General, Image, File, Audio, Playback, Advanced)?
I like the prospect of customising the fields / groups. One to play with later.
-
Clicking the artwork in the new tag window gives a menu of choices with a way to view the image right at the top.
That's the expression:
Custom(Image)
It's possible that should be one of the "Add..." choices because it's a little buried.
Coming next build:
Changed: The new tag window has "Image" as one of the add choices during customization to nicely add the image field and type the right expression for you.
-
Now it's much faster.
It's waaaay faster. It's not as instantly as the old tag window is, but is under a second for me now. Thanks. I'll report back if it is usable now ;)
-
It's waaaay faster. It's not as instantly as the old tag window is, but is under a second for me now. Thanks. I'll report back if it is usable now ;)
The performance is because you're showing Playlists in the window and you have a ton of them. If you removed playlists it should get pretty much instant.
-
At the moment to enter data requires a left mouse click - why not enable the F2 (edit) key as well?
When a user is editing metadata, they'll have a keyboard to hand. Navigation around the tags by keyboard should be facilitated accordingly.
-
once you've clicked the first field, you can tab / alt tab through the group
the issue (i see) with F2 is you need a selection for it to start the edit - when the tag window opens there is no selection (and there shouldn't be, i would hate that since i use groups)
-
In the new tag window, when I enter a value into the Comment or Composer tag and hit enter the pane hangs and doesn't immediately save.
I tag files on a very slow machine, but this behavior doesn't happen on the old window.
-
I've just opened it for the first time. I like it. I like how clicking anywhere on the group header fans open and closed the fields. I would like to see that happen in the Views tree too. (View headers should be 100% width of the tree so that they are easier to click on, like the Tag group headers).
Tab to move between fields is a useful shortcut too. I would be interested to see if there is a keyboard shortcut for moving between next/previous file in the files view list to save having to use the mouse to keep moving back and forth between the tag window and file list.
-
Is there any possibility of getting rid of the data that's automatically added under the thumbnail when "custom(image)" is used?
This is especially ugly when being used for photographs. All that <XMLFN version="1.0"> stuff is not pretty.
Would it be a lot of work to put [caption] under there? Centered, without the field label? Just click to edit.
-
Is there any possibility of getting rid of the data that's automatically added under the thumbnail when "custom(image)" is used?
This is especially ugly when being used for photographs. All that <XMLFN version="1.0"> stuff is not pretty.
Would it be a lot of work to put [caption] under there? Centered, without the field label? Just click to edit.
Coming next build:
Changed: The string <XMLFN... is no longer shown in the new tag window below images.
It will just show the regular filename instead.
-
Thanks for that Matt. Next up in useability, is, the groups...
Open the tag window....
Some groups are expanded, some are closed...
What determines this?
I expand a group, edit a tag, close the tag window.
Open the tag window again, and the group previously expanded is collapsed again....
Can the expanded/collapsed state of each group be remembered?
-
+1
-
Well, I've had some time for more of a play with this today, and found some clues in the "tag file info templates.xml" file...
So, currently, the expanded/collapsed state is not remembered, and I've figured out why the behaviour is confusing...
If you set the expanded/collapsed state of all the groups the way you would want them, then hit "Customise", make no no changes at all, and press OK.
Now, the states of each groups are set, and remembered each time the tag window is opened.
The confusion is arising because this is obviously happening when we quickly dive in to "Customise" to add a field to a group, with no thought at all as to what's expanded and what's collapsed, and when we hit "OK", the group states are updated and from that point forward that's how the tag window will open each time. We need to set them how we want them and dive into customise, and press OK to have the states saved.
We should be able to set the group state in the customise tool, always expanded or always collapsed, and that setting shouldn't change unless we specifically change it.
-marko
-
I confirm that marko
I suspect that the OK button press is what triggers the state save. The "problem" is now that you've sorted it, I have a workaround and it will never bother me again :p
-
Coming next build:
Changed: Made the new tag window save the expanded / collapsed state of groups between runs.
-
Thanks Matt.
It was mentioned over in the main forum that the new tag window was unuseable in the Black on Black skin, so, I knocked a quick skin up for it....
I didn't spend a huge amount of time on it, but it looks kind of OK, and is at least useable, which is better than what anyone using the skin has at the moment.
You're welcome to add the files if you want.
------------------------------------------------------------
A reminder that that wierd thing where, if a field is in edit mode and scrolled up, the edit box floats over the tree in an orphaned state is still there.
-marko
-
Thanks a lot Marko.
Coming next build:
Changed: Added a section for the new tag window to the Black on Black skin (thanks Marko).
-
A reminder that that wierd thing where, if a field is in edit mode and scrolled up, the edit box floats over the tree in an orphaned state is still there.
Next build:
Changed: Scrolling the new tag window will stop any open edits (instead of scrolling the edit off the screen!).
-
Here are the fixes for ModernCards Dark Edition and ModernCards White Edition. Both support the experimental/new tag window now. So that should cover all three ModernCards skins now.
http://www.mediafire.com/file/hco5qqqo5q5xyeb/ModernCardsExperimentalTagWindowFixes.zip
-
Here are the fixes for ModernCards Dark Edition and ModernCards White Edition. Both support the experimental tag window now. So that should cover all three ModernCards skins now.
http://www.mediafire.com/file/hco5qqqo5q5xyeb/ModernCardsExperimentalTagWindowFixes.zip
Thanks so much!
Coming next build:
Changed: Added a section for the new tag window to ModernCards Dark Edition and ModernCards White Edition (thanks Awesome Donkey).
-
Does that mean all skins bundled with MC support the new tag window? Haven't looked at the others. :D
EDIT: Ah, nope. Nearly all of them need slight tweaks.
-
Here's a good starting point for Purity, you guys may want to edit these more (e.g. add the gradients and whatnot).
http://www.mediafire.com/file/8fcaj91dtla3v73/PurityNewTagWindow.zip
-
Here's a good starting point for Purity, you guys may want to edit these more (e.g. add the gradients and whatnot).
http://www.mediafire.com/file/8fcaj91dtla3v73/PurityNewTagWindow.zip
Thanks! I've sure included that for the next build.
-
I'm getting really tempted to switch so it shows the new tag window by default and SHIFT switches back to the old window.
It's probably a terrible idea!
-
It would be nice to get the tag window to redraw when you change the media subtype, atm you have to close the tag window and reopen it to get it to show the right fields after such a change.
-
It would be nice to get the tag window to redraw when you change the media subtype, atm you have to close the tag window and reopen it to get it to show the right fields after such a change.
You mean you make a change that changes what profile it should load? Picking a different file and coming back should reset it, but it probably doesn't reload otherwise.
-
It would be nice to get the tag window to redraw
Actually, it'd be nice if the new tag window redrew/reloaded after changing skins. If you go from a light skin to a dark skin or vice versa with the new tag window open the font color used sometimes appears as the previous skin's value (e.g. either a light or dark color which makes the new tag window fonts appear with the wrong color) until you close the new tag window and reopen it. I noticed this when I was updating all the skins with new tag window support, and thought I was making mistakes with the skin's font color values. :P
-
You mean you make a change that changes what profile it should load? Picking a different file and coming back should reset it, but it probably doesn't reload otherwise.
yes that one, it would be nice if it redrew when that subtype value changes
-
Actually, it'd be nice if the new tag window redrew/reloaded after changing skins.
I've just flipped between a bunch of skins and the new tag window just updated beautifully.
I'm not sure what might be different?
-
It's very simple to reproduce. Use the Modern Cards: White Edition skin, then open the new tag window. Switch to Black on Black from Modern Cards: White Edition and the new tag window font color looks like this;
(http://i.imgur.com/ly3kTw4.png)
It's using the wrong font color (too dark!). So close the new tag window and reopen it (still using Black on Black) and the new tag window appears like this;
(http://i.imgur.com/0icv3WB.png)
This is correct and how the font color should look.
Second example. Switch from Black on Black to Modern Cards: White Edition with the new tag window open, after the switch the new tag window font color appears like this;
(http://i.imgur.com/p3pnH8U.png)
Yikes! This is wrong again (font color is too light!). Close the new tag window and reopen it, now the font color in the new tag window looks like this;
(http://i.imgur.com/Pclbrg7.png)
And this is correct.
-
It's very simple to reproduce. Use the Modern Cards: White Edition skin, then open the new tag window. Switch to Black on Black from Modern Cards: White Edition and the new tag window font color looks like this;
Boy, I can't reproduce. I switch and it's just perfect.
Interesting!
-
Strange, it's VERY easy for me to reproduce on Windows 10 Pro Creators Update 64-bit with a Nvidia GPU and high refresh rate (96Hz+) IPS 1440p monitor.
I'll try setting up a Windows 10 VM and seeing if it happens there as well.
-
There has to be other factors in play other than just switching skins...
I went from Modern Cards white to BoB and can confirm the font colour did not update correctly. Open/close the tag window corrected this.
I got distracted, did some other stuff, got back to MC and remembered I was supposed to be testing stuff...
Switched back to Modern Cards white, and the font colour updated correctly :|
-
Boy, I can't reproduce. I switch and it's just perfect.
Interesting!
I tested on John's machine and it did the wacky color loading!
So I checked in a hopeful fix.
Please try the new build once it's out and confirm.
Thanks.
-
Groovy, thanks Matt! :D
-
The new build is out, so please give it a test!
Thanks.
-
Yep, it fixes itself now, YAY!
-
6. Changed: The new tag window supports using a custom text color (add it to <TAGWINDOW> <Colors Text="FF00FF" />)
I was doing some more work in this area over the past couple of days, and notice that this colour value is not being used in the group names of the tag window.
When looking at something like Thunderstorm and Blue Steel, it's fine, but where I'm seeing this it's a bit, well, 'yuk!'
Would <Colors Text="FF00FF" Group="00FF00" /> be possible?
-marko
-
I was doing some more work in this area over the past couple of days, and notice that this colour value is not being used in the group names of the tag window.
When looking at something like Thunderstorm and Blue Steel, it's fine, but where I'm seeing this it's a bit, well, 'yuk!'
Would <Colors Text="FF00FF" Group="00FF00" /> be possible?
-marko
Good idea!
Coming next build:
Changed: Added support for customizing the group colors in the new tag window. Set: <TAGWINDOW><Colors Group="FF00FF" />.
-
With the way progress on the new tag window has been going, you might be able to push it out as the default tag window soon, perhaps with MC23?
Good work, Matt!
-
I do admit, group color wasn't easy to workaround in the bundled skins, but I think I was able to get all the skins looking pretty great with the new tag window, Thunderstorm in particular is pretty great, IMO.
The *only* thing I can see left with the new tag window in regards to skinning is the search bar on the bottom of the new tag window. Look at a couple skins, e.g. Green Eyes, Blue Steel, Black on Black, etc. You can't change the background, nor the font color of the search box there (in those three examples the search box is white with black font color, which doesn't match the rest of the skin elements). Purity, on the other hand, has a black search box with the new tag window and I still haven't figured out how it set that, yet. That's really the last "sore thumb" in terms of skinning the new tag window.
P.S. Since we're on the subject of the skins, does anyone know why the top menus in the Blue Steel skin are spaced so far away from the separator, which is next to the logo? There's like a 20 to 50 pixel space there! Seeing it like this doesn't really make visual sense to me with all that wasted space, IMO.
-
The *only* thing I can see left with the new tag window in regards to skinning is the search bar on the bottom of the new tag window. Look at a couple skins, e.g. Green Eyes, Blue Steel, Black on Black, etc. You can't change the background, nor the font color of the search box there (in those three examples the search box is white with black font color, which doesn't match the rest of the skin elements). Purity, on the other hand, has a black search box with the new tag window and I still haven't figured out how it set that, yet. That's really the last "sore thumb" in terms of skinning the new tag window.
Well it was just using the edit style from the skin.
I switched it to a search style for the next build, since it is a search.
Not really sure if that will help or hurt, but I changed it anyway :)
-
Thanks Matt. I agree, the new tag window is just about ready for prime time, however, I still think that the 'large edit' issue I've hilighted here...
http://yabb.jriver.com/interact/index.php/topic,101448.msg705653.html#msg705653
could be a problem. It's kind of like, the last stumbling block.
Granted, it's not a bug, but for me, it's definately a step backwards in terms of useability. Anyone else care to comment?
-marko
-
i personally don't agree with you marko (well i don't disagree either), but i'm probably not the average user case (i edit all text blocks like lyrics in notepad, then copypasta).
as for popup window editing - i'm not a fan of popup windows, but there are a lot of requests on the forum regularly to have all the tagging and other windows popout, so i suspect this feature is attractive to many.
grouping tags makes so much sense that i don't even comprehend how anyone could open the old window at this point, bugs or no.
-
One last nitpick regarding the new tag window, can it use what's set for List_Selection.png? Otherwise it seems to use a blue selection color and it *should* use the one used for list, at least.
-
Also, is it possible to add SelectedText and HilightText colors support to <TAGWINDOW>?
P.S. <LIST> Also needs HilightText support (https://yabb.jriver.com/interact/index.php/topic,41727.msg764668.html#msg764668). ;)
-
I use linn klimax ds dnla mode
in jriver media center 23.0.41, DNLA mode have wrong.
44.1K 16bit output mode -> 44.1k mp3 320
above 44.1K -> 48K mp3 320
-
When ripping discs, there are no drop-down options for any fields. This makes adding info take 10 X longer. You used to be able to type a few letters and have a drop-down appear with options to choose from. Click and you're done. Now hunt and peck for me. Definitely, a step in the wrong direction. Please help. Thanks.
EDIT: You have to highlight the individual tracks to get the drop-down options to appear. In the past, you just needed to be in the album/CD you were editing before ripping for the drop-downs to appear.
-
Unless I'm missing something, the new tag window no longer tells me the last time an audio file was played, it just says [Varies].
-
Odd, the new tag window tells me the date/time an audio file was last played. Might be file type dependant? I'm using FLAC files.
-
[varies] implies that you have more than one file selected, with different last played times.
-
Odd, the new tag window tells me the date/time an audio file was last played. Might be file type dependant? I'm using FLAC files.
Through 22, it displayed for all files; ALAC, FLAc, MP3, etc. Now no file types display last played.
-
[varies] implies that you have more than one file selected, with different last played times.
It never happened before 23. If I right clicked an album or individual track in order to bring up TAG, it displayed when it was last played.
-
So apparently 23 only lists when an individual track was last played, not an entire album. That's something I'm not used to.
-
That sounds perfectly logical to me.
You don't play all tracks synchronously, so they are all going to have different 'last played' times. Checking some of my albums that haven't been played for several years, the tracks have different 'last played' times, so it seems unlikely that anything has changed in JRiver.
-
Can't find "year" field.
For audio, one of the tag fields I always verify is "Year". It appears year is now under the "General" group as "Date". I'd like to verify that this field is the old "year"..... and if it is.... why not keep it as year. There are 5 other "date" fields under advanced, but for me year was all I wanted to track (which is either release year or "Billboard Hit" year.
-
Can't find "year" field.
For audio, one of the tag fields I always verify is "Year". It appears year is now under the "General" group as "Date". I'd like to verify that this field is the old "year"..... and if it is.... why not keep it as year. There are 5 other "date" fields under advanced, but for me year was all I wanted to track (which is either release year or "Billboard Hit" year.
You can add the year field by hand. Just look for "Year".
Next build we'll have this little change:
Changed: The fields with values section of the new tag window now includes editable calculated fields like year.
-
That sounds perfectly logical to me.
You don't play all tracks synchronously, so they are all going to have different 'last played' times. Checking some of my albums that haven't been played for several years, the tracks have different 'last played' times, so it seems unlikely that anything has changed in JRiver.
All I'm saying is that in every version before 23, If I hit "Tag" on an album, it gave me a specific date for last played. Whether that was the first track or not, I don't know. With Classical albums, that was helpful because I listen to the entire album. The first image is the tag for "Dusty Springfield-A Brand New Me" in 22. It tells me I last played it 25.9 days ago. The second is for the same album in 23. It says "varied" for last played.
(http://)
-
All I'm saying is that in every version before 23, If I hit "Tag" on an album, it gave me a specific date for last played. Whether that was the first track or not, I don't know. With Classical albums, that was helpful because I listen to the entire album. The first image is the tag for "Dusty Springfield-A Brand New Me" in 22. It tells me I last played it 25.9 days ago. The second is for the same album in 23. It says "varied" for last played.
(http://)
You can customize and insert an expression like this:
FormatDate([Last Played, 0], elapsedago)
Call it something like "Played" and it should show the same thing as v22.
-
You can customize and insert an expression like this:
FormatDate([Last Played, 0], elapsedago)
Call it something like "Played" and it should show the same thing as v22.
I could use some help doing that. Where exactly do I put it? I tried it under "playback" and got no data.
-
I have an album view with the thumbnail text set to
[Name]
[Duration] [Last Played]
In version 23 this still shows the date the album was last played, and it's more convenient than having to check the tag window.
-
I have an album view with the thumbnail text set to
[Name]
[Duration] [Last Played]
In version 23 this still shows the date the album was last played, and it's more convenient than having to check the tag window.
Thank you! That is much better than looking at tags. I've learned something great today!
-
Few things/issues want to add on the new window tag.
When i add a field with expression inside of it on tag window, instead of delimited list, it show only a list of names. Can be another way to achieve with expression field to show delimited instead of line of data? Or these can't work on the tag window.
(https://i.gyazo.com/f4b2279b297092df997fd50361dd2cc3.png)
-
It appears that Calculated Fields are not included in the new tag window. They are in the old tag window. This is the easiest place to check the value of a calculated field. It seems like they should be included in the new tag window, as they were in the old one.
-
Hi dtc
Please clarify. I have calculated tags in the new window, I must not be understanding
-
ferday - Hmm... I have half a dozen tags that are not not included in the new tag window. When I looked at them they were all tags with calculated data. I would expect to see them under Advanced but they are not there. They clearly show in the old tag window. I am not sure what could cause them not to appear. They do not appear in the display and they do not appear as tags in the Customization window. I will look for any other commonality among those that do not appear, but the main thing is that they are calculated fields.
EDIT: It appears the issue is that the tags that are calculated fields are not automatically included in Advanced. You can add them if you customize, but then they appear at the bottom of the advanced list. It seems that calculated tag fields should be treated like other tags and automatically appear in the Advanced list, just like they automatically appear in the old tag window.
-
I used to be able to use expressions in the Name field in the tag windows to change the name, much as suggested in Reply number 2 at https://yabb.jriver.com/interact/index.php?topic=101126.0 (https://yabb.jriver.com/interact/index.php?topic=101126.0). It doesn't seem to work anymore.
So in the name field you could put "Prefix: [Name]" and it would change the name tag to "Prefix: Original Track Name". Quite useful. Doesn't seem to work anymore.
Is there a new way of doing the same thing?
-
Nothing's changed in this area recently, no.
Are you remembering the absolutely essential, leading "="...
=Prefix: [Name]
-marko
-
Nothing's changed in this area recently, no.
Are you remembering the absolutely essential, leading "="...
=Prefix: [Name]
-marko
:) Aha, of course I'd forgotten that essential part. It's been a while since I needed it. Thank you Marko, you're a gentleman and a scholar, much obliged!
-
You're welcome.
In case anyone's wondering, the "=" invokes MC's expression engine, so...
If you were to enter: Prefix: [Name]
then that is exactly what will be applied to your tag.
However, if you add an "=" to the front... =Prefix: [Name]
The expression engine is invoked, and MC will replace [Name] with the contents of the name tag of the current file. It's a system that offers a lot of power and flexibility as it can be used on multiple file selections and with any applicable expression function. (http://wiki.jriver.com/index.php/Media_Center_expression_language)
-
I'm getting really tempted to switch so it shows the new tag window by default and SHIFT switches back to the old window.
It's probably a terrible idea!
It is as far as I'm concerned. I just updated to 23. I really dislike this as the default. How exactly do I switch back to the version in 22? SHIFT doesn't do anything for me.
Edit: Nevermind ... figured out how to SHIFT back to the previous version. Thanks.
-
The old one won't exist forever, if you have tangible feedback for the new one, this is the time!
-
The old one won't exist forever, if you have tangible feedback for the new one, this is the time!
Thanks. I'm probably missing something. I just want to view tag fields that have values in them, like I could in the previous version. How do I do that, or how am I supposed to see that? I'm supposed to create a template for all the various tag views I have now, then remember and select the correct template for each file? Not all my music files use the same tagging scheme. So I'll end up seeing a lot of blank fields, or not seeing fields that have values.
-
Having a dropdown/tab on top of the other tabs that would dynamically include only the tags that have values would be an elegant solution I guess.
-
When you customize the tag window, just pick Add... > Add Fields With Values.
That should nicely make a populated fields listing.
-
Nice :)
-
New tag window seems like a huge improvement over the prior iteration. Thanks!