u/srch4aheartofgold

AI Stadium Broadcast Cam Trend is getting insanely realistic with Seedance 2.0

Prompt:

"Realistic cinematic basketball broadcast crowd cutaway during a fictional professional playoff basketball game. The subject is seated courtside inside a packed indoor arena with authentic playoff energy and natural crowd atmosphere. One continuous broadcast-style take with no cuts or camera angle changes. The subject casually watches the game, smiles naturally, occasionally glances toward the court, then notices the arena camera and gives a relaxed wave. Later they cheer briefly, laugh with a friend beside them, and clap while continuing to watch the game. Movements should feel subtle and realistic — no exaggerated acting, no influencer behavior, and no direct speaking to camera. Visual style should resemble authentic televised sports coverage with telephoto broadcast lens compression, realistic indoor arena lighting, cinematic courtside framing, slight TV grain, subtle compression artifacts, and natural crowd movement. Include fictional broadcast score graphics and lower-third overlays, but avoid all real NBA teams, logos, broadcasters, or copyrighted branding. Audio should include arena ambience, crowd noise, sneaker squeaks, whistles, and generic sports commentary reacting naturally to the subject being shown on the broadcast."

Welcome to use it at www.cliprise.app

u/srch4aheartofgold — 8 days ago
▲ 8 r/BuildWithClaude+7 crossposts

Cursor 50% off first month through this referral link

Title: Cursor 50% off first month through this referral link

Cursor is giving new users 50% off their first month of Pro, Pro+ or Ultra when they sign up through a referral link.

Here’s the link to activate it:

https://cursor.com/referral?code=VOP2EMUQKAFU

I’ve been using Cursor for real project work lately, mostly codebase cleanup, debugging, refactoring, SEO site improvements, and turning rough product ideas into actual implementation steps.

It’s not one of those AI tools that just looks impressive for 5 minutes and then becomes useless. If you already work with code, websites, apps, automations, or technical projects, Cursor can genuinely save a lot of time.

The offer through this link:

  • 50% off your first month
  • Works for Pro, Pro+ or Ultra
  • I get $25 in Cursor usage credit if you buy a plan

So if you were planning to try Cursor anyway, this is probably one of the better ways to start:

https://cursor.com/referral?code=VOP2EMUQKAFU

Would be interesting to hear how others are using Cursor right now. Are you using it mainly for full project builds, debugging, refactoring, or working inside existing codebases?

u/srch4aheartofgold — 8 days ago
▲ 8 r/SoraAi

Sora being discontinued as a normal OpenAI product is honestly a weird moment for AI video.

A lot of people finally started building workflows around it, learning its strengths, figuring out what types of prompts worked, and then suddenly the official app/web experience is gone.

From what OpenAI has published, the Sora web/app experience has already been discontinued, but the API window is still available until September 24, 2026.

That is why we decided to keep Sora available on Cliprise for as long as that API access remains possible.

I know a lot of people here are not just looking for “one more wrapper.” That is fair. The AI video space is full of tools that add a model, charge a markup, and do not really improve the workflow.

What we are trying to do with Cliprise is a bit different.

The goal is not just:

“Here is Sora.”

The goal is:

“Here is Sora inside a broader creative workflow where you are not locked into one model.”

Because the reality is that one model is not enough anymore.

Sora can be great for certain cinematic and physics-heavy scenes, but it is not always the best fit for every shot. Sometimes Seedance 2.0 is better. Sometimes Kling 3.0 is better. Sometimes Veo, Wan, Hailuo, or another model gets you closer faster.

That is why Cliprise is built around multi-model AI creation instead of forcing people into one isolated video tool.

Right now Cliprise includes 47+ AI models across image, video, and creative workflows, so you can test different directions without constantly jumping between platforms.

For Sora specifically, the advantage is simple:

You can still use it while API access exists, but you are not building your whole workflow around a model that is already being sunset as a standalone OpenAI product.

That matters.

If one model disappears, changes pricing, becomes too restrictive, or just does not work for a specific shot, the workflow should not collapse.

That is the bigger problem we are trying to solve.

AI video creators do not just need another model picker.

They need:

fewer disconnected subscriptions

less tab switching

cleaner image-to-video workflows

faster testing

better model comparison

more practical pricing

one place to create instead of five different tools fighting each other

Sora being discontinued is a reminder that the future is probably not about loyalty to one model.

It is about having a flexible workflow where you can use the right model for the right shot.

That is the direction we are building Cliprise toward.

So yes, Sora is still available on Cliprise during the API window, and we will keep supporting it as long as possible within that timeline.

But the bigger value is that Cliprise also gives you access to many other models in the same workflow, so you are not stuck if Sora is no longer the answer.

If you are still creating with Sora, experimenting with Sora 2-style workflows, or looking for a more practical AI video setup, Cliprise is worth checking out.

Website: https://www.cliprise.app⁠

iOS:

https://apps.apple.com/us/app/cliprise-ai-video-generator/id6753740657⁠

Android: https://play.google.com/store/apps/details?id=app.cliprise⁠

u/srch4aheartofgold — 17 days ago
▲ 2 r/n8n

I’m running a self-hosted n8n setup for a production app. One main webhook workflow has grown too large over time and now the initial request can take much longer than expected before the frontend gets a useful response.

The workflow currently handles several responsibilities in one place:

request validation

user/account checks

quota/credit checks

queue checks

optional prompt preprocessing

model/provider routing

job creation

external API calls

status/callback handling

The goal is to make the initial webhook response fast:

validate the request

create a job record

return a job/task ID quickly

continue the heavy work asynchronously

update job status later through callback or polling

Questions:

For a large production n8n workflow, is it usually better to split by media/task type, by provider/integration, or both?

Is it better to replace large Switch/IF routing sections with a database/config lookup?

Can very large workflows create noticeable execution overhead even when only one branch is used?

Which n8n execution data settings usually have the biggest performance impact in production?

Would queue mode with Redis and workers improve single-request latency, or mostly concurrency/scalability?

Is waitForSubWorkflow: true usually something to avoid in webhook flows where the frontend needs a fast response?

What is the recommended n8n pattern for “return job ID immediately, continue processing in background”?

I’m mainly looking for architecture/performance advice, not help with a specific external API.

reddit.com
u/srch4aheartofgold — 20 days ago
▲ 4 r/seedance_video+5 crossposts

I’m building **Cliprise**, a multi-model AI creation platform for people who are tired of juggling five different tools just to make one piece of content.

The core idea is not “one magic model.”

It is the opposite.

Different models are better at different jobs.

One is better for controlled video.

Another for motion-heavy scenes.

Another for cinematic narrative.

Another for image generation.

Another for text rendering.

Another for API use.

So instead of forcing people into one ecosystem, Cliprise gives access to **47+ models** in one place and lets you work across **AI video, AI image, and AI voice workflows** without rebuilding your process every time.

That means you can use things like **Seedance 2.0, Kling 3.0, Sora 2, Veo 3.1, Wan, Hailuo** and more inside one platform rather than maintaining a pile of disconnected subscriptions. Cliprise’s own model and platform pages position this as the whole point: one workflow, not one locked-in model.

A big recent addition is **Seedance 2.0**, which is already live on Cliprise. It matters because it is one of the first mainstream commercial models that can combine **text, images, video, and audio simultaneously** in one generation pass. That is a genuinely useful capability, especially for creators doing ads, UGC, music visuals, trailers, or short-form experiments.

Cliprise also has a **web app**, **iOS**, **Android**, and a **Business API**, so it is not just for casual testing. If you want to create on mobile, do heavier work on desktop, or integrate it into your own product, those paths are all there.

Pricing starts at **$9.99/month** for Starter, with **900 monthly credits**, and the API side uses **separate API credit packs**. That separation is useful because creators and developers usually need different billing logic.

Also worth mentioning: **Hailuo 2.3** is now on Cliprise too, and it looks especially strong for expressive character motion and stylized video work, which adds another useful option to the stack instead of forcing everyone into the same model for everything. 10

So if you are into AI video, AI image generation, or building on top of creative AI infrastructure, Cliprise might be worth a look.

Website:

https://www.cliprise.app

iOS:

https://apps.apple.com/us/app/cliprise-ai-video-generator/id6753740657

Android:

https://play.google.com/store/apps/details?id=app.cliprise

u/srch4aheartofgold — 13 days ago

If you are actively testing MiroFish, share:

  • your goal
  • your setup
  • number of agents
  • model stack
  • approximate cost
  • what worked
  • what failed

Would be great to build a thread with practical examples instead of scattered fragments across random posts.

reddit.com
u/srch4aheartofgold — 2 months ago

For most people I assume it is one of these:

  • setup complexity
  • cost
  • unclear use cases
  • documentation gaps
  • prompt design
  • not knowing how to evaluate output quality

What is the real blocker for you right now?

Would be useful to see whether the biggest problem is technical, conceptual, or practical.

reddit.com
u/srch4aheartofgold — 2 months ago

I am curious what people here actually want to use MiroFish for beyond the hype.

Some obvious directions:

  • prediction
  • market behavior simulation
  • social simulation
  • sentiment dynamics
  • product or messaging testing
  • scenario modeling
  • research

What is your real use case?

Even if it is still rough, early, or half-formed, post it.

The more concrete, the better.

reddit.com
u/srch4aheartofgold — 2 months ago

Welcome to r/MiroFish.

This is an unofficial community for people interested in MiroFish, swarm intelligence, multi-agent simulations, experiments, setups, prompts, workflows, benchmarks, and real-world use cases.

The goal of this subreddit is simple:

  • help people get started faster
  • share useful setups and experiments
  • compare results and ideas
  • build a practical knowledge base around MiroFish

Whether you are here because you saw the repo recently, want to test multi-agent simulations, or are already running serious experiments, you are welcome.

What to post here

You can use this subreddit to:

  • ask setup questions
  • share prompts and workflows
  • post experiments and results
  • compare outputs and behaviors
  • discuss benchmarks and research
  • share use cases, demos, repos, papers, and guides

If you are new, introduce yourself below

Reply in the comments with:

1. What do you want to use MiroFish for?
Examples: prediction, market simulation, social simulation, research, product testing, scenario analysis

2. What setup are you using or planning to use?
Local, API-based, cloud, model stack, number of agents, etc.

3. What is your biggest blocker right now?
Setup complexity, cost, unclear use case, documentation, prompt design, evaluation, or something else

A few quick rules

  • Stay on topic
  • No impersonation
  • No spam or low-effort promotion
  • Be respectful
  • Share context when posting results
  • No deceptive or harmful use cases

If you share results, try to include useful context like:

  • objective
  • prompt logic
  • number of agents
  • model choices
  • assumptions
  • approximate cost
  • what worked
  • what failed

This subreddit is independent and not officially affiliated with the MiroFish developers.

Glad to have you here. Drop your intro below.

reddit.com
u/srch4aheartofgold — 2 months ago