hey thanx,
no panning on my headphones out
when I pan I see visual feedback on the master vu meters in overbridge
but I can’t hear it…hmmm
I’ve found it sometimes works, sometimes doesn’t.
1 Like
try diff headphones just to make sure? sorry dumb advice
1 Like
no thanx really… that is what I thought too :))
thanx
My micro timing seems to have stopped working on 1.10 [assuming I’m not spacing out on something]. Menu looks and acts the same, just no effect. Anyone else have this happen? Tips? … ruling out user error before going further.
With the Make Noise 0coast, i record a sequence in chromatic mode, after when this sequence is read, the notes are 2 octaves transposed
another bug;
the chromatic keyboard notes are without transposition:
C6# D5# F5# G5# A6#
C6 D6 E5 F5 G5 A6 B6
octaves up are ok
Is it an issue with o-coast ?
It probably has limits on the note range
Used dt for more midi today
Definately got some weird encoder sensitivity going on with 1.10. With midi note 2,3,4 .
Genuinely depressing to see new problems like this .( and just for full transparency I do deal with bouts of depression so this may seem a little dramatic ).
Not sure if this fits as a bug, or its just me…
The setting in delay for stereo width, just seems to pan the delay source to the left, or to the right. it doesnt actually “widen” at all?
AFAIK, it works in conjunction with the Ping Pong ‘on’ setting to determine how wide the PP effect is.
Without ping ping pong mode on it will just pan the delay left or right. With ping ping on it will first go to left or right depending on that setting (higher feedback settings will make it more noticeable)
1 Like
Just want to retract what I wrote earlier - upon further use of both Global and Pattern mutes, I have to concur with the idea that they are bugged in some way. Recreating and describing the bug is made harder by the fact that the mutes ‘work’ in a very confusing fashion.
PS. I use mutes in a live jam situation.
1 Like
I’m having an issue with LFO fade. When I turn the fade up, it works at very low levels, fading in the LFO. But beyond a setting of 8, the LFO never kicks on at all. This happens on all wave types and modes, and it happens whether LFO trig is on or off.
When it stops working and I cycle back down through the numbers where it was previously working, the LFO now does not kick on at all. For example, 4 gives me a little fade and LFO works on the way up, but on the way down, 4 does kick the LFO on at all.
When I get all the way back to zero, the LFO kicks on. At that point, increasing fade will have an effect again and LFO works at each level until I get beyond 8.
Is anybody else having this issue?
1 Like
I’ve not tried it but it sounds like you’ve looked into different ways to test , reproduce it .
Did you try turning off/on the Lfo trig parameter both using the interface and parameter lock ?
I think I only used the fade for tremolo type things , it never seemed so obvious when tweaking it , I moved on with other things.
Yeah, I was trying to take a nice sound and slowly fade in some nasty, so that’s why I noticed it. I did figure out how to make it happen.
TLDR: to fade in to a continuous LFO, LFO.T must be on and MODE must be TRG.
The long version:
Part of the problem was me. I realized that FADE works differently than I thought. I thought positive numbers would increase the fade-in, so that’s on me. It took a long time to figure it out though b/c there is definitely some weirdness going on here.
When FADE works and when it does not is not intuitive, and it’s not in the manual.
FRE never fades. Other MODEs fade with LFO.T on but none fade with it off. And then when LFO.T is off, even though FADE doesn’t fade, it does determine whether the LFO is on or off (yes! it works like an on/off switch). That switch behavior only happens in some MODEs, adding to the confusion.
FRE and TRG are affected this way. Others are not, as far as I can tell. And for FRE and TRG, which are affected, the on/off point is not zero. It seems to be in the 20s somewhere. When the switch happens from on to off (or opposite), the change from one state to the other kind of fades in (so maybe that’s why it works this way?). But it’s difficult to tell when that begins. This is why I can’t tell you the exact number where it happens and why I thought it was 8 in my original post.
Man…hopefully I remember all this. It could cause some real confusion for people. It definitely didn’t help me troubleshoot my issue today.
3 Likes
LFO fade is not something I understand so it has been mostly ignored but I agree that the hands on effect of making changes has confusing results, experimentation from me has led to no real understanding of what is going on. The main thing that puzzles me is when I turn the fade in one direction and hear a gradual change and then start turning the encoder the other way there is no audible change untill the centre is met or passed.
I may be wrong, but I understand FADE to be a sort of delay on the start of the LFO, or the opposite… which if in free run mode, there is no “beginning” of the LFO to “fade in” therefore FADE has no effect. If the LFO is set to start, or be triggered, when a note is played, this is when FADE has a function, by either gradually (or quickly) bringing in the LFO, or gradually modulating it out.
3 Likes
Someone mentioned here in this forum that the fade for a free running LFO only occurs at the very beginning after you hit play.
1 Like
makes sense, perhaps the first time you hit play from stop, though a true free run LFO will be going even if the sequencer is stopped.
1 Like
Gotcha. Didn’t realize FRE faded on start, but that makes sense.
I’m with digimatt on the puzzling one-direction fade. I have synths with LFO fade so the concept is not new for me, but the Digitakt implementation sure is, especially as it relates to FRE and TRG with LFO.T off.
In those states, it would make more sense to have no effect. The one time fade as you pass some mystery threshold and subsequent on/off state depending on where FADE is set basically hides a parameter from view.