Fix YouTube sources with German transcripts landing empty
Adding a German YouTube video created a source with a title but no content — nothing to chat with, nothing to summarise. The failure was silent in the UI; the reason only showed up in the container log as "Failed to get transcript for video <id> after retries: No suitable transcript found". Open Notebook extracts YouTube via content-core, which reads captions with youtube-transcript-api. content_core/processors/youtube.py only looks for the languages listed in preferred_languages, and the built-in default is ["en", "es", "pt"] — no German. All four fallback attempts in _fetch_best_transcript use that same list, so a video carrying only a German transcript raises NoTranscriptFound, get_best_transcript swallows it and returns None, and the source is stored with an empty body. The title still arrives because it is scraped separately, which is what makes this look like a success. The youtube_transcripts.preferred_languages key in the package's own cc_config.yaml appears to be the knob for this, but it is dead code on the default path: load_config() copies only the "extraction" block out of that file, so the key never reaches CONFIG and the hardcoded fallback always wins. The only way to set it is CCORE_CONFIG_PATH. config/content_core.yaml (bind-mounted read-only) therefore sets preferred_languages: ["de", "en", "es", "pt"]. Note CCORE_CONFIG_PATH REPLACES the config wholesale rather than merging it (config.py: return yaml.safe_load(file)). The file is consequently a full dump of the effective default config plus the new key — a minimal override file would silently drop the extraction engines and the model/timeout defaults. Its header comment carries the command that regenerates it from inside the container, for when an image update changes content-core's defaults. Verified end to end on the reported video (hzxiegk9QAg): extraction now yields 21553 characters of German transcript, the source is created through POST /api/sources with that full text, embedding produces 17 chunks in 3.4s, and vector search returns the video as top hit. This only covers caption languages. A video with no captions at all still yields an empty source — there is no download-and-transcribe fallback in the image. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
ba98ac4eb4
commit
2a057d04e1
5 changed files with 144 additions and 0 deletions
|
|
@ -444,6 +444,29 @@ wird abgeschnitten. Behoben durch `/no_think` als erste Zeile beider Podcast-Vor
|
|||
den Denkmodus ab, ~3× schneller, volles Budget fürs JSON). Falls es dennoch auftritt: kürzeren
|
||||
Quellinhalt verwenden (nicht das ganze Buch) oder die Generierung erneut starten.
|
||||
|
||||
### YouTube-Video wird als leere Quelle angelegt
|
||||
|
||||
Behoben. Symptom war: Quelle hinzufügen scheint zu klappen (der **Titel** erscheint), aber es gibt
|
||||
keinen Inhalt — kein Text, nichts zum Chatten, nichts zum Zusammenfassen.
|
||||
|
||||
Ursache: Open Notebook holt YouTube-Untertitel über die Bibliothek `content-core`, und die suchte
|
||||
nur nach Transkripten in **Englisch, Spanisch und Portugiesisch**. Ein Video mit ausschließlich
|
||||
deutschem Transkript fiel damit durch; der Fehler stand nur im Container-Log, in der Oberfläche
|
||||
sah die Quelle einfach leer aus. Behoben durch `config/content_core.yaml` (per Bind-Mount
|
||||
eingehängt), die Deutsch an erste Stelle setzt.
|
||||
|
||||
Falls doch mal ein Video leer bleibt, ist meist **gar kein Untertitel** vorhanden (weder manuell
|
||||
noch automatisch) — das lässt sich so prüfen:
|
||||
|
||||
```bash
|
||||
docker compose exec open_notebook /app/.venv/bin/python -c "
|
||||
from youtube_transcript_api import YouTubeTranscriptApi
|
||||
for t in YouTubeTranscriptApi().list('VIDEO_ID'): print(t.language_code, t.is_generated)"
|
||||
```
|
||||
|
||||
Kommt hier nichts zurück, hat das Video keine Untertitel — dann hilft nur, das Video separat
|
||||
herunterzuladen und über die STT-Funktion (Audio-Upload) zu transkribieren.
|
||||
|
||||
### Podcast schlägt beim Vertonen fehl („Failed to generate speech")
|
||||
|
||||
Text und Transkript sind fertig, erst die Sprachausgabe scheitert. Die genaue Fehlermeldung
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue