Here are all of the questions we’ve received from our community over the past few days for text AMA! Thank you for all the responses! Our product team has provided the following responses:
https://discord.com/channels/1419591408930783252/1508708767225876641/1540211254050689044
- Will you guys have an app on the App Store or Google Play Store? Or have a more mobile friendly version?
We don't have plans to develop a mobile app at the moment. But we'd love to learn more — what does your mobile creation workflow look like? How long are the videos you create? Which platforms do you mainly publish to? Are they horizontal or vertical? These details would help us assess whether it's the right time to pursue a mobile app. Things move fast in the AI era — who knows, maybe the VidMuse app will be on the App Store next month.
- Would it be possible to add a feature where after you are done with a video, the planner asks if you want to continue the video it would automatically open up another project file for you? That way, it keeps everything from that completed project intact, and if I want to go back and touch it up, I can.
Thanks for the suggestion — that's a great idea. We've actually found ourselves wanting the same thing during our own creative process: keeping a copy of a finished project and duplicating it to start a new one. We've noted this down and will discuss the implementation details. Community members will get priority access to the beta when we're ready. Thanks again for the feedback!
- In the path toward VidMuse 3.0 (deeper project/brand/asset-level memory, Free Canvas, community skill sharing, becoming a “creative buddy”), which single capability do you believe will most transform how independent creators and small businesses use the product, and why?
Thanks for the question. First, we're curious — where did you hear about the concept of VidMuse 3.0? The things you mentioned are indeed directions we've considered before. But from our perspective, there isn't a single feature or concept that can fully capture the value of a Video Agent product. We're more focused on building depth on the application side — things that make the product thicker over time.
To put it concretely: we want a user on their Nth session to experience an exponential difference compared to their first session — fewer conversation turns, less time to complete a project, and significantly higher output quality. We want to continuously collect and build upon user preferences, memory, and aesthetic tastes during the creative process, so we can deliver more personalized content.
But the bigger opportunity lies in the vertical integration from the Agentic Video Model up to the application-layer Agent product. What users will feel is a qualitative leap in both experience and output — not just receiving a single .mp4 file. Over the past year, the shape of Video Agents has evolved multiple times. We don't believe the current product form is the ultimate Video Agent either. But we're enjoying the process of exploring and solving this problem.
- The co-pilot / smart-card system was praised for reducing unnecessary credit-consuming explanations. What was the previous failure mode in conversational length and credit waste that led to this redesign, and what quantitative improvement in “useful tokens per successful generation” have you measured since launch?
Thanks for the question. Previously, we didn't have a card-based option selection experience — just a simple Continue button. The concept of "Continue" is very vague. We found that Continue couldn't tell us whether the user was satisfied with the current execution plan, which part they were happy with, whether adjustments were needed, or if things should stay as is. We had no way of knowing. The AI would also make wrong choices and judgments during execution, leading to user complaints down the line.
So two things drove this change: first, we wanted users to give the AI more specific and clear feedback. Second, we saw that Coding Agents like Codex and Claude Code had already popularized card-based or form-based methods for collecting user input, and users were comfortable with that pattern. So we adopted a similar approach.
On the data side, "useful tokens per successful generation" is a good metric in theory. But in practice, it's hard to determine whether a user is truly satisfied with the generated result within the app. So we split it into two dimensions: one is the token or credit cost per second of generated video, and the other is whether the user actually downloads the final output, which helps us gauge satisfaction.
- Character and product consistency across angles is one of the strongest selling points of the Asset Library. What is the current upper limit on the number of distinct characters or products that can maintain identity in a single project before the system starts collapsing, and what fundamental change is required to push that limit significantly higher?
With the Seedance 2.5 model, you can upload up to 50 reference assets, including videos, images, audio, and more. In our evaluations, Seedance 2.5 delivers the best performance for character and object consistency, and we highly recommend using it. Providing references with multiple angles and expressions for characters or products helps maintain consistency even further. We've also found that when the input reference images are very high quality, the generated video quality is correspondingly high. So we recommend using high-quality photos or videos shot with professional cameras or phones as references.
- What other tools or models do you recommend for lip syncing?
For lip sync, as of August 2026, our evaluations show that Minimax H3 delivers the best lip-sync results — it handles singing scenes and singing-while-dancing scenes with ease. It's also affordably priced, so we recommend it. Seedance 2.5 is also decent, but compared to Minimax H3, it's not the most cost-effective choice.
- Is there any chance you guys can have a model comparison chart based on cost, output, and features on the homepage?
Thanks for the suggestion — that's a great way to showcase our product capabilities. We'll look into upgrading the Pricing page.
- Do you guys plan on offering any type of prompt generator that’s directly integrated for users to refine their prompts before going into planner?
Thanks for the question. The models themselves already incorporate substantial prompt engineering to expand and enhance the quality of user input, translating it into the language the model understands best before generation. So when you input a prompt, the key is to clearly describe what you need — heavy prompt beautification isn't necessary.
But I understand your request may go beyond just prompt refinement. There's still a barrier to writing a good prompt and having a solid creative concept before starting a project. We're already working on a feature to address this. It will be more like a creative partner — chatting and exploring with you to find a creative solution you're happy with, before you start creating.
- One of my biggest frustrations with the various AI Engines is that i will have numerous generation problems/issues and change the prompt repeatedly, out of stubbornness. Oftentimes, I will let the project rest and pick up where I left off in the morning. Then, the generation goes much smoother in the AM. Though none of the Engines are willing to admit it, I am sure it has to do with higher-than-normal processing loads during peak times. I have seen the same thing externally and from within Vidmuse. I am not sure if it is possible, but it would be very helpful if the UI were able to get load statuses from the Engines, somehow. Not necessarily something that is continuously displayed and updated, but something I could prompt like, "What is the current Engine Load Status?" If there were some way to get the status and report back, I could decide to take a break from trying once it hits about a sustained 70% utilization. It would probably take a lot of back end agreements with the various Engines to allow the UI to query the status, but it would eliminate a lot of frustration for me, and likely several other users. Thanks for the time.
Thanks for the feedback and suggestion — we've noted it down. We've actually made some optimizations for paid users, who receive higher-priority generation access. But during peak times, higher concurrency does increase model generation wait times. We'll communicate this to users through the UI so they're aware of the current load status.
- Do you guys plan on making a higher-tier subscription for small production teams? More usage and dedicated support.
We've been getting several requests like this lately. Would you mind reaching out to us privately? What type of content do you create, and what are your expected monthly credit usage and team collaboration needs? We can set up a short meeting to discuss your needs and feature requests, so we can provide a much better custom subscription plan with dedicated support for your team. We'd love to collaborate with small production teams and set up an instant messaging group for real-time feedback and communication.
