Obsidian auto-sync

[rene-schwabe]

It would be nice if you can auto-sync the transcription to the obsidian vault :)

[ComputelessComputer]

you'll be able to access your notes in *.md in the future - wait!

[papish42]

when? 😃 about to implement my own local pipeline via CLI to get at 'em now

[papish42]

Seconding the request to auto-export transcripts and summaries as .md files into an Obsidian Vault (really just a local folder on the machine. The feature request is: auto-export transcripts and summaries as .md files into arbitrary folders.

[yujonglee]

@papish42 We have

• auto-export all summaries as .md file.
• manual-export transcript to .vtt file

If you can add more colors on what exact workflow you would like to build, I can get it done pretty soon.

[papish42]

Is manual export to vtt file already active? That would totally work fine for my needs. Longterm, as long as I can create an organized file system of transcripts that are easily connected to the .md summaries that will live in my Obsidian Vault, I'm good. While you work on the auto-flow, as long as I can manually get summaries.md (I see those now) and the manual export to .vtt, I'm good. Should I be looking for the vtt files somewhere?

[avigilante]

Maybe I'll try to add more color:

1. Right now, despite setting only "content" to the Obsidian Vault, it seems that Char is "polluting" the Obsidian Vault with a ton of files that have nothing with Content (see pics below). My idea of Content would be: humans, organizations, meetings memos (potentially transcripts, but I personally find the memos 100x more useful than transcripts in Obsidian). So: (1) for me would be to only have content in Obsidian, and not config files.
2. When it comes to Humans, Organizations and Meeting Memos, Char is currently using UUIDs; to me that's pretty useless, as I'm never going to backlink a UUID (it has no meaning). I made one proposal here, but maybe another way to think about it would be to customize the export, like you can do with the Readwise plugin: you can define the file name and content using Readwise variables. Char already exposes some variables via jinja2, which can be used in Char templates; so if I could define Char -> Obsidian export file names for human / organization / meeting memo using jinja2 variables the problem would be solved.

Now, whether (2) above is a job for Char or for someone writing an Obsidian Char plugin, I don't know...

Image 1a: Char configured to only export content to Obsidian

Image 1b: despite Char is configured to only export content to Obsidian, Obsidian is polluted with a ton of non-markdown files

Image 2: An export configuration panel (this one is from Readwise to Obsidian) would be awesome! It could use jinja2 variables like it currently happens with templates:

[papish42]

I agree that we need a more precise and human friendly way to export to Obsidian. For both agent and human work, I would like to auto-export mtg notes and transcripts with human friendly file names. Assuming a transcript has been created, I do not need to also export the raw audio to Obsidian (much larger file sizes which mess with how I store/sync my Obsidian Vault across devices). One lightweight json per mtg would also be useful to assist agents who are analyzing the mtg content in bulk.