Jump to content

2mr2

  • Posts

    3
  • Joined

  • Last visited

  • Country

    Canada

Retained

  • Member Title
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Unzip the file. Drag the plist file into Yate's main window's file list area ... or do a Yate>Import Preferences and select the plist file. Either way the action will then be in the Action Manager.
  2. Hi, I just found this thread. In full disclosure ... I'm the lead developer of Yate. Lot's of transcoders eliminate metadata which is not well known. Others modify the representative names such the software such as Roon no longer detect the items. Yate has a Copy Metadata feature on the Actions menu. Basically you can load two encodings of the same album into the UI and copy the metadata between the two encodings. You can copy all metadata or be selective about it. All conversion of the metadata for the appropriate audio format is done for you. The process is also supported by action statements. As far as Roon goes, Yate's resource page (accessible on the Help menu) has items in the Templates section which when installed will create Roon required custom fields and also supplies a Custom editing panel. The advantage of using custom fields is that you don't have to worry about the low level representation of the items.
  3. Hi, someone just pointed this thread out to me so I thought I should respond. I'm the lead developer of Yate in 2ManyRobots. Audio File Health Check strives to report all items which are out of spec and sever container errors which might affect the playback of a track. An issue being reported does not mean that an audio file will not be played correctly nor does it mean that the tagging information will not parse correctly. Yate 'works around' hundreds out-of-spec' issues in mp3s and every other audio format that it processes......as does virtually every other tag editor and player out there. If any player out there adhered to a 100% interpretation of the various ID3 specifications, it would not decode the tag information in a large number of mp3s that exist today. However, lots of older mp3s have issues such as extra padding (or garbage data) after an ID3 tag before the start of the audio stream. While some players such as iTunes will correctly process the stream, there are other audio applications which mess up or fault on the extraneous data. The utility is useful in detecting these types of issues. The utility was created and supplied free of charge simply because we had been asked for it, we think it has some interesting features and there are a number of streamers out there which adhere a little too closely to published specs. We supply quite a few applications for free because we think they will be useful and we quite frankly don't see charging for them. As far as the utility not repairing any issues, that is correct. It is a diagnostic tool... which may be useful if you are encountering problems. Rather than pick and choose what not to report, we report everything we find, (even trailing nils after the actual comment text in a COMM frame which is not nil terminated in the spec). Yate can fix any (non fatal) issue reported and it can do it in Batch Mode. However, as already mentioned here, many reported issues are benign and can be safely ignored ... which means you don't require any additional applications to fix them...Yate included.
×
×
  • Create New...