Using QuteCsound 0.6.0 in a Windows 7 64-bit Home Premium system, with Csound
5.13, I'm having a look at the VSTi hosting capabilities. I copies the
example for vstinit from the manual.

The notes sent to the VSTi (as it happens, I'm using PianoTeq) play
perfectly, and the edit window opens at the start of the performance ... but
when the score finishes, QuteCsound crashes consistently with a console
message saying, "Message buffer overflow. Messages discarded."

The Run In Terminal option doesn't work -- it reports "Csound Command ERROR:
too many arguments". The flags are -s -otest -b4096 -B16384 -m135.

Is this a known problem? User error? Suggestions welcome.

--Jim Aikin


--
View this message in context: http://csound.1045644.n5.nabble.com/VSTi-Hosting-Windows-QTSC-tp4624833p4624833.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Jim,

Have you tried running it on a command prompt? Also, are other plugins
causing the crash as well? I think Michael also uses PianoTeq on
Windows, so it might be interesting to hear from him if he has the
same problem.

Can you try disabling the extra command line options line in the QCS
preferences to see if that enables running on the terminal (if I
remember correctly there used to be a bug here)?

Cheers,
Andres

On Fri, Jul 22, 2011 at 11:06 PM, Jim Aikin  wrote:
> Using QuteCsound 0.6.0 in a Windows 7 64-bit Home Premium system, with Csound
> 5.13, I'm having a look at the VSTi hosting capabilities. I copies the
> example for vstinit from the manual.
>
> The notes sent to the VSTi (as it happens, I'm using PianoTeq) play
> perfectly, and the edit window opens at the start of the performance ... but
> when the score finishes, QuteCsound crashes consistently with a console
> message saying, "Message buffer overflow. Messages discarded."
>
> The Run In Terminal option doesn't work -- it reports "Csound Command ERROR:
> too many arguments". The flags are -s -otest -b4096 -B16384 -m135.
>
> Is this a known problem? User error? Suggestions welcome.
>
> --Jim Aikin
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/VSTi-Hosting-Windows-QTSC-tp4624833p4624833.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Running it from the Command Prompt works with PianoTeq. With u-he ACE it
works but the edit window is empty. With u-he Zebra 2.5 the edit window is
empty _and_ Csound itself crashes. Native Instruments Massive works properly
when I run Csound from the Command Prompt, or seems to -- bearing in mind
that this is a short test file playing four notes.

The results from within QuteCsound are similar no matter what I do
(although, again, the u-he synths don't show their panels). Shortly after
the performance finishes, QuteCsound crashes.

I don't know what you mean by "the extra command line options line in the
QCS preferences." Under the Run tab, there are no additional command line
flags -- just -b and -B in their own checkboxes, which I would imagine are
necessary. If I comment out the CsOptions in the test file from the manual (
-m3 --displays  -odac), it makes no difference. QTCS still crashes shortly
after the performance ends.

The business with u-he synths not displaying their panels is a bit odd. I'll
contact Urs Heckmann about that. At any rate, it appears there's some kind
of problem in QuteCsound when a .csd finishes running. I'll test further if
you can suggest what to try. (I don't think I have any VSTi's in my Mac
system, so I can't run tests there. All of my VSTi's are in the Windows
machine.)

--JA

--
View this message in context: http://csound.1045644.n5.nabble.com/VSTi-Hosting-Windows-QTSC-tp4624833p4629410.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Jim,

It would seem the vst hostinng opcodes are having trouble with some plugins. They do need a little love from a windows developer...

On the qcs properties under the buffer sizes there should be a text box where you can specify additional flags. This is the box I mean. i'm interested in knowing about the bug when running in the terminal inside qcs.

Cheers,
AndresOn Mon Jul 25 03:45:27 2011 Jim Aikin wrote:
Running it from the Command Prompt works with PianoTeq. With u-he ACE it
works but the edit window is empty. With u-he Zebra 2.5 the edit window is
empty _and_ Csound itself crashes. Native Instruments Massive works properly
when I run Csound from the Command Prompt, or seems to -- bearing in mind
that this is a short test file playing four notes.

The results from within QuteCsound are similar no matter what I do
(although, again, the u-he synths don't show their panels). Shortly after
the performance finishes, QuteCsound crashes.

I don't know what you mean by "the extra command line options line in the
QCS preferences." Under the Run tab, there are no additional command line
flags -- just -b and -B in their own checkboxes, which I would imagine are
necessary. If I comment out the CsOptions in the test file from the manual (
-m3 --displays  -odac), it makes no difference. QTCS still crashes shortly
after the performance ends.

The business with u-he synths not displaying their panels is a bit odd. I'll
contact Urs Heckmann about that. At any rate, it appears there's some kind
of problem in QuteCsound when a .csd finishes running. I'll test further if
you can suggest what to try. (I don't think I have any VSTi's in my Mac
system, so I can't run tests there. All of my VSTi's are in the Windows
machine.)

--JA

--
View this message in context: http://csound.1045644.n5.nabble.com/VSTi-Hosting-Windows-QTSC-tp4624833p4629410.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"