I think I have solved this problem. Instead of linking portaudio and
fluidsynth with the DLL version of the Microsoft runtime library, I linked
them with the static version of the library. Then msvcr80.dll does not need
to be distributed with Csound. Simple.

The cost of this solution is that the runtime library code is duplicated in
both portaudio and fluidsynth, which makes the Csound installation (and
installer) about 2 megabytes bigger. But since the installers are already 
over 20 megabytes each, I think that is a reasonable price to pay.

I have uploaded patched installers, and removed the earlier installers.

Please let me know if this works for you.

I have not addressed the Python issues at this time, but I am thinking about 
them.

Regards,
Mike

----- Original Message ----- 
From: "Art Hunkins" 
To: "Michael Gogins" 
Cc: 
Sent: Friday, November 09, 2007 5:35 PM
Subject: Re: [Cs-dev] OSC on Windows float installers


> Here's an update from my afternoon tests of 5.07 on my WinXP laptop.
>
> For *completely unknown* reasons, OSC has started working today. It's like
> the problem never existed: no more WARNINGs or unknown opcode messages at
> all. A real mystery.
>
> My setup is this: normal floats 5.07 installer, with csnd.dll and
> scoregen.dll removed from /plugins, and msvcr80.dll dropped into /bin.
> (Csnd.dll and scoregen.dll were removed in order to eliminate the WARNING
> messages.)
>
> I've also managed to get sound, using Trappedrt.csd - *but only by
> selecting
> MME drivers* - in csoundGUI. (I also get sound from the command line
> specifying a CsOption = -+rtaudio=mme.) No sound otherwise, whether from
> PortAudio, pa_cb or pa_bl, the other options that csoundGUI offers.
>
> Furthermore, MME gives sound whether or not msvcr80.dll is present in
> /bin.
>
> There you have it. What can you make of all this?
>
> Art Hunkins
>
> ----- Original Message ----- 
> From: "Michael Gogins" 
> To: "Art Hunkins" ; "Developer discussions"
> 
> Sent: Thursday, November 08, 2007 2:57 PM
> Subject: Re: [Cs-dev] OSC on Windows float installers
>
>
>> My test was just rendering "Trapped in Convert" from csound5gui using
> rtpa.
>>
>> Regards,
>> Mike
>>
>> -----Original Message-----
>> >From: Art Hunkins 
>> >Sent: Nov 9, 2007 1:52 AM
>> >To: Developer discussions 
>> >Subject: Re: [Cs-dev] OSC on Windows float installers
>> >
>> >Anthony,
>> >
>> >I am on both WinME and WinXP. My tests with 5.07 are done on my WinXP
>> >laptop; so, no, I don't think that has anything to do with it.
>> >
>> >With regard to 5.07's rtpa.dll issues, I have been testing with one of
>> >my
>> >.csd's known to work with earlier versions (both in WinME and XP).
> However,
>> >I'm doing further testing this afternoon on XP, at Oeyvind's suggestion,
>> >with a "simplest" .csd that doesn't use sensekey and require realtime
> input.
>> >
>> >I wonder whether Michael's successful rtpa.dll test involved realtime
> sonic
>> >output (I assume so), and some realtime input (via sensekey or
> otherwise)?
>> >At any rate, I'll report back soon.
>> >
>> >Art Hunkins
>> >
>> >----- Original Message ----- 
>> >From: "Anthony Kozar" 
>> >To: "Csound Developer list" 
>> >Sent: Thursday, November 08, 2007 1:07 PM
>> >Subject: Re: [Cs-dev] OSC on Windows float installers
>> >
>> >
>> >> Art, you are on Windows ME, correct?  Any chance this has something to
> do
>> >> with it?
>> >>
>> >> Also, regarding putting up beta test releases:  one thing that I
>> >> really
>> >> dislike about the Sourceforge file release system is that when a new
>> >release
>> >> is added to a package, it obscures all previous releases by collapsing
>> >those
>> >> parts of the page.  So, if (for example) you add a Windows-only
>> >> update,
>> >then
>> >> the most recent versions for all other platforms are "hidden".
>> >> Putting
>> >> betas in a different file release package would be one solution.
>> >>
>> >> The other thing to remember with Sourceforge is that we have to
>> >> provide
>> >> source code packages too everytime that we put up a new beta or
>> >> bug-fix
>> >> release (or include sources in the package).
>> >>
>> >> I used to test my releases on a "fresh" computer before uploading them
> to
>> >> make sure that they installed and ran as expected.  As developers, we
>> >often
>> >> install lots of dependencies and forget that we had to do so.  I just
>> >don't
>> >> usually have the time to do this anymore and I doubt that all of us
> have
>> >> spare machines to try release packages on ...
>> >>
>> >> Anthony
>> >>
>> >> Art Hunkins wrote on 11/8/07 12:25 PM:
>> >>
>> >> > Steven and Michael:
>> >> >
>> >> > Dropping msvcr80.dll into the csound\bin directory does not work for
> me.
>> >> >
>> >> > I still get WARNING: could not open fluidOpcodes.dll and rtpa.dll
>> >messages;
>> >> > and later, error: unknown rtaudio module: 'pa'.
>> >>
>> >>
>>
>>> -------------------------------------------------------------------------
>> >> This SF.net email is sponsored by: Splunk Inc.
>> >> Still grepping through log files to find problems?  Stop.
>> >> Now Search log events and configuration files using AJAX and a
>> >> browser.
>> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> >> _______________________________________________
>> >> Csound-devel mailing list
>> >> Csound-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>> >
>> >-------------------------------------------------------------------------
>> >This SF.net email is sponsored by: Splunk Inc.
>> >Still grepping through log files to find problems?  Stop.
>> >Now Search log events and configuration files using AJAX and a browser.
>> >Download your FREE copy of Splunk now >> http://get.splunk.com/
>> >_______________________________________________
>> >Csound-devel mailing list
>> >Csound-devel@lists.sourceforge.net
>> >https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

so I don't need service pack 2 then?

it would be great if i didn't. My only option looks like having to send away
for that on CD...

I was tied up most of the weekend, so I haven't been able to follow all the
twists & turns of this thread as I hoped (in fact the list seems to be
getting busier, which is making "saturation coverage" of all topics more
difficult....

My growing python dependance means less & less need for csound~, so if these
patched 5.07 installers are relatively pain / bug free now I might take the
plunge & try & upgrade....

apologies again for being the most enthusiastic yet most ignorant of csound
users.

(& of course the irony is i don't even really need OSC at the moment. it
just issues like this in general make me nervous..... & observing the
conniptions surrounding 5.07 has been a mildly nerve - rattling
experience...)

T.


Michael Gogins wrote:
> 
> I think I have solved this problem. Instead of linking portaudio and
> fluidsynth with the DLL version of the Microsoft runtime library, I linked
> them with the static version of the library. Then msvcr80.dll does not
> need
> to be distributed with Csound. Simple.
> 
> The cost of this solution is that the runtime library code is duplicated
> in
> both portaudio and fluidsynth, which makes the Csound installation (and
> installer) about 2 megabytes bigger. But since the installers are already 
> over 20 megabytes each, I think that is a reasonable price to pay.
> 
> I have uploaded patched installers, and removed the earlier installers.
> 
> Please let me know if this works for you.
> 
> I have not addressed the Python issues at this time, but I am thinking
> about 
> them.
> 
> Regards,
> Mike
> 
> 

-- 
View this message in context: http://www.nabble.com/OSC-on-Windows-float-installers-tf4762094.html#a13697743
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net