Originally Posted by DS-21
Then what’s the point?
One would think Dirac on time would be a non-issue. They have experience with the XMC-1 and it’s not like the channel count is an issue (see Datasat, Storm).
I think they spent so much time getting eARC and Dolby Vision and Atmos and DTS:X in 9.1.6 working with XO's and with expandable modules and 4K 60hz 4:4:4 that they basically ran out of time trying to get DIRAC enabled.
They must have made that decision some months ago because it's not easy to disable features in firmware, unless it's specifically designed to run as isolated sub-processes (which any smart person would do).
In any case, enjoy being a $5000 no-DSP beta tester...
If the V3 boards on the XMC-1 are that bad, I can only imagine.
Sounds like Emotiva really needs to hire a senior software architect with brains, rather than just hardware monkeys and DSP monkeys and junior software people from India and China (or wherever they got them from...)
Anyone can write bad code, that's easy. Any fresh university graduate can do that. (All theory, no experience...
Writing good code is extremely challenging for monkeys and noobs.
What makes hiring software developers really challenging is that management doesn't know how to code and thus couldn't tell a good coder from a bad one.
Also, many people are very good at lying and falsifying resumes.
If they are charming or good-looking or good at lying, then they get the job. Rather than a skill-based interviewing.
I've been a full-stack software developer for almost 20 years. 90% of interviewers don't have a clue how to interview coders. (IQ tests/questions are a horrible way to filter resumes, equally as bad as asking no programming questions.)
The first thing I ask them is: what's the difference between public, protected and private.
or interfaces vs inheritance
or pointers vs delegates vs events
or dependency injection vs inversion of control
or SOLID vs GRASP vs ACID vs 1-3 normal-form vs MVP vs MVC
or give an ideal architecture with multi-threading and micro services and load-balancing and fault-tolerance and future scalability, with Op's monitoring and business-process flow management.
Based on that I can usually get a good picture of their skill level.
Or better yet: compose a coding challenge and solve it using all of those techniques and principles, and then upload your best code for that along with your resume.
Let's just say: few get hired.
and with almost 100% hiring-accuracy for my problem-space.
I'm sure Emotiva is heavy on the assembler and Dolby/DTS/HDMI/DSP knowledge, so their questions are substantially different, but essentially the same...
I could care less if "the fox, the chicken and the grain can get across a river in min-steps"
or "where do you see yourself in 5 years"
or "why do you want to work here / why did you apply"
or "what is this shape, rotated 90 degrees mirror imagined"
Irrelevant interview questions are Irrelevant.
That won't make my DAC bug-free and future-expandable or released-to-manufacturing on time...