Contact the editorial desk
Reach the right desk the first time. Editorial, privacy and legal enquiries each have a dedicated address, and the form below routes to the editorial desk.
We read every message. Editorial replies usually go out within three business days, though corrections are prioritised over general correspondence. If you are reporting a factual error, include the page address and the specific claim, because that lets us verify and correct faster.
Direct contacts
| Desk | Use for | |
|---|---|---|
| Editorial | [email protected] | corrections, contributions, general enquiries |
| Privacy | [email protected] | data requests and privacy questions |
| Legal | [email protected] | notices, rights and policy matters |
Publisher
Northline Media Engineering LLC operates the portal video-encoding-hub.org. The registered correspondence address is 1420 Harbor Point Drive, Suite 210, Portland, OR 97209, United States. The telephone number is (503) 555-0147, answered during Pacific business hours. Telephone contact is best for scheduling; substantive technical enquiries are easier to handle in writing.
Send a message
The form below does not transmit anything. On submit it takes you to a confirmation page, and your browser sends nothing to us or to anyone else. That is deliberate: we keep the site free of third-party requests and of any server-side collection. To actually reach us, use one of the email addresses above.
What to include in a technical enquiry
Enquiries that arrive with context get useful answers. Tell us the source resolution, frame rate, colour depth and whether the material is interlaced, because those four facts determine most of the decisions that follow. Describe the delivery target as well: a streaming ladder, a broadcast master, an archival copy and a short social cut each tolerate very different quality trade-offs. If you are comparing two encoders, name the presets and the constant-quality value applied on each side, since a comparison between mismatched quality targets measures nothing useful.
Measured numbers help more than impressions. A short table listing average bitrate, peak bitrate, encode time and the resulting file size at each setting is usually enough for us to explain where the bit budget went. Hardware matters too: the same nominal settings behave differently on NVIDIA, Intel and Apple encoders, and several rate-control modes are unavailable on particular silicon generations. Where you can, note whether the encode was CPU-based or hardware-based and which rate-control mode was active.
We answer in writing and keep correspondence focused on method rather than on any particular product. If your question concerns a workflow you cannot share in full, a description of the constraints is enough; we do not need the media itself, and we would rather not receive large attachments. Please also tell us which page of this portal prompted the enquiry, so the answer can reference the assumptions we already published.
Corrections and rights
If you hold rights in material we have described, write to the legal address with the page address and the basis of your claim. We take such notices seriously and respond in writing. We welcome corrections from anyone, including vendors whose products we analyse, provided the correction is supported by reproducible evidence.