Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Raise the 30,000 characters limit? (Read 2832 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Raise the 30,000 characters limit?

Hi guys,

I am having a long complex syntax to display in the default user interface (a custom column) and even after reducing function names to 2 letters and calling them instead of using tag names and reducing all other function names to 2 letters (to save characters) I get over 30,000 character count. The problem is, when the column has a syntax over 30,000 characters, it won't show anything, it will just be an empty field.

So the question is, would it be possible to raise the maximum character limit to some bigger number?  For my syntax, 50,000 would surely be enough. Or if you don't want to change it as the default, could you make it optional (like put in the preferences options a check to increase the count to 50,000 characters)?

Thank you, all the best.

Re: Raise the 30,000 characters limit?

Reply #1 –
I have the same issue with syntax to be put in bottom status bar - the formulas are too long and it does not display everything I have written.
 

Re: Raise the 30,000 characters limit?

Reply #2 –
When it comes to formatting code, a wishlist item:
Multi-line window allowing formatting with linebreaks and tabs (which are to be ignored during parsing).

(Of course it means you will have to ignore requests of parentheses-matching, syntax highlighting and the whole shebang, or at least an "open in external editor".)

Re: Raise the 30,000 characters limit?

Reply #3 –
All good. I did some cleaning and 30,000 will be enough 👍

Re: Raise the 30,000 characters limit?

Reply #4 –
Just to report - the 30k characters cap got lifted in the newest update 👌👌👌

Re: Raise the 30,000 characters limit?

Reply #5 –
Quote from: macak on
Just to report - the 30k characters cap got lifted in the newest update 👌👌👌
I'm honestly dying to know what the formula was that required 30k characters. I've had some long ones, but my longest is still only 2.5k chars.

Re: Raise the 30,000 characters limit?

Reply #6 –
Quote from: MordredKLB on
I'm honestly dying to know what the formula was that required 30k characters. I've had some long ones, but my longest is still only 2.5k chars.

lol it's so long because it uses many different tags (I just counted - 21 different tags - all of them custom). It is used to generate the title of the classical music works, so it has to use the tags that are specific to classical music only. But at the same time all 21 tags are must-have if you want to cover all possible variatiants that can arise and that do exist in the real world.

It's quite a deep rabbit hole, it required a lot of research and I had to start all over again several times because I would find an example that couldn't fit into the formula, so I would have to add a tag that is missing and start from the scratch 😤 (it's faster that way, trust me). This time finally it has everything it needs to have 🙌

So the goal is to display the title correctly every time with whatever combination of the tags is put in. So you just fill in the tags and you will get perfectly displayed title (perfectly in a sense of recommended by Apple Style Guide and if not defined there, then most often used (used mostly streaming services for reference), since there is no hard set rules in classical music). It adds uniformity to the library, makes tagging easier (duh), adds customizability (you have option to show/not show opus, featured instrument, key and tempo + adds some other customizability when having opus and catalogue numbers at the same time), and since the generated title is made of different tags, each one of them can be of different color (shade), so like Opus name is of one shade, key of other, work name of another, etc so it's not 1 boring ugly line of the same color + it's friendly with ReFacets where you can list all the tracks by tempo, key, opus, featured instruments, etc using their respective tags, while if it was only one title tag, that would be impossible/possible only in some cases. It also reads genre tag, so if you have like opera or ballet as the genre, it changes the generated title as in these cases the title is silightly differently formatted (but not if it containes word suite in the name). And also it's not finished yet (>95% finished, but I need to finish the testing since there are so many different possibilities). Although I did automate some of the testing, it still takes a lot of time 😫

PS: regarding character count, actually it still cuts when above 30k (I think i didn't test it properly), but it doesn't matter as it won't be above 30k for sure. The problem is, I have to have a test copy of the formula where every element like space, comma, dot,function, etc has a name assigned to it so that I can find the problem because if there is eg. in some variation a space where it shouldn't be, to find out wich one space is it i have to look at the copy with named elements and say oh it's this one (say 'space180') because otherwise I couldn't be able to find it since there are like 200 of them 😅
And that test sheet is above 30k chars because of the additional naming of those elements (i can get around it). But the main formula is under 27k, so it's ok

Re: Raise the 30,000 characters limit?

Reply #7 –
Sorry, it's 16 tags, not 21 (I officialy can't count) 🙄

Re: Raise the 30,000 characters limit?

Reply #8 –
Quote from: macak on
PS: regarding character count, actually it still cuts when above 30k (I think i didn't test it properly), but it doesn't matter as it won't be above 30k for sure. The problem is, I have to have a test copy of the formula where every element like space, comma, dot,function, etc has a name assigned to it so that I can find the problem because if there is eg. in some variation a space where it shouldn't be, to find out wich one space is it i have to look at the copy with named elements and say oh it's this one (say 'space180') because otherwise I couldn't be able to find it since there are like 200 of them 😅
And that test sheet is above 30k chars because of the additional naming of those elements (i can get around it). But the main formula is under 27k, so it's ok
@macak

As a result of your original message I tested character limitation of 30K within the various components of TF-ELP scripts and can confirm that at least within ELP the limitation is still very much there. I also code TF-PSS which has a limitation of 256K per script and there that limitation has not been lifted as well.

Out of curiosity what techniques you use to limit the size of the TF within foobar?

I code my stuff sitting in source text files with Notepad++ and use plenty of spaces, tabs, empty lines and lots of comments to keep things reasonably readable and understandable. Of course it bloats the code massively and in true TF fields things as comments and any newlines just don't work.

When I want to publish the source code to foobar TF, TF-ELP or TF-PSS I use macro's within Notepad++.
1) One macro strips TABS, spaces, newlines and comments  to create a TF singleliner from the source, which I then copy to the appropiate foobar destination, of course when you actually want to have a space in the singleliner you will need to use $char(32) instead of a space.
2) Another macro does the same but strips all two or more consecutive spaces to one single space.

Some examples:
TF-ELP sourcefile 34,294 bytes, resulting TF singeliner 24,454 bytes.
TF-PSS sourcefile 266,191 bytes, resulting TF singleliner 191,189 bytes.

PS. In ELP I also use some other techniques to be able to use more code than 30K in a single spot by publishing code in "functions".

Re: Raise the 30,000 characters limit?

Reply #9 –
Quote from: Defender on
Quote from: macak on
PS: regarding character count, actually it still cuts when above 30k (I think i didn't test it properly), but it doesn't matter as it won't be above 30k for sure. The problem is, I have to have a test copy of the formula where every element like space, comma, dot,function, etc has a name assigned to it so that I can find the problem because if there is eg. in some variation a space where it shouldn't be, to find out wich one space is it i have to look at the copy with named elements and say oh it's this one (say 'space180') because otherwise I couldn't be able to find it since there are like 200 of them 😅
And that test sheet is above 30k chars because of the additional naming of those elements (i can get around it). But the main formula is under 27k, so it's ok
@macak

As a result of your original message I tested character limitation of 30K within the various components of TF-ELP scripts and can confirm that at least within ELP the limitation is still very much there. I also code TF-PSS which has a limitation of 256K per script and there that limitation has not been lifted as well.

Out of curiosity what techniques you use to limit the size of the TF within foobar?

I code my stuff sitting in source text files with Notepad++ and use plenty of spaces, tabs, empty lines and lots of comments to keep things reasonably readable and understandable. Of course it bloats the code massively and in true TF fields things as comments and any newlines just don't work.

When I want to publish the source code to foobar TF, TF-ELP or TF-PSS I use macro's within Notepad++.
1) One macro strips TABS, spaces, newlines and comments  to create a TF singleliner from the source, which I then copy to the appropiate foobar destination, of course when you actually want to have a space in the singleliner you will need to use $char(32) instead of a space.
2) Another macro does the same but strips all two or more consecutive spaces to one single space.

Some examples:
TF-ELP sourcefile 34,294 bytes, resulting TF singeliner 24,454 bytes.
TF-PSS sourcefile 266,191 bytes, resulting TF singleliner 191,189 bytes.

PS. In ELP I also use some other techniques to be able to use more code than 30K in a single spot by publishing code in "functions".

Hi I had to google what those abbreviations are and i can tell you confidentely I have never tinkered with any of these (I just use default user interface 😃)

But I do use macros, but only to auto fill some tags during testing to save myself time from typing tag values manually and everything else i do manually

Cheers

Re: Raise the 30,000 characters limit?

Reply #10 –
Quote from: macak on
Quote from: Defender on
TF
TF-ELP
TF-PSS
Hi I had to google what those abbreviations are and i can tell you confidentely I have never tinkered with any of these (I just use default user interface 😃)

But I do use macros, but only to auto fill some tags during testing to save myself time from typing tag values manually and everything else i do manually
My post was about some tricks to keep the TF you put in foobar (DUI/CUI whatever) readable and maintainable and be able to cut down on total bytesize, because of the various limitations.

Re: Raise the 30,000 characters limit?

Reply #11 –
Quote
My post was about some tricks to keep the TF you put in foobar (DUI/CUI whatever) readable and maintainable and be able to cut down on total bytesize, because of the various limitations.

Oh I just split it in parts for better clarity (both the normal syntax and syntax for testing where everything is marked) and use lots of $puts/$get cause there are lots of functions that repeat themselves (otherwise the syntax would be wayyy too long) and thats basically it