From the original SynthMaker forum (2004–2014), with its members’ names and dates.
TomC ·
Outsim wrote: - New: the Save Wave component has new format options for 16,24 & 32 bit ints and also 32 bit floats - New: the WaveFile and WaveFileArray components now support 32 bit sample wave files (both float and int)
How cool is THAT?
Thanks a ton for the new features
Tom
trogluddite ·
Yes, this is really cool. Now that we're free of data type limitations we could even start filling mem's with all sorts of other data (not necessarily even audio, I'm thinking hi-res lookup tables for CPU hungry maths functions etc.) - and then bang it all onto hard disk. Many thanks OutSim. 🙂
Tzarls ·
Hey trog....are you sure? I think the data type is still limited to wave files. It´s the resolution of that data that has received some work. Now we can load and save 16, 24 of 32 bit waves. Of course, you can always store your lookup tables in wave files.....
And idea tha comes to my head is that we can now do some kind of encoding (scrambling) to our samples, so we can protect them from simple copying.
trogluddite ·
Tzarls wrote: Hey trog....are you sure? I think the data type is still limited to wave files.
Sure, the file extension must be .wav - but the contents of a .wav is just a big long list of numbers - it isn't a 'sound' until the numbers get read and sent to a soundcard. For example, I have used a mem primitive in the past to store data from controls, for making motion-sequencing. I've also experimented with similar ideas inside a VST host - using an 'audio' effects send/return to get timing data from one plugin to another (making very sure it doesn't come out of my speakers of course!!)
Of course, you'd have to be careful not to load these 'psuedo-wavs' into your media player, that could seriously hurt your ears! There even used to be a bit of freeware that took .bmp and .png files, and changed the file header to look like a .wav - so you could 'hear' your pictures. Sounded bloody awful!!
Tzarls ·
Mmmmm...interesting about using mem for storing motion data. Maybe you can try this as a security measure. For any wave stream that is not sound, try modulating it with a square wave with a frequency = samplerate/2 before saving it to a file. That is, on sample gets multiplied by 1, the next one by -1, the next one by 1 and so on. Obviously, when decoding the data you have to make sure to de-modulate it. But, because of this modulation, if you accidentally play such a file with mediaplayer, it won´t destroy your ears or equipment. In fact, it´ll produce almost no sound. At least I think so.... 😉
infuzion ·
No matter how smart your encryption is, there is always someone who is smarter.
Tzarls ·
Yes, I know that. Not trying to make a Syncrosoft-like protection with SM. Just trying to protect my stuff with something that doesn´t take more than a couple of hours of just-for-fun work. Any more than that is a total waste. Expect maybe for the just-for-more-fun thing. But let´s not get into that debate. What´s great here is that finally, an R&D component got promoted! Now give me a bool2trigger primitive and my 20 pound are yours Outsim! 🙂
trogluddite ·
trogluddite wrote: Sure, the file extension must be .wav
Here's something interesting... The Save Wave primitive always saves the file with .wav extension, even if you choose something different in the file dialogue. However, if you go to the saved file and edit the file extension, you can point the Wave File primitive to the renamed file and it will still load perfectly fine. I now have a file on my desktop with my own .trg extension - it loads into an SM mem, and I can recover all the data perfectly - if you save as 32 bit floats, you can even have values outside the normal -1...1 range, and it's perfectly happy to read it back. Might be possible to use the Shell Exec prim. to do the file renaming automatically, so we could create our own custom file types full of any kind of float data we like - no pretty icon of course, but at least you won't be able to fry your speakers by playing them in Media Player by accident.
infuzion ·
trogluddite wrote: trogluddite wrote: Sure, the file extension must be .wav
The Save Wave primitive always saves the file with .wav extension, even if you choose something different in the file dialogue.
Sounds like a bug report to me!
TheAudiophileDutchman ·
Tzarls wrote: Now give me a bool2trigger primitive and my 20 pound are yours Outsim! 🙂
There you are (sort of) 😉
Tzarls ·
Ah, you must have missed my last posts about this thing.... I was refering to something me and some other guys requested some time ago - bool2true and bool2false primitives, but with poly and mono inputs, in order to get sample accurate triggers.
Mo ·
Tzarls wrote: bool2true and bool2false primitives, but with poly and mono inputs, in order to get sample accurate triggers.
I don't think that green would process at sample-accuracy anyway.
mwvdlee ·
Tzarls wrote: Ah, you must have missed my last posts about this thing.... I was refering to something me and some other guys requested some time ago - bool2true and bool2false primitives, but with poly and mono inputs, in order to get sample accurate triggers.
I don't think there is (or will ever be) such a thing as "Sample accurate" when it comes to the green portion of a schematic.
The 32-bit wavearray will probably come in handy. I don't have 32-bit samples, but my 24-bit samples will probably sound better when not downscaled to 16-bit.
As for wave saving; I sure could use a simple wave editor to replace the complexity of something like Audacity.
infuzion ·
mwvdlee wrote: As for wave saving; I sure could use a simple wave editor to replace the complexity of something like Audacity.
You as a programer should know better; a program almost never stays "simple" unless someone stops working on it & moves on to something else 😉
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker