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

Pages: 1 2 3 4
46
Bug Reports / At times Context menu fails to list plugins.
« on: November 29, 2017, 10:32:18 AM »
Sorry to burden you with a potential bug Steve. I’ve already raised this as a question on the forum, but nobody has come forward with any suggestions – see: https://getmusicbee.com/forum/index.php?topic=23367.0.  

In short, if MB is configured so as to use the 'album covers', 'artists' or a 'custom’ view, plugins are only listed in the context menu once, immediately after start-up.  Subsequent right clicking an album or track displays the context menu without any plugins that are intended to be listed on it.  I’ve established that this issue is dependent on the view that's being used - it doesn’t occur if the view is 'Tracks' or 'Album and Tracks'.

47
Same issue here.

Been searching the reason of this behaviour for the last 2 days.

Started to use GMT Manager to tag genre on my 1800 albums and I have to restart Musicbee after each album its not really efficient

Thanks for coming back to me Paulca. I've just worked out that this issue is dependent on the view that's being used.  It occurs if your using 'album covers', 'artists' or a 'custom view'; but doesn't if the view is 'Tracks' or 'Album and Tracks'.  So good news of sorts 8) .  On a side note, it would be good to hear how you get on with the GMT manager plugin.  I’ve got a similar sized collection and I’m really interested in the possibility of this featuring multiple genres...

48
Beyond MusicBee / Re: Recommendations for HD Media Player?
« on: November 22, 2017, 06:11:04 PM »
Alternatively, get an Amazon Fire Tv box and install an app like Vimu Media Player or Kodi on it

49
Hi I hope someone can help.  If, when MB starts, I immediately right click an album or track, two of the plugins I've installed are listed at the bottom of the context menu that's displayed:

 

However, if I then select another album or track and right click again, these plugins aren't displayed:


 
I've no idea why this should happen.  I've noticed that if I select something other than 'music' from the navigator panel, then select 'music' again, the plugins are displayed once again on the context menu, but this isn't ideal.  Is there anything I can do to resolve this?

50
Skins / Re: Eleven
« on: November 17, 2017, 01:20:32 PM »
Brilliant skin - I really like it, big thanks Assumeddiz 8).  Please though, is there any chance you could do a light version of the skin?

51
I hope someone can shine some light on this.  

I recently tweaked the layout of my install of MB which included moving the visualiser graphic element around and switching it on and off.  I really want this element to feature in the right-side bar and I haven’t got any issues in terms of configuring MB’s layout.  However, for some reason now, when the visualiser graphic element features the playback of music is speeded up, and when it is removed playback is fine, it occurs at the correct speed.

Can anybody provide any guidance on what I could do?  

I’ve tried changing skins – trying both Musicbee3 and Eleven - but that didn’t resolve the issue.  And previously I had mistakenly concluded that the issue was a wasapi bug, but subsequently managed to get everything working again by doing a complete reinstall of MB –  that’s an extreme measure though and if at all possible I would prefer not to repeat that.

52
Many thanks for coming back to me Steven and CritterMan.  Yep, I should have posted this in troubleshotting rather than as a 'bug' :(.  As it transpires, I've been able to resolve this issue by completing uninstalling the player, rebooting the PC then reinstalling it again.  So apologises, false alarm on my part - there's no bug relating to this issue.  Having said that I'm really pleased that wasapi output now works for me as it should! 8)

53
If I select wasapi as the output for the player, the sound I get is badly distorted, with what seems to be a mix of interference and tracks being played too fast.  Adjusting the buffer size and having 'event mode' switched on or off doesn't make any difference - this issue contunes to occur.  

This issue appears to relate only to how musicbee is handling wasapi. Playback using musicbee's DirectSound setting is fine, and whilst the PC is running the latest version of Windows 10 there's no noticable distortion at all when using wasapi with audio players, including Winyl, which like musicbee also uses basswasapi.dll.  I'm like crazy about Musicbee 8) so I'm really hoping this issue can be resolved.  

I'm incidentally using musicbee version 3.1.6493 and trying to get this to play, via wasapi and S/PDif, to a SMSL Q5 Pro.  (This doesn't use any third party driver - Windows has instead configued it with a generic MS driver and sees it as a high audio definition device)

54
Questions / Re: Casting MusicBee from PC to Chromecast - UPDATE
« on: July 20, 2017, 10:10:28 AM »
Have you tried using BubbleUPnP Server (https://www.bubblesoftapps.com/bubbleupnpserver )? This software enhances UPnP/DLNA services and can apparently enable a Chromecast device to function as a UPnP/DLNA renderer.  I personally haven't got a Chromecast but I suspect that it will be easy to configure BubbleUPnP Server to support Chromecast, and once done your Chromecast should be listed as an output source in MBs UPnP plugin.

55
Plugins / Re: Genres, Moods and Themes Manager (V1.1.0)
« on: June 14, 2017, 06:05:30 PM »
I don't know why but for some reason the plugin doesn't seem to be working. I've copied the file to the plugin directory, but when I run MB it isn't listed in preferences, and the GMT Manager and the BOT importer are not been displayed. I incidentally have been trying v1.1 of the plugin with version 3 of MB (3.0.6347). Can anybody help? 

56
'auto-applying' preset means that it will be applied if any track tag is changed (what is probably useless in your case) or if track is added to library (what is probably useful). also if you are satisfied by testing on several tracks, you can just select all tracks and apply preset to them. nothing will changed (or even saved to file) for tracks with correct padding.

This is good to know, thanks

57
It's said that a picture is worth a thousand words.

Assuming you have installed the plugin, highlight a couple of tracks that have show leading zero(s) and click Tools > Additional Tagging Tools > Advanced search and replace...


Now that the ASR window is open, start typing "remove" in the upper window. That will filter out all the presents that DO NOT show the word "remove." Scroll down the list until you see "Remove leading zeros..." and you'll see two presents. To be honest, I don't know what the difference is between them - I always use the second one. Click on it (BUT NOT ON THE CHECKBOX) and it becomes selected. At this point you may have to use the drop-down to add "Track#" to <Tag 1>. Now click on "Preview" and the tracks you selected will appear along with a column showing the track number as is, and a column showing the result of the proposed tag change...


At this point click "Apply" and the tags will be changed...


I want to stress that you should test this a few times on a very small number of tracks to make sure it's behaving as you expect. Once you're satisfied, go back to the present and check the box to the left of the one you want to you want to have automatically applied. You could also check the box next to "Ask confirmation before autoapplying..." but you will have to click 'OK' each time the plugin wants to make a change, which can become quite tedious for a large number of times.

I hope this helps. If you have questions about other uses of this plugin, you should post them in the plugin's thread:
https://getmusicbee.com/forum/index.php?topic=3833.0

That's the ticket - this is really useful.  Many thanks for your help and time phred

58
Many thanks for coming back to me phred.  Boroda74's Additional Tagging and Reporting Tools seem impressive, but I just can't see how any of them can assist.  Sorry I'm new to Musicbee and I'm stumbling around in the dark here.  Please, not wanting to put you out, but is there any chance that you could take me through the steps of setting up the automatic routine you mentioned?  Many thanks in advance

59
I have a relatively large collection of music, some of which has a leading zero before track numbers, and some don’t.  I tend to view this collection by album covers and ideally, I don’t want any of the tracks that are displayed beneath these to display a leading zero as part of a track number.  For example, I would like a track numbered ‘05’ to be listed simply as ‘5’.

I’ve established that if I assign the formula $Pad(<Track#>,1) to a virtual field it will display what I’m looking for.  However, I can’t figure out how this virtual field can be used instead of the normal, standard track number (for tracks displayed beneath their respective album covers).   I was hoping this could be possible via the ‘expanded Panel settings’ for the ‘main panel’ but I’ve had no joy with this.

Any help with resolving this would be much appreciated

60
Plugins / Re: UPnP/ DLNA device support
« on: May 04, 2017, 10:41:53 AM »
So I have had this same problem with my Yamaha RX-V777 receiver where it won't recognize the MusicBee server, but I think I found a work around. Basically I found that if I use BubbleUPnP to manage the server and select the option to 'Create a proxy Media Server on this LAN', my receiver will recognize the proxy MB server and I can browse the library through my receiver.

It's kind of a work around and maybe not ideal since now some other devices I have see both servers, but it at least works. Just thought I would throw this out there as a possible solution for anyone else having this problem with a Yamaha receiver.

+1 for this workaround, BubbleUPnP is very good.  If the DLNA device supports airplay an alternative workaround solution would be to use TuneBlade, Airfoil, or the remote speakers audio plugin developed by Eric Milles.  Ok this may imply a modest outlay of cash, but this could be worth it especially as this may open up the possibility of streaming music to multiple audio devices

Pages: 1 2 3 4