Mixed Case case conversion capitalizes the second letter after straight quote

Support
1

Hi.

I’m trying to figure this out and I think I might have found a bug in the engine.

Applying a Mixed Case conversion on a TITLE tag when straight quote are present in the tag, will capitalize the second letter after the straight quote.

So, for example, let’s take the phrase:

sweet “beautiful cake” day

Just using Mixed Case Conversion on it will become:

Sweet “bEautiful Cake” Day

Attempting to regex around it was unsuccesful. The best I could get was:

Sweet “BEautiful Cake” Day

(EDIT: ) The expected behavior (as far as I know, the one I had worked around for so long) :

Sweet “beautiful Cake” Day

Unless I missed something, that’s a bug.

Using v3.32 on Windows 11.

Cheers.

EDIT 2:
Something seems to have changed between v3.32 and v3.33-b7 because it does not happen in the beta. But then decided to install a portable version of v3.32 and just try again on the same file I’d been banging my head on. Didn’t happen. I’m actually confused. Closed the portable install and ran my normal install and tried again. Didn’t happen.

I’m now even MORE confused.

So, I loaded the 2.5k+ opus files I was working on and tried again. Same result - it worked as intended. So, There’s something else, somewhere, happened, totally unrelated, that broke when I was editing all these files, continuing to apply various actions over and over, over these 2.5k files.

I’m entirely baffled…

2

It would need a screenshot of the function that you use to convert the case.
Or: does it work now?

3

I wish I could’ve taken a screenshot. It’s simple, though. It was straight up a “Convert Case → Mixed Case” action on TITLE only. The third text field was always left empty. There was nothing else in the chain.

Yeah, for some reason, it does now. I really don’t know what went wrong in the engine. Something broke that wasn’t related to the Actions but affected them.

EDIT:

I would like to add some thoughts to this thread.

I was using Bing Copilot trying to figure this out and nothing mentionned worked out. However, there was something that happened in the trial and error of this issue that happen. A regex expression inserted itself instead in the original string and replaces with it was supposed to fix.

The regex was:

$regexp(%title%,'(")([A-Za-z]+)','$1$lower($2)')

The full string in the title tag was (note that it wasn’t fixed - this string is the “corrected version”):

r⧸EntitledPeople “Serve Me First, Or I Start A Riot!” | Ep. 65

And the regex, searching to fix the second uppercase, has done the following (removing the unecessary parts):

[...] “$lower(s)Erve Me [...]

I think there was some extreme (memory?) corruption happening here to the point where the engine would just end up inserting itself. Additionally, I remember trying to around it by doing another actions chain by insert spaces around the straight quote (“), Capitalize as usual then remove the extra space added. It was a 3 steps thing. I imagine that, when doing a chain, it does them in order and, well, removing the spaces I added on step 1 at step 3 would faill for some reason…

By the way, my computer itself runs great and is stable. No strange bug outside of MP3tag really happened.

4

I think this was the problem.

5

I'm not sure if your regular expression is doing what you want it to do.

image
image1623×704 80.1 KB

It looks that it would search for a quotation mark, followed by a UPPER- or lowercase letter from A-z and if found, write the entire word in lowercase.
Note: The used regular expression checking website does not know the Mp3tag command $lower(). I have replaced it on the website with \L

Your example string
r⧸EntitledPeople “Serve Me First, Or I Start A Riot!” | Ep. 65
will NOT match, because the character “ in front of the word Serve is a
U+201C : LEFT DOUBLE QUOTATION MARK {double turned comma quotation mark}
and not the expected "
U+0022 : QUOTATION MARK {double quote}
used in the regular expression.

Update:
This regular expression would work better:
$regexp(%title%,'(“)([A-Za-z]+)',$1\L$2)
↑ ↑↑

Using the "correct" quotation character is crucial.

image
image660×405 11.9 KB

6

I know. But the thing is, when you are 1. terribly bad at programming and 2. don’t have the mind for it, 3. I certainly didn’t want to learn it because I never had that issue before (and also reason 1 and 2) and, 4. I wanted to do the job NOW. I didn’t want to wait days to get people to answer me on a forum.

The conversation was pretty long and I was already suspecting that it was hallucinating. And that’s why AI sucks and I want the bubble to pop.

I’m not surprised that it didn’t work. Like I said above, it was a long convo and I had my doubt about hallucinations already.

The exemple string was copied off the filename of my Opus file. Since I’m on Windows, Double Quotes is a forbidden character. So, the “Left Double Quotation Mark” were used to bypass that. I have a “Replace” function in the “Tag → Filename” function that replace any kind of forbidden filename characters. Before trying to fix this, I ran replace functions all over the 2.5k+ opus files TITLE tags to replace all unicode chars with the ASCII equivalents. Let me double check to make sure what I say is correct… finds and checks file and, yup, copy pasting the character in the tag into this website:

returns

QUOTATION MARK

So, yeah. The example string came from the Opus file I was trying to troubleshoot on.

Wait. No. This very forum changes my straight quotes to “Right Double Quotation Mark”. I just realized this. So, I might have copied and pasted from the tag but the forum changed it to “Right Double Quotation Mark”. I know this because if I copy and paste one of them that’s what I get in the website above. If I do SHIFT+2 (which is my input for QUOTATION MARK - the one used in operations) anywhere else, I get the character I typed and it’s not subtituted automatically. (Side note: I ABSOLUTELY HATE when any kind of software does this automatically for me, thinking that’s what I want. I’m looking at you Macs, iOS and this forum’s software!) (Side-side note: if you do a backspace after typing a quote on this forum software, it’ll change the “ back to ". Just found that out as well.)

In the end though, I knew something was wrong as I never needed to think about this ever. I knew that just using “Mixed Case” case conversion didn’t give me that behavior before. A program reboot fixed it but it means that it’s something rare happening in the background.