Home › Forums › General › News and releases › Drop Standalone support?
- This topic has 6 replies, 6 voices, and was last updated 13 years, 8 months ago by SepticUnderground.
-
AuthorPosts
-
June 17, 2010 at 10:15 pm #132
I was thinking the standalone version of all Ctrlrs is a pain, my thoughts are
– instead of each Ctrlr having a standalone build, create one plugin host that will host multiple Ctrlrs (or other VST/AU plugins) in one instance, thus giving the ability to share MIDI ports (one in one out for all Ctrlr in such a host)
– create a new standalone version withouth the Audio preferences with only MIDI preferences in the Ctrlr itself
why now ? there are some changes in JUCE library and things got a bit complicated, i guess i can fix the old engine but since i need to change the code anyway to make it all work i was wondering what would be more useful for people actualy using this software.
June 21, 2010 at 1:37 am #1604yeah, if people need stadalone they can use a vst converter.
i only use the vst versions. less time spent on making a vst
stadalon means more time for new VST controllers!June 30, 2010 at 8:18 am #1605+1
I am using only the VST versions.July 9, 2010 at 1:26 pm #1606To the contrary I only use the stand alones .
However this –
" create a new standalone version withouth the Audio preferences with only MIDI preferences in the Ctrlr itself "
should work great on Mac as Audio Midi setup alows for external hardware to pass audio through most usb/1394 audio i/o’s with out the need for a host application/ daw running .And to be honest the audio prefrances in the standalones is were I have had the most issues with in sevral ctrlr apps .
So I vote cut the audio pref , but please keep the stand alones …infact I could see use for them even ported to iOS too ” title=”Wink” />
July 13, 2010 at 9:18 am #1607I use also only the vst versions, my goal is always using ctrlr in real tracks, not playing around with the standalone. Imo standalone versions are a waste of energy as there are vst to standalone host converters.
July 17, 2010 at 6:16 pm #1608"TonE":kerukjrn wrote:I use also only the vst versions, my goal is always using ctrlr in real tracks, not playing around with the standalone. Imo standalone versions are a waste of energy as there are vst to standalone host converters.[/quote:kerukjrn]
Says Who ?
I use stand alones to do sound design for patches and only record my synths as audio in real time to keep my sound design and recording split which makes recording time much more efficient …not playing around with knobs and or mouse !As he said he can just drop the audio interface section to speed up process and that’s just fine for me I can do all of that through audio midi setup anyway .
July 27, 2010 at 9:30 am #1609"DBM":6cgtf0uq wrote:"TonE":6cgtf0uq wrote:I use also only the vst versions, my goal is always using ctrlr in real tracks, not playing around with the standalone. Imo standalone versions are a waste of energy as there are vst to standalone host converters.[/quote:6cgtf0uq]
Says Who ?
I use stand alones to do sound design for patches and only record my synths as audio in real time to keep my sound design and recording split which makes recording time much more efficient …not playing around with knobs and or mouse !As he said he can just drop the audio interface section to speed up process and that’s just fine for me I can do all of that through audio midi setup anyway .[/quote:6cgtf0uq]
I totally agree with DBM.
I am using Logic and audiounits usage is a bit clumsy for remote controlling only…I prefer the use of standalone editors aswell on OSX, it works perfectly. Audiosupport can be dropped that is routed via Logic.
-
AuthorPosts
- The forum ‘News and releases’ is closed to new topics and replies.