Hey Jeremy - are there any other changes to the PC version with the latest update, or is this just for Mac compatibility? I saw a note about 48khz, but wasn't sure if that was already addressed before. Wondering if I should download again. Thanks again for branching these changes!... works great!
Also, mentioned this in another thread, but here's a web based tool that can be used to change the destination slot for wavetables... in case you share/download other peoples tables and want to target them to different slots.
https://www.presetpatch.com/pro3wavetool
And some free wavetables here:
https://www.presetpatch.com/synth/sequential-pro-3
Hey,
The PC version has the header "fix" (44100 -> 48000) to the exported files. I don't think this actually affects the processing in the Sequential web app (I tested it a few weeks ago and I don't think it made a difference, since 1024 samples is 1024 samples whether at 44100 or 48000). The PC version also has the dependency fix, but there appear to be linkage differences between PC and macOS probably make it irrelevant, beyond the 500kB or so you save from leaving that out.
I did some sniffing around the sysex files and I am very curious to understand the code used to generate the actual wavetable from the audio files. My investigations would indicate that the data is transferred to the Pro 3 as audio, rather than as some spectral description, which is interesting since it might make it possible to format them to behave, well, differently on-instrument (less smoothly, for instance). If you're into that sort of thing. In any case, I haven't gotten very far with that.
Ideally, Sequential would release a C (or Node.JS or whatever) library to build the sysex from the audio data. On one hand, this will preserve and prolong the technology in the event of a end-of-life for the instrument (or heaven forbid, the company!), and would also allow users/3rd party devs to build interfaces to their liking. The web interface is fine, the actual construction of the data is being done using WebAssembly (or ASM.js or whatever), though, so it's not so easy to determine the methodology -- you can decompile the WebAssembly, but the code's not particularly legible. Anyway, maybe they'll share the method with editor developers at some point so that there are more options.
Sorry, got off on a tangent. Downloading again won't kill you, but it won't fix much for PC or Linux users, either.