randy's Recent Posts
The AUDIO "pre" is patched to the OUTPUT "aux in" in this patch. So if you remove that patch cord, you should no longer hear the dry signal.
thanks garf!
In general, any grain will keep playing until it either ends, or is stolen. As you've noted, when the retrigger rate is 0, the length of a grain is infinite, so it never ends on its own, and things get a bit weird.
When switching to a new preset, certainly I wouldn't want the old grains to end abruptly. I see the ability to "crossfade" presets as very useful. Unfortunately we are left with only the current (new) sample to display. Possibly there could be some kind of indicator that the older samples are no longer in sync with the displayed sample. making the lines dotted for example.
I can see how old samples might "reappear" if the number of voices is messed with. This would be a bug and shouldn't be hard to fix.
There is plenty of room for UI refinement. I'm going to add some kind of numeric entry solution one of these days.
Using the granulator with a rate of 0 is a feature that sort of snuck in against my better judgement. Yes, the modulation multiplies the rate, and in general the rate dial is logarithmic, like the oscillator pitch dials. So multiplying anything with 0 you get 0 again. A separate toggle for 0 might be better.
A new Virta beta:
http://madronalabs.com/media/virta/Virta1.2b5.pkg
Hopefully this fixes the LPG / delay weirdness. The problem was in how the delay responds to silence. I'm not sure how it never came up before! thanks testers.
This will be the last beta unless there are any show stoppers.
I'm making notes of all these things and will get to them ASAP, but after the next update.
The delete key thing never worked properly in all hosts. i spent a bunch of time trying to get it to, because I agree, it was useful! Supporting keyboard input seemed to be a real difficulty with using JUCE framework. That was a while ago, so they have probably improved it. I can look at it again.
Also, I would like to add an interface that works well for tablets. So, maybe you select all the patchcords and you see a kind of menu of what you have selected, with some [X] boxes on it for deleting some or all.
I think this is fixed already. If not I'll investigate after the coming update.
Thanks for the detailed info—I'll investigate this after the coming update.
I am literally working on this today. I will release an update as soon as I can.
Can reproduce the weirdness. Working on it.
NEW BETA: 1.2b3
http://madronalabs.com/media/virta/Virta1.2b3.pkg
This should fix the protocol open bug as well as AU / installation issues. The AU problems were with hosts using an older API to open the component.
If it's happening in Ableton, I am not aware of any workarounds. The release should be very soon.
I have to get these other updates out first. I guess you have seen that I am working on updating all of the plugins with a new licensing system and many other improvements. After that I can get a Soundplane update out. There's a lot going on here and only one developer. Thanks for your patience.
Please write up the problem with the Max loading and email me the details, then I'll make a ticket so I'll be sure to remember when I return to the Soundplane code.
Either once or twice a year.
I tried an auval -a (if that was even helpful) ?
auval is not to fix anything there, but to get me some information I can use to fix any problems. You can also use it to diagnose problems. If you run "auval -a" it will show all the plugins. Then you can look at the name of the plugin you want to test fully and do for example "auval -v aumf Vrta MLbs" to validate Virta.
If the AU is not running please do "auval -v aumf Vrta MLbs" and send me the result in email.
Also you can try clearing your audiounits cache and restarting.
The VST is exactly the same thing as the AU. You can literally copy the .component into the VST folder, rename it to a .VST, and that is the VST. So any problems with loading the VST but not the AU are likely to be fixable in the host. Is it looking in the right directory for VST plugins?
Are you on Windows? There is an issue with some hosts on Windows and I am working on a fix. If you have FL Studio for example you can select "fixed size buffers" to work around the problem. If not please let me know. A fixed version will come soon. Thanks for your patience.
Thanks for writing with the solution. I haven't been able to follow along because I don' t have a Push 2... one of these days!
OK, new beta is at http://madronalabs.com/media/virta/Virta1.2b2.pkg
Loading issue fixed but I haven't looked at the protocol problem.
OK, I'm not using portaudio in the plugin so this is just a build issue. fixing...
eh, odd. I will try installing Sierra here and see if I can duplicate. Meanwhile if you have time, please try restarting, see if that helped, and run "auval -a" and then "auval -v aumf Vrta MLbs" in Terminal and email me the results.
Thanks.
64 bit?
stick around, things are always happening!
Thanks for sharing your experiences. I have yet to test with Sierra. Now that the beta of Virta is out, I will give Sierra a try.
Wow, that's exciting the USB hang seems to have gone away. There's nothing I've been able to do to affect this, which was quite frustrating.
I've been on other stuff, but the touch tracker work will get a debut soon with the next Soundplane update.
Thanks for writing. I have a new hp laptop for Windows 10 and as soon as I get this next release out, I'm going to see about dual-booting it with Ubuntu.
Haha, I think some of the people waiting on this software update might disagree with you! But it's true, fall is a great time for new shirts. Please stay tuned.
Sorry, there is a problem with the note event code. Good news is, I'm working to fix it right now and the release should be soon.
I take it you are on Windows? I only see the issue there, for some reason.
The "fixed size buffer" setting in Reaper should work around the problem. Here are some other tips in a thread: http://madronalabs.com/topics/4541-buffer-issues-with-aalto-and-reaper
[EDIT] I might have been thinking of Fruity Loops re: the fixed size. I just went to test it and I can't find that setting in Reaper.
Way cool ! Great demo sounds.
Seems like it's working as intended. The plugins each remember the size of the window for each instance. So you can make a little Kaivo and a big one and they will remain that size when you load the project the next time.
What I think you are asking for is a global preference, that will control the size of any new window. This is a feature I can add.
The apparent CPU usage might be much better with this next version because i fixed some memory access problems that might be affecting some systems. After this, yes I do plan to work on multicore.
I have a Windows 10 machine set up here and I'm still trying to fix the stuck notes problem.
Kaivo normally remembers the window size. I checked in Bitwig and it works for me. Could it be only big sizes that are not being recalled properly? I don't have that much screen space to check.
Unfortunately this is a Logic problem as far as I can tell. If you pull up Aalto in Ableton Live, you will see that the exponential parameters like cutoff are handled correctly.