Author Topic: Copy Failed-Year, Month, Day parameters describe an un-representable DateTime  (Read 5083 times)

rak

  • Newbie
  • *
  • Posts: 12
I found one post about this.  It was from 2012, with no answer.  I have this issue with one track, a podcast.  Everything else synced fine.  I've used several tag editors to try and figure out what the year, month, day issue is with no luck.  Anyone else?  Solution?

psychoadept

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10711
So this happened while you were trying to sync? Steven may be able to make sense of it, but it would probably be helpful to have the full error text.
MusicBee Wiki
Use & improve MusicBee's documentation!

Latest patches (3.5/3.6)
(Unzip and overwrite existing program files)

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 9441
What version of MB are you using? (Help > About)
How was MB installed? (Installer, Portable, Store)

Where were you copying from and to? And how?
Have you tried looking with the Tag Inspector?
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

abaez

  • Newbie
  • *
  • Posts: 12
I have this same error. Here's the full text: https://i.imgur.com/WIWpPkd.png

Using the newest musicbee portable version 3.3.7491, syncing from my PC to my phone as I have done for many years.

It's only happening with three files out of several hundred. I have tried looking at the tags, file properties, everything I can think of. Nothing seems to fix it.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34416

abaez

  • Newbie
  • *
  • Posts: 12
I figured it out. The year tag was set to 0000. I guess Musicbee doesn't like that.

Folksong

  • Newbie
  • *
  • Posts: 4
Just wandering in to say this is still an issue. I had it on a podcast and the year was set to 0000 in the tags. But all I was asking it to do is transfer the file to the device, so there's no reason for MusicBee to worry about whether the year is valid.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34416
I cant think of any reason the value of the Year tag would matter to musicbee itself - its probably the device throwing an error. Do you have an entry in the error log (help/ support/ view error log)

Folksong

  • Newbie
  • *
  • Posts: 4
Thanks for the response, here's what's in the log:

7/28/2023 11:36:45 PM - Copy D:\iTunes Music\Music\MusicBee\Podcasts\If Books Could Kill\Liberal Fascism.mp3 to vívoactive 4\Primary\Podcasts\Liberal Fascism.mp3
7/28/2023 11:36:45 PM - Year, Month, and Day parameters describe an un-representable DateTime.

Folksong

  • Newbie
  • *
  • Posts: 4
Also I tried copying the rejected file to the device in Windows and it worked, so I don't think the error is coming from the device. It's an MTP device, and I'm synchronizing with "preserve folders and filenames" selected in the options. Probably it's reading the tags in case the other option "use naming template" is selected.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34416
its a bit of a mystery. Could you use this version and send me the new info in the error log
https://mega.nz/file/ksNyVRwQ#mJxDlLaIShp9z0Nt1AxkerupbLEpM9yZq3Jd9JmyKCY
unzip and replace musicbee.exe

edit:
i think i found where the error occurs
https://getmusicbee.com/patches/MusicBee35_Patched.zip
unzip and replace the existing musicbee application files
Last Edit: July 29, 2023, 01:06:26 PM by Steven

Folksong

  • Newbie
  • *
  • Posts: 4
I jumped straight to MusicBee35_Patched. Seems to fix the issue. Thanks!

It looks like every episode of the "If Books Could Kill" podcast has the issue, so it's a good one to test with.

I did see find this in the log after synchronizing, not sure what it was referring to:

7/29/2023 1:05:34 PM - 10.0.19045.0 - 3.5.8610.39724D - System.ArgumentException: An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at #=zmPK226QV1w4CypcUm4X3jjESCi4X.#=z7JUztxN9Hdma(String #=zbquJf56__00M)
   at #=zmPK226QV1w4CypcUm4X3jjESCi4X.#=zqN31dDY=(#=z5ggDNgtG00c6RitqnwTc4vM= #=z$jCxNj0=)
   at #=zSSU$7tRoCmpjsQ46GjOSdm0=.#=zqN31dDY=()
   at #=zJOyG7Q4lFlS8Fj75vje6_B0=.#=z3LyCDGtPX2IL(#=z6xZcNeM= #=zxrgvkx0=)

EPa

  • Newbie
  • *
  • Posts: 3
Hi,

found a bug (that probably noone besides me will ever run into, ever) concerning this:

If any file in the library has an "original year" set to "0000" then any playlists using "original year" fail.

How to reproduce:
- make an autoplaylist using original year and make sure it works
- go to the library and set any file's original year to "0000"
- get back to playlists and try to see the above mentioned list. Boom!

On the top you get the error message
Unable to access <wherever is is the lists are stored><name of your list>.xautopf (which is mileading because the said file IS accesed, see next sentence)

BUT the list is still available for edit, and if you get in the edit window (menu option "Edit AutoPlaylist..."), then uncheck "automatically refresh the matching tracks" so that you can press the "Refresh" button you get the "Musicbee Error" window with the following contents:

MusicBee v3.5.8698.34385D  (Win10.0), 18 Μαϊ 2024 17:18:

System.ArgumentOutOfRangeException: Year, Month, and Day parameters describe an un-representable DateTime.
   at System.DateTime.DateToTicks(Int32 year, Int32 month, Int32 day)
   at #=zEytQFn53YZ3N6xbbPb7I8Us=.#=zjtiidx55_VDLVuMYPA==(String #=z0InSzQg=)
   at #=zEytQFn53YZ3N6xbbPb7I8Us=.#=z25lvPe0dlgnr7pQKBA==(String #=z0InSzQg=)
   at #=zEytQFn53YZ3N6xbbPb7I8Us=.#=zO5u4YGGOsNnp(#=zrHxbKbKSSpgwvOQhk_k8Zbo= #=z_LPN_w8=)
   at #=zEytQFn53YZ3N6xbbPb7I8Us=.#=zj4iwa5MV$flI(#=zrHxbKbKSSpgwvOQhk_k8Zbo= #=z_LPN_w8=)
   at #=zySHSOrj$pQ97dbt8jzcgTTs=.#=zvgiFjH8=(#=zrHxbKbKSSpgwvOQhk_k8Zbo= #=z_LPN_w8=)
   at #=zIysDyiQbAwxpL8rtCkDKoh0=.#=zvzkqMqikjBd6(IList`1 #=zIVXNi6nII6JD, #=zySHSOrj$pQ97dbt8jzcgTTs= #=zh6TovV8=)
   at #=zQxE86buYw_2J$txTjEAt3bjEFKSp.#=zx44HXsMtaAbH(TriState #=zDW$HAxKOM0_6)
   at #=zQxE86buYw_2J$txTjEAt3bjEFKSp.#=zbz980bMd2WAv()
   at #=zasSRk87NCN$KpBsIIr0YuMolN5Zl.#=zFu6VnWm0NfWW(Object #=zkMMOivE=, EventArgs #=zK60pSUM=)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at #=za$uE3YFEXt8$1JF1f48L26s=.OnClick(EventArgs #=zK60pSUM=)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Obviously this is a very exceptional case but it happened to me. If you're wondering why on earth would anyone enter 0000 in the Original Year of a file, well... it's a long story.

Cheers!

PS: MusicBee is the GOAT music manager, thanks for that Steven!

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34416
If any file in the library has an "original year" set to "0000" then any playlists using "original year" fail.
thats fixed now:
https://getmusicbee.com/patches/MusicBee35_Patched.zip
unzip and replace the existing musicbee application files

EPa

  • Newbie
  • *
  • Posts: 3
Ok, I have seen your answer about this patch a number of posts earlier, but that post was from July and I already have the latest musicbee installed (which is dated October, so 3 months later than the patch) I thought this patch was already incorporated into the last version and thought that had to be a new case of the bug.

May I ask why this patch didn't make it to the last musicbee version?