Simon Kusterer

First of all thanks for the response and for making my text more readable :-) I see Processors as independed of `Response.create`. Just an example why I think they should...

I could output the current playback time if that helps? Just don't know if it would be so easy to parse. Maybe we need something like `--output-format json`?

You can access the current playback position through `p.getPostion()` or listen to `position`-events in the ctrl-function: ``` javascript p.on('position', function(pos) { console.log(pos.position); }); ```

Nice to hear. I'll keep it open since I like the idea of having a parseable output.

I already tried it with -ss. It does not work (can't remember the exact reasons) :( However, it will work if someone takes the code from https://github.com/xat/hls-chromecast-demo and integrates it...

Thanks for the kind words :) So your TV does not have any audio output in general? Not just when using castnow? I don't think there is a proper solution...

Did you try it with the --tomp4 parameter (requires ffmpeg)?

@cristianciofu I think your having a different problem. Most likely castnow is not finding your chromecast dongle in the network. This could be a firewall problem. You can also try...

The player instance now can be destroyed like this: ``` javascript player.launch('', function(err, p, ctx) { setTimeout(function() { ctx.shutdown(); }, 5000); ctx.on('closed', function() { console.log('player got shutdown'); }); }); ```...

Nice, but you should run the shutdown() method even if it works without. shutdown() will unlisten eventListeners and stop the setInterval created by the timeline helper. Otherwise it will leek...