is that balance for the BHK Pre? if so how would it know which one to move? could be confusing.
Brian,
This is how the balance worked with the Directstream mk 1 and the BHK preamp. If you wan to adjust the preamp balance first adjust the preamp volume than adjust the balance it will change on the preamp. If you want to adjust the DAC balance first adjust the DAC volume than when you adjust the balance it will adjust the DAC. I am hoping that with future development of the UI firmware that it will eventually work the same with the mk 2.
2 Likes
Ah, never used it. So they could do that in this one.
@tedsmith can I put in a usb pigtail so I do not have to fuss with getting a usb stick in behind the device? is that input inert when playing music as in the wire being in there not hurt anything?
It’s pretty inert. The electrical path is a long way from the FPGA, etc. and there’s no source of noise on that cable. It could be a small RF receiver, but I don’t think that’s likely to be significant. For me the convenience would definitely be worth it.
4 Likes
Just checked mine 2.3.6 and 179. I believe that is latest correct?
Seems logical, also from a writing the code and manual perspective.
1 Like
The Beta team got 2.3.3. Maybe you have new features?
or its 2.3.3 w/o that beta back door they have coded.
No new features that I have seen my remote is working better than at 2.33. My unit can back with 2.36.
2 Likes
@barrys @aaronm - Will you be making 2.3.6 available to those of us that received early units?
Thanks!
Vince
I needed to return my MK2 to PSA because it would not update the firmware, I was on a really old version of it. When I got it back from them about 2 weeks ago it was on 2.3.6 and FPGA 179. So, as far as I know, that is the most current version.
3 Likes
We are not planning to release that to the wild. We had to do a Rev number change for the DAC’s moving forward. The only difference .6 makes is there was a chip on the display screen that could not function with the older software. The .6 will be added on all DAC’s shipped out, but there’s no difference to code or functionality of the 2.3.3. Other than allowing the display chip to talk to the system.
When we have a unit come in for repair or troubleshooting, we just blanket add that code onto the DACs
It’s just the fun parts thing! One week they are in stock, the next week they are not. So we had to change the one display chip.
2 Likes
Is that going to affect the sound in any way? And is that new chip a temporary swap in until the original once again becomes available, or is it a permanent change?
Does this mean there will be two versions of code for the two sets of DACs? Sounds like new chip requires new code. Or will the code branches merge on next release?
Is this chip on all the units including the Beta units? What does the chip do? What information does it display? Why can’t all units be brought up to the level where the display screen chip is functional?
Stepping in here to answer some of the recent questions regarding 2.3.6.
2.3.6 works on all boards and is compatible with all hardware in the field, as will all software going forward. We can auto-detect all hardware revisions and the software knows how to do the right thing. For those who are aware of how software releases work, there was never a separate branch that needed to be merged, the new driver was just added to our main branch.
To answer some other questions:
- The change was to a chip on the display board that actually controls the five button nav cluster. It has no affect on sound and this chip is not even on the main digital board. It’s on a separate board (the display board) that is isolated from the main board.
- This is not a temporary change, we have approved multiple chips to handle the button cluster input. We took this approach due to the supply chain/ parts availability issues, to insure we had multiple paths to building units in production. The parts are from the same manufacture and are cousins, so the underlying driver technology is almost identical. We just have to identify which chip we are talking to and take some slightly different steps during communication.
- The change is transparent to the functionality of the unit. When you press a button that input gets sent to a GPIO chip that eventually gets communicated back to our main processor chip. That signal path is the same regardless of which chip we use.
10 Likes
PIA for the embedded systems folks to have to support/accommodate multiple chips due to the different timing or polarity or code or pinout or whatever the distinction between the chips is but good that the planning was done to overcome the parts shortcoming without a relayout. This sort of thing probably happens a lot and you never hear about it typically with many embedded systems type products
1 Like
Thank-you
So if my five button cluster works properly I can forgetaboutit. 