Rewrite oemer U-Net ConvTranspose pads before packaging.

ONNX Runtime 1.30+ rejects pads [0, 0, -1, -1] on the unet checkpoint. The build now rewrites those nodes to pads [0, 0, 0, 0] and output_padding [1, 1], which keeps the same output size. Version 0.1.1.

README.md

@@ -7,14 +7,14 @@ The usual way to run it is one Linux AppImage. That file contains the window, th
 ## Run the AppImage
 
 ```bash
-chmod +x Recorder-Tab-Converter-0.1.0.AppImage
-./Recorder-Tab-Converter-0.1.0.AppImage
+chmod +x Recorder-Tab-Converter-0.1.1.AppImage
+./Recorder-Tab-Converter-0.1.1.AppImage
 ```
 
 If the file will not start because FUSE is missing:
 
 ```bash
-APPIMAGE_EXTRACT_AND_RUN=1 ./Recorder-Tab-Converter-0.1.0.AppImage
+APPIMAGE_EXTRACT_AND_RUN=1 ./Recorder-Tab-Converter-0.1.1.AppImage
 ```
 
 Open **Twinkle, Twinkle, Little Star** or **Ode to Joy** to see tabs immediately. Or drop a PNG, JPG, or WEBP of a page. The note list under the tab is editable. Fix a bad pitch or duration and the fingerings update. If a photo cannot be read, the app says so and does not invent notes.
@@ -30,9 +30,11 @@ From a checkout, one command:
 That installs Node packages, downloads a relocatable Python plus oemer and its ONNX models, builds the app, and writes:
 
 ```text
-dist/Recorder-Tab-Converter-0.1.0.AppImage
+dist/Recorder-Tab-Converter-0.1.1.AppImage
 ```
 
+The U-Net checkpoint from oemer 0.1.8 has ConvTranspose pads `[0, 0, -1, -1]`. The build rewrites those nodes to pads `[0, 0, 0, 0]` and `output_padding` `[1, 1]` before packaging. That is the same output size, and it is what current ONNX Runtime will load. The rewrite does not change fingerings.
+
 The build needs network access the first time. The AppImage is not committed; keep it under 600MB.
 
 ## Develop in a browser