Answers.Body: <p>I created the Quick Annotation Module many years ago. It was mostly just an experiment, and mostly just for my own personal use and convenience, and I haven't made any attempt to keep it working or up to date in many years. So I suggest this module be considered as abandonware/unsupported. It's quite likely that this module no longer functions in the latest version of Pamguard due to regressions, bugs, and/or <a href="https://en.wikipedia.org/wiki/Software_rot" rel="nofollow noreferrer">bit rot</a>.</p>
  <p>Having said that, it did seem to work reasonably well for me back in its day. So, one potential solution might be to try using an older version of Pamguard. Sadly, while I did write some documentation, there doesn't seem to be an official/initial/minimum version number for the module. However, there's a note in the module's online help indicating &quot;As of 2018-08-02 only CSV files of the following specific format can be imported...&quot;. So, this suggests that the module was in working shape (at least for me) circa August 2018.</p>
  <p>So, if you really want this functionality, and don't care about recent Pamguard features and bug fixes, then you could try using an older version of Pamguard. For example, BETA version 2.00.14 is dated September 2018. If this version works, and you want to try to get back some more recent features, then you could keep testing newer releases (potentially in 50% time increments between the last working version and last broken version) until you find the most modern version in which it still works.</p>
  <p>Hope this helps.</p>
  <p>Cheers,
  Brian</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-07-18T08:36:46.477Z
Answers.Text: Great, thank you so much for your help Brian, I'll give it a try!
Answers.UserDisplayName: Charlie Hamblin
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-07-13T01:30:50.907Z
Answers.LastActivityDate: 2023-07-13T12:10:56.130Z
Answers.LastEditDate: 2023-07-13T12:10:56.130Z
Answers.UserDisplayName: Brian Miller
Body: <p>I am trying to extract wav. files every time I manually select a signal using the Spectrogram Annotation Module in PAMGuard . The only way I have found to do this automatically is by using the clip generator to create a wav. file every time there is an automatic detection in the whistle and moan detector. It looks like this might have been possible with the quick annotation function as there is a box that can be ticked to export new annotations as wav. files. Any guidance appreciated.</p>
  <p><a href="https://i.sstatic.net/yo9Tv.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/yo9Tv.png" alt="enter image description here" /></a></p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-07-12T14:21:27.567Z
Comments.Text: So what is the problem? does the wav export option not work? If not then this may be an issue for PamGuard Dev. team
Comments.UserDisplayName: WMXZ
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-07-12T15:19:48.767Z
Comments.Text: The option does not appear for me, the screenshot I posted is from the PAMGuard help section, presumably from an older version. I have tried looking on all Spectrogram Annotation Module settings and I'm unable to find wav file export options.
Comments.UserDisplayName: Charlie Hamblin
Tags: <pamguard><spectrogram-annotation><wav>
Title: How do I produce a wav. file every time I manually select a signal using spectrogram annotation?
ThreadText: # How do I produce a wav. file every time I manually select a signal using spectrogram annotation?
  
  (Asked by: username_0 on 2023-07-12)
  
  I am trying to extract wav. files every time I manually select a signal using the Spectrogram Annotation Module in PAMGuard . The only way I have found to do this automatically is by using the clip generator to create a wav. file every time there is an automatic detection in the whistle and moan detector. It looks like this might have been possible with the quick annotation function as there is a box that can be ticked to export new annotations as wav. files. Any guidance appreciated.
  
  [![enter image description here](https://i.sstatic.net/yo9Tv.png)](https://i.sstatic.net/yo9Tv.png)
  
  **Tags:** pamguard, spectrogram-annotation, wav
  
  > **Comments:**
  > **username_1**: So what is the problem? does the wav export option not work? If not then this may be an issue for PamGuard Dev. team  
  > **username_0**: The option does not appear for me, the screenshot I posted is from the PAMGuard help section, presumably from an older version. I have tried looking on all Spectrogram Annotation Module settings and I'm unable to find wav file export options.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2023-07-13. Score: 3
  
  I created the Quick Annotation Module many years ago. It was mostly just an experiment, and mostly just for my own personal use and convenience, and I haven't made any attempt to keep it working or up to date in many years. So I suggest this module be considered as abandonware/unsupported. It's quite likely that this module no longer functions in the latest version of Pamguard due to regressions, bugs, and/or [bit rot](https://en.wikipedia.org/wiki/Software_rot).
  
  Having said that, it did seem to work reasonably well for me back in its day. So, one potential solution might be to try using an older version of Pamguard. Sadly, while I did write some documentation, there doesn't seem to be an official/initial/minimum version number for the module. However, there's a note in the module's online help indicating "As of 2018-08-02 only CSV files of the following specific format can be imported...". So, this suggests that the module was in working shape (at least for me) circa August 2018.
  
  So, if you really want this functionality, and don't care about recent Pamguard features and bug fixes, then you could try using an older version of Pamguard. For example, BETA version 2.00.14 is dated September 2018. If this version works, and you want to try to get back some more recent features, then you could keep testing newer releases (potentially in 50% time increments between the last working version and last broken version) until you find the most modern version in which it still works.
  
  Hope this helps.
  
  Cheers,
  Brian
  
  > **Comments:**
  > **username_0**: Great, thank you so much for your help Brian, I'll give it a try!  
  
  ---
  
  