{"id":344,"date":"2026-09-29T20:42:47","date_gmt":"2026-09-29T20:42:47","guid":{"rendered":"https:\/\/fieldlog.net\/blog\/?p=344"},"modified":"2026-10-01T17:58:07","modified_gmt":"2026-10-01T17:58:07","slug":"furtherafield-beta","status":"publish","type":"post","link":"https:\/\/fieldlog.net\/blog\/2026\/09\/furtherafield-beta\/","title":{"rendered":"Help test FurtherAfield: spatial listening for field recordists"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Since I&#8217;ve started field recording, I&#8217;ve had several, uh, discussions, online about what is best to target with recordings, headphones or speakers. A lot of times people default to speakers, at least with conventional microphones. Headphones tend to hang around getting hand-me-downs like a younger sibling, well, unless someone goes out and buys one of those microphones with silicone ears on it, and tags it as *ASMR*<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What if I told you though, there are means of recording, and post-processing that can make a recording sound alllllmost as good on both speakers AND headphones without having to use different mic arrays.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Okay, hopefully with that I have your attention&#8230; The key here is what the industry is currently calling &#8220;spatial audio&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Spatial audio (or historically called things like quadraphonic sound, surround sound, 5.1, 7.1, 3D audio, positional audio, virtual surround, immersive audio<\/strong>)<strong> is sound presented as coming from positions around a listener, rather than simply from left and right speakers.<\/strong> <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For field recordings, it helps preserve the sense of being somewhere. I \/feel\/ that it really helps preserve that sense of place and time in storytelling that I love so much.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Now if you&#8217;re a recordist that really just wants to make the best isolated samples as possible, thank you for reading this far, this is probably about as much will interest you, but you&#8217;re still welcome to fall down this rabbit hole with me.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So, where am I going with all of this&#8230; Well, certain devices like the Zoom H3-VR, or H2essential, or double mid\/side recording rigs, etc etc have made it much much easier\/cheaper to record in spatial audio compatible formats.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">BUT! It&#8217;s a pain in the butt to play it back in a way that can be consumed intuitively for the listener. Even my H2e recordings that I took with 3d video, required an extra dozen steps, and a $15 plugin for me to get the recordings ready to go into Resolve and match to the 360 footage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So, I did what I&#8217;ve done before. I wrote a new app. An app that can open all sorts of spatial audio formats (well it&#8217;s tested with DMS, Ambix, and FUMA so far) and lets the user play back the recordings while being able to change the look angle of listener position. Even better, it <strong>supports the newer headphones with head tracking on both iOS and Android!<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is called <strong>FurtherAfield: Spatial Audio Player<\/strong> and gives immediate life to these style of recordings. Just open the files and play!<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I&#8217;m looking for Android and iPhone beta testers, especially field recordists who can try it with their own recordings. If you record with a Zoom H2essential, work with Ambisonics, or simply want a better way to listen back to a soundscape away from your desk, I&#8217;d love your help.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some more technical details are below, but if you&#8217;re already sold, feel free to <a href=\"#join-the-beta\">jump straight to the beta signup instructions<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Built for listening back in the field<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">FurtherAfield brings source decoding, spatial listening, recording adjustments, and audio export into one mobile workflow. You can check a take while you&#8217;re still at the location, explore a different listening direction, and prepare a version to share or use later.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Open Zoom H2essential MS RAW recordings directly.<\/strong> Select either FRONT_RAW or REAR_RAW and the app looks for its companion in folders you&#8217;ve allowed it to access. It decodes the Double Mid-Side pair during playback, without first converting the recording on a computer. If it can&#8217;t find the companion, you can select it yourself.<\/li>\n\n\n\n<li><strong>Turn through the sound scene.<\/strong> Drag the compass to change your listening direction. First-order Ambisonic recordings also support elevation steering, so you can explore above and below as well as around you. H2essential Double Mid-Side captures a horizontal scene; it doesn&#8217;t acquire height information by being played spatially.<\/li>\n\n\n\n<li><strong>Listen with the headphones you already own.<\/strong> The built-in binaural renderer works with ordinary stereo headphones. Compatible phone and headphone combinations can also use the platform&#8217;s spatial audio and head tracking.<\/li>\n\n\n\n<li><strong>Bring different recordings into the same player.<\/strong> Supported sources include AmbiX and FuMa first-order Ambisonics, stereo, Mid-Side, UHJ, and supported microphone and speaker layouts in WAV files. Untagged files may need you to choose their format and channel layout.<\/li>\n\n\n\n<li><strong>Check and adjust each take.<\/strong> Directional meters help you see activity around the scene. Recenter recording orientation, correct the front direction, adjust gain, and source-channel levels. The app remembers each recording&#8217;s settings and listening position, while queues and saved playlists help you work through a session.<\/li>\n\n\n\n<li><strong>Export what you need next.<\/strong> Export AmbiX first-order Ambisonic WAV, conventional stereo, or binaural stereo for headphone listening. Exports use 24 or 32-bit float audio, and your source files are never modified. (Exporting as binaural stereo will conform the files to 48kHz sampling rate, this is a limitation of the HRTF library I am currently using, but I am working on changing that.)<\/li>\n<\/ul>\n\n\n\n<div class=\"furtherafield-screenshots\" style=\"display:flex;flex-wrap:wrap;gap:20px;justify-content:center;align-items:flex-start\">\n<figure style=\"margin:0;flex:1 1 200px;max-width:260px\"><a href=\"https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/01-listen.png\"><img decoding=\"async\" class=\"wp-image-346\" src=\"https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/01-listen.png\" alt=\"FurtherAfield Android player with horizontal compass, elevation control, and playback controls.\" width=\"1080\" height=\"1920\" loading=\"lazy\" style=\"display:block;width:100%;height:auto\" srcset=\"https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/01-listen.png 1080w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/01-listen-169x300.png 169w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/01-listen-576x1024.png 576w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/01-listen-768x1365.png 768w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/01-listen-864x1536.png 864w\" sizes=\"auto, (max-width: 1080px) 100vw, 1080px\" \/><\/a><figcaption>Explore a recording with the compass and elevation controls.<\/figcaption><\/figure>\n<figure style=\"margin:0;flex:1 1 200px;max-width:260px\"><a href=\"https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/04-settings.png\"><img decoding=\"async\" class=\"wp-image-349\" src=\"https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/04-settings.png\" alt=\"FurtherAfield Android recording settings showing mounting, direction corrections, gain, and channel controls.\" width=\"1080\" height=\"1920\" loading=\"lazy\" style=\"display:block;width:100%;height:auto\" srcset=\"https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/04-settings.png 1080w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/04-settings-169x300.png 169w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/04-settings-576x1024.png 576w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/04-settings-768x1365.png 768w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/04-settings-864x1536.png 864w\" sizes=\"auto, (max-width: 1080px) 100vw, 1080px\" \/><\/a><p><\/p>\n<figcaption>Adjust orientation and levels for each recording.<\/figcaption>\n<\/figure>\n<figure style=\"margin:0;flex:1 1 200px;max-width:260px\"><a href=\"https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/06-export.png\"><img decoding=\"async\" class=\"wp-image-351\" src=\"https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/06-export.png\" alt=\"FurtherAfield Android export dialog offering AmbiX FOA or stereo WAV with optional binaural processing.\" width=\"1080\" height=\"1920\" loading=\"lazy\" style=\"display:block;width:100%;height:auto\" srcset=\"https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/06-export.png 1080w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/06-export-169x300.png 169w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/06-export-576x1024.png 576w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/06-export-768x1365.png 768w, https:\/\/fieldlog.net\/blog\/wp-content\/uploads\/2026\/09\/06-export-864x1536.png 864w\" sizes=\"auto, (max-width: 1080px) 100vw, 1080px\" \/><\/a><p><\/p>\n<figcaption>Export AmbiX, stereo, or binaural audio.<\/figcaption>\n<\/figure>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\"><small>Android beta screenshots. Tap an image to view it full size.<\/small><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a field recordist, the useful combination is being able to open a spatial take, check its orientation, listen from different directions, and make an export without assembling a desktop decoding session first. There is no automatic loudness normalization or limiter: you keep control of gain, with peak and clipping information to help you judge it. Can go from the field to Resolve ready in about 3 clicks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>This is a beta.<\/strong> Head tracking depends on the phone, operating system, headphones, and system settings. Android and iOS control their own tracking; FurtherAfield falls back to its binaural renderer when spatial output isn&#8217;t available. Testing across more real devices (and hearing how convincing the spatial image sounds to different listeners) is an important part of this beta.<\/p>\n\n\n\n<h2 id=\"join-the-beta\" class=\"wp-block-heading\">Join the Android beta<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Note: make sure you use the <strong>same Google account<\/strong> for the Google Group, the testing opt-in page, and Google Play on your phone.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Join the testing group.<\/strong> Open the <a href=\"https:\/\/groups.google.com\/g\/furtherafield\">FurtherAfield Google Group<\/a> and sign in. Choose <strong>Join group<\/strong>. The group&#8217;s address is <strong>furtherafield@googlegroups.com<\/strong>.<\/li>\n\n\n\n<li><strong>Opt in as a tester.<\/strong> Once you&#8217;re a member, open the <a href=\"https:\/\/play.google.com\/apps\/testing\/net.fieldlog.furtherafield\">FurtherAfield testing opt-in page<\/a> with that same account on your Android device and accept the invitation to become a tester. Joining the group and opting in to the test are separate steps.<\/li>\n\n\n\n<li><strong>Install from Google Play.<\/strong> Open <a href=\"https:\/\/play.google.com\/store\/apps\/details?id=net.fieldlog.furtherafield\">FurtherAfield on Google Play<\/a> on your Android phone and choose <strong>Install<\/strong> (or <strong>Update<\/strong> if you already have it). Use this direct link; a closed beta may not appear in Play Store search.<\/li>\n\n\n\n<li><strong>Keep the beta up to date.<\/strong> Check Google Play for updates during testing so you&#8217;re trying the latest available build.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If Google Play says the app isn&#8217;t available, first check the account shown in the Play Store and browser, confirm your group membership, and revisit the opt-in page. New test releases and changes can take several hours to become available. If you&#8217;re still stuck, let me know what message you see and which device you&#8217;re using.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Join the iPhone beta<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Apple beta uses TestFlight.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Install Apple&#8217;s TestFlight app.<\/strong> On your iPhone, get <a href=\"https:\/\/apps.apple.com\/app\/testflight\/id899247664\">TestFlight from the App Store<\/a> and open it to complete its setup.<\/li>\n\n\n\n<li><strong>Open the invitation on your iPhone.<\/strong> Follow the <a href=\"https:\/\/testflight.apple.com\/join\/6yd8HrsZ\">FurtherAfield TestFlight invitation<\/a>. If prompted, choose to view the beta in TestFlight.<\/li>\n\n\n\n<li><strong>Accept and install.<\/strong> Follow the invitation prompts, then tap <strong>Install<\/strong> beside FurtherAfield. TestFlight will show the current device and OS requirements and whether a build is available.<\/li>\n\n\n\n<li><strong>Check for new builds.<\/strong> Enable automatic updates in TestFlight if you wish, or open it to install updates manually. If an invitation is full or a build has expired, let me know.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Head tracking: which devices should work?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Head tracking lets you turn toward (or away from&#8230;) a sound while the recording stays anchored around you. Ordinary binaural playback gives you a spatial image over stereo headphones; head tracking adds the physical movement of your head to that experience.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Based on the manufacturers&#8217; published compatibility and the platform audio paths FurtherAfield uses, the following are the combinations expected to work in principle.<\/strong> This is a theoretical compatibility guide, researched in September 2026. The short testing note below records what has actually been tried in FurtherAfield.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">iPhone: AirPods and compatible Beats<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">FurtherAfield&#8217;s iPhone build requires <strong>iOS 16 or later<\/strong>. Use an iPhone supported by the build and by your headphones, with current iOS and headphone firmware; newer headphone features may require a newer iOS release.<\/p>\n\n\n\n<div style=\"overflow-x:auto\">\n<div class=\"fl-table-scroll\"><table>\n<thead>\n<tr>\n<th scope=\"col\">Headphones<\/th>\n<th scope=\"col\">Expected operating-system pairing<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>AirPods 3; AirPods 4 (both versions); AirPods 5<\/td>\n<td>Compatible iPhone \/ iOS, using Apple&#8217;s Spatial Audio with Head Tracked selected.<\/td>\n<\/tr>\n<tr>\n<td>AirPods Pro 1, 2, and 3<\/td>\n<td>Compatible iPhone \/ iOS, using Apple&#8217;s Spatial Audio with Head Tracked selected.<\/td>\n<\/tr>\n<tr>\n<td>AirPods Max, including Lightning, USB-C, and Max 2 models<\/td>\n<td>Compatible iPhone \/ iOS. Bluetooth is the straightforward starting point for this beta.<\/td>\n<\/tr>\n<tr>\n<td>Beats Fit Pro; Powerbeats Fit; Powerbeats Pro 2<\/td>\n<td>Compatible iPhone \/ iOS, using Apple&#8217;s dynamic head tracking.<\/td>\n<\/tr>\n<tr>\n<td>Beats Studio Pro; Beats Solo 4; Beats 360<\/td>\n<td>Compatible iPhone \/ iOS, using Apple&#8217;s dynamic head tracking.<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\">These are expected matches because FurtherAfield hands spatial rendering to iOS. AirPods 1 and 2 are not in Apple&#8217;s head-tracking list. Head tracking on the Beats models above should not be assumed to carry over to Android just because they can play Bluetooth audio there. Sources: <a href=\"https:\/\/support.apple.com\/guide\/airpods\/control-spatial-audio-and-head-tracking-dev00eb7e0a3\/web\">Apple&#8217;s AirPods guide<\/a>, <a href=\"https:\/\/support.apple.com\/en-is\/guide\/beats\/dev7db73ea55\/web\">Apple&#8217;s Beats guide<\/a>, <a href=\"https:\/\/www.beatsbydre.com\/in\/products\/compare\">Beats headphone comparison<\/a>, and <a href=\"https:\/\/www.beatsbydre.com\/us\/earbuds\/powerbeats-fit\">Powerbeats Fit specifications<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Android: the phone and headphones must both support the route<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">FurtherAfield&#8217;s platform head-tracking path needs <strong>Android 13 or later<\/strong>, plus a phone that exposes spatial audio and head tracking for the connected headset. It sends multichannel audio to Android, which performs the rendering and tracking. The combinations below are therefore more specific than \u201cany Bluetooth headphones with an Android phone.\u201d<\/p>\n\n\n\n<div style=\"overflow-x:auto\">\n<div class=\"fl-table-scroll\"><table>\n<thead>\n<tr>\n<th scope=\"col\">Headphones<\/th>\n<th scope=\"col\">Phone \/ OS pairing to try<\/th>\n\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Sony LinkBuds Fit, LinkBuds Open, LinkBuds S, original LinkBuds (WF-L900), WF-1000XM5, WH-1000XM5, WH-1000XM6, ULT WEAR<\/td>\n<td>Android 13+ phone supporting Android head tracking with the headset. Xperia XQ-EC72 on Android 16 is our concrete starting point.<\/td>\n\n<\/tr>\n<tr>\n<td>Google Pixel Buds Pro or Pixel Buds Pro 2<\/td>\n<td>Supported Pixel phones on Android 13+: Google&#8217;s explicit phone list includes Pixel 6 \/ 6 Pro, 7 \/ 7 Pro, 8 \/ 8 Pro, 9 \/ 9 Pro \/ 9 Pro XL, Pixel Fold, and Pixel 9 Pro Fold.<\/td>\n\n<\/tr>\n<tr>\n<td>OnePlus Buds Pro 2<\/td>\n<td>OnePlus 11 5G on Android 13+.<\/td>\n\n<\/tr>\n<tr>\n<td>Samsung Galaxy Buds2 Pro, Galaxy Buds3, Galaxy Buds3 Pro<\/td>\n<td>Compatible Samsung Galaxy phone running Android 13+ and the required One UI version. Samsung&#8217;s Buds3 guide specifies One UI 6.1.1 or later.<\/td>\n\n<\/tr>\n<tr>\n<td>Motorola moto buds+ (XT2441-1)<\/td>\n<td>Compatible Motorola phone with Dolby Head Tracking, such as the documented motorola edge 50 pro pairing, on Android 13+.<\/td>\n\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\">Sources: <a href=\"https:\/\/www.sony.co.uk\/electronics\/support\/wireless-headphones-bluetooth-headphones\/linkbuds-s\/articles\/00303494\">Sony&#8217;s supported models<\/a>, <a href=\"https:\/\/support.google.com\/pixelphone\/answer\/12967594?hl=en\">Google&#8217;s Pixel phone list<\/a> and <a href=\"https:\/\/support.google.com\/googlepixelbuds\/answer\/12921041?hl=en\">Pixel Buds requirements<\/a>, <a href=\"https:\/\/www.oneplus.in\/press\/press-release\/new-oneplus-buds-pro-2-unlocks-pure-harmony\">OnePlus 11 \/ Buds Pro 2 compatibility<\/a>, <a href=\"https:\/\/www.samsung.com\/au\/support\/mobile-devices\/activate-360-audio-on-galaxy-buds\/\">Samsung&#8217;s 360 Audio requirements<\/a>, and <a href=\"https:\/\/en-us.support.motorola.com\/app\/answers\/prod_answer_detail\/a_id\/179165\/p\/11065\">Motorola&#8217;s pairing guide<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Setting it up on Android<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Update your phone and headphone firmware, connect the headphones, and complete any manufacturer setup. For supported Sony models, look for <strong>Spatial sound and head tracking<\/strong> in Sony&#8217;s SoundConnect companion app and complete the measurement if offered.<\/li>\n\n\n\n<li>In your phone&#8217;s bluetooth settings for the connected headphones, enable spatial audio and head tracking where available. Menu names vary by phone. On supported Pixels, the Pixel Buds settings provide separate Spatial Audio and Head tracking controls.<\/li>\n\n\n\n<li>In FurtherAfield, enable <strong>Head tracking<\/strong> and start playback. This selects Android&#8217;s spatial-audio output; Android controls the headset tracking. FurtherAfield uses this platform path on <strong>Android 13 or newer<\/strong>, and the phone must expose support for the connected headset. See <a href=\"https:\/\/developer.android.com\/media\/grow\/spatial-audio\">Android&#8217;s spatial-audio requirements<\/a>.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If the controls are missing or the route is unsupported, check <strong>Details<\/strong> for the reported capability or fallback reason. Android 6\u201312 can use the app&#8217;s binaural playback and manual steering, but not this platform head-tracking path.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Setting it up on iPhone<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Connect and wear compatible AirPods or Beats, then enable <strong>Head tracking<\/strong> in FurtherAfield and start playback.<\/li>\n\n\n\n<li>Open Control Center, touch and hold the volume slider, and open the Spatial Audio controls if offered for the current playback.<\/li>\n\n\n\n<li>Choose <strong>Head Tracked<\/strong>. Fixed spatializes the sound without following head movement. iOS controls this setting and may remember it per app.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Sadly, pairing Sony or Pixel headphones with an iPhone does not establish Apple head-tracking compatibility; likewise, pairing AirPods with Android does not establish support for Android&#8217;s tracking path. Ordinary Bluetooth playback and head-tracked spatial playback are separate capabilities.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What to listen for<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Keep the phone still and compare the same passage with tracking off and on. Turn your head slowly left and right: with tracking active, a stationary sound should remain anchored rather than following your nose. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The compass will always show your manual listening direction in the recording; it does not display your measured head position. <strong>Reset direction<\/strong> resets that manual offset, not the operating system&#8217;s tracking reference. Sadly, these two OSes don&#8217;t really give positional feedback to the app generating the sound. So the app cannot display what your head is doing at any given time. The azimuth and elevation controllers stay active though, so you&#8217;re able to change the &#8216;forward&#8217; position of the image anytime.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What I&#8217;d especially like help testing<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>R<strong>eal recordings:<\/strong> file opening, RAW-pair discovery, format selection, large files, and recordings from different recorders.<\/li>\n\n\n\n<li><strong>What you hear:<\/strong> direction, front\/back separation, elevation, head-tracking behavior, distortion, clicks, dropouts, or unexpected changes in level.<\/li>\n\n\n\n<li><strong>Everyday playback:<\/strong> seeking, background playback, lock-screen controls, interruptions, and disconnecting or reconnecting headphones.<\/li>\n\n\n\n<li><strong>The field-recording workflow:<\/strong> recording corrections, saved settings, queues, playlists, and whether exported files work as expected in your usual audio software.<\/li>\n\n\n\n<li><strong>Anything confusing:<\/strong> controls you couldn&#8217;t find, unclear labels, or a task that took more steps than it should.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Help me support more spatial recording setups<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">I&#8217;m also looking for people using different surround and 3D recording rigs. Real files from a wider range of recorders and microphone arrays will help me improve automatic format detection, understand the metadata those devices write, and develop additional decoding and playback techniques.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Zoom H3-VR and other spatial recorders:<\/strong> original recordings to check how formats, channel order, orientation, and other useful information are described in the file metadata.<\/li>\n\n\n\n<li><strong>Double Mid-Side recorded on Sound Devices or other multichannel recorders:<\/strong> examples with the microphone setup and channel assignments documented, to help develop support beyond the Zoom F6 I have now.<\/li>\n\n\n\n<li><strong>Quad arrays, eight spaced omnidirectional microphones, and other layouts:<\/strong> recordings accompanied by a description or sketch of where the microphones were placed, their spacing, and which channel belongs to each microphone. Different arrays need different approaches to spatial playback, and I&#8217;d like to test those approaches against recordings people actually make.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">I would love to make this work with as many potential formats\/scenarios as possible. If you&#8217;d be open to helping I&#8217;d love either sample files, or just test reports and screenshots. Anything helps really, and for android users especially, I need a few more testers before the app is eligible to go into &#8216;production&#8217; on the play store.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>These examples will help guide future support; not every setup listed here is fully supported by the current beta.<\/strong> Even if your files don&#8217;t open or don&#8217;t sound right yet, I&#8217;d like to hear about them. Get in touch with a description of your setup so we can arrange a suitable sample.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Send feedback<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The easiest way to get feedback to me is email, houstin@fieldlog.net, but I&#8217;m also on the field recording slack and <a href=\"https:\/\/discord.gg\/wwdtXTgHbF\">discord group<\/a>s. There&#8217;s also the <a href=\"https:\/\/sh.reddit.com\/r\/fieldlog\/\" data-type=\"link\" data-id=\"https:\/\/sh.reddit.com\/r\/fieldlog\/\">subreddit for fieldlog on reddit<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For playback problems, use <strong>Details \u2192 Copy diagnostics<\/strong> in FurtherAfield and include the result. Mention whether Head tracking was on or off. A short example recording can help if you have permission to share it; there&#8217;s no need to post private recordings.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You don&#8217;t need a specialist test setup. A few listening sessions with your own recordings or files you&#8217;ve collected over the years, and an account of what worked or didn&#8217;t, what it has and what you wish it had, will help make FurtherAfield more useful for people out in the world. Thank you for trying it!<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><small>Installation help: <a href=\"https:\/\/support.google.com\/googleplay\/android-developer\/answer\/9845334?hl=en\">Google Play testing information<\/a> \u00b7 <a href=\"https:\/\/testflight.apple.com\/\">Apple TestFlight instructions<\/a>.<\/small><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Explore spatial field recordings on Android and iPhone. Join the FurtherAfield beta, try your own recordings, and help shape the player with real-world feedback.<\/p>\n","protected":false},"author":1,"featured_media":360,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-344","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-furtherafield"],"_links":{"self":[{"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/posts\/344","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/comments?post=344"}],"version-history":[{"count":10,"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/posts\/344\/revisions"}],"predecessor-version":[{"id":361,"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/posts\/344\/revisions\/361"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/media\/360"}],"wp:attachment":[{"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/media?parent=344"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/categories?post=344"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fieldlog.net\/blog\/wp-json\/wp\/v2\/tags?post=344"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}