# MCEBuddy writing incomplete/invalid metadata

**URL:** https://discussion.mcebuddy2x.com/t/mcebuddy-writing-incomplete-invalid-metadata/3242
**Category:** Bugs
**Tags:** metadata
**Created:** [November 11, 2019, 9:14am UTC](https://discussion.mcebuddy2x.com/t/mcebuddy-writing-incomplete-invalid-metadata/3242 "2019-11-11T09:14:27Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Mike-EEE](https://discussion.mcebuddy2x.com/user_avatar/discussion.mcebuddy2x.com/mike-eee/32/1230_2.png) [@Mike-EEE](https://discussion.mcebuddy2x.com/u/Mike-EEE)
#### Post date: [November 11, 2019, 9:14am UTC](https://discussion.mcebuddy2x.com/t/mcebuddy-writing-incomplete-invalid-metadata/3242/1 "2019-11-11T09:14:27Z")

</div>

**Request Type:**  
BUG

**MCEBuddy Version and Type (32bit or 64bit):**  
2.5.1 (02 Nov) - 64-bit

**Operating System and Type (32bit or 64bit):**  
Windows 10 64-bit

**Summary of the problem or suggestion:**  
I’ve been battling a Plex issue for some time:

> **[Plex Live TV DVR Not Capturing Date/Originally Available](https://forums.plex.tv/t/plex-live-tv-dvr-not-capturing-date-originally-available/465950)**
>
> Running into an issue here where the date is not being picked up by Plex 1.17.0.1709: Help. 🙂

Turns out that when enabling the metadata download in MCEBuddy, the video’s `Year` value gets set to 1900. So it would seem the year is not being accurately captured and/or assigned.

Note that I disabled MCEBuddy’s metadata download and the year was no longer set. However, since there are several moving pieces here between MCEBuddy and Plex, there could be another variable at play here that I do not understand. I did not see anything else in settings that was obvious to this issue.

Ideally, the `Year` value would not be set which would allow Plex to set its own record on its side (for sorting purposes).

**Steps to replicate the bug:**

Enable metadata downloading, process video.

**Screenshots:**  
 ![2019-11-11%20(1)](https://discussion.mcebuddy2x.com/images/transparent.png)

Logs attached.

[NFL Football - S2019E2152 - Detroit Lions at Chicago Bears.ts-Football-2019-11-10T17-04-57.5681696-05-00.log](https://discussion.mcebuddy2x.com/uploads/short-url/jnQkNUWaIeJ6UN2CmqXH6F1QUxi.log) (7.9 MB)

---

<div class="post-metadata">

### Author: ![Goose](https://discussion.mcebuddy2x.com/letter_avatar_proxy/v4/letter/g/5f9b8f/32.png) [@Goose](https://discussion.mcebuddy2x.com/u/Goose)
#### Post date: [November 11, 2019, 5:25pm UTC](https://discussion.mcebuddy2x.com/t/mcebuddy-writing-incomplete-invalid-metadata/3242/2 "2019-11-11T17:25:59Z")

</div>

You’re right, MCEBuddy shouldn’t be writing metadata which is invalid/non existent.  
This has been fixed in today’s 2.5.2 beta build. Thanks for reporting it.

---

<div class="post-metadata">

### Author: ![Mike-EEE](https://discussion.mcebuddy2x.com/user_avatar/discussion.mcebuddy2x.com/mike-eee/32/1230_2.png) [@Mike-EEE](https://discussion.mcebuddy2x.com/u/Mike-EEE)
#### Post date: [November 11, 2019, 5:58pm UTC](https://discussion.mcebuddy2x.com/t/mcebuddy-writing-incomplete-invalid-metadata/3242/3 "2019-11-11T17:58:42Z")

</div>

Awesome! Thank you for tackling that pronto! Very much appreciated. 👍