# Move files to an other volume

**URL:** <https://community.mp3tag.de/t/move-files-to-an-other-volume/51566>\
**Category:** Mac\
**Created:** [January 14, 2021, 9:57am UTC](https://community.mp3tag.de/t/move-files-to-an-other-volume/51566 "2021-01-14T09:57:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Metaman](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e99b99/32.png) [@Metaman](https://community.mp3tag.de/u/Metaman)\
**Post date:** [January 14, 2021, 9:57am UTC](https://community.mp3tag.de/t/move-files-to-an-other-volume/51566/1 "2021-01-14T09:57:05Z")

</div>

I want to move music files from my Mac Book to my NAS, which is mounted as a volume.  
I tried to do this by "Conversions" and file rename. But I do not know how to insert the wished volume into the format string.  
Does anyone knows a solution?

---

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [January 14, 2021, 9:59am UTC](https://community.mp3tag.de/t/move-files-to-an-other-volume/51566/2 "2021-01-14T09:59:51Z")

</div>

Let's assume your mounted volume is named `Target`. A valid format string for renaming via "Tag - Filename" would then begin with `/Volumes/Target/`

---

<div class="post-metadata">

**Author:** ![Metaman](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e99b99/32.png) [@Metaman](https://community.mp3tag.de/u/Metaman)\
**Post date:** [January 14, 2021, 11:11am UTC](https://community.mp3tag.de/t/move-files-to-an-other-volume/51566/3 "2021-01-14T11:11:40Z")

</div>

That sounds easy. Thanks for your quick reply.  
I will test it.

---

<div class="post-metadata">

**Author:** ![Metaman](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e99b99/32.png) [@Metaman](https://community.mp3tag.de/u/Metaman)\
**Post date:** [January 14, 2021, 11:27am UTC](https://community.mp3tag.de/t/move-files-to-an-other-volume/51566/4 "2021-01-14T11:27:48Z")

</div>

It seems to work. But there is a follow up problem with access rights:

 ![grafik](https://community.mp3tag.de/uploads/default/original/2X/9/9599b419667e19be22f35efcb9cdfc3585a8ff60.jpeg)

How can I fix this?  
There is no access problem on Finder or OS level.

---

<div class="post-metadata">

**Author:** ![Metaman](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e99b99/32.png) [@Metaman](https://community.mp3tag.de/u/Metaman)\
**Post date:** [January 15, 2021, 7:41am UTC](https://community.mp3tag.de/t/move-files-to-an-other-volume/51566/5 "2021-01-15T07:41:41Z")

</div>

Florian and I are currently investigating this problem by PM.  
Maybe it will help, if any other user can confirm this problem.  
Can you move files with the rename function to a mounted volume (NAS, server, cloud) without any problems or do you get an access violation error, too?

Dankeschön

---

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [January 15, 2021, 2:06pm UTC](https://community.mp3tag.de/t/move-files-to-an-other-volume/51566/6 "2021-01-15T14:06:45Z")

</div>

We've boiled it down to an inconsistency in Mp3tag's way of storing secure bookmarks, which are needed to access files and folders for sandboxed apps.

It's still unclear how this inconsistency appeared and I'm interested in other examples and further research of problems related to that. However, for now, clearing the bookmark cache resolved the issue.

---

<div class="post-metadata">

**Author:** ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)\
**Post date:** [February 14, 2021, 2:07pm UTC](https://community.mp3tag.de/t/move-files-to-an-other-volume/51566/7 "2021-02-14T14:07:00Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
