ZynewaveZynewaveVersion 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.
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?
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.
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.
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.
ZynewaveI am not an expert in the Reaper feature set, but I would say that the two programs have their strengths in different areas. So it is difficult to recommend one of the two without knowing more about your working method. Although you say you don’t have much time to experiment, I would highly recommend that you install the demo/trials of both applications, and see how you progress.
Zynewave@Per Lichtman wrote:
My computer is a bit glitchy at the moment (plus I have the flu) so I am going to have to re-check this later but is anybody else experiencing long delays or crashes when changing between presets either using the internal preset loader or by switching .fxp files (or equivalent) in a host? I know that earlier versions .fxp files won’t load in the new one so don’t worry that I am getting that mixed up. 🙂 Not a confirmed issue here but I figured it would help to have others looking for it too… preferably other healthier people. 😉
Which host(s) does this happen in? Have you tried more than one host?
Zynewave@H-man wrote:
@Zynewave wrote:
I can get rid of this spike by skipping the check and always call the FM processing, but this will result in a small increase in CPU for patches that doesn’t use FM.
Okay that makes sense. However what would then happen if you were modulating an FM dial on a low setting with a sine wave that effectively swept the FM dial to 0? Perhaps it’s best if I cook up a test for this tonight and see what the results are.
No need to worry. If any of the FM modulation parameters are used in the matrix, then all FM processing is running always.
Zynewave@H-man wrote:
1. When the synth is idle (podium stopped, default Kinabalu patch), moving the FM dials from 0 to full quickly causes a big spike on the resource meter in the bottom right.
This happens because I’ve put in a check that skips the FM processing when an osc is not FM modulated (all dials set to zero). The CPU spike occurs because SM rearranges the code when the FM processing on/off state changes. I can get rid of this spike by skipping the check and always call the FM processing, but this will result in a small increase in CPU for patches that doesn’t use FM.
2. Occaisionally (no specific example sorry) I find that there is a lag on parameter changes where a change, for example to an FM dial, is not heard until another parameter, filter cutoff for example, is changed.
I haven’t noticed this myself. Does it happen during playback, i.e. during a heavy CPU load? Are you changing the parameter via MIDI CC or the mouse?
ZynewaveUploaded beta version 0.90.
With these last few changes I now feel that the synth modelling is complete. What remains now are presets, CPU optimization and a few UI flaws with the update of the text readout below the dials.
Changes since the 0.27 version:
Swapped the chorus and delay effects. I think it makes more sense to apply chorus before delay.
The chorus effect is now a true stereo chorus, with extended ranges for the delay, sweep and speed dials.
Added separate delay dials for left and right channels to the delay effect.
The two delay dials and the two LFO speed dials have been extended so that the upper half of the dial range selects between tempo-synced beat divisions.
ZynewaveZynewaveI can’t find a upload ftp command in my IE7 page menu. There is a “Open FTP Site in Windows Explorer” command. I’m on Windows Vista, which may be the difference.
Can anyone recommend some freeware FTP explorers?
I’ve previously used:
http://filezilla-project.org/
I stopped using it when I got Windows Vista, and found that I could use Windows Explorer for all my FTP needs.
ZynewaveI downloaded the “Bass.wav” file, and it appears the file is corrupt. From looking at the header contents of the file, I can see that about 20KB is missing from the end of the file.
Whoever uploaded the Bass.wav, can you please check if the file size on your local disk is larger than 76504576 bytes. If different, then it’s probably the upload that was interrupted.
While loading the corrupted wav file in Podium, I noticed that Podium does not finish the waveform profiling due to file errors. I’ll get that fixed. Maybe that is what caused problems for some of you while trying to play the files.
ZynewaveTo test whether it is a plugin that is the cause for the CPU rise:
Once you’ve stopped playback and the CPU has risen to 45%, start bypassing your plugins one by one using the X button on the tracks, and see if there is a particular plugin that causes the CPU to fall back to normal.