Automation of pattrstorate vs Parameter mode/ paraminitmode?

Hi.

I've built a Max for Live plugin where the only thing I automate in Live is the preset number for a [pattrstorage] object. I'd rather be able to automate individual parameters also, but the two seem to cause too many conflicts, so I've settled on the preset-only approach, which is mostly working OK for me - essentially I just step through a bunch of presets over the course of my track.

I do have one issue though. It won't successfully recall the first preset I'm using. So I have an automation line that more-or-less just starts with preset 1 and then steps through sequentially 2,3,4 etc. However, it won't recall preset 1, despite an explicit automation point to do so. The only way I can get it to recall preset 1 is to have my automation briefly skip to another preset and back to 1, then it works correctly. It's kind of OK as a workaround, but not ideal.

Anyone know how I might sort this out? It occurs to me that it might be because I've set @parameter_enable 1 and @paraminitmode 1, as per the pattrstorage helpfile, which as I understand it embeds the presets in the device so they don't need to be saved manually (which in itself works fine and is definitely useful). I wonder if this is causing some sort of conflict?

The other thing to mention in case relevant is that I'm using a [preset] object to connect to the [pattrstorage] object, just as a front end within the plugin for saving and recalling presets. I wonder if this can cause any such issues - I also note that I have 'Save Preset in Patcher' enabled on this and wonder if this could also cause a conflict. Finally, I wonder if I'd get better results sending the automated preset number to the [preset] object rather than [pattrstorage].

Any ideas gratefully received! Thanks!