I'm not sure whether you meaned this funny, but for anyone seriously looking, you can always find those in the first post, second line, open the zip, extract and read FM9 Release Notes.pdf.Where’s the release notes post, who’s slackin
thanksI thought about mentioning that you can find them in the firmware zip file, but for the sake of brevity I didn't mention it.I'm not sure whether you meaned this funny, but for anyone seriously looking, you can always find those in the first post, second line, open the zip, extract and read FM9 Release Notes.pdf.
And yeah, usually some user will paste them here, today that is @lscottkthanks
You 're parsing a windows file reader...
Tahoe 26.01. The syx. files open with FM9-Edit...
Was able to upload the files, just have not heard them yet. Here's what each firmware update file icon looked like, v. 10.0 and this iteration of DynaCab
I'm not sure whether you meaned this funny, but for anyone seriously looking, you can always find those in the first post, second line, open the zip, extract and read FM9 Release Notes.pdf.
And yeah, usually some user will paste them here, today that is @lscottkthanks
I believe it's kind of a "tradition" to post the release notes as a courtesy for those who don't have time to immediately download or are reading on their phones and MUST know the detailed scoop right a way! 

NoRelease notes do not mention anything needs to be done, but I'll ask anyway: For presets that have a Pitch block with a Virtual Capo algo, do we need to do a block reset of any kind?
I would think, that none other than any bug fixes found in beta 2. Not sure which of the fixes listed in the release notes are from beta 2 though.Does anyone know if there are differences between this firmware and V10 b2?
My educated guess is that it's the Tahoe OS. The files were able to be uploaded via the most recent FM9-Edit, and although the syx. files displayed a question mark, nowhere within the syx. link would suggest the files no longer functions with the current OS.This is not a Fractal firmware issue, this is a MacOS Tahoe issue
It is either:
1. the app associated with syx files was moved, deleted, or no longer functions with the current operating system, or
2. There looks to be a change in Tahoe that impacts Mac app icons by forcing them to conform to iOS-style "squircles"
Always something eh?
You can see both the fm9_1_p08 dynacbs and fm9_dsp_rel FM9 firmware update files without the question mark. I'm intrigued now. Is anybody else working with Tahoe 26.0.1 and observing the question marks my computer displayed as well?Nope, I'm on Sequoia 15.6.1 still (I use Pro Tools, so not updating MacOS yet). Must be a Tahoe thing...
View attachment 160241
The files are fine. The OS changed the icon used to displayI'll just need to be patient and verify this on Friday when more time is available. Regards all of my backups also containing the question mark; that might prove hazardous only if v. 10.0 might not work correctly. Meaning, it won't be possible to revert back to 10 beta 2 because each of my backup files also displays a question mark.
*.syx files because it doesn’t know what application “owns” them and is only a cosmetic difference, the contents of the files remains the same, they have not changed and will not be changed by the OS.Thanks for the reassuring words. It may be possible that Tahoe now utilizes a slightly different MIDI reader, or that FAS is no longer an immediately recognized syx. file type. Whatever the case may be, moving forward just means trying to adapt in case the syx. files might not work. But as you've said, that is likely not the case, and the question mark might have only been a visual cosmetic difference, not a functional one.The files are fine. The OS changed the icon used to display*.syxfiles because it doesn’t know what application “owns” them and is only a cosmetic difference, the contents of the files remains the same, they have not changed and will not be changed by the OS.
System-Exclusive files are created by various MIDI apps when talking to their associated hardware. In this case they are created when Fractal-Bot saved either a block, a preset, a bank of presets, or the system and FC and global settings. The content in the files remains is “exclusive to that particular system”, I.e., the hardware, and won’t mean anything to other MIDI devices, again, it’s “exclusive”.
The icon used to display a particular file type is typically provided by the creator of the application. Fractal doesn’t need to include one because many other applications can generate them too, so macOS falls back on the catch-all generic icon.
It’s nothing ominous.