.iba, 3D, Apple, computer, file folders, gaming, iBooks Author, interactive elements, interactive textbooks, ipad, iTunes Producer, Mac, operating system, OS X Lion, scratch disk, technology, textbook revision, textbooks
At the end of Part #2, I had put out a request for feedback from anyone who had used the ‘Save a Version’ function in iBooks. I am sharing Herman Mittelholzer’s reply as I think it has some crucial information. I follow it up with my reply.
That was an interesting story, but I have come across another issue with iBooks Author that Apple has not as yet responded to. Has anyone else experienced it. Rather than repeating the whole story here, I will instead copy bellow the text of an email I sent to Apple, to which I am awaiting a reply.
It concerns disappearing disk space, that remains permanently lost and requires reinitialising of the hard drive see to get it back!
— I’m following up on two emails I recently sent, with regard to Save a Version facility on iBooks Author.
My issue was that I was permanently losing storage space on my scratch disk every time iBooks Author carried out an auto-save function. This became critical on two occasions when, having stated with 50GB on my main disk, I received a warning that I was running low. I checked and discovered that I had only 1.8GB remaining. Where the other 48GB’s had gone was anybody’s guess.
I had upgraded from OSX 10.6 to 10.7 Lion in order specifically to use iBooks Author for a new project, and thought that perhaps there may have been some clash with software already on the disk. Since I had, by then, no option I backed all my files up, reinitialised the main drive and ran a clean install of OSX Lion. I checked for updates and brought the newly installed system up to date.
I resumed working on my iBooks Author document, this time making a careful note of the disk space at start and at finish. After reinitialising I had 157.74GB a space available, and after working with IBA for about 2 hours, I rechecked to find that the available space had reduced to 141.12GB. The IBA file I was working with was graphic content rich, resulting in the IBA source file totalling 320+GB, so I ran a further experiment. I made a few minor changes and resaved the file 4 times, then checked on the amount of disk space remaining. I discovered that just over another 1GB had disappeared.
My conclusion is that your Version Save facility is saving a complete copy of the file on every auto-save, and since the accumulated saved file seems to be ‘hidden’ it is not possible to delete and regain the disk space. In the case of small text based ebooks this may not have been noticed, but in the case of large content rich publications it can become a serious problem in a very short space of time.
Have you noticed this yourself, and if so is there a workaround I can use to reclaim the lost space, or can I disable to auto-save. —-
If I ever get a reply or a solution I will post it here! Alternatively, has anyone else had this same problem and found a solution that doesn’t require a completely erasing and reinitialising of the hard drive.
I am using IBA on a Macbook Pro 2.4GH laptop. Other than this pretty in annoying issue, IBA is a nice little software package.
For starters, thank you for the detailed post. I also use the Pro 2.4GHz and I too like you have upgraded to Lion just to use the iBooks Author. As I had stated in my first post, I did not save my work using ‘Save a Version’ facility. When I initially started the project I did save it once using the ‘Save a Version’ facility and deleted it after I made a few more modifications to the original. And I didn’t take note of the space used/lost.
However, after the whole issue of the disappearing source file, I made two more mock files, saved them, then saved them using ‘Save a Version’ etc. My testing didn’t quite shed light on the issue I was having as I had not published these mock-books, therefore the source files were still intact.
And then suddenly I had a pop-up saying it was out of disk space which was absurd ’cause I had not downloaded any new programs or loaded any new software – I had just been working on the dang iBA. It was only after reading your post did I realize what had happened. While my initial book was huge, the mock files had nothing in them, and even then it choked! So I can only imagine what it must be when you’re working with big files.
So now the question is:
Does it save a fresh copy
1) Everytime you hit ‘save’
2) Everytime it autosaves
3) Or only with the ‘Save A Version’ facility?
So now it looks like there is no way to hang on to a source file – it either gets gobbled up by iTunes Producer or save it and let it gobble up disk space. If you do get a response or figure out how to get back the lost disk space, please do share. And I hope u figure out!
Me no likey iBooks Author!!!