# Composer Field Not Uploading Correctly **URL:** \ **Category:** Support\ **Created:** [April 30, 2025, 10:22am UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351 "2025-04-30T10:22:45Z")\ **Posts on this page:** 9\ **Page:** 4
**Author:** ![mattiebear](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e47c2d/32.png) [@mattiebear](https://community.mp3tag.de/u/mattiebear)\ **Post date:** [May 1, 2025, 4:02pm UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351/61 "2025-05-01T16:02:54Z")
This works!!! Thank you so much!! ---
**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\ **Post date:** [May 1, 2025, 4:11pm UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351/62 "2025-05-01T16:11:45Z")
> [@mattiebear](#): > > It's not clear if you are saying the Preserve file modification should be ticked or not: If you want Mp3tag to change the modification time of your files every time you change something in your fields, leave it UNTICKED/DISABLED (as shown in screenshot). This way, external software can use this changed date to decide what to do ("backup", "update"...). If you don't want Mp3tag to change this date and time, ENABLE/CHECK this setting and preserve the modification time = keep it unchanged even if you change something inside the file. > [@mattiebear](#): > > Plus the oddest thing is that csv upload was to update the conductor and the genre fields. It uploaded and showed the genres fields perfectly but not the conductor field? If you are still interested to solve this part of the problem, please open a new thread. Then we can start from scratch with your import and CSV - now that you know how to refresh metadata in MusicBee and show such external changes. ---
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [May 1, 2025, 4:15pm UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351/63 "2025-05-01T16:15:11Z")
> [@mattiebear](#): > > So in theory there needs to be some kind of refresh. Also in practice. And this hint to handle a 3rd party program could already be seen 55 posts ago: > [@ohrenkino](#): > > Here is a thread to update the Musicbee cache - perhaps you have to do that to show updated data in Musicbee: ---
**Author:** ![MotleyG](https://community.mp3tag.de/user_avatar/community.mp3tag.de/motleyg/32/440_2.png) [@MotleyG](https://community.mp3tag.de/u/MotleyG)\ **Post date:** [May 1, 2025, 5:48pm UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351/64 "2025-05-01T17:48:19Z")
@mattiebear I do believe the efforts that several people have made over the past two days could have been reduced significantly if the original suggestions had been applied. @ohrenkino@LyricsLover@poster and I all suggested at various times from the beginning that you needed to refresh the MusicBee library to capture any changes made externally, i.e using mp3tag. Bottom line - virtually ALL players use an INTERNAL library for managing their data. If for whatever reason you are managing metadata for your music files externally, these music players almost ALWAYS neeed to have this library forced to refresh. Some make this process easier than others. Please be aware of how to do this with your personal player of choice. This is not a function of mp3tag! ---
**Author:** ![mattiebear](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e47c2d/32.png) [@mattiebear](https://community.mp3tag.de/u/mattiebear)\ **Post date:** [May 3, 2025, 7:44pm UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351/65 "2025-05-03T19:44:56Z")
I want to acknowledge that I wasn't able to follow the instructions provided by certain users, but I think it's important to highlight _why_. The tone in which the guidance was provided came across as patronizing and condescending, which made it harder for me to engage and learn from. If the advice had been offered with more respect and patience, I believe I could have resolved this issue much more quickly. It's interesting that after specifically stating I did not want to engage with a specific user, instead of respecting this, they decided to ignore me and continue to comment, resulting in a 'told you so' post at the end. But this isn’t about pointing fingers—it's a reminder that how we communicate matters just as much as _what_ we communicate. I'm sure you're all here to help others, and a bit more empathy and humility can go a long way. ---
**Author:** ![Doug\_Mackie](https://community.mp3tag.de/user_avatar/community.mp3tag.de/doug_mackie/32/279_2.png) [@Doug\_Mackie](https://community.mp3tag.de/u/Doug_Mackie)\ **Post date:** [May 3, 2025, 11:26pm UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351/66 "2025-05-03T23:26:57Z")
> [@mattiebear](#): > > The tone in which the guidance was provided came across as patronizing and condescending... That, my friend, was entirely in your head. You provided few details at first, which meant that you received requests for more info. That was not condescension, but simply a need for details. > [@mattiebear](#): > > ... after specifically stating I did not want to engage with a specific user, instead of respecting this, they decided to ignore me and continue to comment.... You do not control who responds here. Ohrenkino is a senior and vital contributor, and he made an important observation in this thread: > [@ohrenkino](#): > > MediMonkey and Musicbee both use a database AFAIK that needs updating to show modified data. > So far I have not heard that you have triggered that process. You ignored his suggestion, which was in fact the key to solving your issue. Instead, you proceeded to insult him. > [@mattiebear](#): > > ... a bit more empathy and humility can go a long way. We do not need to be lectured. Responders here are volunteers and their time and experience are valuable. They are not here to hold your hand. If you require more "empathy and humility" then perhaps this forum is not for you. ---
**Author:** ![mattiebear](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e47c2d/32.png) [@mattiebear](https://community.mp3tag.de/u/mattiebear)\ **Post date:** [May 4, 2025, 1:41pm UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351/67 "2025-05-04T13:41:36Z")
Oh I agree with you completely! At this point its entertaining me how upset you're all getting. You carry on lovely. ❤❤❤ ---
**Author:** ![MotleyG](https://community.mp3tag.de/user_avatar/community.mp3tag.de/motleyg/32/440_2.png) [@MotleyG](https://community.mp3tag.de/u/MotleyG)\ **Post date:** [May 4, 2025, 2:04pm UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351/68 "2025-05-04T14:04:26Z")
I believe it is safe to say this thread has run its course. The solution for the original request has been provided. ---
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [May 4, 2025, 2:21pm UTC](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351/69 "2025-05-04T14:21:24Z")
The solution has been found. [Previous page](https://community.mp3tag.de/t/composer-field-not-uploading-correctly/68351.md?page=3)