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.

Messages - Capt_Blakhelm

Pages: 12
As I said in my original post, MMM7 is long superseded by modern versions - its like at 24 or higher and is completely different

And yes, I'm aware of the cheapness/bundlabilty of Magix software.

And I said I wasn't expecting a fix, or really needing or wanting one. Just putting the bug out there in the chance it is fixable.

I thought my lengthy post would have made that clear.

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.

Visualizers / Re: Milkdrop Visualiser Support
« on: July 25, 2021, 09:49:16 PM »
EDIT: MY MISTAKE! The plug in actually works fine for me. There was a Spotify Plug in that caused the below error. It was just weird because I had this issue after installing Milkdrop plugin. Funny thing is, the Spotify Plugin didn't seem to quite work before, but It didn't cause an error before I used Milkdrop

I originally had a problem using the arrow keys in Milkdrop. At first, I couldn't use the arrow keys to select Custom Presets from the "L" menu. Now I can't reproduce the issue, odd. That is a good thing, but basically, the arrow keys don't select different presets. THANKFULLY, I found a work around. Click the Visualizer screen/F1 Menu, Press L for the  Load Preset Menu, then use CTRL + Arrows  Up/Down to select different presets.

YIKES! I'm going  to have to uninstall this one. The instant I play a track, MB crashes with the below error. Funnilty enough, I can "ignore" the error and let MB play and the Visualizer run, but I can no longer interact with MB.

MusicBee v3.4.7855.29345D  (Win10.0), 25 Jul 2021 15:44:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.Plugin.<ReceiveNotification>d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_1(Object state)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Plugins / Re: Similar Artists/Tracks
« on: July 25, 2021, 09:22:23 PM »
Sorry to dig up an old topic, but I found a minor issue with this plug-in, Multiple artists

Perhaps my fault since I sometimes a track with multiple artists seperated by a semicolon (;), especially if an artist goes by their real name and stage name, or if multiple people made the song (musician + vocalist, collaborators, etc)

It seems like the plug in searches strictly for whatever string is in the Artist field, so when there are multiple artist on a track, it will search for all of that text as one search query.. It would be handy if you could choose which artist it searched for or at the very least, force it to only include a string before the first Semicolon

Below is a track by BLANKFIELD and Doragon Entertainment. To be honest, the tracks here are technically all made by BLANKFIELD and Doragon Entertainment would maybe fall under a Publisher at best, But I think this tag info was already in the tracks from the official soundtrack. I probably should just remove the second artist in the specific case, but I have many other tracks where I feel extra artists are necessary and this plug-in would fail in finding the right artist.

Take a look at the Advanced Search and Replace function of the Additional Tagging and Reporting Tools plugin.

Just installed it and

BOY. This screen is daunting to say the least, so it's going to take a while for me to investigate it.

However, from the little I've seen of it, and I even tried importing preset, I don't see anything that mentions "Playlists" or the editing of Playlist names. I haven't dug deep enough into it, but it still seems this is dedicated to editing tags with in tracks. - I am looking to edit the Playlist names themselves.

Edit: I see that these presets have an option to apply itself only if it is included in a playlist, but that still is for editing tracks and not the playlist itself, if I'm reading it correctly.

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. :)

MusicBee Wishlist / Re: Jukebox view
« on: July 05, 2021, 10:48:21 PM »
Got it now.

When he said "since it's inception", I thought he meant since the inception of MB itself.

Sorry for the double post, but I made an edit to my last post that was so long that it should probably warrant a new post honestly. (and I think it answers your question).

MusicBee Wishlist / Re: Jukebox view
« on: July 05, 2021, 09:39:32 PM »
So is this Jukebox thing an actual part of MB now, or just part of the skin Steven posted earlier?
It is, and always was (since it's inception) a view. Just like Tracks View, or Album Covers View or Albums and Tracks View.

I don't see it

MB Version 3.3.7491

MusicBee Wishlist / Re: Tabs for Multi-Disc Albums
« on: July 05, 2021, 09:22:18 PM »
So I just learned today  that grouping tag is sometimes used on albums when multiple songs are part of the same "Act" or group of related songs, such as hidden or bonus tracks. Basically like "Chapters" for an album.

Maybe this post answers what you're looking for?

MusicBee Wishlist / Re: how about finally a 64bit version
« on: July 05, 2021, 09:18:35 PM »
I'm programming illiterate, but I suppose a 64 bit version would allow MB to use more RAM maybe(?). But also, I have a 47k+ music library on a 32GB RAM PC and memory or unresponsiveness has never been a problem for me in MB.

Honestly, I love that MB is now one of the "rare" programs now that actually close when I say FREAKING CLOSE. But "Close to Dock to tray" bas become quite the standard in many Windows application, so it wouldn't hurt to have that option.

I'm pretty sure some programs like uTorrent docks to the tray when you click 'Close' by default, but you can change an option to force it to actually close legacy style.

so I guess


MusicBee Wishlist / Re: Jukebox view
« on: July 05, 2021, 09:13:01 PM »
So is this Jukebox thing an actual part of MB now, or just part of the skin Steven posted earlier?

I guess I misunderstood the post using weblinks in MB itself instead of sending that data elsewhere outside of MB

Edit: I've never used the Custom Web Links/Open  in Web Browser feature seriously until now, so now I have a better understanding of what you're asking.

For example, I made a custom web link called OCremix to search the OCRemix site by artist name. Since uses a specific number for each artist, I have to use the search page instead of it directly linking to an artist page like some other sites handle.

That said, in my opinion, if the artists tag contains a URL instead of the actual artist name, then the tag itself should be corrected to the artists name. I've spent hours editing tags in my library because of incorrect/missing artist and such. Search and Replace is very helpful when needing to correct large amounts of mistagged tracks.

Most singles on OCRemix have as the album title. I would never need to search the web for that via MusicBee, however, for shits ands giggles, I made a Custom WebLink for OCremix to just pull up the Album tag and when used on an OCremix Tag, it produced an error. I didn't read the error, but it may have produced those anomalies you had.

Edit 2:  Did some further tinkering. Was able to make links for search Discogs by Artist OR Album with no problem. Had a Problem when I searched on VGMDB and noticed it converts spaces into  "%20" in the url. This is necessary for most web search engines and works just fine for Discogs. I realized I had the Search URL incorrect for VGMDB

I was using

instead of <Artist> &type= OR <Album> &type=

This fixed it and made VGMDB search it properly.

I haven't tried it with a tag that has slashes or colons, but regardless, MusicBee NEEDS to do that in order to prompt the website to use the proper character in a search. And as I opined above, an Artist tag shouldn't be a URL (unless an artist's name is literally an URL).

I think your problem is a tag problem, not a MusicBee Problem

MusicBee Wishlist / Re: Show Hotkeys that Aren't Default
« on: July 05, 2021, 08:42:26 PM »
I always support ideas that make MB more customizable and editable, but such a feature would benefit so few people to invest development time into, unless this is something very easy to program. That said, I am surprised there is  no "Reset to Default" button in the Hotkey options, or in all of MB from my quick search.

There is an ability to Save and Load settings from a .ini file, but I didn't find a "default Settings" .ini file in the MusicBee Program folder (it could be in another folder like AppData or MyDocuments, etc). If there isn't a default settings file included with MB to rollback to, there definitely should be.

The next best thing you can probably do though is save your settings and find some way to roll yours back to default (uninstall/reinstall Musicbee) or you may be able to download the portable version and see what settings are there.

Pages: 12