dashj | Dash Java Library

looks like dashjs module is exporting the debug file as their main file program:

after running npm install dashjs@4.0.0-npm, i opened ./node_modules/dashjs/package.json

You are using an older version of dash.js. Try using the latest stable one which is currently version 3.2.1: http://cdn.dashjs.org/v3.2.1/dash.all.min.js

In your version 3.1.0 the settings look different:

video/mp4;codecs="avc1" isn't a valid codecstring - it's missing the profile, constraints and level that are required by the SourceBuffer for this bitstream type.

It's happening because you have -flags -global_header set. This is causing the codec extradata to be unset, which in turn means that the ffmpeg DASH manifest generator cannot generate the correct codecstring.

Remove -flags -global_header and it should work fine.

Your import statement should be like below

Your answer is here: https://vuejs-templates.github.io/webpack/static.html

To answer this question, we first need to understand how Webpack deals with static assets. In *.vue components, all your templates and CSS are parsed by vue-html-loader and css-loader to look for asset URLs. For example, in and background: url(./logo.png), "./logo.png" is a relative asset path and will be resolved by Webpack as a module dependency.

Because logo.png is not JavaScript, when treated as a module dependency, we need to use url-loader and file-loader to process it. This template has already configured these loaders for you, so you get features such as filename fingerprinting and conditional base64 inlining for free, while being able to use relative/module paths without worrying about deployment.

I assume that what you need is "Real" Static Assets (it's explained at the same link), as there is no point to "pack" your media file along with JS.

In comparison, files in static/ are not processed by Webpack at all: they are directly copied to their final destination as-is, with the same filename. You must reference these files using absolute paths, which is determined by joining build.assetsPublicPath and build.assetsSubDirectory in config.js.

Alternatively you can change your nuxt configuration to load audio files as described in documentation:

You need to extend its default configuration in nuxt.config.js:

i solved it using shaka packager to encrypt and create the xml manifest for me automatically

A neat solution would be to use rxjs to solve this like shown below:

HLS and MPEG DASH are not particularly low latency as standard and the figures you are getting are not unusual.

Some examples from a publicly available DASH forum document (linked below) include:

Given the resources of some of these organisations, the results you have achieved are not bad!

There is quite a focus in the streaming industry at this time on enabling lower latency, the target being to come as close as possible to traditional broadcast latency.

One key component of the latency in chunked Adaptive Bit Rate (ABR, see this answer for more info: https://stackoverflow.com/a/42365034/334402 ) is the need for the player to receive and decode one or more segments of the video before it can display it. Traditionally the player had to receive the entire segment before it could start to decode and display it. The diagram from the first linked open source reference below illustrates this:

Low latency DASH and HLS leverage CMAF, 'Common Media Application Format' which breaks the segments, which might be 6 seconds long for example, into smaller 'chunks' within each segment. These chunks are designed to allow the player to decode and start playing them before it has received the full segment.

Other sources of latency in a typical live stream will be any transcoding from one format to another and any delay in a streaming server receiving the feed, from the webcam in your case, and encoding and packaging it for streaming.

There is quite a lot of good information available on low latency streaming at this time both from standards bodies and open source discussions which I think will really help you appreciate the issues (all links current at time of writing). From open source and standards discussions:

• https://dashif.org/docs/Report%20on%20Low%20Latency%20DASH.pdf (DASH focus)
• https://github.com/video-dev/hlsjs-rfcs/pull/1. (HLS focus)

and from vendors:

• https://bitmovin.com/cmaf-low-latency-streaming/
• https://websites.fraunhofer.de/video-dev/dash-js-low-latency-streaming-with-cmaf/
• https://aws.amazon.com/blogs/media/alhls-apple-low-latency-http-live-streaming-explained/

Note - a common use case often quoted in the broadcast world is the case where someone watching a live event like a game may hear their neighbours celebrating a goal or touchdown before they see it themselves, because their feed has higher latency than their neighbours. While this is a driver for low latency, this is really a synchronisation issue which would require other solutions if a 'perfectly' synchronised solution was the goal.

As you can see low latency streaming is not a simple challenge and it may be that you want to consider other approaches depending on the details of your use case, including how many subscribers you have, whether some loss of quality if a fair trade off for lower latency etc. As mentioned by @user1390208 in the comments, a more real time focused video communication technology like WebRTC may be a better match for the solution you are targeting.

If you want to provide a service that provides life streaming and also a recording, you may want to consider using a real time protocol for the live streaming view and HLS/DASH streaming for anyone looking back through recordings where latency may not be important but quality may be more key.