Baker Steve

Members
  • Content Count

    23
  • Joined

  • Last visited

About Baker Steve

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As with several previous releases, although the latest release of Waveforms for OS X is claimed to work with OS 10.9 (Mavericks), I have no luck: it crashes on launch. The most recent version I have working here is 3.10.2. 3.1.2. falls over on launch with an Exception Type: EXC_BREAKPOINT (SIGTRAP). Can provide dump if helpful.
  2. Ok - I now have an actual Analog 2, so here's more feedback. Despite the above advice, I had some fun (?) getting Waveforms to recognize the device with the Mavericks build you cited on Feb 11. Sometimes I got the message 'No device detected', while at other times (not sure of the circumstances) I got a message telling me to delete the driver, and the relevant window opens in the Finder. I deleted and reinstalled the driver shat was included with the Mavericks release several times. One possible complication is that I have Parallels Desktop running. When a new USB device is connected, Par
  3. This does appear to be stable in OS X 10.9 - thanks for the heads-up. For the driver, does 'restart having the device disconnected' mean 'restart *with* the device disconnected? Steve
  4. I too have experienced instability with Waveforms on an older version of OS X – everything beyond 3.6 crashes here in launch. I see that the new Waveforms 3.9.1 comes with an optional driver ''For OS X 10.13 or earlier version'. Is this intended to fix the instabilities discussed in this thread, or is it for some other purpose? (I'm still on OS X 10.9 for a variety of reasons that have nothing to do with Waveforms.)
  5. I understand. At least WF 3.6.8 works here. At some point soon I will actually get a physical Analog Discovery 2 (the relevant project's been on the back-burner for 18 months), which will allow me to test whether this is anything to do with running WF in demo mode. At present though it's looking as if more recent versions of WF aren't compatible with OS X 10.9 ('Mavericks'). (I'm stuck with Mavericks for reasons of not rocking the boat with more mission-critical stuff, like all my costly Adobe software that runs under an OS X 10.6 virtual machine in Parallels, plus FrameMaker under W
  6. I'm sorry it's taken me a long time to get back to this. WF 3.7.19 also exhibits the same crash on launch behavior here. I've appended the initial section of the crash dump below. It's maybe important to note that I'm only running WF in demo mode. The highest revision that is stable here is 3.6.8. Waveforms 3.7.19 crash dump.rtf
  7. The Digilent website states that Waveforms v 3.7.5 works with OS X 10.9. However, it always crashes on launch here. v 3.6.8 works just fine. Here is the first section of the crash trace... ath: /Applications/WaveForms.app/Contents/MacOS/WaveForms Identifier: com.Digilent.WaveForms Version: ??? Code Type: X86-64 (Native) Parent Process: launchd [202] Responsible: WaveForms [8930] User ID: 501 Date/Time: 2018-05-03 15:33:38.800 +0100 OS Version: Mac OS X 10.9.5 (13F1911) Report Version: 11 Anonymous UUID: 7BFA442D-B897-118F-12D8-40163310AEDA Crashed Thread:
  8. I've got more info. I think at least part of the problem occurs at save-on-quit: when a cmd-Q or File->Quit command is issued, at least one instrument window closes before the context save. That instrument is therefore not saved, and so not re-displayed on open. Steve
  9. If I spot any causative factor that makes the issue repeatable I will let you know. Steve
  10. I ought to add that this problem is intermittent, so not necessarily repeatable. I've not found a set of circumstances that precipitates it. Steve
  11. Is this issue being addressed? I am definitely seeing lost instruments on a context save/restore, and I need to make a purchase decision. It might be specific to my setup: 2013 MacPro/Mavericks (OS X 10.9.5) with a simulated Analog Discovery 2 in Waveforms 2015 v 3.2.6. I appreciate that you are working on Waveforms 2016, but if there is a bug, I don't expect you want to carry it over into the new version. I'm entirely happy to run tests and/or diagnostics here if that would help: I'm excited about the Discovery 2 and am happy to help. I spent half my working life on electronics