It is not easy! Every time I set the volume output level to 100% and save it according to your guide, it reverts to 40%!
Last edited:
I don't know if you/Andrea did it on purpose or a bug, but setting and saving the output level to 100% is not possible at all😡. Setting and saving it to 99% or lower is OK though😱
Hi quanghao, I am Javier Cobo, I have sent you a private message, but you don´t answer me.
Please tell me the remaining amount I have to pay, I would also know exactly the amount for delivery and que amount to declare. I´ll make to payments, one with delivery+declared value, and another with the rest (Customs in Spain are terrible)
Cannot save the volume level at 100% ?
This week and the next I am in holiday (Naxos island) so I can change the firmware when I came back.
Tell me if there is the necessity of other modifications.
audiodesign said:
1) Cannot save the volume level at 100%
2) Ask to save the input selection (other than USB).
3) Do not mute on high efficiency loudspeakers when level at 1%.
4) Ask to insert a white-on-blue bargraph on the display for the level (while inverting the displayed characters to blue-on-white on the same line), very usefull with the remote.
1) Cannot save the volume level at 100%
2) Ask to save the input selection (other than USB).
3) Do not mute on high efficiency loudspeakers when level at 1%.
4) Ask to insert a white-on-blue bargraph on the display for the level (while inverting the displayed characters to blue-on-white on the same line), very usefull with the remote.
5) Hide the blinking cursor
6) Display "192kHz" (now "191kHz")
7) Bug: Under certain circumstances pressing a button does not get handled. When pressing another button the last one gets executed (like pressing Vol- and then pressing Vol+, Vol- is actually performed)
8) Bug: While in settings mode if the input sample rate changes the display gets overridden with the changed sample rate (which shouldn't show in settings mode) while still being in settings mode
9) Personal feature proposal: Something I would like to have but nothing to complain about: auto dim/turn off the display after a timeout - reactivate it when the remote control is operated (and ignoring the first button that was pushed to turn it back on)
10) Feature: A way to display the installed firmware version
11) Personal feature proposal: The mute button should always be mute. No reuse of this button in any other display mode. It is kind of an emergency button and it should not matter what display mode you are currently in.
2) Ask to save the input selection (other than USB).
3) Do not mute on high efficiency loudspeakers when level at 1%.
4) Ask to insert a white-on-blue bargraph on the display for the level (while inverting the displayed characters to blue-on-white on the same line), very usefull with the remote.
5) Hide the blinking cursor
6) Display "192kHz" (now "191kHz")
7) Bug: Under certain circumstances pressing a button does not get handled. When pressing another button the last one gets executed (like pressing Vol- and then pressing Vol+, Vol- is actually performed)
8) Bug: While in settings mode if the input sample rate changes the display gets overridden with the changed sample rate (which shouldn't show in settings mode) while still being in settings mode
9) Personal feature proposal: Something I would like to have but nothing to complain about: auto dim/turn off the display after a timeout - reactivate it when the remote control is operated (and ignoring the first button that was pushed to turn it back on)
10) Feature: A way to display the installed firmware version
11) Personal feature proposal: The mute button should always be mute. No reuse of this button in any other display mode. It is kind of an emergency button and it should not matter what display mode you are currently in.
Last edited:
1) Cannot save the volume level at 100%
2) Feature proposal : Save the input selection (other than USB).
3) Bug : Do not mute on high efficiency loudspeakers system when level at 1% (for example, remains very loud on VOTT).
4) Feature proposal : Insert a white-on-blue bargraph on the display for the level (while inverting the displayed characters on the same line to blue-on-white), very usefull with the remote.
5) Hide the blinking cursor
6) Display "192kHz" (now "191kHz")
7) Bug: Under certain circumstances pressing a button does not get handled. When pressing another button the last one gets executed (like pressing Vol- and then pressing Vol+, Vol- is actually performed)
8) Bug: While in settings mode if the input sample rate changes the display gets overridden with the changed sample rate (which shouldn't show in settings mode) while still being in settings mode
9) Personal feature proposal: Something I would like to have but nothing to complain about: auto dim/turn off the display after a timeout - reactivate it when the remote control is operated (and ignoring the first button that was pushed to turn it back on)
10) Feature: A way to display the installed firmware version
11) Personal feature proposal: The mute button should always be mute. No reuse of this button in any other display mode. It is kind of an emergency button and it should not matter what display mode you are currently in.
12) Feature proposal : Add a led on the front panel which blink when pressing on a button on the remote. Maybe that pins are already available for this on the controller pcb.
2) Feature proposal : Save the input selection (other than USB).
3) Bug : Do not mute on high efficiency loudspeakers system when level at 1% (for example, remains very loud on VOTT).
4) Feature proposal : Insert a white-on-blue bargraph on the display for the level (while inverting the displayed characters on the same line to blue-on-white), very usefull with the remote.
5) Hide the blinking cursor
6) Display "192kHz" (now "191kHz")
7) Bug: Under certain circumstances pressing a button does not get handled. When pressing another button the last one gets executed (like pressing Vol- and then pressing Vol+, Vol- is actually performed)
8) Bug: While in settings mode if the input sample rate changes the display gets overridden with the changed sample rate (which shouldn't show in settings mode) while still being in settings mode
9) Personal feature proposal: Something I would like to have but nothing to complain about: auto dim/turn off the display after a timeout - reactivate it when the remote control is operated (and ignoring the first button that was pushed to turn it back on)
10) Feature: A way to display the installed firmware version
11) Personal feature proposal: The mute button should always be mute. No reuse of this button in any other display mode. It is kind of an emergency button and it should not matter what display mode you are currently in.
12) Feature proposal : Add a led on the front panel which blink when pressing on a button on the remote. Maybe that pins are already available for this on the controller pcb.
1) Cannot save the volume level at 100%
2) Feature proposal : Save the input selection (other than USB).
3) Bug : Do not mute on high efficiency loudspeakers system when level at 1% (for example, remains very loud on VOTT).
4) Feature proposal : Insert a white-on-blue bargraph on the display for the level (while inverting the displayed characters on the same line to blue-on-white), very usefull with the remote.
5) Hide the blinking cursor
6) Display "192kHz" (now "191kHz")
7) Bug: Under certain circumstances pressing a button does not get handled. When pressing another button the last one gets executed (like pressing Vol- and then pressing Vol+, Vol- is actually performed)
8) Bug: While in settings mode if the input sample rate changes the display gets overridden with the changed sample rate (which shouldn't show in settings mode) while still being in settings mode
9) Personal feature proposal: Something I would like to have but nothing to complain about: auto dim/turn off the display after a timeout - reactivate it when the remote control is operated (and ignoring the first button that was pushed to turn it back on)
10) Feature: A way to display the installed firmware version
11) Personal feature proposal: The mute button should always be mute. No reuse of this button in any other display mode. It is kind of an emergency button and it should not matter what display mode you are currently in.
12) Feature proposal : Add a led on the front panel which blink when pressing on a button on the remote. Maybe that pins are already available for this on the controller pcb.
13) Feature proposal: standby and trigger out options (Quanghao is working on this)
14) Feature proposal: allow microprocessor to accept commands via amanero i2c interface - this should allow control of the DAC via a PC source and through this, android app.
2) Feature proposal : Save the input selection (other than USB).
3) Bug : Do not mute on high efficiency loudspeakers system when level at 1% (for example, remains very loud on VOTT).
4) Feature proposal : Insert a white-on-blue bargraph on the display for the level (while inverting the displayed characters on the same line to blue-on-white), very usefull with the remote.
5) Hide the blinking cursor
6) Display "192kHz" (now "191kHz")
7) Bug: Under certain circumstances pressing a button does not get handled. When pressing another button the last one gets executed (like pressing Vol- and then pressing Vol+, Vol- is actually performed)
8) Bug: While in settings mode if the input sample rate changes the display gets overridden with the changed sample rate (which shouldn't show in settings mode) while still being in settings mode
9) Personal feature proposal: Something I would like to have but nothing to complain about: auto dim/turn off the display after a timeout - reactivate it when the remote control is operated (and ignoring the first button that was pushed to turn it back on)
10) Feature: A way to display the installed firmware version
11) Personal feature proposal: The mute button should always be mute. No reuse of this button in any other display mode. It is kind of an emergency button and it should not matter what display mode you are currently in.
12) Feature proposal : Add a led on the front panel which blink when pressing on a button on the remote. Maybe that pins are already available for this on the controller pcb.
13) Feature proposal: standby and trigger out options (Quanghao is working on this)
14) Feature proposal: allow microprocessor to accept commands via amanero i2c interface - this should allow control of the DAC via a PC source and through this, android app.
Another Bug is that 48kHz sampling rate displays as "47kHz".
On the feature request list above I agree that:
1) it should save the source.
2) I think that mute being its own completely dedicated button is also a smart idea
Some of the other feature requests I tend to suspect might not be practical, but I think that these two new features would make a lot more people happy.
On the feature request list above I agree that:
1) it should save the source.
2) I think that mute being its own completely dedicated button is also a smart idea
Some of the other feature requests I tend to suspect might not be practical, but I think that these two new features would make a lot more people happy.
Yesterday, I sent your DAC for the list and bill of lading number below:
So I put larger, and more carefully, so the weight of the package Dac 8 kg, so I select the shipping TNT and fedexl.
A. TNT Tracking
1. Dredline: Bill TNT: 758 717 669
2. Erlend Saeterdal: Bill TNT: 758 717 655
3. CAAD "47": Bill TNT: 758 717 641
4. Raoul: Bill TNT: 758 717 638
5. Linuxfan: Bill TNT: 758 717 624
B. https://www.fedex.com/fedextrack/
6. Milezone: Bill FedEx: 8034 8573 6321
7. Chansiukwing: Bill FedEx: 8025 9771 5746
C. The DAC you have completed, I will send on the next day.
The shield is sent in the form of letters.
The chassis faulty you will be sent more slowly, because I wait for manufacturers to do more.
Thank you
So I put larger, and more carefully, so the weight of the package Dac 8 kg, so I select the shipping TNT and fedexl.
A. TNT Tracking
1. Dredline: Bill TNT: 758 717 669
2. Erlend Saeterdal: Bill TNT: 758 717 655
3. CAAD "47": Bill TNT: 758 717 641
4. Raoul: Bill TNT: 758 717 638
5. Linuxfan: Bill TNT: 758 717 624
B. https://www.fedex.com/fedextrack/
6. Milezone: Bill FedEx: 8034 8573 6321
7. Chansiukwing: Bill FedEx: 8025 9771 5746
C. The DAC you have completed, I will send on the next day.
The shield is sent in the form of letters.
The chassis faulty you will be sent more slowly, because I wait for manufacturers to do more.
Thank you
I think "1. Dredline" is me.
TNT's rate is not cheap but service is good. Thank you Quanghao for the improved packaging and kind efforts.
TNT's rate is not cheap but service is good. Thank you Quanghao for the improved packaging and kind efforts.
I think "1. Dredline" is me.
TNT's rate is not cheap but service is good. Thank you Quanghao for the improved packaging and kind efforts.
Submitted )
Hi Quanghao & Andrea,
I have been asking to you the schematic of the I/V output stage for several times and you did never answered me on that point.
So, following the traces on the PCB, I tried to recognize how are connected the output connectors XLR and RCA. I think it looks like the joined schematic and I consider this schematic is a little bit simplistic... This means that it is impossible to use at the same time the XLR connector to sub amp and RCA connector to main amp because we will encounter issues in impedance balance.
More, I notice that + and - are not "summed" on RCA output.
- Do you confirm my point of view ?
Thank you very much.
I have been asking to you the schematic of the I/V output stage for several times and you did never answered me on that point.
So, following the traces on the PCB, I tried to recognize how are connected the output connectors XLR and RCA. I think it looks like the joined schematic and I consider this schematic is a little bit simplistic... This means that it is impossible to use at the same time the XLR connector to sub amp and RCA connector to main amp because we will encounter issues in impedance balance.
More, I notice that + and - are not "summed" on RCA output.
- Do you confirm my point of view ?
Thank you very much.
Attachments
Last edited:
- Status
- Not open for further replies.