See my post farther down... there is a new update of the Junglist that resolves most of these problems!


Old post as followed:

I really like the sound of it, but there are some very annoying aspects:

- in Cubase 5.1 (didn't try SX yet) there is a buzzzz noise each time I stop the sequencer or press one of the locator keys...

- it uses midi CC# 32 for the filter, which none of my controllers support (I tried Nord Modular and my Evolution Keyboard)... looks like 32 is reserved somehow in the midi specs, but this is the MOST IMPORTANT data value on this synth, so why not at least map it twice like they did for the volume

- it doesn't recognize midi program change... hello, in which century do we live?

- there is a denormalisation bug that affects a lot of presets (try the moog bass for example), which is visible on P3 and really heavy on P4

Anybody else observed these? The reviews so far mention none of it...

Rant-off

It just keeps getting better and better... I accidentally changed midi CC# 75, to which Junglist shouldn't even respond and it crashed my whole system... I couldn't believe it, so I tried it again - crash... this thing is buggy as hell it seems... very sad, because it sounds good

The junglist is as buggy as hell. Shame that Synapse can't get their act together on this one, i mean it's been out so damn long.
the denormals, even in the latest versions, are very noticeable. Easiest way to test is the "fmbrass" preset. On my p4 24 it used to jump from 3 or 4 % during usage, to 56% when sitting idle! I remmebr i could never work out why this song always used to stall and dropout after the junglist played a sequence. Even on my current athlon, when sitting idle it jumps to 10%. this actually makes it useable, and shows the athlons are way less affected with this, however when you consider the original patch was using only 2% of the cpu, a jump to 10% is still 5xmore!
Also, since every version i have dropping notes in Logic, Sonar via fxpansion adapter, sonar via directixer, sonar in the latest junglist native dxi version.

I use Orion and program changes work, controller linking too. From time to time the CPU spike occurs on some presets, but that's it.

Quote:

use Orion and program changes work, controller linking too. From time to time the CPU spike occurs on some presets, but that's it.

I second that. Unfortuanatly Junglist seems to work fine in orion and terrible in anything else (not that i've tested it thourgly in other hosts, just judging from other users). You'd do better posting this on the orion-central because rich (main programmer @ synapse) uses the forums for user feedback

Chris, just jump to Orion-central, hit the forums button. You must subscribe, it will mail your login right away. After that go to the "bugs and problems" area; there is a dedicated sub-area for plugins there

There is currently another discussion running there from a user that has troubles with Junglist in Sonar (iirc). Maybe it's related.

I don't use Junglist, but here'a a thought to work around the CC#32 problem - if you're using Cubase, use the midi controller map function - map CC#32 to a different controller - that way you send out a different controller #, and Cubase will send it as CC#32 to Junglist.

I just received an update of Junglist (3.11) which solved ALMOST ALL of the problems (the buzzing noise on stop is still there, but I think I can live with that for now)... I don't know if the developers saw this thread, but I am very pleased with this kind of customer service... it's an awesome synth and I will soon write a very positive review, that's for sure.

Chris

that's what makes synapse sooooo cool

v3.11 of Junglist did *not* fix the bug I am having with Junglist DXi playing in Sonar 2.0. I posted this weeks ago (on August 23) on the Orion forum. There's been no progress on it to date.

Jim

jamescalthoff wrote:

v3.11 of Junglist did *not* fix the bug I am having with Junglist DXi playing in Sonar 2.0. I posted this weeks ago (on August 23) on the Orion forum. There's been no progress on it to date. Jim

Now it's a little unfair to put it like that - there has been progress, just no solution. Rich (Synapse lead developer) has attempted to reproduce the Sonar problem with no success (so far). To Rich's credit he hasn't just denied the existence of the bug - He posted a message today stating that his priority was to fix the denorm bug that was plagueing everyone first, and then to continue with his Sonar testing.

If he had just ignored your post or just denied the problem I would have been fighting your corner

NickMilner >>>>>>>>>>>
Now it's a little unfair to put it like that - there has been progress, just no solution. Rich (Synapse lead developer) has attempted to reproduce the Sonar problem with no success (so far). To Rich's credit he hasn't just denied the existence of the bug - He posted a message today stating that his priority was to fix the denorm bug that was plagueing everyone first, and then to continue with his Sonar testing.
<<<<<<<<<<<<<<<<<<

With the understanding that "progress" on a software problem generally comprises reproducing the problem, understanding the cause of the problem, fixing or working around or explaining the problem (or pilot error as the case may be ), and releasing a solution to the problem, I meant to indicate that no "progress" -- in this sense -- had yet been made.

I didn't state nor mean to imply that Rich had not responded to my post. He did. And I'm still hoping he will be able to figure things out.

Jim

On the one hand I didn't really want to reply because I don't want to get into an argument (I'm really not the argumentative type ). On the other hand I felt I had to say something because your post seemed to contribute nothing to the thread other than to put a downer on Synapse support - it was already clear from the post before that your particular problem hadn't been resolved in the latest release. On the other other hand though you're perfectly welcome to vent some spleen about a problem that's annoying the hell out of you, and what's it got to do with me anyway, and I might actually not hit the submit button on this post at all because, as I mentioned earlier, I'm not the argumentative type...

Nick (I presume),

I don't take your posts here as being argumentative. I think they contain valid points.

The reason that I sent my first post was because I thought the bug that I have been seeing exhibited different symtoms from the others that were discussed. So I just thought it would be informative to note that the problem I'm experiencing (which, again, seemed to me to be different from the others mentioned) had not improved with the latest bug-fix release, unfortunately.

Your first post makes even more sense now that I understand better how it came across to you.

On *my* other hand I do find it frustrating to pay $$$ for something and find that it doesn't seem to work at all (in my particular case, there is noise on every note). I understand the added complication of multiple vendors, platforms, hardware, drivers, etc. Nonetheless ...

Jim

jamescalthoff wrote:

On *my* other hand I do find it frustrating to pay $$$ for something and find that it doesn't seem to work at all

Wholeheartedly agree

I finally found the DXi bug, new version will be uploaded
tomorrow. It happens only under specific driver & tempo
settings under SONAR 2, so it took rather long, sorry for that.

Hey Rich,
Nice to see you here!

Great news, Rich!!!

Thanks very much. Actually, I think your response was very prompt. Good job!

And, in the spirit of "one good turn deserves another", I guess I should get out my wallet and go check out that cool-looking, new Scorpion 3!

Cheers,

Jim