Comments (4)
I really dig this; it's hardly any overhead, and would allow at least a version mismatch to be detected in hippo and our standalone player. It can also be trivially skipped by our official player example (and what we ship in intros).
While distributing binary exports of our tunes isn't really a use case we've considered so much, I see no reason why we couldn't do it, especially since we already have this functionality in our StandAlonePlayer.
One thing to note (as we discussed already) is that even with a small header, a player such as hippo would only be able to support songs that are made with the official set of devices we that we ship out-of-the-box. This rules out songs made with WS forks (which I hope are abundant actually; I'd love for people to make their own devices and go nuts) but I think that's a natural tradeoff and something we can happily ignore.
As for whether or not the version should be semver, there probably isn't much value beyond a simple counter that we bump whenever we change the format.
from wavesabre.
I doubt plain semver would make sense for file formats, though. What's does for instance a patch-version mean there?
from wavesabre.
It would only be for matching the tool it was saved with but I guess it's not needed.
from wavesabre.
Similar to the player case, if a demotool wants to integrate with several synths and only wants to look at binary data, it would be useful for it to include such a header. So in that case we'd want a tag + version, i.e. WSBR
+ 4-byte version number, as we described above.
from wavesabre.
Related Issues (20)
- Consider more consistent and precise time handling in converter/song
- Mark deprecated devices as such in their UIs HOT 1
- Properly handle threaded parameter updates
- Consider parameter smoothing solution
- Proposed fixes for the biquad filter and Leveller device HOT 2
- Investigate potential improvements to StateVariableFilter
- Revisit (and likely remove) metaplugin/jbridge setups
- Add new sampler device
- Cover more VS versions when building in CI
- Fix VS 2015 support; add to CI matrix
- Live 10 support
- Live 11 support
- Binary plugin distribution HOT 1
- Proper tutorial(s)
- Make building deprecated code/VSTs opt-in
- Add changelog
- Support VST3 HOT 1
- Dual license MIT and GPLv3 HOT 4
- Investigate including VST3 SDK as a submodule HOT 14
- FL Studio project file conversion broken in FL Studio 20.9 HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wavesabre.