illustrate
Products            Buy            Support Forum            Registrations            Professional            About           
 

Non alphanumeric character handling

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • barkeyo
    replied
    Re: Non alphanumeric character handling

    Hi PeterP, unfortunately my Synology is a bit older, so it can't run DSM7. I don't know whether it's possible, but I'm happy to take a compiled build for DSM6 and put it through its paces. If it works, great, if not then I'll be fine to just re-install beta 3.

    Leave a comment:


  • PeterP
    replied
    Re: Non alphanumeric character handling

    No specific beta timeout in Asset Linux.

    Beta versions (also trial versions) can be installed on top of registered and retain registered status.

    The problem with DSM 6 is that I can compile, but can't test if what I just built works at all, as there's no way to downgrade my NAS back to DSM 6.

    Leave a comment:


  • barkeyo
    replied
    Re: Non alphanumeric character handling

    Originally posted by Spoon
    DSM6 cannot be compiled any more, it is frozen under legacy downloads.
    Hi Spoon, that's disappointing given that beta 3 was provided for both DSM6 and DSM7 only 3 weeks ago. In which case, can beta 3 be used indefinitely?

    Leave a comment:


  • Spoon
    replied
    Re: Non alphanumeric character handling

    DSM6 cannot be compiled any more, it is frozen under legacy downloads.

    Leave a comment:


  • barkeyo
    replied
    Re: Non alphanumeric character handling

    Originally posted by PeterP
    I'm sorry but non-Windows Asset R7.5 still has this bug. I just applied the fix for R7.6 beta which will be posted shortly.
    Hi, I see that a new release of Asset has been made, but a) I can't see whether this release includes the fix and b) I see no Synology DSM6 package available. The R7.6 betas 1, 2 and 3 I've been using specifically because of this fix, were for DSM6. Will a DSM6 compatible version including this fix be released, or has support for it now been terminated?
    Last edited by barkeyo; June 02, 2023, 07:31 PM.

    Leave a comment:


  • barkeyo
    replied
    Re: Non alphanumeric character handling

    Originally posted by PeterP
    I'm sorry but non-Windows Asset R7.5 still has this bug. I just applied the fix for R7.6 beta which will be posted shortly.
    Thanks for the update. I'll look forward to the release of R7.6

    Leave a comment:


  • PeterP
    replied
    Re: Non alphanumeric character handling

    I'm sorry but non-Windows Asset R7.5 still has this bug. I just applied the fix for R7.6 beta which will be posted shortly.

    Leave a comment:


  • barkeyo
    replied
    Re: Non alphanumeric character handling

    Hi Spoon,

    Can you confirm whether this Asset bug regarding the handling of "=" in the Vorbis Comment tags is fixed in the R7.5 release for Synology?

    Cheers

    Leave a comment:


  • barkeyo
    replied
    Re: Non alphanumeric character handling

    Originally posted by vilsen
    If this doesn't resolve for a while, you could try another workaround without touching the ALBUM tag.

    In Asset's Rename List, add the line
    Code:
    album:=(Unknown Album):==
    Then restart & refresh all.
    Hi vilsen, thanks for that suggestion, which I can confirm works a treat. I was reticent to start editing the actual ALBUM tag of the files themselves, since as you highlighted to Spoon, that would have had a knock on effect on the other apps that access the music files.

    Leave a comment:


  • vilsen
    replied
    Re: Non alphanumeric character handling

    Originally posted by Spoon
    It looks like dbpoweramp is not even writing = to the tags of vorbis comments
    It does, I just did a hex check of a flac file tagged by music converter.

    Leave a comment:


  • vilsen
    replied
    Re: Non alphanumeric character handling

    Yes, and it's been said above. But then you'd have to tag specifically for Asset which wouldn't conform with your other applications.

    My point was a workaround that leaves the ALBUM tag intact.

    Leave a comment:


  • Spoon
    replied
    Re: Non alphanumeric character handling

    If you tag the album as == then only 1 = will appear to Asset.

    Leave a comment:


  • vilsen
    replied
    Re: Non alphanumeric character handling

    If this doesn't resolve for a while, you could try another workaround without touching the ALBUM tag.

    In Asset's Rename List, add the line
    Code:
    album:=(Unknown Album):==
    Then restart & refresh all.*

    This will replace "(Unknown Album)" with "=". If you would have other unknown albums they will be renamed too of course, so be careful.

    This works in Windows at least.


    * Since the tags (and file dates) are untouched you need to use "refresh all". With a big library, you could instead edit a tag of the specific album (or just update the file dates) and then use "detecting changes".
    Last edited by vilsen; May 24, 2022, 01:31 PM.

    Leave a comment:


  • barkeyo
    replied
    Re: Non alphanumeric character handling

    Hi Spoon,

    Thanks, you answered my question seconds before I asked it...

    Much appreciated.

    Leave a comment:


  • barkeyo
    replied
    Re: Non alphanumeric character handling

    Hi simbun,

    Thanks, so that would seem to confirm that Asset's ID3 tag handling for mp3 files is fine, but it's handling of Vorbis Comment tags for flac files isn't, at least in this specific scenario.

    In which case, is there a specific way of raising this as a bug to the development team, or is simply posting in the forum sufficient?

    Leave a comment:

Working...