Question
Captivate 2 and Paths to FLV Files
When providing locations of FLV files to be viewed in my
Captivate 2.0 projects everything works fine, but only so long as I
provide Captivate 2.0 with the "absolute address" to a local copy
of the FLV file I am using. If I try to enter a relative path, to
that same file, rather than the absolute path to the FLV file, and
then ONLY if that absolute path points to a file that is on my PC
harddrive, Captivate 2.0 returns a message saying: "File does not
exist. Please select a valid path for a flash video file"
Let me hasten to add that I am very familiar with Captivate 1.0, and other Macromedia web production tools, such as Flash 8 Professional. I also understand the differences between "Progressive Downloads", and "Streaming", regarding the use of FLV files.
All my FLV files were previously created for use in other projects created with programs like Dreamweaver, Camtasia, as well as Flash Pro 8. All my FLV files were created using either Sorenson Spark or the Flash 8 Video Exporter. In each case, my FLV files load and play just fine, whether I provide the SWF container/controller file with the "absolute path" or the even "relative path" to the FLV file; whether it is local on my PC or already on my internet server. In every case, the FLV files and the SWF files work together just fine, so long as each is available to the other at runtime.
But for some reason, with Captivate 2.0, when I play FLV files (using the Progressive Download option), Captivate 2.0 will not even recognize the existence of my FLV video files, unless I provide a full absolute path to the FLV files, and only so long as these exist my PC's harddrive. Relative addressing is not allowed, even if the FLV files are in the very same folder as the Captivate 2.0's saved project file and published SWF file.
While this may be fine for beta testing projects, or for producing Captivate presentations to be run only from a CD, when I want move my finished Captivate 2.0 FLV projects up to my internet file server, I fully expect to be allowed to provide Captivate with either the full internet address (absolute address) to the FLV files, or use a relative address to FLV files in the Captivate project's own online folder.
Captivate 2.0 will simply not accept "relative paths" to a FLV files. Even when these FLV files are still located on my harddrive, in the same folder as the saved Captivate project .CP file, and the produced.SWF output file. Captivate 2.0 also will not accept an "absolute path" to FLV files I already have already placed online, even when I provide the absolute internet address to these files (ie, http://myserver.com/video1.flv)
I use both relative and absolute addressing with my other web production programs from Macromedia. So, what are the possible issues here? Is this a bug in Captivate 2.0? Am I not entering the relative address correctly? What is the correct form for specifying a valid "relative path" to a local FLV video file, within Captivate 2.0 ?
By the way, if I enter a "relative paht" and ignore the error warning messages, saved the Captivate 2.0 Project, then export it out to Flash Pro 8. my Captivate 2.0 project, using either absolute or relative pathing, either local file or internet files, the Captivate 2.0 project, produced from Flash 8, works just fine.
So, what gives? Why would Captivate 2.0 refuse to accept "relative paths" to FLV files, located on my own PC, even if the FLV video file is the same folder as the Captivate 2.0 project files?
Is there a trick here? What is the secret?
So far I love the changes in Captivate 2.0 from 1.0 for desktop captures, especially since Captivate 2.0 interfaces so well with FLASH 8. But the ability to address and play FLV files online, using either relative or absolute addresses, is an absolute must.
Right now, I am using the trial version of Captivate 2.0, just to see how it has been improved since version 1.0
If this 'relative paths' to external FLV issue, cannot be resolved, then I will just stick to programs like Camtasia for my desktop capture projects. (By the way, Camtasia DOES produce produce projects in FLash 8 formats, as well.)
Steve
Let me hasten to add that I am very familiar with Captivate 1.0, and other Macromedia web production tools, such as Flash 8 Professional. I also understand the differences between "Progressive Downloads", and "Streaming", regarding the use of FLV files.
All my FLV files were previously created for use in other projects created with programs like Dreamweaver, Camtasia, as well as Flash Pro 8. All my FLV files were created using either Sorenson Spark or the Flash 8 Video Exporter. In each case, my FLV files load and play just fine, whether I provide the SWF container/controller file with the "absolute path" or the even "relative path" to the FLV file; whether it is local on my PC or already on my internet server. In every case, the FLV files and the SWF files work together just fine, so long as each is available to the other at runtime.
But for some reason, with Captivate 2.0, when I play FLV files (using the Progressive Download option), Captivate 2.0 will not even recognize the existence of my FLV video files, unless I provide a full absolute path to the FLV files, and only so long as these exist my PC's harddrive. Relative addressing is not allowed, even if the FLV files are in the very same folder as the Captivate 2.0's saved project file and published SWF file.
While this may be fine for beta testing projects, or for producing Captivate presentations to be run only from a CD, when I want move my finished Captivate 2.0 FLV projects up to my internet file server, I fully expect to be allowed to provide Captivate with either the full internet address (absolute address) to the FLV files, or use a relative address to FLV files in the Captivate project's own online folder.
Captivate 2.0 will simply not accept "relative paths" to a FLV files. Even when these FLV files are still located on my harddrive, in the same folder as the saved Captivate project .CP file, and the produced.SWF output file. Captivate 2.0 also will not accept an "absolute path" to FLV files I already have already placed online, even when I provide the absolute internet address to these files (ie, http://myserver.com/video1.flv)
I use both relative and absolute addressing with my other web production programs from Macromedia. So, what are the possible issues here? Is this a bug in Captivate 2.0? Am I not entering the relative address correctly? What is the correct form for specifying a valid "relative path" to a local FLV video file, within Captivate 2.0 ?
By the way, if I enter a "relative paht" and ignore the error warning messages, saved the Captivate 2.0 Project, then export it out to Flash Pro 8. my Captivate 2.0 project, using either absolute or relative pathing, either local file or internet files, the Captivate 2.0 project, produced from Flash 8, works just fine.
So, what gives? Why would Captivate 2.0 refuse to accept "relative paths" to FLV files, located on my own PC, even if the FLV video file is the same folder as the Captivate 2.0 project files?
Is there a trick here? What is the secret?
So far I love the changes in Captivate 2.0 from 1.0 for desktop captures, especially since Captivate 2.0 interfaces so well with FLASH 8. But the ability to address and play FLV files online, using either relative or absolute addresses, is an absolute must.
Right now, I am using the trial version of Captivate 2.0, just to see how it has been improved since version 1.0
If this 'relative paths' to external FLV issue, cannot be resolved, then I will just stick to programs like Camtasia for my desktop capture projects. (By the way, Camtasia DOES produce produce projects in FLash 8 formats, as well.)
Steve
AdChoices