Yes, it would be great. They could also communicate with me regarding it. Other DAPs do not experience such issue. According to the logcat logs media button events start going into Cayin's player/media core once display is switched off, so the easy fix would be not to change routing of media button events when screen goes off and when active music player is holding the audio focus.
Would you please share 2 consecutive DSFs with obvious clicks between them so that it would be possible to debug the issue (e-mail to neutronmp@gmail.com).
The problem seems to have worked itself out...I was listening to a Bob Dylan DSF file this morning, which totally froze up with digital noise, and crashed the program. When I rebooted, all of the music from my 2nd SD card was missing from the Neutron library. I did a rescan, and now DSF files seems to playing smooth again.
The problem seems to have worked itself out...I was listening to a Bob Dylan DSF file this morning, which totally froze up with digital noise, and crashed the program. When I rebooted, all of the music from my 2nd SD card was missing from the Neutron library. I did a rescan, and now DSF files seems to playing smooth again.
@dmitrykos I spoke too soon, just had the issue appear again. It is random, so sending you two files won't do any good - because there's no telling when it's going to happen. It is quite a loud pop that is really jarring to the ears.
@dmitrykos I spoke too soon, just had the issue appear again. It is random, so sending you two files won't do any good - because there's no telling when it's going to happen. It is quite a loud pop that is really jarring to the ears.
try this for nothing.
under audio hardware, reduce software latency to min. and increase hardware latency to max. click OK.
see how you go.
Are you decoding DSD in Neutron, or are you sending it to your DAC direct?
try this for nothing.
under audio hardware, reduce software latency to min. and increase hardware latency to max. click OK.
see how you go.
Are you decoding DSD in Neutron, or are you sending it to your DAC direct?
You may have solved my issue - I'm using a FiiO M11, so I believe it's a direct hardware decode with the DAP. I'm just testing out your solution right now - and so far so good.
Thank you!
I think that's an Android thing!
workaround is, give the volume one quick click, Android volume shows up momentarily , then goes away and won't come back.
alternatively , use the slider in eq. screen.
I'm a long time UAPP user on my mobile device for streaming Qobuz however I have just bought a modern chromebook that permits certain apps to work.
UAPP can't be loaded onto the chromebook however I see Neutron can be downloaded.
Can I get Neutron to play Qobuz via my external dac to bypass android 48khz resampling (like UAPP does on mobile) and if so could somebody kindly link me to the process I need to go through please?
There is no such setting currently. This launch is caused by the OS when it tries to connect to the Media Browser service of the app when BT connection is established (probably to provide media info to the destination BT device). This service is required for Android app if it supports Android Auto. It is in to-do to add an option to reject such connection attempts and to avoid launch of the player's core process.
I'm a long time UAPP user on my mobile device for streaming Qobuz however I have just bought a modern chromebook that permits certain apps to work.
UAPP can't be loaded onto the chromebook however I see Neutron can be downloaded.
Can I get Neutron to play Qobuz via my external dac to bypass android 48khz resampling (like UAPP does on mobile) and if so could somebody kindly link me to the process I need to go through please?
To my knowledge Chromebooks do not support any hi-res output and even do not support USB OTG (at least some of them, according user reports), so there is no app which could overcome the single format you get in a Chromebook. Neutron does not support Qobuz streaming service.
There is no such setting currently. This launch is caused by the OS when it tries to connect to the Media Browser service of the app when BT connection is established (probably to provide media info to the destination BT device). This service is required for Android app if it supports Android Auto. It is in to-do to add an option to reject such connection attempts and to avoid launch of the player's core process.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.