Hi Uwe,
no picture yet but size and layout are documented in the attached pdf.
Nick
View attachment ExpansionDrawing.pdf
Hi Nick,
thanks for the pdf. Looks like a nice small board.
Will the input sensitivity for the symmetric XLR input be the same as for the analogue RCA input of the main board (= 0dbV)?
Do you have an estimation when the expansion board will available?
Uwe
thanks for the pdf. Looks like a nice small board.
Will the input sensitivity for the symmetric XLR input be the same as for the analogue RCA input of the main board (= 0dbV)?
Do you have an estimation when the expansion board will available?
Uwe
Hi Uwe,
Input level will be adjustable by software/firmware in dB increments. It's going to cope with any input signal, from very small to quite large.
There are also 2 extra channels with analogue gains that can be used to make the main input on Najda also adjustable with a bit of easy tweaking.
The expansion board should be available in less than 2 months.
Nick
Input level will be adjustable by software/firmware in dB increments. It's going to cope with any input signal, from very small to quite large.
There are also 2 extra channels with analogue gains that can be used to make the main input on Najda also adjustable with a bit of easy tweaking.
The expansion board should be available in less than 2 months.
Nick
Hi Nick,
sounds great!
So there is no need for external attenuation any more.
Looking foorward to the expansion board!
Uwe
sounds great!
So there is no need for external attenuation any more.
Looking foorward to the expansion board!
Uwe
Hi everybody,
am proud owner of Najda DSP as of today!
Is there meanwhile an "easy" way to transfer EQ-calculations from REW to Najda?
Thanks for this great product Nick!
Abel
am proud owner of Najda DSP as of today!
Is there meanwhile an "easy" way to transfer EQ-calculations from REW to Najda?
Thanks for this great product Nick!
Abel
Ok, sorry, been a bit too fast with this question!
Since transitioning from miniDSP, been quiet of expecting similar behavior inNUC as well. After loading a file and seeing no parameters appearing in the right panel, I concluded the file has not been accepted, or is not compatible.
What I'm struggling with now though, is the exclusivity between custom biquads and manually setting EQ's. What I've done till now, is to let REW calculate the EQ's, import into miniDSP plugin and add additional EQ settings for further corrections were needed.
What would be a good workflow with NUC? This is what comes to my mind:
1. Measure each driver and export to file
2. Import into NUC's Graph tab
3. Add EQ settings, delays, crossover points
4. Check with the Summing function of the Graph tab for desired result
Would be glad to hear about how others have refined their workflow!
Abel
Since transitioning from miniDSP, been quiet of expecting similar behavior inNUC as well. After loading a file and seeing no parameters appearing in the right panel, I concluded the file has not been accepted, or is not compatible.
What I'm struggling with now though, is the exclusivity between custom biquads and manually setting EQ's. What I've done till now, is to let REW calculate the EQ's, import into miniDSP plugin and add additional EQ settings for further corrections were needed.
What would be a good workflow with NUC? This is what comes to my mind:
1. Measure each driver and export to file
2. Import into NUC's Graph tab
3. Add EQ settings, delays, crossover points
4. Check with the Summing function of the Graph tab for desired result
Would be glad to hear about how others have refined their workflow!
Abel
Hmm... back in the days of beta testing I did something like this. Let me see if I can find my notes...
Hi Abel,
I haven't ever used REW so I don't know what sort of file they're outputting.
If they output just raw biquad coefficients, then the file can be loaded straight into NUC.
You won't see any parameters in the right panel because you have supplied raw coefficients. It's not straightforward to make the reverse conversion from raw coefficients back into parameters such as Q and F, mostly because you're likely to use filter sections that cannot be expressed in those terms (Linkwitz transformer for example).
Regarding the workflow, the one you have detailed in your previous post seems absolutely valid. That's how I would proceed myself.
Best
Nick
I haven't ever used REW so I don't know what sort of file they're outputting.
If they output just raw biquad coefficients, then the file can be loaded straight into NUC.
You won't see any parameters in the right panel because you have supplied raw coefficients. It's not straightforward to make the reverse conversion from raw coefficients back into parameters such as Q and F, mostly because you're likely to use filter sections that cannot be expressed in those terms (Linkwitz transformer for example).
Regarding the workflow, the one you have detailed in your previous post seems absolutely valid. That's how I would proceed myself.
Best
Nick
OK, I've checked my notes. I must admit that I'm a bit rusty, having not used NUC for a few months now.
I, too, have never used REW for this purpose. I used Charlie Laub's Active Crossover Designer spreadsheet. I did a cut-and-paste into a text file and imported that into Najda. I don't want to say more than that for fear of talking nonsense.
I agree that your work flow sounds right. Perhaps this app note I wrote might also be of help, though it is written with NUC's internal filter controls in mind:
Working with design targets in Najda Under Control (NUC)
I, too, have never used REW for this purpose. I used Charlie Laub's Active Crossover Designer spreadsheet. I did a cut-and-paste into a text file and imported that into Najda. I don't want to say more than that for fear of talking nonsense.
I agree that your work flow sounds right. Perhaps this app note I wrote might also be of help, though it is written with NUC's internal filter controls in mind:
Working with design targets in Najda Under Control (NUC)
🙂
Hey a first black one out there!
(I first wondered: How did Abel manage that on the LCD? 😉 )
Hey a first black one out there!
(I first wondered: How did Abel manage that on the LCD? 😉 )
Hi Sigi,
it's a cheap 4€ LCD from here:
LCD Display 480x240 Graphical 3 in one Blue White RED Artikel im zyscom Shop bei eBay!
Abel
it's a cheap 4€ LCD from here:
LCD Display 480x240 Graphical 3 in one Blue White RED Artikel im zyscom Shop bei eBay!
Abel
Hi Nick,
the info in the following link might be useful to get some OLEDs working. Have a look if you've got a moment … especially post 4&5 in the link ...
Raspberry Pi • View topic - OLED 16x2 HD44780 woes
Abel
the info in the following link might be useful to get some OLEDs working. Have a look if you've got a moment … especially post 4&5 in the link ...
Raspberry Pi • View topic - OLED 16x2 HD44780 woes
Abel
i suspect "real" hd44780 compliant vfds are also picky about startup sequence and timing (i.e need strict compliance)
Nice find, Abel! This is the optimum solution: the same piece of code for both types of display.
Thanks Abel, I'll have an extensive look at this as soon as I can.
As far as I can tell, the so-called drop-in replacements for HD44780 are actually not directly compatible.
I've tested a OLED display with a Winstar driver: nothing at all on the display. I suspected the display was DOA, I'll have another look.
The VFD mentioned above displays garbage. The good thing is that the garbage is correlated to what I'm doing with the Najda - i.e. the garbage changes each time I press a button. Better than nothing huh? 😉
I have good hope to make all these displays compatible in a near future - stay tuned 🙂
As far as I can tell, the so-called drop-in replacements for HD44780 are actually not directly compatible.
I've tested a OLED display with a Winstar driver: nothing at all on the display. I suspected the display was DOA, I'll have another look.
The VFD mentioned above displays garbage. The good thing is that the garbage is correlated to what I'm doing with the Najda - i.e. the garbage changes each time I press a button. Better than nothing huh? 😉
I have good hope to make all these displays compatible in a near future - stay tuned 🙂
Any of you fine lads tried any forms of discrete opamps on the najda dsp board?
Wondering if worthwhile!
Wondering if worthwhile!