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: 1 2
16
MusicBee Wishlist / Re: Vertical A-Z jumpbar on right-hand side?
« on: July 05, 2021, 08:33:31 PM »
I don't know if this was a feature when this post was made, but you can already do this in the View > Arrange Panels settings. Click the three dots for which ever part of your MB layout has  the Jumpbar in the Navigator

17
MusicBee Wishlist / Re: Device templates
« on: July 05, 2021, 08:27:20 PM »
I'm curious how many people a feature like this would affect. On the one hand, you're talking about something only a few people have a problem with. On other other hand,  I'd feel like the kind of people with this problem are the kind of people that use MusicBee.

18
MusicBee Wishlist / Re: Colored Waveform
« on: July 05, 2021, 08:25:12 PM »
Not an important feature for me, but it would be neat to see. It would add a splash of color to the otherwise monochromatic/bichromatic and it can help differentiate between spots that have mild variations in frequency.

19
When does this happen? I have tracks with URLs in album and/or comments and I've never had this problem.

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

21
Bug Reports / Re: Invisible Album Art can't be removed and causes error
« on: August 01, 2020, 10:03:46 PM »
Man I'm sorry but this is just too much for me (maybe not others) to follow at this point.  The only thing I can add is if you tried, after being sure all auto-tagging was OFF, hitting Tools->Advanced->Reset Artwork cache.  Also be sure that the priorities in the Album Artwork Retrieval Filter are set the way you actually want them, and that you then hit the Rescan Artwork button there.  FWIW, the only external tagger I've seen that would have allowed you to delete/edit ONLY the RIFF INFO tags and leave the ID3v2.3 one alone is Kid3.  But if you deleted "all tags" in Mp3tag, that should have been a good starting point also.  "Me mind's a blank" too at this point.  Wav's were never the friendliest file type for tags anyhow, you may want to consider converting them to FLAC files instead which would make things a lot easier.

Good point. Not much of my collection are wav files. This specific album is a mix a both. I don't know why exactly, but I guess it is because whomever ripped it didn't know what they were doing, or got the files from multiple sources. Converting them will probably fix the problem as a by product, but it is still weird how MB is handling them.

22
Bug Reports / Re: Invisible Album Art can't be removed and causes error
« on: August 01, 2020, 07:31:54 PM »
I already have 3.3.7491, or do you mean the beta from Psycoadept's signature.

The album is actually a mix of .wav and .mp3 files, and the invisible image appears on those as well. But I can look into editing the tags externally, that is probably the problem.

This wav file has both an ID3v2.3 tag (with an album art frame ) and a RIFF INFO tag.  My guess is MusicBee is being confused by this.  If you delete the RIFF tag with an external tagger like Kid3 or Mp3tag and then rescan the file, does that stop the problem?  I don't know if MusicBee even supports RIFF.

Some interesting developments:
I made a copy of the .wav
I put the .wav in MP3tag and removed all the tag, thus removing RIFF data
Loaded the .wav in Musicbee and of course, MB seeing no tags, had no info for the file
I added the cover image ONLY in Musicbee and it added the invisible image again on top of the original image.
I deleted all tags/artwork in MP3 images again, and then only added artwork in MP3tag, the invisible image + 2nd full image appeared again.

Somehow in my tag editing of this copy, it generated a title and artist tag, probably from some auto-tag feature.

Lots of messing around later, cleared all tags in musicbee and Mp3tag, turned off auto-tagging, added artwork to file and THEN musicbee DOESN'T see the added artwork.

Just to confirm, I did go into the image in an independent image viewer and verified the image itself doesn't have a big empty spot above it.

My layman's conclusion: Something with the way MB saves data in my personal library is where its getting/adding information from....maybe....that wouldn't explain why the blank image  appeared when only adding one image.

I went into MediaMonkey as well. It doesn't recognize image files in .wav files, but does in MP3. Both my copy of the wav file with and without the artwork look the same in MediaMonkey.

Anyways, I've done everything I can to fix it. It's not a big enough issue for me to be mad about, just mildly annoying. If you have any suggestions, let me know.

23
The location that MB is retrieving the image from can be found by clicking the Save To button in the Artwork tab of the tag editor.
I expect its a corrupted image. If you send me a link to the file i will have a look and if its embedded in the music file then send the music file

That is where it gets weird, because the Tag editor only shows one file.

https://imgur.com/a/EgOQ6i1

There's no other file for it to reference. I do wonder if it has something to do with the local library and not the files themselves

Here's one of the affected tracks
https://www.dropbox.com/s/sz53q0y1rmi1btk/2%20-%20Grimoire%20of%20Souls.wav?dl=0

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

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

https://imgur.com/qCTRkck

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)

25
Bug Reports / Re: MusicBee crashing intermittently
« on: February 17, 2020, 04:45:46 AM »
If you're meaning porn, than not really. I don't use this PC for that. As for the amount of the security, one is basically active anti-virus, the second is active firewall, and the third is an inactive, user-initiated malware scanner. That sounds like standard "decent" security to me.

A recovery wouldn't completely hurt I suppose,  but I'm not quite ready to deal with that and all the reinstalls.

26
Bug Reports / Re: MusicBee crashing intermittently
« on: February 14, 2020, 11:27:38 PM »
Still crashing. It lasts longer (I think) but it still crashes. I don't see an option to "whitelist" Musicbee in Avira Internet security, but I have it whitelisted in my Firewall and anti malware.

I'm not convinced Musicbee itself is the problem, but I don't know about programming/OS'es to say otherwise.

27
Bug Reports / Re: MusicBee crashing intermittently
« on: February 14, 2020, 03:05:20 AM »
Will give it a shot. I'm curious what the other user uses for his OS and security. Might help us narrow things down.

28
Bug Reports / Re: MusicBee crashing intermittently
« on: February 13, 2020, 12:22:55 PM »
I have Windows 7. Not 10.

I don't know about the Silence Remover DSP. I don't see anything like that enabled in my Plugins or Player and Equalizer settings, so I assume I don't have that enabled in the first place.

I have turned off the musicbee v2 Plugin which supports LCD screens on Logitech Keyboards for Troubleshooting. I noticed the LCD wasn't updating anymore before hand. I'll respond with my results.

EDIT: I've left Musicbee up for maybe an hour at this point with the v2 plugin disabled and that seemed to have resolved the problem. I'm not really keeping track of time, so I don't know for sure, but it certainly FEELs like it has be left open longer than the other crashes.

Update: It crashed again. The plug in disabling did not resolve the issue.

29
Bug Reports / Re: MusicBee crashing intermittently
« on: February 13, 2020, 08:31:57 AM »
I'm having the same problem. I've used MB for years without this problem. As of Feb 12, Musicbee seems to crash regularly after about an half hour to an hour of use. Maybe less, but many times by leaving it in the background while doing something else, it has crashed. Crashed after I left it up after doing a Library scan and crash while I was in the middle of editing some tracks (I had MusicBee open at least 10-20 minutes prior. The only recurring variable I can tell so far is the amount of time MB is left up after being open.

I'm using Windows 7 Home Premium
I use Avira Home Security, Comodo Firewall, Malwarebytes 4.0.4, and SuperAntiSpyware.
I'm using the Blue > Midnight Skin

My Musicbee version is 3.3.7165 and my install hasn't changed much since I installed so I DOUBT any changes to MB is the culprit. I don't think MB is at fault here, its probably SOMETHING with the OS or some other conflicting software but I don't know what else.

Some other software I run often are Steam, Chrome, Corsar iCue, Windows Explorer, and Bionix Wallpaper Changer (but again, these have never been problems before)

Pages: 1 2