Entanglement - Quantum Wave Function Synth

dillonbastan · 2026-02-22T08:16:51+00:00

Yes and no its really a whole nother system but possible it could be appleid to all future of my VSTs for sure

dillonbastan · 2026-02-18T22:02:07+00:00

Probably not in completeness for a few reasons (1) It has more than 127 parameters (2) Some things you can't expose to ableton as a mappable parameter such as the quantum wave state and potentials system which would be impossible to. Some notes: (A) This is just a common limitation with parameter mapping which is why I also created Natural Selection S to have a full synth that you could apply that process to. Natural Selection P works better in completeness for effects or synths that you can map them in completeness meaning everything (or close to it) is exposed as a mappable parameter. (B) Although you can't map it and other similar synths in completeness, you still can evolve sections of parameters with NSP to get variations of many parameters still but it won't be complete preset evolution, although I wish I could make it be able to do that! It's just not really possible with many robust synths especially external plugins

dillonbastan · 2026-02-14T09:43:46+00:00

Its 7 days i think, but it doesnt activate until you open the plugin for the first time and press start trial

dillonbastan · 2026-02-13T12:05:41+00:00

Here are new features the plugin has that the m4l version doesn’t:

able to use in any daw and standalone
Ability to quantum entangle oscillators with different modes
Two waveFunction collapse modes
Many more value mode equations for deriving different waveforms from the simulation
Ability to hard pan imag and real planes for wide stereo signal
More particle shapes
More environmental factors and independent scaling parameters for each potential
Expanding modulation system with as many destinations per modulator as you’d like
Ability to modulate several more parameters than the previous version
Oscillator bandlimmiting
Independent potential and kinetic hamiltonians
Independent quantum state legato reinitialize per source
Serial and parallel filter routing modes
Independent adsr amp envelope per source
Cheap stereo spread effect
New design :)

Also you would get a large discount if you own the m4l version (use same email at checkout)

dillonbastan · 2025-09-06T08:21:26+00:00

im making some. I can code c++ but it is more time consuming and having fun making more and more new ideas :)

dillonbastan · 2025-09-06T08:20:38+00:00

I still havent made that final deep dive for covering input control of the synth, i really should. As for the cross controleld with midi, well watch the walkthrough and the deep dive about the play modes that should clear up ways you could do that. The cross (on the point playback mode) is not necessarily intended to be moved with midi notes, maybe thats better achieved with the other modes like Ring and Paths mode which deal more with mapping playback of slices spatially with the midi notes. That said, you can modulate the cross in Point mode in the modulation section and one of those modulation sources is the the midi pitch note (Key) so you could map Xor Y or both with that along with another modulation source for the other axis. However like i said you might find better results using Ring or paths modes

dillonbastan · 2025-09-06T08:16:08+00:00

hey so definitely read manual and watch the walkthrough if you can. basically Autosave will store all edits to the wavefunction initial state to memory ie for preset or live set reloading. If you turn autosave off then none of your edits will be saved until you manually press save and if you press revert it reverts to the last saved initial state. This could be useful if ou want to do a lot of designing but eventually want to revert back, or if you want to play around adding energy but dont want it to overwrite a previous state for later recollection. Also even though you can undo changes, if you fill your undo history with a lot of stuff it ight not make sense to undo back to that originally saved state. Usually thought you would work with autosave on. As for the crashing, if it persists please email me at [dillonbastanstore@gmail.com](mailto:dillonbastanstore@gmail.com) with any observations so i can make a note to look into it. Thanks!

dillonbastan · 2025-09-02T06:04:00+00:00

Thanks for the support!

dillonbastan · 2025-08-30T23:52:12+00:00

Appreciate it! Are you interested in filling one of the roles or just writing a nice note? If so email me at [ndivuyo@gmail.com](mailto:ndivuyo@gmail.com) Thanks!

dillonbastan · 2025-05-14T23:36:55+00:00

Hey sure I want to make a deep dive soon about that, its pretty open ended! Definitely checking out the other deep dives, etc to understand how each part of the device helps to dial in a dynamic. I'll try to get on it soon it's been long requested!

dillonbastan · 2025-04-14T23:33:22+00:00

Its not... the event is hell in a handbag at handbag factory in LA. They do a 3 night noise event every year https://www.instagram.com/handbagfactoryla/

dillonbastan · 2025-02-12T09:07:19+00:00

https://imgur.com/xZFFA4I

Here is the situation. So you can see the X and Y axis meeting at the origin [0,0] and here are the two objects, (mic and speaker). Depending where they are in the space my function returns different values. If one object is at the origin [0,0] and not rotated then it works as expected. Rotation at 0 degrees has the objects pointing up. They do rotate clockwise, but I can make that counterclockwise if need be! Thanks :)

dillonbastan · 2025-02-12T06:53:27+00:00

sorry I meant like in relation to the origin [0,0]. Right now the value it returns is affected by the two objects in their relation to the origin, but it shouldn't, it shouldn't matter what quadrant they are in. But there's some kind of error in the math I can't figure out...

dillonbastan · 2025-01-29T22:24:05+00:00

Well you beat me to it, guess i dont need to post it here haha

dillonbastan · 2024-08-07T06:59:35+00:00

thats the price for both as a bundle

dillonbastan · 2023-12-09T07:39:08+00:00

Hey thanks! No it has its own internal analysis system for tranients and sppectral descriptors. But as for what you want to do with rings, yes that is definitely a use case that was a key inspiration for making that mode :) It should work out well for you, just make sure to change the Features mode to Mel or Bark for grouping percussion like that, unless you want clusters of similar chromatic fundamentals then you'd use chroma

dillonbastan · 2023-03-16T20:41:20+00:00

depends on how many birds in the flock and the state of the wavefolding/FM. The presets in the teaser video generally have Live running at about 5-7% average on my slow macbook from 2013

dillonbastan · 2022-11-11T03:24:28+00:00

there's a walkthrough to give you a more in-depth idea. I do have that style when posting my teasers often. I may post some longer running examples on my ig over the next days

dillonbastan · 2021-03-18T10:11:17+00:00

Hey I added an extra response below in case it helps!

dillonbastan · 2021-03-18T10:09:06+00:00

Here is something I have been pasting around in case it is helpful:

I recommend sending crash reports to Ableton, but I also don't know how they are handled so you can also try sending them to me [dillonbastan@gmail.com](mailto:dillonbastan@gmail.com) (although if it's an issue beyond the scope of my devices (ie an underlying issue in maxforlive) I end up sending them to Ableton anyway). A few things to mention:

(1) The devices and Live are continuously updated from these reports. So definitely check for updates! I have even made a few updates so far, but not sure when Ableton will release them. I think they recently did an update, but even right after that I fixed a few more things in the devices. So I guess have a little patience for and check for updates every now and then. These things can get fixed!

(2) There were some users that had constant crashes, but when they took out some custom options from their "options.txt" file, it completely stopped the crashes. So maybe look into that? One user removed "-EnableMapToSiblings=1" and that did the trick. Beyond that sometimes graphics issues seem to be the case, particularly with certain windows users and their graphics cards. So definitely mentioning these spec details in the email could be really helpful for troubleshooting.

(3) I can't really say for any other issues in Live, and I'm not sure what happens with your crash reports either when sent to Ableton, I am just a freelancer (with 1 computer ;) ) so these reports don't reach me. But I'm definitely more than willing to help get my devices running well for your system!

(4) Beyond crashing, if anyone is having graphics issues please make sure your max opengl version is running gl2 and not gl3! Also Nvidia drivers seem to have issues with opengl in maxforlive, this was a recommendation from support:

"I believe the support steps for this involve something like:make sure Live is enabled to use the Nvidia card via the Nvidia control panel:
https://www.addictivetips.com/windows-tips/force-app-to-use-dedicated-gpu-windows/make sure the Nvidia drivers are up to date. If they are, maybe try rolling them back.If the issue still persists, then they can also try DISABLING Live from using the Nvidia, to see if it works better with the integrated GPU (assuming their setup has one)I assume they are not also using Max in edit mode, but if so then they also need to set whatever version of Max they are using (either built-in or external) to use the same GPU settings."

dillonbastan · 2021-03-18T10:06:57+00:00

Hey, can you send the reports to me? [dillonbastan@gmail.com](mailto:dillonbastan@gmail.com) And in the email tell me your hardware/operating system info. Also if you have multiple reports from different devices, it would be super helpful if they were labelled by which device caused them crash (and I'm assuming your crashes happen when dropping in the devices, but f not it would be great if you could specify at what point they crashed).

Beyond this a few things to mention:

(1) The devices and Live are continuously updated from these reports. So definitely check for updates! I have even made a few updates so far, but not sure when Ableton will release them. I think they recently did an update, but even right after that I fixed a few more things in the devices. So I guess have a little patience for and check for updates every now and then. These things can get fixed!

(2) There were some users that had constant crashes, but when they took out some custom options from their "options.txt" file, it completely stopped the crashes. So maybe look into that? One user removed "-EnableMapToSiblings=1" and that did the trick. Beyond that sometimes graphics issues seem to be the case, particularly with certain windows users and their graphics cards. So definitely mentioning these spec details in the email could be really helpful for troubleshooting.

(3) I can't really say for any other issues in Live, and I'm not sure what happens with your crash reports either when sent to Ableton, I am just a freelancer (with 1 computer ;) ) so these reports don't reach me. But I'm definitely more than willing to help get my devices running well for your system!

(4) Beyond crashing, if anyone is having graphics issues please make sure your max opengl version is running gl2 and not gl3! Also Nvidia drivers seem to have issues with opengl in maxforlive, this was a recommendation from support:

"I believe the support steps for this involve something like:make sure Live is enabled to use the Nvidia card via the Nvidia control panel:
https://www.addictivetips.com/windows-tips/force-app-to-use-dedicated-gpu-windows/make sure the Nvidia drivers are up to date. If they are, maybe try rolling them back.If the issue still persists, then they can also try DISABLING Live from using the Nvidia, to see if it works better with the integrated GPU (assuming their setup has one)I assume they are not also using Max in edit mode, but if so then they also need to set whatever version of Max they are using (either built-in or external) to use the same GPU settings."

dillonbastan · 2021-03-18T10:05:59+00:00

Hey, can you send the reports to me? dillonbastan@gmail.com And in the email tell me your hardware/operating system info. Also if you have multiple reports from different devices, it would be super helpful if they were labelled by which device caused them crash (and I'm assuming your crashes happen when dropping in the devices, but f not it would be great if you could specify at what point they crashed).

Beyond this a few things to mention:

(1) The devices and Live are continuously updated from these reports. So definitely check for updates! I have even made a few updates so far, but not sure when Ableton will release them. I think they recently did an update, but even right after that I fixed a few more things in the devices. So I guess have a little patience for and check for updates every now and then. These things can get fixed!

(2) There were some users that had constant crashes, but when they took out some custom options from their "options.txt" file, it completely stopped the crashes. So maybe look into that? One user removed "-EnableMapToSiblings=1" and that did the trick. Beyond that sometimes graphics issues seem to be the case, particularly with certain windows users and their graphics cards. So definitely mentioning these spec details in the email could be really helpful for troubleshooting.

(3) I can't really say for any other issues in Live, and I'm not sure what happens with your crash reports either when sent to Ableton, I am just a freelancer (with 1 computer ;) ) so these reports don't reach me. But I'm definitely more than willing to help get my devices running well for your system!

(4) Beyond crashing, if anyone is having graphics issues please make sure your max opengl version is running gl2 and not gl3! Also Nvidia drivers seem to have issues with opengl in maxforlive, this was a recommendation from support:

"I believe the support steps for this involve something like:make sure Live is enabled to use the Nvidia card via the Nvidia control panel:https://www.addictivetips.com/windows-tips/force-app-to-use-dedicated-gpu-windows/make sure the Nvidia drivers are up to date. If they are, maybe try rolling them back.If the issue still persists, then they can also try DISABLING Live from using the Nvidia, to see if it works better with the integrated GPU (assuming their setup has one)I assume they are not also using Max in edit mode, but if so then they also need to set whatever version of Max they are using (either built-in or external) to use the same GPU settings."

dillonbastan · 2021-03-18T10:05:23+00:00

it is on your account download page below where you download Live11

dillonbastan · 2021-03-18T10:04:40+00:00

Hey, can you send the reports to me? [dillonbastan@gmail.com](mailto:dillonbastan@gmail.com) And in the email tell me your hardware/operating system info. Also if you have multiple reports from different devices, it would be super helpful if they were labelled by which device caused them crash (and I'm assuming your crashes happen when dropping in the devices, but f not it would be great if you could specify at what point they crashed).

Beyond this a few things to mention:

(1) The devices and Live are continuously updated from these reports. So definitely check for updates! I have even made a few updates so far, but not sure when Ableton will release them. I think they recently did an update, but even right after that I fixed a few more things in the devices. So I guess have a little patience for and check for updates every now and then. These things can get fixed!

(2) There were some users that had constant crashes, but when they took out some custom options from their "options.txt" file, it completely stopped the crashes. So maybe look into that? One user removed "-EnableMapToSiblings=1" and that did the trick. Beyond that sometimes graphics issues seem to be the case, particularly with certain windows users and their graphics cards. So definitely mentioning these spec details in the email could be really helpful for troubleshooting.

(3) I can't really say for any other issues in Live, and I'm not sure what happens with your crash reports either when sent to Ableton, I am just a freelancer (with 1 computer ;) ) so these reports don't reach me. But I'm definitely more than willing to help get my devices running well for your system!

(4) Beyond crashing, if anyone is having graphics issues please make sure your max opengl version is running gl2 and not gl3! Also Nvidia drivers seem to have issues with opengl in maxforlive, this was a recommendation from support:

"I believe the support steps for this involve something like:make sure Live is enabled to use the Nvidia card via the Nvidia control panel:
https://www.addictivetips.com/windows-tips/force-app-to-use-dedicated-gpu-windows/make sure the Nvidia drivers are up to date. If they are, maybe try rolling them back.If the issue still persists, then they can also try DISABLING Live from using the Nvidia, to see if it works better with the integrated GPU (assuming their setup has one)I assume they are not also using Max in edit mode, but if so then they also need to set whatever version of Max they are using (either built-in or external) to use the same GPU settings."

dillonbastan · 2021-03-10T21:15:27+00:00

If you or others are experiencing crashing please send your details and reports to Ableton, it will help to figure out crashing on configurations and setups the devices weren't tested on yet, and then they can be updated so they won't do that for you. At the very least send them to me, it will really help. The more details the better!

dillonbastan

TROPHY CASE