Converting roast alog to new profile triggers Modified Artisan Profile and loadBackground fails

[tjohnson250]

Problem Description

On Artisan 4.2.0, using Designer to turn a prior roast into a background profile results in “Modified Artisan Profile. Load it anyway?” when loading the profile in the Background window. loadBackground from a button claims the background is loaded, but fails.

Sample_edited_profile.alog.txt
Sample_prior_roast.alog.txt

Steps To Reproduce

In Artisan v4.2.0/latest:

1. File → Open an existing roast .alog to create a modified background profile
2. Tools → Designer
3. Modify DROP temperature slightly
4. Exit Designer
5. File → Save As new .alog
6. Roast → Background → Load that newly saved .alog

Result:

2026-07-03-TRJ-artisan-settings.aset.txt

When using loadBackground() on a button, Artisan reports loading, but the background is not loaded

Expected:
A profile saved by the same Artisan version should load as background without validation warning.

Artisan Version

Other - include in Description

Computer OS and Version

Mac Tahoe 26.3 and Windows 11 25H2

Connected devices or roasting machine

Artisan 3e

Files

• A sample profile *.alog file, renamed to *.alog.txt is attached.

• A settings file (Help>> Save Settings) *.aset, renamed to *.aset.txt is attached.

• Screenshots are attached.

• No files are attached.

[MAKOMO]

Dear Todd,

Thanks for this report. Artisan v4.2 computes and adds a check-sum over the content of an alog file before writing. On loading alog it verifies that this check-sum is valid. Any modification of the file content outside of Artisan invalidates this checksum.

We can confirm that the file Sample_edited_profile.alog.txt you attached does not validate on loading.

We followed your steps to reproduce your issue using the settings file and the original file Sample_prior_roast.alog.txt you provided and could not reproduce the issue on any of the supported platforms, including macOS ARM you are using. Note that any manipulation of the data inside of Artisan, like using the Designer, should still produce a valid file with a correct check-sum as it gets written through the standard Artisan save-file mechanism.

Could you please verify that you can reproduce the issue using the steps you listed above?

Best,
Marko

[tjohnson250]

More information and files. On my mac, I loaded a prior roast (attached below) as the background curve using Roast->Background->Load. I did not get the Modified Artisan Profile warning. I next opened the same roast in Artisan using File->Open, Entered Designer and checked Used Landmarks Only, exited designer, Used Save as to save to the second file below. When I use Roast->Background->Load I get the warning about the modified artisan profile. Note that PID settings shown in the file names will not match those in the settings file above.

Saved after Designer 3e.0.Equality Peru Warmikuna Women's Medium Roast 430 F (1.25 kg PID, 3.9, 6, 60, t-10)_26-07-04_1141.alog.txt
3e.555.Equality Peru Warmikuna Women's Medium Roast 430 F (1.25 kg PID, 3.9, 6, 60, t-10)_26-06-19_2118.alog.txt

[MAKOMO]

Followed the process you described step-by-step but again couldn't duplicate the issue. However, replacing "Save As" by "Save a Copy As" I could reproduce. I found the cause for this and will fix this as soon as possible.

Thanks for your report!

[MAKOMO]

This one is fixed. I made you a signed build for macOS ARM to test:

https://github.com/artisan-roaster-scope/artisan/releases/tag/v4.2.1-beta1

[tjohnson250]

I just tried the version above, but as soon as I load a past roast I get the spinning wheel and have to force quit the app. I can send the crash report if that helps, but it is quite long.

[MAKOMO]

Strange as nothing did change here about loading, only a small change (fix) was applied to saving of files.

Yes, please attach the crashlog. Please also attach an artisan .alog file that fails to load (all your previous attached files load quite file for me using that build). Could you please also bring Artisan into debug mode before the hang (hold OPTION & COMMAND keys while clicking on the plus icon in the upper left corner to toggle the debug mode) and attach (or send by email) your artisan log files (hold only the OPTION key while clicking on the plus icon and an email should open with those files attached)?

THANKS FOR YOUR SUPPORT!

[ayovev]

Dear Todd,

Thanks for this report. Artisan v4.2 computes and adds a check-sum over the content of an alog file before writing. On loading alog it verifies that this check-sum is valid. Any modification of the file content outside of Artisan invalidates this checksum.

We can confirm that the file Sample_edited_profile.alog.txt you attached does not validate on loading.

We followed your steps to reproduce your issue using the settings file and the original file Sample_prior_roast.alog.txt you provided and could not reproduce the issue on any of the supported platforms, including macOS ARM you are using. Note that any manipulation of the data inside of Artisan, like using the Designer, should still produce a valid file with a correct check-sum as it gets written through the standard Artisan save-file mechanism.

Could you please verify that you can reproduce the issue using the steps you listed above?

Best, Marko

@MAKOMO Just curious, what is the significance of the checksum in this specific context, and what does invalidating it actually mean as far as being able to load other people's profiles into your Artisan instance? Does that mean if a user modifies a profile on their machine outside of Artisan, they wouldn't be able to give it to someone else to use and follow?

[roasterdave]

@ayovev All sorts of errors and subtle problems can be introduced when an artisan log is manually edited outside the application. We have seen and chased such issues many times. The checksum highlights when a profile has been modified.

You certainly can share profiles edited outside artisan. Open it in artisan (File>> Open). If the file was edited outside of artisan answer Yes in the confirmation window.

If the profile loads properly, immediately save it (File>> Save). The file will be rewritten and the checksum will be properly updated. Now the profile will open without the warning and will also load successfully as a background profile.

[ayovev]

@roasterdave Ah ok, that's great clarification; thank you!

[MAKOMO]

Found the regression causing the non-termination and fixed it. New beta build is available.

[Brewzologist]

I'm having this same error in v4.2.0 on a Windows 10 machine. Every time I open any profile I get this message. I also opened, saved and immediately reopened and still get this message. Is it fixed in the latest beta build? Thank you, Steve.

Note: I do use the feature that saves a PDF along with my .alog if that has anything to do with it.