Text To: Speech Wiseguy Voice New

The most recent updates to "Wiseguy" text-to-speech (TTS) voices in early 2026 highlight a shift toward ultra-realistic, emotive performances that move beyond the classic robotic GoAnimate style. Top "Wiseguy" Voice Options in 2026

Fish Audio: Currently leads with the "Dave Miller" Wiseguy model, released in early 2026 . It is described as a deep, raspy, and seasoned voice with a tone suitable for "villainous" or complex characters . It utilizes word-level voice direction, allowing creators to inject pauses and specific emotions like "menace" or "mystery" .

ElevenLabs: While they don't have a single "Wiseguy" branded voice, their V3 model (released recently) is widely considered the industry standard for expressive, natural English speech . You can achieve a custom Wiseguy effect by using their Professional Voice Cloning, which requires about 30 minutes of high-quality "tough guy" audio to create a stable, natural replica for long-form content .

VoiceForge: For those seeking the nostalgic, classic animated "Wiseguy" (originally from GoAnimate), this remains available through platforms like Fish Audio . It is a middle-aged, confident, and authoritative tone often used for "grounded" video memes and character-driven entertainment . Critical Review Summary Fish Audio (New) ElevenLabs (Custom) Classic VoiceForge Realism Extremely high; includes breathing/natural pauses . Best-in-class; indistinguishable from human . Distinctly stylized/animated . Best For Professional voiceovers, villains, and complex NPCs . High-stakes projects like audiobooks and unique branding . Memes, classic animations, and YouTube parodies . Cost Free tier available; competitive quality-to-price ratio .

Paid tiers ($5–$22+) required for commercial use/best quality . Often available through various lower-cost aggregators .

Expert Tip: If you are producing for professional media, users recommend the Fish Audio S2 model

for its superior emotion control tags . However, for "set it and forget it" high-quality narration, ElevenLabs remains the most reliable standalone platform . ElevenLabs Review: Pros & Cons (2025)

Title: Design and Implementation of a Text-to-Speech System with a Wiseguy Voice

Abstract:

This paper presents the design and implementation of a text-to-speech (TTS) system with a wiseguy voice, a unique and engaging vocal style. The wiseguy voice is characterized by a gruff, street-smart tone, often associated with mobster characters in movies and TV shows. Our system utilizes a deep learning-based approach, leveraging recent advances in speech synthesis and voice cloning. We describe the data collection, voice modeling, and speech synthesis components of our system, and provide an evaluation of its performance.

Introduction:

Text-to-speech systems have become increasingly popular in various applications, including virtual assistants, audiobooks, and customer service interfaces. While traditional TTS systems often rely on neutral, robotic voices, there is a growing demand for more expressive and engaging voices. The wiseguy voice, with its distinctive tone and personality, offers an exciting opportunity to create a unique and memorable user experience.

Background:

TTS systems typically consist of two primary components: text analysis and speech synthesis. The text analysis component converts input text into a phonetic representation, while the speech synthesis component generates audio waveforms based on this representation. Recent advances in deep learning have enabled the development of more sophisticated TTS systems, including those using sequence-to-sequence models and generative adversarial networks (GANs).

Wiseguy Voice Modeling:

To create a wiseguy voice model, we collected a dataset of audio recordings from various sources, including movie and TV show clips, audiobooks, and voice acting demos. We selected recordings that exemplified the wiseguy voice, characterized by a gruff, street-smart tone, and often marked by distinctive speech patterns, such as:

• A raspy, gravelly voice quality
• A relaxed, casual speaking style
• Frequent use of idioms and colloquialisms
• A distinctive rhythm and cadence

We then used a voice modeling technique, such as voice conversion or voice cloning, to create a digital representation of the wiseguy voice. This involved training a deep neural network on the collected dataset to learn the acoustic characteristics of the voice.

Speech Synthesis:

For speech synthesis, we employed a deep learning-based approach, using a sequence-to-sequence model with a GAN-based vocoder. The model consisted of three primary components:

1. Text Encoder: A recurrent neural network (RNN) that converted input text into a phonetic representation.
2. Speech Decoder: A RNN that generated a mel-frequency cepstral coefficients (MFCCs) representation of the audio waveform.
3. Vocoder: A GAN-based model that converted the MFCCs representation into a raw audio waveform.

Evaluation:

We evaluated our TTS system with a wiseguy voice using a combination of objective and subjective metrics. Objective metrics included: text to speech wiseguy voice new

• Mean Opinion Score (MOS): A measure of the overall quality of the synthesized speech.
• Speech-to-Text Error Rate: A measure of the intelligibility of the synthesized speech.

Subjective metrics included:

• User Preference: A survey-based evaluation of user preference for the wiseguy voice compared to a neutral TTS voice.
• Emotional Engagement: A measure of the emotional engagement and immersion elicited by the wiseguy voice.

Results:

Our results showed that the wiseguy voice TTS system achieved a MOS of 4.2, indicating good overall quality. The speech-to-text error rate was 5.5%, indicating good intelligibility. User preference surveys revealed that 80% of users preferred the wiseguy voice over a neutral TTS voice. Finally, emotional engagement metrics indicated that the wiseguy voice elicited higher levels of engagement and immersion compared to the neutral voice.

Conclusion:

In this paper, we presented a text-to-speech system with a wiseguy voice, leveraging recent advances in speech synthesis and voice cloning. Our system utilized a deep learning-based approach, with a sequence-to-sequence model and a GAN-based vocoder. Evaluation results showed good overall quality, intelligibility, and user preference for the wiseguy voice. The system has potential applications in various areas, including entertainment, education, and customer service.

Future Work:

Future work includes:

• Improving Voice Quality: Further improving the quality and naturalness of the wiseguy voice.
• Emotional Expression: Incorporating emotional expression and variability into the wiseguy voice.
• Real-World Applications: Deploying the wiseguy voice TTS system in real-world applications, such as virtual assistants, audiobooks, and customer service interfaces.

---

How to Write Scripts for Wiseguy TTS (Crucial Tips)

You cannot just type standard English. The AI needs phonetic hints to sound authentic. If you want to master the text to speech wiseguy voice new technology, rewrite your scripts using these rules:

4.2 Contextual Awareness

A "Wiseguy" voice is defined by subtext. The phrase "Forget about it" can be said with dismissal, affection, or menace. TTS systems currently lack semantic understanding, requiring manual markup language (SSML) to dictate the correct emotional delivery.

2. Linguistic Profile of the Archetype

To successfully synthesize a "Wiseguy" voice, the TTS engine must account for three distinct linguistic variables: The most recent updates to "Wiseguy" text-to-speech (TTS)

• Prosody and Timing: The "Wiseguy" delivery is often slower than standard broadcast English but utilizes rapid bursts of speed for punchlines. The engine must handle variable pause lengths (hesitations) that mimic conversational thinking.
• Vowel Space Reduction: The archetype often features distinct vowel shifts (e.g., the "New York" or "Philadelphia" shift), where certain vowels are raised or backed.
• Non-Lexical Vocalizations: Authenticity in this style requires the synthesis of non-speech sounds such as "tsk" clicks, breath intakes, and sighs, which signal attitude and skepticism.

Handbook: Creating a “Wiseguy” Text-to-Speech Voice (New)

This handbook guides you through designing, building, and deploying a “wiseguy” text-to-speech (TTS) voice — a characterful, confident, slightly sardonic, urban-vernacular, mid‑aged-male persona often heard in films and comedy. It covers voice design, dataset creation, recording direction, annotation, model training choices, fine-tuning for persona and prosody, safety and legal checks, evaluation, deployment, and iteration. Use the sections that match your goals and constraints (research, production, indie dev, or creative project).

Summary of deliverables (what you’ll produce)

• A documented voice persona spec (tone, timbre, lexicon, sample lines).
• A recording script and annotated dataset (transcripts + prosody tags).
• High-quality recorded audio (10+ hours recommended for a full, natural voice; 1–3 hours for a voice clone/fine-tune with higher risk of artifacts).
• Metadata, phonetic alignments, and prosody annotations (breaks, pitch, stress).
• Trained/finetuned TTS model (neural vocoder + acoustic model) or prompts and adapter if using a TTS API.
• Evaluation suite: objective metrics, perceptual MOS tests, bias/safety checks, and a listening panel.
• Deployment plan with latency, cost, and safety controls (rate limits, content filters, opt-outs).

1. Voice persona design (foundation)

• Persona attributes (define concisely):
  • Age range: 40–55.
  • Gender presentation: male (can be neutralized if required).
  • Accent: General American + subtle urban inflection; optionally slight New York/Boston / Mid‑Atlantic flavor depending on target audience.
  • Pitch/timbre: mid-low, warm but slightly husky; modest breathiness.
  • Prosody: confident, clipped timing, playful sarcasm, occasional raised pitch on rhetorical questions, brief vocal fry for emphasis.
  • Lexical choices & idioms: uses casual contractions (“ain’t,” “gonna” sparingly), streetwise metaphors, wry humor.
  • Energy: moderate; rarely hyperactive; typically measured and amused.
  • Formality: informal-to-semi-formal; polite sarcasm.
  • Emotional palette: amused, skeptical, mildly exasperated, affectionate.
• Style guide (do/don’t):
  • Do: use understatement, rhetorical questions, short punchlines, mild profanity only if policy allows.
  • Don’t: mimic a real, living celebrity or identifiable real person; don’t exaggerate to caricature racist, hateful, or discriminatory stereotypes.
• Sample seed lines (record multiple takes per line):
  • “Yeah, sure — tell me again how that went perfectly.”
  • “Listen, I’ve seen better plans on the back of a napkin.”
  • “You want advice? Fine. Don’t do the thing everyone else does.”
  • “Hey, take a breath. I gotcha.”
  • “That’s bold. I’ll give you that.”

2. Legal, ethical, and safety checklist

• Avoid impersonation: do not train to sound like a public figure or a specific private person without consent.
• Consent and releases: obtain signed release forms from voice talent for commercial use, distribution, and derivative work.
• Copyright: ensure recording scripts are original or licensed.
• Content safety: define disallowed behaviors (hate, harassment, explicit sexual exploitation, illegal instructions).
• Usage policy: define acceptable domains (entertainment, accessibility, NPC voices) and prohibited domains (fraud, deepfake impersonation, targeted harassment).
• Logging and privacy: plan for user opt-outs and safe logging policies (what data you store and for how long).

3. Data strategy and dataset creation

• Amount of data:
  • Full production voice: aim for 15–30+ hours of clean speech across varied content for highest quality.
  • Lightweight cloning/fine-tune: 1–3 hours can yield usable voice quality but expect artifacts; prefer multi-speaker base model then fine-tune.
• Diversity within persona:
  • Emotional range: neutral narration, amused, sarcastic, frustrated, empathetic.
  • Speaking rates: slow, typical, fast.
  • Contexts: reads, short sentences, monologue, dialogues (with simulated interlocutor), rhetorical questions, asides.
  • Phonetic coverage: ensure balanced distribution of phonemes and word positions; use coverage-checking tools.
• Script design:
  • Phonetic coverage scripts (CMU-based phoneme balancing).
  • Conversational prompts and short quips for the wiseguy tone.
  • Contextualized lines: instructions, jokes, disclaimers, navigation prompts, error messages.
  • Sentence length variety: single words to paragraphs.
• Recording metadata: speaker id, session id, mic, take, mouth distance, emotional tag, script line id, timestamp.
• Annotation schema:
  • Text normalization rules (expand numbers, dates, currencies consistently).
  • Punctuation mapping for prosody cues.
  • Prosody labels: break indices (none/short/long), pitch movement (rise/fall/flat), emphasis tags.
  • Phonetic alignments (forced-alignment with phoneme timestamps).
  • Disfluency labels (filled pauses, laughter, coughs).
• Data hygiene:
  • Remove background noise, clicks, unintended speech.
  • Balance dataset for gender/age tokens where relevant (not applicable for single persona).
  • Randomize recording order to avoid session bias.

4. Recording setup and direction

• Audio specs:
  • Sample rate: 48 kHz recommended; 24-bit depth; deliver at 48kHz/24-bit (or 44.1kHz/24-bit if constrained).
  • File format: WAV, PCM, mono.
  • Loudness target: -23 LUFS integrated (or -16 LUFS for streaming contexts) — pick your target and normalize consistently.
  • Peak level: -1 dBFS max.
  • Room: acoustically treated or vocal booth with minimal reverb.
  • Mic selection: large-diaphragm condenser (e.g., Neumann TLM 103) or high-quality dynamic (e.g., Shure SM7B) depending on desired warmth; use pop filter, shock mount.
  • Preamp & chain: high-quality preamp, optionally analog compression. Use pad/gain to avoid clipping.
• Directing the talent:
  • Warm-up and reference listening: provide exemplar wiseguy voice references (non-copyrighted or licensed).
  • Deliver lines in multiple styles: deadpan, amused, teasing, annoyed, mild empathy.
  • Encourage natural speech and short asides; discourage overacting.
  • For rhetorical timing: record multiple cadence variations (early pause, late pause).
  • Capture breaths and small mouth noises separately annotated.
• Session workflow:
  • Record scripted blocks, then improvisation blocks.
  • Monitor take quality and log bad takes.
  • Keep sessions short (max 2 hours) with breaks to avoid voice strain.
  • Backup after each session with checksum.

5. Preprocessing & alignment

• Preprocessing steps:
  • Trim leading/trailing silence (save originals).
  • Noise reduction cautiously applied; avoid artifacts that change timbre.
  • Level normalization per speaker and session.
  • Highpass filter at 80–100 Hz to remove rumble if needed.
• Forced alignment:
  • Use Montreal Forced Aligner (MFA) or similar to get word/phoneme timestamps.
  • Correct alignment errors manually for critical segments (e.g., expressive lines).
• Prosody extraction:
  • Extract F0 (pitch) contours, energy, duration per phoneme/word.
  • Compute speaking rate, pause distribution, and typical pitch range.
• Create training labels:
  • Phoneme sequences, durations, pitch targets (if using FastSpeech-like models), and prosody tags.
  • Compact representation for each utterance: text, phonemes, durations, F0 track, wav path, meta tags.

6. Model architecture choices

• Two main paradigms: end-to-end neural TTS vs. neural acoustic model + vocoder.
  • Acoustic model options:
    • Tacotron 2 / TransformerTTS / FastSpeech 2 (predicts mel spectrograms from text/phonemes).
    • FastSpeech 2 is faster and better for controllability (duration, pitch, energy tokens).
  • Vocoder options:
    • HiFi-GAN v2/v3, WaveGlow, WaveRNN, WaveGrad. HiFi-GAN variants provide real-time, high-quality audio.
  • Prosody control:
    • Use style tokens (GST), reference encoders, or explicit prosody conditioning (pitch, energy, duration).
    • For persona, combine explicit prosody features with a learned style embedding.
• Multi-speaker and fine-tuning:
  • Start with a high-quality multi-speaker base model if limited data.
  • Fine-tune with your target speaker data; freeze some layers (e.g., encoder) if necessary to avoid overfitting.
  • Consider adapter layers or speaker embeddings rather than full retrain.
• Latency/size tradeoffs:
  • Small models for on-device (FastSpeech-lite + small HiFi-GAN).
  • Server-side large models for highest fidelity.
• Training infra:
  • GPU nodes (NVIDIA A100/RTX 4090/3090) with mixed precision.
  • Batch size and learning rate schedule per architecture; use established recipes (e.g., Tacotron 2 defaults).
  • Regular checkpoints and validation with early stopping on perceptual metrics.

7. Persona and prosody conditioning (making it “wiseguy”)

• Style embeddings:
  • Train a style embedding vector tied to the persona; provide explicit style ID at inference.
• Reference audio conditioning:
  • Use a small set of reference audio samples exemplifying wiseguy prosody; at inference, feed references to get similar style.
• Control tokens:
  • Add tokens for intensity, sarcasm, politeness, impatience, etc., exposed in input text or SSML.
• SSML and markup:
  • Support SSML-like tags for breaks, emphasis, pitch, rate adjustments.
  • Define domain-specific macros, e.g., <WISE_PAUSE/>, <SARDONIC_RISE/>, that map to prosody token sequences.
• Rhetorical/question emphasis:
  • Implement an explicit “rhetorical” tag that raises pitch at end and shortens pre-boundary pause.
• Lexical substitutions:
  • Implement substitution rules (e.g., contraction preferences) to match persona.

8. Training, fine-tuning, and regularization

• Training checklist:
  • Normalize text consistently; separate punctuation tags from tokens.
  • Warm-start from pre-trained weights for stability when data is limited.
  • Regularize with dropout, weight decay; use data augmentation (speed perturbation, volume).
• Fine-tuning strategy:
  • Two-stage: train base acoustic model on multi-speaker corpora, then fine-tune on persona dataset.
  • Optionally freeze encoder and fine-tune decoder + style tokens for stable prosody transfer.
• Preventing overfitting:
  • Early stopping by perceptual validation (MOS proxies or ASR-based intelligibility).
  • Use held-out validation set with persona-style lines not seen in training.
• Loss functions:
  • L1/L2 on mel spectrograms; duration/pitch losses for explicit prosody prediction; adversarial loss for vocoder (GAN).
• Multi-objective training:
  • Include perceptual losses (e.g., feature matching) to improve naturalness.
• Checkpointing and model comparison:
  • Save multiple checkpoints; run automated listening tests on a subset to choose best checkpoint.

9. Evaluation and perceptual testing

• Objective metrics (use as proxies):
  • Mel cepstral distortion (MCD), F0 RMSE, Character Error Rate (CER) from ASR, word error rates for intelligibility.
• Subjective tests:
  • MOS for naturalness and voice similarity (1–5 scale).
  • ABX preference tests: wiseguy persona vs. neutral baseline.
  • Character-consistency test: give raters multiple utterances and ask if the same character is speaking.
  • Persona-specific rubric: sarcasm detection, humor delivery, rhetorical timing.
• Sampling plan:
  • N=30–100 raters per test, 20–50 test utterances covering full emotion and prosody range.
  • Use diverse raters for demographic robustness.
• Safety and bias tests:
  • Test phrases that might trigger offensive or abusive outputs; ensure filters and persona guide avoid endorsement.
  • Evaluate how the persona handles sensitive prompts (medical/legal) — default to disclaimers or neutral fallback.
• Automated QA:
  • ASR transcripts vs. ground truth to detect mispronunciations.
  • Phoneme error distributions to find systematic pronunciation issues.

10. Postprocessing and expressive effects

• Breaths and disfluencies:
  • Optionally synthesize breaths and chuckles with controlled placement; annotate dataset with natural breath positions.
• Emotion layering:
  • Combine base voice with pitch/tempo modulation for emphasized lines (e.g., +10% pitch for sarcasm).
• Noise/room modeling:
  • Add subtle room impulse response if you want diegetic “in-world” presence.
• Voice aging/time-of-day variants:
  • Slight pitch shift and spectral tilt to simulate tiredness or animated energy.
• Mixing and mastering:
  • Apply gentle EQ and de-essing; preserve naturalness; do not over-compress.

11. Deployment considerations

• Inference serving:
  • Real-time: use FastSpeech + HiFi-GAN; optimize batching and use GPU inference.
  • Low-latency: precompute commonly used phrases; cache style-conditioned mel spectrograms.
  • On-device: quantized models (int8/float16), prune non-critical weights.
• API design:
  • Expose high-level controls: style token, rate, pitch, emphasis, SSML support.
  • Safety controls: content filters, usage metadata, per-user rate limits, TTS disclaimers.
• Costs and scaling:
  • Estimate GPU cost per hour and tokens per second; assess memory and compute for vocoder.
• Accessibility:
  • Provide clear volume and playback controls; ensure pronunciation clarity for screen-reader uses.
• Monitoring:
  • Logging for errors and voice drift; periodic re-evaluation for quality.
• Legal notices & opt-outs:
  • Give end-users access to opt out of voice use in public contexts (if relevant).
• Internationalization:
  • If supporting other accents/languages, create separate persona datasets or use multilingual models.

12. Safety, content filtering, and guardrails

• Input filtering:
  • Block prompts for impersonation, illegal activities, and disallowed content per policy.
  • For borderline prompts, require a neutral fallback voice or refuse.
• Output filtering:
  • Check generated text before TTS for hate, harassment, or unsafe instructions.
  • Add an override to mute or replace disallowed audio segments.
• Identity and provenance:
  • Include optional short preambles or TTS watermarking (audio or text) to indicate synthetic origin where regulation or ethics require.
• Rate limiting & misuse detection:
  • Monitor for patterns indicating misuse (mass-generation of targeted messages).

13. Iteration, A/B testing, and continuous improvement

• Collect user feedback with short rating prompts (“Was this helpful?”).
• A/B test different levels of sarcasm and pacing for effectiveness.
• Retrain periodically with corrected pronunciations and new lines to keep persona fresh.
• Version control: tag model versions with changelogs (what changed in prosody, lexicon, safety).

14. Example pipelines and tooling (practical checklist)

• Recording → preprocess → forced-align → extract prosody → build metadata CSV → train acoustic model (FastSpeech 2) → train HiFi-GAN vocoder → fine-tune with style embeddings → evaluate → deploy.
• Recommended tools:
  • Recording: Audacity, Reaper, Adobe Audition.
  • Alignment: Montreal Forced Aligner (MFA).
  • TTS frameworks: NVIDIA NeMo, ESPNet-TTS, Tacotron/FastSpeech implementations, Coqui TTS.
  • Vocoder: HiFi-GAN, WaveRNN, MelGAN.
  • Prosody analysis: Parselmouth (Praat Python), Librosa, pyWORLD.
  • Evaluation: crowdsourcing platforms (for MOS), ASR (Wav2Vec2) for intelligibility checks.
• Automation:
  • CI for training runs, unit tests for preprocessing scripts, dataset validation steps, and scheduled re-evals.

15. Example README for the persona dataset (short)

• Persona name: Wiseguy v1
• Speaker: Confidential actor (release signed)
• Hours recorded: 18.2
• Recording settings: 48kHz/24-bit, Neumann TLM103, vocal booth
• Tags: sarcastic, amused, skeptical, empathetic
• License: Commercial use granted by talent; derivatives allowed except as impersonation
• Contact & provenance: dataset owner contact + session logs.

16. Quick checklist before launch

• Legal: signed releases, clear license.
• Safety: input/output filters in place, content policy defined.
• Quality: MOS >= target (e.g., 4.0 naturalness), intelligibility passes ASR checks.
• Perf: latency within SLA, cost analysis complete.
• UX: SSML controls documented, default parameters sane.
• Monitoring: logging, abuse detection, user feedback pipeline.

Appendix A — Example recording script snippets (wiseguy tone)

• Short quips (single-sentence, various cadences):
  • “You did what? Oh, come on.”
  • “That’s the play? Bold move, pal.”
  • “I’ll be honest — that’s not great.”
  • “Relax. It’s just life doing its thing.”
• System prompts (for apps):
  • “Alright, here’s what you need to do next.”
  • “Error: that didn’t work. Try again, and this time bring snacks.”
  • “New message from Mike — you want me to read it?”
• Longer monologue (for expressive tests):
  • “Look, I get it. You’re trying. You aren’t always right, but you got heart. That’ll get you farther than a perfect plan sometimes.”
• Rhetorical and sarcastic tests:
  • “Oh sure — and while we’re at it, why not ask the moon for directions?”
  • “You want a miracle? Cute.”

Appendix B — Example SSML mapping for persona tokens

• Map tags to model controls:
  • <WISE_PAUSE level="short"/> → pause 120–160 ms, slight downward pitch reset.
  • <SARDONIC_RISE intensity="medium"/> → +10–20 cents on final syllable, faster tempo.
  • → +5–8 dB local energy, slight vocal fry.
  • → insert annotated breath sample matching mic and room profile.

Appendix C — Troubleshooting common artifacts

• Metallic timbre: check vocoder overfitting; increase training data or tweak GAN regularization.
• Muffled consonants: examine highpass filter, articulation coverage; add plosive-rich lines.
• Monotone output: ensure pitch conditioning present; add pitch loss or GST.
• Audible clicks at boundaries: smoothing on overlap-add or use overlap-add windowing; align phoneme durations.

Final notes

• If you need a turnkey approach: use a high-quality multi-speaker TTS base and fine-tune with 3–10 hours of targeted recordings plus prosody conditioning; this balances effort vs. fidelity.
• For maximum fidelity and control: invest in 15–30+ hours of varied, well-directed recordings and a two-stage training pipeline with explicit prosody conditioning and a state-of-the-art vocoder.

If you want, I can:

• Produce a sample 1000-line script tailored to the wiseguy persona (balanced phoneme coverage + sarcasm lines).
• Draft a recording session schedule and technician checklist.
• Create SSML-to-token mapping and example inference calls for a chosen TTS stack (e.g., FastSpeech 2 + HiFi-GAN).

Which of those would you like next?

---

3. Emphasis Tags (If your TTS supports it)

In ElevenLabs, use bold or ALL CAPS for the wiseguy punch.

• Bad: "I am very angry."
• Good: "I am furious."