@HISEnberg Yes I do, but some very simple/small ones in a plugin and some much more complex in a standalone. None of them relying on a background task that having been said.
But in the standalone FFT analyser I remember fighting against a lot of instabilities so I used some flags here and there. I don't remember exactly, but probably flags preventing a repaint until the new FFT path is sure to be ready (because it wasn't a simple path, it took a lot of cycles to generate...)

@d-healey Hmmm… good point…

But since the original limit they give is 200/day, I’m pretty sure it’s not a monthly average and you trigger the security with the first newsletter

@Lindon said in How/Where do you actually market/sell your plugins?:

@ustk said in How/Where do you actually market/sell your plugins?:

Volume & Scaling
Current estimated volume: ~1,500 emails/day (will scale with user growth).

Here might be your problem:

Volume & Scaling
Current estimated volume: ~1,500 emails/day (will scale with user growth).

What transaction web site doing these:

Account verification emails (double opt-in)
Password reset links
Order/payment confirmations
Critical system notifications (e.g., security alerts)

needs this many per day straight out of the gate? You have clearly found some magic formula for subscription and sales...

I'm not selling for a long time, but the website and some communications are running for several years. So over the time I gathered 1500+ subscribers even if the real sell is just starting. So 1500/day is what I need, even if only once per month.

Of course, I don't need SES for the transactional emails, but since it has been advised online (by professionals) not to talk about marketing, transactional emails are the only thing I can speak about technically. And they are affirmative, they want technical explanation and I gave them everything I have, with several screenshots of the configurations.

I have pushed to a support yesterday, and the guy seemed to understand the situation and pushed it further for a new assessment. In the waiting I provided even more stuff, screen copy of the CRM, DNS config, hook links, verified badges, and also tested their bounce and complaint simulator so they see it works...

I am ready to receive any advice but they are staying silent, their "security politics" is to not give any clue on what you are doing bad... no assistance...

At this point I am not confident it'll change anything. So I'll probably hire someone on Fiverr specialised with SES and moving out of sandbox + email limit.

I haven't yet found another cheap system that is not relying on SES, except maybe SendGrid at 20$/m

WTF???

Second attempt to get out of the Sandbox mode in SES has been rejected and they don't give any reasons. Everything has been configured and all tests are working. 3 full days I'm on it to make everything compliant and here's the response, which is now definitive...

Hello,

This case was escalated for a secondary review. We appreciate your patience while we have reviewed your case.

I have thoroughly reviewed your account and the information you have provided so far. Although we appreciate your efforts to use Amazon SES, I am afraid we have come to the final conclusion that we are still unable to grant your request. We made this decision because we believe that your use case would impact the deliverability of our service. Unfortunately, for security purposes we cannot provide specific details that led to this decision.
We understand that you may not agree with the outcome, but we will not be able to assist you and there will be no further response to additional messages on this subject.

We appreciate your understanding in this matter.

We value your feedback. Please share your experience by rating this and other correspondences in the AWS Support Center. You can rate a correspondence by selecting the stars in the top right corner of the correspondence.

And here's my second attempt (plus screenshots of my system)

Dear AWS Support Team,

Thank you for your message regarding my previous application. I sincerely apologize for any shortcomings and appreciate the opportunity to clarify our use case further.

I hope this message finds you well. I am writing to kindly request production access for Amazon SES to support our platform’s transactional email needs.

Use Case & Justification

We operate XXXX, an e-commerce platform that relies on Amazon SES for time-sensitive, user-triggered communications, including:

• Account verification emails (double opt-in)
• Password reset links
• Order/payment confirmations
• Critical system notifications (e.g., security alerts)

Our emails are transactional and we strictly adhere to AWS’s best practices and anti-spam regulations (CAN-SPAM/GDPR).
We deeply respect our customers’ trust and never spam. Our reputation is our most valuable asset.

Technical Preparedness

To ensure deliverability and compliance, we’ve implemented:

• Full email authentication: SPF, DKIM, and DMARC configured and verified for our domain (xxxxxx.com).
• Unsubscribe mechanisms: Included in all applicable emails (where required by law).
• Double opt-in: For user registrations to prevent unsolicited emails.

Volume & Scaling

• Current estimated volume: ~1,500 emails/day (will scale with user growth).
• Sending reputation: We monitor bounce/complaint rates via Amazon SNS and keep them below 2% and 0.1% respectively.

Sample Email for Reference (screenshot attached)

---

Subject:
XXXXXX : Please Confirm Subscription

Body:
Click the button below to confirm subscription:

[Yes, subscribe me to the mailing list]#activate_link#

If you received this email by mistake, simply delete it. You won't be subscribed if you don't click the confirmation link above.

For questions about this list, please contact:
newsletter@xxxxxx.com

---

We deeply respect AWS’s policies and the trust placed in SES users. If further details or adjustments are needed, we’re happy to provide them. Thank you for your time and consideration.

Warm regards,

Now I feel just stuck and desperate and will just rant on whoever mf* decided this...

@DanH Though, neither hover nor clicked seem to react...

@DanH It should be obj.valueAsText instead of just valueAsText

And obj.hover instead of obj.over

@HISEnberg Perhaps something like this:

HiseSnippet 1642.3ocuX0saaaCElxNJowKcnEXWLrqD5UtCot1yoosXXHt1ItKXMIFwYAcXnHiVh1hvRjZRT0wan.CX2zWgd01qQuYuA6p8BrGg9FrcHorsjkSyhQWLRaLO+wuygmyGYamPtMIJhGhLJcx3.BxXCytiYB2VtXJCs+tHiO0rc6SNaDU31DaObPHOl4bBNZHp43.bTDwAYXT7oRqMVeEj5y61oI1CyrIyDgPmxo1jmQ8ohYR6z3anddswNjSn9ordqF6ayYs3d7X.YEMqhBf8FOfbHVZVASzWiibQFetYsG8Xa7V1OX6Zjs5ssyCc1tm8irq2GW24wO.WW80sqWuNxX08bnBdXWAVPhPFqzj6LtqKeDSuAmRin87HxE0PcgcVKtM2yQlhRonVtTOmNSJYQHHJclU.KpKfeh4ATG5T4yJj2RovZlGoKfFExBuhYfWszvqZJ3s.HYjBRqngzsM6ZGRCDyzHwyGYtOSPB6igyozPQaKpveWzrEGrfIp3iGRZGBKl5Q4sqVcSK3ut6WVBrJh6QpX6QvgkAAkfCuHg0KwgVPuiNdset0WYoZspLfH1qeehsn7c.0VSzemrd1uunCyCbZBH.2Zw8C3LXQ46nUOmO61ra5cYWZTfGdbyXX2B6B8R.tysko81B7FhQNeKWMigGmXnztiIXmDixhklO8Dvn8XCnLnzDRfy0rCPkAKjtDRFXEfEtoRUs4c.gpfBezoakHhPNoD1B640ChV49wLaAkyJe2R+bo0gHVwFTcDK0V4BAyoL.UY7fv8J3OSBm.GpCX45U06z8uuUK0taIbIZbQYpu2aZHKQYdPVYMYysRBtJij3HIcfJTpLIYOAaeFG.YSYjhfJ6lVe+8psoE7CzQcuZu.9cEIXVOwgPR.LBIjUh0KsdHQDGxfrHaUoizji4wB.WyJJCTnYPk9.KyS77JqYThpLxkJHx3MP5qV5Tk87fDUuYCp3DhGoPuLk1TUOjYPB3qUQB+ZJ39pjSpbelVk3rC4BxQImUPFXMup98WnNYaQH2yS1is.05Cv2iikYw98HgaB8kdwjoFB7CYIcLuXRmzbh15tzTFxY6ynhiBHrKhoDkzZCe6a2eWr.KYpRjA1EPBETIDL1k7R3dBMu05l6RhFJ3AJaSF8AlbgR6MmvpgYDODE3ttgotg.c9rqR9tFimsvowHpivcpfe37FtD5.2TWIQafxSfBT2bmXOrHKet7VuDEP8NCIpjnjEQEiSeq3GLR9+qP71lcnBa2EiwBK.ivox+GXL4pwaZp48mAvULa+7qg6AM06eIyID+pM+iMSeWPFXbXrelK.jCGFFPRkb4nwqMmMmEHYnBImv6.1WNB6G3QNFf+lV8731C6R+IR9gy.M5ZJsnrsKlAMwQKyL7p+mKX0d+mWZ1yAGfEgTX.xDpA56LakfNYMnfbTVutpbsrkoKg4nV7OvmDk0lVv.k0lnLEKvgDwHd3P0IUx2QFqIOV1vLRUjOq+40P.qMejb1mlz.CGNJYc3diCb4LpsTj1hIH8I9.8rXBbgmJdBl5I636FGAbTNGw5BFqdepQwSgSWUfWyDt2oBjHENj6.pVsM1FJrikz+xQIIsGz2RBqXOs+MCVyz.odnZF0xnN4Is5BGfZeEiF7fVihonA0cuxUvrYA8FsezoRsvMmnSks.x7QESo4ESfr1TdjMbgmjJ.kKGBIURodQPNk5qBjkpfF+ymPtO27y7Rj4Eygb9jVi8ftaG3o1J2mztzAGBfRn8e0oqfypCnrjpvLpqCvmOmra0nqfDHG.SSC2cHYjttjVprzspjDkfxEkcI8wwdhb6H58CosZjCRu9ulGR+9adyayCoF+p+eti9U5sCI+XLzsNdNb8KCWLt.4WBtd2N4KUUuhkpMT3x5X4TIJW7WbA6c6ft5mg.HthmgOEXBu1gDvzcgPZMyNt3nbXBgVx9pODXZU0qWlAo3+329r6+h2dwkoTLLlx2YkkZ4llXF1abDohTUdZEsKWS7Ix.eo7IoSn0LU+aWylRaX5KesuVS9LZhOWRNUHSNkgPy35nySGfknySB2lb9Per5V5k5Y6WKuovGaGxOyV+LIYc8FJIP6DScPst4Ax0V0Pub9r0m5POy1Nanx43WrrNVeYcbqk0wGrrNt8x53CWVGezk6n7+urmDK395m9ACDc1SOOarGCCupUMNh9W.KKnpjB

Here it is only the path generation that is handled in the bg, not the painting. But I reckon the painting already happens in the bg as it is not in sync with the message thread (I might be wrong though...)

Don't forget to handle the BG status and/or shouldAbort cases if needed

Oh and also it is not advised to talk about marketing anymore, despite of course it represent the vast majority of any company's emails... The focus should be on transactional emails... Being hypocrite seems appropriate sometimes

@Matt_SF Thanks Matt! I can see your point with the double opt-in, and I just enabled it for the subscribe popup

I might indeed ask for marketing help sooner or later

I can bet that SES made it more difficult recently for companies to apply. I just asked DeepSeek, and that chatty boy is way more technical, talking about SPF, DKIM, and DMARC and compliance with CAN-SPAM/GDPR, opt-in/opt-out mechanisms...

Now and with Dan's example I can surely write-up a message compiling everything (explanations & technical bits) that can work... Or will it?

@DanH Thanks! Very interesting indeed! Not technical, but at the same time very oriented toward respect of your customers and SES as well.

I think I will make a mix of yours and what claude AI suggested, adding the double opt-in.

@d-healey said in How/Where do you actually market/sell your plugins?:

most of my subscribers come through product purchases so I don't for those

I see I can set this in FluentCRM, I need to check how to to this for the popup, might be directly in the FleuntForms form...

You might ask ChatGPT for help with this.

I did, and claude AI. quite helpful, especially claude which gave me a good insight a minute ago

Where did you find it? Maybe i can find mine too.

I think about here: AWS Support > Your support cases

Also, do you advise for double opt-in email when someone subscribes? That would surely help email bounce, but it might prevent people from actually subscribing by adding extra steps...

@d-healey Yes I can still apply again. I have seen online other people having the same issue. And advices was given (not from amazon) regarding being way more technical, like even talking about DKIM, DMARC, SPF...
It appears talking about the bounce handling might be their major concern, but I don't know what I could say that is more specific about this.
I don't know where to start to be sure to hit the bull the second time, as I am afraid there might be no third attempt allowed... I'm trying to get real examples that worked

@d-healey said in How/Where do you actually market/sell your plugins?:

Install FluentCRM and FluentSMTP and combine it with Amazon SES.

Alright so I tried to configure this.
But I realised that for both getting out of the SES sandbox to get a production/live behaviour, and for leveraging the 200 email/day limit, I had to apply. I received a response today, both are denied...

Below is the application message I sent as requested.
Any idea what could have gone wrong?
What you guys did you do to get accepted?

Hello,

Please find below the required information regarding our email sending practices to assist in evaluating our sending limit request.

xxx is a brand focused on developing audio plugins for musicians. The emails sent include order confirmations, newsletters, and updates on existing or newly released products. These communications may contain general information as well as promotional content, such as discount coupons or sales announcements.

Email campaigns are managed through FluentCRM. Subscriber lists are maintained via both manual and dynamic segmentation. New subscribers opt in to receive newsletters and transactional emails either during the checkout process or via a "stay tuned" popup on our website.

Newsletters are sent approximately once per month. Promotional emails related to sales or coupons are sent during major holiday periods (e.g. Black Friday) or when a new product is released.

Bounce handling is managed through FluentCRM, which automatically segments and removes invalid addresses. Complaints are treated with high priority, and any customer requesting removal is manually unsubscribed. Additionally, all recipients have access to unsubscribe and preference management links in the footer of each email as well as in the customer account page.

An example email is attached for your reference.

Best regards,
Greg xxx
Owner, xxx

@DanH I agree that a button click that open the snippet and closes the window at the same time might be a nice option to have

@d-healey oh boy I you. I've started one as well but definitely more messy...

@DanH Snippets from where? If it in your clipboard already, pressing cmd/ctrl + shift + V will instantly open that snippet

Sooner or later, we'll need an exhaustive list in the doc for this plethora of pre-proc defs...
But a better integration would be a window with checkboxes and sub categories in the setting menu

@HISEnberg said in FFT Analyser Path - Need help drawing the magnitude to height:

does that just mean the Synth.deferCallbacks(true), or are you referring to the specific script?

Interface script should always be deferred. Included scripts are just part of interface so they inherit from it.
Scripts that are dealing with midi/audio shouldn't be deferred

@HISEnberg Maybe you could just try with the stock createPath to see if it's stable and if the issue is about UI drawing / message thread

Is your interface script deferred?

Long ago I had a lot of crashes doing that kind of things. It's now stable and I reckon I added extra security here and there.

Also when working with a buffer, I tend to create a copy to work with instead of the original. Afraid that another thread want access at the same time (I don't always know if the writeLock is set, so...)

@HISEnberg Have you checked the perf with the new profiler? This would help finding the bottleneck