Topic: New Tag Window (Read 21691 times)

Awesome Donkey · « **Reply #50 on:** April 19, 2017, 09:47:10 am »

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.

marko · « **Reply #51 on:** April 19, 2017, 09:53:19 am »

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 :|

Matt · « **Reply #52 on:** April 19, 2017, 09:57:45 am »

Quote from: Matt on April 19, 2017, 09:11:35 am

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.

Awesome Donkey · « **Reply #53 on:** April 19, 2017, 10:15:14 am »

Groovy, thanks Matt!

Matt · « **Reply #54 on:** April 19, 2017, 10:23:18 am »

The new build is out, so please give it a test!

Thanks.

Awesome Donkey · « **Reply #55 on:** April 19, 2017, 10:26:37 am »

Yep, it fixes itself now, YAY!

marko · « **Reply #56 on:** April 20, 2017, 12:19:14 am »

Quote

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

Matt · « **Reply #57 on:** April 20, 2017, 06:16:21 am »

Quote from: marko on April 20, 2017, 12:19:14 am

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" />.

Awesome Donkey · « **Reply #58 on:** April 20, 2017, 06:20:49 am »

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!

Awesome Donkey · « **Reply #59 on:** April 20, 2017, 06:28:18 am »

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.

Matt · « **Reply #60 on:** April 20, 2017, 06:52:23 am »

Quote from: Awesome Donkey on April 20, 2017, 06:28:18 am

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

marko · « **Reply #61 on:** April 20, 2017, 11:00:51 am »

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

ferday · « **Reply #62 on:** April 21, 2017, 10:47:43 pm »

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.

Awesome Donkey · « **Reply #63 on:** May 12, 2017, 06:36:23 am »

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.

Awesome Donkey · « **Reply #64 on:** May 12, 2017, 07:01:13 am »

Also, is it possible to add SelectedText and HilightText colors support to <TAGWINDOW>?

P.S. <LIST> Also needs HilightText support.

tcpipkim · « **Reply #65 on:** August 27, 2017, 03:43:30 am »

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

Walt Whitman · « **Reply #66 on:** August 27, 2017, 04:06:35 pm »

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.

Birdsrule17 · « **Reply #67 on:** August 28, 2017, 03:10:48 pm »

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].

Awesome Donkey · « **Reply #68 on:** August 28, 2017, 03:47:35 pm »

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.

BillT · « **Reply #69 on:** August 28, 2017, 04:04:51 pm »

[varies] implies that you have more than one file selected, with different last played times.

Birdsrule17 · « **Reply #70 on:** August 28, 2017, 04:40:48 pm »

Quote from: Awesome Donkey on August 28, 2017, 03:47:35 pm

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.

Birdsrule17 · « **Reply #71 on:** August 28, 2017, 04:43:03 pm »

Quote from: BillT on August 28, 2017, 04:04:51 pm

[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.

Birdsrule17 · « **Reply #72 on:** August 30, 2017, 08:31:17 am »

So apparently 23 only lists when an individual track was last played, not an entire album. That's something I'm not used to.

BillT · « **Reply #73 on:** August 30, 2017, 11:33:29 am »

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.

badger · « **Reply #74 on:** August 30, 2017, 02:27:18 pm »

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.

Matt · « **Reply #75 on:** August 30, 2017, 02:53:30 pm »

Quote from: badger on August 30, 2017, 02:27:18 pm

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.

Birdsrule17 · « **Reply #76 on:** August 30, 2017, 02:58:06 pm »

Quote from: BillT on August 30, 2017, 11:33:29 am

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.

Matt · « **Reply #77 on:** August 30, 2017, 03:09:17 pm »

Quote from: Birdsrule17 on August 30, 2017, 02:58:06 pm

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.

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.

Birdsrule17 · « **Reply #78 on:** August 30, 2017, 03:19:52 pm »

Quote from: Matt on August 30, 2017, 03:09:17 pm

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.

DJLegba · « **Reply #79 on:** August 30, 2017, 03:20:03 pm »

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.

Birdsrule17 · « **Reply #80 on:** August 30, 2017, 03:30:49 pm »

Quote from: DJLegba on August 30, 2017, 03:20:03 pm

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!

SkGe · « **Reply #81 on:** August 31, 2017, 02:53:03 pm »

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.

dtc · « **Reply #82 on:** August 31, 2017, 03:43:25 pm »

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.

ferday · « **Reply #83 on:** August 31, 2017, 06:20:56 pm »

Hi dtc

Please clarify. I have calculated tags in the new window, I must not be understanding

dtc · « **Reply #84 on:** August 31, 2017, 09:32:13 pm »

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.

Matthew1968 · « **Reply #85 on:** October 14, 2017, 02:49:12 am »

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. 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?

marko · « **Reply #86 on:** October 14, 2017, 03:04:10 am »

Nothing's changed in this area recently, no.

Are you remembering the absolutely essential, leading "="...

=Prefix: [Name]

-marko

Matthew1968 · « **Reply #87 on:** October 14, 2017, 07:44:29 am »

Quote from: marko on October 14, 2017, 03:04:10 am

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!

marko · « **Reply #88 on:** October 14, 2017, 11:06:20 am »

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.

CalJake · « **Reply #89 on:** October 18, 2017, 08:40:36 pm »

Quote from: Matt on April 19, 2017, 06:57:00 am

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.

Hendrik · « **Reply #90 on:** October 19, 2017, 04:28:16 pm »

The old one won't exist forever, if you have tangible feedback for the new one, this is the time!

CalJake · « **Reply #91 on:** October 21, 2017, 02:12:50 pm »

Quote from: Hendrik on October 19, 2017, 04:28:16 pm

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.

tyler69 · « **Reply #92 on:** October 21, 2017, 02:35:04 pm »

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.

Matt · « **Reply #93 on:** October 21, 2017, 02:36:44 pm »

When you customize the tag window, just pick Add... > Add Fields With Values.

That should nicely make a populated fields listing.

tyler69 · « **Reply #94 on:** October 21, 2017, 02:38:51 pm »

Nice

Axedall · « **Reply #95 on:** October 22, 2017, 11:00:04 am »

New tag window seems like a huge improvement over the prior iteration. Thanks!

INTERACT FORUM

Author Topic: New Tag Window (Read 21691 times)