Wave Copilot - A WAV file utility for production sound (Mac, Windows & Linux)

[Matt Nantel]

15 hours ago, RsmithSound said:

Just downloaded the trial. I'm having good luck with it so far. I think there is some room for quality-of-life improvements to the playback page, though these would not necessarily be as pressing as some other suggestions:

As it stands, the playhead behaves in an "insertion follows playback" style, where the playhead stops where playback stops. I would like to see a toggle to set the playhead to start from the same position every time.

It would be nice to navigate with the keyboard, perhaps with the J/K/L keys, or the arrow keys, or brackets.

It would be nice to have different solo mode options. The solo buttons all latch now. I would like an "X-OR" option where hitting solo on a new track cancels the solo of the previous track; only one track is in solo at a time. Like the playhead note, this would just be an additional option.

 

I see we can double-click to set faders to unity. Perhaps double-clicking in the pan field should set the panning to center.

I feel the urge to zoom in on a longer recording. Something to consider. And if you implemented that, I would recommend the ability to set a preference for window scrolling behaviors during playback. And maybe a modifier key to scroll left and right. I'd vote for the Shift key. 

These are all just "nice to have" ideas. I'm really loving the core functionality behind this. Great work!

I will work on that for the next release. Thank you for the suggestions.

[callou]

A minor suggestion by using it , the ability to detach the playback window as an option would be great! i realy like the "pro tools like " playback suggestion above too!

by the way:  the auto mixer is a great idea! 

[RsmithSound]

I may have found a small quirk that might be worth looking into, Matt. Double check my work on this one.

 

I am testing some files and using the "Combine Poly" tab to match secondary ISO files recorded in 32 bit float to 24 bit main mix LR files loaded into the main files page. I export the combined files with the poly files converted to 32 bit float. When loading the exported files back into the files page, the new files show as 24 bit in the bit depth field of the recording tab of the metadata despite the successful conversion to 32 bit float. Perhaps the files are retaining that 24 bit metadata from the original poly files? But the files themselves turn out as expected and other software is showing the metadata as 32 bit. When the files are reversed in the combining operation with the 32-bit files treated as the primaries, that metadata field shows 32 bit depth as expected.

If it's some sort of bug, I would just recommend that bit of metadata is updated to avoid any unnecessary confusion. But I could also be overlooking some other reason for this outcome.

 

Thank you!

[Kvark]

Any chance for an iPad version?

I do all my file handling and uploading on the road on an iPad with LTE.

[Matt Nantel]

Just now, Kvark said:

Any chance for an iPad version?

I do all my file handling and uploading on the road on an iPad with LTE.

How do you access your files from your recorder on an ipad? Can you tell me a bit more about your workflow?

2 hours ago, RsmithSound said:

I may have found a small quirk that might be worth looking into, Matt. Double check my work on this one.

 

I am testing some files and using the "Combine Poly" tab to match secondary ISO files recorded in 32 bit float to 24 bit main mix LR files loaded into the main files page. I export the combined files with the poly files converted to 32 bit float. When loading the exported files back into the files page, the new files show as 24 bit in the bit depth field of the recording tab of the metadata despite the successful conversion to 32 bit float. Perhaps the files are retaining that 24 bit metadata from the original poly files? But the files themselves turn out as expected and other software is showing the metadata as 32 bit. When the files are reversed in the combining operation with the 32-bit files treated as the primaries, that metadata field shows 32 bit depth as expected.

If it's some sort of bug, I would just recommend that bit of metadata is updated to avoid any unnecessary confusion. But I could also be overlooking some other reason for this outcome.

 

Thank you!

Hi, 
Thanks for pointing me out this issue. This is a bug in the metadata. It is already fixed and will be part of the next release. This should come out very soon. 

[Kvark]

19 hours ago, Matt Nantel said:

How do you access your files from your recorder on an ipad? Can you tell me a bit more about your workflow?

 

I use the iOS native Files app. It's a dumbed down version of Finder.

 

I mostly copy the isos in through usb-c, directly from my transmitters. I also use a SD card reader when I need to.

 

I put the isos in separate folders in a root folder, and then zip the root folder. Then I upload it through dropbox. All of this works pretty well, but I'm unable to manipulate the files in any meaningful way. Being able to make and/or split polywavs would be awesome. There is no such app currently available for the iPad.

[inspire]

One small thought from a daily user of the software:

I really appreciate all the new features and workflow improvements that have been added recently. It is great to see the application evolving so quickly.

At the same time, one of the things I like most about Wave Copilot is its simplicity, speed, and ease of use. I hope that as new features are added, those qualities remain a priority as well.

In my opinion, the current balance is very good: powerful enough to handle complex workflows, yet simple enough to stay fast and intuitive. Keeping that balance will be one of the keys to the software's long-term success.

[Matt Nantel]

On 6/11/2026 at 4:35 PM, Kvark said:

 

I use the iOS native Files app. It's a dumbed down version of Finder.

 

I mostly copy the isos in through usb-c, directly from my transmitters. I also use a SD card reader when I need to.

 

I put the isos in separate folders in a root folder, and then zip the root folder. Then I upload it through dropbox. All of this works pretty well, but I'm unable to manipulate the files in any meaningful way. Being able to make and/or split polywavs would be awesome. There is no such app currently available for the iPad.

Thank you for outlining your workflow. At this time, I’m not planning to bring Wave Copilot to the iPad. Supporting iPad would require a fundamentally different architecture and likely a near-complete rewrite of the codebase.

 

From the research I’ve done, achieving good performance on iPad when processing files, especially very large ones such as RF64 file, appears to be quite challenging. The limitations around file handling and sustained performance make it difficult to deliver the experience I’d want users to have.

[Matt Nantel]

On 6/10/2026 at 6:46 PM, RsmithSound said:

I may have found a small quirk that might be worth looking into, Matt. Double check my work on this one.

 

I am testing some files and using the "Combine Poly" tab to match secondary ISO files recorded in 32 bit float to 24 bit main mix LR files loaded into the main files page. I export the combined files with the poly files converted to 32 bit float. When loading the exported files back into the files page, the new files show as 24 bit in the bit depth field of the recording tab of the metadata despite the successful conversion to 32 bit float. Perhaps the files are retaining that 24 bit metadata from the original poly files? But the files themselves turn out as expected and other software is showing the metadata as 32 bit. When the files are reversed in the combining operation with the 32-bit files treated as the primaries, that metadata field shows 32 bit depth as expected.

If it's some sort of bug, I would just recommend that bit of metadata is updated to avoid any unnecessary confusion. But I could also be overlooking some other reason for this outcome.

 

Thank you!

The new version 1.0.13 has just been released and a fix for this issue is part of it. 

On 5/30/2026 at 7:13 PM, callou said:

A minor suggestion by using it , the ability to detach the playback window as an option would be great! i realy like the "pro tools like " playback suggestion above too!

by the way:  the auto mixer is a great idea! 

A new version is now available (1.0.13) with the possibility to detach the playback window with other improvement in that same window.

On 5/29/2026 at 9:09 PM, RsmithSound said:

Just downloaded the trial. I'm having good luck with it so far. I think there is some room for quality-of-life improvements to the playback page, though these would not necessarily be as pressing as some other suggestions:

As it stands, the playhead behaves in an "insertion follows playback" style, where the playhead stops where playback stops. I would like to see a toggle to set the playhead to start from the same position every time.

It would be nice to navigate with the keyboard, perhaps with the J/K/L keys, or the arrow keys, or brackets.

It would be nice to have different solo mode options. The solo buttons all latch now. I would like an "X-OR" option where hitting solo on a new track cancels the solo of the previous track; only one track is in solo at a time. Like the playhead note, this would just be an additional option.

 

I see we can double-click to set faders to unity. Perhaps double-clicking in the pan field should set the panning to center.

I feel the urge to zoom in on a longer recording. Something to consider. And if you implemented that, I would recommend the ability to set a preference for window scrolling behaviors during playback. And maybe a modifier key to scroll left and right. I'd vote for the Shift key. 

These are all just "nice to have" ideas. I'm really loving the core functionality behind this. Great work!

Hi, all your suggestions have been implemented in the new version (1.0.13).
 

• Playback mixer : Pan reset: double-clicking the pan slider on any channel strip instantly resets it to center (0). No more manually dragging back to the middle.
• Playback mixer : Exclusive solo: holding Ctrl (Windows/Linux) or Cmd (Mac) while clicking the Solo button on a channel now solos only that channel and unsolos all others. A regular click still toggles solo additively as before.
• Keyboard file navigation: pressing the Left arrow key on the Playback tab loads the previous file and Right loads the next file, following the current sort order. The shortcut is active whenever you are not typing in an input field.
• Return to Start: a new toggle button (↺) in the transport bar lets you pin the playhead to a play-in point. When enabled, pressing Stop or reaching the end of the file returns the playhead to exactly where you pressed Play, not to the beginning of the file. When disabled (default), the playhead stays wherever it stopped.
• J/K/L shuttle and ⏪/⏩ seek buttons: the transport bar now includes Rewind (⏪) and Fast Forward (⏩) buttons, each stepping the playhead by 5 seconds. The J, K, and L keys provide NLE-style shuttle control: J and L seek −5 s / +5 s when stopped; while playing, each L press doubles playback speed (1×, 2×, 4×, 8×) and each J press steps it back down, pausing at 1×; K plays from the current position when stopped, or pauses when playing. Space respects the Return to Start toggle: when off, Space pauses in place; when on, Space acts as Play/Stop and returns to the play-in point. The current shuttle speed is shown as a badge next to the play button.
• Waveform zoom: the waveform now supports horizontal zoom from 1× to 1000×. Use Ctrl+scroll (or trackpad pinch on macOS) to zoom centred on the cursor, or use the ‒ / + buttons in the transport bar. The current zoom level is shown between them. You can also use CTRL/CMD + - or  CTRL/CMD + = to zoom in and out or  CTRL/CMD + 0 to return to x1. When zoomed in, Shift+scroll (or a two-finger horizontal swipe on macOS) pans through the file, and a scrollbar below the timeline ruler lets you jump to any position. The timeline ruler adapts its tick spacing to stay legible at every zoom level. The playhead stays visible at all times. The view follows it automatically during playback and zoom always keeps it on screen. Zoom is fully supported in the detached Playback window.
• Detachable window: the Playback tab can now be popped out into its own floating window. Click the ⇱ icon to the right of the Playback tab label to detach it; the tab disappears from the main bar. File navigation syncs in both directions — loading a file in the main window updates the detached player, and using Previous/Next in the detached window navigates the main file list. The full mixer, transport, and automix controls all work in the detached window. Close the window to reattach.
• Console toggle: a new "Console" bar between the transport controls and the mixer can be clicked to collapse or expand the mixer panel. When collapsed, the waveform zone expands to fill the freed space, useful when working with many-channel files and you want more track height visible. Click the bar again to restore the mixer.

[callou]

i just tried 1,0,13, the detachable playback  make everything goes havoc...gui lagg, audio drops and so forth...tried on may Mac Studio M1 with differents ext drives...

 

edit : Mac studio M1 on Sequoia and same behavior on my M2 macbook Air on Ventura.

[inspire]

I can try and report with the Windows machine on Wednesday morning.

[Matt Nantel]

On 6/14/2026 at 8:53 AM, callou said:

i just tried 1,0,13, the detachable playback  make everything goes havoc...gui lagg, audio drops and so forth...tried on may Mac Studio M1 with differents ext drives...

 

edit : Mac studio M1 on Sequoia and same behavior on my M2 macbook Air on Ventura.

Version 1.0.13 was working well on more performant computers. I did some code optimization. This should now work fine on your M1 and M2 with version 1.0.14. 

[callou]

1 hour ago, Matt Nantel said:

Version 1.0.13 was working well on more performant computers. I did some code optimization. This should now work fine on your M1 and M2 with version 1.0.14. 

Just tried it , the gui still lags a bit when playback is detached, but it is definitly usuable now.

[Matt Nantel]

39 minutes ago, callou said:

Just tried it , the gui still lags a bit when playback is detached, but it is definitly usuable now.

Just for my info, what kind of files are you trying to play (poly, multi-mono, mono). What length, and how many channels? Are you waiting for the waveform to display before playing the files? When the waveform is display, is it still lagging? I did some tests on an intel mac, and I was able to play my files without any issue. Normally it should be fine on M1 and M2 mac as well. I have not issue on and M5. 

[inspire]

Version 1.0.14 – everything looks good from my perspective! But there is one small thing I thought I’d mention:
“Add Files” is there, which is great. But it would also be useful to have a “Close All” option.
Right now I have to close the whole program to achieve that — or is there some other way to do it?

[Matt Nantel]

5 hours ago, inspire said:

Version 1.0.14 – everything looks good from my perspective! But there is one small thing I thought I’d mention:
“Add Files” is there, which is great. But it would also be useful to have a “Close All” option.
Right now I have to close the whole program to achieve that — or is there some other way to do it?

Hi, 

 

To remove all the files at one, you just have to click on the checkbox on the header of the list. That will select all files from the list and than you click on the remove button. On my screenshot the checkbox is just before the "Current Name" Column. 

 

[inspire]

Okay, thanks for that little tip!

[Allen Rowand]

@Matt Nantel Just bought a license, happy to support a responsive developer!

[Kvark]

On 6/13/2026 at 12:55 AM, Matt Nantel said:

Thank you for outlining your workflow. At this time, I’m not planning to bring Wave Copilot to the iPad. Supporting iPad would require a fundamentally different architecture and likely a near-complete rewrite of the codebase.

 

From the research I’ve done, achieving good performance on iPad when processing files, especially very large ones such as RF64 file, appears to be quite challenging. The limitations around file handling and sustained performance make it difficult to deliver the experience I’d want users to have.

 

Thanks for replying. I understand.

 

Have you or anyone tried Wave Copilot on a Macbook Neo? 
How’s the performance there?

[Matt Nantel]

1 hour ago, Kvark said:

 

Thanks for replying. I understand.

 

Have you or anyone tried Wave Copilot on a Macbook Neo? 
How’s the performance there?

I haven’t had the chance to test it on a MacBook Neo, but the app is working fine on older computers running Intel processors, so it should work fine on Neo.

[Kvark]

I don't understand the connection, but ok.

 

”The MacBook Neo does not use an Intel chip; it is powered by Apple Silicon. Specifically, it runs on the A18 Pro chip, which is the same processor found in the iPhone 16 Pro models."

[Matt Nantel]

4 hours ago, Kvark said:

I don't understand the connection, but ok.

 

”The MacBook Neo does not use an Intel chip; it is powered by Apple Silicon. Specifically, it runs on the A18 Pro chip, which is the same processor found in the iPhone 16 Pro models."

You can see some tests here comparing the Mac intel with the Mac Neo. The Mac Neo seems impressive :