I'm making vst version of SEQ16 now.Jonathan Shepherd wrote:Thank you Tadashi. A sequencer eh? Is it based on one of your M4L sequencers?
I wanna release it early next year.
I'm making vst version of SEQ16 now.Jonathan Shepherd wrote:Thank you Tadashi. A sequencer eh? Is it based on one of your M4L sequencers?
Great newshyakken wrote:I'm making vst version of SEQ16 now.Jonathan Shepherd wrote:Thank you Tadashi. A sequencer eh? Is it based on one of your M4L sequencers?
I wanna release it early next year.
Ha ! , good to know I'm not the only one with this bug, and it's not just FLStudio, did it look something like this ? :.jon wrote:I ran into a non-critical bug with HY-Mono, the GUI started randomly showing the default JUCE elements and font. Live 9.7/Windows 10, with 6 instances of HY-Mono.
RuediRena wrote:Thanks, Paree.Paree wrote:Strange. I have a spare laptop with Ubuntu studio installed in it. I'll check it when i get time.RuediRena wrote:Oh my!
My in most cases stable running system of Ubuntu 16.04 (32 bit)/Jack/Wine 1.6.2/Reaper 5.311/WineAsio is choking heavily on HY-Mono (32 bit) crashing Reaper every five minutes.![]()
Advice anyone?
Greetings
Ruedi
Some more information on my system as I've been a bit sloppy on my first post:
It is actually also Ubuntu Studio, i.e. I am running a lowlatency kernel and gdiplus is already installed.
Here is what Mono gui showed on the last trial of mine to shape a Kick. Had two duplicated instances running, one phase inverted and both FX windows were opened. Suddenly Reaper crashed, froze and Mono displayed on one of its GUIs (the one I was not working on) the following.
It is the original screenshot. Notice the suddenly blue tinted pots and the blackened rectangle under the VCF Modulation which should be Env2.
Buggy plugin compatibility mode was on on both instances, doesn't make a difference if it is on or off. Mono also crashes Reaper with only one instance. And every time the FX window is open, me changing patches on the fly while transport is active. I am playing around with the synth which is my normal procedure in this stage. Not with Mono![]()
What is going on there?
Let's see if this bugger is to be resolved in the next days as I as well have the time and the motivation to do some HY-Mono audio engineering.

Yeager wrote:Ha ! , good to know I'm not the only one with this bug, and it's not just FLStudio, did it look something like this ? :.jon wrote:I ran into a non-critical bug with HY-Mono, the GUI started randomly showing the default JUCE elements and font. Live 9.7/Windows 10, with 6 instances of HY-Mono.
[img]<span%20class="skimlinks-unlinked">http://www.kvraudio.com/forum/download/ ... 9036</span>[/img]
I can make it look like this on commandsee here :
<span class="skimlinks-unlinked">http://www.kvraudio.com/forum/viewtopic ... 3392</span>
RuediRena wrote:Reposted from the OSC94 thread in the Instruments forum on here:
hyakken, if you still read this thread, do you have any advice for me? Is there sufficient information from my side? Seems, that I am not the only one. I wouldn't mind the blue font, but I mind the Reaper freezes and would dearly participate in the with this interesting plugin of yours.
TIA/Ruedi
RuediRena wrote:Thanks, Paree.Paree wrote:Strange. I have a spare laptop with Ubuntu studio installed in it. I'll check it when i get time.RuediRena wrote:Oh my!
My in most cases stable running system of Ubuntu 16.04 (32 bit)/Jack/Wine 1.6.2/Reaper 5.311/WineAsio is choking heavily on HY-Mono (32 bit) crashing Reaper every five minutes.![]()
Advice anyone?
Greetings
Ruedi
Some more information on my system as I've been a bit sloppy on my first post:
It is actually also Ubuntu Studio, i.e. I am running a lowlatency kernel and gdiplus is already installed.
Here is what Mono gui showed on the last trial of mine to shape a Kick. Had two duplicated instances running, one phase inverted and both FX windows were opened. Suddenly Reaper crashed, froze and Mono displayed on one of its GUIs (the one I was not working on) the following.
It is the original screenshot. Notice the suddenly blue tinted pots and the blackened rectangle under the VCF Modulation which should be Env2.
Buggy plugin compatibility mode was on on both instances, doesn't make a difference if it is on or off. Mono also crashes Reaper with only one instance. And every time the FX window is open, me changing patches on the fly while transport is active. I am playing around with the synth which is my normal procedure in this stage. Not with Mono![]()
What is going on there?
Let's see if this bugger is to be resolved in the next days as I as well have the time and the motivation to do some HY-Mono audio engineering.
[img]<span%20class="skimlinks-unlinked">https://dl.dropboxusercontent.com/u/304 ... .png</span>[/img]
Sorry for late reply..jon wrote:I ran into a non-critical bug with HY-Mono, the GUI started randomly showing the default JUCE elements and font. Live 9.7/Windows 10, with 6 instances of HY-Mono.
This is great news, hyakken. Folks over at OSC will appreciate your effort dearly.hyakken wrote:
Sorry for late reply.
I will update HY-Mono next.
Please wait for while.
Thank you.

About automation issue.Taron wrote:AH, here you are!
Hey hyakken,
OSC should really have a link right to your thread, hehe. Anyway, I hope you don't mind some quick feedback, if you decide to fix HY-Mono a little more. It's a fun little beasty, but has a few mean troubles. I'll just give you a quick list:There are a few mysterious things that I don't understand, such as a loss of association between DAW's automation lane and the chosen parameter on the synth. I don't quite know what's missing in your code that this could happen, but I think, something must be a little out of sorts?! I'd go through all the parameter and host connection to them. This is tricky and annoying stuff to program, I know it already, but it's vital, too!
- The filter envelope having an attack, even if it's a 0. (very unfortunate!)
- The DC offset the filter's resonance creates with a saw wave oscillator. (I sympathize with the coding pains!)
- Retrigger only seems to retrigger Env 1, but should also retrigger Env 2
- MIDI modulation Targets could include LFO depth. Might be easiest to globalize it that way. But what you currently have as VCO1 and 2 should really control their "MODULATION" dial (or amount) to reduce the confusion. Currently it is some sort of supplemental pitch bending and feels a bit accidental.
- Portamento AUTO mode to only have it glide between connected notes.
- LFO modes, if only just a choice between SINE and TRIangle, would really help!
Anyway, I was bitching a bit early on (still am some, sorry), I'm deadly afraid to close my project, not knowing what it will sound like when I open it again, but while I'm doing my track, I'm actually enjoying what comes out of this! That makes me really hope you'll give HY-Mono a good hard look, because it very well deserves it and you'll certainly deserve what will come out of the OSC! It'll be fun, I'm sure!
Thanks for doing what you do!
Thank you for your testing.Taron wrote:Ok, seems like the parameter automation sticks now.
ALSO, seems like you've fixed the Env2 retrigger, which is beautiful!
Now, if you could get the envelopes to have 0 attack, rather than a soft one, it would be great! You could, if you were concerned about a click, make a ramp at some fraction of the frequency of the sound, be it a quarter or so, but they should have the power to pop.
By the way, I really like the look you're going for! I, by the way, also had the funny surprise GUI design change with more than one instance open, hehehe. Funny stuff. That seems to be fixed, too!
...love the scaling ability for sure! Super well done!
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026