Csound Csound-dev Csound-tekno Search About

csoundQT shortcuts [was Re: [Csnd] csoundapi and csound~]

Date2013-10-02 08:11
Frompeiman khosravi
SubjectcsoundQT shortcuts [was Re: [Csnd] csoundapi and csound~]
Hi Andres,

So far it's been really stable. Interestingly I'm on 10.7.5.

Some of the examples still don't work and I have one issue. The shortcuts with the 'alt' key (to stop performance for instance) seem to also require the 'fn' key. So I have to hold down alt+fn and then press S to stop. Is this normal? 

Thanks
Peiman 




On 1 October 2013 21:36, Andres Cabrera <mantaraya36@gmail.com> wrote:
Hi Peiman,

Good to hear. There were some reentrancy issues with the MIDI modules, which have been solved with the latest Csound6. Maybe the fact that everything was now built using 10.8 made the difference.

Cheers,
Andrés


On Tue, Oct 1, 2013 at 5:50 AM, peiman khosravi <peimankhosravi@gmail.com> wrote:
I've just downloaded the nightly build of qt and it seems to be running fine so far!

P
On 1 October 2013 13:40, Richard Dobson <richarddobson@blueyonder.co.uk> wrote:
It is true that the SDK is under NDA, so that only registered developers can create plugins. Probably only a closed-source wrapper system like Cycling74's sadly discontinued Jitter system would be viable. The SDK for AAX does look somewhat better than the RTAS one ever was (based on the old MacOS ported very crudely to OS X), and while such things will never be simple, I think it does look more attractive to develop for. Not being a Pro Tools user as such, I have no immediate reason to mourn the loss of RTAS!

Pat of the problem with developing PT plugins is that they need a minimum level of support to be included for all the various external hardware control surfaces, including third-party ones.  In a few cases they have provided simulators as part of the SDK (using one computer networked to the development machine), but one way and another it is a rather expensive business, which I guess is why PT plugins are themselves "cheap" at a whole new order of magnitude.

Richard Dobson


On 01/10/2013 12:06, Rory Walsh wrote:
Fair point. Vienna library looks like a nice solution, but not worth
the money if it's for just one application. I thought that you just
might have a license for it there already. It's a pity Avid have
locked all plugins to AAX in the latest version of Protools. I doubt
there is much chance of them providing me with a license which enables
people to develop high end plugins for free. Seems kind of anti-avid.
I also heard that developers of previous VST to RTAS plugins had awful
times dealing with Avid.





Send bugs reports to the Sourceforge bug trackers
csound6:
           https://sourceforge.net/p/csound/tickets/
csound5:
           https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"






Date2013-10-03 20:19
FromAndres Cabrera
SubjectRe: csoundQT shortcuts [was Re: [Csnd] csoundapi and csound~]
Hi Peiman,

That is weird, I haven't seen that... You can always change your shortcuts from the menu option.

Cheers,
Andrés


On Wed, Oct 2, 2013 at 12:11 AM, peiman khosravi <peimankhosravi@gmail.com> wrote:
Hi Andres,

So far it's been really stable. Interestingly I'm on 10.7.5.

Some of the examples still don't work and I have one issue. The shortcuts with the 'alt' key (to stop performance for instance) seem to also require the 'fn' key. So I have to hold down alt+fn and then press S to stop. Is this normal? 

Thanks
Peiman 




On 1 October 2013 21:36, Andres Cabrera <mantaraya36@gmail.com> wrote:
Hi Peiman,

Good to hear. There were some reentrancy issues with the MIDI modules, which have been solved with the latest Csound6. Maybe the fact that everything was now built using 10.8 made the difference.

Cheers,
Andrés


On Tue, Oct 1, 2013 at 5:50 AM, peiman khosravi <peimankhosravi@gmail.com> wrote:
I've just downloaded the nightly build of qt and it seems to be running fine so far!

P
On 1 October 2013 13:40, Richard Dobson <richarddobson@blueyonder.co.uk> wrote:
It is true that the SDK is under NDA, so that only registered developers can create plugins. Probably only a closed-source wrapper system like Cycling74's sadly discontinued Jitter system would be viable. The SDK for AAX does look somewhat better than the RTAS one ever was (based on the old MacOS ported very crudely to OS X), and while such things will never be simple, I think it does look more attractive to develop for. Not being a Pro Tools user as such, I have no immediate reason to mourn the loss of RTAS!

Pat of the problem with developing PT plugins is that they need a minimum level of support to be included for all the various external hardware control surfaces, including third-party ones.  In a few cases they have provided simulators as part of the SDK (using one computer networked to the development machine), but one way and another it is a rather expensive business, which I guess is why PT plugins are themselves "cheap" at a whole new order of magnitude.

Richard Dobson


On 01/10/2013 12:06, Rory Walsh wrote:
Fair point. Vienna library looks like a nice solution, but not worth
the money if it's for just one application. I thought that you just
might have a license for it there already. It's a pity Avid have
locked all plugins to AAX in the latest version of Protools. I doubt
there is much chance of them providing me with a license which enables
people to develop high end plugins for free. Seems kind of anti-avid.
I also heard that developers of previous VST to RTAS plugins had awful
times dealing with Avid.





Send bugs reports to the Sourceforge bug trackers
csound6:
           https://sourceforge.net/p/csound/tickets/
csound5:
           https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"