mirror of
https://git.mirrors.martin98.com/https://github.com/bytedance/deer-flow
synced 2025-08-19 20:19:14 +08:00
fix: fix podcast issue
This commit is contained in:
parent
afb8571cbd
commit
3d1d289dbd
2
.vscode/launch.json
vendored
2
.vscode/launch.json
vendored
@ -40,7 +40,7 @@
|
||||
"request": "launch",
|
||||
"program": "${workspaceFolder}/server.py",
|
||||
"console": "integratedTerminal",
|
||||
"justMyCode": true,
|
||||
"justMyCode": false,
|
||||
"env": {
|
||||
"PYTHONPATH": "${workspaceFolder}"
|
||||
}
|
||||
|
@ -7,15 +7,16 @@ You are a professional podcast editor for a show called "Hello Deer." Transform
|
||||
- **Length**: Keep the script concise, aiming for a runtime of 10 minutes.
|
||||
- **Structure**: Start with the male host speaking first. Avoid overly long sentences and ensure the hosts interact often.
|
||||
- **Output**: Provide only the hosts' dialogue. Do not include introductions, dates, or any other meta information.
|
||||
- **Language**: Use natural, easy-to-understand language. Avoid mathematical formulas, complex technical notation, or any content that would be difficult to read aloud. Always explain technical concepts in simple, conversational terms.
|
||||
|
||||
# Output Format
|
||||
|
||||
The output should be formatted as a JSON object of `Script`:
|
||||
The output should be formatted as a valid, parseable JSON object of `Script` without "```json":
|
||||
|
||||
```ts
|
||||
interface ScriptLine {
|
||||
speaker: 'male' | 'female';
|
||||
text: string;
|
||||
text: string; // only plain text, never Markdown
|
||||
}
|
||||
|
||||
interface Script {
|
||||
@ -68,7 +69,6 @@ interface Script {
|
||||
</example>
|
||||
|
||||
> Real examples should be **MUCH MUCH LONGER** and more detailed, with placeholders replaced by actual content.
|
||||
> You should adjust your language according to the `Settings` section.
|
||||
|
||||
# Notes
|
||||
|
||||
@ -77,3 +77,7 @@ interface Script {
|
||||
- Alternate between the male and female hosts frequently to maintain interaction.
|
||||
- Avoid overly formal language; keep it casual and conversational.
|
||||
- Always generate scripts in the same locale as the given context.
|
||||
- Never include mathematical formulas (like E=mc², f(x)=y, 10^{7} etc.), chemical equations, complex code snippets, or other notation that's difficult to read aloud.
|
||||
- When explaining technical or scientific concepts, translate them into plain, conversational language that's easy to understand and speak.
|
||||
- If the original content contains formulas or technical notation, rephrase them in natural language. For example, instead of "x² + 2x + 1 = 0", say "x squared plus two x plus one equals zero" or better yet, explain the concept without the equation.
|
||||
- Focus on making the content accessible and engaging for listeners who are consuming the information through audio only.
|
||||
|
Loading…
x
Reference in New Issue
Block a user