The Official Sequential/DSI Forum

Major issues after upgrading to 1.1.4.27

Major issues after upgrading to 1.1.4.27
« on: January 09, 2019, 11:34:48 AM »
Yesterday I performed my first upgrade since I got my Rev2 16 voice (it was on some 1.0 version, do not remember exactly which). My Rev2 was working without any problems that I had noticed. The upgrade itself using MIDI-OX was without any error messages and I let the Rev2 perform its calibration routine. Once I started playing it, it immediately sounded really different. I've done some digging around to try to isolate the issue(s). Some of the things I noticed:


F1P1 LosVangelis2041, only layer A active: on C#5 and D5 there is suddenly a lot of modulation that can not be heard on other notes with the same patch

Initialize the basic program: Shape Mod for Osc1 seems not to affect the sound at all

Initialize the basic program, select Triangle for Osc 1: Shape Mod is working, but not between 2 and 5 o'clock


All of this is heard by using a headphone (AudioTechnica M50x) directly plugged in to the Rev2.

There is probably a lot more that is currently not working as expected. I am looking for options to resolve this. Can I install another version of the OS or will that get me into even more trouble?

I've mailed the text above also to Sequential Support. I really want this to be resolved quickly.

DSI Prophet Rev2 16 voice, Arturia Drumbrute Impact, Tascam DP-008 EX

cbmd

  • *****
  • 349
    • Sequential
Re: Major issues after upgrading to 1.1.4.27
« Reply #1 on: January 09, 2019, 12:05:38 PM »
Hi Jeroen,

I've replied to your inquiry through our support channels.  Please follow up with me regarding the issues you've encountered via email.

Thanks!
Sequential

Re: Major issues after upgrading to 1.1.4.27
« Reply #2 on: January 09, 2019, 11:21:00 PM »
Yesterday I performed my first upgrade since I got my Rev2 16 voice (it was on some 1.0 version, do not remember exactly which). My Rev2 was working without any problems that I had noticed. The upgrade itself using MIDI-OX was without any error messages and I let the Rev2 perform its calibration routine. Once I started playing it, it immediately sounded really different. I've done some digging around to try to isolate the issue(s). Some of the things I noticed:


F1P1 LosVangelis2041, only layer A active: on C#5 and D5 there is suddenly a lot of modulation that can not be heard on other notes with the same patch

Initialize the basic program: Shape Mod for Osc1 seems not to affect the sound at all

Initialize the basic program, select Triangle for Osc 1: Shape Mod is working, but not between 2 and 5 o'clock


All of this is heard by using a headphone (AudioTechnica M50x) directly plugged in to the Rev2.

There is probably a lot more that is currently not working as expected. I am looking for options to resolve this. Can I install another version of the OS or will that get me into even more trouble?

I've mailed the text above also to Sequential Support. I really want this to be resolved quickly.

Jereon, you've got me a little worried about my own Rev2 now. I had honestly never noticed that F1P1 had a layer B before (is this normal? is it a consequence of it being an 8-voice version), so I just turned my Rev2 on to have a look. Low and behold there is a layer B, but it is not active when I load that patch. I have recently updated to 1.1.4.27 too, but, like I said, I don't think it has ever been active on F1P1. That in itself is not too much of an issue, I guess.

The sound, however, very well may be.

I'm not sure what kind of modulation you are talking about, but if I go to edit layer B on that patch, the sound is all over the place, completely different to when I stack it with layer A and turn the volume of layer A down to zero. Is it possible for layers to effect each other even if the volume of one of the layers is set to zero? So I checked a bunch of supposedly one-layer patches and many of them seem to have a layer B that are not simply "Name of Patch (B)." This was quite a revelation to me! And some of these layer Bs sound "odd" to me...

I must mention that I turned the synth off, left it a few minutes, and turned it on again. Layer B on patch F1P1 seems "normal" now, but still different to when stacked with layer A and the volume on layer A is turned down to zero. But I cannot be sure that the previous, "weird" sound will not return. I guess I should also add, for what it is worth, that I was not listening through the headphone jack on the Rev2, but via headphones through my mixer (I understand that the polarity on the Rev2's headphone jack is reversed, and only for onw layer). I doubt this has much of an effect on the current issue, but I thought it might be worth mentioning.

So now I have no idea whether there is an issue with my Rev2 or the OS. Should I get in touch with support?

Razmo

  • ***
  • 2168
  • I am shadow...
    • Kaleidoscopic Artworks
Re: Major issues after upgrading to 1.1.4.27
« Reply #3 on: January 10, 2019, 01:28:29 AM »
For some reason it seems there are a few possible bugs with layer B on the REV2 that has still went under Sequential's radar as of yet... it's not only limited to the 8-voice version... it still have problems with the layer B sound going crazy sometimes with certain parameter settings (sounding like sample rate reduction, and this was acknowledged by DSI support and put on their Bug list)... I still get notes that suddenly cut out while playing that should not go out (like if i hold two keys with the left hand and play something with the right hand, then sometimes, the two keys held with the left hand will get cut out, even though they are held down... at other times it just cuts them out randomly without any clear pattern to it). if the later is related to layer B I cannot say... but there certainly are a few elusive bugs present here and there that seems to keep avoiding notice because they are hard to reproduce. Any reproducible bug should be sent to Sequential support with details about how to reproduce the bug, since it's obviously the only way Sequential put the bugs on their internal bug list... it's no use writing them on the forums alone.
If you need me, follow the shadows...

Re: Major issues after upgrading to 1.1.4.27
« Reply #4 on: January 11, 2019, 01:32:02 PM »
First I would like to share the solution by Sequential support (thanks a lot, Carson!). Since I did an upgrade from 1.0.x to 1.1.4.27 I basically introduced a lot of voice based changes to my Rev2. In my case the solution was to remove the previous calibration and re-calibrate again. Clearing the previous calibration can be done by pressing both TRANSPOSE keys and the GLOBAL key. Once the CLEAR CALIBRATION parameter is shown, press write. Then perform the normal calibration routine (global, calibrate, write).

Together with support I ran some additional checks on behaviour but all seems to be as expected now.
DSI Prophet Rev2 16 voice, Arturia Drumbrute Impact, Tascam DP-008 EX

Re: Major issues after upgrading to 1.1.4.27
« Reply #5 on: January 11, 2019, 01:49:05 PM »

Jereon, you've got me a little worried about my own Rev2 now. I had honestly never noticed that F1P1 had a layer B before (is this normal? is it a consequence of it being an 8-voice version), so I just turned my Rev2 on to have a look. Low and behold there is a layer B, but it is not active when I load that patch. I have recently updated to 1.1.4.27 too, but, like I said, I don't think it has ever been active on F1P1. That in itself is not too much of an issue, I guess.

The sound, however, very well may be.

I'm not sure what kind of modulation you are talking about, but if I go to edit layer B on that patch, the sound is all over the place, completely different to when I stack it with layer A and turn the volume of layer A down to zero. Is it possible for layers to effect each other even if the volume of one of the layers is set to zero? So I checked a bunch of supposedly one-layer patches and many of them seem to have a layer B that are not simply "Name of Patch (B)." This was quite a revelation to me! And some of these layer Bs sound "odd" to me...

I must mention that I turned the synth off, left it a few minutes, and turned it on again. Layer B on patch F1P1 seems "normal" now, but still different to when stacked with layer A and the volume on layer A is turned down to zero. But I cannot be sure that the previous, "weird" sound will not return. I guess I should also add, for what it is worth, that I was not listening through the headphone jack on the Rev2, but via headphones through my mixer (I understand that the polarity on the Rev2's headphone jack is reversed, and only for onw layer). I doubt this has much of an effect on the current issue, but I thought it might be worth mentioning.

So now I have no idea whether there is an issue with my Rev2 or the OS. Should I get in touch with support?

Funny how you still can find some stuff that was previously hidden. I just check F1P1 and I can not hear the things you described with Layer B behaving out of control and sounding different when played in isolation or stacked with Layer A. Rev2 directly to my headphones.

Really eratic behaviour is a good reason to get in touch with support. By now I've learned the Rev2 is capable of a lot of wild modulation. So if you have ruled out this is caused by extreme settings, you can always contact support.
DSI Prophet Rev2 16 voice, Arturia Drumbrute Impact, Tascam DP-008 EX

Re: Major issues after upgrading to 1.1.4.27
« Reply #6 on: January 13, 2019, 07:29:51 PM »
There is also this bug with layer B since the upgrade:  when a patch is called up via remote program change command, patch B volume is 0, meaning it's silent!

This does not happen when you manually select the patch, only when responding to program change commands.  I have a ticket open with support already.

And aftertouch still does not work with layer B. 
Moog One <> Prophet Rev2 16V <>  Andromeda <> Kronos 61 <> Nord Stage 2 HA76 <> Integra 7 <> Minilogue XD module <> Blofeld desktop <> Behringer Model D <> Minitaur <> Slim Phatty <> Matrix 1000 <> Micron <> Privia PX-5S <>  MODX7 <> TG77 <> ASM Hydrasynth <> Perform VE <> FCB1010

Re: Major issues after upgrading to 1.1.4.27
« Reply #7 on: January 14, 2019, 12:17:27 AM »
Thankfully, I have not been able to replicate the strange layer B behaviour on preset F1P1. However, I have experienced the silent layer B when changing program remotely (not to mention a host of issues with Cubase). I'll try the clear calibration protocol and then recalibrate.     

Re: Major issues after upgrading to 1.1.4.27
« Reply #8 on: January 27, 2019, 01:46:58 PM »
I would like to add my experience with the 1.1.4.27 update. Bought it yesterday, got home and it froze up on me after about 10 minutes. Did it about a dozen times over the course of the next couple of hours. Also upon arriving at a patch called ďcanít kill me ď ( I think thatís what it was called) there was a ring modish characteristic that carried over to the other patches when I left that patch. Brought it back to the store, played another one in store only to have it do that same ring mod thing. Something really not good going on. Bummed as I had been eyeballing the rev 2 for many months.
-Mike

Razmo

  • ***
  • 2168
  • I am shadow...
    • Kaleidoscopic Artworks
Re: Major issues after upgrading to 1.1.4.27
« Reply #9 on: January 28, 2019, 05:49:15 AM »
I would like to add my experience with the 1.1.4.27 update. Bought it yesterday, got home and it froze up on me after about 10 minutes. Did it about a dozen times over the course of the next couple of hours. Also upon arriving at a patch called ďcanít kill me ď ( I think thatís what it was called) there was a ring modish characteristic that carried over to the other patches when I left that patch. Brought it back to the store, played another one in store only to have it do that same ring mod thing. Something really not good going on. Bummed as I had been eyeballing the rev 2 for many months.
-Mike

That "ringmod" bug has been a persistent one for some time now... it was presumably "fixed" twice... I have not experienced it since the second time it was fixed... your problem has probably been that those REV2's you've tried had older OS versions... the latest OS beta is by far the most stable I've encountered thus far...
If you need me, follow the shadows...