PPTA file corrupting my audio and video
Over the years, we’ve had a bizarre issue with Articulate Studio (first with 09, and now with 13), and I wondered if anybody else was having the same issue. Every so often, we would lose all of the media from a project (audio and/or video). For years, we chalked it up to some kind of user error, and so we would go back and re-add all of the lost audio or video. You can imagine how annoying that was, but it happened just infrequently enough that we didn’t investigate the root cause.
When we upgraded to Studio 13 and it kept happening, I opened a ticket with Articulate, and they were able to tell me that under certain circumstances (a few listed below), Articulate will get confused and won’t be able to read in the current PPTA file, which is what houses (among other things) all Articulate media. Instead, Studio renames the PPTA file to [your-file-name]_old.ppta, and then creates a new PPTA file. So, the “solution” is to blow away the newly-created PPTA file, remove the “_old” from the original PPTA file, and the re-launch Articulate.
This is sort of okay, except that Articulate doesn’t tell you when it gets confused, and so you could be working away for hours on something before noticing that your media is gone. At that point, you’re either going to lose all data in the original PPTA file or the newly-created PPTA file.
So the best solution here is for Articulate Studio to not get confused. If that’s not possible (and I concede there may be very good reasons why it gets screwed up), then at the very least, Studio should alert the user that a new PPTA file is being created. If Studio is smart enough to figure out that a new file must be created, the it’s got to be smart enough to alert the user, right?
My understanding is that Studio gets confused most often if it’s working on a file that’s not on the local C drive. This includes networked shares, mapped drives, etc. In my case, I’ve got Studio 13 running on Windows 7 inside VMWare on a Mac, and the actual data files were sitting on the Mac’s file system.
Anybody else have similar issues?