Minim always scans music database

[Alekz]

(09-01-2013 21:02)simoncn Wrote:  It does this every time you select Restart from the minim icon. If you have music playing, this continues to play while the restart is in progress.

Aha! Got it now! Thanks!

[clasch66]

Same problem here with "Error: incorrect FLAC header xyz at offset 0 in file ..."

Haven't tried all, but the ones I tried play without a problem. Any news on this?

Same with "Error: unexpected end of file at offset xyz in file ..."

Cheers Claus

[dvdr]

@simoncn - is there any way to introduce an option to NOT scan at the start?
Reason for this: imagine, that I do not have my server running 24/7, and right now, starting and checking of the database takes about 10 minutes at each start. Not a nice thing, if you want to listen to music right away.
But no critizism without suggesting a solution (without bloating MinimServer's code with some sort of "autowatch" feature...):
What about an option in the configuration "do not scan on startup" for all those, who know, that they are not changing their collection all too often. So MinimServer could start up right away, and in case you DID add music, you start the rescan manually from your control-point (aka Plugplayer, Songbook etc.). In the list of albums/artists etc., there is a button at the bottom, right below "[folder view]", that says "rescan". If you hit it, you start a rescan.
Asset uPnP had this feature in the beginning, before they developed an autoscan feature, so I think, it might be a possible way to enhance MinimServer's useability - what do you think?

[simoncn]

(30-08-2013 23:50)dvdr Wrote:  @simoncn - is there any way to introduce an option to NOT scan at the start?
Reason for this: imagine, that I do not have my server running 24/7, and right now, starting and checking of the database takes about 10 minutes at each start. Not a nice thing, if you want to listen to music right away.
But no critizism without suggesting a solution (without bloating MinimServer's code with some sort of "autowatch" feature...):
What about an option in the configuration "do not scan on startup" for all those, who know, that they are not changing their collection all too often. So MinimServer could start up right away, and in case you DID add music, you start the rescan manually from your control-point (aka Plugplayer, Songbook etc.). In the list of albums/artists etc., there is a button at the bottom, right below "[folder view]", that says "rescan". If you hit it, you start a rescan.
Asset uPnP had this feature in the beginning, before they developed an autoscan feature, so I think, it might be a possible way to enhance MinimServer's useability - what do you think?

This request is very timely, as I have just implemented a "restart without rescan" capability for inclusion in the next release of MinimServer. When a rescan is needed, the user will also be able to initiate a "rescan and restart" operation by selecting this from MinimWatch (not from a UPnP control point). In some future release, I hope to be able to also support a "rescan without restart" capability.

You are asking for something slightly different (an option to do the initial startup without rescanning), and I'll think about the best way to provide this.

[dvdr]

Simon, thanks for that answer & considering my suggestion - that indeed is good news! May I add two suggestions / observations?

- is it possible to display "newly added albums"? Usually, I'm listening more often to those albums, that I just added, so it would be convenient to access them directly ;-) Is that possible with the current version with a special entry in the config, or would that have to be implemented?

- Using Songbook, whenever I have restarted MininServer (either restart or reboot of the server), I am having problems with the discovery. Most of the times, Songbook will not display MinimServer in the uPnP-server list (MinimServer is already up and running!), when I fire up Songbook. I will have to use the function "clear and search" to completely clear the list of uPnP-devices, then I will be able to access MinimServer. Sometimes (I assume, it is when just reboting MinimServer) MinimServer is still in the list, but I cannot access it anymore.
Also, sometimes MinimServer will be displayed as "UpNp-server" (I can see its IP, so it is MinimServer), then I cannot access/browse it. After a few "clear and scan"-s, it finally will we found as MinimServer (that's the name I gave it in the config), and then I can access/browse it.
Any idea, what that could be? The IP is fixed, btw....

Thanks again for your continuing support!

[simoncn]

(02-09-2013 11:02)dvdr Wrote:  Simon, thanks for that answer & considering my suggestion - that indeed is good news! May I add two suggestions / observations?

- is it possible to display "newly added albums"? Usually, I'm listening more often to those albums, that I just added, so it would be convenient to access them directly ;-) Is that possible with the current version with a special entry in the config, or would that have to be implemented?

This isn't possible currently. It's on my list of requested features for a future release.

Quote:- Using Songbook, whenever I have restarted MininServer (either restart or reboot of the server), I am having problems with the discovery. Most of the times, Songbook will not display MinimServer in the uPnP-server list (MinimServer is already up and running!), when I fire up Songbook. I will have to use the function "clear and search" to completely clear the list of uPnP-devices, then I will be able to access MinimServer. Sometimes (I assume, it is when just reboting MinimServer) MinimServer is still in the list, but I cannot access it anymore.

These problems are caused by issues with how Songbook discovers the server. You should be able to solve these problems by using MinimWatch to set the ohnet.port property to a fixed port number. The recommended port number is 9791. In the next release of MinimServer, this will be the default setting.

Quote:Also, sometimes MinimServer will be displayed as "UpNp-server" (I can see its IP, so it is MinimServer), then I cannot access/browse it. After a few "clear and scan"-s, it finally will we found as MinimServer (that's the name I gave it in the config), and then I can access/browse it.
Any idea, what that could be? The IP is fixed, btw....

Thanks again for your continuing support!

I haven't seen this and I don't know what would cause it. It is probably something that Songbook is doing. It's quite likely that setting the ohnet.port property will fix this as well.