Ah, OK. I figured it was user error on my part but am happ-ish to learn it isn’t but is due to a bug. I’ll be eagerly looking for the update.
Thanks for confirming that too, I was getting pretty frustrated tweaking it over several sessions trying to figure it out.
