Hey, I just committed a branch that allows to load .sub files from the FlipperZero. With my setup it works but shows up a pretty bad signal quality.
Could you check if it works for you?

I just implemented loading but not exporting (at least yet), because URH will drop further information like the frequency directly after loading a sub. Users may not understand why loading and then exporting the same sub file ends up with wrong (i.e. default) signal settings in the file. I am a little bit afraid of (valid) usability complaints...What do you think?

This is great. Let me grab it and test. thank you!!

I have added a rudimentary export feature for .sub files. All parameters are constants and export will only work for .sub-files.

I'm having problems installing the branch manually on my macbook air M1. Seems to be an issue with pyqt5. Going to try on my Linux machine tonight.

Got it working on a different machine and it seems fine. I'm honestly not sure what to expect though. I'm able to have enough scale to see the binary/hex data stream. I checked most of my raw captures and they always show as digital type signal. I'm assuming since this is a raw capture it's always going to be an OOK type of modulation or is that just what I've captured? (I honestly don't really understand this raw format besides assuming its a plot on a graph)What did your signal quality look like? I attached some more samples if you wanted to compare.

I see your point about it dropping configuration. You could either:

1. Try and parse the frequency line on line 3 of the raw sub file when importing and prompt the user for anything else missing when saving.
2. Add an alert that lets the user know when saving no signal settings.
3. Add an alert that lets the user know when importing is has no signal settings.
4. Maybe require enabling this format on start. So users understand it's limitations?

Archive.zip
d

The .sub files contain something like a quadrature demodulated signal whereby there are only two possible amplitudes: 0 and 1. Reading the files as demodulated data was actually not a big problem, so I guess, the RX part is alright.

Saving .sub files is a little bit more complicated. Information is missing and as URH is designed to work with real SDRs, the backend does not really make it easy to work with those files.
In theory of shouldn't be a problem to ask the user for missing information but that would require some dirty proprietary hacks that interferes with URHs generic approach or introduces usability problems.

For a start, an export of demodulated signals to .sub is available - works more or less (you have to edit the file for frequencies != 433M and so on)

Probably the best solution would be to implement a plugin similar to the Yardstick plugin (which should even use the same internal hardware...) to save arbitrary files as .sub-file in the Generator-Tab. This, however, is a lot of work if all the Flipper settings should be supported. I am not sure, if it is worth it to implement it right now because a rudimentary export support is already there.

Plugin isn't a bad idea, or just leave it as a branch for now to see how flipper evolves. I originally asked flipper to create a tool to export raw captures as something more flexible for other tools and they declined.

I really like the idea of a plugin though. One of the biggest problems iIface trying to investigate different signals is so no unifying tool unless you're an expert with GNURadio. So adding more to UHR plugins and providing documentation on creating your own would make this feature optional and also easier for someone like me to tinker with.