ROON new DSP feature is a very interesting feature for people like me using digital volume control, upsampling and easy room coorrection.
Implementing roon bridge on melco avoid to add small streamer device in the chain.
(20-Jul-2017, 12:30)Hifi_swlon Wrote: [ -> ]What happened to Melcos App?
Roon taking 5-10 secs to foreground seems a bit long. Mines 1-2s.
Hi HiFi-swlon on the HighEnd I spoke with a Melco coworker. The confirmed the app just before the release is (September 2017) !!
Very similar time to the planned core infinity date. Maybe they're just piggy backing on whatever Devialet do?
(20-Jul-2017, 16:00)Hifi_swlon Wrote: [ -> ]Very similar time to the planned core infinity date. Maybe they're just piggy backing on whatever Devialet do?
In my time working for a UK company, very rarely, if ever, was their a major software release during the summer months. The timing was usually mid/late September when the majority of staff were available for the implementation and, dare I say, the eventual debugging and fix releases.
(20-Jul-2017, 11:43)Rufus McDufus Wrote: [ -> ]I tend to power the Melco off when I'm not using it (the N1A isn't totally silent so can be a bit annoying) and as a result of startup time - usually Twonky taking a while to rescan (grr) I tend to prefer to use Lumin nowadays because it keeps an index of tracks and can play tracks virtually straight after Melco power up.
That Twonky startup scan can be avoided if you have access to the Twonky startup command, but that's not accessible on Melco and I've not managed to hack into it (yet).
You can disable Twonky when you have MinimServer installed on the Melco. Link here -
www.minimserver.com/install-melco.html
See extract from installation notes:
[NEW] Twonky and MinimServer should both start automatically when the N1 is powered on. Having Twonky running as well as MinimServer can cause performance issues with a large library. To stop Twonky running, you can edit the minimserver.options file in the share/MinimServer/etc folder and change the stoptwonky setting from false to true. This setting will take effect the next time you power on the N1.
The N1 front panel doesn't show the details of music files that are being streamed by MinimServer.
(20-Jul-2017, 16:51)nicoludio Wrote: [ -> ] (20-Jul-2017, 11:43)Rufus McDufus Wrote: [ -> ]I tend to power the Melco off when I'm not using it (the N1A isn't totally silent so can be a bit annoying) and as a result of startup time - usually Twonky taking a while to rescan (grr) I tend to prefer to use Lumin nowadays because it keeps an index of tracks and can play tracks virtually straight after Melco power up.
That Twonky startup scan can be avoided if you have access to the Twonky startup command, but that's not accessible on Melco and I've not managed to hack into it (yet).
You can disable Twonky when you have MinimServer installed on the Melco. Link here - www.minimserver.com/install-melco.html
See extract from installation notes:
[NEW] Twonky and MinimServer should both start automatically when the N1 is powered on. Having Twonky running as well as MinimServer can cause performance issues with a large library. To stop Twonky running, you can edit the minimserver.options file in the share/MinimServer/etc folder and change the stoptwonky setting from false to true. This setting will take effect the next time you power on the N1.
The N1 front panel doesn't show the details of music files that are being streamed by MinimServer.
Thanks! I have done that in the past. I actually slightly prefer the sound quality from Twonky, even though it annoys the hell out of me for many reasons. There's not really a lot in it SQ-wise though.
I think I might go back to Minimserver... I chop and change too frequently!
Been out of the loop for a while. Must have overlooked your previous messages. Think that you were one of the first Melco/MinimServer users...
The Melco boots up faster when Twonky is disabled though, and I just have this nagging feeling that disabling one unused server would reduce CPU usage, etc. and enhance the sound.
