Fix #119

[ohnx]

Also switched to my fork of node-ffmetadata, where the issues writing covers should be fixed. (from testing, this seems to be true.)

[benkaiser]

Looks good, I'll test it out locally later today and merge if it all works fine :)

[benkaiser]

Just tested it out, works great! Thanks @ohnx

[benkaiser]

@ohnx can you also create a PR to node-ffmetadata with your fix? I'm happy keeping it as your fork until they accept the PR though

[benkaiser]

Also in future, you don't need to publish your fork to use it in package.json, you can directly refer to a git repo :)

[ohnx]

@benkaiser The repo creator doesn't like having the flag map 0 set, since it breaks some part of their workflow.

parshap/node-ffmetadata#11 : "This would have to be an option, as in my own workflow I like to strip all extra data out of audio file and re-attach my own cover art."

I can make it an option, I suppose, and then make a PR.

[benkaiser]

I see, so does your change break for m4a files?

I'd at least recommend commenting on that issue and asking how they would like a fix implemented, if parshap wants it behind an option then we can use that option in Stretto.