Build a listening space around full-scale floorstanding sound and the warmth of walnut veneer.
Passive three-way floorstanding design in Walnut
Three 6.5-inch woofers, dedicated midrange and dome tweeter
Supplied per loudspeaker; a stereo pair uses two units
Manufacturer product photograph · Two F346 loudspeakers shown; each supplied individually.
The product in practice
Features that shape the experience
The F346 is the flagship floorstanding loudspeaker in Revel’s Performa4 family. Its three-way design combines dedicated bass, midrange and high-frequency drivers in a curved walnut cabinet. Start with a stereo pair or make it the front left and right foundation of a carefully matched media-room system.
Dedicated drivers for each range
Three 6.5-inch Micro Ceramic Composite woofers work alongside a 6.5-inch Deep Ceramic Composite midrange and a 1-inch DCC dome tweeter.
A considered soundstage
The seventh-generation Acoustic Lens waveguide is designed to manage high-frequency dispersion and the transition to the midrange across the listening area.
Walnut with thoughtful details
Natural walnut veneer, magnetic grilles and solid aluminium feet create a finished appearance. Dual rear ports make room placement an important part of the setup.
Flexible speaker connections
Dual binding-post sets support single-wire, bi-wire or bi-amp arrangements when matched and connected correctly.
Start with the experience
Where it fits in your day
A dedicated music room
Plan a stereo pair around the main listening seat, room dimensions and the recordings you return to most.
A pair of F346 loudspeakers with a suitable integrated amplifier or separates, your preferred music source and the required speaker cabling.
Streaming stereo
Consider an ARCAM SA35 or SA45 as part of the design. Revel lists these models for its anechoic EQ support; final amplifier choice and setup should suit the room and listening needs.
Performa4 media room
Explore a system with F346 front speakers, a Performa4 C245 centre and a B140 subwoofer. Surround speakers, AV electronics and calibration are specified for the complete room.
Planning examples. Final quantities, accessories, compatibility, availability and installation scope are confirmed in your quotation.
What to confirm before choosing
A stereo system uses two loudspeakers; quantities are confirmed in the proposal. Share your existing amplifier or receiver model so load suitability, connections, placement and system balance can be reviewed.
The photograph shows two loudspeakers with and without a grille. Each F346 is supplied individually; the quotation states the quantity.
Amplifier suitability, rear-port placement, safe cable paths and room layout are reviewed before specification.
Current supply, finish, accessories and service scope are confirmed in your quotation. No stock or delivery commitment is implied.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_session
The number of page views in this session and the current page path
30 minutes
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type
session
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature
