# RELEASETIME - problem getting JRiver to recognise it
**URL:** https://community.mp3tag.de/t/releasetime-problem-getting-jriver-to-recognise-it/68369
**Category:** Support
**Tags:** player
**Created:** [May 1, 2025, 11:36am UTC](https://community.mp3tag.de/t/releasetime-problem-getting-jriver-to-recognise-it/68369 "2025-05-01T11:36:44Z")
**Posts on this page:** 5
**Page:** 2
### Author:  [@Noteworthy](https://community.mp3tag.de/u/Noteworthy)
#### Post date: [May 2, 2025, 1:27pm UTC](https://community.mp3tag.de/t/releasetime-problem-getting-jriver-to-recognise-it/68369/21 "2025-05-02T13:27:53Z")
The problem here is that for flac files, RELEASETIME is contained in the Vorbis comment block that imported and hence not recognised.
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [May 2, 2025, 2:48pm UTC](https://community.mp3tag.de/t/releasetime-problem-getting-jriver-to-recognise-it/68369/22 "2025-05-02T14:48:05Z")
I would ask over there in the JRiver forum why they don't support a formatted date that is directly human-readable for everyone (without calculation of any datediffs to 1900).
* * *
But I believe, I have found a workaround in JRiver:
JRiver let you ADD whatever field you like in
Ctrl + O (Tools -\> Options) -\> Library and Folders -\> Manage Library Fields
There you can click on Add New Field
There you can - for example - add a new field called `MY_RELEASETIME`
The most important thing is: DO NOT CHOOSE Data Type **Date**!
Choose **String** as Data Type.
And activate "Save in file tags (when possible)"
After closing the Tag Panel in JRiver and reopening it, you should see your new added custom field `MY_RELEASETIME` between all other field names.
You can now enter whatever you want into this MY\_RELEASETIME in JRiver
and this value will also be visible in Mp3tag
You can change and save MY\_RELEASETIME in Mp3tag.
Then you can "Update Library (from Tags)" in JRiver and see the changed values.
This interchange works - tested - for FLAC files.
You need to test it with your FLAC files.
Please try if this also works with your existing RELEASETIME ISO date format by defining it NOT as "Date" but as "String" instead.
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [May 2, 2025, 3:08pm UTC](https://community.mp3tag.de/t/releasetime-problem-getting-jriver-to-recognise-it/68369/23 "2025-05-02T15:08:02Z")
Just for the record:
JRiver seems to use an "internal floating-point representation... to store a date and time" and offers own internal functions like **ConvertDate(...)** to create such numbers.
[External JRiver Source](https://wiki.jriver.com/index.php/Date_and_Time_Functions#ConvertDate(%E2%80%A6))
---
### Author:  [@Noteworthy](https://community.mp3tag.de/u/Noteworthy)
#### Post date: [May 3, 2025, 6:27am UTC](https://community.mp3tag.de/t/releasetime-problem-getting-jriver-to-recognise-it/68369/24 "2025-05-03T06:27:36Z")
@LyricsLover,
Many thanks for your inputs.
Your solution really works well.
I hope our exchanges and more importantly, your research will be of great use to readers of this forum who use JRiver like me.
There are a great many who have JRiver but who have historically tagged their media with MP3Tag as I have seen on the JRiver support forum.
I received [a similar solution](https://yabb.jriver.com/interact/index.php/topic,141196.0.html) on the JRiver forum last night.
Many, Many THANKS once again.
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [June 2, 2025, 6:28am UTC](https://community.mp3tag.de/t/releasetime-problem-getting-jriver-to-recognise-it/68369/25 "2025-06-02T06:28:28Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
[Previous page](https://community.mp3tag.de/t/releasetime-problem-getting-jriver-to-recognise-it/68369.md?page=1)