Hi,
I am trying to set up some songs on a DAW using some instances/tracks of DIVA (Revision 7422) and my custom made patches (I am using a very powerful Win 7 Pro workstation … so PC power should not be an issue).
After I programmed my patches on the DIVA default User area (Diva.data\UserPresets\Diva), I have copied these to the MIDI Programs area (Diva.data\Presets\Diva\MIDI Programs) in order to be used by the DAW.
I verified the DAW correctly load all instances of DIVA, each one a different MIDI channel, and load the right patches from DIVA MIDI Programs area using MIDI Bank change & MIDI Program changes commands … so far, so god.
Now the problems started …
First, all my patches are made with Multicore = on, Accuracy = divine & Offline Accuracy = best, however all patches are loaded on DAW with default values (Multicore = off, Accuracy = great, Offline Accuracy = same), therefore, I have to go track by track changing these parameters each time I open the DAW and load the song or project … There is a way to avoid this and set the values Multicore = on, Accuracy = divine & Offline Accuracy = best, for all patches when they are loaded on DAW from DIVA MIDI Programs area?
Second, when song mixing process comes, obviously (at least for me!), We need to make some final adjustments on patches, in order to fit in the mix, BUT I simply cannot save those changes! … If I try to save a patch on (I suppose) the DIVA MIDI Programs area an error message show up: “Saving preset failed: The name 0:nnn nnn Patch Name can’t be used”
If I insist, finally the modified patch is saved on Diva.data\UserPresets\Diva but no on Diva.data\Presets\Diva\MIDI Programs, therefore I have to manually copy the *.h2p from UserPresets to MIDI Programs, restart the DAW, reload the Diva instance and send again the MIDI Bank, Program change command in order to see the modification … Is this normal? Or am I missing something, or doing something incorrectly? … Cannot believe I have to do all this process every time I adjust, let say, the filter cutoff on a patch.
I really appreciate any help regarding this.
I really, really, like the analog sound of DIVA, but with these problems on a DAW environment I thinking twice to use it …
Best regards.
Santiago Luque
HELP: DIVA is not working correctly on DAW!
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
Hi, about the presets not being saved:
When you tried to save the presets, you got the error message because you used a colon in the name. This is a Windows file system restriction, there are some characters which cannot be used when creating a file in Windows.
On Windows, those characters are: \ / : * ? " < > |
About Multicore and Accuracy:
Those settings are not saved with the preset, they are only saved with your host's project file.
To remember their setting, set them to the value you want in each instance of Diva, then save your project file.
When you tried to save the presets, you got the error message because you used a colon in the name. This is a Windows file system restriction, there are some characters which cannot be used when creating a file in Windows.
On Windows, those characters are: \ / : * ? " < > |
About Multicore and Accuracy:
Those settings are not saved with the preset, they are only saved with your host's project file.
To remember their setting, set them to the value you want in each instance of Diva, then save your project file.
That QA guy from planet u-he.
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Hi there,
Some valid points... let me explain.
1. MIDI Program Changes
In order for those not to crash your DAW (most DAWs anyway), the MIDI Programs need to be kept in memory - a file access is not possible for a plug-in during a MIDI Event. So our plug-ins scan the MIDI Programs folder when the plug-in gets first loaded to keep them in memory.
It's a valid point that people will want to change presets a bit and save them again. We'll add it to our to-do-list, where we also have a request for an option to rescan the entire MIDI Programs folder.
2. Accuracy settings and Multi Core
We have deliberately made them "instance parameters". So they save with project, and browsing presets does not affect these settings. If these settings were recalled with presets, many people would not be able to browse preset banks where the Multi Core setting is turned off or quality is set to Divine. Other people experience worse performance when Multi Core is turned on, particularly with multiple instances. So we can't just turn it on by default.
However, in Repro-5 we have added an option to set a default value for the quality. I'll make a note that we do the same in Diva for the next update.
Now, you re-open your project, those settings should be exactly where you left them, i.e. if you save a project with MultiCore on, it should reopen with MultiCore on again and so on. If they are not, please contact support at u-he dot com with detailed information (host, maybe a project you did). It possible that your host handles things different to others and we have to look into it.
Thanks for your suggestions,
- U
Some valid points... let me explain.
1. MIDI Program Changes
In order for those not to crash your DAW (most DAWs anyway), the MIDI Programs need to be kept in memory - a file access is not possible for a plug-in during a MIDI Event. So our plug-ins scan the MIDI Programs folder when the plug-in gets first loaded to keep them in memory.
It's a valid point that people will want to change presets a bit and save them again. We'll add it to our to-do-list, where we also have a request for an option to rescan the entire MIDI Programs folder.
2. Accuracy settings and Multi Core
We have deliberately made them "instance parameters". So they save with project, and browsing presets does not affect these settings. If these settings were recalled with presets, many people would not be able to browse preset banks where the Multi Core setting is turned off or quality is set to Divine. Other people experience worse performance when Multi Core is turned on, particularly with multiple instances. So we can't just turn it on by default.
However, in Repro-5 we have added an option to set a default value for the quality. I'll make a note that we do the same in Diva for the next update.
Now, you re-open your project, those settings should be exactly where you left them, i.e. if you save a project with MultiCore on, it should reopen with MultiCore on again and so on. If they are not, please contact support at u-he dot com with detailed information (host, maybe a project you did). It possible that your host handles things different to others and we have to look into it.
Thanks for your suggestions,
- U
-
- KVRer
- Topic Starter
- 21 posts since 19 Jan, 2016
Thanks very much for your clarifications.
Regarding MIDI Programs, I‘ve made tests and could verify that If I stop the DAW, go to PRESETS, then select MIDI Programs folders and save the patch with only “nnn Patch Name” name, the nnn Patch Name.h2p is indeed saved on Diva.data\Presets\Diva\MIDI Programs with the modification on it, but, as Mr. Urs said, the previous patch (without the modification) is still on memory and when you press PLAY again, the previous patch (without the modification) is the one which is used by the DAW, so you need to reload the DIVA instance to hear the patch modification.
It will be nice to see this change (option to rescan the entire MIDI Programs folder) on a next DIVA release. Thanks.
Regarding Accuracy settings and Multi Core, unfortunately I cannot do that, but it’s my fault because I have been using a “half-free”DAW (Anvil Studio) that only save in *.mid format (with some internal parameters). I have been using this DAW because I found very intuitive and easy, and I like the way you can work directly on the staff (sheet music) view, but I will switch to a more professional (but I hope still easy and intuitive) DAW. I am thinking on Cubase Elements 10 or FL Studio Fruity or Producer, any suggestions?
On any case, Mr. Urs, thanks for taking in consideration my suggestion, I really think the Accuracy settings and Multi Core are part of the patch parameters, therefore should be saved and kept into the *.h2p file.
Finally, like to hear you at U-he have plans to support and update DIVA, I really like DIVA a lot, so far it’s the only way I could find to replicate on a VST patches from Japanese classics such as the Jupiter8, Juno 6 or MS-20 (with some tweaking of course).
Best regards.
Santiago Luque
Regarding MIDI Programs, I‘ve made tests and could verify that If I stop the DAW, go to PRESETS, then select MIDI Programs folders and save the patch with only “nnn Patch Name” name, the nnn Patch Name.h2p is indeed saved on Diva.data\Presets\Diva\MIDI Programs with the modification on it, but, as Mr. Urs said, the previous patch (without the modification) is still on memory and when you press PLAY again, the previous patch (without the modification) is the one which is used by the DAW, so you need to reload the DIVA instance to hear the patch modification.
It will be nice to see this change (option to rescan the entire MIDI Programs folder) on a next DIVA release. Thanks.
Regarding Accuracy settings and Multi Core, unfortunately I cannot do that, but it’s my fault because I have been using a “half-free”DAW (Anvil Studio) that only save in *.mid format (with some internal parameters). I have been using this DAW because I found very intuitive and easy, and I like the way you can work directly on the staff (sheet music) view, but I will switch to a more professional (but I hope still easy and intuitive) DAW. I am thinking on Cubase Elements 10 or FL Studio Fruity or Producer, any suggestions?
On any case, Mr. Urs, thanks for taking in consideration my suggestion, I really think the Accuracy settings and Multi Core are part of the patch parameters, therefore should be saved and kept into the *.h2p file.
Finally, like to hear you at U-he have plans to support and update DIVA, I really like DIVA a lot, so far it’s the only way I could find to replicate on a VST patches from Japanese classics such as the Jupiter8, Juno 6 or MS-20 (with some tweaking of course).
Best regards.
Santiago Luque
-
- KVRAF
- 24447 posts since 7 Jan, 2009 from Croatia
Check out Reaper for an affordable but extremely flexible DAW.
I disagree that Multicore and Accuracy should be saved per patch, though. There's a VERY good reason why these are instance parameters, and Urs explained it above.
I disagree that Multicore and Accuracy should be saved per patch, though. There's a VERY good reason why these are instance parameters, and Urs explained it above.
-
- KVRer
- Topic Starter
- 21 posts since 19 Jan, 2016
Thanks for the DAW suggestion EvilDragon.EvilDragon wrote: Tue Feb 05, 2019 11:34 pm Check out Reaper for an affordable but extremely flexible DAW.
I disagree that Multicore and Accuracy should be saved per patch, though. There's a VERY good reason why these are instance parameters, and Urs explained it above.
You are right, thinking twice, if Multicore and Accuracy parameters (per diva instance/track) can be saved into DAW parameters, I believe it will work for me.
Regarding my first “semi-pro” DAW purchase, to be honest, the more I research on Internet, the more confused I get.
I am into Minimal Wave genre, so I am just looking for a simple DAW where I can have some instances/tracks of the U-he VST synths (I have Diva & Repro), and I can easily create MIDI tracks (lineal and/or with patterns) and compose songs. Also, I would like to have the option of compose and edit MIDI with classic musical notation.
I will use the VST own effects, as well as use the VST to do percussion sounds (for instance the Diva MS-20 model!). At most, I will use one audio track to record a voice and one additional master VST effect, such as U-he Satin or Presswerk, then I will mix and put it all in a WAV (and mp3) song demo file … as simple as that, like in the old times.
Since primarily, I will only use (U-he) VSTs … and I don’t want a fully loaded DAW (and its price!), it seems the option would be something like Cubase 10 Elements, but I will take a look at Reaper as well.
Thanks again for your suggestions.
Regards.
Santiago Luque
-
- KVRAF
- 24447 posts since 7 Jan, 2009 from Croatia
Reaper can do everything you mentioned, including editing via notation. Cubase Elements is limited in track count if I remember correctly - Reaper isn't.
-
- KVRist
- 101 posts since 20 Feb, 2018 from La Spezia, Italy
Hi there,
I might suggest you Ardour, which is a very capable DAW indeed.
It is the base for Harrison Consoles MixBus, which is definitely another very nice sounding DAW.
I’m currently using Bitwig, which I find extraordinary, but it is not low price.
Best regards,
Fabrizio
I might suggest you Ardour, which is a very capable DAW indeed.
It is the base for Harrison Consoles MixBus, which is definitely another very nice sounding DAW.
I’m currently using Bitwig, which I find extraordinary, but it is not low price.
Best regards,
Fabrizio