BETA OS v1.1.5.9 Bug Report Thread

[maxter]

I'm experiencing a bug when attaching an LFO to the VCA -- it causes the oscillators to generate a tone despite no key presses on an initialized patch. Is this a known issue? super annoying.

I don't think it's a bug, as it's modulating the VCA level found in Misc parameters, which is a direct control of the VCA (for drones etc). But you could route Env 3 to control the amount of the LFO that's modulating the VCA level. Or perhaps routing the LFO directly to Envelope 2 amount could work?

[barkatope]

Hello

Apologies if this is the incorrect place to post, I've looked everywhere and I can only see one other mention of my issue very early on in this thread and could not see a fix.
The below user seems to have suffered the same issue where basically the notes played out the sequencer just hold and do not end. It happens when recording in Cubase, leaving one long note and also when just triggering other devices. I'm on 1.1.5.9 USB connected but have tried MIDI and have tried every setting one at a time but cant seem to figure this out?
 
Has anyone else come across this as I can't find a workaround. Thanks.

Don't know if this is a bug or user error - don't *think* it's user error, could be wrong though, just can't figure what it might be. Anyways, I updated my Rev2 desktop to 1.1.14.18 yesterday to try out the poly sequencer MIDI out. It works, but I'm not getting any note off information, all the notes just hang there. I've got a workaround, I have my DAW (Bitwig) set up to force all incoming notes to a fixed length (I'm using 16th notes) and then everything works fine. So it's not freezing up, it's continues to send the correct note information. There's no MIDI incoming to the Rev2, just MIDI out from the Rev2 to my DAW. edit: I'm using DIN, not USB for MIDI. I'm clocking the sequencer with gates/triggers.

[bIG joB heAd]

Don't know if it's related to OS v1.1.5.9 because i have my prophet for only two days but i've noticed that i can't modulate FX param1 when it's on clocked BBD delay (tried with every modulation source available).

[minor7th]

I just tested this in Logic. The Rev2 sequencer does not send note off midi commands. Therefore all recorded notes are stretched to the end of the region. It seems to be a bug. The only workaround I see is to manually shorten the recorded notes in the DAW. Logic has a nifty tool called Midi Transformer.

Hello

Apologies if this is the incorrect place to post, I've looked everywhere and I can only see one other mention of my issue very early on in this thread and could not see a fix.
The below user seems to have suffered the same issue where basically the notes played out the sequencer just hold and do not end. It happens when recording in Cubase, leaving one long note and also when just triggering other devices. I'm on 1.1.5.9 USB connected but have tried MIDI and have tried every setting one at a time but cant seem to figure this out?
 
Has anyone else come across this as I can't find a workaround. Thanks.

[barkatope]

I just tested this in Logic. The Rev2 sequencer does not send note off midi commands. Therefore all recorded notes are stretched to the end of the region. It seems to be a bug. The only workaround I see is to manually shorten the recorded notes in the DAW. Logic has a nifty tool called Midi Transformer.

Hello

Apologies if this is the incorrect place to post, I've looked everywhere and I can only see one other mention of my issue very early on in this thread and could not see a fix.
The below user seems to have suffered the same issue where basically the notes played out the sequencer just hold and do not end. It happens when recording in Cubase, leaving one long note and also when just triggering other devices. I'm on 1.1.5.9 USB connected but have tried MIDI and have tried every setting one at a time but cant seem to figure this out?
 
Has anyone else come across this as I can't find a workaround. Thanks.

Aah Cheers. Thanks for confirming for me, hopefully there will be a fix in the coming updates.

[bax]

@Eric Blair found an issue with the Globals menu described in the following post:

https://forum.sequential.com/index.php/topic,4946.msg49267.html#msg49267

His description:

_______________________________________________

To see if I was going mad I went back and checked.
In the "global" menu.
My rev 2 module goes...
25. 26. 27. 29. 30.
But in the other direction it goes...
30. 29. 26. 25.

So it misses out "27. Save Edit B" in one direction!

I think I may have stumbled across a bug in 1.1.5.9

_______________________________________________

I am seeing the same behaviour as well.  Not anything that isn't able to be worked around, but it is definitely there...

Thanks!
bax

[skipgilles]

This is somewhere between een bug report and a feature request (since I do not no whether the not so useful behavior is intendet like it is):

The shortcut <destination> - <move modwheel> only works once. If there is already one modwheel entry in the mod-matrix, the shortcut does not do anything anymore. It would be natural to have it either 1) create a new mod slot for modwheel (the same behavior as when using the shortcut the first time; this would be my preferred behavior), or 2) jump to the existing modwheel mod slot.