Issues with M4A files when editing metadata - Resolved! Install 5.2.10

RobG's Avatar

RobG

07 Jun, 2020 12:05 PM

Issue found in latest release 5.2.9 on following system... (AND reproduced in 5.2.7)

OS X 10.13.6 (17G13035)
MacBook Pro (Retina, 15-inch, Late 2013)
2.6 GHz Intel Core i7
16 GB 1600 MHz DDR3
NVIDIA GeForce GT 750M 2048 MB / Intel Iris Pro 1536 MB (Auto Graphics Switching = OFF)
Flash Storage 702GB available
Java (build 1.8.0_251-b08)

Hi Hendrick,

I'm testing with file types AIFF, FLAC, M4A, MP3, OGG and WAV. The following issue is only reproducible with M4A.


User plays M4A file. At any point whilst track is playing, user 'Loves' or 'Dislikes' by either

  • Click the hollow Heart icon in the track's row in the library

  • Navigate through menu Edit - Loved or Edit - Dislike

  • Use keyboard shortcuts Shift+Cmd+L or Shift+Cmd+D

Expected behaviour: Love or Dislike attribute applied to track without impact to currently playing file

Actual behaviour when clicking Heart icon: Audio drops out after 2-4 seconds. The speaker icon in Library still shows sound emitting state, as if track is playing. On the player, Play/Pause button shows Pause (ie as if still playing), but time elapsed ceases to increment and time remaining ceases to decrement. (ie track has stopped whilst icons show it is playing - Let's call this a frozen track)

Actual behaviour using Edit menu: Same as above.

Actual behaviour when using keyboard shortcuts: Same as above, but not always working. Sometimes the track freezes, sometimes not. However, the keyboard shortcuts will neither apply the heart nor strike-through-heart icons.

When user plays a love/dislike'd track, changing the love/dislike attribute will trigger the same frozen behaviour.

If user pauses the frozen track, the speaker icon in library list changes to a silent speaker and the player's Play/Pause button shows Play. Unpausing frozen track results in 1 second of audio before freezing again.

  1. 1 Posted by RobG on 07 Jun, 2020 12:22 PM

    RobG's Avatar

    Logs... though I wish I'd captured these sooner. I've now renamed beaTunes5.app and the folders in the Library and Cache and installing 5.2.7 to see if I can reproduce in the earlier version

  2. 2 Posted by RobG on 07 Jun, 2020 12:52 PM

    RobG's Avatar

    Issue reproduced in 5.2.7. Thread title and o/p updated

    Hopefully closing beaTunes with a frozen track is reflected in logs

  3. Support Staff 3 Posted by hendrik on 07 Jun, 2020 02:11 PM

    hendrik's Avatar

    Thanks for the report.

    Didn't have the time yet, to look at the logs, but just wanted to say one thing:

    Because 5.2.9 introduced an internal database schema change, you cannot simply downgrade from 5.2.9 to a previous version. The database is slightly different, i.e., you will probably see issues with matchlists and a warning at startup.

  4. Support Staff 4 Posted by hendrik on 07 Jun, 2020 02:36 PM

    hendrik's Avatar

    Took a brief look at the logs.

    I'm actually a little surprised you see this behavior only for .m4a.

    Did you analyze for ReplayGain? If you did, what happens when you turn track volume normalization on or off? Does the issue remain?

  5. 5 Posted by RobG on 07 Jun, 2020 05:19 PM

    RobG's Avatar

    Because 5.2.9 introduced an internal database schema change, you cannot simply downgrade from 5.2.9 to a previous version. The database is slightly different, i.e., you will probably see issues with matchlists and a warning at startup.

    I didn't downgrade. I'm using a test library of 164 tracks covering each audio filetype, so before reinstalling 5.2.7 old version I renamed the app, the beaTunes folders under
    ~/Library/Application Support and ~/Library/Caches, and trashed my test library.

    ... So the behaviour should've been that of a clean install, right?

    However, the reinstall of 5.2.7 did not prompt me to register, which did puzzle me. So for sanity, I deleted both the renamed 5.2.9 app and folders AND the reinstalled 5.2.7 app and folders, did a clean install of 5.2.7

    The behaviour not only persists, but my UI is looking like this...

  6. 6 Posted by RobG on 07 Jun, 2020 05:25 PM

    RobG's Avatar

    Actually, more correctly it looks like this, as the freeze occurred when I Disliked the track via the Edit menu...

    (Edit: Also, despite closing beaTunes, it lingered, and appeared as an open app when fast-switching between apps. In 'Force Quit Applications' it appeared to be running normally. 'Show All Windows' minimised all other apps and the system message showed "No Available Windows".)

  7. Support Staff 7 Posted by hendrik on 08 Jun, 2020 02:19 PM

    hendrik's Avatar

    Just to make sure I understand correctly:

    The freeze only affects the player, but no other UI elements. Correct?

  8. Support Staff 8 Posted by hendrik on 08 Jun, 2020 02:34 PM

    hendrik's Avatar

    However, the reinstall of 5.2.7 did not prompt me to register, which did puzzle me. So for sanity, I deleted both the renamed 5.2.9 app and folders AND the reinstalled 5.2.7 app and folders, did a clean install of 5.2.7

    Registration is stored in the preferences, not in Application Support. That's why it survives deletion of the database etc.

  9. 9 Posted by RobG on 08 Jun, 2020 02:52 PM

    RobG's Avatar

    The freeze only affects the player, but no other UI elements. Correct?

    Correct. Everything else appears normal. Though when the issue first appeared, I was getting massive lag in mouse actions (ie It seemed like my trackpad stopped working, then the places I'd clicked would catch up... but I don't see that anymore)

  10. Support Staff 10 Posted by hendrik on 09 Jun, 2020 06:17 PM

    hendrik's Avatar

    Thanks.

    I think I have the UI artifact fixed and I have an idea what the issue is with manipulating and playing the same file is and how it can be solved. But to do this right, this requires some more thinking, so there won't be a super-quick fix for this unfortunately.

  11. 11 Posted by RobG on 10 Jun, 2020 01:58 PM

    RobG's Avatar

    Excellent! The important thing is you see it and have an idea. Far better to find the right solution than stick a plaster on it :) Good luck!

  12. Support Staff 12 Posted by hendrik on 10 Jun, 2020 02:31 PM

    hendrik's Avatar

    Any chance you could send me one of the (clean) files the freeze occurs on?
    I have trouble reproducing the issue.

  13. 13 Posted by RobG on 10 Jun, 2020 03:29 PM

    RobG's Avatar

    Here are files that are definitely freezing...

  14. 14 Posted by RobG on 10 Jun, 2020 03:33 PM

    RobG's Avatar

    Here are back-up copies of the same files that have not yet been added to beaTunes...

  15. 15 Posted by RobG on 10 Jun, 2020 03:37 PM

    RobG's Avatar

    Also, I'm happy to install Team Viewer or similar, if you need to take a look at my system at any point

  16. Support Staff 16 Posted by hendrik on 12 Jun, 2020 07:42 AM

    hendrik's Avatar

    Thank you for the files. Much appreciated.

    I will try to reproduce the issue today!

    Re TeamViewer: Thanks for the offer, but at this moment that does not seem to be necessary.

  17. Support Staff 17 Posted by hendrik on 12 Jun, 2020 07:59 AM

    hendrik's Avatar

    Hm.. Looks like I cannot reproduce it with the current dev snapshot.

    Does the issue also occur?
    Or just when setting Like/Dislike in a certain way?

    Specifically, does the issue occur when you attempt to set like/dislike via the mouse and menu? (Let's ignore shortcuts and the table UI for a second here.)

    Does it perhaps depend on how long the track has already been playing?

  18. Support Staff 18 Posted by hendrik on 12 Jun, 2020 12:45 PM

    hendrik's Avatar

    Hey there,

    If you're interested in trying fixes for the keyboard shortcuts and UI artifacts, please try https://www.beatunes.com/download/beaTunes-5-2-10-SNAPSHOT.dmg

    Cheers,

    -hendrik

  19. 19 Posted by RobG on 13 Jun, 2020 02:53 PM

    RobG's Avatar

    Hi Hendrik, Sorry for not replying sooner. Should I still try the above snapshot?

    Does the issue also occur? Or just when setting Like/Dislike in a certain way?
    Specifically, does the issue occur when you attempt to set like/dislike via the mouse and menu? (Let's ignore shortcuts and the table UI for a second here.)
    Does it perhaps depend on how long the track has already been playing?

    • It didn't matter how long the track had been playing

    • Would always happen when Like/Disliked actioned via menu

    • Happening less often when mouse was used, but still would occur

    Strangely... At the moment I cannot reproduce!

    I had some issues with choppy streaming video a couple of days ago and had to log a call with Apple. Doing an NVRAM reset helped for a while, but ultimately the issue was with having Safari open on both my 'Web' login and my 'Multimedia' login. I wonder if the freezing track issue is similar? (though just impacting M4A is a bit peculiar)

    Oh, I just remembered: I also installed SoundFlower, so a change in my available audio inputs/outputs. beaTunes is and has always been on Default output

    I'm going to switch to 'Multimedia' login and open Ableton, switch back to 'Web' and then see if the bug recurs

    (Edit: In the time it took to write this comment, beaTunes 5.2.9 did crash after I'd been clicking/menu-ing to try and recreate the bug)

  20. 20 Posted by RobG on 13 Jun, 2020 03:17 PM

    RobG's Avatar

    So...

    Switch User... No apps open on switched profile.

    Switch back to this 'Web' user, open beaTunes, play M4A test files

    • Like/Dislike with mouse... GUI bug occurs but NOT audio freeze

    • Like/Dislike with menu... Functions as designed. No bugs

    • Keyboard shortcuts not tested. Out of scope.

    Closed beaTunes.

    Switch User... Open Ableton. Play then stop Ableton

    Switch back to this 'Web' user, open beaTunes, play M4A test files

    • Like/Dislike with mouse... GUI bug DID NOT occur. NOR audio freeze!!!

    • Like/Dislike with menu... Functions as designed. No bugs

    • Keyboard shortcuts not tested. Out of scope.

    So basically, I can't reproduce the bugs at the moment. Maybe the NVRAM reset fixed it?

    Please confirm if you want me to test the above Snapshot, or if you have a more recent one.

  21. Support Staff 21 Posted by hendrik on 14 Jun, 2020 07:35 AM

    hendrik's Avatar

    Sorry for not replying sooner. Should I still try the above snapshot?

    No worries. The snapshot is still current and should fix the keyboard shortcut issues and the visual artifact. I'd appreciate a confirmation for both fixes.

    So basically, I can't reproduce the bugs at the moment. Maybe the NVRAM reset fixed it?

    No idea. I had assumed that the player part of beaTunes was irritated by changing the file at the same time as it was played. That would have nothing to do with NVRAM.

  22. 22 Posted by RobG on 14 Jun, 2020 09:06 AM

    RobG's Avatar

    No idea. I had assumed that the player part of beaTunes was irritated by changing the file at the same time as it was played. That would have nothing to do with NVRAM.

    This was true of m4a only... until yesterday. The joys of testing on a live system! LOL.

    So asides from the GUI bug in 5.2.9 around Love/Dislike/Instrumentation icons (such as the Dislike on Test File 0057 disappearing when I click Love on TF 0058), things are looking good.

    I can do some snapshot testing today, either on the one above, or a more recent version, if you have one

  23. Support Staff 23 Posted by hendrik on 14 Jun, 2020 09:20 AM

    hendrik's Avatar

    I can do some snapshot testing today, either on the one above, or a more recent version, if you have one

    That would be great! The URL above points to the latest version.

    Thank you!

  24. 24 Posted by RobG on 14 Jun, 2020 04:06 PM

    RobG's Avatar

    I'm able to recreate the freezing track bug :( Duration of play does not impact the occurrence (am testing both at <10s and >1min, different files for each test). The bug continues to only occur on m4a files.

    Could I ask, with the test files I sent you...

    • have you analysed and inspected then in the app and then tested? or

    • added the files to the library and tested without analysis, etc?

    Once I've finished this bit of testing, I'm going process the files in Mixed In Key and then play them again in beaTunes. Earlier, when I could not recreate the bug in 5.2.9, my files were ones that I'd completed full workflow on, so had been analysed and updated by MiK.

  25. 25 Posted by RobG on 14 Jun, 2020 05:33 PM

    RobG's Avatar

    This is the completed test from the files only processed in beaTunes...

  26. 26 Posted by RobG on 14 Jun, 2020 07:17 PM

    RobG's Avatar

    Some good news and bad news...
    Good news, I've identified at what stage in my workflow the freezing file issue occurs.
    Bad news, is its after beaTunes analysis.

    I attach latest logs and an Excel workbook with the User Defined Text Info fields for all 6 test files, as copied from Yate, to follow in separate comments due to Tender file size limits.

    Excel - https://1drv.ms/x/s!Aqo0_fw4PhxP0geMJx6BD8bi_7NA?e=l4gUeL

    Note that the attached files are from the file sets for each stage in the process as titled by the .zip files. They may or may not have been files I've actually used in tests, but they are all copies of the original files that I've been using throughout and they have all been played in beaTunes at some point. I felt sending the same files makes for easier comparison.

    Hope this will help you pin down the issue!

  27. 27 Posted by RobG on 14 Jun, 2020 07:19 PM

    RobG's Avatar

    Test files - Not yet analysed files

  28. 28 Posted by RobG on 14 Jun, 2020 07:23 PM

    RobG's Avatar

    Test files - Only analysed in beaTunes 5.2.10-Snapshot

  29. 29 Posted by RobG on 14 Jun, 2020 07:28 PM

    RobG's Avatar

    Last set of test files - Analysed in beaTunes 5.2.10-Snapshot where freezing was seen, then analysed in Mixed In Key 8.5, freezing no longer occurs

  30. Support Staff 30 Posted by hendrik on 14 Jun, 2020 07:34 PM

    hendrik's Avatar

    Hey Rob,

    thanks for your effort!

    Without having looked at your files yet, what analysis settings do you use in beaTunes? Could you please send a screenshot of your analysis options settings (the dialog that appears when you click on “analyze”)? Hopefully that will make reproducing the issue easier for me.

    Cheers,

    -hendrik

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac