Project folder name that start with "0" is always deleted after relaunch on 24.2.1

[lawrenciumkan]

On Premiere Pro 24.2.1, my project folders naming with "0" at the start, the "0" is always deleted after relaunch. 

As I use only digits of date to name my folders, say Feb 27th is "0227", Jan 15th is "0115" the folder name after relaunch becomes "227", "115". It happens everytime I relaunch the project.

I also tested with different digits and naming, only when folders with "0" at the start and using only digits in the naming, the "0" will be deleted. If I use digits out of "0" at the start, or add other characters instead of only digits. For example, "20240119" for Jan 19th 2024, or "0225A" for Feb 25th Version A, or even with a hiphen "0221-2" for Feb 21st Version 2. These combinations won't affect any names after a relaunch, the screenshot is the examples. 

My current solution is to add a underline at the end of the folder name to avoid being deleted. And it never happened on 24.1 or previous version. Hoping for a fix. 

Spec: Premiere Pro 24.2.1, Mac Studio M1 Max 64GB. 

[Stan Jones]

I can confirm that a bin named with a zero at the beginning is renamed without the zero after relaunch. PR Release 24.2.1 and Beta 24.3.0.38.

I did not test for any other elements (all digits etc). I did not test with an earlier version.

Stan

[Ann Bens]

If you add a . (period) it will stick.

Might be a bug or might be by design?

@mattchristensen

[Stan Jones]

I tested in 23.6.4, and it does NOT drop the zero on relaunch.

Stan

[lawrenciumkan]

Probably is a bug, as it didn't happen on previous versions, including the 2024 Ver 24.1. I hope it's not a feature as it'll cause a lot of confusions and inconvenience. 

[AndyCollins]

Can confirm this is happening in 24.2.1. A bin labelled "001" will become "1" on reopening a project. However a bin labelled "00A" will remain as "00A" so it just seems to be if zeros are followed by other numerals.

[mattchristensen]

Thanks for reporting this, I can see it too. We'll get this fixed.

[andys80070523]

Thanks all! My first time posting something after all these years. I love the response time!

[Stan Jones]

This appears fixed in Beta 24.4.0.14.

Stan

[jstrawn]

Thank you for reporting this! The bug has already been fixed and can be found in a recent beta build, like PrPro 24.4 Beta 014 or higher. It will also be fixed inthe next public release of PrPro (after Pr 24.2.n).