Use this: "Receive $200 off of an Analog Discovery 2 just by buying one of our FPGA or SoC boards costing over $100!".
Is that supposed to be a link? Automatic on checkout? I didn't see any mention of it in my (admittedly quick) poke around.
This would normally be off-topic by itself, but there is a relevant question that relies on this background. I do have some projects in mind that might use one of those other boards, but I don't know enough yet to pick one:
- Processing at least 1080p30 video (preferably higher, but I'm unsure of what to call "enough" yet) with absolute minimal latency. Thinking maybe 2 pixels' worth of delay maximum, since there's nothing involving the neighbors. (grayscale, color-invert, attenuation, chroma/luma-keying, that sort of thing) Plus some additional signals to control which features to enable at the moment and by how much. The keyer input should be a USB "display", as a PC would see it, and there should also be a USB capture function for the PC to record the final result. The USB connections can afford to be buffered, but the critical path between the dedicated video I/O must be immediate.
- DSP audio, probably fixed at 48kHz with 24-bit converters all around or better, or direct-digital to a set of class-D chip amps or something like that. Total of 6 channels in and 6 channels out physically, plus 8x8 for recording/playback over USB, USB HID for control by a custom PC app, and some GPIO for physical controls and indicators. (potentiometers, encoders, buttons, and LED's) The functions here are a smattering of EQ's, gains, crossover filters, limiting, mixing, and the occasional A/B switch instead of a mixer just to keep the other input out of the way. Like the video processor, this also needs to have absolute minimal latency between the dedicated audio connections - thinking maybe 2 samples max. at 48kHz - but the USB side can afford a good buffer.
Those should be separate devices, not combined, so that a problem with one doesn't take down the other.
I know nothing about FPGA's at the moment, except for the basic theory and one freshman "intro to logic" lab class in college about 10 years ago (I went a slightly different direction), and my proficiency in the "sequential world" is only on 8-bit MCU's, so I'll need to start from almost-scratch and build up to all of this. And because of the tight latency requirements, I suspect that I'll have to write my own code instead of using a 64-sample library or something like that.
The latency requirement isn't completely naive, although it could be a little bit. I'm thinking about completely replacing an actor's vision while in character, and avoiding an audio comb filter through an inch or two (a few cm) of foam, while replacing what doesn't get through the foam's acoustic lowpass. (mic outside, speaker inside, and vice versa for speaking, plus an off-the-shelf radio pack to connect it to a larger sound system) For most applications, including a "normal" USB sound card or live sound reinforcement, 64 samples of latency at 48kHz is probably fine: you'll get more of a difference by moving a mic or speaker, or the listening position, by just 2 feet (less than 1m).
Do you happen to know of a good starter board for that goal (the bullet points, and where I'm starting from), that would work with this deal?
It might not matter yet at this point, but the project itself will probably require all custom PCB's just to fit everything in - dev boards are too bulky for that - so I'd also need to have good documentation of what the chip itself actually needs, and be able to get the chip and its support parts on their own in single quantities...probably a couple of years from now.
BNC board is +$20 or something like that.
The BNC board by itself is $20, and the "Pro" bundle includes it for $20 more than the base unit by itself, plus a set of probes, clips, and wires. So I'm probably looking at the "Pro" bundle.
Although I'm not sure about RPi, the application is not particularity lightweight. Good thing you can download it for free and evaluate. It is even a bit useful as a free tool as it supports audio card as a source for the scope.
Hmm...so it might require a 4 to even be usable at all. That's good to know.
And the audio input would be nice too! I was thinking to use Audacity for that, but a for-real 'scope that uses that input would be MUCH better. It's not a replacement for an actual 'scope probe, but still handy for audio projects.