Syntakt 1.00 : bug reports

True, makes sense. Midi is not my forté. Maybe it would be a good idea to update the DN and DT to channel 14 then for new projects, but I suppose that might confuse people. Anyway, thanks for the response, clearly not a bug and at least I know the extra step to do when making new projects now.

“I found a small issue on the analog tracks. I’ve got a sustained drone”

I got that too today

Ok this one has me stumped…

Edit: When using OB this does not work, however it does work when not in OB.

  1. Default pattern (initialize a new project)
  2. On track 11 add a single trig at the start
  3. Set trig length to infinite, and the trig condition to 1st (just wanted a sustained note)
  4. Hit play, and if it works you should hear a sustained dual VCO tone
  5. Use [FUNC]+[FX] and enable track 11 for the analog FX
  6. Silence

Why?

Is your Track muted?

Nope. I do this on a newly initialized project. Did the steps work for you? Do you hear a sustained note?

If I send a digital track with a sustained note it works fine, and I can adjust the analog filter on the FX track and hear it change. But if I use track 11 it cuts out completely.

Weird, I can’t replicate this :face_with_monocle:. Seems to work for me

1 Like

Can I get a mod/team member/community to comment on this one (my original post that i am replying to in this comment)? It seems like a big deal. I want to know if anyone else is dealing with it or if it’s a problem with my installation.

I can reproduce it consistently, but unfortunately, support can’t recreate it yet. Maybe you could contact them too.

Theres probably another factor involved as well, are you using TRC’s? I have a drone set to ‘1st’ TRC, which is always affected.

I’ll check it when I get home. happened to me when first selecting the machine, no trc’s or any setting set yet. then pulled down all the envelope settings to try take the tail off n no change. eventually stopped hanging after i recorded in some notes with short env.

1 Like

Confirmed I do not see the illustration either on Syntakt. I do see the illustration on Digitakt.

Reaper
Windows 10
OB v2.1.1.2

1 Like

:point_up_2: :joy:

2 Likes

May relate to switching a Track loaded with an ‘open’ AHD to a e.g. DVCO which has an infinite decay default - so the machine switch just kicks the oscs in

If it’s that it has been mentioned by a few and almost certainly discussed internally by now

It’s more a consequence than a bug, but it may be addressed as it can be unexpected/undesirable

1 Like

yea that makes sense. I’ll check it out :+1:

1 Like

thanks for the confirmation. i am in ableton on windows. I am assuming it is affecting everyone and not yet implemented.

Thanks for testing this!

Have you tried it with OB?

I just found that it doesn’t work when in OB, but works normally when not in OB.

(OB = Overbridge, and my audio is coming in from the VST Plugin)

1 Like

Oh you’re right! This doesn’t work in OB but works without OB. Interesting find!

EDIT: scratch that, I got it to work in OB. Let me try to replicate what I did…

EDIT 2: I got it to work by loading up a sound on the track (I just chose HIDDEN KICK), then immediately choose the DUAL VCO machine type again and it works…

1 Like

After playing around a bunch more, following your steps (in Overbridge), if you change the AMP (ADSR) release to INF on track 11 then it works. It defaults to 32.

So I’m not able to think straight on what the expected behavior should be on a LEN = INF AMP ADSR Release < INF to determine if OB is correct and overriding the unit or the unit is correct.

1 Like

Cool - thanks for testing this. It’s definitely weird behavior.

Like you I can get it to work if change the amp to an infinite release.
Why it doesn’t work in OB with a default release of 32 is a mystery.

I also found that you can’t use retrig on the FX track.

For example, I want to play a note with retrig at 48ths for a 1/2 note and want the filter env to ratchet.

You can do this on other tracks, but not on the FX track :frowning:

Since the LFOs on the FX track can tweak the filter, I’m not sure why retrig does not work.

To reproduce:

  1. On a normal track, place a note, and set retrig to a rate of 1/48 and a length of 8 (which is 1/2)
  2. On the filter for the same track set the filter freq to 60, resonance to 40, and the envelope to +10
  3. Play the sequence and you should hear the filter trigged rapidly.
  4. Do the same on the FX track, and it will only trig once.
1 Like

I’ve reported this, it was confirmed

2 Likes