The Official Sequential/Oberheim Forum
SEQUENTIAL/DSI => Pro 2 => Topic started by: cbmd on July 27, 2018, 04:51:08 PM
-
Please post any bugs you might find on the 1.4.0.1 OS to this thread.
Thanks!
-
Great, but is there any manual for the added features?
Or do we have to explore for ourselfes (bug reporting is difficult then, when it is not clearly stated how it SHOULD work)
-
Great, but is there any manual for the added features?
Or do we have to explore for ourselfes (bug reporting is difficult then, when it is not clearly stated how it SHOULD work)
Will be lovely to clear up a few things; for example, now you've squashed the MIDI clock bug (thanks!!) I'm exploring the arp and sequencer for almost the first time. However, the arpeggiator seems key-synced so I'd like to check if that is intentional or there's a setting I've missed to turn this off.
Updated very much appreciated! Filter 2 is behaving very differently - in a good way!
Not sure if this a bug: If you adjust the Retrigger parameter (Misc Params) while sequencer or arpeggiator playing, playing stops. Have a few other possibles but will post in correct place when I know more.
-
Do you need ver 1.3 installed to install the latest version. I have Ver 1.2.3.2 currently installed.
-
Great, but is there any manual for the added features?
Or do we have to explore for ourselfes (bug reporting is difficult then, when it is not clearly stated how it SHOULD work)
ARP beat sync on/off is available in the globals.
Exponential/Linear FM toggle is in 4th soft tab of oscillator screens.
Alternate Tunings is available in the globals
Sequencer lock on/off is available as soft button 4 in main program screen.
Sequencer Direction is located in 4th soft tab of sequencer/arp screens.
MIDI CC OUT and CV Gate out are available as modulation destinations in the sequencer.
Switchable high/low DDL feedback available in 2nd tab of delay screens.
Add rest/tie while recording to track 1 of sequencer should be pretty intuitive. While recording, pressing a step past the current step will add rests all the way to the target step. Ties work the same as when you are not recording.
Hope this helps!
-
Do you need ver 1.3 installed to install the latest version. I have Ver 1.2.3.2 currently installed.
You should not need to update to the 1.3 OS prior to updating to the latest beta. Just make sure to reset your globals once it has been installed.
-
I don't have any bugs to report other than this update has brought tears of joy to my eyes!!!
-
ARP beat sync on/off is available in the globals.
Exponential/Linear FM toggle is in 4th soft tab of oscillator screens.
Alternate Tunings is available in the globals
Sequencer lock on/off is available as soft button 4 in main program screen.
Sequencer Direction is located in 4th soft tab of sequencer/arp screens.
MIDI CC OUT and CV Gate out are available as modulation destinations in the sequencer.
Switchable high/low DDL feedback available in 2nd tab of delay screens.
Add rest/tie while recording to track 1 of sequencer should be pretty intuitive. While recording, pressing a step past the current step will add rests all the way to the target step. Ties work the same as when you are not recording.
Hope this helps!
It does - I knew there must be a switch for the ARP ;)
Apart from the DDL setting, found the rest; although when I sent the tuning sysex there was no message on the screen and I seem to have just 1 named tuning, possibly that's correct though?
Cheers for making one of my fave instruments better.
Paul
-
The screen will not update to indicate the reception of the alternate tunings. If they were loaded correctly, there should be 17 different tunings available to select from.
-
I think I found a bug, after updating Filter 2 is not closing fully and when turning the cutoff there are no changes in sound until about 95. Re-calibrating the filters doesn't fix it, tried a few times already.
-
Do you need ver 1.3 installed to install the latest version. I have Ver 1.2.3.2 currently installed.
You should not need to update to the 1.3 OS prior to updating to the latest beta. Just make sure to reset your globals once it has been installed.
Thanks!
-
I think I found a bug, after updating Filter 2 is not closing fully and when turning the cutoff there are no changes in sound until about 95. Re-calibrating the filters doesn't fix it, tried a few times already.
Thanks for the report. Would you please try setting the cutoff pot to its minimum setting, then run the filter calibration?
The behavior you described seems related to known bug which was purportedly fixed in the BETA OS. We might need to look at it further.
-
I think I found a bug... if I go into Oscillator mods and crank the FM up while a key is pressed down, it will sometimes send me to the sequencer note screen.
I still love this update though!
-
Cancel mine. I still had Midi Osx up with the Pro 2 plugged in. User error.
-
I already tried that a few times (minimum setting) to no avail. After around 7 calibrations or so, it went back to closing almost fully even though I didn't do anything different.
I think I found a bug, after updating Filter 2 is not closing fully and when turning the cutoff there are no changes in sound until about 95. Re-calibrating the filters doesn't fix it, tried a few times already.
Thanks for the report. Would you please try setting the cutoff pot to its minimum setting, then run the filter calibration?
The behavior you described seems related to known bug which was purportedly fixed in the BETA OS. We might need to look at it further.
-
The behavior you described seems related to known bug which was purportedly fixed in the BETA OS. We might need to look at it further.
It's fixed for me - an unexpected treat given our previous discussions about it. More than chuffed!
Am I imagining it - or does filter 2 resonance go further too?
-
Great, but is there any manual for the added features?
Or do we have to explore for ourselfes (bug reporting is difficult then, when it is not clearly stated how it SHOULD work)
Sequencer lock on/off is available as soft button 4 in main program screen.
Very excited about this update, thank you!!! Question what does the Seq. Lock do?
-
amazing update!! thank you so much!
my SEM filter is also not closing all the way like mentioned above.
i am also wondering about modulation destination shortcuts, like on the P12 where holding an lfo or envelope button and then twisting a knob where you want the modulation destination to be makes it a destination for that controller. know what i mean? what are the prospects of getting something like that for the pro2? quality of life stuff.
but damn!! im so happy with this update!
-
The SEM filter's cutoff is known to not go as low as the 2040 filter. What you are hearing may be expected.
The ability to hold an envelope/LFO button and auto assign its dedicated destination by turning a parameter is on our list of items to consider for implementation.
-
Thanks so much all at DSI for this update! Just awesome :D I am about to try it out now. will post any bugs that i come across but thank you so much again! :D
-
Great, but is there any manual for the added features?
Or do we have to explore for ourselfes (bug reporting is difficult then, when it is not clearly stated how it SHOULD work)
Sequencer lock on/off is available as soft button 4 in main program screen.
Very excited about this update, thank you!!! Question what does the Seq. Lock do?
I was a bit baffled by this to start with but I think when Seq Lock is on it keeps the current sequence in memory and when you change to a different patch it will still keep using the sequence from where you originally turned Seq Lock on.
That's my impression of it but I could be wrong, I just noticed it by trial and error :)
-
Super update - thank you DSI team!
The ability to hold an envelope/LFO button and auto assign its dedicated destination by turning a parameter would be very helpful - so please, please get it implemented in the fantastic Pro 2.
-
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.
-
A word of caution... Don't make the same mistake as me and think that your Cue/Playlist will be ok without doing a backup! I didn't realise I'd lose all my stored Cue/Playlist settings when doing the reset globals stage of the update.
Oh well, you live and learn :)
-
I was a bit baffled by this to start with but I think when Seq Lock is on it keeps the current sequence in memory and when you change to a different patch it will still keep using the sequence from where you originally turned Seq Lock on.
That's my impression of it but I could be wrong, I just noticed it by trial and error :)
From a brief play yesterday, it leaves the Sequencer button lit, as if you'd saved it that way in the patch. So if a patch's pattern is running already, the new one's will take over.
I've always thought it rather odd that when you press the sequencer's play button it doesn't do anything except tell you to press the sequencer button if not lit (a bit Hitch Hikers Guide To The Galaxy that one). This at least lets you be in 'sequencing mode' or not, regardless of your patch stored settings.
-
Update - I'm quite wrong ;)
-
I also notice a big difference in patches i used the exp. FM on the previous version.
They sound different with less "power" on the FM modulation. I checked if the exp. FM is loaded with the patch-thats not the problem. Bug in FM implementation of exp. FM?
-
If all LFOs selected the dedicated encoder don´t effect the parameters (Frequency, Shape, Destination) anymore. Only the four soft knobs work. Bug?
-
Here’s a doozy of a bug (1.3.1.23):
Press the Seq Lock button on any patch and immediately turn the Program Select encoder in any direction: the sound will change, but the program name will stay displaying the name of the program you had selected when you pressed “Seq Lock’.... This persists even even if you change to say a ‘Misc Params’ or ‘Oscillator’ screen for example.
-
Here’s a doozy of a bug (1.3.1.23):
Press the Seq Lock button on any patch and immediately turn the Program Select encoder in any direction: the sound will change, but the program name will stay displaying the name of the program you had selected when you pressed “Seq Lock’....
Yes I noticed that but wondered if it was deliberately showing the name of the sequence patch? I suspect you are right thought, it is a bug :)
-
Here’s a doozy of a bug (1.3.1.23):
Press the Seq Lock button on any patch and immediately turn the Program Select encoder in any direction: the sound will change, but the program name will stay displaying the name of the program you had selected when you pressed “Seq Lock’....
Yes I noticed that but wondered if it was deliberately showing the name of the sequence patch? I suspect you are right thought, it is a bug :)
I wonder if they could add a function using the “compare” button that lets you see both the patch from which the sequence was taken and the patch whose sound is currently being used to play that sequence.
-
Possible bug - sync to an external clock only works in round BPM? I've been using my Elektron Octatrack as source and noticed very sloppy delays in the Pro2. When I round up, they sound much better.
-
Possible bug - sync to an external clock only works in round BPM? I've been using my Elektron Octatrack as source and noticed very sloppy delays in the Pro2. When I round up, they sound much better.
Hi Bong Mystic. Can you please make a brief example demonstrating this behavior to us and email it to support (at) davesmithinstruments (dot) com? Thanks!
-
It would also be a good idea to try to test the delays with a secondary MIDI CLOCK source. I've checked a Pro 2 slaved to Ableton with a tempo of 100.5 and am not noticing any troubles with clock sync'd delay times.
-
It would also be a good idea to try to test the delays with a secondary MIDI CLOCK source. I've checked a Pro 2 slaved to Ableton with a tempo of 100.5 and am not noticing any troubles with clock sync'd delay times.
OK, will do. I've been using an Octatrack as master and noticing things not very tight but that it seemed 'right' when I changed tempo to a round number. Another delay running from same clock always very tight so have never suspected it.
Will do proper digging tomorrow and send audio/details.
Thanks.
-
Nice update! Its good to see Pro 2 receive so much love. Hope to see future DSI designs having a similar sequencer.
-
It would also be a good idea to try to test the delays with a secondary MIDI CLOCK source. I've checked a Pro 2 slaved to Ableton with a tempo of 100.5 and am not noticing any troubles with clock sync'd delay times.
Good call. I spent more time testing today and discovered that the clock source and tempo are indeed relevant. I'd been working at low tempii (e.g. 60.6) and noticing a degree of flam between the delays and initial notes. Changing the clock source from the Octatrack to my Cirklon sequencer, the flam is almost entirely eliminated - and hardly noticeable at higher tempii.
I had also not been comparing like to like, having my 'good' delay (an Elektron Analog Four) running in mono while forgetting to do the same for the Pro2 delays.
So it's all good, apologies for the over-eager report. (Now back to trying to get those tunings to load ;) )
-
So it's all good, apologies for the over-eager report. (Now back to trying to get those tunings to load ;) )
Did you or anybody else get the tunings to load? I tried a few times after I updated the os with no issue but the tunings 2-17 are still blank.
-
Did you download the separate tuning file? And load it via sysex after you updated to the os beta?
That worked for me.
I tried to load the tunings before updating the os. It didnt work. But it worked to load them after i updated the os.
When loading in the tunings there should be no feedback on the oled display at all.
-
Did you download the separate tuning file? And load it via sysex after you updated to the os beta?
That worked for me.
I tried to load the tunings before updating the os. It didnt work. But it worked to load them after i updated the os.
When loading in the tunings there should be no feedback on the oled display at all.
Yup, i did all that. Updated OS first, verified working. Sent tuning sysex, no response as anticipated. But also no change to the alt tunings 2-17. Tried a few times. There must be a trick to it?!? Does it matter what state the synth is in, global settings or something I'm missing? I just turn it on and send the tuning file (via usb, worked fine for os,) but so far no change. I'll keep at it and hopefully it will stick... i'm looking forward to this particular feature!
-
Not a bug:
The ARP Beat Sync is a long time coming. Could it be implemented for the sequencer as well? We can't always be 'on time' when playing back a sequence and key transposing ;) Or at least buffer change , or ensure sequence plays till end before transpose...however way you want...BEAT SYNC for the Sequencer as an option. ..Thank you.
-
Try turning RESTART OFF in the sequencer parameters. This will assure the sequence doesn't restart when you hit a key off time when transposing the sequence.
-
Hey,
The screen will not update to indicate the reception of the alternate tunings. If they were loaded correctly, there should be 17 different tunings available to select from.
I'm having problems with the new tunings ...
In Globals I have an entry for "26. Scale (Alt Tunings)" and if I scroll through them all there are 17 numbered entries but all the titles are the blank except the first which says "1. Equal Temperment"
If I select any of the tunings apart from the first, the tuning is the same but the timbre is different - kind of muffled with lots of highs/mids missing and quiet (with the program I was testing it on_.
I updated the o/s first and then tunings.
thanks
-
Double check that your Sysex Cable global parameter is set to the correct port (MIDI or USB). Try closing/reopening sysex librarian/midi ox and try the transmission again.
-
Thanks!
Alt scales now showing up in Globals :)
Double check that your Sysex Cable global parameter is set to the correct port (MIDI or USB). Try closing/reopening sysex librarian/midi ox and try the transmission again.
-
I know this is my own pet feature that I want, so take this "bug report" FWIW.
I still can't get the sequencer to act as a pure control sequencer when in paraphonic mode. In Mono mode, I think it's working fine.
From what I can tell, when the Sequencer is enabled, it's like it is reserving a note to itself - even if I have Notes: Off on Track 1.
Use this experiment on a factory paraphonic patch Cascades P2 F5. Play a 4 note paraphonic chord. Nice isn't it?
Now enable the Sequencer. Select Track 1. Turn Notes: Off. My expected behavior is that Track 1 will not affect the notes of the synth engine.
Press play. Here that sequencer taking over a note? You can hear a sustained note.
Turn the level of all oscillators down - all to zero. The note is still there. In fact, its the Sub of Osc 1 that is sounding. The Sequencer, some how, is opening the envelope of just the sub of OSC 1? What?
The destinations of all sequencer tracks is None on this factory patch. As far as I can tell, the Sub of OSC1 is not a destination in the mod matrix.
So, needless to say, this is breaking paraphonic mode when the sequencer is enabled.
It's like the Sequencer is reserving a note even if I set Notes: Off. And it appears to be reserving the Sub?
It's weird. Try to play that 4 note chord with the sequencer on. It's totally wrong. Turn sequencer off, then play your chord, then back on etc... When the sequencer is on, you'll hear that Sub sticking to the lowest note that has been played since the sequencer was enabled.
Closer, but it still doesn't work the way I am hoping we can get it to work.
When in paraphonic mode, the Pro2 seems smart about what note it's going to assign to OSC1, because OSC1 has the sub it seems to dynamically assign the lowest note to that oscillator. Seems pretty smart.
But when the sequencer is playing, even with Notes: Off, Mute: On/Off, it's like the Sequencer has reserved the Sub or the voice with the sub, or the priority is all out of whack. Feels like I'm playing with 2 or 3 paraphonic voices.
Very confusing.
-
Alt tunings file will not load. 1.3.1.23 loaded, sysex enabled via usb. Tried restarting sysex librarian application. Send file shows no status on pro2 display, no tunings loaded, just equal temperment and all the others are blank.
-
Alt tunings file will not load. 1.3.1.23 loaded, sysex enabled via usb. Tried restarting sysex librarian application. Send file shows no status on pro2 display, no tunings loaded, just equal temperment and all the others are blank.
Do you have a specific MIDI channel set for your Pro2? One of the things I did to mine was set channel to 'All' before sending tunings.syx. Not sure if that did it but it worked in the end.
-
I am not convinced the Tuning file is loading correctly. I too had similar problems but eventually got it to load. However, it seems the display names in ‘Global / 26. Scale (Alt Tuning)’ window are not correct, and who knows if any other bits and bytes have gone astray.
Scales:
1. Equal Temperament
2. Harmonic Series
3. Carlos Harmonic Twelve Tone
4. Meantone Temperament
5. 1/4-Tone Equal Temperament
6. 19-Tone Equal Temperament
7. 31-Tone Equal Temperament
8. Pythagorean C
9. Just Intonation in A with 7-limit Tritone at D#
10. 3-5 Lattice in A
11. 3-7 Lattice in A
12. Other Music 7-Limit Black Keys in C
13. Dan Schmidt Pelog/Slendro
14. Yamaha Just Major C
15. Yamaha Just Minor C
16. Harry Partch 11-limit 43 Note Just Intonation
17. Arabic 12-Tone
Displayed Name:
1. Equal Temperament
2. HrmA1-60
3. HrmA-12T
4. Meantone.3
5. 1/4TonET.4
6.19ToneET.5
7. 31ToneET.6
8. PythagoC.7
9. JIA7/5D#.8
10. 3-5LattA.9
11. 3-7LattA.10
12. 7.LimBlkC.11
13. PelSlenB.12
14. JIMajYam.13
15. JIMinYam.14
16. Partch11.15
17. Arabian C
Correct Name:
1. Equal Temperament
2. HrmA1-60
3. HrmA-12T
4. Meantone
5. 1/4TonET
6.19ToneET
7. 31ToneET
8. PythagoC
9. JIA7/5D#
10. 3-5LattA
11. 3-7LattA
12. 7.LimBlkC
13. PelSlenB
14. JIMajYam
15. JIMinYam
16. Partch11
17. Arabian C
-
That's just a display bug. On our list!
-
Turns out the naming issue was literally mis naming in the file itself. A new Alt tunings file has been loaded to the OS download thread which fixes the names.
Thanks!
-
Probably a dumb question but I'll ask anyway :)
I've not bothered loading the alt tunings as I can't see me needing them, would that be a problem? Are these tunings an optional extra or should I go ahead and load them?
-
Don`t know if this is bug or a feature:
I wonder why a OSC FM Setting of 255 is not the max?
You can push this by adding modsources to it (Slider or DC pushes the FM amount further).
Can`t we dial in max fm amount without using several mod sources?
-
Are these tunings an optional extra or should I go ahead and load them?
Completely optional. Won't hurt anything if you don't load them.
-
Can`t we dial in max fm amount without using several mod sources?
The intended max value of a given parameter is the amount you can get to using the knob. We allow for extra range through the mod matrix as a way to push things outside "normal" operation if so desired, thus extending the sonic possibilities.
-
Try turning RESTART OFF in the sequencer parameters. This will assure the sequence doesn't restart when you hit a key off time when transposing the sequence.
I had an opportunity to test this tonight. It's not as bullet proof as the new ARP BEAT SYNC. Be cool if it could be.
-
We know the program name does not update when locking the sequence (great feature from the Evolver btw!)
It would be great if on the program screen it displayed the locked sequence bank and program numbers in the soft button 3 location or elsewhere.
-
Can`t we dial in max fm amount without using several mod sources?
The intended max value of a given parameter is the amount you can get to using the knob. We allow for extra range through the mod matrix as a way to push things outside "normal" operation if so desired, thus extending the sonic possibilities.
this makes kind of sense - your sense ;D
Love the Pro2
-
Can`t we dial in max fm amount without using several mod sources?
The intended max value of a given parameter is the amount you can get to using the knob. We allow for extra range through the mod matrix as a way to push things outside "normal" operation if so desired, thus extending the sonic possibilities.
this makes kind of sense - your sense ;D
Love the Pro2
Agreed.
https://youtu.be/4xgx4k83zzc
-
Hi, I have a few bugs so far and will continue to post links of what I find as I come across things.
1. I am not sure if this is a bug but it sure behaves different to what I would expect. I am trying to sequence and control my moog dfam (osc 1 of dfam) via gate and cv out from the dsi pro 2 sequencer. now i setup the correct settings in menu like 'keytrack 127 to cv out 1' and then 'dc -64 to cv out 1' and when i record via the keyboard a sequencer pattern into seq track 1 the pro 2 and dfam play the same notes when I have the volume of both up. now my problem is that when I go into seq 1 on pro 2 and 'mute' the track..it no longer sends gate or sequences the dfam. I want to sequence my dfam from track 1 and be able to do other stuff on the pro 2 without it also playing the same sequence. I try other things like copying the seq 1 track to another track which i make cv 1 out..but now the 2 tracks add in cv voltage and now the dfam plays almost out of range..If you could investigate this Carlsen and try out some stuff similar I think you will know what I mean. Also I tried sequencing my moog sub 37 via midi out channels from sequencer and the having the midi all selected in the global menu didn't pick up the sub37. I'll have to try the midi sequencing out again but I remember that it worked before update now something with the midi sequencing didn't work. If you could investigate this also Carlsen that would be great. I will post more if I find more bugs. Cheers and thanks :)
-
Hey there Albywelch,
Note Track 1 will always be tied to the gate out. In this case, I would suggest that you first disable the note number to CV out modulation. Keep the negative DC modulation to CV out 1. Next, copy track 1's sequence to track 2. Assign track 2 to CV out 1. Select track 3 and select the destination as CV Trig out 2. CV out 1 will now send the CV/pitch voltage and CV out 2 will act as the gate.
Concerning the MIDI assignments, first thing to check is that some velocity value is set per step of the track.
Hope this helps!
P.S. It's CARSON, not Carlsen :D
-
In some respects I'm pleased to see that the wiping out of my Cue/Playlists was a bug but I do wish I'd waited until this newest version to update now! ;)
Edit - yes I do know I should have taken a backup first :)
-
haha my bad calling you carlsen..don't know why i thought that, must of been watching too much magnus carlsen the chess player haha.
Thank you very much for your reply Carson! That fixed those 2 issues..thanks! :)
-
After this Update when trying to change my Midi Channel it freezes.. cant change Midi Channel afterwards need to restart Pro2
-
Please reset your global parameter preferences and check whether the freeze is still present thereafter.
To reset the globals, press the GLOBAL button, navigate to the RESET GLOBALS menu item, and select the menu item.
-
Not a bug because it's always been this way... but is there any reason I can't just hit play on the sequencer and have it start playing? If the sequencer button can flash to show it knows I've pressed play, could it instead turn on and save me a button press?
Would be a sweet time-saver.
-
Am I missing something with the arp beat sync? Got a rock solid clock going on via a USAMO and it's enabled in the global menu. Isn't in time with the beat.. it still starts every time I hit a key instead?
-
Arp Beat Sync will cause any newly played notes to sync to the next clock divide value. So if you have a clock divide of 1/16, then the newly played notes will play on the next 1/16th step.
-
Question about 1.3.1.30RC
Fixed Bug: Increase modulation range of exponential FM by four
what does this mean? Will e.g. the slider with a value of 255 quadruple the mod depht to previous versions?
This will cause a massive change in saved sounds (e.g. with a sequencer track modulates the FM depht now 4 times as much)
Can you explain? Thanks!
-
Question about 1.3.1.30RC
Fixed Bug: Increase modulation range of exponential FM by four
what does this mean? Will e.g. the slider with a value of 255 quadruple the mod depht to previous versions?
This will cause a massive change in saved sounds (e.g. with a sequencer track modulates the FM depht now 4 times as much)
Can you explain? Thanks!
Hi mosen. I believe you had pointed out on an earlier BETA version that you had to add up mod slots to get the full range for exponential FM though the mod matrix. Now, with 1.3.1.32, you can get the full range with a single slot. [By full range here I mean a value of 255 for the dedicated OSC X FM parameter.]
Are you finding that patches you made using exponential FM on OS 1.3.0 or earlier sound different than with the 1.3.1.32 BETA OS?
-
I believe you had pointed out on an earlier BETA version that you had to add up mod slots to get the full range for exponential FM though the mod matrix.
Are you finding that patches you made using exponential FM on OS 1.3.0 or earlier sound different than with the 1.3.1.32 BETA OS?
This is right, i was suprised by the fact that the fm amount is not full range initial and can be stacked up with additional mod sources (first noticed this fact now, after having a pro2 for two years)
i compared patches with the sequencer modulating the FM Amount of OSC in Exp.Fm mode and yes - they sound very different (basically fm mod amount x4) now in the new OS. i think this new factor 4 would be a drastic change in fm control which will lead to many different users are disappointed that there patches sound different (need to lower the fm amount x 4). so, could live with the old bahevior and stack fm mods, or there will be an option which is saved with each patch. Like in the osc level page a button "4xFM" . that would be best i think - if this is possible to program i would go this route. thanks
-
I believe you had pointed out on an earlier BETA version that you had to add up mod slots to get the full range for exponential FM though the mod matrix.
Are you finding that patches you made using exponential FM on OS 1.3.0 or earlier sound different than with the 1.3.1.32 BETA OS?
This is right, i was suprised by the fact that the fm amount is not full range initial and can be stacked up with additional mod sources (first noticed this fact now, after having a pro2 for two years)
i compared patches with the sequencer modulating the FM Amount of OSC in Exp.Fm mode and yes - they sound very different (basically fm mod amount x4) now in the new OS. i think this new factor 4 would be a drastic change in fm control which will lead to many different users are disappointed that there patches sound different (need to lower the fm amount x 4). so, could live with the old bahevior and stack fm mods, or there will be an option which is saved with each patch. Like in the osc level page a button "4xFM" . that would be best i think - if this is possible to program i would go this route. thanks
We're not seeing what you describe here. Please send examples to support (at) davesmithinstruments (dot) com, and we can look further into it.
-
Im not sure if this has been noted: A bug I've found - holding one of the LFO selection buttons for a long press does not bring up the "edit all" screens like it does for the the OSC and Delay sections. I feel like I used to be able to do this....(maybe not?)
-
I just found another one I think: After some playing with the unit, My Pro 2 is now 'locked' playing only super high resonance and high octave sounds, no matter which patch I switch to. It's quite odd - after a restart it's fixed. I do not know how to replicate this one, but it has never happened before this update.! Thanks for the update btw - some amazing features.
-
I think I've found another (sorry!): Ive made one of the sequencer tracks look weird - like a long grey box, not the usual white bars. I was assigning the FM amount to sequencer track 6. Maybe this is normal but it doesn't seem right. The other sequencer pages work fine. I can also shorten the length of the grey bar by shortening the sequence. Here is a link to view it: https://www.dropbox.com/s/vy6uew2jvvy49mz/IMG_1177.jpg?dl=0
-
In 1.3.1.30 we are so close to having the sequencer act as just a modulation sequencer for paraphinc okay. Wow, this is great and has been a long time coming. Thank you very much for working hard on this guys!
Still, there seems to be some instances where I’ve found the sequencer wanting to open the envelope on just the sub oscillator. It’s like I’m playing and all the sudden, I can’t get the sub to stop playing if the sequencer is on. None of the primary oscillators play, but the sub does on its own. Weird.
Also, when the sequencer is not on, the voice selection does seem to prioritize OSC 1 as the lowest note so the sub is always the lowest note. But in paraphonic mode with the sequencer playing, that doesn’t seem to work the same and the sub oscillator (OSC 1) gets selected for various notes in a chord.
Also, in paraphonic mode with the sequencer on, with the sequencer set to trigger on sequencer (not Key), the sequencer doesn’t start on its own and waits until I play keys (reset is off). And setting the sequencer mode to key in paraphonic mode is pretty weird acting.
This is very close and I know it’s a hard feature to get right and not on the top priority, but these are my observations. Thanks again!
-
I haven't upgraded to 1.3.1.32 yet because I've been trying to verify that I'm hearing what I'm hearing on 1.3.1.30, but I'm certain I found a bug that hasn't been addressed. Otherwise I am loving every bit of these new updates!
When I create or use an FM patch and then switch to a paraphonic patch, the paraphonic voice sounds distorted and clipped.
The paraphonic voice will go back to normal, but only after selecting a couple other non-FM patches and returning to the paraphonic voice. In this clip I used 4 VoicesPara because it really highlights what I'm hearing:
https://www.dropbox.com/s/kvmsfu08jn168fm/Pro%202%20FM%20Bug.wav?dl=0
-
Thanks everyone. I'd just like to remind you all to please email support directly with your bug reports, along with steps to reproduce them. This forum thread is great for seeing if other users see what you see, too, but digging deeper should happen via direct communication with us. support (at) davesmithinstruments (dot) com.
-
Revert Parameter doesn't seem to work on the Filter Routing and Filter 2 Type (LP/BP/HP). Revert All works on these parameters.
-
With 1.3.1.35 I can now play paraphonic chords and notes with the sequencer running as a pure modulation source with no detectable bugs. DSI has fixed every single paraphonic play with sequencer modulation bug I could come up with.
Wow. Great job DSI and thank you!
-
With 1.3.1.32 and 1.3.1.35 the first note of a new sequnce is not played on the first cycle. I record on 5 patches (own patches) a new sequnce. The first note is not played (only on the first cycle). The tracks 2-16 are empty.
If i use a factory sound with the factory sequnce, all worked fine.
-
i test it again and the behaviour only occurs if sequencer restart is "on".
-
Send a note to their support email with an example of how to reproduce it. They are quite responsive right now, but eventually the window will close.
-
with 1.3.1.32 & 1.3.1.35, looks like I'm still have problems with local control OFF :
- impossible to set reset points in the sequencer tracks when it is off
- when I switch from sequencer to arp, seq button remains lit and step leds are still moving, and sequencer continues to play until I press some notes on the keyboard (don't think it behaved that way previously) and vice-versa, arp button remains lit when switching to seq (I have both buttons lit and have to deactivate manually)
- the seq play/stop button only works for stop, it doesn't work for play (clock in slave mode and receiving an external clock from the DAW in both cases). The only way to start the sequence is launching it from the daw
-
Oh, also it looks like the CC # are wrong for OUT2 in the sequencer tracks (also, what does "OUT 2" refers to ?)
-
Im not sure if this has been noted: A bug I've found - holding one of the LFO selection buttons for a long press does not bring up the "edit all" screens like it does for the the OSC and Delay sections. I feel like I used to be able to do this....(maybe not?)
Yes, that definitely used to work this way. It's also noted in the manual that if you want to edit the same parameter on all 4 LFOs simultaneously, one should press and briefly hold one of the LFO buttons. That this is not working anymore could be a byproduct of the quick assign method, though (if you hold an LFO button and then move any parameter to assign a mod destination).
-
Oh, also it looks like the CC # are wrong for OUT2 in the sequencer tracks (also, what does "OUT 2" refers to ?)
Out 2 refers to the MIDI Out 2/Thru port.
-
I’m contemplating buying another Pro 2, after having sold my last one due to bugs, instabilities, etc.
Generally it was related to how the synth functions when local was off, just laggy and unpredictable.
I’d like to use it as a main controller for the studio, plugged into Ableton Live. Does anyone with the newest OS have any current issues with the OS while using it that way?
-
The gate source is ext in, and the gate source of the sequencer is also ext in.
The sequencer is on but not running. If the ext in is triggering the synth while im in record mode inputting notes with the keyboard, the synth starts playing a held note which doesnt go away unless i turn the sequencer off.
-
Feature request here -- can there be a second mode of Local Off where note/velocity/aftertouch/modwheel/pitch are sent on a separate midi channel?
The Moog Sub 37 has a feature like this which REALLY helps avoid data collisions when using a deep external sequencer like a Squarp Pyramid, AND *it keeps all the onboard synth knobs active* while allowing a user to not get buried in keyboards. If this could be done, this instrument would be even more amazing than it already is.
KUDOS to all the other fixes/features in the Beta OS update. My Pro 2 feels 10x more stable and reliable!
-
I was wondering if in a future OS update you can add the feature to change the length of the sequence trigger tracks? Am trying to trigger my Nord drum 2 from my pro 2 and can't help but get double triggers (occasionally can get it after mucking around for ages with the Nord drum 2 setting and pro 2 trigger track levels to get a single trigger occasionally, but it is just unusable).
Devices like the Nord drum 2 expect really short triggers, shorter than the cv trigger sequences currently are..so yeah just wondering if this could be an option in the future? :)
Cheers and thanks,
Allan
-
Hi Sequential and Forum members!
Thank you so much for continuing Pro 2 OS development and feature enhancements. Owned this synth for 2+ years and its been an awesome center piece of my synth studio. Looking forward to new sound designs with the latest features. Linear FM yes!
Observation with Pro 2 OS Beta v1.3.1.41:
I noticed Alternate Tunings in the Global Menu do not apply to the Note Number in the mod matrix. When driving an outbound oscillator via CV (Note Number - 127 - CV Out 1) and selecting an alternate tuning in the Global Menu, the CV output voltage / outbound oscillator remains equal temperment. I'm not a huge user of alternate tunings, but, happened to notice this while exploring the cool new features in this OS Beta RC. Would be nice to have onboard and outboard CV controlled oscillators track the alternate tunings together.
Feature wishlist: polyphonic CV output e.g. play four notes, send those to each of the 4 CV outputs to outboard oscillators mapped via Note Number (1-4 maybe?) to CV OUT (1-4) in the modulation matrix. Also, would be nice to set the Oscillator ordering in Paraphonic mode. i.e. always start with Osc 1, after all keys are released, instead of fixed round robin.
Thank you !
-
On Beta 1.4.0.1 the first note of a sequence is still not played, if the sequencer parameter "restart" is "on". You could test it with preset F7 27 SleasyCoil and all presets with restart = "on" for the sequencer.
With 1.3.1.32 and 1.3.1.35 the first note of a new sequnce is not played on the first cycle. I record on 5 patches (own patches) a new sequnce. The first note is not played (only on the first cycle). The tracks 2-16 are empty.
i test it again and the behaviour only occurs if sequencer restart is "on".
-
I was able to replicate the issue you noted with the first step not playing. The issue is permanently resolved if you switch the sequencer from 32 step mode to 16 step mode, then back to 32 step mode. Save the patch and you should be good to go!
-
Hi Carson and pro 2 members!
Just last week I bought my pro 2 and am very excited about it. Did the upgrade (1.4) yesterday and noticed that when sending midi out from the tempest and while muting one instrument, the sequencer on the pro 2 stopped running. Had to hit play on the tempest again to restart the sequence on the pro 2. This happened nearly everytime I muted an instrument. Changing from one beat to another gave no error.
-
Hi,
in the CC#-List of the manual i can't find a entry about CC# für Filter 2 Attack, Decay, Release and Sustain. Is there a reason?
Also, is there a possibility to Modulate Sustain of Filter 1/Filter2 and the Amp Section via the Modulationsmatrix or Trackmodulation? Often i need explizit to change these parameter.
Is there a reason how i can't change expizit the Sustainparameter?
Can this fix via update?
Thanx for u work and for this great update.
best regards
Helge
-
Thank you Sequential team for working so hard on the new firmware! I can now integrate the Pro 2 sequencer with my setup without any issues.
I agree with Chavycat that being able to use the alternate tuning with external gear via the CV out would be a blessing. I really think it would make the Pro 2 almost invaluable for a modular system due to its ability to save so many microtonal patterns.
best regards,
Adam
-
I have a bug with the pro2 1.4.1 OS - using the keyboard & with midi the Pro 2 is playing back 1 semitone too high - even off the init patch. The behaviour comes and goes - restarting the machine it will disappear - but resetting to the init, the tuning is out.... this is making the pro 2 very un-useable!
-
Try running a pitch and mod wheel calibration routine.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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
-
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?
-
Not sure how many of these are bugs and how many are examples of expected behaviour. Perhaps others can help.
It is currently impossible to assign the sub oscillator level as a sequencer destination using the sub oscillator level knob. I had to do it by scrolling through destinations in the menu.
Using a parameter’s knob to set the per-step level in the sequencer track does not give access to the knob’s full range (I’m in jump mode); this is only possible using the sequencer’s step level knob.
One can’t turn the “shape mod” knob to assign shape mod as a sequencer destination (it works via the “shape/noise” knob instead oddly).
-
Sequencer length change bug:
1. Latch+Hold to set Basic Program.
2. Press SEQUENCER button to switch sequencer on.
3. Hold down 17-32 button and press Reset to reset max lenght to 32 steps.
4. Press Play button. After the first 16 steps the pitch changes somewhere hi. It is not posible to change the pitch anymore, even when switch off sequencer, change osc pitch, change patch (program) or anything else. Power off/on is only solution to stop this behavior.
The same was in 1.4.0.1 already.
-
Sequencer length change bug:
1. Latch+Hold to set Basic Program.
2. Press SEQUENCER button to switch sequencer on.
3. Hold down 17-32 button and press Reset to reset max lenght to 32 steps.
4. Press Play button. After the first 16 steps the pitch changes somewhere hi. It is not posible to change the pitch anymore, even when switch off sequencer, change osc pitch, change patch (program) or anything else. Power off/on is only solution to stop this behavior.
The same was in 1.4.0.1 already.
Have you submitted this as a support ticket too? If not, please do so as it probably won’t get seen otherwise.
-
Submitted now.
-
installs and works nice so far - no bugs after few hours usage yet. thank you for your work!
-
Hello, I've first updated OS from 1.3.0.0 to 1.4.0.1, then from 1.4.0.1 to 1.4.0.5 and I am experiencing this:
When I recall a preset with arp or sequence active, if I press the Global button while sequence/arp is running, sound freezes for a moment. I have never noticed this on 1.3.0.0 but I am not sure if there was the same behavior. Hope this can be fixed. Thank you for this great instrument and support.
-
Hi, if i try to set a sequence in key mode the sequencer doesn't respond and come back to sequencer mode.
-
MY PRO 2 destroyed by latest update.
:'(
I did install the latest OS, and my pro 2 is now toally F....
I have an LFO on every sound including the basic patch. I can change the OSC just by changing the shape of the LFO.
I have tried to go back to 1.3 but same problem..Please help.
-
Please post any bugs you might find on the 1.4.0.1 OS to this thread.
Thanks!
How can we get into the BETA program? Open to everyone?
-
The beta versions are always available to all in the forums.
-
The beta versions are always available to all in the forums.
I see, my bad. thanks
-
The beta versions are always available to all in the forums.
I see, my bad. thanks
You’re welcome, enjoy :)
-
Hi,
Where can I download the latest version (1.4.0.5)?
I've installed 1.4 from 1.3 and I have a bug to report: the Alternate Tuning doesn't appear to work as the options in the Global menu only show numbers (up to 17) after the Equal Temperament setting, and they don't allow the patches to play properly.
I've reset the Global settings and unplugged USB cable.
Please advise!
I love this synth!
:-)
-
Hi,
Where can I download the latest version (1.4.0.5)?
You'll find the latest version over here: https://forum.sequential.com/index.php/topic,1223.0.html
-
Paraphonic sequencing sent to an external poly synth is resulting in hung notes all over the place in reverse, random, and ping pong modes. Works as expected in forward mode.
In this configuration, the alternate playback directions can only be used as a special effect as the target synth quickly reaches a sustained mess.
External synth is a single timbre on a Novation Summit.
-
Hello
I recently update to the newest firmware, and some of my patches with sequences sound different.
Any idea why, or how to fix it?
-
Hello
I recently update to the newest firmware, and some of my patches with sequences sound different.
Any idea why, or how to fix it?
could you specify in which way they sound different?
Like individual notes and their pitch being different or just the sound/timbre of them?
When I encounter this I check with a basic sawtooth patch weather the filters are working right. And if there happen to be slopes in the filter curve I recalibrate them (up to 5 times in a row testing).
Especially with resonance this can change the whole flavor of a sequence.
-
Hello
I recently update to the newest firmware, and some of my patches with sequences sound different.
Any idea why, or how to fix it?
could you specify in which way they sound different?
Like individual notes and their pitch being different or just the sound/timbre of them?
When I encounter this I check with a basic sawtooth patch weather the filters are working right. And if there happen to be slopes in the filter curve I recalibrate them (up to 5 times in a row testing).
Especially with resonance this can change the whole flavor of a sequence.
The sequence was a highly altered edit of a preset. There are crunchy tones where there were once smooth tones. I have checked every sequence for what may be causing it. I haven't had any luck. I recalibrated everything, but not the filter curves. The filters seems to be fine. I was a dummy for not backing everything up.
-
I saw this when linear FM was added. I had previously programmed some patches utilizing exponential FM, but after I updated the firmware with the linear FM addition, some of those patches/sequences changed. I haven't bothered to reprogram them yet, and in all fairness, I don't know for sure if that was the cause, but just an observation, and something you might check, if applicable.
-
Couldn't you try rolling back the firmware, see if the patches revert and then back up before reinstalling the latest firmware?
It could be that certain parameters were given a slightly different location in the code between versions; this would cause differences (but saving probably wouldn’t help anyway).
-
Couldn't you try rolling back the firmware, see if the patches revert and then back up before reinstalling the latest firmware?
It could be that certain parameters were given a slightly different location in the code between versions; this would cause differences (but saving probably wouldn’t help anyway).
I can try this. Where do I find older versions of the OS?
-
Couldn't you try rolling back the firmware, see if the patches revert and then back up before reinstalling the latest firmware?
It could be that certain parameters were given a slightly different location in the code between versions; this would cause differences (but saving probably wouldn’t help anyway).
I can try this. Where do I find older versions of the OS?
The main sequential website should have the latest official (non-beta) release of the firmware. At the very bottom of this page:
https://www.sequential.com/download-latest-pro-2-os/
-
MIDI Port 2 is set to Out, but it doesn't work. If I plug the same cable from the MIDI Out Port 1 it works as it should.
Not sure if it's a bug, but I don't see how it wouldn't transmit data when set to Out in Global.
-
Quick poll to Sequential moderators-- is it safe to assume beta 1.4.0.5 is no longer under active development?
Most recent supported firmware is 1.4.0.1 and alternate tunings are not properly implemented. Beta 1.4.0.5 seemed to attempt to rectify this but the tuning Sysex does not correct the issue.
-
Alternate Tuning Fix-- after updating your firmware be sure to 'Reset Globals'. The Alt tuning Sysex transfer (via Sysex Librarian on Mac) will then function as expected. Alternate Tunings are then present in slots 2-16.
Question is still open on the release status of firmware 1.4.0.5.
-
Hi,
Normally, if you play a single note with paraphonic sound it plays each oscillator sequentially .
After the update to 1.4.0.5 , it stops cycling oscillators after some chord is taken.
See the video attached.
I'm not sure it is related to 1.4.0.5, but I notice it after an upgrade.
Thanks,
Stas.
-
Please post any bugs you might find on the 1.4.0.1 OS to this thread.
Thanks!
Link for OS 1.4.0.5 Beta for PRO 2
-
"Request Global Parameter Dump" sysex message (F0 01 2C 0E F7) isn't working in OS 1.4.0.5 and 1.4.0.1.
MIDIOX Reproduction:
1. Request Program Edit Buffer Dump (F0 01 2C 06 F7)
ok works
2. Request Global Parameter Dump (F0 01 2C 0E F7)
the reply is 2 bytes of garbage
3. Request Program Edit Buffer Dump again (F0 01 2C 06 F7)
no reply
Pro2 doesn't accept any new sysex messages until the next reboot.
Or an initiate of sysex dump function (for example "Dump Current Program") from the globals menu will wake up again the "sysex listener".
(Tested with USB. The MIDI port doesn't work either, but I didn't analyzed that case)
-
Hi All,
I just installed Pro 2 BETA version 1.4.0.5 but I'm still having problems with my filter 2. When sweeping F2, has a point between 100 and 130 where the filter acts with wrong values.
I have tried initializing, clearing and calibrating the filters many times.
Is this something that can be solved with software or do I have a problem with my hardware?
Thanks !!!
-
Hi,
I have been talking to Sequential support and they have told me that I have to send my PRO-2 to repair my filter 2.
Sequential support has been very quick and kindly to reply and propose a solution.
Thanks !!
-
- When I update the OS, I can see an indication on the front panel, and checking under Globals confirms I've installed 1.4.0.5. But when I run the alternative tuning sysex with MIDI-Ox, I see no indication of data reception on the Pro 2. Is there a way to check that the alternate tunings update has been installed?
- This is more of a question than a bug report. The Pro 2 manual states that to start with an initialized patch, you press Global and turn Soft Knob 1 until you reach option 31, which the manual claims will be Basic Program. But the globals all have to do with MIDI and I/O, so 31 is CV 1 Out Scale, which seems logical for that page. Is there a different way to get to Basic Patch now?
-
- When I update the OS, I can see an indication on the front panel, and checking under Globals confirms I've installed 1.4.0.5. But when I run the alternative tuning sysex with MIDI-Ox, I see no indication of data reception on the Pro 2. Is there a way to check that the alternate tunings update has been installed?
- This is more of a question than a bug report. The Pro 2 manual states that to start with an initialized patch, you press Global and turn Soft Knob 1 until you reach option 31, which the manual claims will be Basic Program. But the globals all have to do with MIDI and I/O, so 31 is CV 1 Out Scale, which seems logical for that page. Is there a different way to get to Basic Patch now?
Just scroll a bit further and look for "Basic Program" in the list (menu item #36 on OS 1.4.0.1).
In the 1.4 manual addendum, its referred to by the name instead of the numerical order in the list. I guess once the manual has gone out in physical print maybe they are reluctant to update the primary .pdf. You can find the manuals and addendums on the main support page for the Pro 2.