H-man.
Per Lichtman[CONSOLIDATED MULTIPLE POSTS INTO ONE IN ORDER TO SAVE SPACE]
@H-man wrote:
Frits, Per,
I have had this in Podium as well. I didn’t respond right away becuase I thought the issue may have been dealt with in the updates.
It is not occuring frequently however the most recent occured when I was changing presets via the file/load preset action.
I believe that it is related to playback/sustained notes. That is, if I had turned of ‘Monitoring’, turned it back on and loaded the preset, then the hang would not have occured.
The result is a freeze or ‘lock-up’ in Podium and is usually accompanied by a loud buzz. To date I have not been able to recover from this and am left with the CTRL+ALT+Delete & kill in task manager as my only path back to windows.
I should point out here that I almost always have several instances on Nucleum open/activated at the time.
Also, other plugins had produced similar results in Podium. You wa shock is a classic example for me.
Ben
Interesting. I haven’t tried it yet in Podium but I have gotten quite good at getting Nucleum to crash in other apps.
As you mentioned, monitoring is important. I find that timeframe varies a bit (sometimes I have a crash within the first two loads, sometimes it takes many more) but that I could get through well over 30 repeated loads without crashing if I wasn’t playing any notes through Nucleum.
In my own tests, the sessions contained one instance of Nucleum 0.90 and nothing else. Most recently, I have been creating the crash by reloading the same test preset using the internal browser over and over again. I started with my own presets and (after replicating it with multiple files) using the default Kinabula preset. I am currently testing that preset except with voices set to “Mono Hold” as I think that earlier test files may all have been polyphonic…
I was able to recreate the crash with “Mono Hold” as well. I am going to try moving from the internal browser to .FXP files to see if the results are the same.
Has anybody else had Nucleum change its “click” behavior?
During the last few days I have had a couple instances where I would open up Nucleum (either 0.27 or 0.90 as it seems to happen with both) and find that dials and menus exhibited a difference response to mouse clicks.
Normally, I simply click and drag in order to, for instance, change a dial value. In these cases, I would have to click and release or double click in order to change values. I have been willing to chalk it up to a system anomaly but I also recently had it happen in two hosts, both with fresh song loads, consecutively.
Now, unless anyone else has had this happen, my best guess is that some key on my keyboard got stuck and I just didn’t realize it or something similar. This issue has not come up many times, but it did come up multiple times so I wanted to just check with others.
H-man@Per wrote:
Now, unless anyone else has had this happen, my best guess is that some key on my keyboard got stuck and I just didn’t realize it or something similar.
Dodgey mouse maybe 😆 I haven’t had anythig like this or similar and I have been reworking a bunch of presets created in the earlier versions as well. Sorry to hear it….
Probably should ask Frits while I’m here. If we want so submit presets for possible inclusion in the release, where would you like us to put them and when by?
I also just spent an hour or so working on presets with no issues 🙂 but I was avoiding swhitching during playback.
My only remaining issue with Nucleum is the nipple on the dial 😛 It is tactile and it works to kind of have some thing to put the mouse on but somehow it just annoys me 😕
Is it too much to ask for a non-nipple version??? Perhaps the line on the dial could go all the way to the centre?
Ben
ZynewaveOk, I just got the hang bug for the first time. It happened when I used the “Load Program” menu, while holding a chord. Do you guys get the hang bug when simply changing programs using the arrow buttons at the top of the window?
I’ll try to hunt down this bug, as it of course is a serious issue. Fixing the bug may require a fix in SM. The preset management in Nucleum is using the standard components that SM offers.
Zynewave@H-man wrote:
Probably should Fits ask while I’m here. If we want so submit presets for possible inclusion in the release, where would you like us to put them and when by?
Eventually I’ll create a wiki page where users can upload their presets. For now you can email it to me. No rush.
My only remaining issue with Nucleum is the nipple on the dial 😛 It is tactile and it works to kind of have some thing to put the mouse on but somehow it just annoys me 😕
Is it too much to ask for a non-nipple version??? Perhaps the line on the dial could go all the way to the centre?
Arrgh, did you have to call them nipples? 😆
Now I have to change them.
H-man@Zynewave wrote:
Arrgh, did you have to call them nipples? 😆
Now I have to change them.
😆 😆 😆
Frits thanks, as we would say here you are a top bloke! I was laughing myself when I wrote that thinking “…man this is pedantic, I’m gonna get kicked and banned for this!”
In return I’ll keep working my butt off on my preset bank ( …I actually think I just made a pretty convincing trumpet 😯 ).
Would I be right in guessing that all the parameters are pretty much finalised now?
Oh and the latest additions that came in 0.9 are fantastic. I’m lovin this synth. SM issues aside, one can now get some very complex sounds out of this thing.
Ben
Zynewave@H-man wrote:
Would I be right in guessing that all the parameters are pretty much finalised now?
Yes, unless user feedback convinces me that I have overlooked something.
Per Lichtman@Zynewave wrote:
@H-man wrote:
Would I be right in guessing that all the parameters are pretty much finalised now?
Yes, unless user feedback convinces me that I have overlooked something.
Unless there is the option of adding dotted durations to the sync times of the effects or LFOs, I think things have gotten pretty balanced. For trance, it is frustrating note having the option of dotted 1/8 notes though. But I can always use external delays. 🙂
As far as the bugs, I will try to test some more very soon but I still have the flu and that slows things down a bit.
Zynewave@Per Lichtman wrote:
@Zynewave wrote:
@H-man wrote:
Would I be right in guessing that all the parameters are pretty much finalised now?
Yes, unless user feedback convinces me that I have overlooked something.
Unless there is the option of adding dotted durations to the sync times of the effects or LFOs, I think things have gotten pretty balanced. For trance, it is frustrating note having the option of dotted 1/8 notes though. But I can always use external delays. 🙂
I can add dotted divisions without affecting the parameter much. But then what about triplets? Don’t I risk fans of other genres than trance will miss the triplet option?
ZynewaveVersion 0.91 is uploaded.
Changed the appearance of the dials.
Previous Nucleum versions were all built with the latest SM 1.0.9 release. This 0.91 version is built using a beta of the upcoming SM 1.1 release. According to the SM beta release notes there are fixes relating to hangs in various hosts, so I thought this may solve the preset loading hang bug. My tests so far has not produced hangs with this new version. Please let me know if you still experience the hang bug.
Also added a “Shimmer Pad” patch.
PodianerI get cpu spikes and audio dropouts each time I change the preset. I have not experiences with softsynths, because most of the time I record audio. Is this supposed to happen on my 2.66 Dual core machine?
I really would encourage you Frits, to put Nucleum in the Podium installer when it’s done. Seems to be a very versatile plugin you put together here.
H-manFrits, Thanks for the UI change! Same feel, better look IMO.
@Podianer wrote:
I get cpu spikes and audio dropouts each time I change the preset.
Yes, the spikes are still there in 0.91 but only if you use the arrows on the UI. I find that it doesn’t spike though when loading presets from the Track Inspector, with Auto-assign preset on. 😕
No crashes this time though. even after some exhaustive preset browsing. 😀
@Podianer wrote:
I really would encourage you Frits, to put Nucleum in the Podium installer when it’s done. Seems to be a very versatile plugin you put together here.
+1
Per Lichtman@H-man wrote:
Frits, Thanks for the UI change! Same feel, better look IMO.
@Podianer wrote:
I get cpu spikes and audio dropouts each time I change the preset.
Yes, the spikes are still there in 0.91 but only if you use the arrows on the UI. I find that it doesn’t spike though when loading presets from the Track Inspector, with Auto-assign preset on. 😕
No crashes this time though. even after some exhaustive preset browsing. 😀
@Podianer wrote:
I really would encourage you Frits, to put Nucleum in the Podium installer when it’s done. Seems to be a very versatile plugin you put together here.
+1
If you’d like I could furnish the extensive Process Monitor logs to illustrate the point, but the gist is that my findings are the same: v 0.91 does not crash in the same tests for internal preset loading as 0.90. Here is the longer version. Kudos Frits!
With the filters I applied in Process Monitor, I basically ended up using it to keep track of how many times I load a preset before app crashes. With version 0.90, I loaded presets 78 times the first run, 9 times the second run and 24 times the third run before causing a crash. 78 was the highest number I had logged so far. The timing is rather specific so I can’t accurately get it to crash within a certain number of loads with my torture session. With 0.91, however, even loading the preset 128 times did not cause a crash. This took about 6 minutes and got very boring. 🙂 Starting over, I tried again and stopped trying to crash it after 71 loads without issue. Is that sufficient to confirm proper function?
I preferred the old dial design (felt a bit more intuitive to be able to have a knob to grab onto rather than just the edge of a dial) but opinions are a dime a dozen and I’d be hard pressed to provide a concrete argument for one over the other. Besides, there are way more important things afoot. 🙂
H-man@Per Lichtman wrote:
I preferred the old dial design (felt a bit more intuitive to be able to have a knob to grab onto rather than just the edge of a dial) but opinions are a dime a dozen and I’d be hard pressed to provide a concrete argument for one over the other. Besides, there are way more important things afoot. 🙂
Sorry Per. Now I feel like a total heel. 🙄
The dials as they are now are very similar to the traditional Podium Level and Pan dials which I and others always quite liked.
My bad …right, back to business. 🙂
Ben
rinxaiHey, I like the new knobs! I prefer, very nice!
Dots and triplets please!!!
I have had some instances of buggy behavior, but no crashes yet. In depth report to follow later.
There are a few minor issues with sounds that modulate in some ways when no modulation nor fm is active. Somewhat like an unpredictability in output, which can sometimes add interesting character, and sometimes not. Its quite subtle but is noticeable on certain presets. More details once pinpointed.
Per Lichtman@rinxai wrote:
Hey, I like the new knobs! I prefer, very nice!
Dots and triplets please!!!
I have had some instances of buggy behavior, but no crashes yet. In depth report to follow later.
There are a few minor issues with sounds that modulate in some ways when no modulation nor fm is active. Somewhat like an unpredictability in output, which can sometimes add interesting character, and sometimes not. Its quite subtle but is noticeable on certain presets. More details once pinpointed.
rinxai, when you post later on could you mention/provide links to, specific presets that demonstrate the behavior? I’d be happy to verify and see if I could replicate it in other patches on my system.