# Decoder "MAD" betrayed us on ... / NFSv4 problem?

**URL:** <https://discourse.libretime.org/t/decoder-mad-betrayed-us-on-nfsv4-problem/376>\
**Category:** Get Help\
**Created:** [September 12, 2019, 3:25pm UTC](https://discourse.libretime.org/t/decoder-mad-betrayed-us-on-nfsv4-problem/376 "2019-09-12T15:25:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![unosonic](https://avatars.discourse-cdn.com/v4/letter/u/67e7ee/32.png) [@unosonic](https://discourse.libretime.org/u/unosonic)\
**Post date:** [September 12, 2019, 3:25pm UTC](https://discourse.libretime.org/t/decoder-mad-betrayed-us-on-nfsv4-problem/376/1 "2019-09-12T15:25:05Z")

</div>

my media stor is on a NFSv4 share. Uploading tracks works, permissions / ownership are ok. I can play all uploaded sounds in preview, but they don’t play in a stream:  
ls\_script.log:  
`[decoder:2] Decoder "MAD" betrayed us on "/var/tmp/airtime/pypo/cache/scheduler/10.mp3"!`  
`[dummy(dot)3:3] Source failed (no more tracks) stopping output...`  
10.mp3 is a empty file, 0 Bytes. But of course it isn’t in the file store. Seems copy to pypo/cache/scheduler/ failes somewhere.  
any help apprechiated!

---

<div class="post-metadata">

**Author:** ![robbt](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/robbt/32/15_2.png) [@robbt](https://discourse.libretime.org/u/robbt)\
**Post date:** [September 13, 2019, 12:38pm UTC](https://discourse.libretime.org/t/decoder-mad-betrayed-us-on-nfsv4-problem/376/2 "2019-09-13T12:38:00Z")

</div>

This seems like a permission issue with airtime-pypo which copies things to other directories as part of the staging for liquidsoap.

---

<div class="post-metadata">

**Author:** ![unosonic](https://avatars.discourse-cdn.com/v4/letter/u/67e7ee/32.png) [@unosonic](https://discourse.libretime.org/u/unosonic)\
**Post date:** [September 13, 2019, 10:39pm UTC](https://discourse.libretime.org/t/decoder-mad-betrayed-us-on-nfsv4-problem/376/3 "2019-09-13T22:39:33Z")

</div>

I’ve initialized it again (rm airtime.conf), then rebooted everything and now it seems to work. May have been a local problem, will observe it for a while.