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 - Capt_Blakhelm

Pages: 1
So I came across a bug that practically nobody using this program will run into.. I can explain the "WHY?!" later if you're curious, but started running Magix Music Maker 7 and MusicBee 3.4.7855 simultaneously. This can cause problems, such as

-MMM7  not being able to start
-being able to run multiple processes of it while the program actually never appears on screen
-MMM7 not closing due to MB being open
-MB locking up with a right click when a process for MMM7 is  running
-Menu in system tray for MB locking up when MMM7 is running

This problem is fixed by...well not having MMM7 in the first place, or closing any processes of it still running in the background even if you have closed it.

Considering this is such an obscure problem, I severely doubt this is something you're in any rush to fix, but I did want to bring it up IN CASE it causes conflicts with any other Digital Audio Workstations (DAW). I have a couple others and I haven't tried it yet.

Even if you wanted to fix it, I am not sure it is fixable. 1) MM7 is in the ballpark of 15-20 years old and was designed for the Windows 98/Me/XP era and getting a copy is next to impossible (I only got once from a rare listing on Ebay). It's obviously no longer supported and is superseded by more modern versions of MMM, or Acid, or Samplitude 2) People have mentioned problems with the way Magix music/audio editing software causing audio driver screwups and this is more than likely a Magix problem than an MB problem specifically 3) This is possibly problem with any major DAW since how they interact with sound drivers/sound cards - heck my problem might Specifically be due having a dedicated sound card instead of relying on onboard audio.

I'm not expecting a fix for this, but if it is something that could be easily be fixed, that would be cool and might solve other issues (or cause them XD).

WHY am I running these two programs together?
I made a song in MMM6 years ago, but lost the disc. I bought MMM7 from an ebay seller and tried to recreate that song for nostalgia. I wanted to compare my original song with MMM 7 so I can find out how I made the sounds I made back then. It would be my luck that they caused problems for each other, but at least I figured it out.

The Capitalize and Search and Replace functions are very handy for cleaning up grammar and punctuation problems of tracks downloaded from the Internet.

Playlists have the same problem when for example, many game playlist files in torrents start with a "00" or "000" for no obvious reason. It's pointless to have dozens of playlists starting with the same number.

Anyways, it would be very handy if I could use those same tools somehow on the playlist names themselves, simply because I have so many and the vast majority of them have "issue" like this i'd rather not going and manually edit on each one.

Not an important feature for me, but it would be very convenient. :)

I have a huge collection of tracks from a bundle with its track numbers missing in tag data, but listed in the file name. The current Auto-Tag tool to grab data from the file name almost works.....but the files are named in a format of  <Track #> - <Artist> - <Track Name>.

For example

1-Dark Fantasy Studio- Departure

So by using this tool, every track number tag will be the entire filename, minus the .mp3 part of it.

It would be nice if you could limit the amount of  characters this tool pulls info from, so that way, I could limit it to a maximum of 2 characters and it would only pull the track number 1-41.

So i'd have to manually rename  all the tracks to just their track numbers, or use the tool as is then remove the remaining characters from the track tag. I might as well do it manually one at a time then.

Hopefully this would be something easy to implement. MusicBee remains to me the best music library manager, but every once in a while it has me saying, "I wish I could do X".

Thanks for MB. :)

Bug Reports / Invisible Album Art can't be removed and causes error
« on: July 30, 2020, 07:52:43 AM »

I found a strange issue where a specific album my music displays an invisible object taking up space before the album art in the Track Information panel.

The album in question is the Castlevania: Grimoire of Souls Soundtrack. I doubt the album itself it the problem (IT'S CURSED!, lol) but so far, it is the only selection of tracks exhibiting this problem.

I was customizing my panels in the preferences and found that there is a large gap under the track info and before the actual image I want to use as the album art. It LOOKS like Musicbee is somehow finding/generating another image as an album cover and trying to display it. Hovering my mouse over this "gap" says it is an image, but I don't have any other image files in the folder but one cover.jpg to cause this. I've compared this file to other music files in my library and they don't have this issue despite having the same settings under the "Artwork" tab in the Edit Panel

I can remove the artwork and it goes back to only displaying one square saying "No Album Art" but the moment I reassign art to it, it acts as if there are two images to be displayed again.

This error doesn't affect playback or usability of Musicbee at all. In fact, when I get a pop-up of a new track playing in taskbar, the correct cover appears just fine. It's just a strange, nagging annoyance when viewing the track in fullscreen MusicBee.

As part of my troubleshooting on a previous version of MB, I changed the name of cover.jpg, which caused MB not to be able to find artwork. Unchecking the "Primary picture" checkbox under the image caused the error below. I updated my MB to 3.3.7491, but I still have the invisible image bug

MusicBee v3.3.7165.34284 (Win10.0), 30 Jul 2020 0:43:

System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at #=zQK2gn$ayPzjVqwLPj$rhNW0=.#=ztpRhkPyKKydqsfsMug==(Object #=zySAfqQw=, EventArgs #=z2hFhQMw=)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at #=zM2VGjI5pgr6zMo8nS7cXJSmVMU7U.OnClick(EventArgs #=z2hFhQMw=)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Pages: 1