Full Version: plugin requests
I don't know if i am missing it somehwere on the forums... i know the v .9 was released very recently so i am not expecting a miracle but i really liked this fancy plugin. if anyone hears anything about the volume control, track info panel, tabbed panel stack, or project M, let me know i am dying in anticipation.
0.9 is still in beta (currently is beta 8) and the sdk for plugin developers has not been released so there aren't any updated versions of 3rd party plugins available since no one can make them until 0.9 final is released and the sdk required will follow after that. patience is a virtue, heh
-daz
-daz
QUOTE(DrO @ Sep 15 2005, 09:11 PM)
0.9 is still in beta (currently is beta 8) and the sdk for plugin developers has not been released so there aren't any updated versions of 3rd party plugins available since no one can make them until 0.9 final is released and the sdk required will follow after that. patience is a virtue, heh
-daz
-daz
i figured, and i have patience i was just curious as to how it all worked, i am reather new at understanding these processes. i hope i didnt sound like a jerk. thanks for the response.
It works something like this: Core developers would rather work on core bugs and features than chase bugs introduced by 3rd party components. Just telling people not to install components obviously wouldn't work. 
Also, the SDK may change in not-neccessarily-forseen ways during the pre-release process, causing additional 3rd party bugs were open development allowed.
Certain privileged components with strong ties to the core are given access to the pre-release SDK so that they can work with the new system, provide feedback and suggestions to the core developers, and supply such core components for beta testing. After all, who would seriously stress the beta if all it could do was play standard inputs?
As long as the plugins you have requested have not been abandoned by their respected authors, they will be updated in turn. When this is isn't known and asking will only result in having the thread shot down and locked as someone helpfully demonstrated just today (for umpteenth time).
If you really need 3rd party components for your audio enjoyment, it is recommended that you stick to the official release. However, if you can live without them, use the beta and contribute by explicitly detailing any bugs you may find. And remember: "Good things take time."
Also, the SDK may change in not-neccessarily-forseen ways during the pre-release process, causing additional 3rd party bugs were open development allowed.Certain privileged components with strong ties to the core are given access to the pre-release SDK so that they can work with the new system, provide feedback and suggestions to the core developers, and supply such core components for beta testing. After all, who would seriously stress the beta if all it could do was play standard inputs?
As long as the plugins you have requested have not been abandoned by their respected authors, they will be updated in turn. When this is isn't known and asking will only result in having the thread shot down and locked as someone helpfully demonstrated just today (for umpteenth time).
If you really need 3rd party components for your audio enjoyment, it is recommended that you stick to the official release. However, if you can live without them, use the beta and contribute by explicitly detailing any bugs you may find. And remember: "Good things take time."
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.