<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div apple-content-edited="true" class=""><br class="">
</div><div class="">This is something I’m interested in following up on, but my schedule is full, at the moment.</div><div class=""><br class="webkit-block-placeholder"></div><div class="">Ian</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 21 Sep 2017, at 21:19, Grimm | Eelco <<a href="mailto:eelco@grimmaudio.com" class="">eelco@grimmaudio.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Dear MLA friends,<div class=""><br class=""></div><div class="">Like Bob Ludwig has brought up more than once, the UMG Watermarking of files by Universal is an even worse problem than low bit rate codecs. According to my old Tidal contact, Universal had stopped adding the mark to new masters. I asked confirmation from my Spotify contact and he wrote:</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">What we've heard is that they still use it, but they've improved it a lot so it's almost inaudible ... that's supposed to have happened ca 2014/2015. So we've tried to push them to redeliver their entire back catalog with the new watermarking, but so far they've been completely unyielding - and they also say they haven't changed the watermarking either :/</blockquote><br class=""></div><div class="">This is new to me. Does anyone have more information about this?</div><div class="">I asked him for a hint about who to pressure. And he wrote:</div><div class=""><br class=""></div><div class=""><div class="gmail_quote"></div><blockquote type="cite" class=""><div class="gmail_quote">No idea who to pressure - I would imagine contacting tech sites like The Verge could be effective. Did I send the link to the blog posts one of our employees has made? <a href="https://www.mattmontag.com/page/3" class="">https://www.mattmontag.com/page/3</a></div><div class="gmail_quote">That could perhaps be used to point newspapers to the problem. He started writing about it before joining Spotify, but has followed up (still on his private blog) a couple of times. Just make sure not to mention you've been in contact with us officially ... we certainly don't want it to be seen as us putting pressure on them, even if that's what we want to do :)</div></blockquote><br class=""></div><div class="">Is there anything we can do?</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Eelco</div></div>_______________________________________________<br class="">MLA mailing list<br class=""><a href="mailto:MLA@grimmaudio.nl" class="">MLA@grimmaudio.nl</a><br class="">http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl<br class=""></div></blockquote></div><br class=""></body></html>