Sylenth1 version 2.0 update

[cc-purno]

Hi Lennard,

Great update! I tried version 2.0 on my pentium 4 older laptop and I have exacly the same problem as another user. When the gui is up its really lagging and stuttering quite a lot. Perhaps you use some sse that the pentium 4 doesnt support?

Hmmm I haven't tested it on single core CPU's, so maybe that's got something to do with it. Anyone else here tried it on a single core cpu?

Hi Lennard,
(trots op nederland!! )

I tested the demo of v2 on my AMD 64 3200+ (single core) to be sure what I would buy (tested in Orion Platinum)
Preset browser etc are an huge improvement but:

- Knob positions now update much slower when changing presets or moving a knob on my Xboard49 controller. Knobs actually seems to move in +/-10 steps when moving the xboard knows quick or changing presets.
This reduces the overall responsiveness feeling that was so great in V1. Hope this can be fixed in the bugfix update.

Thnx!

[Lennard]

I tested the demo of v2 on my AMD 64 3200+ (single core) to be sure what I would buy (tested in Orion Platinum)
Preset browser etc are an huge improvement but:

- Knob positions now update much slower when changing presets or moving a knob on my Xboard49 controller. Knobs actually seems to move in +/-10 steps when moving the xboard knows quick or changing presets.
This reduces the overall responsiveness feeling that was so great in V1. Hope this can be fixed in the bugfix update.

Thnx!

Hi, this seems to be the same issue some others reported indeed. Do you by any chance get a high CPU usage when this happens? You can check CPU usage in taskmanager for example (Ctrl-Shift-Esc). Are preset changes slow too? Do you get any sound stuttering maybe?

[cc-purno]

Hallo again,

I checked cpu usage in the taskmanager and noticed:
- As soon as I insert an instance of sylenth v2, cpu usage jumps to 70-80 %. ( (I am not even playing notes then)
- The cpu usage meter in orion displays 0%
- When changing presets, the CPU usage jumps to 100% which probably causes the glitchy GUI updates (in orion, cpu keeps at 0%)

thnx

CC

[Lennard]

I checked cpu usage in the taskmanager and noticed:
- As soon as I insert an instance of sylenth v2, cpu usage jumps to 70-80 %. ( (I am not even playing notes then)
- The cpu usage meter in orion displays 0%
- When changing presets, the CPU usage jumps to 100% which probably causes the glitchy GUI updates (in orion, cpu keeps at 0%)

Thanks for checking, that makes sense. So there's something in the GUI causing high CPU usage on some systems for some reason, which is also why it doesn't affect dual core cpu's when only running 1 instance. I assume you mean the CPU usage stays 70-80% on a constant level, right?

What if you do not open the GUI at all? Does it still have high CPU usage? And what if you close the GUI window after having opened it? Does the CPU usage jump back to 0?

Also, can you try running it in another host? Savihost for example, which is a small standalone VST host:
http://www.hermannseib.com/english/savihost.htm
Just download, rename it Sylenth1.exe and put it in the same folder as Sylenth1.dll

[cc-purno]

Hi Lennard,

I will do all these tests when I am home from work this evening. I can also provide you with a screenshot of the Taskmanager CPU usage. (I am also into programming vsti (synthmaker) and PC's/programming some sort)

CC

[cc-purno]

Hi Lennard,

first revealing test results in Orion Platinum 7.5 retail:
(Win XP on AMD 64 3200+/ Soundblaster live 5.1 / KX Asio drivers / Ati Radeon 9700)



[0] Starting taskmanager
[1] Launching Sylenth
[2] Sylenth idle
[3] Changing presets, by clicking the preset browser.
[4] When reaching preset Arp man Machine: idle CPU usage drops to around zero

I could reproduce this behavior every time.

After futher analyse of the patch , I found out that this is the first patch opening by default at PART B.
And indeed, when I click on part B, idle CPU usage drops to around zero!
I suspect the cause lies somewhere in how the separate GUI parts (A and B) are managed on single CPU systems.

Closing the GUI does not make any difference in this by the way.

Now I will start the test on savihost.



CC

[cc-purno]

Here we go:
savihost (still using KX asio drivers)




[0] Starting taskmanager
[1] Sylenth idle
[2] Changing presets, by clicking the preset browser.
[3] Sylenth idle
[4] Moving the cutoff knob (any knob actually) on part A and B with mouse

I compared this with the Sylenth1 v1 demo in Savihost and I don't see any of these CPU peaks with v1 (cpu stays below 10 % in any situation; moving knobs, playing etc. )

Update:
I now also tested moving knobs by mouse in Orion and see the same CPU spikes (but these are added the 50% idle CPU usage until the patch arp Machine Man is opened..)


CC

[Lennard]

Here we go:
savihost (still using KX asio drivers)




[0] Starting taskmanager
[1] Sylenth idle
[2] Changing presets, by clicking the preset browser.
[3] Sylenth idle
[4] Moving the cutoff knob (any knob actually) on part A and B with mouse

I compared this with the Sylenth1 v1 demo in Savihost and I don't see any of these CPU peaks with v1 (cpu stays below 10 % in any situation; moving knobs, playing etc. )

Update:
I now also tested moving knobs by mouse in Orion and see the same CPU spikes (but these are added the 50% idle CPU usage until the patch arp Machine Man is opened..)


CC

Thanks, this is really helpful! I finally managed to reproduce the problem on different pc using an onboard soundcard. Not sure yet why I can't reproduce it on my main system, but at least I can start debugging now

[djanthonyw]

Hey Lennard, any news on the AU version, on schedule, about how much longer? Thanks.

[fragmentated]

Hey Lennard, any news on the AU version, on schedule, about how much longer? Thanks.

I would love to know too. I really want to pull the trigger and buy this but not without the AU version.

[Lennard]

I finally managed to reproduce the problem on different pc using an onboard soundcard. Not sure yet why I can't reproduce it on my main system, but at least I can start debugging now

Strangely enough the problem is gone now I installed the development environment, so I still can't debug it Anyway I'll keep on trying..

Hey Lennard, any news on the AU version, on schedule, about how much longer? Thanks.

Well I want to fix this bug first (and any other bugs that can be found) before continuing the AU version because it uses mostly the same code and thus also has the same bugs. It's pretty hard to say when it'll be ready. I would roughly guess about 1 or 2 months after the bugfixes update, but I just can't say for sure yet.

[djanthonyw]

Wow, thought it was going to be sooner than that, but I know you're trying your best to get it out. Lennard, is there any chance of current users being able to beta test?

[cc-purno]

Just discovered that I can also reproduce the stuttering sound other users reported
In essence this is caused by 100% CPU usage after you set windows colors
to 16 bit!
Compare the CPU usage graphic from Orion/Sylenth under 16 bit (below) with the one I posted before. Now idle CPU usage has jumped to around 100%.



[0] Starting taskmanager
[1] Sylenth idle
[2] Changing presets/playing notes. Bacause the CPU is used 100% already, sound now stutters. (Even the thank you voice stutters if you don't play a note)
[3] Sylenth closed

So it might be interesting to ask users with the stuttering sound to set their colors to 32 bit in windows to see if it reduces the issue.

Savihost:
- Under 16 bit color, sylenth now also has a high idle CPU usage under savihost(on 32 bit it was zero!) Its around 50% (same as in orion under 32 bit color!)
> Closing the GUI does not help
> As soon as I switch to 32 bit color, idle CPU use jumps again to ~zero
> Stangely, this does not work the other way around. Because when switching again to 16 bit, idle CPU use stays ~zero.

Hope this helps

CC

[Lennard]

Wow, thought it was going to be sooner than that, but I know you're trying your best to get it out. Lennard, is there any chance of current users being able to beta test?

Sure, but a beta version will be ready only about a week or so before official release.

Just discovered that I can also reproduce the stuttering sound other users reported
In essence this is caused by 100% CPU usage after you set windows colors
to 16 bit!

Thanks for testing again. I'm pretty sure the reason for the high CPU usage is because the whole GUI gets redrawn over and over again for some reason. If only I could debug it, I could probably find that reason pretty fast. I will be trying some more pc's and hope I can reproduce this bug somewhere.

[HunterKiller]

Thanks for testing again. I'm pretty sure the reason for the high CPU usage is because the whole GUI gets redrawn over and over again for some reason. If only I could debug it, I could probably find that reason pretty fast. I will be trying some more pc's and hope I can reproduce this bug somewhere.

Just bust into people's homes at random and say it's a matter of national security!

Use their PC and then disappear. Oh and don't forget to use the



Neuralizer at the end.

Happy debugging.