Record Autosave Feature

This read-only archive contains discussions from the Adding Feature forum.
New feature request may be posted to the Adding Feature forum.
Technical support is available via the Help forum.
Gale Andrews
Quality Assurance
Posts: 41761
Joined: Fri Jul 27, 2007 12:02 am
Operating System: Windows 10

Re: Record Autosave Feature

Post by Gale Andrews » Fri Nov 21, 2014 10:25 pm

jackinct wrote:Re Task Scheduler: as a long time Win 7 home user, I made my first attempt this week to use that feature. It was a disaster. The attached image file shows what happens when I attempt to open the 'program'; that popup window is following by two more such windows with other warning statements. I've made an extensive, time consuming search of the issue via Google searches and it is quite evident that many end users are experiencing similar issues (and have been going back to the XP OS) to include those that have gotten the attention of Microsoft tech support whose suggested fixes don't work. I tried some of the MS tech support suggestions, but 'no joy'.
Did you try the first two fixes here which have almost 100 votes between them: http://answers.microsoft.com/en-us/wind ... 7fb80edb56?

Either way, you don't have to use Task Scheduler - examples at http://www.top5freeware.com/windows-task-scheduler. Your main task is creating the script.


Gale
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual

Edgar
Forum Crew
Posts: 2043
Joined: Thu Sep 03, 2009 9:13 pm
Operating System: Windows 10

Re: Record Autosave Feature

Post by Edgar » Sat Nov 22, 2014 12:16 am

Hi Jack!

I sent you a private message…
I placed a zip file in my Dropbox:
https://www.dropbox.com/s/17cw7lz9rj1wj ... 4.zip?dl=0
This is a zip archive which has the documentation for the new features, language localization files (Languages & locale folders) the new executable (ABC.exe) and the appropriate wxWidgets libraries. When you unzip this it should create a folder with the executable, the five libraries, the localization folders and the documentation folder. From your original folder you will also need to bring in copies of the plug-ins, Nyquist & modules folders (none of which are required for automated recording). It should then be ready to run. Technically, it is designed to be run from a terminal or script but if opened by double-clicking on the program icon it will function as a normal version of Audacity with no automatic recording ability. The documentation is quite extensive and should explain everything you need to know about how to use it.
jackinct wrote: Finally, I would think that as a starting point, it would be a safe presumption that the recordings are being made using Audacity's Timer Recorder. The user would initiate an ATTENDED recording session (setting one up), and fill in the Timer Recorder dialog window; at the conclusion of session your script would have to launch, and likely in the context of a scheduled shutdown.
I do not use Audacity's Timer Recorder. The user would either launch this program from a CLI/terminal or script telling it for how long to record and the name (with fully qualified path) under which to save the recording; only the WAV & FLAC formats are recognized as valid for saving. The FLAC save options need to be set up by running the program once before setting up a recording session. This application DOES NOT use the Audacity configuration folder but sets up its own folder in the same location with the name "AudacityABC"; this means you will need to run the program once to set up all of your configuration preferences (input & output devices etc.).

If you have questions or comments don't hesitate to ask!
-Edgar
running Audacity personally customized 2.0.6 daily in a professional audio studio
occasionally using current Audacity alpha for testing and support situations
64-bit Windows Pro 10

jackinct
Posts: 12
Joined: Wed Nov 19, 2014 4:32 pm
Operating System: Please select

Re: Record Autosave Feature

Post by jackinct » Sat Nov 22, 2014 4:13 pm

Gale Andrews wrote: Did you try the first two fixes here which have almost 100 votes between them: http://answers.microsoft.com/en-us/wind ... 7fb80edb56?
Thank you for the suggestion.

I tried your suggestion at answers.micro.... AT LENGTH (multiple attempts) and 'no joy' ; obviously some have gotten Task Scheduler to work, and others not. I share the conclusion in some of the posts that the core problem is that Scheduler is broken, and since end users have been complaining about it directly to MS for quite some time (years), I can only conclude that MS has no intention of putting any resources into fixing the problem. I've run into a similar set of MS's attitude affecting a very large number of its users re not addressing a chronic problem with its Net Framework gear (on another machine); their software engineers speak to the problem in places like answers.micr...but none of them are willing to go on record as saying that the gear is dysfunctional and you're better off re wasted time to simply forget about it.

Jack.
Last edited by jackinct on Fri Apr 24, 2015 4:43 pm, edited 2 times in total.
Reason: Fixed quote tags

Locked