Char length or type limits -- title roast properties

[prmango43]

What I thought was a W11Pro problem ended being I apparently exceeded char length or type limits
in the roast properties title bar. This caused graph time axis to be compressed by about 40% on output.

[roasterdave]

I cannot reproduce this with a roast title over 360 characters in length. What version of artisan are you running? It will help if you post both this alog file and your settings file (Help>> Save settings). Add a ".txt" suffix to both files then drag them onto a reply on this web page (email replies don't handle attachments well). I will take a look.

[prmango43]

My BAD!! Discussion text should have been ".... This caused graph.jpeg time axis to....." Not "..... This caused graph time axis to..."

Problem is not the roast profile graph -- problem is the graph.jpeg/png output after using that long line of text as Title name when replacing "Roaster Scope." I did follow the reset procedure as suggested, but nothing changed. So it appears that the input text line has embedded(??) chars somewhere. Truly regret wasting everyone's including my time. This discussion can be dropped/deleted as applicable. Again, thanks.

[roasterdave]

Yes, that is quite different. However, I still can not reproduce the compression. Can you tell me step-by-step how you are saving to an image file?

[prmango43]

Steps & text below. Can you please provide char length and type allowed to name the roast properties (Title) --TIA. BTW, text has 230 char, 41 spaces , and 3 hidden symbols identified as being the 3 dashes. Another test -- after pasting text in the Title bar, I replaced 3 instances of "space, dash, space" with 1 space each and no change -- still compressed graph.jpg time axis. Laptop or PC work station, results when pasting full text is same -- compressed graph.jpg time axis. Questions??

1 -- On Laptop -- saved roast original with app default name -- closed app
2 -- On PC -- opened app and loaded copied saved roast file -- can be done with empty log too
3 -- go into menu roast>properties -- or L-click near L axis
4 -- open text file, copy full text and paste in Title bar to overwrite Roaster Scope -- hit OK

At this point user can save log or not -- doesn't matter.

5 -- in app menu File>save graph (jpeg or png) any name useful if testing -- as long as full text was pasted in Title bar the same result, compressed graph.jpg output. Have been using jpg, but tested png same results.

OR

6 -- #5 but shorter name; edited text after pasting and overwriting Roaster Scope -- I used El Salvador Pacamara -- in this case 20 char, graph.jpg output not compressed.

El Salvador Premium Chalatenango – Saul Murcia – Finca Las Ventanas – Pacamara Honey Arr 10/29/25 Lot 0248 1375 MASL Oscar Aguilar Variety Pacamara HG/LG Arrival Date: 10/29/25 Lot #: 0248 Origin: Chalatenango Processing Method: Honey Altitude 1375 MASL Variety Pacamara
EOF

[prmango43]

Spent about some time tonight testing what number of chars would cause the compression. 135 characters including a carriage return seems to be a limit (??), where in order to accommodate more text (>135 chars) for the Title name the graph.jpg output is moved to the left in the output window an equivalent amount of extra space (chars).

[roasterdave]

Thank you for the additional information. I have not been able to reproduce what you see with images but I did find something related with vector drawings. The compression appears to be sensitive to both the window size and the length of the title. I am investigating this issue now. Thanks for your patience, it may be a little while before it is resolved.

Can you please provide char length and type allowed to name the roast properties (Title)

There is no particular restriction for what you can place in the Roast Properties Title field. The length is limited to 32,767 characters (including the characters used to encode UNICODE characters). When artisan generates a file name from the Title, artisan will filter out the nine reserved characters <>:"/|?* to avoid Windows errors. Aside from this filter, artisan hands the file name to Windows as it is. From then on the limitations are with Windows.

To learn about the Windows file name length and character limitations have a look at this resource.
https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file

[MAKOMO]

Should be improved in the current Continuous Build. Thanks for reporting!

[prmango43]

YW -- guess this can be closed??

[roasterdave]

Do you you find it is working now when saving to PNG or JPG? I was never able to reproduce the problem with images, but was able only in some cases with vector drawings. If it is working for you it can be closed.

[prmango43]

The problem was noticed accidentally when I inadvertently copied/pasted the wrong line of text. So I don't feel urgency to test the build and rather wait tilll the next production version is out. If Artisan needs the build tested that will take some planning as I'm pressed. In a few days I can probably squeeze time to check if my sandbox is OK and test the build. BTW, which build forward?? (never mind -- 4.2.1)

[prmango43]

Did my sandbox test and even with the full original test (>170? chars) and png or jpg graph output there was no compression. So build is working -- at least for this test case.

[MAKOMO]

Excellent! Thanks for reporting and taking those extra steps to verify that our change improves the situation. I will close the issue. The fix will be in the next release which should appear this October.