Amazing work by all, team. Profound congratulations.
3 Likes
WOW!!! You guys are unbelievable. Thank all of you so much. This takes Rack up another whole level.
3 Likes
did that make it in? I still only see Dark (my default), medium and light. Not sure if contrast on the dark one went higher or not, looks same to me.
All the rest is awesome, and what a boatload of stuff for you to fix. Sure this will be quite bulletproof by the time submission comes aroundā¦l.
I had one scary thing yesterday that I still havenāt been able to replicate or track down (Rosetta apps donāt always leave trace info when stuff goes wrong). What happened was:
I was patching away on my 23 SurgeXT modules in a single patch patch, and all of the sufdden audio dropped hard, cut off like someone pulled the plug from the audio interface type of hard cut. Oddly the UI seemed to sort of function still (so main thread was dead, but UI thread was still sort of working), as I could click buttons but nothing would be happening, all VUs were stuck and unmutable. I quite Rack and noticed it left the dead main thread hanging as a zombie. So I had to kill it. I have never, since 0.5.1 seen this happen. And very disconcerting that not even the system log has as much as a warning or anything to show. Not sure if Surge stuff was even part of issue, but given that patch is all my ususal stuff (used forever and never given issues) and added the Surge stuff, so might well have something to do with that.
If it happens again I will see if I can poke about in the debugger to see if I can track something down. But alas, so far futile.
1 Like
I sometimes like to use the VCV Rack Cmd+Z, and Cmd+Shift+Z for this. I totally agree, itās a great feature being able to A/B different settings, I often think itās such a luxury that you can do it for free in VCV with the undo/redo keyboard shortcut.
1 Like
Hi all!
surge_lfoeg_delaybug.vcv (2.5 KB)
I do see a strange behavior when using the LFO+EG with a delay on the envelope. As soon as I dial in a delay (and be it in the range of ms) no envelope is generated anymore.
Am I doing something wrong?
Man, wow. I saw Omriās video when it came out, and tonight I finally got a chance to sit down and start exploring the new SurgeXT modules. I was reading all the discussions about the FM oscillators, so I just pulled out the FM2 and FM3 and started modulating them. I havenāt had this much fun with non-melodic content in a long time!
Reminds me a bit of something I saw someone else post while reading community messages, about the first month they got into VCV Rack, they hardly slept at all.
I feel like these modules feel a little bit like that. When I was cranking up the oscillator drift on a module I had this moment where I could have sworn I smelled that weird mixture of phenolic and solvents and heated dust motes coming from who knows where.
Just focusing on the VCOs (I used the Twist, FM2, and FM3, and even threw in a Kitchen Sink, I donāt use that one enough either, Squinky) The UI is really nice, the visualization of the waveforms is both informative and adds a lot to the fun.
The multi-matrix modulation is brilliant and the visualization of the modulation range as youāre setting it is super cool.
It really does feel like an early christmas (that strange memory-smell of warm electronics is coming back to me again), and like a major level-up for VCV Rack. Plus a great way for the Serge code to get used by more people, Iāve heard so many great things about it, but never really got to play with it properly.
Thanks so much to all involved working on this, itās really huge! And super fun.
PS to k-chaffin, I think what makes the FM-OP just so charming is that itās a very musical module. That feels a little handwavy, but it just has so many nice sounds easily accessible. I think thatās as good a reason to find oneself often reaching for a specific module as any other, and sometimes one of the best reasons. Sometimes that musicality of an interface is as much about what isnāt available as the things that are. Thatās my feeling about it.
Good night from here to all, thanks for all the hard work from everyone, and the great sounds, my house has been rattling for the past hour as these various oscillators go through different cancellation and combination phases, itās really wonderful.
4 Likes
High contrast is a display color, not a skin - itās an option for all skins.
A user requested a White display colour, to aid accessibility, and thatās mostly what this is (or very light grey in fact) - but we realised that by default, the knob value arcs are the same colour as the the display and if you have a āwhiteā knob value arc and are using the light skin, then it essentially became āwhiteā on āwhiteā and therefore invisible.
Soā¦ if you use the high contrast colour on the light skin, the display colour is āwhiteā but the knob arc colour is black (or very dark grey).
Thatās why we called it āHigh contrastā rather than āWhiteā as that term allows for both black and white. Another option we considered was āGrayscaleā.
4 Likes
āTriggerā using a gate that is longer than delay + attack.
Then voltage level of the envelope only rises during the attack phase - and only when the gate is high.
A trigger pulse is only 1 ms in length. Not enough time for the attack to grow, only when the delay and attack times are very very short (<1ms).
Hereās your patch with an added GATES module.
3 Likes
I should probably reliable those gate and gateenv yeah?
2 Likes
Obviously if you can repro this I would love to look. Thank you!
Ahā¦ okay. Thanks for the clarification.
Iāll relabel the triggers as gates before library!
1 Like
aha! sorry to be somewhat boneheaded 
1 Like
Sorry for bringing this up again.
Unfortunately this doesnāt explain why the (short) trigger is enough when the delay is set to zero.
When the delay is set to zero the short trigger is enough to initiate a full envelope cycle. The weird behavior only occurs when the delay is set to something greater zero.
Itās not a trigger itās a gate. So with delay set to 0, attack set to 1 second, and a .01 second trigger you
Skip delay Initiate 1% of the attack (so rise to 1%) then initiate the release
Does that help?
I had Rack (under Windows) crash sort of like that a couple of weeks ago but I could never determine what may have been the cause. I was just patching away on a patch I have used and modified a lot.
So having delay (and attack) set to zero is something different than having delay/attack set?
Shows a short trigger and the result.
I would understand that the gate has to last for the whole period of the envelope if it wouldnāt work for a (short) trigger when delay and attack are not set. As shown above the the full envelope is generated (not a small percentage!) when only the trigger is used.
Sorry, but I really canāt correlate āitās a gateā with the behavior shown.
What you are seeing there is just a fast attack and long release stage (the part that happens after the gate finishes)
The gate has to last the Delay, Attack, Hold, Decay, and Sustain stages (but not Release).
But in your example above you donāt have any Delay, Attack, Hold, Decay stages (and sustain is a level held while gate is high (which is very short time given you just have a trigger).
Well yes. Having delay and attack set to zero means the gate puts you immediately at the hold phase So the envelope jumps immediately to 1 on any impulse.
Think about ti like this. Itās a gate not a trigger. The gate moves you through phases. If attack and delay are set to 0 then the envelope goes delay (0) ā attack; attack (0) ā hold on the very first impulse. The hold phase is at one. You then immediately release
Note that the HOLD and DECAY are ignored on a trigger when attack and delay are 0.
2 Likes