Jump to content

Miska

Members
  • Content Count

    14819
  • Joined

  • Last visited

About Miska

  • Rank
    Masters Level Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Miska

    HQ Player

    Well, server side doesn't have any library browsing functionality anymore at all, only the library maintenance functionality. So the server cannot and is not intended to provide same functionality as client. So all content browsing/use is at the client side. I kind of fail to understand point of a huge playlist instead of using the library browsing and searching functionality and control the playback from there. There you have all the artist and other information available and searchable. People wanted to have more focus on the artwork and that's why it is more central piece on the Client. Yes, frequently Roon core and HQPlayer server would be on same or different machines. And then Roon control and HQPlayer client on something else. But anyway, yes you would have Roon's user interface and Client running side by side, since Roon doesn't include all the HQPlayer control functionality. Based on the feedback almost nobody was using those with v3. I am trying to minimize amount of duplicated functionality between the two that also requires synchronizing two GUIs (which tends to get tricky).
  2. Miska

    HQ Player

    How far does it go before failing? Do you get the startup splash screen?
  3. Miska

    HQ Player

    They are not gone, they are just relocated to the Client application when lot of other functionality was split into server and client pieces. In Pro they are in the main window because Pro is not, and cannot be, remote controlled with a client. If you want to access the functionality you should. You could think it like this; if you have a web server to host a web site like this, you don't go to the web server software to view the pages. Instead you use web browser (client) to view the pages served by the server software. This is similar thing.
  4. Of course I know how HQPlayer does it, since I've implemented it. I don't know what Roon does, when you play from Roon to HQPlayer, you shouldn't be performing any DSP in Roon. It would be just stupid the perform convolution after the upsampling, it would increase load a lot, while performing eq for frequencies that don't exist in the source material. At least with HQPlayer that is not necessary, you would only include one filter matching highest rate/frequencies you want. Then it is scaled as necessary by HQPlayer to match the other sampling rates. This is no different than the same operation performed by the filter creation software.
  5. It is not available because it only works with most recent versions of both HQPlayer and NAA. There are still number of older NAA software versions out there where it doesn't work. I don't know if there is any standard for such volume tags. At least I have not seen it in the metadata specifications. When HQPlayer's library is used for playback, it is technically doable. When source is for example Roon it is not possible unless Roon is the one adjusting the volume at a right moment. That is not really much of a problem, volume changes are already ramped using a smooth curve.
  6. Since Roon already controls HQPlayer volume they could also do this control without changes to HQPlayer side. When Roon is used as playback source it is not possible to implement such solely at HQPlayer side.
  7. HQPlayer Convolution: Yes UPnP: Yes on Embedded Streaming Services: Yes (depends on control application)
  8. HQPlayer does it's own core allocation based on the CPU topology. And if that gets messed up the performance will suffer a lot.
  9. Note: Messing with such things related to HQPlayer will certainly screw up HQPlayer's operation. So don't do it.
  10. Miska

    HQ Player

    In v4 the graphical interface and server were stripped into separate pieces. At the server side, only configuration things were left in the GUI, in addition to bare minimum to operate the player in drag-and-drop way. Everything else regarding playback control was moved to the client side, which is a remote control application. This also allows use of the same client with Embedded version. So server (HQPlayer application itself) has a very lean GUI while the Client has all the fancy graphical rendering things (using OpenGL). This also removes unused extra things from the HQPlayer server when it is controlled by what ever external client (or combination of).
  11. Miska

    HQ Player

    For DSD output you always need a modulator. Modulator setting is not specific for PCM or DSD sources. I hope this information is quite clearly indicated in the status displays too.
  12. Miska

    HQ Player

    The drop-down menus are still there!?
  13. Miska

    HQ Player

    I kind of wonder why you wouldn't use the EC also for DSD?
  14. I doubt it makes any difference, I would be worried if it does... I have two smart HP switches and one smart Cisco switch on the way between HQPlayer server and Hapi. Since they are in different rooms, so two room specific switches and one central patch bay switch. Works fine.
  15. Miska

    HQ Player

    There is different kind of silence playback at start and stop, no more basic silence patterns but instead silence generated by the modulator.
×
×
  • Create New...