A letter for kb
category: general [glöplog]
Hi,
My PC laptop blew up few weeks ago and I have an unfinished v2m that needs attention... Right now the only working computer I have at home is an Intel Mac with OSX 10.4 Tiger. So, what would be the chances for getting a Mac version of V2 VST plugin?
I have also XCode 2.5 and other dev stuff installed on this box, so I could help with compiling and/or testing if needed. I guess there might be also others out there who'd like to use V2 on Mac.
PS. I sent you also email, but it looks like you're reading Pouet more regularly.
Cheers,
Matti
My PC laptop blew up few weeks ago and I have an unfinished v2m that needs attention... Right now the only working computer I have at home is an Intel Mac with OSX 10.4 Tiger. So, what would be the chances for getting a Mac version of V2 VST plugin?
I have also XCode 2.5 and other dev stuff installed on this box, so I could help with compiling and/or testing if needed. I guess there might be also others out there who'd like to use V2 on Mac.
PS. I sent you also email, but it looks like you're reading Pouet more regularly.
Cheers,
Matti
melw has leading.
I demand a linux version.
I demand a version that automatically generates a complete soundtrack.
not a chance
I demand a bucket!
Poor kb ..
Melwyn's PC ASPLODE!!!
just use boot camp or parallels desktop :p
I demand a C64 port!
Zest, boot camp is not available for Tiger any longer and I've heard running audio programs under Parallels can be frustrating performance-wise. Could still try the latter, though. Anyhow, to my understanding compiling a VST plugin for OSX shouldn't be rocket science, especially when it comes to Intel Mac's.
Hi,
SRSLY: Can't we put that almost eight year old thing to rest now? I mean, nothing against people still using it but can't anyone kinda understand how much fun is it to still have to maintain that thing and how very fed up I am with its "It was 2000 and I didn't have any CPU left" sound when compared to other synths out there (as in outside the demoscene)?
If there is somebody who seriously wants to do a Mac version, chances are I even give out the full source code to that person. It's way more work than a simple recompile tho: the GUI of VST plugins is either "native" or "whatever toolkit you want to use (eg. our own VSTGUI stuff". In the case of V2, it's all GDI+. Wrapped away in a few classes, but still.
And then the whole plugin code is still from times when the synthesizer itself was not reentrant and there was no chance in hell to get more than one instance running without some brutal fakery.
Let's put it that way: If you (whoever that "you" is) are interested in getting all the code, understanding what the VST GUI does and then throwing it away and rewriting it in a clean and platform independent manner, contact me. For any other inquiries... well.
SRSLY: Can't we put that almost eight year old thing to rest now? I mean, nothing against people still using it but can't anyone kinda understand how much fun is it to still have to maintain that thing and how very fed up I am with its "It was 2000 and I didn't have any CPU left" sound when compared to other synths out there (as in outside the demoscene)?
If there is somebody who seriously wants to do a Mac version, chances are I even give out the full source code to that person. It's way more work than a simple recompile tho: the GUI of VST plugins is either "native" or "whatever toolkit you want to use (eg. our own VSTGUI stuff". In the case of V2, it's all GDI+. Wrapped away in a few classes, but still.
And then the whole plugin code is still from times when the synthesizer itself was not reentrant and there was no chance in hell to get more than one instance running without some brutal fakery.
Let's put it that way: If you (whoever that "you" is) are interested in getting all the code, understanding what the VST GUI does and then throwing it away and rewriting it in a clean and platform independent manner, contact me. For any other inquiries... well.
Why not provide it somewhere for download under any arbitrary "don't care" open source license, like zlib license? With an additional README stating you absolutely don't want to have anything to do with it anymore, ever?
kb: see, thats what you get for releasing it! see! in 5 years time the support requests'll really start getting annoying.
actually the saddest part of it all is how few times v2 has been beaten (in the scene).
actually the saddest part of it all is how few times v2 has been beaten (in the scene).
It could probably be used as a very nice set of building blocks for others though.
...and now to turn the discussion into a "my synth is better" fight!
killer: because all code around the synth core is ugly and hacky as fuck (I've written the first GUI version in less than two days, the Winamp plugin was done when I was so drunk that I can't even remember having coded it, and Paniq's well-meant attempt at a non-ugly GUI was completely spoiled by having to interact with the stuff below it). Better that stuff doesn't get released. Really. :)
Gargaj, we already know that 8KHz samples that have been compressed to death by non standard codecs are the future, so why bother *g*
Gargaj, we already know that 8KHz samples that have been compressed to death by non standard codecs are the future, so why bother *g*
kb: Well, I could give it a try.
kb: hey, at least perhaps providing sample support at all is the future, you know, for styles other than ebm.. :) okok, stop!
seriously, we already discussed it and agreed that if we ever did do another 64k we'd probably have to do something a lot more interesting for the music than the current synth. whatever that is i have no idea. good job we dont have anything planned then really. :)
btw, i fully sympathise with kb's vst interface issues. vstgui is garbage. a horrific piece of code that appears like it was written by a student intern. i used mfc for mine, which makes it completey tied to windows as well.
actually, while we are on the subject of synths: help! im looking for a tracker-esque program that's nice to use, can support vsti, and (importantly) lets you send all the midi channels at once to one instrument. i'd like to use renoise, but the last issue is a sticking point. has anyone found a way around it for renoise, or is there something else that works?
(the last time i tried this was in 2004, and i ended up using ztracker and a loopback to a standalone vst host. that setup somewhat sucked.)
seriously, we already discussed it and agreed that if we ever did do another 64k we'd probably have to do something a lot more interesting for the music than the current synth. whatever that is i have no idea. good job we dont have anything planned then really. :)
btw, i fully sympathise with kb's vst interface issues. vstgui is garbage. a horrific piece of code that appears like it was written by a student intern. i used mfc for mine, which makes it completey tied to windows as well.
actually, while we are on the subject of synths: help! im looking for a tracker-esque program that's nice to use, can support vsti, and (importantly) lets you send all the midi channels at once to one instrument. i'd like to use renoise, but the last issue is a sticking point. has anyone found a way around it for renoise, or is there something else that works?
(the last time i tried this was in 2004, and i ended up using ztracker and a loopback to a standalone vst host. that setup somewhat sucked.)
same problem as smash here .. if anyone has any workaround to renoise sending all the midi channels to one instrument, i'd hump his leg.*
*don't take my word on that
*don't take my word on that
smash:
in renoise create an vsti alias instrument to route several channels to one vsti instance.
apart from that you can try madtracker. it also supports routing of midi channels to one vsti instance
in renoise create an vsti alias instrument to route several channels to one vsti instance.
apart from that you can try madtracker. it also supports routing of midi channels to one vsti instance
oh and i also have ugly native win 32 gui code wrapped around my synths, so it seems thats a normal thing ;)
(and yes, vstgui is just plain bullshit)
(and yes, vstgui is just plain bullshit)
There is no problem to send all MIDI channels to the same VSTi in Sony Acid btw.
It doesn't have a "tracker" interface though, which might be a dealbreaker.