NOTICE: Get ready for final regression phase

We are reaching the last phase of the beta.

In a short while we will freeze any code changes, and have 2-3 days of massive regression testing for the final version, before getting it published.

It would be so great if you could all massively test and use it, having in mind that it is going to be the final version for release. We will only make last minute changes if real blockers are found during this test.

Thank you for your great work and contribution !

I still cannot get over the ableton vst 32 hurdle i just cannot connect to the sub.

My Sub and editor have worked great all week! but today the editor can not find the sub, and device manager has a yellow triangle on the sub37 driver to

nothing works at all with it, I have tried restarting live, sub, pc and editor but no change.

thanks

So I have had to uninstall the driver and then install again,

The sub now works again,

for me this wouldn’t be a problem if I had to just install again, but every time I install the drivers for the sub37 my miniataur stops working, so I have to find out what’s the problem with that now! :frowning:

thanks

see Amos’ comment about Minitaur driver updates in other thread

http://forum.moogmusic.com/viewtopic.php?f=20&t=24834&p=152515&hilit=minitaur#p152515

Thanks
I missed that one, its actually my post :S

I guess i have something I’ve noticed and i might be late to the game but when I use the AU version on my build below the automation works as you would think like other plugins in Live. I touch the knob with the mouse or on the sub 37 and ableton automatically detects what I am adjusting and brings up the current automation lane displayed. When I use the VST version the behavior doesn’t work the same. Live does record the movements if i use the hardware or the mouse but i have to go into the I/O section and find the automation manually. If i use the mouse to select the parameter/ knob on the plugin it will then bring it forward. I am just curious if this is normal behavior or not.

Thanks for checking,

Are other plugins act just the same way (AU vs. VST) ? Or does the Editor act differently ?

Thanks, please let us know if the driver issue rises again.

As long as it seems to work for other users and computers, it looks like it’s specifically related to your system and setup,
we will still need to check this though.