Stunsworth
pfm Member
I can't recall any specifications being posted over there, though to be honest Facebook seems to have dried up as a source of information about the project.
MDAC First Listen (part 00111011)
- Thread starter fred sonnen
- Start date
- Status
I can't recall any specifications being posted over there, though to be honest Facebook seems to have dried up as a source of information about the project.
adamdea
You are not a sound quality evaluation device
Yes you're quite right, with the mountain of available information on the mdac 1.5 only an idiot would make assumptions.
Let's see what the data sheet says, shall we?
Yes! It's all a juge pile of fake news!! Come on hippies!!!
Contribution to the audio side of things: Really hope that there's more hardware to follow. Mdac 1.5 and 2, fdac, vfet, ministreamer, all prototype dacs and their spinoffs are not enough, maybe.
russel
./_dazed_and_confused
I am hoping the mdac1.5 is closer to what we originally ponied up for rather the moon on a stick mdac 2.0 morphed into.
JohnW
pfm member
The MDAC 2 is still able to be a slave unit eg. when used with DSP (never 5.1). Slave units will be MDAC2 but without front panel.
MDAC1.5 is balanced output, Discrete DAC, uses the same modulator options as MDAC2, but uses a standard Analogue stage rather then the Direct Digital To Analogue conversions (DD2A) of the MDAC2.
Just returned to where the MDAC is located and can report version A.010.
No report of USB Buffer Flush error.
I don't hear the clicks via the MDAC audio output.
John, thank you for the suggestion to try V0.90. It worked better than A.010 (Benchmark LED not flashing anymore), but clicks (or is it pops?) can still be heard every 3-10 seconds (more frequent on 24/96 material). I guess I could try other firmware versions in the hope one might work, but I won't press my luck.
Therefore, please let me know if your kind offer to provide a streamer on loan is still valid and is feasible for you, say within the next 5-7 days, or not, so that I can plan my next step.
Therefore, please let me know if your kind offer to provide a streamer on loan is still valid and is feasible for you, say within the next 5-7 days, or not, so that I can plan my next step.
JohnW
pfm member
It appears that The LED flashing is not important - its just indicating the SPDIF validity flag which is set on the A0.10 software to work around the ESS Left Channel Locking Bug (Data's OK).
I would more worry about why the Benchmark cannot lock to the MDAC's SPDIF output - bare in mind its being correctly decoded by the MDAC's internal ESS.
Can you not pop into your local deal and try a different DAC on the MDAC's output?
What Cable are you using between the MDAC and Benchmark- A Standard RCA to RCA?
I'd be happy to take a look at your MDAC if you cover shipping costs.
WRT Streamer, its a bad time, as we are just about to build and test the MDAC2 Discrete DAC PCB's... so its going to be very busy in the lab - and very important time WRT the progress of the MDAC 1.5 / 2 project...
Give me a day to see if I can find anything I can send you...
I would more worry about why the Benchmark cannot lock to the MDAC's SPDIF output - bare in mind its being correctly decoded by the MDAC's internal ESS.
Can you not pop into your local deal and try a different DAC on the MDAC's output?
What Cable are you using between the MDAC and Benchmark- A Standard RCA to RCA?
I'd be happy to take a look at your MDAC if you cover shipping costs.
WRT Streamer, its a bad time, as we are just about to build and test the MDAC2 Discrete DAC PCB's... so its going to be very busy in the lab - and very important time WRT the progress of the MDAC 1.5 / 2 project...
Give me a day to see if I can find anything I can send you...
Cables are a Supra Coaxial and an Amazon Basics optical. Benchmark locks properly to a Sony Bluray player on Coaxial and to a Samsung tv on optical, if that's any indication.
WRT Streamer, no problem, I totally understand (am waiting for an MDAC2 myself). If there's anything lying around that might stop the gap, that'd be great...
WRT Streamer, no problem, I totally understand (am waiting for an MDAC2 myself). If there's anything lying around that might stop the gap, that'd be great...
Last edited:
Stunsworth
pfm Member
...just to mention there is some news on the Facebook Group (the loudspeaker chatter may have obscured it) ...the boards received last week had an issue on a section so John is testing the other sections that were printed correctly; then reissuing AFAIK ...these things happen
As far as I can see the only images of the new boards are CAD renderings.
JohnW
pfm member
...just to mention there is some news on the Facebook Group (the loudspeaker chatter may have obscured it) ...the boards received last week had an issue on a section so John is testing the other sections that were printed correctly; then reissuing AFAIK ...these things happen
Yes, caught a few little bugs, nothing big. within the last few hours have the latest Clock circuit working on the PCB's... I'm now going to confirm the clock distribution (across galvanic isolation barrier etc)... Shame about the Gerber output error as so far these PCB's would have been good.
Jareks working on the updating the design / next step with balanced outputs (This board is just single-ended)... expecting to release Monday next week - this time we will careful go over the Gerber outputs to insure we dont have a repeat of the software bug that corrupted the last PCB's.
davidjt
pfm Member
Extract from John's latest Facebook update:
"The DevDAC II PCB files were issued this morning, [16th August] took a little longer then expected as we updated the design based upon feedback from the smaller Single-ended Discrete DAC PCB (I've been testing circuit sections on the bench these past few weeks)"
"The DevDAC II PCB files were issued this morning, [16th August] took a little longer then expected as we updated the design based upon feedback from the smaller Single-ended Discrete DAC PCB (I've been testing circuit sections on the bench these past few weeks)"
moosemeat
pfm Member
A few people on Facebook are advocating that John change the plan from designing the MDAC2 PCB to fit the MDAC case to some other, larger case. Déjà vu! Perhaps these people aren't aware we've already been down this path. Perhaps they're also unaware that changes to the plan will result in significant changes to timescale. Based on the latter alone, I, for one, am against any change to the plan.
- Status