Member Avatar for Actxiom

I have just uploaded my first video .avi to a web site. The Flash 8 encoder is real slick, works relatively well.

The procedure is also relatively simple

Without the video feature a regular .fla file is published and two additional files are created, the .swf file and the .html file.

When adding the video component, the encoder takes a video file and converts it to an .flv file. This has to be sent to the server along with video.swf file that is created and a skin file - .swf (a custom controller).

Just thought I would pass this information along. I am new to this forum and have no idea how much interest there is out there about this stuff.

Dave

  • 3 Contributors
  • 3 Replies
  • 264 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by lunarstudio

Dani AI

Generated

Good to see testing Flash 8’s video workflow — and good points from and . The notes below pick up gaps that often trip people when they move from a single test clip to a production site: codec choice, delivery method, seekability, and quick checks you can run before going live.

Pick the right codec for your audience — quality vs compatibility. On2 VP6 (Flash Player 8+) gives noticeably better quality at lower bitrates; Sorenson Spark remains the fallback for older players. Decide by measuring the Flash Player version share for your visitors and encode accordingly. (Adobe: video format support) (airsdk.dev)

Make FLVs seek-friendly. Many encoders don’t write the full onMetaData/keyframe table needed for reliable scrubbing when delivering over HTTP. If seeking is important, inject metadata (keyframe arrays/cue points) with a tool such as flvtool2 or flvmeta before publishing. Example commands:

flvtool2 -U myvideo.flv
# or
flvmeta -U myvideo.flv

These tools compute and add the onMetaData/keyframe info so the player can jump to the right byte offsets. (manpages.org)

Understand delivery tradeoffs. Progressive download (HTTP) is simplest and economical for on‑demand video; streaming (RTMP / Adobe Media Server or HTTP Dynamic Streaming) is required for live, low‑latency, adaptive or DRM‑protected delivery. Also confirm your web server supports HTTP range requests (byte‑ranges) — players use partial content requests to fetch segments during seeking. (, MDN: Range header) ()

Quick operational checks: run curl -I http://yourserver/video.flv and look for Accept-Ranges: bytes; test seeking in your player after running flvmeta/flvtool2; and spot‑check CPU/network on target client machines. If seeking still fails, re-inject metadata or consider a small server-side pseudo‑streaming module or a streaming server.

Recommended Answers

All 3 Replies

Member Avatar for rus

I agree, Dave. Flash video is very slick in what you can do with it. I've used it on several projects and think it could easily take over as the lead in the "new" streaming video craze.

Member Avatar for Actxiom

That "streaming video craze" has got me all excited.

www.dittomark.com

This is my direction.

Member Avatar for lunarstudio

Yes. It's definitely the format all the high-end professionals are using to deliver. It encodes with the highest compression to quality ratio and the streaming capabilities are second to none.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.