We're getting slightly different results. I don't get any message in system.log about being unable to use Personal Voices, and it writes a 4.1K file that plays nothing. I dl'ed your code, built it, and tried to save some personal voice speech, but got the same 4.1K file. (Also, note typo in Makefile, -e should be -o)

We're getting the same results, I also get a 4.1k emtpy file and it's not system.log, it's the streaming os log. -e is not a typo, it's the extra argument my code adds in order to not conflict with say command's -o argument. You need to use -e for my code to work and the file extension must be .caf, not .aiff or any other.

Air$ ./authorize_terminal Killed: 9 Air:$ DYLD_INSERT_LIBRARIES=./mysay.dylib say -v Chap "text to speak" -e path.caf say: invalid option -- e Usage: say [-v voice] [-o out] [-f in | message] (Have already authorized byt wanted to show the kill 9) FWIW I use bash but also tried zsh.

This means that the DYLD_INSERT_LIBRARIES isn’t inserting the library into the process and the authorize_terminal executable isn’t allowed to run either. This may happen if system security is set to full rather than reduced or if you haven’t enabled the arm64 ABI for Silicon Macs. I must have wrongly assumed that arm64 was enabled on your machine. What is the output if you type "arch" in terminal and press enter?

In any case, I have added x86_64 architecture to the project, so consider re-building it from github. Also, before trying to save to file, make sure that say -v YourPersonalVoice "some text" (without any options) does output audio to speakers. If not, try restarting your machine, I have noticed that PersonalVoice randomly stops working system-wide and needs a restart to fix this.

arch => arm64. Have rebuilt from github (but I'm definitely on M1 MBA). Have restarted (same experience w/random failures). say -v Chap Hello works correctly. Both authorize_terminal and DYLB say ... fail as before. Settings > Privacy&Security > Developer Tools > Terminal = allow/on. What have I missed?

(Transferred discussion to chat)

On M1 macs, there's a boot option for enhanced security, limiting access to protected memory addresses and other features. You might need to reduce or disable this security measure in order for hooking to work (therefore the dylib and unsigned binaries)

My nvram boot args are: nvram -p ... boot-args -arm64e_preview_abi amfi_get_out_of_my_way=0x1

To disable security, you can boot in Recovery mode , open terminal and type "csrutil disable" and reboot... or use the System Security menu in Recovery

or you might just need to do this step:

But still I wonder... if you followed my guide on your first post in order to authorize terminal, how did that terminal tool run without getting killed?

Good q. re: your authorize tool running successfully at first. Here is some "FWIW" info: the training function of Personal Voice has stopped working: when I get to the point where it's checking for a quiet environment, it listens to me read the sentence;

it seems to note that I've finished; the record button returns to its original state; and then nothing further happens: previously it would either complain of background noise, or proceed to record the first training sentence. I even created a new user and tried to create a personal voice, and the same thing happened.

Scratch the above. Sound input setting was set to Transcriptions Text to Speech, hence it wasn't hearing anything. Set it back to Mac Mic and all is well for training.