Having recently had the (dis)pleasure of getting a DS1054Z oscilloscope, I'd confidently say I'd prefer mouse/keyboard-controlled numbers on a multi-gigahertz processor PC, over a waveform-scrolling jog wheel which updates at 3 frames per second with unpredictable acceleration. Though given a processor that isn't slower than trying to run YouTube on a Pentium M, I'd probably prefer a physical knob or dial for continuous parameter control.
I had the pleasure of using a high-end but quite old digital scope recently (it had a 3.5 inch floppy drive for saving data). It's unreal how much nicer it was to use than much newer scopes (some of which were similarly expensive - the nicest one in the office has amazing specs but the interface is absolutely dire). I think it's just another example of the general trend towards lag in user interfaces.
Argh, I have the same 'scope and I know exactly what you're talking about. It's annoying to try to get the horizontal/vertical position over just enough without flinging it an entire screenful over. Not to mention trying to name files with the detent-less intensity/selection knob.
Great hardware for the money, but it sure is a little annoying to use. Don't forget to hack in the options if you haven't already!
I used to save files under the default name and rename on my PC, but got too lazy. I'm up to NewFile9.csv, having suffered from the scope refusing to recognize USB flash drives until I rebooted and lost my saved trace (DSRemote wouldn't connect to my scope over USB or Ethernet, I resorted to using the dreadful Windows UltraScope software to export a CSV) (somehow UltraScope manages to be as slow on a Ryzen 5600X as the DS1054Z software on the decade-old microcontroller), later stopped recognizing my drive mid-save (the progress bar hung indefinitely, the flash drive idle LED turned off) until I replugged the drive and tried saving again, and minutes-long CSV save times and randomly unchecking all but one save channel (I couldn't find good tools to parse .trc and .wfm files into PulseView-readable files).
So I'm not the only one! I thought the flash drive was buggy, but yeah my scope will just randomly start ignoring the flash drive I have in it. It's always after you capture that one-off random event and finally have it on-screen, too.
I haven't had the pleasure of using their desktop software yet. I do know that sigrok/pulseview has support for the DS-series, but aside from running it to make sure it could talk to the scope I haven't used it much. It doesn't look like it does much more than just duplicate the screen of the scope, but it might have more functionality that I am not aware of.
