# Embedded audio and video

**URL:** <https://talk.commonmark.org/t/embedded-audio-and-video/441>\
**Category:** Extensions\
**Created:** [September 6, 2014, 3:00am UTC](https://talk.commonmark.org/t/embedded-audio-and-video/441 "2014-09-06T03:00:25Z")\
**Posts on this page:** 1\
**Showing post:** 62

<div class="post-metadata">

**Author:** ![vitaly](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/vitaly/32/396_2.png) [@vitaly](https://talk.commonmark.org/u/vitaly)\
**Post date:** [December 31, 2015, 11:29am UTC](https://talk.commonmark.org/t/embedded-audio-and-video/441/62 "2015-12-31T11:29:16Z")

</div>

I don’t understand why audio/video should be covered by the spec. This task can be completely automated by external preprocessor. For example, in nodeca:

1. Inline links to youtube/vimeo/… are replaced with video title
2. Links to youtube/vimeo/… on separate paragraph are replaced with video player

Rules can be extended to ANY url pattern, without spec change. So, i don’t know why audio/video files should be special case.

For node.js we did [https://github.com/nodeca/embedza](https://github.com/nodeca/embedza) to automate things.

Discouse has similar ruby package, “onebox”, but AFAIK it does not supports inline links & flexible fallback (try block format if available, if not - try inline)

---

_[View the full topic](https://talk.commonmark.org/t/embedded-audio-and-video/441)._