# Sound quality opinions? **URL:** \ **Category:** Organelle\ **Created:** [June 22, 2017, 1:49pm UTC](https://forum.critterandguitari.com/t/sound-quality-opinions/1369 "2017-06-22T13:49:07Z")\ **Posts on this page:** 1\ **Showing post:** 28
**Author:** ![thetechnobear](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.critterandguitari.com/thetechnobear/32/42_2.png) [@thetechnobear](https://forum.critterandguitari.com/u/thetechnobear)\ **Post date:** [September 19, 2017, 9:05pm UTC](https://forum.critterandguitari.com/t/sound-quality-opinions/1369/28 "2017-09-19T21:05:38Z")
> [@oweno](#): > > Although it is still possible to get messed up if a user has an old mother.pd in a patch folder, so ideally there would just be a version tag in mother.pd and it wouldn’t get loaded if it didn’t match OS version. yeah. this is a concern, as Ive seen past posts here, with errors related to using customised mother patches. the issue is , I don’t want to load the mother patch, only then to have to unload it because its the wrong version… but I guess, given a pure data patch (mother.pd) is just plain text, I can easily search it for a version tag… say in a comment. also I think we could version the mother patch (=protocol) separately from the mother host, so that we only update the motherpd version, if something is changed in it that we know is means ‘custom mother.pd’ need reviewing… which I think is not often the case. there is a slight issue, how to notify the user, that his custom mother.pd has been ignored? I guess we could try to find a way to flash a message on the display… but that’s going to be a bit annoying. (hmm, we could then move the mother.pd, to mother.pd.old, so its only displayed once) --- _[View the full topic](https://forum.critterandguitari.com/t/sound-quality-opinions/1369)._