Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - hiccup

Pages: 12 3 ... 531
1
Visualizers / Re: CoolEdit Nostalgia visualizer
« on: June 16, 2024, 09:28:50 PM »
Impressive stuff, finally a nice plugin spectrum display for this player.  Thanks, kamen.
And now, a next challenge? ;-)
https://getmusicbee.com/forum/index.php?topic=23394.msg136636#msg136636

2
Questions / Re: High-Res audio albums
« on: June 16, 2024, 04:11:28 PM »
Go to options > tag(2) > highlighting (define rules)  > click ... > select bitrate / depth > grater> define youself.
Find icon you wont as a badge, then click icon square and select.
Good info.
Adding to it: that's for Tracks view, for Albums view you need to open Albums > Customise Panel and set highlighting rules there.
(these work independently)

PS
This is obviously not a Wish but a Question, so it probably will get moved.
It would also be good if you added something like 'icon' or 'highlight' to the subject title, since the current title is a bit vague.

3
Plugins / Re: Additional Tagging & Reporting Tools
« on: June 16, 2024, 03:30:06 PM »
$SentenceCase(string,sentence_separator) has only 2 parameters (i think all other parameters are senseless for it). i'check why simplest syntax (using only 1st parameter doesn't work for $TitleCase and $SentenceCase)

1.
I think it would be useful if there was an additional parameter where you can define a list of words (usually abbreviations) that should be in capitals.
(for things like BBC NYC USA III IV etc.)
Both $SentenceCase and $TitleCase should then have this.

2.
And a question about the possible variations of constructions:
Am I correct to understand that these would all be viable constructions:

$TitleCase(<Title>,param1,param2,param3,param4)
$TitleCase(<Title>,param1,param2)
$TitleCase(<Title>,param1,',param3,param4)
$TitleCase(<Title>,',',',',param5)

3.
Earlier I reported that the most basic variations: $SentenceCase(<Title>) and $TitleCase(<Title>) threw an exception.
It's working now, so there was probably something wrong on my side of things. Sorry for that.

4.
For anyone interested in testing this stuff, here's a silly title I currently use for testing that (I think) covers most challenges:

Code
adventures in the south of l.a.: the fight - a cat vs. the bee (guitar solo) {afx remix}
(I'm probably going to use this title as an example in the functions cheat sheet too, so please let me know if it's missing some specific 'challenge')

4
Plugins / Re: Additional Tagging & Reporting Tools
« on: June 16, 2024, 05:50:02 AM »
what would you expect to get using $Seconds($Now())?

Something like 79560132299

To be clear, I am not requesting for this to work, neither do I think entering something like 2024/06/16 06:57:00 as duration would be of much use.

My asking about this was simply a result of reading your explanation of the function, and taking it too literal.
Thinking that you meant you could enter date/time values like that, while you were probably only explaining the behind-the-screen workings of this function?

In reality users will probably have an existing <Tag> as duration, and don't have to worry at all about the date/time format it contains?

Since using <Time> already works perfectly, perhaps don't put in more of your time and effort in improving it in also getting dates to work?
It has never been requested, and I myself can't think of a realistic case it would be used by someone.

5
Bug Reports / Re: Toolbar Elements Overlaying Each Other When Full
« on: June 15, 2024, 03:33:16 PM »
I don't think this qualifies as an actual software bug.

The only thing I think that could be improved on is that when elements such as these are battling for the same available space, they don't overlap each other visually, but one of them gets truncated, indicated by …

Which is common practice in almost all applications (including MusicBee) for situations like this.
But since this involves graphics and not simply text, it's probably not very straightforward to address.

6
I can see a purpose in this, thinking that if it was available many users would use it.
But somehow I think it won't be implemented in MusicBee by the developer.
(I may very well get proved wrong though)

To me this seems something that could work very well as a plug-in for MusicBee.
I think it would be a very interesting and rewarding challenge for someone with plugin-coding talents and some taste in graphics design.

so from me:

+1 for having this functionality/improvement in MusicBee
+100 for a plugin that makes this possible

7
Questions / Re: WHat XE and XW stand for, when one Rips a CD?
« on: June 15, 2024, 02:29:44 PM »
Welcome to the forum MuzikBee

Those are country/region codes. (in this case Europe - World-wide)
Releases for different regions could e.g. have titles written differently.

8
Plugins / Re: Additional Tagging & Reporting Tools
« on: June 15, 2024, 01:01:54 PM »
This is probably more an academic question than something actually important, but still:

About $Seconds(duration)

Using a tag (such as <Time>) as duration makes sense to me and works great.

But your explanation on this function says this:
"$Seconds(duration): duration can contain both years/months/days AND hours/mins/secs parts, OR only one of these parts."

But when trying something (silly) as:
$Seconds(2024/06/15 01:01:30)
it throws an exception.
(for one, it probably doesn't like the forward slashes. Only using 01:01:30 works fine)

1.
Am I using the wrong syntax?

2.
Do you think this functionality is actually useful, and does it need to be present? (and thus explained?)
At the moment I can't think of using $Seconds like this, but maybe you or somebody else can think of a use-case for this?

edit:
3.
For what it's worth:
this:
$Seconds($Now())

and also this variation:

fails.

edit2:
Thinking this through a bit more:
For explaining this function, I could probably forget about any 'behind-the-screen-considerations", and keep it short and simple, something like this?:

$Seconds(duration)
(the tag containing the) 'duration' may contain yyyy/mm/dd and/or hh:mm:ss information

9
Plugins / Re: Additional Tagging & Reporting Tools
« on: June 15, 2024, 12:10:33 PM »
@Boroda

I'm working on updating the Virtual Tag Functions tables with new functions.

Can you confirm that in the first table, the new title- and sentence-case functions would be described as:

    name
     syntax
SentenceCase *$SentenceCase(string,lower_case_words,word_separators,lower_case_between_chars_opening_list,lower_case_between_chars_closing_list,lower_case_after_chars)
TitleCase *$TitleCase(string,lower_case_words,word_separators,lower_case_between_chars_opening_list,lower_case_between_chars_closing_list,lower_case_after_chars)

Or does SentenceCase perhaps have less or different 'switches' (can't find the correct term at the moment. Operators? Variables? > Parameters) than TitleCase?
(this Is STILL a tough NUT to cRaCk for ME ;-)


edit

Also, with previous plugin versions, the most basic variations such as:
$SentenceCase(<Title>)
$TitleCase(<Title>)
work.

But with 8.2 this now throws "Invalid naming template"?


edit2
And another thought:
Would it perhaps be a good idea to have three functions for capitalisation?

1.
SentenceCase(string)

2.
TitleCase(string)

3.
CustomCase(string,lower_case_words,word_separators,lower_case_between_chars_opening_list,lower_case_between_chars_closing_list,lower_case_after_chars)

It would make things much easier and accessible for (most) users requiring only the basic functionality, and yet also allow perfectionists to customise and tweak things to their personal needs?

10
Questions / Re: Disc Duration
« on: June 15, 2024, 11:44:16 AM »
Code
$DurationFromSeconds($Sum($Seconds(<Time>),<Disc tracks>))
Which will only require two virtual tags instead of three.
Nope, doesn't work.
There is some limitation on nesting with regards to the $Sum function.

11
Bug Reports / Re: error log help
« on: June 15, 2024, 08:03:01 AM »
Adding to sveakul's suggestion for things to try, a google search on the error message usually seems to point towards some database issue.
Maybe corrupted, maybe lack of disc-space, not sure.

You could see if you can revert to a backup version of MusicBee's database file, or rebuild it somehow?
I have no experience or actual knowledge on how to do such things, but a forum search is likely to give you some pointers on that.

12
Questions / Re: Disc Duration
« on: June 15, 2024, 06:42:31 AM »
Building upon the great solutions that Mayibongwe and Karbock have already provided, thanks to Boroda it is now possible to accomplish this with three virtual tags instead of four, but more importantly, much simpler formulas.
It requires the latest version of the Additional Tagging & Reporting Tools plugin (v8.2.8932)
(see here for a link to the first version that has this new functionality)

It (probably?) also requires MusicBee v3.6

These are the three virtual tags:

1.
Seconds
$Seconds(<Time>)

2.
Disc tracks
<Album><Album Artist><Disc#>

3.
Disc duration
$DurationFromSeconds($Sum(<Seconds>,<Disc tracks>))
 

13
Plugins / Re: Additional Tagging & Reporting Tools
« on: June 15, 2024, 06:35:54 AM »
default TimeSpan parser interprets "3:30" as 3 hours, 30 minutes. i've fixed this:
Thanks, working great now.

14
Plugins / Re: Additional Tagging & Reporting Tools
« on: June 14, 2024, 02:52:18 PM »
i've added 2 new VT functions:
$Seconds(duration): duration can contain both years/months/days AND hours/mins/secs parts, OR only one of these parts.
$DurationFromSeconds(seconds): should return minimal string representation of duration (obligatory including "hours" part), e.g. 00.01.00.00:00:00, or 00:01:00 (for 00/00/00 00:01:00)
Thanks for the very fast service!

Am I misunderstanding how $Seconds should be used?:
When I do:
$Seconds(<Time>)
for a track of 3:30 it outputs: 12600, which is 60 times the amount of seconds?
I was expecting to get 210?

15
Beyond MusicBee / Re: earliest release year
« on: June 14, 2024, 02:45:20 PM »
…as after further testing on the same test CD's from earlier it doesn't give a single year that is more accurate of different (in my case) so I guess I leave that plug-n of as it increases querying time more then 10x
That's odd. With my testing (CD1), without the plugin activated 10 songs are tagged to be in the 50's, and with the plugin it increases to 13.
Not a giant improvement, but still.
The slow down when using the plugin is indeed substantial. Especially for compilation albums.

I have slightly modified the earliest year script in this post.

To get the regular 'date' (MusicBee's 'Year') written with Picard's 'original year', add the following line to the bottom of the script.
(or create a separate script for it)

Code
$set(date,$if(%_originalyear%,%_originalyear%,%originalyear%))
Let me know if there is still something not working well?

PS
When using the Tag Inspector to check date/year values, be aware that you may see tags or values that were not written the last time you used Picard on them.
They can be older tags that were written before that, and were not deleted or overwritten later.

Pages: 12 3 ... 531