The Official Sequential/Oberheim Forum
SEQUENTIAL/DSI => Pro 2 => Topic started by: jobinho on November 11, 2015, 05:07:30 AM
-
I tried the Sound Tower editor and was wholly unimpressed. The aesthetics, UI & usability all falling way short.
This synth is crying out for a comprehensive and well designed software component. Just the ability to rename and organise patches effectively, as well as enhance patch creation - would really aid the Pro 2.
(edit: just demoing the latest update from SoundTower - it seems less buggy and more usable - would be great to have waveform icons that match the ACTUAL waveforms - also drag and drop for presets would be great)
-
I'll second that! Love my Pro 2... DSI has really outdone themselves. On all levels. But a synth of this depth, simply needs a computer based editor.
Cheers!
-
I agree 100% - these days a Patch management app is minimum requirement.
With DSI creating their own forum, I hope this is a sign of things to come with DSI catching up.
Clavia NL software rocks.
-
With DSI creating their own forum, I hope this is a sign of things to come with DSI catching up.
I have a hard time imaging the DSI that I know do their own editors. Perhaps an outsourced solution could help them. But given how their current software development resources are and how much work making a good editor is I would be very surprised if that ever happened. Actually it would be way better if they did more OS updates instead of making their own editors! ;)
And yeah it would be nice with high quality editor solutions being made for DSI products. Its really sad that the Soundtower editors do not works as well as customers are hoping for.
Anyhow, this thread could be the perfect place for you to describe the editor and librarian features you dream about having! ;-)
-
Anyhow, this thread could be the perfect place for you to describe the editor and librarian features you dream about having! ;-)
That part is easy. For the editor, access to every synth parameter, logically laid out on as few pages as possible. Saving macros would also be a nice feature... For example, saving the settings for part or all of the step sequencer, or the settings of the entire filter section.
For the librarian, the ability to copy, paste, store, rename, and rearrange the patches and banks. That should cover it.
Cheers!
-
Just demoing the latest update from SoundTower - it seems less buggy and more usable - would be great to have waveform icons that match the ACTUAL waveforms - also drag and drop for presets would be great
-
Surely it's only a matter of time until they do so, after all the Mopho has one.
-
Surely it's only a matter of time until they do so, after all the Mopho has one.
Isn't the Mopho kind of hard to sell without an editor? :)
-
http://www.synthgraphics.com/mopho_tetra.html, using a Behringer BCR-2000
-
Hi everyone!
I am looking for a solution to save my patches - without overwriting patches from the factory and userbanks. Can I do this with the Soundtower software?
Thank you for the help and I am super happy with the Pro2 - such a beast of a synth :D
Best, mr.highcut
-
FYI I started building a Ctrlr Pro2 panel. Just give me some time. It will be free. Will post some pictures soon.
Of course you can also have a look to the SoundTower editor.
-
FYI I started building a Ctrlr Pro2 panel. Just give me some time. It will be free. Will post some pictures soon.
Of course you can also have a look to the SoundTower editor.
Sounds great, please do keep us posted 8) Will it feature a librarian?
-
FYI I started building a Ctrlr Pro2 panel. Just give me some time. It will be free. Will post some pictures soon.
Of course you can also have a look to the SoundTower editor.
Sounds great, please do keep us posted 8) Will it feature a librarian?
Yes, I'll try. Hopefully we have good documentation from DSI...
-
FYI I started building a Ctrlr Pro2 panel. Just give me some time. It will be free. Will post some pictures soon.
Of course you can also have a look to the SoundTower editor.
Sounds great, please do keep us posted 8) Will it feature a librarian?
Yes, I'll try. Hopefully we have good documentation from DSI...
Well, there's the rub.
The SYSEX docs are more than likely not good enough for you to make your panel. The parameter locations DO NOT match the NRPN locations. At least they did not on the Prophet 6.
If it helps, I can send you what work I started on the Prophet6. I had a debug routine whereby you can twiddle a knob, do a dump, and the debugger would display what SYSEX byte changed. It's not automated since you have to turn a knob on the synth, so it's going to take maybe a couple hundred passes.
What I really wanted was a patch librarian, but the Ctrlr.org API for that part is poorly documented - doesn't exist. I just wanted to make a patch librarian but I got held up off the bat with incomplete SYSEX docs from DSI and no docs for the MIDI lib stuff from ctrlr.org
Let me know if you want to see my hacked code for the Prophet 6. If you're good at this stuff, you may be further along than I already was.
-
Thx for your support offer. At this time not needed... but maybe later ;)
FYI, I have decoded most of the Moog Sub37 sysex dump by indeed using the same technique (try to set all params to 0, dump with Midi-OX and save as reference, then change each param one by one from min to max value and dump then reset and do next param; same for multi-values params; then compare with reference file using HxD, one param at a time) and I can now read their files and display them in my Sub37 editor.
Here I have now made the panel layout with all Pro2 parameters.
During w-e and next week I will give correct names and do the real time NRPN handling (bi-directional).
Then week after I'll do all "On value change" methods that will display explanation from the manual on the current parameter + saved value + current value (I did this for the Sub37 and it is really cool).
Then will build the read single program dump stuff.
Will not address the sequencer in a first instance. I will focus on program editor + program reading/writing + librarian
I attach a picture showing the idea of the layout (at least as it is right now)...
-
Looks great!
-
I attach a picture showing the idea of the layout (at least as it is right now)...
Fantastic... will this work as an AU? If it had instantaneous recall for unlimited number of patches that would be amazing - and id happily pay for it. This is where the soundtower librarian fails.
-
Fantastic... will this work as an AU? If it had instantaneous recall for unlimited number of patches that would be amazing - and id happily pay for it. This is where the soundtower librarian fails.
Didn't know this.
Ctrlr gives the possibility to have standalone, VST and AU panel versions so even if I worked in standalone mode until now I should create VST and AU versions of the same panel as well.
And it will not be needed to pay ;) Ctrlr is freely developed by Atom and different people around the world are making panels for their own use and are happy to share them.
Of course you depend on goodwill and willingness and time to spend. Maybe you will not have all the features you dreamed of but it is free and you have full freedom to take an existing panel and adapt it further 8)
-
Any update on the ctrlr panel? :)
-
Sure!
Things are going very well but anyway taking time even if I'm working on it a bit every day.
I have all the extracts from the manual about the parameters.
I have built and fixed the wave shapes display and the filter routing display. The displays and controls are enabled/disabled according to the wave and filter selections.
I had to reverse engineer the sysex program data dump but this is now done (except the sequencer part) and I'm busy to do each OnChange method for each parameter.
I can upload a program and today I have fixed the bank and program handling (it will be possible to load and save in different banks/programs). I put the handling logic on paper and now I have to implement and test it.
I have also started the librarian and can read sound banks in a very efficient way. However I will work further on it once the single program load and save will be finished.
You will have 2 disk banks and the 4 user banks to play with.
The layout is still not fully fixed.
I have also settled the base for an ini file that will contain the banks used and some other parameters.
I have also added the Global parameters tab content.
Here are a few pictures...
So, just a bit patience. The most important is that I don't see any blocking issue as I got with the Sub37 :)
-
That looks great! Nice one for putting in all the time and effort.
-
So, just a bit patience. The most important is that I don't see any blocking issue as I got with the Sub37 :)
This is looking great so far!
-
Wow, fantastic effort!
Thank you.
I have the Soundtower editor, and I find it a little clunky to use - the UI / UX is OK, not great.
Oh, I noticed a typo in your "envelopes" tab!
Cheers,
Simon
-
super excited! great work, sir!
-
Great job!! Looking awesome!
-
Looks great! Really looking forward to this one.
-
Honestly can't wait. I mean, it's an easy-to-use synth but the ability to route the mod matrix using a GUI will be superb.
-
Thx to all for your encouragements!
To be honest it is quite a work due to the number of parameters and buttons...
@binman_uk: here is a screenshot of the Modulations and LFOs tab. Quite packed. Let me know your remarks. I wanted to add some Modulation number or LFO number but not sure I can do it without enlarging the panel. I can do that without any problem in fact; the issue will come for people with a too small screen - are there still?.
In height I cannot extend more (I see this on my laptop, I reached almost max) - I had to extend it to increase the top LCD by one line.
-
That looks good.
To be honest I'd rather have a spacious layout than a cramped one - if it needs to be bigger then personally I think that's the way to go. I imagine most people are running at least 1920x1080 or 1920x1200 these days (on desktop PCs at least).
-
One more question, goodweather: I'm not sure whether I missed anything, but is this editor going to be cross-platform?
-
One more question, goodweather: I'm not sure whether I missed anything, but is this editor going to be cross-platform?
Well, it is a Ctrlr panel and in fact a large xml file. Ctrlr is available on Mac and on PC in standalone and in VST.
As soon as I'll get something decent, I'll share the panel and anyone will be able to use/test it and send me feedback.
I'm using a PC and Ctrlr standalone but other people could test it on a Mac.
When running OK standalone, I'll try the AU/VST version so we can have it inside our DAW.
Theoretically it should rock, let see how it will turn out ;)
-
Well, it is a Ctrlr panel and in fact a large xml file. Ctrlr is available on Mac and on PC in standalone and in VST.
As soon as I'll get something decent, I'll share the panel and anyone will be able to use/test it and send me feedback.
I'm using a PC and Ctrlr standalone but other people could test it on a Mac.
When running OK standalone, I'll try the AU/VST version so we can have it inside our DAW.
Theoretically it should rock, let see how it will turn out ;)
Okay, count me in as a prospective beta tester for Macs.
-
One more question, goodweather: I'm not sure whether I missed anything, but is this editor going to be cross-platform?
Well, it is a Ctrlr panel and in fact a large xml file. Ctrlr is available on Mac and on PC in standalone and in VST.
As soon as I'll get something decent, I'll share the panel and anyone will be able to use/test it and send me feedback.
I'm using a PC and Ctrlr standalone but other people could test it on a Mac.
When running OK standalone, I'll try the AU/VST version so we can have it inside our DAW.
Theoretically it should rock, let see how it will turn out ;)
I could also test it on Mac for you.
Cheers!
-
happy to be a MAC tester!
-
I use the CTRL.org already for my voyager, works great.
The Soundtower stuff is well....meh
DSI should compensate you for the effort. I am sure a whole lot of ppl appreciate a CTRL editor version for all DSI synths.
I would like one for my P6/P12 and Pro2 plz :)
I will test also for you if you need more testers.
OSX10.9.5 nMPro 32GB hexacore.
-
I use the CTRL.org already for my voyager, works great.
The Soundtower stuff is well....meh
DSI should compensate you for the effort. I am sure a whole lot of ppl appreciate a CTRL editor version for all DSI synths.
I would like one for my P6/P12 and Pro2 plz :)
I will test also for you if you need more testers.
OSX10.9.5 nMPro 32GB hexacore.
Well, I'm not doing this for money, just for pleasure, learn something and getting something as I want (and hoping other people will appreciate it as well...)
About DSI, they are great in support but didn't give me the sysex specs. I had to find them myself. However, they have a neat implementation and it was easy. Anyway, it took me several hours to cover all params and I could have spent that time doing something else.
Doing this for the Pro2 but I looked at the P12 manual and saw it is really close to the Pro2.
I'm sure I could adapt the Pro2 editor for P12 If I could get a P12 for a while (but that is another story...).
-
Well it is not that I meant DSI should give you lots of money, but some merchandise of some sort, like stickers , or t-shirts or that kindof stuff. I really think alot of ppl will love a ctrl version of the DSI editors, soundtower is just too buggy and not up to date with latest OS releases etc.
-
That looks good.
To be honest I'd rather have a spacious layout than a cramped one - if it needs to be bigger then personally I think that's the way to go. I imagine most people are running at least 1920x1080 or 1920x1200 these days (on desktop PCs at least).
Yeah, make it a large one. 1920x1080+ resolutions plz.
-
Hi guys, some news and some question...
Status of the work: still very good progress (working on it 1 to 2 hrs a day)
- all params can be adjusted, they have their NRPN number and message handling
- same for global parameters (bug found in 1.1.0 - maximum values cannot be reached by Midi input - but just got a message from DSI support that it has been corrected in 1.2.0.2)
- I have put red numbers for the 16 modulations and for the 4 LFOs
- Filter secondary screen is adjusted when you move the corresponding parameters
- bi-directional behaviour has been tested and works nice (this is really cool in fact): you modify something on the panel and the screen of the Pro2 is edited. You modify the Pro2 and the panel jumps to the corresponding tab (I implemented this and you also have the option to disable it if you want) and you see the button turning or going on/off.
For that one I will submit an enhancement request to DSI to have the screen switching to the panel of the edited param on Midi input (with possibility to disable if for example you would send a lot of info by Midi and don't want your Pro2 screen getting crazy) - all params have supporting manual text on the main screen and have values as on Pro2
- you can load a single program and after selecting any parameter you see the current value and the saved value
- librarian started. You can pick a source program and a destination program with the mouse and this is highlighted with colors. I can extract program names from bank dumps.
Started/Ongoing/Planned:
- initialization of the panel (securing you get the panel where you left it, no more need to reload the bank disk files or the last program)
- Osc split filter routing display (for the moment I have only non split display - it is the same but without the OSC split indication on the top)
- save of a single program (I have already put all the logic on paper - there are several cases of load/save)
- develop the different possible bank and program actions (visually + data handling)
- use of imported font instead of relying on OS fonts. I analyzed the Pro2 font and found it was either Neo-Sans-Std or Neo-Sans-Std-Medium.
So, still some work but I hope to get this ready after summer vacations.
I'll provide you the panel for testing quite soon even if unfinished. I'll indicate what you should not test...
Question: what is the typical file path on a Mac (I'm speaking about syntax)?
In Windows : and \ are used as on D:\Users\Dominique\Documents\My Pro2\Factory banks\F5 Bank.syx
Cheers...Dominique
-
Mac OS is built on UNIX so the file separator is "/"
-
Mac OS is built on UNIX so the file separator is "/"
Spaces as escaped with a backslash "\"
-
Thx. Will be fine.
I also forgot to say that the envelope graphs are changing when you turn any DADSR knob but that you can also move the graph anchors which is making the knobs turning ;)
A detail about program source and destination: you will do a right click to select a source program and a left click to select a destination program (needed or not depending on the action).
Yesterday I did the bank select picking and highlighting (done by clicking on the bank label), prepared the bank action button, added back the bank files display as secondary screen (I already changed several times the layout). This secondary screen will only show the filename to avoid issues with too long file paths.
Bank and program actions will get a "Are you sure? or OK to proceed?" confirmation question (my first synth was a DX7...) but you will be able to disable this confirmation if you want.
-
Hi everybody, time is flying and you deserve some news...
Status of the work: still very good progress but maybe at a slightly lower speed
- bank management with different types of actions - 2 Disk and 4 User banks
- program management with different types of actions
- individual load with different types of actions depending on Disk-User-Factory banks
- individual save with different types of actions depending on Disk-User-Factory banks
- Rename (I had this basic function almost forgotten...)
- About information with change log, backlog info.
- Startup of the panel fixed
- Finaly not using embedded font as it gave problems. Users will have to install the Neo-Sans-Std font on their computer before using the panel (however I will make further tests and try-outs with embedded fonts later. Never giving up...)
- Different corrections here and there
Started/Ongoing/Planned:
- testing and adapting individual program Load/Save and in combination with bank and program management (possibilities described in attached document)
- Osc split filter routing display (for the moment I have only non split display - it is the same but without the OSC split indication on the top)
So, close to readiness for initial download and still maintaining the target for August (...this year :) )
-
excellent, keep up the good work man... your time/dedication isn't going unnoticed over here!
-
Looks excellent! Keep up the great work and thanks for the updates!
-
Hi everybody, time is flying and you deserve some news...
Status of the work: still very good progress but maybe at a slightly lower speed
- bank management with different types of actions - 2 Disk and 4 User banks
- program management with different types of actions
- individual load with different types of actions depending on Disk-User-Factory banks
- individual save with different types of actions depending on Disk-User-Factory banks
- Rename (I had this basic function almost forgotten...)
- About information with change log, backlog info.
- Startup of the panel fixed
- Finaly not using embedded font as it gave problems. Users will have to install the Neo-Sans-Std font on their computer before using the panel (however I will make further tests and try-outs with embedded fonts later. Never giving up...)
- Different corrections here and there
Started/Ongoing/Planned:
- testing and adapting individual program Load/Save and in combination with bank and program management (possibilities described in attached document)
- Osc split filter routing display (for the moment I have only non split display - it is the same but without the OSC split indication on the top)
So, close to readiness for initial download and still maintaining the target for August (...this year :) )
Looking awesome, can't wait to try it out now :)
-
Thx jobinho and the others!
Well... The panel is ready and I think I'll publish it between 15 and 21st of August.
I'm doing different further tests (mainly in bank and program management) and make some small corrections/improvements.
I will also write some small README1st doc related to the installation of the font, the initial usage of the panel and some explanations on the different features.
Here is what changed since end of June (top is the most recent):
- Bank AutoSave switch and code adaptation
- Program proceed confirmation switch and code adaptation
- Clean/reset bank action (with reset of variables) added
- Tests Load/Save/Bank and Program management
- Receiving bank completed and working
- Coded Save buffer to User bank
- Progress bar hide/unhide modified due to bug
- Added MIDI Arp Notes and Program Send Global parameters
- LFO, Env and Mod Destinations adapted
- Filters Enable, Osc split working with Pro 2
- Cleaner Delays On/Off
- Filter 2 N/BP switch replaced by rotary button
- Different small corrections
- All secondary screens updated on Load
- Delays On/Off as Oscillators
-
Sounds like it's been an awful lot of work. Thanks again man.
I honestly can't wait. It should open up a new raft of possibilities with this synth!
-
Sounds like it's been an awful lot of work. Thanks again man.
FYI, I spent between 300 and 400 hours on this panel since January...
Quite a lot in fact... When done, I think it will be time for sound design and ambient music recording :)
-
FYI, I spent between 300 and 400 hours on this panel since January...
Quite a lot in fact... When done, I think it will be time for sound design and ambient music recording :)
;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D
-
Just out of curiosity, do you need any beta testers for this?
I'd be happy to repay some of your hard work by assisting with any testing any whatnot (if there are any bugs, of course). :)
-
I am very excited for this. Currently I have midi CC's set up but having all the parameters accessible in one place will be a joy.
Would happily beta too :)
-
Sure!
In fact the idea is to release the panel as a beta version so several of you can test it and identify bugs and propose some changes then let's say in 2-3 months release it as v1.0).
At the moment I was doing analysis at byte level of the programs (example: load program then save; you should get the same if you don't do any change) and I think I found some issue in the included DSI packing program inside Ctrlr (unpacking is OK).
So I need to write my own packDSI function.
I think I'll release next week (was initialy intended to be this week but got delayed by different stuff).
-
OK. I have now written my own DSI data packing function and it works fine (using my function instead of the internal Ctrlr one). :):) Was a bit afraid of that issue found just before releasing...
Will now prepare some README doc with some instructions and explanations then package the panel and publish it on the Ctrlr site.
As said below, will be for this w-e or during next week.
-
OK. I have now written my own DSI data packing function and it works fine (using my function instead of the internal Ctrlr one). :) :) Was a bit afraid of that issue found just before releasing...
Will now prepare some README doc with some instructions and explanations then package the panel and publish it on the Ctrlr site.
As said below, will be for this w-e or during next week.
Sweet!
-
Excellent, can't wait!
This is by far the most expensive synth I've ever owned and consequently feel the need to learn it inside out. Have put a lot of time and effort in so far and made maybe 10 tracks with it but I think I'm still only scratching the surface of it's true capabilities.
The editor should help speed up that learning curve, especially as I'll be able to see how some of the stock patches are created and the modulations they use at a glance. Perfect.
Will test the hell out of this for you.
Fingers crossed any future OS updates based on feature requests don't require too much rework for you. Am I right in thinking the most time-consuming bit is/was the patch management code (which hopefully shouldn't change in the future)?
-
This synth is indeed fantastic with a huge number of possibilities and in fact so many that it is an endless source of sounds.
It is not only great in possibilities but also in user interface (great panel and screen) and actual sound.
So much pleasure...
Well, in fact it was not the patch reading (reverse engineering of sysex) that took time but the bank and program management.
Then in fact you spend quite some time in each bit and piece: getting a nice display of the wave curves (not perfect as I don't have the PW impact but quite OK for the moment), filter selection mechanism, Osc On/Off, Delays On/Off, right and good text info for each param, general mechanism for displaying that info + the current value + the saved value, etc...
The time goes in the number of parameters and the work needed to modify something similar 50 (or more) times...
You will see it will help you but after this first release I will add an output of the settings of all params at once in a text form and that I think will also help. Then you would send those text files in a soft like KDIFF3 and you would see the differences in parameters highlighted.
To learn about the synth, understanding it and its possibilities, I can only refer to the sets of videos made by Marc Dotty. I'm listening them several times to fully grasp the way of working (especially those on polyphony).
That one is really funny... We have a monophonic synth that is actually a polyphonic one (can play several notes at the same time) but where DSI is saying it is paraphonic while in fact it is not really because you can retrigger the VCA of each note and where in fact as well it is not really a true polyphinc synth as the filter envelopes are not retriggered because unique... So lovely... ;) ;) ;) ;)
Cheers 8)
-
how is this coming along? has it been released yet?
-
Was planned for this week...
I stopped testing and improving/adapting since one week and have almost finalized the Instructions document.
Then I'll take the package and the manual and try it on my wife's PC by exactly following what I wrote in order to get confirmation it works.
So, just a few hours/days and it will be ready for you as test version :)
I'll probably keep it in 0.x test versions for 3 months then provide a 1.0
8)
-
D-Day is there...
The panel is ready and you can download it at http://ctrlr.org/dsi-pro2-editor-and-librarian/ (http://ctrlr.org/dsi-pro2-editor-and-librarian/)
You will find installation instructions and guidance in the manual included in the zip file.
I published it as v0.25 beta version and I propose to stay in beta during 3 months in order to gather your feedback and make corrections/improvements.
8)
-
D-Day is there...
The panel is ready and you can download it at http://ctrlr.org/dsi-pro2-editor-and-librarian/ (http://ctrlr.org/dsi-pro2-editor-and-librarian/)
You will find installation instructions and guidance in the manual included in the zip file.
I published it as v0.25 beta version and I propose to stay in beta during 3 months in order to gather your feedback and make corrections/improvements.
8)
Thanks for your work on this. I will try it out over the coming days and compare it to the Soundtower editor that I use occasionally.
BTW, there happens to be good weather here to day in Ireland (a rare thing) - goodweather = good weather = downloaded editor - coincidence, I think not 8)
-
D-Day is there...
The panel is ready and you can download it at http://ctrlr.org/dsi-pro2-editor-and-librarian/ (http://ctrlr.org/dsi-pro2-editor-and-librarian/)
You will find installation instructions and guidance in the manual included in the zip file.
I published it as v0.25 beta version and I propose to stay in beta during 3 months in order to gather your feedback and make corrections/improvements.
8)
Legend. This is my Tuesday night sorted then!
I'll keep a log of any issues and will report back.
Much appreciated.
-
Thanks for this.
When loading I get an error as in the attached image.
The controller then appears, I set the midi up and get nothing sent to the P2 and nothing received.
The Ctrlr log is empty.
The Ctrlr midi monitor shows no messages.
-
Another update:
After loading another Ctrlr panel and getting that to work the P2 panel started working!
I'm probably being a numptie but I can't work out how to get the patch on the P2 synced to the panel though.
The Bank, Program, Load, Save and Rename seem to have no effect.
The "Programs Library" is empty.
The program always reads "U-P0 SquareBass".
Any ideas?
Cheers
Andy
-
Thank you for your generous work on this editor. Very excited to get working with it.
I am using a Nektar Panorama P6 as MIDI controller. This is connected to my computer via USB, as is the Pro 2.
In Ctrlr, I have:
Input Device set as Pro 2, MIDI channel 2
Controller Device is Panorama P6, MIDI channel 0
Output Device is Pro 2, MIDI channel 2
Is this correct? Should I be able to play the Pro 2 from the Panorama while Ctrlr is open? I have set the global parameters on the Pro 2 as instructed in the PDF. Thank you.
-
Another update:
After loading another Ctrlr panel and getting that to work the P2 panel started working!
I'm probably being a numptie but I can't work out how to get the patch on the P2 synced to the panel though.
The Bank, Program, Load, Save and Rename seem to have no effect.
The "Programs Library" is empty.
The program always reads "U-P0 SquareBass".
Any ideas?
Cheers
Andy
Hi Andy,
already sent you a PM for your previous message...
I tested all of this from a completely fresh installation of Ctrlr and the Pro2 panel on a new PC and didn't get any issue...
Did you follow the installation instructions that I wrote in the manual?
From which point do you start seeing differences/issues?
Sorry for the inconvenience...Dominique
-
Thanks for this.
When loading I get an error as in the attached image.
The controller then appears, I set the midi up and get nothing sent to the P2 and nothing received.
The Ctrlr log is empty.
The Ctrlr midi monitor shows no messages.
OK. It is strange I didn't get this message when testing a new installation but I think I could find the reason.
My PackDsiData has been executed at panel load when there was nothing because I didn't have a classical if condition to avoid this at the beginning of the function (all functions must have this). So, I have now added this test and hopefully it should be better.
Ctrlr is still a mystery on many points as there is no documentation and just a forum.
I wrote a Step by Step guide but there is still a lot to learn...
I'll wait a few more feedbacks to post the 0.26
Meanwhile I will add the Glide parameters...
-
Corrected/modified today:
- FM and AM intervals are 0-255 and not 127 (was just a display issue)
- Added test at beginning of PackDsiData to avoid issues at panel load (forgotten in that function)
- Glide mode combo added (was not forgotten - see manual - but did it now...)
Will publish those changes after a few more user's feedback...
-
Another update:
After loading another Ctrlr panel and getting that to work the P2 panel started working!
I'm probably being a numptie but I can't work out how to get the patch on the P2 synced to the panel though.
The Bank, Program, Load, Save and Rename seem to have no effect.
The "Programs Library" is empty.
The program always reads "U-P0 SquareBass".
Any ideas?
Cheers
Andy
Hi Andy,
already sent you a PM for your previous message...
I tested all of this from a completely fresh installation of Ctrlr and the Pro2 panel on a new PC and didn't get any issue...
Did you follow the installation instructions that I wrote in the manual?
From which point do you start seeing differences/issues?
Sorry for the inconvenience...Dominique
No need to be sorry, it's very good of you to have done this for us all. I can imagine the time it took!
-
Hello Goodweather! first of all this looks absolutely fantastic , just wow! Now , i'm on cubase 64 bit and i get the same message of bobthedog . Here the screenshot. Thats said i have the editor partially working. The nrpn msgs work fine, but (i guess) sysex don't. I set it up the setting correctly and installed the fonts. For example, changing the waveforms from the graphic selection windows doesn't have any effect, same thing for the graphic envelopes , but they don't even move. Also i cannot load programs from the pro2. Any ideas on what could be the problem? Btw thx again, awesome job!
-
Hi all,
as I said, thx for your trust and sorry for the inconveniences. I can assure you this panel works fine...
BobTheDog is using a Mac. Are you also using a Mac? Don't know if this could be linked...
Anyway, I made some corrections (see below) and hopefully the message you get should disappear.
Please download the 0.26.
You don't need to re-install the font of course. Just replace the panel, redo your Midi settings and save as .panel as described in the manual.
First time I'm publishing some software solution... Well, now I understand it is not easy to reproduce all situations the users can have... We will find solutions and it will work. Just a matter of patience and fight...
-
hi goodweather, i'll try with the new version , i'm on pc btw. what version of ctrlr are you using?thx a lo again
-
downloaded the new version and works almost perfectly!! so far all the parameters are fine! The only problem is the transmission of some presets, strangely mainly from user 1 bank, but the editor is awesome! Absolutely fantastic job|!
-
downloaded the new version and works almost perfectly!! so far all the parameters are fine! The only problem is the transmission of some presets, strangely mainly from user 1 bank, but the editor is awesome! Absolutely fantastic job|!
You can't imagine how good it is to read your feedback. I started to be somewhat anxious...
If you have a PC then you are in the same situation as me and at least we can fine tune. Good!!!
I tested from scratch a different PC with a download of the latest Ctrlr version and we have Windows 10.
Can you please send me in PM the things you are doing with User1 bank in order to come to some issues?
I will also have some look myself. Maybe a typo... Most of the time all Ux banks are treated exactly the same way...
Have a nice w-e... 8)
-
Hi,
Just given the new version a go. The initial error on load has now gone :)
When trying to load presets though I get an error as shown in the attached image.
Cheers
Andy
-
Hi man, just getting version 0.26 running now. First impressions are that most things seem to work but when I cycle through the waves using the editor it doesn't seem to change on the synth?
-
Hi man, just getting version 0.26 running now. First impressions are that most things seem to work but when I cycle through the waves using the editor it doesn't seem to change on the synth?
Hi! Different things to check...
When you get this behaviour, it is usually not only the wave shapes but all params not acting bidirectional. Way to solve it: close panel, close Ctrlr, switch Pro2 OFF then ON then restart Ctrlr and panel. Maybe it is not needed to close the panel and you can directly close Ctrlr.
Other things you can check are the Global parameters settings especially the Midi channel.
PLease try again and let me know 8)
-
When trying to load presets though I get an error as shown in the attached image.
Hi Andy,
we have indeed solved that panel started issue :)
As you can see the error messages are quite cryptic...
I don't have a method strictly called "get" in that Load_OnChange method... ???
So, can you please describe me the situation when you are getting this error?
- do you have banks loaded and from which bank are you trying to load?
- did you try the single .syx programs I provided in the zip file?
- did you try the bank .syx I provided in the zip file?
-
Hi,
I had a look through the code, hampered by the fact the debugger doesn't work and there is no global find!
Your problem is here:
isPro2InDevices = function()
-- No action if the panel is in bootstrap or program states
if not isPanelReady() then
return
end
sDevices = utils.getMidiInputDevices()
for i=0, sDevices:size()-1 do
if tostring(sDevices:get(i))=="Pro 2" then
return (true)
end
end
return (false)
end
if tostring(sDevices:get(i))=="Pro 2" then
That is the line that fails, if you change it to:
isPro2InDevices = function()
-- No action if the panel is in bootstrap or program states
if not isPanelReady() then
return
end
sDevices = utils.getMidiInputDevices()
for i=0, sDevices:size()-1 do
if tostring(sDevices[i])=="Pro 2" then
return (true)
end
end
return (false)
end
It then works.
Having just spent a little time with ctrl you must be an Angel to have created this stuff as it is a nightmare to use, just awful!
-
Actually that fixed the overload message but the code doesn't work, looking into it...
-
ok, got it working on OSX, should be fine on pc as well:
isPro2InDevices = function()
-- No action if the panel is in bootstrap or program states
if not isPanelReady() then
return
end
sDevices = utils.getMidiInputDevices()
return sDevices:contains("Pro 2", true)
end
-
Thanks Andy!
I was just typing that it could be a difference between the Ctrlr Mac and PC versions...
Thanks for finding the issue. I'll adapt the code of my function.
About Ctrlr, well, indeed it has been very tough sometimes... :-\
8)
-
The StringArray that is returned by getMidiInputDevices() is an extension in c++, my guess is the versions are different on the PC and OSX. Or the one on OSX is buggy maybe.
OSX seems to have been left behind a while ago by ctrlr!
I can now load a sysex file and send it to the P2 and all works fine :)
I'm a bit confused by the bank and program knobs, should they change bank and program on the P2?
Also the graphical Wave selectors on the oscillators are not working, they update from the P2 but don't update the P2.
-
I'm a bit confused by the bank and program knobs, should they change bank and program on the P2?
No, the philosophy I took is that you must first receive your banks in Programs Library tab to make them available in the main Load and Save buttons.
So, you load a sysex or Ux from loaded bank or Fx from the synth then you can save it at different places.
I can implement direct Bank/Program change buttons later if people want it
Also the graphical Wave selectors on the oscillators are not working, they update from the P2 but don't update the P2.
Works also fine on my side (I knew it but I just retested it again now for the 4 oscillators).
Strange that it works when coming from the synth and not when you change on the panel...
Another Mac/PC difference?
Did you try switching the Osc On/Off?
-
downloaded the new version and works almost perfectly!! so far all the parameters are fine! The only problem is the transmission of some presets, strangely mainly from user 1 bank, but the editor is awesome! Absolutely fantastic job|!
Sorry for the delay - will try tonight!
-
Ahh, Lua!
-
Hm, I can't for the life of me get this working at all now.
Globals 100% set up correctly. Ctrlr set up correctly.
No updates on the Pro2 when I change something on-screen
No updates on screen when I change something on the Pro-2
Ctrlr is the latest version as of today. Pro-2 is latest firmware as well.
I get the following error when I load one of the patches you supplied...
EDIT: I've figured out why it's doing that. For some reason every time I start ctrlr it sets my Pro-2 to midi channel 3 and messes up some other options. I also downgraded CTRLR and that seems to have allowed input/output to work.
-
Will be testing this extensively very soon. Thanks again for all the hard work on it :)
-
Hm, I can't for the life of me get this working at all now.
Just to be sure... Are you using a Mac or PC?
If Mac, then I got an error reported by BobTheDog (see below) and I'll publish 0.27 tonight that should fix it.
Otherwise, we can exchange PMs or meet on the Ctrlr forum chat at an agreed time
-
v0.27 published - http://ctrlr.org/dsi-pro2-editor-and-librarian/ (http://ctrlr.org/dsi-pro2-editor-and-librarian/). It includes the correction of the issue identified by BobTheDog (thx!) for Mac users.
No other change so PC users do not need to download this one...
-
For those interested I have now released the v1.00 of the Ctrlr Pro2 editor.
http://ctrlr.org/dsi-pro2-editor-and-librarian/ (http://ctrlr.org/dsi-pro2-editor-and-librarian/)
Added:
- Compare button
- Programs info tab: list/export current values, saved values, current and saved values, differences only, full comparison of two programs, differences between two programs
In the pipe: categories, availability as VST, morphing between 2 programs and random patch generator...
Have fun with this fantastic synth!
-
You did a very cool Job. Yeah! Thank you very very very very very much.
-
You did a very cool Job. Yeah! Thank you very very very very very much.
Thank you 8)
-
For those interested I have now released the v1.00 of the Ctrlr Pro2 editor.
http://ctrlr.org/dsi-pro2-editor-and-librarian/ (http://ctrlr.org/dsi-pro2-editor-and-librarian/)
Added:
- Compare button
- Programs info tab: list/export current values, saved values, current and saved values, differences only, full comparison of two programs, differences between two programs
In the pipe: categories, availability as VST, morphing between 2 programs and random patch generator...
Have fun with this fantastic synth!
Great work thanks! Will this work as a plugin too?
-
Great work thanks! Will this work as a plugin too?
I'll check this now (was on my table since some time...).
What I already did was to have Ctrlr as plugin (Ctrlr-VST-Win32.dll in your vstplugins directory) and then load the panel.
What I will check now is to have the Pro2 panel as Ctrlr-Pro2.dll file.
Question: what is needed to be a good plugin? WHat would be the difference between loading the panel in a Ctrrlr plugin or having the panel directly as plugin?
-
(copying this from what I posted on the FB Pro2 users group; will also be copied in Prophet 12 forum)
As some of you may know I have built a free Pro2 editor/librarian Ctrlr panel. Some people asked me to make a P12 version of it and I have someone testing it as I don't have a Prophet 12.
This gave me the opportunity to build a way to load Prophet 12 sounds into the Pro2 panel.
Tbh, it works nice and you get nice sounds BUT I'd like to get help on actually comparing those sounds with the original ones. For example I think that I should reduce Delay 4 amount or just set it to 0 as on the Pro2 it is BBD and not on the Prophet 12. As the Prophet 12 has less features than the Pro2, most of the other stuff are quite OK.
Btw, still wishing DSI will do a new hybrid mixing OB6 and poly Pro2 in one nice synth ("JD-XA on steroids"). One can always dream ;)
So, please contact me if you are the happy owner of the Pro2 and a Prophet 12 and if you are willing to help me with those comparisons and adjustement tests.
For the others: I'm preparing a version 2.0 of the Pro2 panel. It will correct some minor mistakes, add inverted envelopes, load P12 programs and banks, categories management and program randomizer.