OK, tested the new version, both in REAPER and in VSTHost. Here is the report:
1. Loading a Multi saved with the previous version (the one before this) crashes the host (again).
2. I am able to create a new Multi (which I can save and reload without crashing), but, although the names are displayed correctly while I am loading the presets in the different instances, when I save the Multi, quit EVE, instantiate EVE again and reload the Multi, the names appear (again) all with the name of the preset loaded in Instance 1. They sound correct, it's just the names displayed that are wrong.
We moved on a little, but not enough yet. And it seems I will need to create a new Multi for every new version until this is solved.
Wusik Beta Testing (new installers, new Wusik EVE V5 and other products updates)
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
Oh yeah, getting closer now. Sorry I take so long to fix things up, but I'm getting there. This all happened as I changed the WHOLE code, so I forgot a few things. 
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
Ok, I found a problem with SF2 files. Sometimes they add extra regions with some tweaks that my code doesn't use. So what I'm doing is ignoring regions that already exists that uses the same sound. For instance, preset #33, from above, has 50 played regions (using Extreme Sample Converter to load), but it gives me 1127 regions in the code. 
After I added the -no-duplicated-same-sound-regions code it went down to 50 regions like ESC had. 
Will post new code soon, will finish the other bug reports...
After I added the -no-duplicated-same-sound-regions code it went down to 50 regions like ESC had. Will post new code soon, will finish the other bug reports...-
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
SF2 became a complete mess, as much as SFZ. That's partly why basically all samplers have been dropping support - it's a pain to keep compatibility, and no one is responsible for the standard. As much as I liked SF2 (and still do, to an extent), I think you should perhaps concentrate on the things that are more important (finish the main code, try to assemble a way to retake the old library and create updated presets for it, and launch EVE as a finished product) and then get back to work on the other instruments that are still partially finished, like Wusik Station (launching the Multi support) and Wusik 8008 and Wusik One (I think the skins still need a lot of work).WilliamK wrote: Mon Nov 26, 2018 10:16 pm Ok, I found a problem with SF2 files. Sometimes they add extra regions with some tweaks that my code doesn't use. So what I'm doing is ignoring regions that already exists that uses the same sound. For instance, preset #33, from above, has 50 played regions (using Extreme Sample Converter to load), but it gives me 1127 regions in the code.
It's also my opinion that some rethinking of the GUI of WusikStation is in order (take the GUI I posted of WusikStation 7 as an example). There are lots of wasted space in the current version, as there were already in version 8 (I don't understand why do we need such a big waveform display in the main GUI, for example).
Only when you get a polished and really finished portfolio of products, should you turn to such minor things as SF2 support. Sorry guys, I may sound selfish, but believe me, I am thinking in William business' future. He made this kind of mistakes already in the past (I know, I have been watching him since the beginning). He tends to get diverted with minor stuff and lose sight of what's really important.
@William: If you think you can solve all the problems posed by SF2 soon enough, good. But you are almost 100% dedicated to that for two weeks already. Remember that EVE is supposed to ship with its own library, and has its own file format. SF2 is an add-on, not the main feature. It is also an old, basically abandoned, file format. And EVE isn't even your main product. Think about it.
Fernando (FMR)
-
- KVRist
- 315 posts since 13 Jun, 2009
That is your view but from my point of view it is little different. Wusik Station 8 had issues with sfz a lot but it got polished. It is very good for sfz sample libraries which I have a lot. And doesn't start to hog my HDD like sforzando when loading it (I have 20 or more Gb sfz).fmr wrote: Mon Nov 26, 2018 10:30 pm Sorry guys, I may sound selfish, but believe me, I am thinking in William business' future. He made this kind of mistakes already in the past (I know, I have been watching him since the beginning). He tends to get diverted with minor stuff and lose sight of what's really important.
@William: If you think you can solve all the problems posed by SF2 soon enough, good. But you are almost 100% dedicated to that for two weeks already. Remember that EVE is supposed to ship with its own library, and has its own file format. SF2 is an add-on, not the main feature. It is also an old, basically abandoned, file format. And EVE isn't even your main product. Think about it.
Hearing that sf2 is coming to v9 made my decision to upgrade. So I guess from business side its a good future to have.
There isnt decent x64 sf2 player on Windows OS. Yeah Kontakt will do it or any other but they will convert when saving duplicating stuff on HDD. I heard tx16 or something, sorry forgot name, is good but I don't wanna spend time learning all those functions and tiny knobs.
So, maybe a side thing but important too. Not saying that other stuff isnt even more important but sf2 shouldn't be abandoned.
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
Guys, is not like I'm working 100% on SF2. I'm taking this long as I was playing around with the Intel compiler, which took me days to get it working to the point I wanted. Them I got a SSD to my computer and installed Windows 10 NEW, and all the programs I use. So that tooks some time too. I went one weekend away, and also worked on another project with a friend. I know this is taking longer than expected, but I will finish things up. Almost done with a new file that seems to solve all problems... 
I went one weekend away, and also worked on another project with a friend. I know this is taking longer than expected, but I will finish things up. Almost done with a new file that seems to solve all problems... -
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
As for the MIDI Omni, I tested here with SAVhost 32 bits and Reaper 64 Bits and it works as it should. Could you double-check that on your host midi-input is also set to All-Channels (Omni)? Just in case.
I'm still a bit worried that the installer is taking 30 minutes for you. I tried to find something but so far nothing.
I'm compiling the new files now...
I'm still a bit worried that the installer is taking 30 minutes for you. I tried to find something but so far nothing.
I'm compiling the new files now...
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
Ok, new file there, BETA 80, Windows only for now. Tomorrow I will do the OSX version. Also, this version is not optimized, I used the regular MSVC compiler that runs faster. Tomorrow I do the Intel Compiler version that has a 20% drop in CPU usage on my computer tests.
Ok, this version, I fixed the wrong-name on multi-preset saves. Don't open previous files, as they will mess things up. Delete all your multi-preset files.
On SF2 I did several things. First, click the Global Options (Wusik Logo) and select Sample Player, be sure that Auto Normalize is OFF when loading large SF2 files. This will speed things up, as most SF2 files I tested don't need this.
I fixed a problem with single-shot samples, and other things. The presets mentioned before that were playing distorted are now playing correctly.
It should be stable, at least the code is good. But tomorrow I will double check a few things out, if you guys have crashes when loading SF2 files. If it is a file that always crash, PM me a link for the file or upload to dropbox so I can check what's going on.
Again, thank you all for the super help!!
Best Regards, WilliamK
Tomorrow I do the Intel Compiler version that has a 20% drop in CPU usage on my computer tests.Ok, this version, I fixed the wrong-name on multi-preset saves. Don't open previous files, as they will mess things up. Delete all your multi-preset files.
On SF2 I did several things. First, click the Global Options (Wusik Logo) and select Sample Player, be sure that Auto Normalize is OFF when loading large SF2 files. This will speed things up, as most SF2 files I tested don't need this.
I fixed a problem with single-shot samples, and other things. The presets mentioned before that were playing distorted are now playing correctly.
It should be stable, at least the code is good. But tomorrow I will double check a few things out, if you guys have crashes when loading SF2 files. If it is a file that always crash, PM me a link for the file or upload to dropbox so I can check what's going on.
Again, thank you all for the super help!!
Best Regards, WilliamK
-
- KVRist
- 123 posts since 4 Sep, 2006
William,
You are going through this like a whirlwind, but hope the stress of getting EVE off the ground is not overwhelming. If it takes you awhile to fix something, I think users are just grateful that you can fix the reports in your own good time.
The really offending sf2 fonts are fixed and they play as one would expect. There is still an issue with the Crisis Music Box font (#10) There is a granular distortion that does not manifest in TX16
Amazed at how the sf2 support is taking shape. I realize that there are different respected opinions on whether sf2 should just be scrapped as a dead medium. Only can offer my opinion as one with an incredible and viable collection of sf2 libraries that are as relevant today as when they were written.
I'm thankful that EVE draws in the power of these files. Only increases the worth and utility of EVE.
JohnK
You are going through this like a whirlwind, but hope the stress of getting EVE off the ground is not overwhelming. If it takes you awhile to fix something, I think users are just grateful that you can fix the reports in your own good time.
The really offending sf2 fonts are fixed and they play as one would expect. There is still an issue with the Crisis Music Box font (#10) There is a granular distortion that does not manifest in TX16
Amazed at how the sf2 support is taking shape. I realize that there are different respected opinions on whether sf2 should just be scrapped as a dead medium. Only can offer my opinion as one with an incredible and viable collection of sf2 libraries that are as relevant today as when they were written.
I'm thankful that EVE draws in the power of these files. Only increases the worth and utility of EVE.
JohnK
-
- KVRian
- 975 posts since 10 Jan, 2007 from London
EVE V5 Beta 80
Still the same:
Set up a multi with say instance 1 'xxx', instance 2 'yyy'....Save multi as 'test'.
Load 'test'.
Remove all instances...we are left with 'test' showing in the instance slot 1...should read 'xxx'. The multi preset name should not appear in an instance slot!
Still the same:
Say I have instance 2 open, then I make the mistake of trying to load a multi...OK, I get the warning that I can only load a multi on the first multi preset layer , but then when I click OK, sure, the new multi is not loaded but its name appears in the instance 2 slot!" Here again, the multi preset name should not appear in an instance slot! And perhaps the warning should read "Multi Preset files can only be loaded when first instance is selected" (rather than 'on the first multi preset layer')...or better still, why not just let a multi preset be loaded regardless of which instance is showing?
Suggestions:
'Remove All instances' is confusing and not actually what happens. Should be 'Remove Added Instances'
It's easy to confuse presets with soundsets, especially if they have the same name E.G. the preset 'Analog Voices' and the soundset 'Analog Voices'. So would be great if the soundsets in the browser had a different colour font...or perhaps a different colour background...and the same colour would be had by the the vertical bars to the left of the soundset slots (and the horizontal bar (with 1 2 3 4) above the browser). This would more clearly associate soundsets with Soundset Layer slots.
The 'Multi Preset' section (top of browser) could be named 'Multi Instances', then instead of having 'Multi' as a sub folder of 'Presets' have a 'Multi Presets' folder sitting above and at the same level as 'Preset MIDI Files'.....so 'Multi Instances' and 'Multi Presets' are close to each other and associated, rather than having 'Multi' buried way down in 'Presets'. And having a right click option to 'Save Multi Preset' would make things more obvious. Having multi presets as a subset of presets is not intuitive.
Anyway, just suggestions, perhaps starting points for a way to make this whole multi presets thing more quickly and easily understandable.
Still the same:
Set up a multi with say instance 1 'xxx', instance 2 'yyy'....Save multi as 'test'.
Load 'test'.
Remove all instances...we are left with 'test' showing in the instance slot 1...should read 'xxx'. The multi preset name should not appear in an instance slot!
Still the same:
Say I have instance 2 open, then I make the mistake of trying to load a multi...OK, I get the warning that I can only load a multi on the first multi preset layer , but then when I click OK, sure, the new multi is not loaded but its name appears in the instance 2 slot!" Here again, the multi preset name should not appear in an instance slot! And perhaps the warning should read "Multi Preset files can only be loaded when first instance is selected" (rather than 'on the first multi preset layer')...or better still, why not just let a multi preset be loaded regardless of which instance is showing?
Suggestions:
'Remove All instances' is confusing and not actually what happens. Should be 'Remove Added Instances'
It's easy to confuse presets with soundsets, especially if they have the same name E.G. the preset 'Analog Voices' and the soundset 'Analog Voices'. So would be great if the soundsets in the browser had a different colour font...or perhaps a different colour background...and the same colour would be had by the the vertical bars to the left of the soundset slots (and the horizontal bar (with 1 2 3 4) above the browser). This would more clearly associate soundsets with Soundset Layer slots.
The 'Multi Preset' section (top of browser) could be named 'Multi Instances', then instead of having 'Multi' as a sub folder of 'Presets' have a 'Multi Presets' folder sitting above and at the same level as 'Preset MIDI Files'.....so 'Multi Instances' and 'Multi Presets' are close to each other and associated, rather than having 'Multi' buried way down in 'Presets'. And having a right click option to 'Save Multi Preset' would make things more obvious. Having multi presets as a subset of presets is not intuitive.
Anyway, just suggestions, perhaps starting points for a way to make this whole multi presets thing more quickly and easily understandable.
-
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
I have been unticking the Install Presets option, and installation runs much faster now (although still slow when compared with other installers). It seems that the Installer is maybe comparing one by one all the presets already installed, and that's what takes so much time.WilliamK wrote: Mon Nov 26, 2018 11:19 pm As for the MIDI Omni, I tested here with SAVhost 32 bits and Reaper 64 Bits and it works as it should. Could you double-check that on your host midi-input is also set to All-Channels (Omni)? Just in case.
I'm still a bit worried that the installer is taking 30 minutes for you. I tried to find something but so far nothing.
I'm compiling the new files now...
Don't know if that helps.
Fernando (FMR)
-
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
+1goldglob wrote: Tue Nov 27, 2018 5:18 am Suggestions:
'Remove All instances' is confusing and not actually what happens. Should be 'Remove Added Instances'
+1goldglob wrote: Tue Nov 27, 2018 5:18 am It's easy to confuse presets with soundsets, especially if they have the same name E.G. the preset 'Analog Voices' and the soundset 'Analog Voices'. So would be great if the soundsets in the browser had a different colour font...or perhaps a different colour background...and the same colour would be had by the the vertical bars to the left of the soundset slots (and the horizontal bar (with 1 2 3 4) above the browser). This would more clearly associate soundsets with Soundset Layer slots.
+1goldglob wrote: Tue Nov 27, 2018 5:18 am The 'Multi Preset' section (top of browser) could be named 'Multi Instances', then instead of having 'Multi' as a sub folder of 'Presets' have a 'Multi Presets' folder sitting above and at the same level as 'Preset MIDI Files'.....so 'Multi Instances' and 'Multi Presets' are close to each other and associated, rather than having 'Multi' buried way down in 'Presets'. And having a right click option to 'Save Multi Preset' would make things more obvious. Having multi presets as a subset of presets is not intuitive.
Vey good suggestions goldglob
Fernando (FMR)
-
- KVRian
- 1025 posts since 1 Mar, 2003 from Exmoor
Do you have the engine installer in the same folder as the 16gb sounds installer? If they are in the same folder it will re-install all the sound files as well, so try installing the engine from a different folder perhaps - (apologies if this has already been mentioned).fmr wrote: Tue Nov 27, 2018 8:55 am I have been unticking the Install Presets option, and installation runs much faster now (although still slow when compared with other installers). It seems that the Installer is maybe comparing one by one all the presets already installed, and that's what takes so much time.
Don't know if that helps.
γνῶθι σαὐτόν
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com