randy's Recent Posts
The good news is I finally saw this bug occur on my own system. I did a long torture test session changing patches in Logic and was able to see some bad input from Logic that I hope is the cause of these problems.
moved to software forum... i should really fix it so people can't post to the News forum, my bad. I look forward to hearing your sounds!
In other words, I'm getting somewhere? Sweet!
No dropouts here for your patch. This issue is highest priority for me though.
If you try this demo component do you get the dropouts?
(Component only - I'm assuming you know how to drop this in the right place)
[EDIT] - updated component again. Should print all the numerical errors if any, and there's a button for you to copy them. click the nearly invisible button on the right to bring up the debug output.
Think of each sequencer's position as a continuous number with a fractional part, not just the integer step number. The light just shows the integer position. But depending on where the actual fractional position is within the step, you can get different results.
This is what the difference is between your example and the preset. If you change your example so that the number of steps is 1 and rate is nonzero, you will get the results you expect.
Uh, I see now but I have no idea. That's very strange. Thanks for making the video. I'll investigate soon because, if there's some behavior I don't understand, maybe it's a clue to one of the other bugs happening.
It's a little weird but not that weird. I made a mistake by believing what you wrote in the text in your movie. Only one voice is detuning a bit when you change slider 4, not all of them. To verify, turn all the other faders to the same note, and hear the increased beating that results for turning up fader 4.
What's happening is that one voice gets mostly the signal from fader 3, with a tiny bit of fader 4 mixed in. This is because of the way the interpolation works. When the rate is 0. and has never been changed, the fractional part of the step is 0.0001 or something like that. If you set the # of steps to 1 and turn the rate up, you should get more obvious behavior.
I don't have too much time now but I'll try to explain better in the manual.
Thanks for the report. I want to fix this ASAP.
It doesn't quite make sense to me what you're talking about, because I don't know what you mean by "affect the de/tuning of the unison notes". Maybe the difference is where the sequence is within the step. It's kind of complicated to explain without pictures. I'm trying right now in the manual, so maybe stay tuned for a full explanation. The outputs with 0 steps in a sequence and 1 step will be different, and if you run the clock, then stop it, it will be frozen in the middle of a step and you can see different results.
no easter egg type thing is intended. and if vst and au work differently, that would be a bug. can you tell me a sequence of steps to do, that gives different results for the VST and AU versions? You could start from default or any factory patch.
.mlpreset files should be the same on both platforms. It's just XML.
On the Mac there's also an .aupreset format for full AU compatibility.
cool news! ekwipt, can you try using the VST with the default 32-bit mode off?
I like these ideas. The signal dials would be hard to make in hardware though :-)
I made an update of Aalto to fix a real problem with the sequencer that crept in at the last minute. The new demo is up on the website. If you are a registered user, you should get your links in the mail over the next couple of hours.
fixed sequencer UI bug
fixed mouse wheel behavior on Windows
fixed typo in reverb algorithm, sound now restored to v.1.1 glory
demo version now prints debug info
Thanks for the feedback. I may change that wording. I'm not the kind of person that would make my software do something malicious.
Short answer is, if you are offline, there will be no problems.
I am willing to discuss in more detail, but I'm headed off on vacation for a week.
Sorry you're having difficulties. I can't think why examination would just hang. I can suggest you try the VST, assuming DP runs VSTs. I'm on vacation for a week starting later today--have added this issue to the list for when I get back.
It's still a good suggestion.
Sorry to hear it. What kind of computer (CPU) do you have?
Aalto 1.2 for Mac and Windows will be available this Friday, June 10 at around noon Seattle time.
New in Aalto version 1.2:
- Mac and Windows VST versions
- 64-bit Mac AU / VST
- 64-bit Windows VST
- Improved performance (20-50% faster than version 1.1)
- Brand new patching interface
- New cross-platform preset format
- Improved dial ballistics
- Over 100 new presets from Alessandro Cortini, Richard Devine, Rory Dow, Surachai, Edward Ten Eyck and Madrona Labs.
Mac people, you are really going to enjoy so much more smoothness as compared to 1.1 --- I'm really happy to send this one out. Now I have to go make the scripts for the website that do the watermarking and emailing, and spend a little more time on the manual. I might be kind of quiet until Friday. Seeya then.
I heard another report from a customer that 1.2.1 fixes the Maschine problems on Mac! Would love to hear more confirmation of this.
Hi John, I think he is making good products too, so I just decided to get in touch at some point.
@ekwipt, thanks for the report. Be sure to try Aalto 1.2.1!
The best thing here would probably be a diagram.
Anyway, the reverb dial is a reverb send for each voice, simple as that.
My first reaction was "I have no idea..." but then I saw, what you're trying to do should really work. So I looked through the code and I think I may see a fix that would give the behavior you want.
I'm not going to push out another 1.2.x release before a couple of weeks though, unless there's some really bad problem in the meantime. So, I will get this working for you, just not right away.
To confirm, when you change a dial, your MIDI stuff does update, correct?
Fixed. Thanks for letting me know!
Good idea about alt... or something to get semitone steps. I'll think on this.
Not sure about the color idea, if only because I don't thin it would look nice, or be very readable, esp. with more voices. But keep 'em coming...
You can even get two totally different 8 note sequences... see the patch 2x8 seq or something in the "techniques".
you are right. broken build script = old version in there. I'm going to upload new mac versions now...
I do see CPU spikes switching presets in Logic . I don't know what I could do about that. I might work on it, but not soon. In my experience Logic is less efficient than other hosts.
I do not get crashing or any problems with more than one Aalto. I am on Logic 9.1.3 however.
Maybe this will be better for you in the 1.2.1 version.
create a different pitch sequence per voice
you can't exactly do that. Think of the modules as faceplates to 4 identical modules, like a polysynth. The signals going through them can change, but the settings of the front panel knobs can not. since the sequencer has only the 16 sliders, the same sequence goes to all the sequencer voices.
You can do some tricks with the voice signal from KEY though, like set "offset" or "rate" in the seq to a different value for each voice. or, you can set the pitch of the osc to a different offset for each voice for weird harmonies.
Thanks for the discussion, people, it's helping me finish the manual... :-)