Bug with Video Encoder in 2008

UPDATE- This IS a bug, and Trivantis is aware of it. They "hope to have a fix when the first service pack comes out." So there I was, we bought the new full (enterprise, or developer, or pro, whatever...) version of 2008 with the understanding that we'd be able to take all of our videos in various formats, encode them to FLVs and then go from there. We even went so far as to get a confirmation from support PRIOR to purchasing 2008 that this was do-able.So imagine my dismay when the 1st time I go to use the encoder and it generates a FLV that contains 2 seconds of digital noise and blackness.I got on the phone with support (we paid for the pro-version support too) and walked him through my issue:Insert random .RM movie onto stageGo to Publish projectSelect Compression and make sure video is checked and level is set to Medium. This, I was told will ensure that all videos in the project will get converted to FLVs with "Medium" compression.Publish movieNow, this publishes a course with the video (in its original format). Not good. As I was informed, this was supposed to generate a FLV of all the videos.So now, I go into the course, right-click on the video and select "edit"This opens the handy-dandy "Video Editor" that's part of the super-duper pro/enterprise/developer package.From there, you can select File- Save As... and save the video as a FLV. When you do that, you get an "Encoding" progress bar as the video is supposedly encoded.So now, you have an FLV that you can use, right?Nope.Open the FLV in Lectora, or your favorite FLV player, and all you have is 2 seconds of dial-up modem sounds, and black screen.The support guy on the phone was very nice, professional, and helpful, but said "Yup- that's happening on my end too. We might have to put this in a list of bugs."Does this sound strange to you? Now, I'm no big-wig Lectora programmer, but doesn't it make sense that you would check this (seemingly) obvious process? I can understand that when you get into crazy programming and custom actions/etc. the potential for unknown bugs grows, but this seems just plain silly. It's like developing a WYSIWYG web editor and not testing to see what happens when someone tries to insert a .BMP...Anyhow, I still LOVE Lectora (and I was a huge nay-sayer of getting it in the 1st place) but I hope that this bug turns out to be something minor on my end, and not the program/testing end.I'll keep everyone up-to-date on this, but if anyone else could verify this, that would bee cool too.Thanks,JoeEdited By: CDC_Joe on 2008-3-27 9:3:1

Discussions have been disabled for this post