A unique feature, definitely interesting to me. Add this to the list of DAC V1 features and… I couldn’t resist: just ordered a DAC V1!I hope this new functionality will make interaction with the DAC V1 even more interesting and exciting
A unique feature, definitely interesting to me. Add this to the list of DAC V1 features and… I couldn’t resist: just ordered a DAC V1!I hope this new functionality will make interaction with the DAC V1 even more interesting and exciting
It is shame that there is no desktop DAC with functionality like Neutron DAC and remotely controlled by mobile app like Qudelix 5k DAC.That will me my dream setup for PRi streamer.
Thank you! I cant wait for it! Web based management is the way to go without ability to control DAC V1 over BT. It will serve as my desktop DAC connected to RPi streamer and amp. 5V balanced output can add dynamic range, but this another storyWith time being all can be possible
For now, active development is happening on simultaneously mobile + web version of NConfigurator. Here is a screenshot of the initial working version on Android device with DAC V1 connected to it:
View attachment 429168
It is not a pure mobile app. Mobile app is running the native NConfigurator core which acts as USB interface to the connected DAC V1 and as a HTTP server for the Web API, it also runs web view (GUI) of the web-app being developed in Angular - 3 roles in total. Web-app is served by nconf.neutronhifi.com externally.
Once completed, NConfigurator (any version, including PC) will be able to run as HTTP daemon, so you will be able to run it as service on some headless mini-PC serving as audio streamer via DAC V1. It then can be accessed with a web browser from any other device.
Of course, you will be able to just install Android version of NConfigurator from Google Play and access DAC V1 connected to this Android device, above is just the extended usage scenario.
Do you think NConfigurator could be embedded onto something like a ESP32?With time being all can be possible
For now, active development is happening on simultaneously mobile + web version of NConfigurator. Here is a screenshot of the initial working version on Android device with DAC V1 connected to it:
View attachment 429168
It is not a pure mobile app. Mobile app is running the native NConfigurator core which acts as USB interface to the connected DAC V1 and as a HTTP server for the Web API, it also runs web view (GUI) of the web-app being developed in Angular - 3 roles in total. Web-app is served by nconf.neutronhifi.com externally.
Once completed, NConfigurator (any version, including PC) will be able to run as HTTP daemon, so you will be able to run it as service on some headless mini-PC serving as audio streamer via DAC V1. It then can be accessed with a web browser from any other device.
Of course, you will be able to just install Android version of NConfigurator from Google Play and access DAC V1 connected to this Android device, above is just the extended usage scenario.
Do you think NConfigurator could be embedded onto something like a ESP32?
Then… could a version of USB isolator include this ESP32 (or else) HTTP server as an added feature? USB isolator would become the desktop host for DAC V1…
Maybe I'll be lucky and see balanced outs on this stationary device ) Packed with features like V1 and excellent support from you that device will have no contenders, maybe one - RME, but this is another price range. Support is the key here, I think.ESP32 (S2/S3) are Full-Speed USB MCUs, so will not serve in this scenario as DAC V1 is a High-Speed USB device (primarily). Also, such idea looks too complicated because Isolator V1 must simulate self as USB DAC to US Host (PC for example) to collect audio USB packets from it and then on 2-nd USB port (outbound) it has to behave as USB host for DAC V1 and feed received USB data from PC. Normally USB isolator is not seen by PC as USB device, it just replays USB packets with specialized IC (making USB data transmission isolated) and generates isolated DC power. So when you connect some USB client to Isolator V1 for example, then USB Host (PC) sees connected USB device as if it is connected by the cable directly to PC.
Better and much simpler just develop new USB DAC (stationary in this case) with isolated USB port and WiFi capability onboard. Then MCU/CPU of the device will host NConfigurator, WiFi/LAN would serve Web API of NConfigurator and isolated port will substitute Isolator V1.
@dmitrykos How are Intersample Overs processed in DACv1? Hopefully it is not bothering question, I'm sure you, with your skills have take care of it. Thank you.
Thank you, to be safe from bad recorded music with intersample overs it is recommended to run -3dB from max volume when operating as desktop DAC connected to AMP. Right?There is no clipping in DAC V1 at all frequencies, otherwise we would measure a distortion (obviously) and so high precision would not be achieved in the benchmark of the review and own measurements. Oversampling Filter's 2-nd stage normalizes gain so that it would not exceed max in digital domain. Furthermore you have Impedance presets in NConfigurator which engage (or not) Master Trim setting of the DAC chip to avoid clipping in analog domain.
Thank you, to be safe from bad recorded music with intersample overs it is recommended to run -3dB from max volume when operating as desktop DAC connected to AMP. Right?
How can a EQ profile be switched easily in Windows? Would be great to have a pop-up from a task tray icon with a list of saved profiles to pick from. Or perhaps this is available already? Also, maybe even better, is there a way to switch profiles from a command line?
Thank you or detailed explanation. I'm using UAPP app to play bit-perfect to DAC. But some songs are recorded in wrong way, not respecting specs for audio mastering. I'm referencing to this article for example:If you are not using any DSP which can equalize digital representation of the audio wave then you do not need that headroom (-3 dB). When music player app is reading/decoding music file the data in it is already truncated/clamped to the valid digital range, for simplicity let's say [-1.0, 1.0]. So if no processing is done on this data then it will not cause any overloading in digital domain and DAC chip will also output non-clipped analog wave. It must happen like this.
But, if there are errors in music player app, for example it converts from floating point to integer representation and does not clamp values to the valid range then overloading can happen in digital domain. If hardware design has flaws then it can also can cause clipping in analog output, or maybe there is no THD setting via some app like NConfigurator for DAC V1 which corrects master volume of the DAC chip for the impedance of the connected headset.
So there is no general rule for -3 dB thing to my view, if you really hear overloaded sound then decreasing master gain to some value which stops this behavior is a good idea.
But some songs are recorded in wrong way, not respecting specs for audio mastering.