Skip to main content
Topic: Columns UI (Read 3749637 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Columns UI

Reply #7275
I am unable to reproduce into NG a frame behaviour I had in CP.
Apparently all the settings are the same.
I checked and the padding in the same too.

This is what I had in CP


And this is what I get in NG


Thanks

Re: Columns UI

Reply #7276
I guess you had frame-top and frame-bottom set to the (unselected item) background colour? That should still be possible.
.

Re: Columns UI

Reply #7277
As usual, you were right.

Now my frame style looks right
Code: [Select]
$if(%_isplaying%,
$set_style(frame-top,1,$get(text-play))
$set_style(frame-bottom,1,$get(text-play)),
$set_style(frame-top,1,
$ifequal($mod(%_playlist_number%,2),0,
$get(back-even),$get(back-odd)))
$set_style(frame-bottom,1,
$ifequal($mod(%_playlist_number%,2),0,
$get(back-even),$get(back-odd)))
)

If you know a simpler way, please let me know.

Thanks.

Re: Columns UI

Reply #7278
To get rid of an old track info mod panel (steal the focus) I'm trying to use
an Item Details panel. It's ok but:

- if I put it in "current selection" mode, when I select a playing track the time doesn't count.
- if I put it in "current selection/playing item" I loose the follow cursor behaviour
- in "current selction" mode, if I click on the most part of the UI items (Tagger panel, History, etc)
the panel goes blank and stays like that until I click on a track. The previously selected track
is still shown as selected but the tagging scripts are not applied.
If it's up to you, is it possible to have the Item Details panel keep on showing the last selected track info
until one click on another track, please? And to show the time running even in current selection when selecting the playing item?
And also not to loose the selection so that the scripts can be applied without having to select the track again.

Have a look.
https://vimeo.com/263958930


Thanks.


Re: Columns UI

Reply #7279
I think it should be possible to get the time etc. in there when the playing track is manually selected. I'll have a look at that.

In terms of how the 'current selection' stuff behaves, I'm afraid it's difficult to change as it's managed by the foobar2000 core. (I assume you haven't noticed any difference there in the Default UI.) There is the alternative of using the 'playlist selection' options instead of the 'current selection' ones (though I appreciate that might not do what you want either).
.

Re: Columns UI

Reply #7280
Another annoying thing I noticed is that "item details" panel goes blank
if you click on the tab of another panel placed in a panel stack and you
have to click acaing on the already selected track to see its info.
Old track info mod didn't do that and also "panel stack splitter" doesn't do that
and keeps on showing the track info (both in follow cursor mode).

If it is possible, I ask you to have a look into this matter
and see if this "Item details" panel behaviour can be fixed.

Thanks for taking the time to listen.


Re: Columns UI

Reply #7281
Well track info mod follows the focused playlist item rather than the selection of the focused child window. The closest thing in Items details is the playlist selection mode.
.

 

Re: Columns UI

Reply #7282
To me, the only lacking thing is a way to hide the "live" playing time
(always tied to the now playing item) when the playing item is not selected
or, even better, a way to know if the selected track is playing or not.

And what about the items panel going blank when you click on another UI element
as I described? Is it unavoidable or intended or fixable?

Thanks.

Re: Columns UI

Reply #7283
I was hoping to create a column to show missing items in the library with a fn similar to foo_uie_panel_splitter like the $findfile fn.

Anything like this possible. Thanks.

Re: Columns UI

Reply #7284
Hi!

What's the state of Columns UI these days? I see lots of commits on github for this year and 2017, but no releases whatsoever. The latest is still from 2016.
Why is this? What is this about?

Re: Columns UI

Reply #7285
I just haven't released a new version yet, but as you may have seen there is a fair amount of changes pending release.

The next version will be 1.0.0 alpha 1. There are a few things I'd like to tidy up before releasing it, and I'd prefer for foobar2000 1.4 to be out of beta.

So you'll have have to wait a bit longer for a new release, but if you're curious enough there are compilation instructions in the repo's readme.
.

Re: Columns UI

Reply #7286
Will you implement logarithmic volume slider? Thanks

Re: Columns UI

Reply #7287
Just wondering if there's any known performance issues between CUI's spectrum analyzer and WASAPI playback. The audio is fine, but the spectrum analyser is extremely choppy when outputting to any WASAPI device. I seem to recall there being a fix for this.

Re: Columns UI

Reply #7288
Will you implement logarithmic volume slider? Thanks
Are you referring to the fact that -10 dB isn't halfway at the moment? I can certainly fix that.

Just wondering if there's any known performance issues between CUI's spectrum analyzer and WASAPI playback. The audio is fine, but the spectrum analyser is extremely choppy when outputting to any WASAPI device. I seem to recall there being a fix for this.
I'm not aware of anything, and I didn't observe anything odd from some quick tests locally. Are any other visualisations affected? Does it happen with all tracks? What version of the WASAPI output do you have?
.

Re: Columns UI

Reply #7289
I'm not aware of anything, and I didn't observe anything odd from some quick tests locally. Are any other visualisations affected? Does it happen with all tracks? What version of the WASAPI output do you have?

WASAPI is v3.3
CUI is v0.5.1

Actually, I've just found that the issue seems to occur specifically with WASAPI event mode. Push mode seems to be ok, but push is somewhat unreliable with my hardware. Also, I created a new f2k profile with nothing but CUI and WASAPI, and the analyzer runs perfectly in either event or push mode, so its definitely something in my profile doing it. I'm actually puzzled because I'm not using any other visualizations or DSP's. Now that I know this I'm going to spend some tomorrow and figure it out. I'll let you know what I find out :D

Re: Columns UI

Reply #7290
Are you referring to the fact that -10 dB isn't halfway at the moment? I can certainly fix that.
Actually I was referring to this issue (not opened by me), but yeah, that would be nice if that could be fixed (didn't realize that before :) ). Thank you.

Re: Columns UI

Reply #7291
Hello Dear musicmusic,
I'm happy to use Columns UI, I really like it, thanks for your work!
And I would like to offer one improvement.
Could you realize the possibility of viewing the full contents of the MOD/XM sample list in the window "Item properties" of CUI as in XMPlay (See attach XMP pic).
Now all the sample text is not visible in the window only if you select the function properties (See attach Foobar CUI).
Perhaps you could add SMPL00, SMPL01 etc. as fields in item properties?
Hi!
I would prefer to add "Message" as field in item properties. However, the text of the message is not displayed completely (see attached pic).
Is it possible to expand in height the field for long messages?

Other:
filter by filesize works strange. For "KB" followed by "MB" then again "KB", while it should be in series (see attached pic)

Thanks.

Re: Columns UI

Reply #7292
Is it possible to expand in height the field for long messages?
Not using Item properties, but you could use Item details for that.

filter by filesize works strange. For "KB" followed by "MB" then again "KB", while it should be in series (see attached pic)
Do you mean sorting? The standard sorting doesn't understand file size units (also the inconsistent number of decimal places doesn't help). Custom sorting scripts exist to handle that situation, so if you enable 'Use custom sort script' for that column and use %filesize% for it (the file size in bytes) it should work. (Also make sure you're using NG playlist if you happen to be using Columns playlist, as I don't think the latter does the natural sorting that will still be required.)
.

Re: Columns UI

Reply #7293
Exactly, i meant sorting.
I did as you said and everything began to work as I wanted!
Look at this. It's great!
Thank you musicmusic!
By the way you didn't see my suggestion about display "dead" links ? I think it's possible for the CUI
Reply #23

Re: Columns UI

Reply #7294
Not sure if I saw that post, though there was a request on GitHub some time ago (perhaps you?) I don't have any plans to implement that directly in Columns UI. I'm also not sure it should be or it should be tied to a specific playlist view – if a title formatting field was provided, you could display it how you want. Perhaps it could be done in a separate component.
.

Re: Columns UI

Reply #7295
Not sure if I saw that post, though there was a request on GitHub some time ago (perhaps you?)
No, I didn't the request to GitHub.
Quote
... if a title formatting field was provided, you could display it how you want.
I could try to formatting title field accordingly. Сould you tell me what function (%...% or $...) informs about an error play a file? and how to use strikethrough font?

thanks.

Re: Columns UI

Reply #7296
Is it possible to expand in height the field for long messages?
Not using Item properties, but you could use Item details for that.
@musicmusic,
However, there are not visible metadata messages in some xm-modules even in Item details panel CUI. Only one character is visible - "."
As I understand, there is limitation of number characters display in a metadata message not more than 920 units in CUI element.
I think it is a bug and please fix it.
See attachment xm with more than 920 characters in the metadata message.

Thanks.

Re: Columns UI

Reply #7297
I could try to formatting title field accordingly. Сould you tell me what function (%...% or $...) informs about an error play a file? and how to use strikethrough font?

thanks.
It doesn't exist at present, I was merely giving a way it could be implemented independently of Columns UI.

However, there are not visible metadata messages in some xm-modules even in Item details panel CUI. Only one character is visible - "."
As I understand, there is limitation of number characters display in a metadata message not more than 920 units in CUI element.
I think it is a bug and please fix it.
See attachment xm with more than 920 characters in the metadata message.
For non-playing tracks it is fixed for the next version. For playing tracks, the behaviour apparently varies by file format and input component, but 'OpenMPT Module Decoder (kode54 fork)' seems to work fine for me.
.

Re: Columns UI

Reply #7298
I tried 'OpenMPT Module Decoder (kode54 fork)' component, in this regard the behavior is the same.
Anyway, thanks for the reply and I am looking forward to the new version Columns UI.

Thanks.

Re: Columns UI

Reply #7299
Neither foo_dumb nor foo_openmpt54 set long metadata on the dynamic track info, only possibly on the static metadata collected on track open.

I have considered making a minor patch to the subsong detection, to avoid listing subsongs that don't start on row 0 of a pattern, since this library indexes those, but that's another topic.

E: Yes, foo_dumb sets some metadata on dynamic info. But only playback position and status information, and pattern title changes on the %title% field.

 
SimplePortal 1.0.0 RC1 © 2008-2018