@Christoph-Hart Tested it, works perfectly here!
![](/assets/uploads/profile/2353-profileavatar-1715283263968.jpeg)
CyberGen
@CyberGen
I only know that I know nothing.
Best posts made by CyberGen
-
RE: Filter Display bug... is it fixed yet
-
RE: Wavetable Index at 100% Kills Sound
@CyberGen New findings update: Even though changing the slices setting had initially yielded positive results, it was not solving the problem 100% of the time for me. After much trial and error I found a better fix by going into the sample editor window and moving the sample end just a few cycles short from the very end. This has been giving me consistent wavetable all the way to the end.
Hope this helps. Cheers.
-
RE: Engine.saveUserPreset() no confirm dialog
@aaronventure Oh, I see now.
"CONFIRM_PRESET_OVERWRITE=0" no semicolon at the end.
It works now.
Thank You. -
RE: Look and Feel question.
@aaronventure trace is more for like properties, I mean something like (see below) but instead of this customized code, the original or default look and feel code. It would be so useful as a starting point reference.
// ALERT WINDOW laf.registerFunction("drawAlertWindow", function(g, obj) { Console.print(trace(obj)); var a = obj.area; var mA = [a[3]*0.01, a[3]*0.01, a[2]*0.99, a[3]*0.99]; g.setColour(Colours.darkgrey); g.drawRect(mA, 1); });
-
RE: HISE performance slowing down when using SVG project?
@d-healey Is pretty straight forward, below an example.
David, thank you again.
I will change all my paths to stings, its going to take me a minute. I'll let you how it goes.
Cheers!
// GLARE 1 g.beginLayer(0); g.gaussianBlur(a[3]*0.04); g.setColour(Colours.withAlpha(Colours.white, 0.9)); glarePath.loadFromData(glarePathData); g.fillPath(glarePath, glareArea); g.endLayer();
-
QWERTY Keyboard Octave - setKeyPressBaseOctave - Feature Request
Hello,
I'm moving this from a general question into a feature request.
Kindly requesting a way to change the base octave triggered by the QWERTY keyboard into HISE. This would be very useful for when you don't have a midi keyboard at hand and need to input notes directly from the computer-keyboard. "Z" and "X" are a very popular choice for + and - one octave. I've also seen apps that use the keyboard numbers for direct octave jump.
Below the original topic.
Re: Computer Keyboard OctaveThank you.
-
Latch mode for the Hardcoded Arpeggiator.
I would like to propose the addition of a "Latch Mode" to the HISE Arpeggiator. This feature would provide users with a unique creative tool, distinct from the existing Hold Mode, to expand their musical possibilities.
Description:
Arpeggiator Latch Mode, although similar to the existing Hold Mode in some aspects, offers a distinct functionality that adds a layer of versatility to HISE's arpeggiator.One unique aspect of Arpeggiator Latch Mode is that it automatically resets the arpeggio note pattern when the user presses a new set of keys after having released all keys. This behavior ensures that the arpeggio starts fresh with each new chord/note input, allowing for seamless transitions between chords and arpeggio patterns.
Some Benefits:
Enhanced creative possibilities with a unique approach to arpeggio sustain.
Clear differentiation between Hold Mode and Arpeggiator Latch Mode, catering to various musical needs.
A versatile tool for live performance and studio production across genres.I kindly request the consideration of this feature addition, recognizing its potential to diversify the HISE experience for users across the musical spectrum.
Thank you.
-
RE: Gain AHDSR Monophonic not working?
@ulrik In monophonic mode, the envelope responds to one note at a time, typically retriggering the attack phase, as opposed to polyphonic mode where each note gets its own independent envelope.
-
ULTRA-CLEAN OSCILLATORS
Hello Friends,
For a while now, I've been scripting a wavetable synth with HISE. Although I've been struggling along for a crazy-long time with it, I'm now getting close to something resembling a complete pro soft synth, with just about all the features I set out to include in it.
One thing still doesn't feel right yet: the quality of the wavetable sound. I don't have an artifact problem, but at times the sound can feel a bit broken up and not as sharp as I was hoping it would be, especially with the filter peak cranked. To understand this issue a bit more, I went to the Xfer Records page to look at Serum's features. Right away, I was hit with "ULTRA-CLEAN OSCILLATORS," the heading in one of the paragraphs. (Copied Below)
They claim Serum features advanced math that makes things sound better than basically any other wavetable synth on the market. It made me wonder how much of it is already built into the HISE wavetable synth and how much needed to be programmed in. Also, how much is just a marketing plan with no real advantage on HISE's wavetable synth.
Since I'm not a math nor coding expert, I come to you cracks for guidance. Please read Serum's description of their OSCs. Let me know if HISE already delivers this level of performance and I just need to do better with my wavetables, or if there is anything I can do (coding) that would bring the quality and sharpness of the sound to the highest possible level.
Thank you.
ULTRA-CLEAN OSCILLATORS
Playback of wavetables requires digital resampling to play different frequencies. Without considerable care and a whole lot of number crunching, this process will create audible artifacts. Artifacts mean that you are (perhaps unknowingly) crowding your mix with unwanted tones / frequencies. Many popular wavetable synthesizers are astonishingly bad at suppressing artifacts - even on a high-quality setting some create artifacts as high as -36 dB to -60 dB (level difference between fundamental on artifacts) which is well audible, and furthermore often dampening the highest wanted audible frequencies in the process, to try and suppress this unwanted sound. In Serum, the native-mode (default) playback of oscillators operates with an ultra high-precision resampling, yielding an astonishingly inaudible signal-to-noise (for instance, -150 dB on a sawtooth played at 1 Khz at 44100)! This requires a lot of calculations, so Serumβs oscillator playback has been aggressively optimized using SSE2 instructions to allow for this high-quality playback without taxing your CPU any more than the typical (decent quality) soft synth already does. Load up Serum and we think youβll be able to notice both what you hear (solid high frequencies, extending flat all the way up to the limits of hearing) as well as what you donβt hear (no unwanted mud or aliasing gibberish- just good, clean sound). -
RE: Filter Display bug... is it fixed yet
@d-healey I'm using the one marked as "sorry guys" Mar 18. Which was the one that solved the bug that started this topic.
Latest posts made by CyberGen
-
RE: QWERTY Keyboard Octave - setKeyPressBaseOctave - Feature Request
@ustk I believe it's Synth.noteOff() that's deprecated. If you use it, the console throws a message to use noteOffByEventId. Anway, I only used playNote hoping somehow it wouldn't require a noteOff callback as I was testing @aaronventure suggestion.
I think it would be better to just add the octave control to the existing qwerty keyboard function.
-
RE: QWERTY Keyboard Octave - setKeyPressBaseOctave - Feature Request
@aaronventure uhm.. sorta got it to work like this:
const var key = "a"; const var qwertyOctave = 0; Content.setKeyPressCallback(key, function(key) { if (key == "a") { Synth.playNote(60 + (qwertyOctave * 12), 100); } });
Now how do I get the note to stop playing? what is the onNoteOf version of the keyPressCallback?
-
RE: QWERTY Keyboard Octave - setKeyPressBaseOctave - Feature Request
@aaronventure hmm...
ignorance mostly.
Do you mean with: setConsumedKeyPresses(); and setKeyPressCallback(function(obj) ?
I hadn't thought about it.... would this override it's default functionality? -
RE: Engine.saveUserPreset() no confirm dialog
@aaronventure Oh, I see now.
"CONFIRM_PRESET_OVERWRITE=0" no semicolon at the end.
It works now.
Thank You. -
RE: Engine.saveUserPreset() no confirm dialog
@aaronventure tried it on the extra definitions tab but:
"invalid token at start of a preprocessor expression"
Compilation Failed. -
RE: Engine.saveUserPreset() no confirm dialog
@ustk Sorry for reviving this ancient topic.
I removed the confirmation message successfully in HISE, but it still shows up in the compiled binary.
How do I remove it for the compiled version?
I export directly from HISE.
-
RE: Script Editor - Script Tabs - how to show in relative path?
@d-healey oh my... ok, when I have the time I'll try to smoke it out. Thank you.
-
RE: Script Editor - Script Tabs - how to show in relative path?
@d-healey works normally on a local temp project. But I have used icloud for my projects for a very long time and never had this issue before. Something else has changed.
-
RE: Script Editor - Script Tabs - how to show in relative path?
@d-healey Yes, in the script folder. Recent version but not latest.