The tag I am looking for is Original Year, not original date. On Tue, Jun 7, 2016 at 11:39 PM, Adrian Sampson <[email protected]> wrote:
> Thanks for sending the output; it’s weird that Google Groups wouldn’t let > you send those files! > > I found this line in the metaflac output: > > comment[49]: ORIGINALDATE=2012-04-13 > > So it looks like the data’s in the right place. I’m not sure why Picard or > Foobar wouldn’t display the tag. > > On Jun 7, 2016, at 8:29 PM, Andy Pastuszak <[email protected]> wrote: > > I'll email them to you direct. > > Andy > > > On Tue, Jun 7, 2016 at 11:28 PM, Adrian Sampson <[email protected]> > wrote: > >> Hmm, no—were there attachments? Perhaps Google Groups filtered them? >> >> On Jun 7, 2016, at 8:23 PM, Andy Pastuszak <[email protected]> wrote: >> >> Did you delete the post with the attachments? >> >> On Tuesday, June 7, 2016 at 10:05:34 PM UTC-4, Adrian Sampson wrote: >>> >>> Yes, please include all the output. >>> >>> On Jun 7, 2016, at 6:50 PM, Andy Pastuszak <[email protected]> wrote: >>> >>> Ok when I do beet info, it shows the two missing tags: original_year >>> and mb_trackid. But when I look at the tracks in Musicbrainz Picard I >>> don't see either track. In Foobar2000, I see the MUSICBRAINZ_TRACKID tag, >>> but I don't see original year. >>> >>> When I use metaflac with the --list option, it does not show an original >>> year tag of any kind. I can use both commands and paste the output in, if >>> you're interested. >>> >>> Andy >>> >>> >>> On Monday, June 6, 2016 at 4:06:12 PM UTC-4, Andy Pastuszak wrote: >>>> >>>> Sure. I'll play with it tonight. Thanks for getting back to me. >>>> >>>> On Sunday, June 5, 2016 at 12:21:08 AM UTC-4, Adrian Sampson wrote: >>>>> >>>>> That should be fine. Can you look at the metadata with the `beet info` >>>>> command (for which you’ll need to enable the `info` plugin) and compare >>>>> that to what Picard sees? If there’s a mismatch, there may be a >>>>> compatibility plugin in either Picard or beets. >>>>> >>>>> On Jun 4, 2016, at 9:04 PM, Andy Pastuszak <[email protected]> wrote: >>>>> >>>>> Perhaps I am doing something wrong. I have a folder full of songs for >>>>> the album California 37 by Train. I did a beets import and it imported >>>>> them and found the correct release. Just to make sure tags were written, >>>>> I >>>>> used the beet write command. When I load the files back up in Picard, >>>>> they >>>>> don't have the Original Year or Musicbrainz Tracck ID tags. >>>>> >>>>> Does this have anything to do with the fact that I have FLAC files >>>>> with Vorbis comments? >>>>> >>>>> On Friday, June 3, 2016 at 12:34:32 AM UTC-4, Adrian Sampson wrote: >>>>>> >>>>>> Hi! I’m glad you’re enjoying beets. It does actually fetch the >>>>>> original year: >>>>>> >>>>>> $ beet fields | grep original >>>>>> original_day >>>>>> original_month >>>>>> original_year >>>>>> >>>>>> You can see it by typing something like: >>>>>> >>>>>> $ beet list -af '$original_year $album' >>>>>> >>>>>> > On Jun 2, 2016, at 8:01 PM, Andy Pastuszak <[email protected]> >>>>>> wrote: >>>>>> > >>>>>> > I have been using MusicBrainz Picard to tag all my music and have >>>>>> been playing with beets and loving it. >>>>>> > >>>>>> > One of things I noticed is that beets does not use the Musicbrainz >>>>>> tag "Original Year," which is something I use quite a lot. Is there a >>>>>> way >>>>>> to get beets to write this tag to the metadata of my files? >>>>>> > >>>>>> > Andy >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > You received this message because you are subscribed to the Google >>>>>> Groups "beets" group. >>>>>> > To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to beets-users...@googlegroups. >>>>>> <http://googlegroups.com/>com <http://googlegroups.com/>. >>>>>> > For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "beets" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> >>>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "beets" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "beets" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "beets" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > You received this message because you are subscribed to the Google Groups > "beets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "beets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "beets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
