The Official Sequential/DSI Forum

Pro 2 BETA 1.4.0.5 Bug reports

Re: Pro 2 BETA 1.4.0.1 Bug reports
« Reply #100 on: January 01, 2019, 06:19:43 AM »
When running the arpeggiator, adjusting the sequencer length in the menu causes the arpeggiator to stop. This happens both latched and unlatched, though in latched the notes just hang. If one then holds notes down again, it restarts but sounds like the envelopes are at the end of their cycles and not being triggered anew.

Re: Pro 2 BETA 1.4.0.1 Bug reports
« Reply #101 on: January 01, 2019, 07:21:53 AM »
Parameter revert doesn’t seem to work on “filter envelope amount” “velocity amount” or “delay” in the “F1 Env Amt” and “F2 Env Amt” tabs. Using “revert all” does work though.

For reference, I was using patch F6 P27 Dynamic Brass

I wonder if it might be useful for the screen to jump back to showing the parameter being reverted as soon as the button, knob or encoder is pressed or turned; this would give immediate visual feedback that the parameter has been reverted. Or maybe just a quick message to say it’s been done as I can see that users might want to continue holding the “revert param” button to further adjust other values without having to press it multiple times.

Re: Pro 2 BETA 1.4.0.1 Bug reports
« Reply #102 on: January 01, 2019, 09:16:25 AM »
Routing “slider position 1” to “filter 2 decay” or “filter 2 decay” results in reverse behaviour; raising the slider causes the decay time to fall even though the modulation amount is set to positive.

Re: Pro 2 BETA 1.4.0.1 Bug reports
« Reply #103 on: January 01, 2019, 12:11:12 PM »
In paraphonic mode I’m only able to play three notes; the fourth one always steals the first played of the other three. Not sure if it’s firmware or hardware as I just got it today. All four oscillators do work as I can make 4-oscillator patches in mono mode. I’ve submitted a ticket.

This is either temperamental (or maybe user error). Does the behaviour of paraphonic mode depend heavily on having at least some attack and decay dialled in on the amp envelope as opposed to just a “gate” setting (zero attack, zero decay, maximum sustain)? I ask as for the moment it seems to be working and that’s the only significant change I made. Though why would it previously only play 3 notes? Seems a bit random.

Re: Pro 2 BETA 1.4.0.1 Bug reports
« Reply #104 on: January 02, 2019, 10:17:22 AM »
In paraphonic mode, assign Osc 1 to modulate filter 2’s state and set an amount. Changing oscillators in the mod matrix results in a timbral shift even though they are tuned to the same pitch, have the same wave shape and have the same output level.

Re: Pro 2 BETA 1.4.0.1 Bug reports
« Reply #105 on: January 03, 2019, 05:22:42 AM »
In paraphonic mode I’m only able to play three notes; the fourth one always steals the first played of the other three. Not sure if it’s firmware or hardware as I just got it today. All four oscillators do work as I can make 4-oscillator patches in mono mode. I’ve submitted a ticket.

This behaviour seems to come and go. It started happening again yesterday.

Re: Pro 2 BETA 1.4.0.1 Bug reports
« Reply #106 on: January 04, 2019, 05:50:36 AM »
Dear Sequential! First of all, thank you for working hard to improve this excellent instrument which I really love!

I guess I have found a bug. My related setup is an MPC X and the Pro2. I only started to experience the following after 1.4 was installed. The phenomenon is that if I push any of the MPC’s function buttons, such as pad banks, channel mixer, pad mixer, etc which normally don’t send any CC or NRPN messages (I have tested it with midi monitoring, they truly don't send them) while running a sequence, an unwanted sound appears in the current patch running on pro2 (an arpeggiator). It sounds like when you change between patches while playing. I guess you will know what I mean. As for the MPC: it’s sending MIDI Clock, without MMC and connected via normal MIDI to the Pro2 back and forth (first I used the USB going back to the MPC, then I changed to MIDI to eliminate the possible error sources and of course my MIDI cables are OK, but at the end I found that these don't relate to the issue).

The phenomenon only occurs when I put the Pro2 in slave mode. Without slave mode, the arpeggiator runs off from the beat, even if ARP BEAT SYNC is turned on, but I don't experience the phenomenon. I have tried turning on and off receiving and sending CC or NRPN messages, but neither this and nor the other setting options in the Globals seem to affect this weird sound effect. It only disappears when the Pro2 is not in slave mode (but then it becomes inaccurate). I also tried to plug out the midi cable going back to the MPC, but it also didn’t affect the presence of the weird sound phenomenon. I think I have tried almost every combinations, but seemingly this somehow relates to the Pro2 being in slave mode (I always said, slavery is a bad thing… :D). Do you have any ideas what could this be? If you find the cause, please let me know what made this happen, I would like to understand it. I have never experienced such thing on my OB6 nor on other synths ever. Thank you in advance! András Lászlóffy, Absolute Hit Space, Hungary

Re: Pro 2 BETA 1.3.1.23 Bug reports
« Reply #107 on: January 09, 2019, 12:01:08 AM »
One bug I noticed is that old patches that used exponential FM sound very, very different. It seems to me that exponential FM is behaving very different after Linear FM was added.
Take for example preset P65 F7 "Masheen", if you remember how that one sounded, you'll hear how different it is now, sounds like a completely different patch.
PM sent. Did you get this solved? If so, how?