The Official Sequential/DSI Forum

SEQUENTIAL/DSI => Prophet => Prophet Rev2 => Topic started by: extempo on August 07, 2018, 02:26:21 PM

Title: BETA OS v1.1.5.9 Bug Report Thread
Post by: extempo on August 07, 2018, 02:26:21 PM
This thread is for users to discuss potential bugs. Please send any bug reports directly to support (at) sequential (dot) com. Sending bug reports, along with steps for reproducing the bug, directly to our dedicated support channel is the only way to ensure that we receive them.
Title: LFO Bug?
Post by: vanluke on August 07, 2018, 02:32:10 PM
I believe I found a LFO related bug. Possibly it is similar (or the same?) to this one already mentioned (which supposedly was solved): https://forum.davesmithinstruments.com/index.php/topic,2061.0.html

The thing is: in some patches with some notes the LFOs do strange things:

First Example: F4P9 Clavia Mello. Notes B2, C3, B5, C6 (mostly this last one) sound extremely rare and dissonant. If you set off the destination of the 2nd LFO, most of the problem disappears. (However, if you repeatedly play note B2, you'll note that there is still some LFO-thing going around badly but it does not sound so bad as in the beginning). I find this quite sad because this is one of my favourite patches :(

Another example: F2P82 Canadian. Press B2, it sounds broke. Then play B5, it sounds worse.

And a third one, this time citing the author of the post above:
Here is how to recreate the bug:

1. press Transpose Down/Up and Hold button to initialize a program.
2. Set LFO1 destination to Osc1 Freq
3. Set LFO1 Amount to max
4. Set LFO1 Frequency to 58
5. Play the upper last octave of the REV2 keyboard

somewhere in the middle of this octave you'll start to hear the LFO acting strangely... it happens with all the waveshapes, and at any rate setting... at lower rates you can easily hear what is going on... the amount has to be quite high before it starts to break up, and the amount for that will depend on the waveshape you choose, but all of the waveshapes does this.
(...)
In my case, using former configuration, it happens from E3 to G4.

My actual OS version is 1.1.4.9 but I also did that with the 1.1.4.5 and was the same.

Does this happens in your rev2?
Title: Re: LFO Bug?
Post by: Razmo on August 07, 2018, 02:51:34 PM
I still once in a while get a single key that suddenly have a strange pitch glide or wobble (in lack of better words), but it's completely random, and i cannot replicate it... so i do not believe the stabillity of the voices has reached 100% yet... but they did improve it a lot since the initial OS'es...
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: Razmo on August 08, 2018, 12:17:44 AM
When my REV2 is in screen saver mode, and an OS update is started, when the screen comes on, the font is so heavily enlarged that it wraps over on the screen making it look like a bunch of garbage
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: Razmo on August 08, 2018, 01:02:36 AM
When my REV2 (and many others user's) has warmed up for a while, the calibration of the oscillators and filters suddenly slows down and stop... it never pull thru the calibration.
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: Razmo on August 08, 2018, 01:49:04 AM
I've send a support ticket about this one...

After the latest update, it seems that something is wrong with the global Master Finetune... if it's the filters in self oscillating mode or the oscillators that are pitched wrong I cannot say, but I think it's the oscillators since the problem is with the Master Finetune parameter.

After doing the update I noticed that the Master Finetune parameter was suddenly set to -49 in the globals... I did a global reset again to make sure it went away... but now the oscillators are those -49 cents off... it's like it's -49 cents off even when the parameter reads 0... it's like the offset is wrong or something... if i set the parameter back to -49, then the oscillators sound correct.

EDIT: after some tests, it seems that it was certain of my presets that suddenly sounded different... 2-3 programs that utilized the filter in self oscillating mode had the problem... when I checked them, some parameters was set to have this sound, and i was able to correct them... i just do not understand why they sounded alright before this latest 1.1.4.13 OS update...
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: Sagemund on August 09, 2018, 01:45:42 AM
Hello, I'm new on this forum and have the REV2 for half a year now.
Did the latest update because I saw it had an ARP beat sync in the features of the update:
 "Main OS 1.1.4.9
  1. Feature: Arp Beat Sync global'

It does not seem to be there...
Could anyone clear this up for me?
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: latoxine on August 09, 2018, 04:23:59 AM
Hello, I'm new on this forum and have the REV2 for half a year now.
Did the latest update because I saw it had an ARP beat sync in the features of the update:
 "Main OS 1.1.4.9
  1. Feature: Arp Beat Sync global'

It does not seem to be there...
Could anyone clear this up for me?

Hello,

do you mean that you don't see it in the global ? I don't remenber if it's present in this last update, but it was in the previous one...
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: Razmo on August 09, 2018, 04:46:00 AM
Hello, I'm new on this forum and have the REV2 for half a year now.
Did the latest update because I saw it had an ARP beat sync in the features of the update:
 "Main OS 1.1.4.9
  1. Feature: Arp Beat Sync global'

It does not seem to be there...
Could anyone clear this up for me?

I'm on 1.1.4.13, and i have "Arp Beat Sync" in the globals... it's entry .14
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: Sagemund on August 09, 2018, 05:37:13 AM
Hey, thanks for the answer.
But what I see now is that I didn't opload to 1.1.4.9 or 1.1.4.13 but to the previous update 1.1.4.5.

I can't seem to find the update file for 4.9 or 4.13.... :S
If I search for the latest update the only thing I can find is this page:
https://www.davesmithinstruments.com/updating-prophet-rev2-os/

There it says the latest update is 1.1.4.5...

Where can I find the update file for 4.9 or 4.13?

Sorry to have to put this in the "bug-report"
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: Razmo on August 09, 2018, 06:13:56 AM
Hey, thanks for the answer.
But what I see now is that I didn't opload to 1.1.4.9 or 1.1.4.13 but to the previous update 1.1.4.5.

I can't seem to find the update file for 4.9 or 4.13.... :S
If I search for the latest update the only thing I can find is this page:
https://www.davesmithinstruments.com/updating-prophet-rev2-os/

There it says the latest update is 1.1.4.5...

Where can I find the update file for 4.9 or 4.13?

Sorry to have to put this in the "bug-report"

The file is in the sticky thread at the top of this forum... that is the only place you can find beta versions, and they are always published there... what you find in the support area of an instrument on the website is always the last official non-beta release... i believe that is what you have found because that is still 1.1.4.5

go here: https://forum.davesmithinstruments.com/index.php/topic,1531.0.html
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: vanluke on August 12, 2018, 12:46:44 PM
The LFO Bug I mentioned above was solved after updating to 1.1.4.13, erasing calibration and calibrating again.
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: shiihs on August 15, 2018, 03:57:44 AM
It looks like the new OS version breaks alternative tunings. Not the biggest of deals for most users until you, like me, rely on them.

Resetting globals, recalibration, even after erasing calibration, etc, doesn't resolve the problem.

Luckily, it suffices to just downgrade the OS again, and even without recalibration we already get the correct tunings back.
I've contacted support about it, but wanted to spare you the time of finding out for yourself.


Title: DDL Delay Problem
Post by: gernotreininger on August 22, 2018, 11:53:15 PM
Hi. When turning on DDL Delay and turn the timing to quarter dot (clk sync) there is no delay. Can anyone confirm or is it a problem with my rev2. Thank you in advance.
Title: Re: DDL Delay Problem
Post by: maxter on August 23, 2018, 08:55:47 AM
Hi. When turning on DDL Delay and turn the timing to quarter dot (clk sync) there is no delay. Can anyone confirm or is it a problem with my rev2. Thank you in advance.

When this has happened to me, the cause has been that I've previously set the Clock Mode to Slave of some sort. That makes the tempo synced delays not work, as they're waiting for a clock signal to sync to. Press Global and see if this could be the case.
Title: Re: DDL Delay Problem
Post by: gernotreininger on August 23, 2018, 10:12:34 AM
Hi. When turning on DDL Delay and turn the timing to quarter dot (clk sync) there is no delay. Can anyone confirm or is it a problem with my rev2. Thank you in advance.

When this has happened to me, the cause has been that I've previously set the Clock Mode to Slave of some sort. That makes the tempo synced delays not work, as they're waiting for a clock signal to sync to. Press Global and see if this could be the case.
Thank you for your input. My rev 2 is always switched to slave and all the other delay timings work like expected so I don't think it's a midi clock problem....
Title: Re: DDL Delay Problem
Post by: double-u on August 23, 2018, 02:19:49 PM
Hi. When turning on DDL Delay and turn the timing to quarter dot (clk sync) there is no delay. Can anyone confirm or is it a problem with my rev2. Thank you in advance.


I can confirm I'm experiencing the same issue with an initiated patch and only activating the DDL stereo synced as slave set to quarter dot. rest of the timing divisions function flawlessly.
Title: Re: DDL Delay Problem
Post by: gernotreininger on August 23, 2018, 08:56:48 PM
Hi. When turning on DDL Delay and turn the timing to quarter dot (clk sync) there is no delay. Can anyone confirm or is it a problem with my rev2. Thank you in advance.


I can confirm I'm experiencing the same issue with an initiated patch and only activating the DDL stereo synced as slave set to quarter dot. rest of the timing divisions function flawlessly.
Thank you for testing!
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: shiihs on August 24, 2018, 01:36:13 AM
Before I upgrade again, does BETA OS v1.1.4.18 fix the alternative tuning issues? I'm a bit surprised that the changelog doesn't mention anything wrt tuning, even though support assured me the problem was known, being looked at and would be fixed in the new beta version.

Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: Razmo on August 24, 2018, 03:37:15 AM
For DSI:

I see in your changelog of the latest v1.1.4.18, that you fixed something with the LFOs regarding syncing... I think that you somehow introduced a new bug when you messed with this because I now have a program I've made, that sound VERY wrong... it is a program that utilize a keysync'ed and clocked LFO1, to shift (via OSC Mix parameter) between oscillator 1 and 2 (via a triangle LFO)... the LFO is synced to clock and with keysync because it needs to allign perfectly with the gated sequencer... in short, the sequencer is used to shift the pitch upward, and one oscillator's pitch is changed via the gated sequencer, while the LFO is making sure that the other oscillator is the one being heard... a little hard to describe it, but the preset smoothly shifted between the two oscillators, at the same time as the gated sequencer changed their pitches.

That program was smooth before OS v1.1.4.18... with the new beta that smoothness is suddenly gone... I'm unable to figure out what is causing this, but to me it sounds like the divisions have changed.... did you fix something regarding the divisions of the LFO's?
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: Razmo on August 24, 2018, 03:44:18 AM
Addition to my above post:

I have the LFO in question set to 2 steps per cycle in the program.... that worked fine with prior OS'es... I tried changing this with OS v1.1.4.18, and now it has to be set to 4 steps for the program to work the way it did before... this seems illogical, and i believe you must have accidentally changed the divisions of the LFOs somehow...

I'll add that I'm clocking via the internal master clock, I'm not sync'in to MIDI clock in any way.
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: Razmo on August 24, 2018, 03:56:41 AM
One more note: OS v1.1.4.18 is making every program I've made that use the LFOs in clocked mode, not sound the way they did before v1.1.4.18. The division settings has been messed up. This must be a bug.
Title: LFO LEDs strange flashing
Post by: skrohmer on August 24, 2018, 11:18:23 PM
Hi,

I have recently updated to V 1.1.4.13, however did not try several version which came up during the last months. Now I see that the LFO LEDs are flashing in a very strange way. Before I contact the support, can anyone reproduce this? Example:

1. Create Init Patch -> all four LEDs are static on
2. Switch LFO 1 to a different waveform -> LED goes off and stays off
3. Switch LFO 2, 3 or 4 to a different waveform -> LED is flashing quickly
4. Switch all LFOs to waveform Square and activate CLK SYNC for all
5. Select LFO 1 and change FREQUENCY -> LED of LOF 2 is flashing according to the frequency
6. Same happens for LFO 2 and 3 -> LED of LFO 3 and 4 is flashing

Seems to be a wrong assignment, frequency of LFO n affects LED n+1.
Title: Re: LFO LEDs strange flashing
Post by: eagleman on August 25, 2018, 05:17:15 AM
I can verify your example. It's the same with the resent 1.1.4.18 update.
Title: Re: LFO LEDs strange flashing
Post by: skrohmer on August 25, 2018, 05:24:20 AM
Thanks, support has been informed.
Title: Re: LFO LEDs strange flashing
Post by: Razmo on August 26, 2018, 01:00:39 AM
Yup... I have the same response... most certainly a bug there. Seems like the LFO's are a bit buggy... latest beta also introduced problems with the division settings.
Title: Clocked LFO division settings bug...
Post by: Razmo on August 26, 2018, 03:00:07 AM
I've written about this bug in the Bug thread, and I've also written support about it... but I'd like to hear if anyone else has noticed, that any program they have created, or other preset that use clocked LFO's sounds different with the latest 1.1.4.18 OS?

All the presets I've made thus far, that use the LFOs in clocked mode (as master or slave, it does not matter), seems to have the division settings messed up... one particular program i made, that had it set to "2 steps", now sound completely wrong, and is fixed now setting it to "4 steps" instead.

It happens to ALL programs I've made, that use the LFOs in clocked mode.

I really hope that DSI will be fast with fixing this bug because it temporarily stops you from wanting to create new presets until it's fixed... otherwise anything you create that use the LFO's in synced mode will sound wrong when they have fixed it...

http://razmo.ziphoid.com/Bug.mp3

The above audio demo show what I'm talking about. The first sound you hear is a single key being pressed and held for the duration of the sound... that first sound has the Time Division setting of LFO1 set to 4 steps... This is the way the sound was made to sound, but to make it sound like this after OS 1.1.4.18, I had to change the Time Division setting of LFO1 to "4 steps"... in my original preset it was "2 Steps"... with OS 1.1.4.18, and the Time Division set to "2 Steps", it now sounds like the second sound in the demo above... clearly different because the Time Divisions of 1.1.4.18 does not match prior OS'es anymore.

A bit about the sound:

the two oscillators are playing different pitches that are set up by the gated sequencers... seq1 play oscillator 1, and seq2 play oscillator 2... they gradually change the pitch upward with oscillator 1 playing the first note, oscillator 2 playing the second, then oscillator 1 playing the third and so on... the sequencers restart on every new note played so that the sequence start over.

With this alone, the two oscillators would just mix equally, and the pitch changes would be abrubt as the sequencers change the pitches, so to get those smooth fades you hear in the first sound, I use LFO1 set to a triangle, and let this LFO smoothly change the oscillator MIX parameter... that way, when one oscillator is heard only, the others pitch is changed by the sequencer for that oscillator... but for this to work, the LFO would have to be both keysync'ed and clock synced, otherwise the LFO will not line up with the sequencers. The LFO and sequencers play VERY tight together in this sound, so the Time Division setting of LFO1 is crucial to avoid that the oscillators are heard when their pitch is changed by the sequencers.

The second sound you hear has very abrupt changes because the LFO is no longer correctly synced with the pitch changes in the sequencers...

I have made 3-4 other programs that use a clocked LFO, and these also sound wrong with OS 1.1.4.18...

Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: AlainHubert on August 26, 2018, 07:05:33 PM
Just updated to 1.1.4.18 and there's a bug with the LFO speed LED indicators section. When selecting LFO1 and trying to adjust its speed the LED of LFO2 changes speed instead (although the speed of LFO1 actually changes as it should). Same thing for LFO2, when trying to change its speed with the Frequency knob, the flashing speed of LFO3 LED changes instead of the one for LFO2. Not to mention the microscopic font of the OLED display during firmware update...  ???


Not that those LEDs are terribly useful in the first place (can hardly see them flashing anyway), but it's still an additional bug that wasn't there before.

There's been a new firmware update for the OB6 too, and it also messed up some of the LEDs on the front panel (support already advised of it, awaiting conformation from them).
I reverted back to a previous firmware version on the OB6.

And I think I'll have to do the same on my REV2 (going all the way back to 1.1.4.5 since it's the last one that didn't add any new bugs and was stable).

That firmware code must be a real mangled spaghetti mess if LED indicators aren't pointing to the right variable in the table after new code is added... ? 

What the use of adding new features and correcting bugs, if it means creating new and unrelated ones each time ?  ::)

BTW, DSI programmers should port the digital encoder software fix from the Prophet X and REV2 to the OB6 also. At least that worked well without messing up something else. Because who needs acceleration on an encoder with only from 3 to 10 possible positions ?  :o
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: RonGerrist on August 27, 2018, 08:25:00 AM
To me, as a software development team lead, this bug fixing and adding features look very unprofessional.
How 1 fix creates a new bug in a totally unrelated area is beyond me. Also, don't they do basic regression testing?

I'm not updating my REV2. I'm happy it works fine now.

I wonder when there will be a REV22
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: extempo on August 27, 2018, 10:28:39 AM
Thanks for your bug reports, everyone. I'd just like to take a moment to remind everyone that these are BETA OS versions we post here, and not production releases. No one is under any obligation to load these versions, of course. If you've reported a bug directly to support, you will hear back from someone, either with an acknowledgment of the bug or a request for more information or additional steps for reproducing it. Sometimes fixing existing bugs or adding features changes other things in unexpected ways. Thanks!
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: RonGerrist on August 27, 2018, 12:13:18 PM
Thanks for your bug reports, everyone. I'd just like to take a moment to remind everyone that these are BETA OS versions we post here, and not productions releases. No one is under any obligation to load these versions, of course. If you've reported a bug directly to support, you will hear back from someone, either with an acknowledgment of the bug or a request for more information or additional steps for reproducing it. Sometimes fixing existing bugs or adding features changes other things in unexpected ways. Thanks!

You have a fair point, my apologies if I came across a bit too harsh.
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: ffx on September 07, 2018, 04:01:24 AM
Hi,

I have two questions regarding beta firmwares:

- Can I easily downgrade to my current stable version 1.1.4.5, if the beta version is not satisfying, or is that a problem?

- Do I still have to do those global parameter resets and OSC calibration?

Thanks!
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: Kasimir Effekt on September 07, 2018, 12:44:38 PM
I'm not sure if this is a bug, but maybe someone of you could try to see if this behavior also appears on your device and if that is intentional:

Load a basic patch, reduce cutoff and set a high filter env amount with short decay (naturally, you get a "clicky" sound).
If all 16 (or 8 ) voices are played while the sustain pedal is held down, the envelope will no longer be triggered, until you deactivate sustain! Every added note now sounds very dull...
Oddly enough, you can fix this behavior by setting Keymode to "retrigger" - which according to the manual should only affect unison sound ...

Actually, from the experience with other polyphonic synthesizers, I assume that with the consumption of all voices, "voice stealing" should occur - but the retrigger behavior should not change!
 
Or am I wrong, and that is normal behavior? Thank you in advance!
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: dequalsrxt on September 18, 2018, 10:32:05 AM
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.
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: maxter on September 18, 2018, 11:35:23 AM
I'm not sure if this is a bug, but maybe someone of you could try to see if this behavior also appears on your device and if that is intentional:

Load a basic patch, reduce cutoff and set a high filter env amount with short decay (naturally, you get a "clicky" sound).
If all 16 (or 8 ) voices are played while the sustain pedal is held down, the envelope will no longer be triggered, until you deactivate sustain! Every added note now sounds very dull...
Oddly enough, you can fix this behavior by setting Keymode to "retrigger" - which according to the manual should only affect unison sound ...

Actually, from the experience with other polyphonic synthesizers, I assume that with the consumption of all voices, "voice stealing" should occur - but the retrigger behavior should not change!
 
Or am I wrong, and that is normal behavior? Thank you in advance!

I think it's normal behavior. It's mainly for unison/mono mode, where each voice is already assigned, meaning the voices don't cycle. The trigger mode should, imo, set how the envelopes of the voices act when a voice is "stolen", or reassigned a new note, when the envelope has not completed its last cycle. I use OS 1.1.4.5, and it's the same there so I think it's intentional.
Title: Bug Sustain Pedal?
Post by: minor7th on September 19, 2018, 11:35:55 AM
I just updated my Rev2 16Voice to 1.1.4.18 and I came across a bug while using the sustain pedal. Playing one note with key down -> sustain pedal down -> key up sustains the note as long as the sustain pedal is held down. This is the expected result, so far so good.
This only works for the first 8 consecutively played notes, for the next 8 notes there is no held sustain while the next 8 notes do work as expected again. It seems to me, that the sustain works only for one sound board. Is this a general bug or a malfuction of my synth?
Title: Bug Sustain
Post by: minor7th on September 19, 2018, 12:01:59 PM
After investigating the above bug some more I can conclude, that at least my instrument behaves strangely. I can reproduce the following behaviour consistently.

Playing a program in "single mode" (meaning neither stack nor split is activated) after 8 played notes there is no sustain function for the next 8 consecutively played keys only to have sustain again for the next 8 notes. If I play two keys at the same time, the sustain function alters after 4 played double note chords. The same is true for playing the same program with "Edit Layer B2 activated.

Strangely enough, playing still the same program but with "Stack A+B" activated, no matter how many notes or chords I play, the sustain functions for each an ever one and for both layers as is expected.
With the same program in Split Mode I get consistend sustain function on the lower keyboard while no sustain on the upper part, which I guess is as designed.
Title: Re: BETA OS v1.1.4.18 Bug Report Thread
Post by: dequalsrxt on September 20, 2018, 01:52:51 PM
Ok I don't think this behavior is actually bug. It occurred to me last night that I'm not getting note off information because I'm clocking the sequencer with gates, so there is no midi timing info for the rev2 to pass on, just pitch.

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.
Title: Re: Bug Sustain SOLVED
Post by: minor7th on September 23, 2018, 12:30:16 AM
Fixed with newest OS 1.1.4.25

After investigating the above bug some more I can conclude, that at least my instrument behaves strangely. I can reproduce the following behaviour consistently.

Playing a program in "single mode" (meaning neither stack nor split is activated) after 8 played notes there is no sustain function for the next 8 consecutively played keys only to have sustain again for the next 8 notes. If I play two keys at the same time, the sustain function alters after 4 played double note chords. The same is true for playing the same program with "Edit Layer B2 activated.

Strangely enough, playing still the same program but with "Stack A+B" activated, no matter how many notes or chords I play, the sustain functions for each an ever one and for both layers as is expected.
With the same program in Split Mode I get consistend sustain function on the lower keyboard while no sustain on the upper part, which I guess is as designed.
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: AlainHubert on September 23, 2018, 07:50:19 PM
Thank you DSI for this latest firmware update (1.1.4.25). We can now have a global LFO that remains in sync, or have independent ones by using Key Sync. To put them back all in sync (global), simply using Unison with 16 voices and using Key Sync once to reset them. Except for the random waveform which still behaves as 16 independent LFOs, generating different random values but in sync, unfortunately.

I'd sure would have preferred a dedicated LFO Global Mode (on/off) parameter, but this is better than nothing, and at least now they all remain properly timed and not drifting anymore.

Now, if only that 12 db filter mode would have more resonance, that would be the icing on the cake, but I fear that this is a hardware limitation not fixable in software... Oh well.

There still remains the Tempo LED bug when the REV2 is in Slave Clock mode, with an external MIDI clock source, which flashes twice as fast as the source clock, sometimes not at all, or sometimes stays lit when switching from Master to Slave...



 
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: Quatschmacher on September 24, 2018, 12:40:28 PM
Thank you DSI for this latest firmware update (1.1.4.25). We can now have a global LFO that remains in sync, or have independent ones by using Key Sync. To put them back all in sync (global), simply using Unison with 16 voices and using Key Sync once to reset them. Except for the random waveform which still behaves as 16 independent LFOs, generating different random values but in sync, unfortunately.

I'd sure would have preferred a dedicated LFO Global Mode (on/off) parameter, but this is better than nothing, and at least now they all remain properly timed and not drifting anymore.

Now, if only that 12 db filter mode would have more resonance, that would be the icing on the cake, but I fear that this is a hardware limitation not fixable in software... Oh well.

There still remains the Tempo LED bug when the REV2 is in Slave Clock mode, with an external MIDI clock source, which flashes twice as fast as the source clock, sometimes not at all, or sometimes stays lit when switching from Master to Slave...

Cool! Could this also be implemented on the P12?
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: Razmo on September 24, 2018, 12:55:01 PM
I'm not sure what it is yet... but I think there may be a bug with the unison mode... i cannot get the detune parameter to have any effect on a monophonic program I'm working on... it simply has no effect for some reason... if I take an initialized program though, it does work when switching unison on and choosing more than one voice... just will not work in the program I'm working on... I've not been able to figure out yet, what other parameter is the cause of this in my program.
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: Kasimir Effekt on September 26, 2018, 04:37:32 AM
Hello everybody. I have noticed some more bugs (although it may be that they already existed in previous firmware versions and it is known behavior):

- If an Lfo is in clk sync mode, its frequency can no longer be controlled as a destination in the mod matrix

- Modwheel is partially not taken over via shortcut as a mod source - as a workaround, you have to first assign a different mod source, then modwheel is recognized again.

- There is some strange behavior regarding the MIDI functionality via USB:
The Rev2 creates a MIDI loop when recording in Cubase so that the recorded midi notes are not played back. The settings in the DAW (such as MIDI Filter) did not solve the problem.
When "Local off" is activated, the duplicate notes disappear, but no programs or banks can be manually selected on the Rev2. To dial in presets quickly, it is a bit awkward to work with PC commands in this case ... I think it should be possible to record without MIDI doubling, but you should still be able to select presets on the keyboard.

Furthermore, as a result of modifying "local on / off", the selected preset sometimes stops COMPLETELY to produce sound - Neighboring presets generate sound ..! I need to study this problem a bit more closely to find a possible cause.

I'm grateful if some of you experienced users could clear things up for me. Many Thanks
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: Razmo on September 26, 2018, 04:53:35 AM
Hello everybody. I have noticed some more bugs (although it may be that they already existed in previous firmware versions and it is known behavior):

- If an Lfo is in clk sync mode, its frequency can no longer be controlled as a destination in the mod matrix

- Modwheel is partially not taken over via shortcut as a mod source - as a workaround, you have to first assign a different mod source, then modwheel is recognized again.

- There is some strange behavior regarding the MIDI functionality via USB:
The Rev2 creates a MIDI loop when recording in Cubase so that the recorded midi notes are not played back. The settings in the DAW (such as MIDI Filter) did not solve the problem.
When "Local off" is activated, the duplicate notes disappear, but no programs or banks can be manually selected on the Rev2. To dial in presets quickly, it is a bit awkward to work with PC commands in this case ... I think it should be possible to record without MIDI doubling, but you should still be able to select presets on the keyboard.

Furthermore, as a result of modifying "local on / off", the selected preset sometimes stops COMPLETE to produce sound - Neighboring presets generate sound ..! I need to study this problem a bit more closely to find a possible cause.

I'm grateful if some of you experienced users could clear things up for me. Many Thanks

Regarding the sync'ed LFO's not being modulateable when synced... this is normal I'd say, and probably intentionally made so... it is not limited to the LFO's as far as i know... anything trying to modulate the LFO Rate while it is in sync mode is probably not going to be working.

It would be cool though, if it was possible to modulate between the different divisions from the Mod Matrix...
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: Kasimir Effekt on September 26, 2018, 08:13:31 AM
Hi Razmo,
yes, your're right: synced LFO can not be modulated by any source. Too bad, because it's not uncommon at all to switch different time divisions of a clock synced LFO (for example, if I think of dubstep "wobble basses") ;)

Do you know anything about the MIDI doubling problem? I have read in another forum that the problem can possibly be circumvented by using a MIDI cable and two different MIDI tracks in the DWA, for each MIDI IN and MIDI OUT.

Another user wrote that the problem with stacked programs can be fixed by switching off multimode, which is not the case for me. See here: https://forum.sequential.com/index.php?topic=2356.0


Hello everybody. I have noticed some more bugs (although it may be that they already existed in previous firmware versions and it is known behavior):

- If an Lfo is in clk sync mode, its frequency can no longer be controlled as a destination in the mod matrix

- Modwheel is partially not taken over via shortcut as a mod source - as a workaround, you have to first assign a different mod source, then modwheel is recognized again.

- There is some strange behavior regarding the MIDI functionality via USB:
The Rev2 creates a MIDI loop when recording in Cubase so that the recorded midi notes are not played back. The settings in the DAW (such as MIDI Filter) did not solve the problem.
When "Local off" is activated, the duplicate notes disappear, but no programs or banks can be manually selected on the Rev2. To dial in presets quickly, it is a bit awkward to work with PC commands in this case ... I think it should be possible to record without MIDI doubling, but you should still be able to select presets on the keyboard.

Furthermore, as a result of modifying "local on / off", the selected preset sometimes stops COMPLETE to produce sound - Neighboring presets generate sound ..! I need to study this problem a bit more closely to find a possible cause.

I'm grateful if some of you experienced users could clear things up for me. Many Thanks

Regarding the sync'ed LFO's not being modulateable when synced... this is normal I'd say, and probably intentionally made so... it is not limited to the LFO's as far as i know... anything trying to modulate the LFO Rate while it is in sync mode is probably not going to be working.

It would be cool though, if it was possible to modulate between the different divisions from the Mod Matrix...
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: Razmo on September 26, 2018, 09:52:03 AM
I've found a bug:

1. initialize a program
2. set LFO1's amount to max
3. set LFO1's rate to 25
4. set LFO1's destination to OSC1 Frequency
5. set LFO1's clock sync to "on" (make sure REV2 is master clock)

now press a key and hold it down... you should hear the pitch go up and down smoothly, as the triangle of LFO1 modulates the pitch in sync with the masterclock (at 6 steps).

and now for the bug:

6. press the Stack A+B
7. turn down the volume of layer B to "0" so that it will not interfere with the sound.
7. press a key and hold it down again

now you should hear that the smooth triangle modulation is no longer a smooth triangle waveform... it abruptly change the pitch modulation, and it seems that it somehow phase resets the triangle waveform, because if you change the time division the abrupt reset seems to occur at the same time interval... it's almost like oscillator sync, just with the LFO somehow.

I have no idea why this happens when the B layer is enabled (stacked mode)... but it does, and it's definitely a bug that need fixing.
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: dslsynth on September 26, 2018, 12:10:24 PM
I have no idea why this happens when the B layer is enabled (stacked mode)... but it does, and it's definitely a bug that need fixing.

Just in case: have you checked that the resulting program matches the front panel changes you performed?

Also, wonder if its connected to this Prophet 12 problem:
https://forum.sequential.com/index.php/topic,2884.0.html
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: Razmo on September 26, 2018, 02:17:50 PM
I have no idea why this happens when the B layer is enabled (stacked mode)... but it does, and it's definitely a bug that need fixing.

Just in case: have you checked that the resulting program matches the front panel changes you performed?

Also, wonder if its connected to this Prophet 12 problem:
https://forum.sequential.com/index.php/topic,2884.0.html

Yes... I did... but for some reason it went away again at some point... then came back.. it seems that it's a bit unstable and therefore others who try this may not experience it... makes it a bit hard to replicate it... it seems to be dependent on certain things... I'll have to test it some more...
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: Kasimir Effekt on September 26, 2018, 03:07:25 PM
Confirmed! Stacked programs definitely change the behavior of clock-synced LFOs:
1. initialize a program on layer A, reduce cutoff
2. initialize a program on layer B, set LFO1 (square wave, medium amount) to osc1 freq
3. play the stacked program - you hear the modulated frequency, everything is fine.
BUT:
4. now switch LFO1 on Layer B to clk sync - the pitch change has disappeared!

I've found a bug:

1. initialize a program
2. set LFO1's amount to max
3. set LFO1's rate to 25
4. set LFO1's destination to OSC1 Frequency
5. set LFO1's clock sync to "on" (make sure REV2 is master clock)

now press a key and hold it down... you should hear the pitch go up and down smoothly, as the triangle of LFO1 modulates the pitch in sync with the masterclock (at 6 steps).

and now for the bug:

6. press the Stack A+B
7. turn down the volume of layer B to "0" so that it will not interfere with the sound.
7. press a key and hold it down again

now you should hear that the smooth triangle modulation is no longer a smooth triangle waveform... it abruptly change the pitch modulation, and it seems that it somehow phase resets the triangle waveform, because if you change the time division the abrupt reset seems to occur at the same time interval... it's almost like oscillator sync, just with the LFO somehow.

I have no idea why this happens when the B layer is enabled (stacked mode)... but it does, and it's definitely a bug that need fixing.
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: Razmo on September 27, 2018, 03:58:30 AM
Confirmed! Stacked programs definitely change the behavior of clock-synced LFOs:
1. initialize a program on layer A, reduce cutoff
2. initialize a program on layer B, set LFO1 (square wave, medium amount) to osc1 freq
3. play the stacked program - you hear the modulated frequency, everything is fine.
BUT:
4. now switch LFO1 on Layer B to clk sync - the pitch change has disappeared!

I've found a bug:

1. initialize a program
2. set LFO1's amount to max
3. set LFO1's rate to 25
4. set LFO1's destination to OSC1 Frequency
5. set LFO1's clock sync to "on" (make sure REV2 is master clock)

now press a key and hold it down... you should hear the pitch go up and down smoothly, as the triangle of LFO1 modulates the pitch in sync with the masterclock (at 6 steps).

and now for the bug:

6. press the Stack A+B
7. turn down the volume of layer B to "0" so that it will not interfere with the sound.
7. press a key and hold it down again

now you should hear that the smooth triangle modulation is no longer a smooth triangle waveform... it abruptly change the pitch modulation, and it seems that it somehow phase resets the triangle waveform, because if you change the time division the abrupt reset seems to occur at the same time interval... it's almost like oscillator sync, just with the LFO somehow.

I have no idea why this happens when the B layer is enabled (stacked mode)... but it does, and it's definitely a bug that need fixing.

Yes... that does the same thing... and the modulation seems to go haywire as soon as stacked mode is switched on... if you switch it off again, the modulation comes back in... etc.

I have a feeling that some of the fix for the LFO in sync mode that was done in the latest OS has introduced this new bug... I would bet that they somehow have mixed up some stuff between the two layers, so that one layer also influence the other layer or something like that...

This is a bug that needs to be fixed because it totally ruins the use of the synced LFOs again when you're using stacked programs... I hope that DSI will confirm this bug (?)
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: minor7th on September 27, 2018, 12:06:25 PM
Strange, at first I could not replicate Razmos and Kasimirs problems. Programmed from a freshly initialized patch everything sounds as expected. Stack enabled the Clock synced LFO on layer 1 produces a smooth sweep on OSC 1 freq. Continuous use of the sustain pedal, changing the master clock and divider, playing extensive chords, use aftertouch, change LFO 1s speed and amount or clock sync, switch stack on and off, nothing changes unexpectedly. The OSC1 freq is smoothly modulated.

But I dare you to activate key sync on LFO 1. The waveform of LFO 1 is now hard synced to a source which I could not identify (the LED blinks accordingly). Deactivating key sync solves the problem but for every 8th note played, the LFO is hard synced again. Key sync on again and every note is problematic. Key sync off again, now a strange pattern with good and bad notes. After several key sync on and off events, the LFO is permanently hard synced. Even changing to another program and back does not solve the problem. Switching the Rev2 off and unplugging the power cord for 20 seconds and then on again does not even help. The program seems permanently damaged.

The only fix I have found so far is to start over with a freshly initialized patch...

Edit:
Found a fix for the „hard synced LFO“ once it has occured: Turning the affected LFOs frequency all the way up to 1/16 steps and then back to the desired value fixes the problem. Just do not hit that key sync button again.

Confirmed! Stacked programs definitely change the behavior of clock-synced LFOs:
1. initialize a program on layer A, reduce cutoff
2. initialize a program on layer B, set LFO1 (square wave, medium amount) to osc1 freq
3. play the stacked program - you hear the modulated frequency, everything is fine.
BUT:
4. now switch LFO1 on Layer B to clk sync - the pitch change has disappeared!

I've found a bug:

1. initialize a program
2. set LFO1's amount to max
3. set LFO1's rate to 25
4. set LFO1's destination to OSC1 Frequency
5. set LFO1's clock sync to "on" (make sure REV2 is master clock)

now press a key and hold it down... you should hear the pitch go up and down smoothly, as the triangle of LFO1 modulates the pitch in sync with the masterclock (at 6 steps).

and now for the bug:

6. press the Stack A+B
7. turn down the volume of layer B to "0" so that it will not interfere with the sound.
7. press a key and hold it down again

now you should hear that the smooth triangle modulation is no longer a smooth triangle waveform... it abruptly change the pitch modulation, and it seems that it somehow phase resets the triangle waveform, because if you change the time division the abrupt reset seems to occur at the same time interval... it's almost like oscillator sync, just with the LFO somehow.

I have no idea why this happens when the B layer is enabled (stacked mode)... but it does, and it's definitely a bug that need fixing.

Yes... that does the same thing... and the modulation seems to go haywire as soon as stacked mode is switched on... if you switch it off again, the modulation comes back in... etc.

I have a feeling that some of the fix for the LFO in sync mode that was done in the latest OS has introduced this new bug... I would bet that they somehow have mixed up some stuff between the two layers, so that one layer also influence the other layer or something like that...

This is a bug that needs to be fixed because it totally ruins the use of the synced LFOs again when you're using stacked programs... I hope that DSI will confirm this bug (?)
Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: shiihs on September 27, 2018, 01:59:05 PM
A potential bug with LFOs and clock sync mode (at least I think it's a bug):

Choose LFO1, enable LFO CLK SYNC, turn the LFO Frequency button. The display shows discrete values for the sync rate (OK!), but NRPN 37 is sent with continuously varying values between 0-150 (Not OK? Usually discrete values on the display are also sent as discrete values via NRPN).


Title: Re: BETA OS v1.1.4.25 Bug Report Thread
Post by: mightymusic on September 28, 2018, 05:55:03 AM
After updating to 1.1.4.25 the arpeggiator only send notes to the midi output when the clock mode is set to Off or Master. As as slave the arp doesn't send out the notes to the output. This only works when using the USB midi port. But i don't use this because this produces a bit high noise on the audio output..
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: dp on October 02, 2018, 08:05:41 AM
It looks like the new OS version breaks alternative tunings. Not the biggest of deals for most users until you, like me, rely on them.

Hey shiihs. I also rely heavily on them and was about to update (I'm a few versions back).  When you say it breaks them, can you explain in what way? My guess is that it isn't calculating the tunings correctly...

Thanks
Title: Re: BETA OS v1.1.4.13 Bug Report Thread
Post by: shiihs on October 02, 2018, 01:19:16 PM
Hey shiihs. I also rely heavily on them and was about to update (I'm a few versions back).  When you say it breaks them, can you explain in what way? My guess is that it isn't calculating the tunings correctly...

In 1.1.4.13 everything sounded as if it was forced into a 12 notes/octave harnass (even stuff like bohlen-pierce, 24 EDO, 92 EDO... whatever I sent to it sounded like an awful out of tune (in a bad way :) ) 12 EDO) The tuning problem appears to be solved in 1.1.4.25 though. I can happily noodle in whatever my heart desires again. Also they now implemented dumping tunings from the instrument to the computer (before, it was one-way communication from pc to synth), so it's even improved a little.



Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: eagleman on October 10, 2018, 10:50:00 AM
I would like to know if others are experience the same with the arp beat sync when it is set to quantize as described in this thread.

https://forum.sequential.com/index.php/topic,2988.0.html

For me its an obvious bug. An example, when I set the arp to up and relatch to on and hold is engaged its not sure that it starts with the lowest not and most time it starts with a rest (pause). This makes it impossible to use.
Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: Razmo on October 10, 2018, 12:46:12 PM
I would like to know if others are experience the same with the arp beat sync when it is set to quantize as described in this thread.

https://forum.sequential.com/index.php/topic,2988.0.html

For me its an obvious bug. An example, when I set the arp to up and relatch to on and hold is engaged its not sure that it starts with the lowest not and most time it starts with a rest (pause). This makes it impossible to use.

It seems to not only be when relatch is on, it's just easier to note it in that mode... to me it sounds like the ARP sequence is not relatched properly... if you play a chord without relatch, and switch quickly to a new chord when you release the previous chord, then it also sound like the new chord is not played from the beginning of the ARP sequence, even when all keys has been released before the new chord is pressed. Actually it also does this if you wait a bit before pressing the new chord.

To be honest, it actually sounds like it is not relatching at all, in any given case... it seems like the last chord you held before letting go of the keys is actually still playing "in the background" (just without the notes actually being triggered of course), so that when you hit a new chord, it just continue playing the notes from where ever it was when you press the new chord.
Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: Razmo on October 10, 2018, 01:02:06 PM
I noticed that in the thread where Extempo described the ARP, he said that the ARP will always follow the blinking TAP TEMPO LED... actually it does not and that may be part of the problem with the relatching.

Try creating a simple patch that will step each time the TAP TEMPO LED light up (division setting "Quarter")... now try to hit a chord halfway thru that flashing LED... suddenly the notes trigger at various points with the LED depending on when you hit a new chord... this is certainly not right... the notes should come in, locked to the LED flashing, or at least in the correct time division of it... it certainly do not.
Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: eagleman on October 11, 2018, 03:45:33 AM
I noticed that in the thread where Extempo described the ARP, he said that the ARP will always follow the blinking TAP TEMPO LED... actually it does not and that may be part of the problem with the relatching.

Try creating a simple patch that will step each time the TAP TEMPO LED light up (division setting "Quarter")... now try to hit a chord halfway thru that flashing LED... suddenly the notes trigger at various points with the LED depending on when you hit a new chord... this is certainly not right... the notes should come in, locked to the LED flashing, or at least in the correct time division of it... it certainly do not.

Thanks Razmo. Tried this and I experience the same. There seems to be a multi problem with the firmware here. Hope its on the bug list.
Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: gernotreininger on October 11, 2018, 03:58:33 AM
I noticed that in the thread where Extempo described the ARP, he said that the ARP will always follow the blinking TAP TEMPO LED... actually it does not and that may be part of the problem with the relatching.

Try creating a simple patch that will step each time the TAP TEMPO LED light up (division setting "Quarter")... now try to hit a chord halfway thru that flashing LED... suddenly the notes trigger at various points with the LED depending on when you hit a new chord... this is certainly not right... the notes should come in, locked to the LED flashing, or at least in the correct time division of it... it certainly do not.

Thanks Razmo. Tried this and I experience the same. There seems to be a multi problem with the firmware here. Hope its on the bug list.
Same arp issue here as well.
Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: minor7th on October 15, 2018, 11:35:31 AM
Arp Bug?

I can't get a flowing ARP line in conjunction with the sustain pedal, no matter which setting under Globals #26 I use.

I simply want to play a 6 note chord, hold it with the sustain pedal while arranging my fingers for the next chord to be played. While the pad sound on layer A sounds as expected, the arp sequence on layer B either stops or does not retrigger or does retrigger on every other chord. All the other ARPs, hard- and software, I have work perfectly.

Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: Antonino on October 17, 2018, 01:23:20 AM
Triange wave work badly.
Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: Razmo on October 17, 2018, 06:02:32 AM
Triange wave work badly.

Have you tried re-calibrating the REV2? ... I have no problems with the triangle wave here...
Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: Antonino on October 17, 2018, 06:32:02 AM
yes, I calibrated twice and it works very badly, I'm worried, it's the second main board I change.
Title: Re: BETA OS v1.1.4.26 Bug Report Thread
Post by: Razmo on October 17, 2018, 06:34:39 AM
yes, I calibrated twice and it works very badly, I'm worried, it's the second main board I change.

try and have the REV2 on for half an hour... then turn it off, wait 10 seconds, then turn it on again and do the calibration once again... I'm pretty certain, that if your triangle waveform sounded ok before the upgrade, then it's not the board that is the problem, but something else.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: creativespiral on October 20, 2018, 10:05:31 AM
I see under the release notes for 1.1.4.9
16. Bug Fix: Pan Mode defaulting to Alternate regardless of saved state of parameter

I am running the latest version 1.1.4.27, and this still seems to be an issue (or I'm not understanding how its supposed to work)

If I set an INIT patch, and set PAN MODE to ALTERNATE, then turn up the PAN SPREAD in the amp env, I'm getting Alternating left/right panning for each time I hit a key/voice (Expected Behavior, although doesn't seem to be hard left / hard right).   But if I set the PAN MODE to FIXED, I'm getting the exact same results... which doesn't seem like intended behavior.

I want to be able to set LAYER A to hard left, and LAYER B to hard right.   I was expecting that setting the PAN MODE to FIXED that the Pan Spread of 64 would be centered, 0 would be hard left and 127 would be panned hard right.  Or is there some other control that determines the panning in Fixed Mode?   

ALSO, it seems that when Pan Spread is set to max and Alternate Mode, it doesn't actually hard pan each voice... there seems to be some volume still coming through in the "off side".  It is possible to hard pan (ie 100% left, 0% right) a layer to the right or left?

Thanks!
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: eagleman on October 20, 2018, 10:41:54 AM
I’m on firmware 1.1.4.27 on the Prophet REV2.
There are still some issues with the Arp Beat Sync Quantize function. I made a video explaining this. I compare the REV 2 with how I think it should work on a Deepmind 12.
The issue with the missing note is fixed and all is on time with the new firmware. That's good. The bug now is that the arp sequence doesn't start with the right note. It's somehow random.

Could some of you guys confirm this behavior.

https://youtu.be/llCh4PEbj50

Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: maxter on October 20, 2018, 11:38:32 AM
I see under the release notes for 1.1.4.9
16. Bug Fix: Pan Mode defaulting to Alternate regardless of saved state of parameter

I am running the latest version 1.1.4.27, and this still seems to be an issue (or I'm not understanding how its supposed to work)

If I set an INIT patch, and set PAN MODE to ALTERNATE, then turn up the PAN SPREAD in the amp env, I'm getting Alternating left/right panning for each time I hit a key/voice (Expected Behavior, although doesn't seem to be hard left / hard right).   But if I set the PAN MODE to FIXED, I'm getting the exact same results... which doesn't seem like intended behavior.

I want to be able to set LAYER A to hard left, and LAYER B to hard right.   I was expecting that setting the PAN MODE to FIXED that the Pan Spread of 64 would be centered, 0 would be hard left and 127 would be panned hard right.  Or is there some other control that determines the panning in Fixed Mode?   

ALSO, it seems that when Pan Spread is set to max and Alternate Mode, it doesn't actually hard pan each voice... there seems to be some volume still coming through in the "off side".  It is possible to hard pan (ie 100% left, 0% right) a layer to the right or left?

Thanks!

This is actually how it's intended to work, mostly. The misc parameter "Pan mode" alternate/fixed, only sets how panning is affected when used as a mod destination (matrix, lfo etc). The spread parameter is not affected by this setting.

To pan a layer you need to set up DC as mod source and pan (fixed) as destination in the mod matrix. Then you can hard pan the layers to your liking.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: brinnandeskepp on October 27, 2018, 07:12:48 AM
I'm still getting the weird unintended bitcrush/ringmod bug on my FX fairly often. Means I can't use the instrument in live performances!
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: AlainHubert on October 27, 2018, 08:23:39 AM
I'm still getting the weird unintended bitcrush/ringmod bug on my FX fairly often. Means I can't use the instrument in live performances!

I do occasionally get this also on my REV2. Quite annoying. Sequential needs to address this and correctly reset the effects DSP when changing patches.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: minor7th on October 29, 2018, 10:32:02 AM
I'm still getting the weird unintended bitcrush/ringmod bug on my FX fairly often. Means I can't use the instrument in live performances!

So do I. Everytime I'm using my Rev2 this issue pops up. Quite annoying to be frank...
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: rhullings on October 29, 2018, 12:18:26 PM
Me too, and the arp still seems to be a bit of a mess. I'm getting the note order problem detailed in the video a few posts above and am experiencing some weird behavior (dropping notes, being out of time) when locking to an incoming clock signal over USB. I should probably try it over MIDI. It does at least seem better than it was before, just not perfect.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: minor7th on October 29, 2018, 01:47:15 PM
I’m on firmware 1.1.4.27 on the Prophet REV2.
There are still some issues with the Arp Beat Sync Quantize function. I made a video explaining this. I compare the REV 2 with how I think it should work on a Deepmind 12.
The issue with the missing note is fixed and all is on time with the new firmware. That's good. The bug now is that the arp sequence doesn't start with the right note. It's somehow random.

Could some of you guys confirm this behavior.

https://youtu.be/llCh4PEbj50

Yes, same problem here. Arp on internal clock with beat sync enabled generates some weird note sequences. I could not figure out a pattern, neither with three note arps nor with four or any other number notes arp. It just does not start with the lowest note.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: eagleman on October 29, 2018, 02:42:55 PM
Yes, same problem here. Arp on internal clock with beat sync enabled generates some weird note sequences. I could not figure out a pattern, neither with three note arps nor with four or any other number notes arp. It just does not start with the lowest note.

Thanks minor7th. Hopefully this will be fixed in a forthcoming update. I use the ARP function a lot in my performances and been forced to use  the Rev 2 trough other hardware to get it working.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Deonc on November 01, 2018, 03:00:19 AM
I'm still getting the weird unintended bitcrush/ringmod bug on my FX fairly often. Means I can't use the instrument in live performances!

So do I. Everytime I'm using my Rev2 this issue pops up. Quite annoying to be frank...

I get this very frequently too, I just bought the rev2 for live use and I am looking to do a show in a couple of weeks so I hope this is fixed soon.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: jamespianoo on November 01, 2018, 11:29:14 AM
Hi there guys,

I recently bought the Prophet Rev 2 and upgraded it to the latest software. However I seem to have this issue since I upgraded that whenever I use the pitch bend it changes the entire pitch of the synth to a tone/step down. Resetting the global settings fixes it until I use the pitch bend again.

Does anyone know if this is a bug or is there a way to rectify the issue? Please help!
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: skrohmer on November 01, 2018, 12:04:14 PM
I recently bought the Prophet Rev 2 and upgraded it to the latest software. However I seem to have this issue since I upgraded that whenever I use the pitch bend it changes the entire pitch of the synth to a tone/step down. Resetting the global settings fixes it until I use the pitch bend again.

Does anyone know if this is a bug or is there a way to rectify the issue? Please help!

Hi, did you already calibrate the wheels?
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Kasimir Effekt on November 01, 2018, 12:49:29 PM
I think I've found another bug: when stack mode is activated, the poly sequencer can no longer be started via the sequencer jack. (SeqPedalMode in Globals set to 'normal').
It still works via the play button. Can someone confirm this?
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: jamespianoo on November 02, 2018, 07:51:08 AM
I recently bought the Prophet Rev 2 and upgraded it to the latest software. However I seem to have this issue since I upgraded that whenever I use the pitch bend it changes the entire pitch of the synth to a tone/step down. Resetting the global settings fixes it until I use the pitch bend again.

Does anyone know if this is a bug or is there a way to rectify the issue? Please help!

Hi, did you already calibrate the wheels?

That did it, thanks!
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Troy92Evans on November 02, 2018, 05:12:45 PM
My ARP is certainly still off rhythm. And to clarify my LFO’s and whatnot are clocked fine so it’s not a MIDI issue. The speed changes when I change the external tempo from my daw (have also tried various clock sources, same result)but it isn’t synced to being on beat. Anyone else?

Also I don’t want to be coming at anybody. I love all the updates. Just curious if anybody else sees this.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Tugdual on November 03, 2018, 03:37:52 AM
I'm new to The Prohet REV2 so hard to say if the issue I face is related to the beta version.
Anyway I use the REV2 together with Ableton using the "External instrument". General parameters: 4.Slave no S/S,  16: Local Off. Everything works fine but after may be 1h I start hearing a very loud an digital effect that totally sounds like decimation (undersampling). If I unplug the REV2 and use headphones, same result. Somehow I believe this is related to the internal sound effects but even when I disable them I still have the lound sound. If I change the program, it carries on. Totally sounds like the effect sections crashed. Only cure so far is power Off/On
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 03, 2018, 03:42:42 AM
I'm new to The Prohet REV2 so hard to say if the issue I face is related to the beta version.
Anyway I use the REV2 together with Ableton using the "External instrument". General parameters: 4.Slave no S/S,  16: Local Off. Everything works fine but after may 1h I start hearing a very loud an digital efefct that totally sounds like decimation (undersampling). If I unplug the REV2 and use headphones, same result. Somehow I believe this is related to the internal sound effects but even when I disable them I still have the lound sound. If I change the program, it carries on. Totally sounds like the effect sections crashed. Only cure so far is power Off/On

Sounds like you're also experiencing the problem with the internal FX like you mention... there are situations where the FX act strangely when you are working in split/stacked mode... it seems to occur when two of the same FX are used on both layer A and B at the same time... so when it happens, try to look at what FX are active on the two layers... I know that some people have this problem with distortion on both layers... the bug has been around for some time, but SCI has not fixed it yet for some reason.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: andey on November 03, 2018, 09:05:36 AM
OS V1.1.4.27 turn on  Local Control-off does not work Layer B .What should I turn on to make it work Layer B. OS 1.1.4.5 Layer B works.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: ensoniq70 on November 03, 2018, 09:40:54 AM
I'm still getting the weird unintended bitcrush/ringmod bug on my FX fairly often. Means I can't use the instrument in live performances!
New REV-2, update to the latest Beta Version = Same problem here. Some Presets destroy the sound with the FX completely. No change if i use another preset or a blank patch. I have to switch off my REV-2 to eliminate this bitcrush/ringmod FX Bug.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: UXS on November 04, 2018, 03:08:09 AM
I'm still getting the weird unintended bitcrush/ringmod bug on my FX fairly often. Means I can't use the instrument in live performances!
New REV-2, update to the latest Beta Version = Same problem here. Some Presets destroy the sound with the FX completely. No change if i use another preset or a blank patch. I have to switch off my REV-2 to eliminate this bitcrush/ringmod FX Bug.

Hello

I confirm that. The same problem here. The Rev2 has to be turned off to fix this bitcrush/ringmod FX issue.
I can't use Rev2 now to be honest :(
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Troy92Evans on November 04, 2018, 12:15:49 PM
Go back to a previous OS rather than a beta for now....”I can’t use the REV2 now” is a bit extreme. Never go into a performance with anything short of a thoroughly investigated new update, on anything, ever. Not your computer, not a synth, not anything.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Stue007 on November 04, 2018, 10:33:04 PM
Hi, same here - happens sometimes when changing programs by hand fast with the sequencer being on, too. The Rev2 has to be turned off to fix this bitcrush/ringmod FX issue. This bug is still existing in the newest Beta release unfortunately.

Otherwise I love my Rev2, awesome synth!

Cheers
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: bbirecikli on November 05, 2018, 12:43:25 AM
Hi,

Downloaded 1.1.4.27 via the support section of the product. I'm assuming it is not beta anymore.

I'm having an issue with doubling midi notes, as they are recorded into my host (Ableton) connected via USB.
 
Local Control is off, Multimode is off.

Tried alternating different parameters but it always comes down to having Stack A+B option enabled. I get a recording of a really short and the actual note after that. When I don't stack it behaves normal.

Attaching a screenshot of a midi recording (Manually moved second long note to the right so it revealed the double).

Thanks,

B
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: andey on November 05, 2018, 03:26:06 AM
where can I download OS 1.1.4.5
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Merlijn Nash on November 05, 2018, 04:30:43 AM
I've got a few notes (2 f-sharps) where the oscillators (or the shapes) are duller since the latest patch (1.1.4.27). Kinda hard to explain so I attached some sound.

Calibrated multiple times, including all the Razmo tricks ;)

It only happens with oscillators 1&2 (not with the sub or noise or resonance), so I'm guessing it's not the filter.

On some presets this doesn't occur, but it happens on any INIT patch right off the bat.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Vathan on November 05, 2018, 06:09:54 PM
I just installed 1.1.4.27 upgrading from 1.1.4.5 and I'm experiencing something odd.

The keyboard on the unit itself, even with local on, will not trigger sounds on many patches if the stack mode is engaged. External keyboards work fine. I reset globals and calibrated, but it's still not working correctly.

Downgrading to 1.1.4.5 returns everything to normal. Is this a bug or my unit specifically?
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Merlijn Nash on November 06, 2018, 12:53:32 AM
I've got a few notes (2 f-sharps) where the oscillators (or the shapes) are duller since the latest patch (1.1.4.27). Kinda hard to explain so I attached some sound.

Calibrated multiple times, including all the Razmo tricks ;)

It only happens with oscillators 1&2 (not with the sub or noise or resonance), so I'm guessing it's not the filter.

On some presets this doesn't occur, but it happens on any INIT patch right off the bat.


Fixed by first resetting globals, then calibrating
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: AlteredMode on November 06, 2018, 04:50:00 AM
I've been experiencing issues with the arp which appears to have already been detailed here in terms of it being slightly off in time. I've also had the issue with the FX happen once today but was able to clear it with powering off and on again. Any indication when they might release a patch that resolves these?
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 07, 2018, 05:37:04 AM
Regarding the FX bug, it happened to me yesterday with two programs I've created... particularly one where I used the hipass filter on both layers on one program, and then switching to the other introduced this RingMod like sound... from the times I've experienced it, it always seems to happen when layer A & B have the same FX going... sometimes it screws up the program it's used in, at other times it works with that program, but makes other programs sound weird when switching to them... I'll do some more experimentation with this today and post it if I find anything reproducible.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 07, 2018, 01:36:25 PM
I've been working on a program that should simulate a thunderclap... and this program will start the "ringmod" like sound after being played for a while, all by itself... it is a program that use the distortion FX on both layers... really annoying...
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 07, 2018, 01:53:57 PM
Refering to this thread from october 2017, the FX problem should be fixed: https://forum.sequential.com/index.php/topic,1959.0.html

For some reason, this is not the case... I'm on the latest beta, and it's still present... if SCI want the program that replicate the problem they can write me a note about it, and I'll give them the program for testing.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Robot Heart on November 07, 2018, 04:47:51 PM
Just a friendly reminder if anyone wants us to verify a bug, please write our dedicated support channel with reproducible steps and pertinent information. It's *the only way* you can be certain we have seen it or acknowledge it:

support (at) sequential.com

We can't always check each forum.
Thanks!

Oh, and it's Sequential (Sequential LLC to be exact), not SCI. The "Circuits" part of the name had already been dropped before Dave sold the company to Yamaha in the '80s.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 07, 2018, 05:09:49 PM
Just a friendly reminder if anyone wants us to verify a bug, please write our dedicated support channel with reproducible steps and pertinent information. It's *the only way* you can be certain we have seen it or acknowledge it:

support (at) sequential.com

We can't always check each forum.
Thanks!

Oh, and it's Sequential (Sequential LLC to be exact), not SCI. The "Circuits" part of the name had already been dropped before Dave sold the company to Yamaha in the '80s.

This thread is a bit confusing then, because it's an official post that say "Bug Report Thread"... so people must assume that you at Sequential will be reading the bug reports here (!?) ... what is this thread for then? just for debating user to user?
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Robot Heart on November 07, 2018, 05:44:09 PM
It's so all the bug reports are in one place. It helps consolidate the forum so everyone, users and us, can find things easily and there aren't tons of "bug report" topics all with just a few comments in each.

However, we can't constantly monitor each forum. We just don't have the bandwidth to do that. That's why it's imperative that you contact us through our dedicated support channel to ensure your bug is visible and/or verified.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Tugdual on November 07, 2018, 11:33:52 PM
Refering to this thread from october 2017, the FX problem should be fixed: https://forum.sequential.com/index.php/topic,1959.0.html

For some reason, this is not the case... I'm on the latest beta, and it's still present... if SCI want the program that replicate the problem they can write me a note about it, and I'll give them the program for testing.
I confirm I also have the issue and now I wonder why it takes so much time fixing a so dramatic and visible problem. Because of its random nature? Or because it is inherent to a hardware design issue that cannot be fixed? I have one week left before I decide to return or keep the synth and while I love it so far this issue is a major show stopper. Please DSI help me make the right decision.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 08, 2018, 12:41:33 AM
Refering to this thread from october 2017, the FX problem should be fixed: https://forum.sequential.com/index.php/topic,1959.0.html

For some reason, this is not the case... I'm on the latest beta, and it's still present... if SCI want the program that replicate the problem they can write me a note about it, and I'll give them the program for testing.
I confirm I also have the issue and now I wonder why it takes so much time fixing a so dramatic and visible problem. Because of its random nature? Or because it is inherent to a hardware design issue that cannot be fixed? I have one week left before I decide to return or keep the synth and while I love it so far this issue is a major show stopper. Please DSI help me make the right decision.

The bug might be more deep than DSI initially thought... it was thought to be fixed in an update long ago, but I'm certain that it still persist, and I'll write them a bug report right now, sending them the program I've made that introduce the bug every single time it's played... that should get them going, if they are not already on the trail of this stubborn bug.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 08, 2018, 12:54:14 AM
I've contacted support as requested about this, and supplied them with the program I made that introduce the bug... I'll let you guys know when I hear something about it.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 08, 2018, 01:03:06 AM
It's so all the bug reports are in one place. It helps consolidate the forum so everyone, users and us, can find things easily and there aren't tons of "bug report" topics all with just a few comments in each.

However, we can't constantly monitor each forum. We just don't have the bandwidth to do that. That's why it's imperative that you contact us through our dedicated support channel to ensure your bug is visible and/or verified.

Alright... thank you for the clear explanation... Personally I knew that you want us to contact you via support, since you've written it countless times in other threads... i just had to get this clarified openly once again so that everyone reading and writing in this thread know this, because i got this feeling that not everyone know it.

Maybe it would be a good idea to write what you just did, in the first post in this thread?
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 08, 2018, 01:20:41 AM
Refering to this thread from october 2017, the FX problem should be fixed: https://forum.sequential.com/index.php/topic,1959.0.html

For some reason, this is not the case... I'm on the latest beta, and it's still present... if SCI want the program that replicate the problem they can write me a note about it, and I'll give them the program for testing.
I confirm I also have the issue and now I wonder why it takes so much time fixing a so dramatic and visible problem. Because of its random nature? Or because it is inherent to a hardware design issue that cannot be fixed? I have one week left before I decide to return or keep the synth and while I love it so far this issue is a major show stopper. Please DSI help me make the right decision.

This will be pure speculation about the cause of the bug... but to me, the sound gives me the impression that it's purely a FX DSP bug... it's only present when the FX are on, so that's a certain give away.

To me, the way it sounds is like if all FX are at a lower sampling frequency... this could probably happen if the DSP is working with more than it can handle I think... what makes me think that this is the cause is that any of the FX will work just fine when you are using only one layer... it will start only when both FX engines are in use on both layers at the same time...

Now, I do not know if the REV2 has two separate DSPs, one for layer A and one for layer B, but I'd suspect that it actually have only one that handles the DSP for both layers... thus, if two of the FX use too much processing power in tandem, you may get this bug perhaps... I do not know how DSP heavy the distortion algorithm is... I'd assume it would not be much, but I have no clue about it of course.

So... IF this is a matter of the DSP getting overloaded with some particular combinations of FX, then it may be that it's unfixable unless DSI knows how to optimize the DSP code for those FX...

but if this is the case, then it would be nice to know exactly what FX and what combinations it is that we will have to see as "defunct".

One thing I noticed as well, with my program was, that it started happening when the parameters of the distortion FX was at certain settings... I worked on that program for more than two hours without it screwing up at all, until the end of my work with it... that means that I had both layers going with the distortion FX for about two hours before it began happening... weird.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 08, 2018, 01:49:03 AM
I can add one more observation to this bug... it's only layer B that has this problem... this is probably why some program switching after layer B has screwed up will sound correct... simply because it's not using layer B at all.

I tested this by simply making my program go haywire on layer B, and then turning down the layer B volume... i can hear that Layer A sounds fine.

So switching FX on layer B off, or turning off stacked/split mode will remove the problem, but it will introduce it again as soon as they are switched back on, and will be present on any program that use layer B until the REV2 has been power cycled.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: AlainHubert on November 08, 2018, 09:20:44 AM
It might be an obscur Analog Devices Sharc DSP hardware bug that is difficult to fix in software perhaps ?
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Razmo on November 08, 2018, 12:51:34 PM
I got an answer on my support ticket about the FX bug... it has been confirmed as a bug, and added to the bug list, and should be fixed in an upcoming beta release, so stay tuned for the fix :)
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Tugdual on November 08, 2018, 02:00:46 PM
I got an answer on my support ticket about the FX bug... it has been confirmed as a bug, and added to the bug list, and should be fixed in an upcoming beta release, so stay tuned for the fix :)
That's good news... thanks for your follow up Razmo
Title: Is the wheel calibration a dummy feature?
Post by: Tugdual on November 08, 2018, 02:16:38 PM
I executed a wheel calibration (Global 28) multiple times and while checking with MIDI OX, I found that no change was ever recorded. I eventually purposely sabotaged the calibration, setting minimum at 33% way before min position, and max at 66% way before max position and again no change.

Is the calibration a dummy feature?
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: rhullings on November 08, 2018, 03:44:49 PM
Has anyone submitted submitted a service ticket for the arp bug (wrong order, still not perfectly in sync)? If not I'll put it in.  Would love to have that fixed.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: minor7th on November 08, 2018, 11:38:49 PM
Has anyone submitted submitted a service ticket for the arp bug (wrong order, still not perfectly in sync)? If not I'll put it in.  Would love to have that fixed.

No, not yet. Thank you for reporting this bug through the „official“ channel.
But I do hope we are not supposed to coordinate the bug reports ourselfs on this forum. From now on I will send my reports directly to support while still adding them to this thread.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Kasimir Effekt on November 10, 2018, 09:21:41 AM
jfyi: I submitted a support ticket to Sequential - the sequencer pedal bug is confirmed and will (hopefully) be fixed soon.

I think I've found another bug: when stack mode is activated, the poly sequencer can no longer be started via the sequencer jack. (SeqPedalMode in Globals set to 'normal').
It still works via the play button. Can someone confirm this?
Title: Re: DDL Delay Problem
Post by: workfloh on November 16, 2018, 05:33:49 PM
Hi. When turning on DDL Delay and turn the timing to quarter dot (clk sync) there is no delay. Can anyone confirm or is it a problem with my rev2. Thank you in advance.

The same here.
Title: Re: DDL Delay Problem
Post by: workfloh on November 16, 2018, 05:34:32 PM
Hi. When turning on DDL Delay and turn the timing to quarter dot (clk sync) there is no delay. Can anyone confirm or is it a problem with my rev2. Thank you in advance.

The same here.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: cbmd on November 16, 2018, 05:38:28 PM
See if increasing/decreasing the BPM causes this to change.  The delay has a maximum buffer size, if a sync'd delay time exceeds this buffer, then the buffer size is reduced.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: workfloh on November 16, 2018, 06:47:05 PM
See if increasing/decreasing the BPM causes this to change.  The delay has a maximum buffer size, if a sync'd delay time exceeds this buffer, then the buffer size is reduced.

Okay. Thanks.

I found two new Bugs:

1. I init a sound. Then i use the pitch wheel (especially the higher notes) and turn (slowly) up and down.
It makes some strange things. Bleeps and blops.
No smoothe pitch.

2. The (global) parameter "dont start and stop (master/slave mode) doesnt work for me. it starts the sequenzer everytime.

Can everyone reproduce it?

Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: World Studios on November 20, 2018, 02:23:14 AM
Hi, all! I upgraded to 1.1.4.27 from a much earlier version and performed all sorts of resets and recalibrations plus I did all of it twice to be double sure, but still Stack mode did not work at all, Neither triggered from USB midi not the keyboard. I found 1.1.4.5 here on the forum and tried that. Stack works again.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Kasimir Effekt on November 21, 2018, 08:28:31 AM
I noticed the following behavior: normally the time parameter of the rev2's delay effects can be changed steplessly by a source (for example the modwheel). This works even when the delay has "clk sync" activated (which I think is totally useful)!
But it does NOT work for the BBD-delay: the time-parameter can not be changed by another source when clk sync is switched on! It makes no sense that this delay should behave differently than the others...
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: jok3r on November 22, 2018, 01:49:23 AM
It's more a question than a bug report, because I'm not able to reproduce it, but it happens from time to time:

Sometimes the amount knob in the LFO section does not respond to changes anymore, but only for a single LFO. If I choose another LFO it works pretty well. If I switch back to the "failing" one, it still doesn't work. Switchen patches doesn't solve the issue. The only solution I found for this so far is to power cycle the synth. After that it works again.

Did this happen to anyone around here, too?
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: camillomuc on November 22, 2018, 09:48:27 AM
Yes, I also have this issue from time to time.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: jg666 on November 22, 2018, 10:23:09 PM
It's more a question than a bug report, because I'm not able to reproduce it, but it happens from time to time:

Sometimes the amount knob in the LFO section does not respond to changes anymore, but only for a single LFO. If I choose another LFO it works pretty well. If I switch back to the "failing" one, it still doesn't work. Switchen patches doesn't solve the issue. The only solution I found for this so far is to power cycle the synth. After that it works again.

Did this happen to anyone around here, too?

Yes I get this happening but not always on the same knob. It also happens on my Pro2, again I don’t think it’s always the same knob, but I can’t reproduce it at will so can’t work out why it happens. My initial thinking was that it was a particular patch that causes it but I couldn’t make it happen again when changing through the same patches.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: Vathan on December 04, 2018, 11:22:30 AM
Hi, all! I upgraded to 1.1.4.27 from a much earlier version and performed all sorts of resets and recalibrations plus I did all of it twice to be double sure, but still Stack mode did not work at all, Neither triggered from USB midi not the keyboard. I found 1.1.4.5 here on the forum and tried that. Stack works again.

Yes! I'm having this same issue. Support told me it's logic's fault on midi echo, so apparently, my computer cares about what OS I'm running. Hard to believe, since 1.1.4.5 still works as it always has.

FWIW, I have several DSI synths, and something similar to this happened a while ago with the Prophet 12. Eventually another release fixed the issue. Currently my OB6, Prophet 12, and Prophet X work fine in all modes with logic and local turned off.

Hoping to hear about an update on this, so we will see.
Title: Re: BETA OS v1.1.5 Bug Report Thread
Post by: eagleman on December 08, 2018, 06:25:44 AM
Just made a support ticket about the arp sync that still plays the notes in the wrong order as to set under the arp mode. I’m on firmware 1.1.5
Title: Re: BETA OS v1.1.5 Bug Report Thread
Post by: eagleman on December 10, 2018, 01:32:38 PM
Just made a support ticket about the arp sync that still plays the notes in the wrong order as to set under the arp mode. I’m on firmware 1.1.5

Quoting myself.
Just got this confirmed as a bug and that its on the list to be fixed in an coming update :)
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: cbmd on December 10, 2018, 03:40:01 PM
This bug has been fixed and the new OS has just been posted.
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: eagleman on December 11, 2018, 05:13:14 AM
This bug has been fixed and the new OS has just been posted.

Thank you very much for this long awaited update. Now it possible for me to use the rev 2 live without an external sequencer!! The arp is working flawlessly. I can start an arp-sequence press hold, do something else, com back and change cords. Everything is in time and in the right note-order reflected by the arp mode :)
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: Razmo on December 11, 2018, 05:25:45 AM
This bug has been fixed and the new OS has just been posted.

Thank you very much for this long awaited update. Now it possible for me to use the rev 2 live without an external sequencer!! The arp is working flawlessly. I can start an arp-sequence press hold, do something else, com back and change cords. Everything is in time and in the right note-order reflected by the arp mode :)

How do you change the chords? I have to stop the HOLD mode first, before assigning a new chord... otherwise a new chord held is just added to the already held notes... or am I misunderstanding what you're writing?
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: eagleman on December 11, 2018, 05:28:42 AM
This bug has been fixed and the new OS has just been posted.

Thank you very much for this long awaited update. Now it possible for me to use the rev 2 live without an external sequencer!! The arp is working flawlessly. I can start an arp-sequence press hold, do something else, com back and change cords. Everything is in time and in the right note-order reflected by the arp mode :)

How do you change the chords? I have to stop the HOLD mode first, before assigning a new chord... otherwise a new chord held is just added to the already held notes... or am I misunderstanding what you're writing?

You have to set Arp Relatch to on under the ARP settings.
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: Razmo on December 11, 2018, 06:08:11 AM
This bug has been fixed and the new OS has just been posted.

Thank you very much for this long awaited update. Now it possible for me to use the rev 2 live without an external sequencer!! The arp is working flawlessly. I can start an arp-sequence press hold, do something else, com back and change cords. Everything is in time and in the right note-order reflected by the arp mode :)

How do you change the chords? I have to stop the HOLD mode first, before assigning a new chord... otherwise a new chord held is just added to the already held notes... or am I misunderstanding what you're writing?

You have to set Arp Relatch to on under the ARP settings.

arrh... sure... i should have known that :D ... thank you... it's actually quite useful now for what I intend on using the REV2 for in the future. Now the only thing I could wish for is that Sequential will finally fix that problem with recording to both layers in the polysequencer, when "Edit Layer B" is set to edit both layers (blinking).
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: eagleman on December 11, 2018, 06:47:17 AM
This bug has been fixed and the new OS has just been posted.

Thank you very much for this long awaited update. Now it possible for me to use the rev 2 live without an external sequencer!! The arp is working flawlessly. I can start an arp-sequence press hold, do something else, com back and change cords. Everything is in time and in the right note-order reflected by the arp mode :)

How do you change the chords? I have to stop the HOLD mode first, before assigning a new chord... otherwise a new chord held is just added to the already held notes... or am I misunderstanding what you're writing?

You have to set Arp Relatch to on under the ARP settings.

arrh... sure... i should have known that :D ... thank you... it's actually quite useful now for what I intend on using the REV2 for in the future. Now the only thing I could wish for is that Sequential will finally fix that problem with recording to both layers in the polysequencer, when "Edit Layer B" is set to edit both layers (blinking).

For sure a very time saving feature even if you are using an editor. For now, I’m happy with the arp working. For me a real gamechanger using this synth. By the way I think that the Arp relatch setting should be se to on by default. Think this is the most normal behavior like on the deepmind12 and the old Rolands.
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: Razmo on December 14, 2018, 05:06:46 AM
I've sent a support ticket, since the FX bug on layer B is still present under special circumstances... I've created a program that makes it crash the layer B FX which i sent along with the support ticket, so they should be able to reproduce the bug.

Again it happens when layer B has the same FX as layer A... in this case the HiPass filter... in the first place it did not do this... it happened exactly when I made a modulation matrix assignment that routed the VCA envelope back to it's VCA envelope release time... so I'm not even certain it has to do with the FX alone (or at all for that matter)... I'm more keen on thinking it might be a modulation matrix problem.

The bug makes layer B sound like it's either very low sample rate, or running thru a ring modulator... or like I'm beginning to suspect; a modulation source that has gone haywire and is making audio rate modulation to the VCA at insane speeds.
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: luk.vermeir@gmail.com on December 14, 2018, 07:31:33 AM
This bug has been fixed and the new OS has just been posted.

Thank you very much for this long awaited update. Now it possible for me to use the rev 2 live without an external sequencer!! The arp is working flawlessly. I can start an arp-sequence press hold, do something else, com back and change cords. Everything is in time and in the right note-order reflected by the arp mode :)

How do you change the chords? I have to stop the HOLD mode first, before assigning a new chord... otherwise a new chord held is just added to the already held notes... or am I misunderstanding what you're writing?

You have to set Arp Relatch to on under the ARP settings.

still a pity this exact behavior doesn't exist out of the ARP mode.

'Hold and Relatch', for playing perfectly sustained notes / chords after each other, without needing to press a sustain pedal all the time, just ain't possible with the REV2. Unless you use other dedicated hardware, like Squarp Pyramid but that's a bit overkill just for that functionality.

Just wondering why it's not possible to add this relatch functionality in HOLD mode, if it's already possible with the arp...

Also, the 4-notes limitation for chords on this great 16V (or 8V) synth still doesn't seem to be addressed with the latest updates... So playing a root note + a 4 note chord on top of that and save this chord in 'chord memory', skips one of that 5 notes or voices. That ain't really a bug though, but just some strange limitation decision...
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: Razmo on December 15, 2018, 02:56:32 AM
I can confirm that the FX/Modulation bug is still present, and that it has been added to the bug list again...

By the way; is anyone else in here experiencing that the Arpeggiator sometimes just simply stops playing while you hold down chords? ... you can usually start it again by repressing the chord, but I just wonder why this happens... it's happening frequently enough for it to be irritating, but not regularly enough to be able to reproduce anything. It also happens on non-arpeggiated sounds, thus just ordinary playing where the sound stops when you are still holding down keys.

Also... since I've had my REV2, sometimes (maybe once or twice a day) I experience a sudden "crackle/pop" coming from the REV2... it's just very briefly, sounding like if you had a loose plug, giving of a loud crackle/pop... it happens approx. once  or twice a day with me while playing, and only while actually playing the keys... I've never experienced it while not touching the keys... I just keep wondering if this is somehow related to this modulation bug (I do not believe it's an FX bug anymore)... if certain situations in the engine makes the modulation of something "burst" perhaps... but again; it's impossible to find a way to reproduce it, so I've not been able to make a support ticket for this behavior.
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: RockyRacoon on December 29, 2018, 04:04:24 PM
New Bug?

The program changes correctly (including sound) but it only updates the program name and not the program number on the display. I am sending classic LSB/MSB/ProgramChange messages from a Nord Stage 2 or an iPad (tried both)

OS is the BETA 1.1.5.1

Watch here:
https://youtu.be/X34QuDSycIk
Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: minor7th on January 06, 2019, 09:03:58 AM
Thanks for the major improvements to the arpeggiator in 1.1.5.1. Finally, it is usable in a live situation. But only as long as one sticks to zero Arp Repeats.
With any repeats dialed in the arpeggio will start in up mode with the highest instead with the lowest note and vice versa in down mode with the lowest note instead of the highest.

I will send a bug report.
Title: Re: BETA OS v1.1.4.27 Bug Report Thread
Post by: benjaminmatthews1982 on January 08, 2019, 06:23:24 AM
See if increasing/decreasing the BPM causes this to change.  The delay has a maximum buffer size, if a sync'd delay time exceeds this buffer, then the buffer size is reduced.

Okay. Thanks.

I found two new Bugs:

1. I init a sound. Then i use the pitch wheel (especially the higher notes) and turn (slowly) up and down.
It makes some strange things. Bleeps and blops.
No smoothe pitch.

2. The (global) parameter "dont start and stop (master/slave mode) doesnt work for me. it starts the sequenzer everytime.

Can everyone reproduce it?

hello workfloh (and DSi peeps),

I also am getting the bug mentioned in #1 in a very similar fashion -- I am on the latest OS 1.1.5.1

Basically the pitch wheel is slow to respond and consistently out of tune -- I have to disable pitchbend range (set to 0) to make the synth play in tune now.  I have recalibrated wheels and oscilators.  I have disconnected MIDI cables to make sure no other device is interferring.  About out of ideas, going to have to submit a ticket to get this fixed -- I'm concerned there may be a physical problem with my wheel as this started out of the blue (did not patch OS recently other than to troubleshoot this issue).  I also rarely use the pitch wheel in my performances and only noticed the issue because the synth randomly got out of tune.

Title: Re: BETA OS v1.1.5.1 Bug Report Thread
Post by: OneLittleFonzie on January 08, 2019, 07:05:32 AM
Also... since I've had my REV2, sometimes (maybe once or twice a day) I experience a sudden "crackle/pop" coming from the REV2... it's just very briefly, sounding like if you had a loose plug, giving of a loud crackle/pop... it happens approx. once  or twice a day with me while playing, and only while actually playing the keys... I've never experienced it while not touching the keys... I just keep wondering if this is somehow related to this modulation bug (I do not believe it's an FX bug anymore)... if certain situations in the engine makes the modulation of something "burst" perhaps... but again; it's impossible to find a way to reproduce it, so I've not been able to make a support ticket for this behavior.

I have this a lot with bright patches AND using chorus. I'll check tonight on which standard patch I can reproduce this.
Title: Re: BETA OS v1.1.5.6 Bug Report Thread
Post by: AlainHubert on January 11, 2019, 09:11:38 AM
Updated to the latest 1.1.5.6 beta, and I'm sorry to report that the MIDI Clock Mode in Slave Mode TEMPO LED blinking fix still has a problem when BPM is set to 30 when receiving MIDI clock from another MIDI device, resulting in the LED flashing randomly. At all other speeds it flashes correctly (although not always in correct phase relative to incoming source clock).


Title: Re: BETA OS v1.1.5.6 Bug Report Thread
Post by: Kasimir Effekt on January 11, 2019, 10:03:56 AM
I have to report that the mod matrix still has the problem that the modwheel can not be assigned immediately via the source shortcut. you have to assign a different source first, then the modwheel seems to work too.
Title: Re: BETA OS v1.1.5.6 Bug Report Thread
Post by: Razmo on January 11, 2019, 12:40:45 PM
I've just installed the latest v1.1.5.6 ... and generally I'm good this far... but two of my presets which also had problems earlier (the dreaded ringmod like sound), and that I changed some parameters in to make the bug go away, now sounds a bit different than before... it's presets that utilize the distortion effect that somehow seems much more distorted... much grunge'ier... not that it's bad, and I'll edit the two presets to sound like before, but it makes me wonder if you at Sequential changed something to the distortion FX algorithm to fix the bug?
Title: Re: BETA OS v1.1.5.6 Bug Report Thread
Post by: studiodc on January 11, 2019, 03:33:54 PM
(although not always in correct phase relative to incoming source clock).

MIDI clock has no concept of phase at all, so this is very normal with all beat synched MIDI devices. You can resync certain components to the clock with the MIDI transport START command which at least provides the idea of the initial phase relationship, but only transport-sensitive controls (the sequencer, usually) are likely to obey this.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Razmo on February 05, 2019, 05:43:26 PM
I just discovered that the "ringmod" bug is still present... just made a preset that introduce it... again a problem with layer B... this time, after loading this bugged preset, I also experienced strange behavior when switching to a preset that only use layer A after having loaded that buggy preset... at one time it started to ping pong the sound from left to right for eight keystrokes, then the sound changed to center for the next eight keystrokes... another time it played for eight keystrokes, and then went silent for another 8 keystrokes...

It seems that the bug change character as I switch the Layer B effect on/off...
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: cbmd on February 05, 2019, 05:57:31 PM
Thanks for the note.  We'll look into it...and fix it as we always do.

Also worth noting that this is not related to a specific Layer B problem.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Razmo on February 05, 2019, 06:05:01 PM
Thanks for the note.  We'll look into it...and fix it as we always do.

Also worth noting that this is not related to a specific Layer B problem.

ok... it just always seem to happen when the B layer is initiated... anyway, I'm just glad you will fix this because this bug (what ever it is) is happening quite often for me when I'm designing my sounds, and the reason I'm loosing my temper a bit over it (explaining the now moderator erased comment I made in my last post).

I have been doing quite a bit of sound design on the REV2 over the last 7-8 months, and I often run into some strange behaviors from time to time, that I usually cannot even replicate to make a support ticket about it... If I just happen to squeeze out all the bugs with my sound design i do not know... but there just seem to pop something up from time to time... that is why I proposed to take a thorough look at the engine.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: thefunkyoystersgang on February 06, 2019, 03:33:47 AM
hi
i did the update from 1.1.4.27 to 1.1.5.9,
I have still the same issue with my rev2.
I mainly create from basic program my own presets, and mainly stack sounds.
I send program change from ableton and the sound is ok, programs are changing. but the display don't change the number of program (always U2P42 appears...) the name of the preset is changing correctly but not the preste number, even if the sound is the correct one. It's not a big issue, but it is the kind of thing that can make me panic one stage, making me wondering about a problem from ableton or midi wire....
Anyone experiencing the same issue ? any idea to solve it?
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: thefunkyoystersgang on February 07, 2019, 07:39:49 AM
When BBD delay is on, with clock sync on, LFO & Matrix modulating Param1 are not working. Didn't with a EG.
Is it normal?
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: musicmaker on February 07, 2019, 08:22:16 AM
Never had calibration issues with any F/W but 1.1.5.9 always is stuck at Voice 1. OSC2.
Reset Global, Power off/on does not fix it. Did the same sequence on 1.1.5.9 as I do after every upgrade: Reset Globals then start Calibration
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Kasimir Effekt on February 07, 2019, 12:55:15 PM
Yes. I already informed the Support about this issue - they told me that „the BBD is different than the DDL“ regarding the time parameter. It seems to be an intentional configuration.

 
When BBD delay is on, with clock sync on, LFO & Matrix modulating Param1 are not working. Didn't with a EG.
Is it normal?
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Ujamroll on February 13, 2019, 09:49:33 AM
Hi All,

Have I done some completely stupid? 🥴

I purchased a Rev2 several months ago. It appeared to be working fine. So far so good.

Yesterday, on the DSI product support website I noticed the current OS firmware is 1.1.4.27. I checked my OS version and it said 1.5???. Trusting what I found on the website I followed the instructions and installed the 1.1.4.27 firmware. I now have major problem. Following installation I have gained a loud ‘clicking’ sound on voice trigger/key depression. On initial investigation it seems to specific to the B Natural key in the higher octaves. It is not present on all patches but it is prominent where LFO mod is involved (strings etc).

Having just joined the forum I have noticed mention of OS 1.1.5.9.

Which beckons the question, have been stupid and installed the wrong Time OS 🥴
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Razmo on February 13, 2019, 10:29:52 AM
Hi All,

Have I done some completely stupid? 🥴

I purchased a Rev2 several months ago. It appeared to be working fine. So far so good.

Yesterday, on the DSI product support website I noticed the current OS firmware is 1.1.4.27. I checked my OS version and it said 1.5???. Trusting what I found on the website I followed the instructions and installed the 1.1.4.27 firmware. I now have major problem. Following installation I have gained a loud ‘clicking’ sound on voice trigger/key depression. On initial investigation it seems to specific to the B Natural key in the higher octaves. It is not present on all patches but it is prominent where LFO mod is involved (strings etc).

Having just joined the forum I have noticed mention of OS 1.1.5.9.

Which beckons the question, have been stupid and installed the wrong Time OS 🥴

I don't think it said 1.5... there is no such OS version yet... do you mean 1.1.5? ... you seem to have downloaded the latest OFFICIAL OS from the homepage, but there are newer BETA OS in this forum... you can download it from the sticky thread in the top of this forum... no problem, just install that and you're good to go :)
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: skipgilles on February 20, 2019, 04:24:55 AM
I want to repost a little bug: 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.

I cannot the current non-behavior is as intended.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: camillomuc on February 20, 2019, 03:16:54 PM
I think there is still an issue with the arp and the gated sequencer in stack mode:
If just Layer A or B is active, the gated sequencer plays all 16 steps in key step mode (arp on/16th), but in stack mode just 8 steps of the sequence are played.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: camillomuc on February 23, 2019, 03:58:12 AM
I have a second problem: Sometimes in unison chord mode the notes of the chord are not playing simultaneously.
It seemes, that this happens sometimes after changing programs. I can only reset it, if I restart the rev2.
Did anyone else notice this issue?
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: exorb on March 02, 2019, 09:04:36 PM
Has anyone mentioned the random global tuning (Master Coarse) going on everytime you turn your baby on?

Also alot of custom split patches does'nt work, the "B" split is "empty" (no OSC selected).

Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Razmo on March 03, 2019, 02:39:31 AM
Has anyone mentioned the random global tuning (Master Coarse) going on everytime you turn your baby on?

Also alot of custom split patches does'nt work, the "B" split is "empty" (no OSC selected).

I do not get any random global master coarse... are you certain you do not have your REV2 set up with some sort of MIDI controller or DAW that is sending out tuning data or something?

And about the B layer... have you tried to see if layer B is also off on stacked programs? ... if yes, then have you dumped the bank sounds you're talking about via USB to your REV2? ... if you do that too fast, all layer B presets will get scrambled (not working) because the dump has to put in delays between each program in the dump... this has been documented earlier as a probable cause for layer B's acting up strangely.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: camillomuc on March 07, 2019, 03:23:31 PM
I have a second problem: Sometimes in unison chord mode the notes of the chord are not playing simultaneously.
It seemes, that this happens sometimes after changing programs. I can only reset it, if I restart the rev2.
Did anyone else notice this issue?
Now I did discover another issue with layers a+b sometimes running out of sync (both layers with gated seq at the same bpm in "no reset mode"). When I restart the synth, both layers are in sync again. Strange behaviour...
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: RobustAmerican on March 09, 2019, 02:24:08 PM
Well I just updated from 1.1.4 to 1.1.5.9. Followed the directions to the T and some of my sounds have gone completely sideways. I've narrowed it down to the LFOs that were set to clock sync. The LFO beat division settings have changed. They all seem to be 3 to 4 times faster than they were. Oh boy. I also had to calibrate several times to get the oscillators sounding consistent from voice to voice. I finally unplugged all cables, except the power, and ran the procedure a third or forth time with good results.

This has me more than a little worried about releasing my sounds. How can I be absolutely sure that the sounds are exactly as they should be when they change so much with a version upgrade? Some of them were almost unrecognizable.

What really has me worried is this:
After updating, I went through all my sounds and fixed the LFO beat division issues that surfaced with 1.1.5.9. Did I just screw up my sounds? Were they in fact working correctly with 1.1.4? Or are they working correctly with 1.1.5.9? This is a bad place to be in when trying to create sounds for a commercial release. Of course I have back ups of both versions but I still don't know which settings are going to translate to the end users properly.

I guess I'll have to document the OS used to create the sounds and include some sort of disclaimer that explains what might happen if used with other OS versions.

Thanks for your time!

Randy
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: extempo on March 11, 2019, 10:35:17 AM
Well I just updated from 1.1.4 to 1.1.5.9. Followed the directions to the T and some of my sounds have gone completely sideways. I've narrowed it down to the LFOs that were set to clock sync. The LFO beat division settings have changed. They all seem to be 3 to 4 times faster than they were. Oh boy. I also had to calibrate several times to get the oscillators sounding consistent from voice to voice. I finally unplugged all cables, except the power, and ran the procedure a third or forth time with good results.

This has me more than a little worried about releasing my sounds. How can I be absolutely sure that the sounds are exactly as they should be when they change so much with a version upgrade? Some of them were almost unrecognizable.

What really has me worried is this:
After updating, I went through all my sounds and fixed the LFO beat division issues that surfaced with 1.1.5.9. Did I just screw up my sounds? Were they in fact working correctly with 1.1.4? Or are they working correctly with 1.1.5.9? This is a bad place to be in when trying to create sounds for a commercial release. Of course I have back ups of both versions but I still don't know which settings are going to translate to the end users properly.

I guess I'll have to document the OS used to create the sounds and include some sort of disclaimer that explains what might happen if used with other OS versions.

Thanks for your time!

Randy

Hi Randy, please see this note in the change log from a handful of BETAs ago.

Main OS 1.1.4.25 - Release Candidate

BugFix: Clock synced LFOs were previously being calculated incorrectly, as the result of a bug dating back to the Prophet 08. This was fixed in BETA 1.1.4.18, but resulted in changes to user patches utilizing synced LFOs. 1.1.4.25 introduces versioning so that user patches with clock synced LFOs made prior to 1.1.4.18 mostly sound correct with the fix. The caveat is that some time divisions still won’t sound correct and will need to be manually reset. We felt that is was better to have this bug fixed, despite the inconvenient result in certain limited circumstances. Thanks for understanding.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: RobustAmerican on March 12, 2019, 04:20:49 PM
Quote
Hi Randy, please see this note in the change log from a handful of BETAs ago.

Main OS 1.1.4.25 - Release Candidate

BugFix: Clock synced LFOs were previously being calculated incorrectly, as the result of a bug dating back to the Prophet 08. This was fixed in BETA 1.1.4.18, but resulted in changes to user patches utilizing synced LFOs. 1.1.4.25 introduces versioning so that user patches with clock synced LFOs made prior to 1.1.4.18 mostly sound correct with the fix. The caveat is that some time divisions still won’t sound correct and will need to be manually reset. We felt that is was better to have this bug fixed, despite the inconvenient result in certain limited circumstances. Thanks for understanding.


Ahhh, thanks so much for that. Not sure how I missed it. I guess I should read all those notes again....again.

Randy
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: noir on April 27, 2019, 07:16:37 AM
I experience the following bug:
I configured pickup mode for poti values. When I hold [show] to see the real value of a parameter while turning the poti and I accidentally release [show] before the value is reached, the parameter just jumps to the position of the poti and overwrites the original value with this.

Maybe it could be more foolproof to just show the value of the poti as soon it is moved?
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: AlainHubert on April 30, 2019, 09:17:21 AM
I experience the following bug:
I configured pickup mode for poti values. When I hold [show] to see the real value of a parameter while turning the poti and I accidentally release [show] before the value is reached, the parameter just jumps to the position of the poti and overwrites the original value with this.

Maybe it could be more foolproof to just show the value of the poti as soon it is moved?

I think that the Show Value is meant to do exactly this: show the current value of a parameter. I don't think that it was intended to be used as a continuous value display. Anyway, just make sure to remove your hand from a given pot before releasing the Show button. Problem solved.

But I second your idea of automatically showing a parameter value when turning a given knob. That would be great. But I wouldn't keep my hopes up, since Sequential has pretty much given up on adding new features on this model.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: noir on April 30, 2019, 12:17:26 PM
I think that the Show Value is meant to do exactly this: show the current value of a parameter. I don't think that it was intended to be used as a continuous value display. Anyway, just make sure to remove your hand from a given pot before releasing the Show button. Problem solved.
I don't know what you mean. At least for me this function works as the following:
Poti of parameter A is physically at 9 O'clock.
In the current preset, it somewhere else.
If I want to see the actual value of parameter A without changing it, I need to hold the [show] button and turn the Poti until it reaches the saved position. There's no value shown to me until the position is reached.

Especially in a stressful live situation (this is where I'm using this device most of the time) it can happen that you slip off this button.

I hope that they just change this behavior, it's such a very minor fix with a big impact on the usability. I'd even sign a NDA and do it by myself...
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: OneLittleFonzie on April 30, 2019, 12:30:32 PM
I just tested what it does on my rev2.

When the stored value = 0 and the pot is at at 63. I press misc, and turn up. After turning about 15 degrees up it shows 0.
Also the other way around. When I turn about 15 degrees down, the actual value is shown.

This makes me think that you don't have to reach the stored value but it appears that way. It just takes quite a turn to get the stored value on the display. Not just by touching it.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Galileo on May 11, 2019, 03:36:29 AM
Hi,
I'm new to the Rev 2 and don't know if it's a bug or not, already written to the support but I think there are misunderstandings in the issue.
It's related to the poly sequencer, I can't modify or insert notes from the keyboard in tracks other than 1 ( i can using the encoders)
Here is a simple example and exactly the steps i do:


I record simple a polyphonic sequence G-  F rolling the chords while holding notes.
check the notes entered and they are :
step 1 G Bb D (voice 1,2 and 3)
step 2 F  A  C

and that is ok.

now  i want to change the C in the third voice in Eb

I hit record, navigate using the encoders parameter and track to step 2 of voice 3
I hit Eb on my keyboard .

check the sequence and what i have now is :

step 1 G Bb D (voice 1,2 and 3 )
step 2  Eb A C

Eb is recorded in voice 1 and not in voice 3.

firmware is 1.1.5.9
Prophet rev2 desktop module

Is the sequencer intended to work like this or not?
Is this a bug of the firmware of a problem with my unit?

Thank you very much

Andrea
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: keston on June 14, 2019, 08:28:38 AM
I have discovered that the neither the arp nor sequencer will start when the clock divide is set to 1/64 triplets if the REV2 is in slave mode receiving MIDI clock from either the MIDI DIN in or USB.

1. Go to globals and set MIDI Clock Mode to Slave
2. Send MIDI Clock from another device or a computer to the REV2
3. Set the clock divide to 1/64 triplets
4. Try pressing play on the sequencer or on/off on the arp
5. Neither the arp or sequencer will play

If you start the arp or seq in 1/32 note triplets it will allow you change to 1/64 note triplets properly. I just updated yesterday so I don't think it was happening in 1.1.4.27, but I could be wrong and just discovered the behavior.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: skipgilles on June 14, 2019, 02:05:37 PM
Annoying, buggy LFO behavior after key sync has been enabled.
I have Rev2, 8 voices, v1.1.5.9 installed, calibrated multiple times.

To produce problem:

step 1)
I have a simple program in layer A or B (no stack or split) with an LFO (say reverse saw) controlling something (say cut-off), NO clk sync, NO key sync. After a fresh power-on of the instrument, this functions as expected: I hear the spikes in the cutoff in sync for all voices (0-7, looking in the display after pressing global).

step 2)
Now, I enable key sync and play a couple of notes, and disable key sync again.

resulting bug:
Now, I have two non-synced lfo's, one for voices 0-3, and one for voices 4-7, audible as non-synced cutoff spikes in the sound.

The bug also happens when, instead of step 2, I simply select another program with key sync on and play some notes. They only way to get the expected sound is to power the instrument off and on again.




Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: skipgilles on June 14, 2019, 04:24:23 PM
Ah, I see this has been discussed in length already (under the name "global sync"). Did not search enough before posting. Well, I find this behavior really useless. Depending on how my single oscillator LFO's happen to be started when using a previously selected key-sync program, my no-key-sync program sounds less or more chaotic. That seems ridiculous to me.

Maybe I am spoiled by the intuitiveness of modern digital stuff made in red, but this seems so unintuitive to me. Along with many other funny behaviors that are maybe very "classic synth-like", I am considering selling this beautiful sounding machine that, after a year of intensive use, has still not become a friend.

EDIT:
Hey, but wait, this does not explain why my first four voices (0-3) are in sync with each other and so are my second four (4-7).
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: cbmd on June 14, 2019, 05:13:01 PM
Regarding the 3 descriptions of potential bugs above.

1. When record is active, newly played notes on the keyboard overwrite the old sequence.  If you want to edit a sequence, use the SHOW button to access the sequencer screen, and use the soft encoders to change a step's value.

2. I've checked a REV2 in shop and am not able to replicate the described issue with the arp/sequencer not playing when clock divide is set to 64 triplets and the synth is externally sync'd.  I advise you to reset your global parameters and check again.

3. Concerning the LFOs, the LFOs are free running and per voice.  When the synth is first powered on, every LFO on every voice is initialized at the same time.  If Key Sync is turned on, the LFO(s) on the triggered voice are reset to their zero point.  The LFOs will continue at that phase until a new key is played on the voice.  This is the expected behavior of 'polyphonic LFOs', nothing is wrong with your REV2 in this regard.  In contrast to this, the Prophet 6 only has a single LFO which affects all 6 voices.

Hope this helps!
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: keston on June 17, 2019, 02:04:34 PM
Multiple reset globals and power cycling has solved part of this. Now, with external clock, the arp works fine but the sequencer won't start at the highest clock division (1/64 triplets). What is strange is that if you hold down the sustain pedal the notes do play (and they are sustained), but as soon as you let off they stop. I have tried all the different Arp. Pedal and Seq. Pedal settings, but they all exhibit the some problem. Is anyone running an external clock able to reproduce this?

I have discovered that the neither the arp nor sequencer will start when the clock divide is set to 1/64 triplets if the REV2 is in slave mode receiving MIDI clock from either the MIDI DIN in or USB.

1. Go to globals and set MIDI Clock Mode to Slave
2. Send MIDI Clock from another device or a computer to the REV2
3. Set the clock divide to 1/64 triplets
4. Try pressing play on the sequencer or on/off on the arp
5. Neither the arp or sequencer will play

If you start the arp or seq in 1/32 note triplets it will allow you change to 1/64 note triplets properly. I just updated yesterday so I don't think it was happening in 1.1.4.27, but I could be wrong and just discovered the behavior.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: godparticle on June 25, 2019, 06:16:38 PM
Does this OS thing include any fix for that ring mod sound bug related to the fx? It kind of makes this board unplayable at times...
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Razmo on July 10, 2019, 06:32:20 AM
I'm having a bit of a problem, when I use the gated sequencer set to reset when it gets a MIDI note-on.

I'm trying to sync my REV2 and PEAK together, by setting both to reset when receiving a note-on... The REV2 is set to play a sequence using the gated sequencer, and PEAK is set to retrigger an arpeggio... what I'm trying to do is to make both reset on a note-on, and then play in sync. I have both synths receive the same MIDI clock signal coming from my V-Synth GT, and the note-on the two synths recieve is also coming from the V-Synth GT... both synths are connected to the V-Synth via MIDI DIN, so what the two get is exactly the same signal, so there cannot be any deviances in the signal that they recieve... I'm using a MIDI splitter cable for this.

My PEAK retrigger as it should, tight and on the spot as it gets a note-on... but the REV2 seems really sloppy with it's retriggering of the sequence... I'm wondering if this is a bug... I'm thinking that maybe the internal resolotion of the REV2 is perhaps 96PPQN, and that maybe the PPQN timer is not reset, but only the actual sequence? ... it sounds like some sort of jittering because of the PPQN timer being at different positions when the resetting of the sequence occurs... it's a very short jitter, but it's enough to make any kind of key-trigger sync of the REV2 to any other machine impossible which is kind of a shame really.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Razmo on July 10, 2019, 07:32:50 AM
I have made a short demo example of what I'm talking about here: http://razmo.ziphoid.com/sync.mp3

the first part is my V-Synth GT playing back a rhythm sample that is locked to BPM (98BPM)... this clock is sent to both PEAK and REV2 along with the note-on triggers from the GT's keyboard.

Next part I add the PEAK's arpeggio and trigger it a few times... as can be heard, the PEAK lines up perfectly with the GT.

Next part I add the REV2 playing an additional rhythm via the gated sequencer, and as can be heard it's all over the place... the tempo is right, but the resetting is definitely off and jittery.

I do not know if this behavior is also present with REV2's arp and sequencer... probably is I would guess.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Troy92Evans on July 13, 2019, 11:27:29 PM
I’m not somewhere where I can listen right now but if I haven’t just stopped, set tempo (or kept it the same) and then started abletons clock (as in from the beginning or maybe from an exact downbeat, I usually play live so I just start it from the beginning every time) my arpeggiator is a nightmare. It kinda scares me live and isn’t like abletons arp where I can tap tempo in and drop it in live with a band. It’s kind of a shame and makes it much more of a played keyboard than an arp or sequencer ever, which is how I usually am anyway but I’d love to do both...
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: CPN37 on July 26, 2019, 03:11:08 AM
I thought I'd mention a bug which I've already reported to Sequential and they've added to their list for a future OS update, just in case anyone else notices similar behaviour.

Basically when I am switching from my own User program to User program, sometimes the Delay FX which is part of the program will not load on either side of a Split. This seems to happen when I change programs quickly. If I reload the program again the Delay FX is back as it should be.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: CPN37 on August 31, 2019, 05:56:19 AM
I thought I’d add another bug which Carson has already tested and confirmed to be a software issue that he’s added to the list for a future update, just in case anyone else comes across it too.

I noticed that for one of my own patches, where I have assigned the Modulation wheel via Mod Slot 1 to pitch oscillator 1 down an octave when pushed all the way to the upper position, ie:

Mod Slot 1
Source: ModWheel
Amount: -24
Dest: Osc1Freq

that the notes G#, A, A# & B were sounding different - a little quieter - than the other notes on the keyboard in a certain octave, when Osc1 was using a Sawtooth waveform. It turns out that this behaviour is way more noticeable if you choose a Triangle waveform instead for Osc1, those four notes sound like they are sawtooth waveforms whereas every other note on the keyboard sounds like a triangle, as they should. This, when the Mod Wheel is pushed to the maximum.

The problem is the same for Oscillator 2, if you set the Mod slot 1 Destination to Osc2Freq too.

It only happens on one octave, so if Osc1 Freq is set to C2, and the ModWheel is pushed all the way up, then the strange G# to B notes are at the very upper octave.

Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: creativespiral on August 31, 2019, 12:09:29 PM
Just adding this here, as it seems to be a good repository of this info:

Support Ticket 48090 - Confirmed Bug

Gated Sequencer does not advance properly when using both layers in Key Step mode.

A fix to this would improve Voice Modeling capabilities with the Rev2, and also allow proper working patches with dual layer syncopated sequences using the Gated Sequencer key step with arp.   We'll be able to create some really advanced melodic motion patches using both layers. 
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Razmo on August 31, 2019, 12:57:59 PM
I can add, that the timing of starting a gated sequencer when synced to external clock is very jittery... It is impossible to align the onset of the sequence with other gear... I tried this by sending the exact same electrical signal from my V-Synth GT to both REV2 and PEAK via a physical MIDI splitter cable, sending clock signals and note on to both synths... peak playing a key synced arpeggio, The GT playing a looped and timesynced drumloop, and REV2 playing a gsynced gated sequencer sequence... The PEAK follows the GT 100% in time, but REV2 jitters the onset of the sequence differently on each and every new triggering... It sounds like if the PPQ counter in REV2 is not reset on retriggering the sequence.

Also, I wrote support about this a month ago and was promised a confirmation later... I have still not heard anything, and do not know if they forgot to write me back... But now the bug is listed here as well if anyone else have this problem.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Kasimir Effekt on August 31, 2019, 02:20:42 PM
Furthermore I can confirm that the midi clock signal generated by the rev2 is very unstable - at the midi out port you can measure constant fluctuations.
I‘m not sure sure if this problem already has been reported.



I can add, that the timing of starting a gated sequencer when synced to external clock is very jittery... It is impossible to align the onset of the sequence with other gear... I tried this by sending the exact same electrical signal from my V-Synth GT to both REV2 and PEAK via a physical MIDI splitter cable, sending clock signals and note on to both synths... peak playing a key synced arpeggio, The GT playing a looped and timesynced drumloop, and REV2 playing a gsynced gated sequencer sequence... The PEAK follows the GT 100% in time, but REV2 jitters the onset of the sequence differently on each and every new triggering... It sounds like if the PPQ counter in REV2 is not reset on retriggering the sequence.

Also, I wrote support about this a month ago and was promised a confirmation later... I have still not heard anything, and do not know if they forgot to write me back... But now the bug is listed here as well if anyone else have this problem.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Darrolav on September 11, 2019, 04:17:12 PM
Hello, anyone knows if the next firmware update will be announced anytime soon?
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: confinedsc on September 16, 2019, 05:17:22 PM
Is it a bug that the slew of the gated sequencer doesn't affect a sequence when it is routed through the mod matrix? 

Slew only works for me when you route the sequence to a parameter directly from the sequencer section, not the mod matrix.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Djinn on September 26, 2019, 07:44:36 AM
When will we see another update I'd love to see some new features! Let alone all these annoying bugs that need fixing... I hope the rev2 is not another example of dsi seeing its users just hanging in the wind with another unfinished product.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: workfloh on September 30, 2019, 01:27:18 PM
Hi.
I have a Question.
Is the Patch-Volume increase or decrease linear?

For example: I have two patches.
The volume of patch 1 is 80. The volume of patch 2 is 120.

When i decrease both with the value of 20 (patch 1 is 60 and patch 2 is 100 now), have i still the same volume ratio?

Thanks alot!
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: Larioso on October 10, 2019, 10:07:57 PM
Is it a bug that the slew of the gated sequencer doesn't affect a sequence when it is routed through the mod matrix? 

Slew only works for me when you route the sequence to a parameter directly from the sequencer section, not the mod matrix.

Yes, this would be a problem if true, one of the things I thought of doing - using mod matrix as well from gated sequencer.

Can anybody confirm this?

My module is still on the way, so will see which OS is on it when arriving next week.

What is the interval new OS releases?
A bit disturbing that 2 year old synth still have major bugs.
It could be I just return it.

Should have looked up forum before purchase.
Most things I've seen reported is not things I would use, like external clocks and such.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: noir on October 12, 2019, 10:28:55 AM
I just tested what it does on my rev2.

When the stored value = 0 and the pot is at at 63. I press misc, and turn up. After turning about 15 degrees up it shows 0.
Also the other way around. When I turn about 15 degrees down, the actual value is shown.

This makes me think that you don't have to reach the stored value but it appears that way. It just takes quite a turn to get the stored value on the display. Not just by touching it.

This is not the case for me. I have to turn the poti until it has reached the saved position. Tested it on many parameters.
Title: Re: BETA OS v1.1.5.9 Bug Report Thread
Post by: confinedsc on October 15, 2019, 02:48:00 PM

Yes, this would be a problem if true, one of the things I thought of doing - using mod matrix as well from gated sequencer.


Just to be clear, you can definitely route the gated sequencer through the mod matrix just fine.  The issue is that for example, if you modify sequence A slew with sequence B and then you route sequence A to osc pitch through the mod matrix, the pitch is not gliding gradually like it should from slew, it is jumping in quantized amounts.