a killer feature :)

[Cramp]

"atom":2qw7kftp wrote:

If you open Ctrlr as a VST or in any other VST host (Live, Reaper) it will export a VST version. It always exports itself.[/quote:2qw7kftp]
Vst on Mac should be with ".vst" extension right? I didn’t know that Live exports VST on Mac. Logic did export AU with ".component" extension

[atom]

Live does not export anything on MAC it just opens Ctrlr as a VST plugin (the VST is in the .dmg file you download)

[Cramp]

"atom":12sqpgiu wrote:

Live does not export anything on MAC it just opens Ctrlr as a VST plugin (the VST is in the .dmg file you download)[/quote:12sqpgiu]
my bad, missed that. )

[Karl]

Hi,

here is the screenshot with the small "labels" in the "edit window". It’s the same for the midi setup page. By the way, in my case the automation labels are correct.

[atom]

weird can you tell me what os version and language u are using?

[atom]

I have a question about this feature in general, do you think that it’s a good idea to add additional download options in the Device Database for downloading instances of AU/VST/Standalone for each platform, provided by panel authors, and in consequence add an auto-update feature that will check for newer versions of a perticular instance and inform the user of such an event in Ctrlr. This would require for the panel creator to upload each instance (vst/au/standalone mac/win/linux) to the device database

I was also considering automating this, that is adding an option that would automagicly pack the panel into the requested binary and send that to the user, but that would require changing the hosting provider from sf.net to something else. I’d need to be able to run WINE to update the windows binaries on the server side, it’s impossible in the current state.

Or is it maybe best to leave the distribution of instances to the panel creators and let them deal with versions updates etc.

Any thoughts ?

[Cramp]

"atom":e4e0hwt9 wrote:

I have a question about this feature in general, do you think that it’s a good idea to add additional download options in the Device Database for downloading instances of AU/VST/Standalone for each platform, provided by panel authors, and in consequence add an auto-update feature that will check for newer versions of a perticular instance and inform the user of such an event in Ctrlr. This would require for the panel creator to upload each instance (vst/au/standalone mac/win/linux) to the device database

I was also considering automating this, that is adding an option that would automagicly pack the panel into the requested binary and send that to the user, but that would require changing the hosting provider from sf.net to something else. I’d need to be able to run WINE to update the windows binaries on the server side, it’s impossible in the current state.

Or is it maybe best to leave the distribution of instances to the panel creators and let them deal with versions updates etc.

Any thoughts ?[/quote:e4e0hwt9]

As for me I could only VST for DAW on Windows, MAC AU and VST.. but not linux.
I would prefer to upload instances by myself. It doesn’t take to much time. Nice feature by the way

[snk]

"atom":zss1yzam wrote:

I have a question about this feature in general, do you think that it’s a good idea to add additional download options in the Device Database for downloading instances of AU/VST/Standalone for each platform, provided by panel authors, and in consequence add an auto-update feature that will check for newer versions of a perticular instance and inform the user of such an event in Ctrlr. This would require for the panel creator to upload each instance (vst/au/standalone mac/win/linux) to the device database

I was also considering automating this, that is adding an option that would automagicly pack the panel into the requested binary and send that to the user, but that would require changing the hosting provider from sf.net to something else. I’d need to be able to run WINE to update the windows binaries on the server side, it’s impossible in the current state.

Or is it maybe best to leave the distribution of instances to the panel creators and let them deal with versions updates etc.[/quote:zss1yzam]
I think that a single "central point" where to download all panels, formats, updates is better.
Else, it might be too easy to get lost and confused after a "panel hunt" on dozens of forum…
If there could have an auto-update feature that would be icing on the cake indeed ” title=”Wink” />
Thanksagain Roman for all your efforts !

[Karl]

Hi,

regarding the small labels – I’m running Logic Express 9 on an Intel iMac OS X 10.6.4

I’m not a programmer, so don’t ask me about the "language" I’m using ” title=”Wink” />

Thanks for looking into this issue

Bye.

[dasfaker]

He is asking the idiom of your OS ” title=”Wink” />

[dasfaker]

"atom":3nrkyzdi wrote:

I have a question about this feature in general, do you think that it’s a good idea to add additional download options in the Device Database for downloading instances of AU/VST/Standalone for each platform, provided by panel authors, and in consequence add an auto-update feature that will check for newer versions of a perticular instance and inform the user of such an event in Ctrlr. This would require for the panel creator to upload each instance (vst/au/standalone mac/win/linux) to the device database[/quote:3nrkyzdi]

I agree with snk

[atom]

I’m asking cause not everyone will be able or want to use Linux or MAC/Win to export their instances for other to use. And in case of updates they’ll have to go back to those platforms just to update their panels.

[atom]

"Karl":21qlso3w wrote:

Hi,

here is the screenshot with the small "labels" in the "edit window". It’s the same for the midi setup page. By the way, in my case the automation labels are correct.[/quote:21qlso3w]

This was a bug in JUCE, today the author posted a fix for that, and i did a new nightly build that should contain a fix for the problem, let me know if it’s still there or is that fixed.

[atom]

"Karl":2stbrtay wrote:

Hi,

here is the screenshot with the small "labels" in the "edit window". It’s the same for the midi setup page. By the way, in my case the automation labels are correct.[/quote:2stbrtay]

This was a bug in JUCE, today the author posted a fix for that, and i did a new nightly build that should contain a fix for the problem, let me know if it’s still there or is that fixed.

[Syntholabo]

Hey, I’m getting started with Ctrlr on Logic9.

When I deleted the cache file you mentioned above, CTRLR audio unit still was not there, and other plugins failed to load. So I copied the cache file back, and I’m back to where I started.

What am I misunderstanding about loading CTRLR as audio unit plugin on Logic Software Instrument track?

Thanks
M

[Author]

Posts