Yeah it's really frustrating for me, too. This is a very good suggestion -- probably what's reasonable at this stage would be to have a setup page for VSTs that merely describes the early state and mentions you can set a path in the Preferences window for when you're ready to try that. My only small hesitation right now is that at this stage, with the amount of problems being seen, I'm almost more interested in gathering information about what's going on.sinkmusic wrote:- Having a program that crashes even before you put your hands on it can be very frustrating, so why not install without asking the VST path, adn then make a "preferences" fodler for the user to select his VST folder.
I've had this page up -- it's a public wiki so people are welcome to share their VST experiences. I have no problem at all tracking what doesn't work, but it's not yet reasonable to track what does work (at least for me, acting in any sort of official capacity). The issue is that, of the problems I've had reported, so far they've either been fixed in the 1.0.3 or I can't reproduce them, with the majority falling into the can't reproduce category. I test on dozens and dozens of VSTs and things have been working pretty flawlessly here, which is obviously not the experience many people are having. So I'm not about to begin making claims on what will work. There's clearly an environmental issue I need to track down.sinkmusic wrote:- make a thread in the Wiki "known to work / known to crash VST plugin", it ocud be useful both for the users, the seq dev team, and the concerned plugin's dev... That way, too, i coudl be able to make a "beta test" folder with just a doen of "known to work" plugins, and have fun with sequitur...
thanks much,
eric

