ClipFlair Forums. Create discussion topics and get answers
I've noticed that when i have (lets say) a combined captions and audio state that i want to save, form the (caprions)options view, the audio file(s) are not saved (no audio file not appear in .zip created).
PS: Worked fine though when saved only audio
audio is not currently saved in CaptionsGrid state (in the .clipflair.zip) file. Will add this most probably this afternoon (will store WAV files in the .clipflair.zip)
one can now save audio (as uncompressed WAV) for each revoicing entry with the Save button shown at the respective grid row
also note that import/export from/to TTS and SRT standard formats with the buttons available on the captionsgrid toolbar obviously don't save audio since no standard format that I know of supports storing captions with audio
Now CaptionGrid saves/load (revoicing) audio data for captions inside its .clipflair.zip file at /Audio/ subfolder (an Activity Container Component saves a .clipflair.zip for each one of its components inside its own .clipflair.zip file [this also covers nested - at any nesting depth - Activities case])
Note that due to some internal property renaming (from CaptionAudioVisible to AudioVisible), after loading state saved from previous versions, the audio column will get hidden and you need to flip over the captiongrid and check "Audio Visible" to show it
Also note that there is a related bug that needs to be fixed I think (need more testing there to verify it does always occur), where after closing (say when loading some saved state from a .clipflair.zip file) the Media player and CaptionGrid components at an Activity, it keeps them alive in the background I think (can try closing a CaptionsGrid after you add some revoicing and see if as video is playing you here the revoicing audio still play at the respective times).
I just checked in an ativity I've created and the audio file in the 'zip file' lasts 2 seconds, when it should last at least '30'.
Another thing about the last bug you mention, it still keeps the previous components of the activity alive after saving, and I think this is something that should not happen to avoid confusion.