Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - theta_wave

Pages: 12 3 ... 8
1
In the recent 3.5.x builds, I noticed something happening files in my inbox when moving/verifying music files outside of Musicbee.

Example 1: For downloaded purchases (bandcamp/qobuz/beatport/etc.), inbox files that have been moved by myself from a first monitored folder (downloads) to another second monitor folder (staging) via file explorer leave behind a missing file indicator for the first audio track despite rescanning the folders and acknowledging that files are indeed no longer in the first folder and are to be removed from the library.

Example 2: In other times, when verifying my ripped CD with cuetools, temp wav files created for verification against cddb and accuraterip databases (and deleted after verification) end up as being displayed as missing files as shown in the screenshot below. Again, these files still remain after rescanning the directory and acknowledging that the files are no longer there and are to be removed from the library. This has been my workflow for the past several years using Musicbee and do not recall seeing this issue as shown in the screenshot. Only after updating Musicbee 3.4.x to 3.5.x did I notice this issue. When moving these inbox FLACs from the first monitored folder to the second monitored folder, at least one stray flac entry remains in the inbox. Like in example 1, it requires manual removal from the inbox tab.

In both examples, this issue is not resolved after rescanning the monitored folders and acknowledging removal of these missing files from the inbox.

Expected behavior: Inbox files that are no longer present in monitored folders are removed either automatically (as they were prior to my 3.4.x -> 3.5.x update) and/or removed after the user acknowledges that the files are no longer present and desires to remove them.

Additional comment: Also, I noticed that there's no easy way to remove such indicated files from the inbox. Locate missing files simply does as it says without the option to trash the missing files from Musicbee's db. I was there was an easier way to going about it instead of going to the inbox tab, break up my sorting criteria there, set sorting by "Date Modified" to highlight the missing files having an "N/A" value from the field, and remove these entries once and for all from there. Because I regularly purchase music online and continue to rip what's left of my CD collection, all of these steps get tedious fast when missing inbox files were immediately and automatically resolved in past Musicbee versions.



Best,
theta

2
Bug: Double clicking an album under album view takes me out of album view to an "album and tracks" view showing all of the album's tracks, which can already be viewed in album view when single clicking an album (showing the tracks "directly under the selected album or artist"). I have to perform another click on the back arrow to take me back to the album view. The options under "customise panel" and panel settings are provided below.

Expected: Double clicking an album under album view plays the album (I think this was the old setting, no?) or does nothing per the settings.

Comments: I feel that double-clicking the album under album view that takes the user out of the present view to another view showing only that album is a little jarring and requires an additional click to bring back the previous view. Furthermore, I feel it is a bit redundant if the setting for showing the tracks "directly under the selected album or artist" is already selected as shown in my "customise panel" setting.

Thank you for looking into this issue.




3
Hi,

I've seen quite a few crashes lately, usually after I return to Musicbee after leaving my system idling for a few minutes or so, otherwise sound output is fine. This happens infrequently. There's no crash window and nothing is reported in ErrorLog.dat. Thankfully, Musicbee handles crashes these days far better than before (no more zeroing out of "Subscriptions.dat" for example).

Windows 10 Pro 20H2
Intel iGPU - DisplayPort
Power Settings configured to turn off the monitor after a few minutes or so

Musicbee version: 3.4.7628 (portable) (executable modified by editbin to use >2GB of memory)
Output: WASAPI Exclusive
DAC setup: Schiit Eitr → Schiit Modi Multibit v2

Player setup:


Crash reports from Event Viewer (ErrorLog.dat shows nothing):
Code
Faulting application name: MusicBee.exe, version: 3.4.7628.34032, time stamp: 0x5fb624f5
Faulting module name: basswasapi.dll, version: 2.4.2.0, time stamp: 0x5a0c633d
Exception code: 0xc0000005
Fault offset: 0x0000378c
Faulting process id: 0xe08
Faulting application start time: 0x01d6e3d777009fc5
Faulting application path: I:\0_MusicPlayers\MusicBee\MusicBee.exe
Faulting module path: I:\0_MusicPlayers\MusicBee\basswasapi.dll
Report Id: 55d83c30-7246-472d-8a90-e67112641102
Faulting package full name:
Faulting package-relative application ID:

Code
Application: MusicBee.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at #=zmAXGS76UIDUCBYRKDcpL7Yc=+#=zCPD_bnOlnIsrU2GB7w==.#=zyje73rpCewjgT2lCk3bJcx8=()
   at #=z44ym6VJm9cLtvryrUFy8z_Q=+#=zkImfASTEA8HT.#=zUCatDdM=(Boolean)
   at #=z44ym6VJm9cLtvryrUFy8z_Q=+#=zkImfASTEA8HT.#=zreSG4YM=(Boolean)
   at #=z44ym6VJm9cLtvryrUFy8z_Q=.#=zreSG4YM=()
   at #=zwY0e0t$NMS7eGkN8OgTYMWg=+#=qUrqV9EWuySsJqs83f3cOLQ==._Lambda$__174-0()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
   at System.Threading.Tasks.Task.ExecutionContextCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
   at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
   at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

4
Version: 3.3.7367 P

I know that some old albums of mine include <ARTISTSORT> tags from way back when. Every so often, it gets read into Musicbee's sorting list wreaking havoc on my autoplaylists. I'm trying to hunt them down to get rid of unwanted autoreading of <ARTISTSORT> into Musicbee's sorting list/rules (i.e. deleting <ARTISTSORT> from their tags). Is there a way to query <ARTISTSORT>? Querying <Sort Artist> displays every artist in my collection despite my library only having the two sorting rules: [.que] -> Que; {{{ Sunset }}} -> Sunset. Just one album having <ARTISTSORT> affects the rest of the artist's albums that do not have <ARTISTSORT> in their tags.

5
Questions / [6833] Locations of panel elements changed
« on: September 23, 2018, 05:59:32 AM »
With 6833, the first time I updated in over a month, I noticed that the ratings and fav buttons shifted over to the left of the track playing panel on all DarkRED flat skins, shown in the first image below.  The prior placements is shown in the second picture taken from an older build, 6735, after reverting.




6
For tunes in the Inbox, <Artist> fills in <Album Artist> when <Artist> has a value and <Album Artist> is null.  I was trying to find and correct files with their <Album Artist> fields having null values.  I tried creating an autoplaylist just for that: setting the inbox as the music tracks source and "Album Artist" has no value.  Unfortunately, those with null <Album Artist> didn't show up and I think I found out why in the screenshot below.  For compilations and inbox tracks, the latter usually intended to be edited by the user, I do not find the default behavior too helpful.


7
Wishlist: Have an option to set the max resolution for artwork copied to a device.

Issue: Online music retailers like Apple's iTunes are now including cover art >2000px with their album/song purchases.  The problem is that many musicplayers for phones/DAPs cannot handle such resolutions, so the copied artwork is displayed as an empty space.  

Workaround (not much of one currently): The existing option to resize artwork on-the-fly isn't a solution either because a setting of 1000px (or 700px) would resize small album artwork (CD rips where the only cover art found online is 300px) to much larger resolutions thereby increasing the space taken up by "folder.jpg" on the digital device.  For example, if one has a thousand singles transferred to a device (with other albums with hi-res artwork), wherein each single has individual artwork of 300px, then the larger converted artwork from those singles will unnecessarily balloon the amount of space taken up by album art for no discernible reason.

Conclusion: I believe having a setting to cap the artwork resolution transferred to a device will solve this issue.


8
Having an issue getting the right formula to launch cygwin bash, as an external tool, in the path of the selected file; yes, I'm crazy.  Under the template editor preview, the following formula looks fine.


Command: c:\cygwin64\bin\mintty.exe /bin/sh -lc 'cd "$(cygpath "/cygdrive/i/Shoegaze/A Place To Bury Strangers/(2018.04.13) Pinned/")"; exec bash'


<Path>: I:\Shoegaze\A Place To Bury Strangers\(2018.04.13) Pinned
Application Path: C:\cygwin64\bin\mintty.exc
Parameters: /bin/sh -lc "'"cd "\"""$"(cygpath "\""/cygdrive/$Replace($Replace(<Path>,I:,i),\,/)"\"")"\""; exec bash"'"

Under template editor, the result column under preview shows exactly what I want, but the Window title flashes and then close while displaying "-lc 'cd"; exec bash" in the title bar when trying to launch it from External Tool right click menu.  A successful launch from cmd.exe displays "/cygdrive/i/Shoegaze/A Place To Bury Strangers/(2018.04.13) Pinned/" as the title.  I figure that the characters I'm wanting to escape (successfully per the preview result) is not being handled the same way outside the template editor.

9
Questions / 3.2.x - Removing the playlist infobox (how?)
« on: January 21, 2018, 11:23:53 PM »
Hi,

I tried v3.2.xxxx for the first time yesterday (the 1/20/18 build).  The first thing I noticed was the playlist infobox.  Personally, I have no need for it and tried looking around how to disable it.  Unfortunately, I couldn't find it while browsing the panel arrangement menu (main and top panels), layout (1), or layout (2) options.  Right clicking it in hopes of bringing up a right click menu with the disable option didn't work either.


10
Problem: For my sync settings, I have Musicbee create folders to the destination drive or virtual device based on metadata in the tags (e.g. \Music\<genre>\<artist>\(<year>.<monthdate>) <album>\<track#>. <title>).  I also have the cover saved as "folder.jpg" in the last child directory.  The problem is when the last child directory changes due to changed metadata.  I believe Musicbee normally autodeletes empty directories, however the last child directory is not empty due to "folder.jpg" still being around; in syncing, I believe files with changes are deleted and then copied over from the library to a new child directory on the sync destination rather than moved.  Folder.jpg apparently is not deleted, thus the folder is not empty and thus remains there.  So, one is left with the following:

\Music\Foo\(2018.01.10) Album\
\Music\Foo\(2018.01.10) Album [Deluxe Edition]\

In the above, it could be that the metadata for <Album> changed to include "[Deluxe Edition]" between syncs, or there was a format change corresponding to the changed metadata.  Now, the first directory has folder.jpg and nothing else.  Musicbee will not autodelete the directory due to the presence of folder.jpg.

Solution: Below are bash commands that will list and (list and) remove directories that contain folder.jpg and nothing else.  The first command is to check and make sure that the command will remove the directories that need to be removed.  The second command is self-explanatory.  Just run either of them in the root Music directory/drive.

Code: "List the directories"
shopt -s nullglob dotglob globstar; for d in **/; do files=("$d"*); if (( ${#files[@]} == 1 )) && [[ "${files[0]##*/}" = folder.jpg ]]; then echo "$d"; fi; done

Code: "Removing folder.jpg and the directory"
shopt -s nullglob dotglob globstar; for d in **/; do files=("$d"*); if (( ${#files[@]} == 1 )) && [[ "${files[0]##*/}" = folder.jpg ]]; then rm -vr "$d"; fi; done

Credit goes to the folks at #bash @ Freenode for helping me out on finding the appropriate bash command.

11
Virtualtag shown in the screenshot below <Composer-Album>: $Sort($If($RxReplace(<Album>,"(^.*?)(\:.*$)","$1")=$RxReplace(<Composer>,"(?:^.*\s)(.*$)","$1"),$RxReplace(<Album>,"(?:^.*?\:\s)(.*$)","$1"),<Album>))

Present Workaround: Have 2 virtualtags, one for display (w/o $Sort) and one for sorting (w/ $Sort).  The album featuring Gil Shaham below has "Vivaldi: The Four Seasons (OCO: Shaham)" as its <album>.

Rationale: For classical music in this instance, there are many albums whose <album> tags consist of "Composer (Last Name): Album title" due to the presence of multiple composers on a single album.  In a dedicated composer playlist presenting tracks by said composer only, I (or rather my OCD ;)) found the composer name prefixing the album title to be redundant, thus unnecessary.  The present workaround is fine, but it uses up two virtualtags instead of one if $SSort() was an option.



12
Bug Reports / [FIXED] [6480] File Organiser exceptions went a little haywire
« on: September 29, 2017, 05:52:13 PM »
Hey Steven,

I updated just now and noticed how a number of File Organiser exceptions for my existing preset have changed to the opposite rule.  The first two exceptions are okay (directed to <Album Artist> (is) and <Genre> (is [twice / match all]).  The rest underneath the first two changed (listed in order): <Album> (contains > does not contain); <Artist> (contains > does not contain); CustomTag1 (is > is not any of); CustomTag1 (is > is not any of); and CustomTag1 (contains > does not contain).  I last used the File Organiser yesterday (prior update) with no issues.

I changed them back easily, but I'm worried for others that might have auto-organize turned on or might blindly click "OK" after having long set their file organization rules.

13
Bug Reports / [6477] Typo in the hotkeys configuration menu
« on: September 27, 2017, 05:48:28 AM »
Just a minor bug under the Action column:

Tools: Auto-Tag by Track - Update Misssing Album Pictures

14
For those with large libraries containing a sizeable amount of metadata, MusicBee tends to use a lot of memory.  The problem is that once it reaches a threshold (.NET threshold for 32bit programs is 1.3 GB), System.OutOfMemoryException error messages will pop up and sometimes cause MusicBee to crash.  There is a way to bump up this threshold up to 4 GB by one of two ways: 1a) Run editbin.exe included in a package by Steven or 1b) run editbin.exe included in Microsoft Visual Studio (Community Edition).

Which way is easier?  "1a" should do the trick in one step, but if you are OCD and absolutely need to know whether editbin.exe worked, then "1b" is the way to go.  Besides, if editbin.exe doesn't work, then you won't see MusicBee run significantly above 1.3GB in task manager before crashing.

1a) Editbin.exe from Steven's package

i) Download link: https://www.mediafire.com/file/9h6dxa3wcg84tdh/EditBin.zip/file

ii) Extract all three files from it and copy it to MusicBee's program directory (usually, C:\Program Files (x86)\MusicBee\)

iii) Run the following command (Go to MusicBee's program directory in explorer and type "cmd.exe" (without quotes) in the address window and hit enter):

Code
editbin /LARGEADDRESSAWARE MusicBee.exe

1b) Editbin.exe from Visual Studio

i) Download Microsoft's Visual Studio IDE (Community Edition) installer: https://www.visualstudio.com/

ii) Run the installer

iii) Click the "Individual components" tab and select "C++/CLI support" and "VC++ 2017 v141 toolset (x86,x64)" and finish the install

iv) Open up notepad and create a batch file with the content below.  Save it as "Filename_of_your_choice.bat" anywhere in your computer.

Code
@echo off
ECHO -------------------------------------------------------
echo Musicbee (LargeAddressAware)
Echo.
Echo Choose what do you want to do...
Echo 1. Enable /largeaddress aware flag
Echo 2. Check the status of MusicBee.exe
Echo.
ECHO -------------------------------------------------------

CHOICE /C 12 /M "Select one:"

:: Note - list ERRORLEVELS in decreasing order
IF ERRORLEVEL 2 GOTO CHECK
IF ERRORLEVEL 1 GOTO ENABLE

:CHECK
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\HostX64\x64\dumpbin.exe" /HEADERS "C:\Program Files (x86)\MusicBee\MusicBee.exe" | more

:ENABLE
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\HostX64\x64\editbin.exe" /LARGEADDRESSAWARE "C:\Program Files (x86)\MusicBee\MusicBee.exe"
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\HostX64\x64\dumpbin.exe" /HEADERS "C:\Program Files (x86)\MusicBee\MusicBee.exe" | more

v) Double click the bat file you just created.

Checking whether it worked, those who followed 1a earlier proceed to 1a below; likewise those who followed 1b above proceed to 1b below.

1a) Dumpbin.exe from Visual Studio

i) Install Microsoft Visual Studio according to 1b)-i) through iii)

ii) Hit Windows Button+R, type cmd.exe and press enter

iii) Copy and paste the following in the command line:

Code
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\HostX64\x64\dumpbin.exe" /HEADERS "C:\Program Files (x86)\MusicBee\MusicBee.exe" | more

iv) Hit enter

v) The result should match the highlighted message from the picture below: "Application can handle large (>2GB) addresses."

1b) From the .bat file made earlier

The bat file you made should produce a screen similar to the one below.  Pay attention to the highlighted portion: "Application can handle large (>2GB) addresses."


15
During the last few patches, I've been experiencing more and more "out of memory errors".  Either the one below that closes the program, or, more commonly after leaving Musicbee open for some time, the details tab in the right panel goes completely blank necessitating a restart.  With 16GB of memory, I have quite a few programs open at any time, but I still have more than 4.5GB of memory free.  With my large library (and its metadata), is Musicbee hitting the 32bit process address space limit?

Code
MusicBee v3.1.6431.37338 (Win6.1), 15 Aug 2017 20:41:

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.Threading.Thread.StartInternal(IPrincipal principal, StackCrawlMark& stackMark)
   at System.Threading.Thread.Start(StackCrawlMark& stackMark)
   at System.Threading.Thread.Start()
   at #=qT0m4wGFjnNcF8s$JbqVlFahzOlWu0d5Q89OpIYoDZtdEv2fq5IgbtCJu5FtK01aE.#=qFc$bFdY0DA5fm9lc_mHH$c2U1qthubzVLzNVfSobSB8=()
   at #=qT0m4wGFjnNcF8s$JbqVlFahzOlWu0d5Q89OpIYoDZtdEv2fq5IgbtCJu5FtK01aE.#=q3GklzxFwZLF$O$AaQbrEEA==(Object #=qSoI1$x9LCxOVZ6RQr0PCaQ==)
   at System.Threading.TimerQueueTimer.CallCallbackInContext(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.TimerQueue.FireNextTimers()
   at System.Threading.TimerQueue.AppDomainTimerCallback()

Pages: 12 3 ... 8