Yeah, definitely depends on use case. Few extra bits (that you lose on very simple frontend that doesn't have that many input levels to choose from) is nice for audio stuff, and all in one package makes some tasks much easier vs cobbling together same setup from separate hardware.
I could see a lot of use out of it in setting a test jigs, as you can both generate and receive signal while having some digital IO to control DUT/the testing jig.
If I was doing audio stuff only and had to choose I'd probably pick this over a scope then just make a jig with a bunch of sockets common to audio stuff.
But for more generic stuff, eh, scope gonna give you soo much more.
Comments
More breadth though, don't think you could really call a winner without saying 'for what'.
Yeah, definitely depends on use case. Few extra bits (that you lose on very simple frontend that doesn't have that many input levels to choose from) is nice for audio stuff, and all in one package makes some tasks much easier vs cobbling together same setup from separate hardware.
I could see a lot of use out of it in setting a test jigs, as you can both generate and receive signal while having some digital IO to control DUT/the testing jig.
If I was doing audio stuff only and had to choose I'd probably pick this over a scope then just make a jig with a bunch of sockets common to audio stuff.
But for more generic stuff, eh, scope gonna give you soo much more.