Csound Csound-dev Csound-tekno Search About

[Cs-dev] libo, osc opcodes...

Date2008-02-06 12:38
FromRory Walsh
Subject[Cs-dev] libo, osc opcodes...
It has come to my attention that there is a problem running the osc 
opcodes from within Lettuce. If the osc instrument is run, stopped, and 
run again windows reports the following:

Access violation at address 0117654D in mondule 'liblo.dll'. Read of 
address 0000000C.

As far as I can tell it does run correctly the first time. Could it be 
something to do with the way I end a performance in Lettuce using the 
API? I am calling csoundCleanup() csoundReset() at the end of the 
performance, there is a new compile on every run. The message output 
from Csound is the same in Lettuce as it is from the command yet 
something is prevent the liblo.dll library from being freed at the end 
of the performance. Any ideas?

Rory.




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2008-02-06 13:52
FromVictor Lazzarini
SubjectRe: [Cs-dev] libo, osc opcodes...
Try csoundDestroy() and then create a new instance.


At 12:38 06/02/2008, you wrote:
>It has come to my attention that there is a problem running the osc
>opcodes from within Lettuce. If the osc instrument is run, stopped, and
>run again windows reports the following:
>
>Access violation at address 0117654D in mondule 'liblo.dll'. Read of
>address 0000000C.
>
>As far as I can tell it does run correctly the first time. Could it be
>something to do with the way I end a performance in Lettuce using the
>API? I am calling csoundCleanup() csoundReset() at the end of the
>performance, there is a new compile on every run. The message output
>from Csound is the same in Lettuce as it is from the command yet
>something is prevent the liblo.dll library from being freed at the end
>of the performance. Any ideas?
>
>Rory.
>
>
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2008.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2008-02-06 18:39
FromRory Walsh
SubjectRe: [Cs-dev] libo, osc opcodes...
Thanks Victor, unfortunately that didn't do the trick either. The real 
problem is that my code is a complete mess which makes it really 
difficult to debug things. For now at least osc instruments will have to 
be run from the command line I'm afraid. Cheers,

Rory.


Victor Lazzarini wrote:
> Try csoundDestroy() and then create a new instance.
> 
> 
> At 12:38 06/02/2008, you wrote:
>> It has come to my attention that there is a problem running the osc
>> opcodes from within Lettuce. If the osc instrument is run, stopped, and
>> run again windows reports the following:
>>
>> Access violation at address 0117654D in mondule 'liblo.dll'. Read of
>> address 0000000C.
>>
>> As far as I can tell it does run correctly the first time. Could it be
>> something to do with the way I end a performance in Lettuce using the
>> API? I am calling csoundCleanup() csoundReset() at the end of the
>> performance, there is a new compile on every run. The message output
>>from Csound is the same in Lettuce as it is from the command yet
>> something is prevent the liblo.dll library from being freed at the end
>> of the performance. Any ideas?
>>
>> Rory.
>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net