File Size

It's a bit tricky to answer that question definitively. It's a bit like saying 'how much food is too much?' We all have different appetites, we all last ate at different times, etc.And in the online learning content world we all have different end user PC specs, different bandwidths and so on.The overall file size of a published Lectora title is somewhat irrelevant though. What matters is the amount of bandwidth-hungry content on each page.As a rule of thumb we try to avoid any image or media-rich content more than about 250KB per screen. But a series of 10 consecutive Lectora screens, each with 200KB of content (for example) will be OK because each screen (HTML page) is being served to the user separately.A real no-no would be a single screen with 1MB for example.However, in Lectora you can easily 'cheat'. A 60-second audio file would probably be very large on one screen, but if you break it up into 10 or 15 second chunks and put each chunk sequentially on a new Lectora page you can give the user the impression that they are listening to a single file when in fact they are served with several pages, each playing the next piece of the narrative.A simple Lectora action saying 'Go to Next Page' (timed to happen as soon as the small audio chunk has finished) will do the job.k9tiger, I think you're really going to struggle with a 4MB Captivate movie playing on anyone's PC! Any way you can take a similar approach and chunk it up as separate movies in Captivate, then string them together in Lectora using the above technique?I work for a company in the UK that has a national network of branches, so bandwidth is always our enemy. We use this sort of technique a lot.Hope that helps.Edited By: montague on 2008-4-9 10:22:21