Synthesizer
-
Wow very nice I’d like to add your friend code so I can see how this works.
My friend code: SW-8581-8532-8511
senas8 -
@sys64738 when I was looking into sound, I just remembered this extraordinary Synthesizer project. It would be lovely to see more of your project and enjoy some demo spirit.
-
I am back from the real world of synths, after a year of studying more synthesis. I have submitted this project to the new share feature in Fuze. There is still a bug with the sequencer. I'll fix it if I can if not maybe someone else can.
-
Awesome! Great to have you back
-
Really great news! Looking forward to trying out the synthesizer!
-
@pianofire Thanks guys, break must have improved my brain. Fixed the sequencer bug, improved the step sequencer. Now v1.2 I assume the shared version will always be latest or do I have to re-submit it? Do I post the ID now or wait until it stops saying pending (new to the sharing feature)
-
@sys64738 The ID will stay the same unless you unshare it. The program will be unavailable for download until it has been approved.
-
OK it is approved
-
Thanks Pianofire. The Code is N9FSENNDNR
-
I downloaded it and it looks amazing!
However, there seems to be an issue with the touch input?
When holding down a key, it seems to register multiple inputs very quickly?
Also, pressing A more than once seems to mess up the sequencer timing?
-
@vinicity thanks, there is no ADSR envelopes in Fuze, I believe they are still working on it, so there is no sustain, you can change the length of the basic envelope. I have been fiddling with the touch sensitivity trying to get it to a happy medium of not delaying to much or not rapid fire 60hz repeats when you touch.
I'm am not sure if Fuze has indepth enough touch API to do this better. Yes pressing play sequencer while the sequencer is playing will mess it up. It also occasionally crashes if you press randomize while sequencer is running, and the BPM isn't scaled correctly.
-
It seems the touch ribbon and the leftmost key overlaps...
-
@vinicity maybe by a few pixels? That's easily adjusted, I didn't notice an issue when playing it.
-
In that case, would you ever want to trigger more than once? I think a good solution would be to trigger only when the len(touch()) changes from 0 to 1?.
-
Here is a video showing the synth functions and interacting with real instruments and effects.
-
What a great video! Love it!
-
Have you seen the program that @spikey made?
It is also an interesting approach, and it allows for saving sound patches between sessions...https://fuzearena.com/forum/topic/947/re-use-sounds-from-the-soundfx-generator-with-the-usb-keyboard
-
Wow this is great. Gave it a quick go last night and after seeing your great video I'll be trying again tonight. Well done.
-
To avoid that irritating click sound, maybe you can just loop through the channels for each note played? So that the previous note can fade, while the new one plays?
If it is important that you can only have one note playing at the time, you could start the new note on a new channel, and set the volume of the previous channel to zero... -
@vinicity I have not seen Spikeys project, but he tell me he had a usb keyboard working ( would be great to get a midi keyboard working ). A monophonic synth can only play one note at a time, in the past it was suggested it was the channel clicking and I did stop the channel before playing the new note but it made no difference. I just added code right now to make it rotate through channels each note and it still clicks so unless one of the devs know I don't know. We get this issue in sampling in real music with mismatched zero points in the waveforms. Maybe it's clicks in the audio engine in fuze maybe a dev can answer the issue. I know it does it one some "patches" and not others and only if you re press a note in about the first second, even if the note plays for several seconds, after that first second even on a troublesome patch it does not click.
Maybe the ADSR engine update will fix it.
