# Video + timeline related information – in DT, the wider file ecosystem & in knowledge work in general

**URL:** <https://discourse.devontechnologies.com/t/video-timeline-related-information-in-dt-the-wider-file-ecosystem-in-knowledge-work-in-general/72235>\
**Category:** DEVONthink\
**Tags:** devonthink3\
**Created:** [August 8, 2022, 11:13am UTC](https://discourse.devontechnologies.com/t/video-timeline-related-information-in-dt-the-wider-file-ecosystem-in-knowledge-work-in-general/72235 "2022-08-08T11:13:20Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![lerone](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/lerone/32/6146_2.png) [@lerone](https://discourse.devontechnologies.com/u/lerone)\
**Post date:** [August 29, 2022, 9:17am UTC](https://discourse.devontechnologies.com/t/video-timeline-related-information-in-dt-the-wider-file-ecosystem-in-knowledge-work-in-general/72235/28 "2022-08-29T09:17:26Z")

</div>

hey Bluefrog,

thanks. This kind of summing-up and reacting reflection is appreciated.

> [@BLUEFROG](#):
>
> It is nodding to the strengths and the core of DEVONthink:

I see that as one of the core take-aways. And it is a reasonable 'meta-'argument. I think indeed every app has it´s character (and characters 🙂 ) – and that is ultimately a good thing. And simply something one better takes into account and acknowledges when dealing with complex apps. (And certainly DT has a lot of cores and strengths… 🙂 )

> [@BLUEFROG](#):
>
> text-based processing and connections between text-based documents.
> 
> Consider an empty database.  
> You put a video in it.  
> Except for a minimal amount of metadata indexed, there is no inherent usefulness to having the video in the database, relative to DEVONthink’s core functions.

This goes to the core of the argument (‘architectural’ logic). And _ **this is what I would indeed debate and contest to some extent.** _  
First of all there is **metadata in non-textual documents**. And surely ‘metadata’ is not an aspect alien to the DT-horizon and architecture. – Consider the way DT itself acknowledges this in principle; e.g. importing / indexing of existing documents; importing some of the IPTC (text-)metadata _from images_(!); but also DTs many affordances to input, manipulate and work with metadata alongside ‘body-text’).

One thing I think safe to say is that this **‘mode of textual hybridity’** (– text in the human-readable body of documents; other textual metadata, human readable, interactionable or not…) is _a base-feature/-reality of current day (digital) documents_. With that in sight and contrasting of text vs. video (image / audio) gets … complex. Especially if one considers DT on it´s own terms (document handling vs. simple ‘note taking’ etc.)

> [@BLUEFROG](#):
>
> Now consider a new empty database.  
> Create a plain text file. Even with Lorem Ipsum filling it, there is already an immediate source of indexed text to search for and compare via See Also or file with Classify.

– In my view out of the multiple functional universes that DT serves (and it is a master at that), you are restricting discussion with this particular framing of your example to the mental space / scenario of notetaking (or something in that realm…).

* * *

Then there were in the course of the relevant threads here 'like **three’ – by-and-large _unadressed_ – arguments** – also challenging this equation on different bases:

1. there are **more and more ways to input text alongside timebased media** (see YT- and podcast chapters; see subtitles and closed captions; see ‘special’ (research) software like Kyno, or even FinalCut and metadata / keywords / markers etc.). Also there is growing, more specialized base for this in more specific research-centric domains (… up to attorneys, and script writers). It is rather a question of how to evaluate this trend.  
– Again, as to the somewhat ecclectic way DT-as-is already acknowledges this: YT chapters are recognized and imported! (– even though I still do not understand on what technical protocoll :-}). Also take PDFs: PDFs were (and to some extent still are) image / design based to a large degree. What is DT response in that particular case? It implements OCR!! – So this definitely – to me – is a rather pro-active channeling into the direction of ‘text-culture’. (Which, functionally, I like btw. I am not against ‘text’ 😃 )

2. … brings to the second point that was raised in this (or the ‘sibling-thread’): it is **possible by now to do automated transcription**. and actually we see that all over the internet by now, certainly in more professional / enterpreneurial realms. As to that there was @AW2307 point that autotranscription really is something (like OCR) that could be considered (at least conceptually) – see [here]. ([Interested in your scenarios / experiences around timeline related documents / knowledge (audio / video) - #2 by AW2307](https://discourse.devontechnologies.com/t/interested-in-your-scenarios-experiences-around-timeline-related-documents-knowledge-audio-video/72437/2))

3. related to the third point raised… as, lastly, there is certainly **the trend of bringing text as automatic / ‘natural’ augment to video (and audio) ‘consumer’ platforms**. again, see YT-example, vimeo following, chapter and note culture in audio platforms and apps (like soundcloud, or in the better podcast apps).

* * *

So, I really do appreciate you getting to the conceptional core of it, and follow through. But I think your reaction also shows **the (unacknowledged) ambivalencies as they exist**, even within DT: your example excludes images totally, which are put into DT regularly I suppose (and are also regularly discussed here). It omits some of DT reals ‘core strengths’ and programmatics (like OCR; IPTC support, native time based references etc.).

> [@BLUEFROG](#):
>
> So no, I don’t believe development is driven by a bias against media or not wanting to _”keep up with the times” (especially when new does not always equal better)_

I surely don´t think it´s an active form of _'not wanting to_ ”keep up with the times”’ :-). I am also acknowledging _this is all strategic decision stuff_. but I think **to ”keep up with the times”’** one has to have _open_ ears, and eyes, and a culture of attentive discussion _in relation to tectonic shift and evolutions_. (DT itself is a child of the transition from print to digital text, I guess). I think things like OCR for PDF while not adressing auto-transcription even conceptually is a sign of some bias. (That is not to beat this over anyones head, of course…)

In that spirit I thank you for your response here. As you see, in the end I ‘personally’ think _a reductionist narrative of text-files vs other media-files doesn´t hold very long_ if going into the matter (and into DT itself), neither conceptually, nor in terms of document culture development, nor review of DT-genealogy itself…

But I would never argue with decisions made by others about what ‘core strengths’, ‘profiles’ etc. they want to give their app (project). For sure. 🙂  
So, in some way as you might see, what I am calling for is _some more **serious and open ‘accounting’ and systematic reflection** – while not leaving DT´s grounds, aspirations, or premises_…

So, thanks for getting to it…!

---

_[View the full topic](https://discourse.devontechnologies.com/t/video-timeline-related-information-in-dt-the-wider-file-ecosystem-in-knowledge-work-in-general/72235)._