[Csnd] New Windows installer release candidate
Date | 2017-11-10 21:59 |
From | Michael Gogins |
Subject | [Csnd] New Windows installer release candidate |
AppVeyor is now building Windows installers for the 6.10.0 release candidate. Please test Csound and CsoundQt from the installer here (or later) and report issues: https://ci.appveyor.com/api/buildjobs/kptdhpcnq040eng0/artifacts/msvc%2FSetup_Csound_x64_6.10.0rc-vst.exe Regards, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |
Date | 2017-11-11 00:18 |
From | Rory Walsh |
Subject | Re: [Csnd-dev] New Windows installer release candidate |
Thanks Mike, I'll start building with this one straight away. On 10 November 2017 at 21:59, Michael Gogins <michael.gogins@gmail.com> wrote: AppVeyor is now building Windows installers for the 6.10.0 release |
Date | 2017-11-11 08:35 |
From | Søren Jakobsen |
Subject | Re: [Csnd] New Windows installer release candidate |
Thanks a lot Mike! A little prayer - a 32 bit version would also be useful, as many VSTs don't come in 64 bit version. Best regards, Søren On 11/10/17, Michael Gogins |
Date | 2017-11-11 10:43 |
From | JTG III |
Subject | Re: [Csnd] New Windows installer release candidate |
i realize that this is a bit late to be asking this, but I was wondering recently about the csound6~ object for Pure Data and windows, because on the mac I sometimes use, it seems to work fine with the 32bit version of PD, which I use almost exclusively as some libraries aren't so compatible with the 64bit release (like Gem, which isn't able to play back video, etc.) Is there anything specific to windows that prevents csound and pd getting along? On Nov 11, 2017 3:35 AM, "Søren Jakobsen" <sorenkj@gmail.com> wrote: Thanks a lot Mike! A little prayer - a 32 bit version would also be |
Date | 2017-11-11 11:46 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
You could try a 32 to 64-bit bridging application like JBridge (https://jstuff.wordpress.com/jbridge) or 32 Lives by Soundradix (www.soundradix.com) which should allow you to use your 32-bit plugins in Csound. But I have not tried it. People say that not all plugins work well in these application. Let us know if you try it. Regards, Mike On Nov 11, 2017 03:35, "Søren Jakobsen" <sorenkj@gmail.com> wrote: Thanks a lot Mike! A little prayer - a 32 bit version would also be |
Date | 2017-11-11 11:51 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
Please enter an issue in GitHub to configure the AppVeyor build to include csound6~. Regards, Mike On Nov 11, 2017 05:43, "JTG III" <jordanthomasgibbonsiii@gmail.com> wrote:
|
Date | 2017-11-14 10:05 |
From | Tarmo Johannes |
Subject | Re: [Csnd] New Windows installer release candidate |
Hi, on Windows 10 I downloaded the installer, moved away old Csoundx64 folder to do clean test. Csound from command line Works, but there was no CsoundQt included in the installer. I downloaded then the csound.zip file, copied CsoundQt-d-html-cs6.exe to C:\Program Files\Csound6_x64\bin CsoundQt opens fine but when I hit Run on some file, it crashes, message from automatically opened Visual Studio debugger: ---- Unhandled exception at 0x00007FFA9754B618 (ntdll.dll) in CsoundQt-d-html-cs6.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF. If there is a handler for this exception, the program may be safely continued. ---- I cannot copy the exact Stack tab but the processes in stack are: ntdll.dll csound64.dll CsoundQt-d-html-cs6.exe Can it be something to do with libsndfile or starting CsoundPerformanceThread? Using csound API by itself seems to work since opening Configuration, correct devices are listed and Csound API is used to fetch those. When I build CsoundQt myself against the libs of the 6.10.0 Appveyor build, I get the same result. Info from QtCreator debug mode: Stack: 1 RtlWakeConditionVariable ntdll 0x7ffa9754b618 2 csoundCondSignal csound64 0x7ffa6f6cce44 3 CsoundPerformanceThread::Perform csPerfThread.cpp 452 0x7ff751f8f890 4 CsPerfThread_PerformScore::Perform csPerfThread.cpp 482 0x7ff751f91eb6 5 csoundPerformanceThread_ csPerfThread.cpp 498 0x7ff751f905aa 6 o__realloc_base ucrtbase 0x7ffa9412cde0 7 BaseThreadInitThunk KERNEL32 0x7ffa955c8364 8 RtlUserThreadStart ntdll 0x7ffa97547091 Debugging stopped at csPerfThread.cpp 452 Hope this info is useful. greetings, tarmo 2017-11-11 13:51 GMT+02:00 Michael Gogins <michael.gogins@gmail.com>:
|
Date | 2017-11-14 21:18 |
From | Oeyvind Brandtsegg |
Subject | Re: [Csnd] New Windows installer release candidate |
Sorry for the late reply. Tested this now, and installation works fine. Command line csound works well. Also tested with Cabbage, exporting a few of the more recent plugins from the crossdaptive project. All seems to work ok. All best Oeyvind 2017-11-10 22:59 GMT+01:00 Michael Gogins <michael.gogins@gmail.com>: AppVeyor is now building Windows installers for the 6.10.0 release Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://crossadaptive.hf.ntnu.no http://gdsp.hf.ntnu.no/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp |
Date | 2017-11-14 21:39 |
From | Tarmo Johannes |
Subject | Re: [Csnd] New Windows installer release candidate |
Hi, Can you try CsoundQt from bin folder and run some examples? This crashes for me - have tried on two different Windows 10 computers. Tarmo 14.11.2017 23:18 kirjutas kuupäeval "Oeyvind Brandtsegg" <oyvind.brandtsegg@ntnu.no>:
|
Date | 2017-11-15 00:15 |
From | Nathan Holmes |
Subject | Re: [Csnd] New Windows installer release candidate |
The installer is not giving me a CsoundQt executable either. Where should I be getting that from to test the new version? In the meantime, I tried it with both the 0.9.4.1 CsoundQt executable and the 0.9.5-rc2 version from another thread, with the following results: trying to run CSDs with the multicore option enables gives me a "Failed to allocate barrier" error. Yet running CSDs with the multicore option disabled crashes CsoundQt instead.Csound.exe itself seems to be working alright, seeing that it can be run in terminal with no crashes, and it produces sound as expected. Unfortunately, it still doesn't work with multicore enabled (giving me the "Failed to allocate barrier" error again, whereas the previous version of Csound did not give me this error). On Tue, Nov 14, 2017 at 1:39 PM, Tarmo Johannes <trmjhnns@gmail.com> wrote:
|
Date | 2017-11-15 22:50 |
From | Steven Yi |
Subject | Re: [Csnd] New Windows installer release candidate |
Hi Nathan, Thanks for reporting this. I suspect the muilticore issue is a problem that was introduced when we first started to port the code base to no longer use pthreads with Visual Studio. I'm getting a direct crash with my local VS build here using trapped.csd as a test. I'll take a look and see if I can sort it out and will report back any changes here. steven On Tue, Nov 14, 2017 at 7:15 PM, Nathan Holmes |
Date | 2017-11-16 06:39 |
From | Oeyvind Brandtsegg |
Subject | Re: [Csnd] New Windows installer release candidate |
Hello Tarmo, Sorry, I can't seem to find CsoundQt in the bin folder or elsewhere. There is however some 25 other files with names starting on qt, and 3 other folders also with Qt* names, so it is perhaps partially there(?) 2017-11-14 22:39 GMT+01:00 Tarmo Johannes <trmjhnns@gmail.com>:
Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://crossadaptive.hf.ntnu.no http://gdsp.hf.ntnu.no/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp |
Date | 2017-11-16 07:36 |
From | Tarmo Johannes |
Subject | Re: [Csnd] New Windows installer release candidate |
I think, Michael fixed it, when I downloaded the installer from newest available build at appveyor , I think yesterday daytime, CsoundQt is there. Another option (that I tried, too) is to download the Csound. zip file, extract CsoundQt from there and copy into Csound installation bin folder. Tarmo 16.11.2017 8:39 kirjutas kuupäeval "Oeyvind Brandtsegg" <oyvind.brandtsegg@ntnu.no>:
|
Date | 2017-11-16 08:17 |
From | Oeyvind Brandtsegg |
Subject | Re: [Csnd] New Windows installer release candidate |
Ok. I was not aware that there was updated versions of the installer, as I only saw the first link posted by Michael on Nov 10th. I would perhaps make sense to allow for the known issues to be fixed and then invite to another round of testing? 2017-11-16 8:36 GMT+01:00 Tarmo Johannes <trmjhnns@gmail.com>:
Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://crossadaptive.hf.ntnu.no http://gdsp.hf.ntnu.no/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp |
Date | 2017-11-16 14:10 |
From | Rory Walsh |
Subject | Re: [Csnd] New Windows installer release candidate |
One thing I notice about this version is that I have to Ctrl+C twice from the command line to stop Csound. Is anyone else seeing this? It's not a big deal, but I guess it would be nice to know why. While Cabbage runs fine, it causes a crash on exit, VS points me towards Csound. I assume this version is a release build rather than a debug build (although I didn't check). I wonder if it would be good to change to debug builds for testing so we can try to dig a little deeper into any issues we find? On 16 November 2017 at 08:17, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote:
|
Date | 2017-11-16 19:33 |
From | Rory Walsh |
Subject | Re: [Csnd] New Windows installer release candidate |
CsoundQT crashes as soon as I hit run with the latest installer. My crash is taking place whenever ~Csound() is called. This was working fine in the previous release. On 16 November 2017 at 14:10, Rory Walsh <rorywalsh@ear.ie> wrote:
|
Date | 2017-11-16 19:54 |
From | Tarmo Johannes |
Subject | Re: [Csnd] New Windows installer release candidate |
Yes, That's what I have been trying to say for weeks - in some reason Appveyor build does not work with CsoundQt, in my case crash happens in in CsoundPerformanceThread (when you run a csd). Also older CsoundQt versions crash the same way, also when I build CsoundQt myself using the libraries.2017-11-16 21:33 GMT+02:00 Rory Walsh <rorywalsh@ear.ie>:
|
Date | 2017-11-16 20:15 |
From | Rory Walsh |
Subject | Re: [Csnd] New Windows installer release candidate |
Thanks Tarmo. I'm trying to build a debug version of Csound for Visual Studio now so I can dig a little deeper, but I can't get past the generate project bat :( I'm just doing a completely fresh clone of Csound. Hopefully this will work. For what's it is worth, I don't use the CsoundPerformanceThread class at all. On 16 November 2017 at 19:54, Tarmo Johannes <trmjhnns@gmail.com> wrote:
|
Date | 2017-11-16 20:20 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
I will debug this when I can. Maybe tonight, maybe in a few days. Best, Mike On Nov 16, 2017 2:55 PM, "Tarmo Johannes" <trmjhnns@gmail.com> wrote:
|
Date | 2017-11-16 20:43 |
From | Rory Walsh |
Subject | Re: [Csnd] New Windows installer release candidate |
Thanks Mike. That would be great. In the meantime I'll see if I can manage to get Csound building on my windows machine. On 16 November 2017 at 20:20, Michael Gogins <michael.gogins@gmail.com> wrote:
|
Date | 2017-11-17 19:43 |
From | Rory Walsh |
Subject | Re: [Csnd] New Windows installer release candidate |
It looks like the crash on exit might have something to do with vst4cs.dll? Visual Studio points me there at any rate. Removing it the from the plugin folder seems to resolve the issue for me. On 16 November 2017 at 20:43, Rory Walsh <rorywalsh@ear.ie> wrote:
|
Date | 2017-11-17 20:28 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
Thanks for the information, I will debug it when I get a chance. That's probably very helpful. Regards, Mike On Nov 17, 2017 14:44, "Rory Walsh" <rorywalsh@ear.ie> wrote:
|
Date | 2017-11-17 20:53 |
From | Rory Walsh |
Subject | Re: [Csnd] New Windows installer release candidate |
I have to say, apart from that one little thing, it runs very well for me. I was telling Steven earlier how happy I am to step through Csound code with the Visual Studio debugger! We've waited a long time for this privilege! Hats off to all involved once again. On 17 November 2017 at 20:28, Michael Gogins <michael.gogins@gmail.com> wrote:
|
Date | 2017-11-18 00:30 |
From | Steven Yi |
Subject | Re: [Csnd] New Windows installer release candidate |
I put in a few hours of Windows debugging and I think I've fixed some things. I've done some simple tests running Tarmo's CsoundQt 0.9.5 build, Blue, and live coding with Csound UDP server and it all ran here for me. I tried this with my local Visual Studio build as well as with the Appveyor build: https://ci.appveyor.com/api/buildjobs/nlyr0fywd2lk9s6y/artifacts/msvc%2FSetup_Csound_x64_6.10.0rc-vst.exe The AppVeyor build does not have CsoundQT included, though it appears to package all of the QT libraries. For multicore, I managed to get it to the point where it doesn't crash but now it just hangs. (Devs: I think it has to do with the ATOMIC_CAS code, thinking it should be using different InterlockedCompareExchange function for pointers rather than longs...). I'll announce here when I get further with that. Otherwise, for those testing on Windows, please do use try a new round of testing with the version above and report any issues. Thanks! steven On Fri, Nov 17, 2017 at 3:53 PM, Rory Walsh |
Date | 2017-11-18 19:10 |
From | Steven Yi |
Subject | Re: [Csnd] New Windows installer release candidate |
Update: I found the fix for ATOMIC_CAS on Windows and multicore Csound is now working here (was able to render trapped to disk using -j2). AppVeyor didn't seem to pick up the commit so I manually triggered one just now: https://ci.appveyor.com/project/csound/csound/build/1.0.821 Artifacts will post once that build completes. (For devs, I've also pushed the latest to coverity so we'll get a report on that soon) On Fri, Nov 17, 2017 at 7:30 PM, Steven Yi |
Date | 2017-11-18 20:46 |
From | Nathan Holmes |
Subject | Re: [Csnd] New Windows installer release candidate |
Hi Steven, With the latest build, that does fix the crashing issue I had about 4 days ago, but unfortunately I'm still getting a "Failed to allocate barrier" message when I use the multicore flags, on both Windows 7 and Windows 10 (both 64 bit).I also realized there's a bit more to the message: it's preceded by "csoundCreateBarrier() is not implemented on this platform" (if that helps at all). On Sat, Nov 18, 2017 at 11:10 AM, Steven Yi <stevenyi@gmail.com> wrote: Update: I found the fix for ATOMIC_CAS on Windows and multicore Csound |
Date | 2017-11-18 21:10 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
csoundCreateBarrer is only available from Windows 8 on. If you are on an earlier version of Windows, you will not be able to run the MSVC build of Csound. Yes, the CsoundVST DLL should now be included in the AppVeyor build and in local builds based on the AppVeyor build. Last time I tested, it worked for me in Reaper. Regards, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Nov 18, 2017 at 12:46 PM, Nathan Holmes |
Date | 2017-11-18 21:17 |
From | Steven Yi |
Subject | Re: [Csnd] New Windows installer release candidate |
Hi Michael, Nathan tested on Win10 so that's not quite the issue. What I see is that in your commit: https://github.com/csound/csound/commit/878d44500d369d54591ed8142178ee29e5707a74 you added: PUBLIC void *csoundCreateBarrier(unsigned int max) { #if defined(_USING_V110_SDK71_) notImplementedWarning_("csoundCreateBarrier"); return 0; #else SYNCHRONIZATION_BARRIER *barrier = (SYNCHRONIZATION_BARRIER*)malloc(sizeof(SYNCHRONIZATION_BARRIER)); if (barrier != NULL) InitializeSynchronizationBarrier(barrier, max, -1); return (void*) barrier; #endif } PUBLIC int csoundDestroyBarrier(void *barrier) { #if defined(_USING_V110_SDK71_) notImplementedWarning_("csoundDestroyBarrier"); return 0; #else DeleteSynchronizationBarrier(barrier); return 0; #endif } PUBLIC int csoundWaitBarrier(void *barrier) { #if defined(_USING_V110_SDK71_) notImplementedWarning_("csoundWaitBarrier"); return 0; #else EnterSynchronizationBarrier(barrier, 0); return 0; #endif } Which is a compile-time thing. The commit message doesn't explain anything and I don't know the rationale behind this change: could you explain? My guess is that my local VS2017 build uses through the original paths but the AppVeyor build (using VS2015) goes through the _USING_V110_SDK71_ paths. Can those #ifdefs be removed and the original code restored, or is something else necessary? On Sat, Nov 18, 2017 at 4:10 PM, Michael Gogins |
Date | 2017-11-18 21:18 |
From | Steven Yi |
Subject | Re: [Csnd] New Windows installer release candidate |
Side note: This release: https://ci.appveyor.com/api/buildjobs/kk8d47adayyya153/artifacts/msvc%2FSetup_Csound_x64_6.10.0rc-vst.exe should have CsoundQt now. On Sat, Nov 18, 2017 at 4:17 PM, Steven Yi |
Date | 2017-11-18 21:24 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
Go to the AppVeyor page for Csound here: "https://ci.appveyor.com/project/csound/csound". That is the latest build. If the latest build did not complete, click on the "History" tab and click on the latest build that did complete. Click on the "Artifacts" button (the Windows installer is one of the artifacts), e.g. for the latest build that will be: https://ci.appveyor.com/project/csound/csound/build/artifacts. Download the Windows Csound installer by clicking on the link named "msvc\Setup_Csound_x64_6.10.0rc-vst.exe". It's big. Run the installer. You must be on at least Windows 8 64 bits. CsoundQt should be something like "C:\Program Files\Csound_x64\bin\soundQt-d-cs6.exe". Run this, and if it works, run one of the simple examples such as Examples/Music/Kung-Xanadu. You might have to fiddle with the Configuration settings for plugins and audio output to hear anything. Regards, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Tue, Nov 14, 2017 at 7:15 PM, Nathan Holmes |
Date | 2017-11-18 21:27 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
I just built Csound commit 076f5a3a02a0387778d6cdee273bba36c270c193 and CsoundQt commit 00387fc41521a32b3fba746689dadab62125b994 locally on Windows 8 with MSVS 2015. CsoundQt worked fine for me. No crashes, neither after running, nor after stopping running, nor after quitting CsoundQt. Best, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Nov 18, 2017 at 1:18 PM, Steven Yi |
Date | 2017-11-18 21:37 |
From | Steven Yi |
Subject | Re: [Csnd] New Windows installer release candidate |
Did you run -j2 (multicore) with any file? I suspect your build will report the same problems that Nathan reported, but would like verification. On Sat, Nov 18, 2017 at 4:27 PM, Michael Gogins |
Date | 2017-11-18 21:40 |
From | Rory Walsh |
Subject | Re: [Csnd] New Windows installer release candidate |
Hi Steven, that latest release you posted runs fine for me, CsoundQT too, great work! Note I didn't install the vst stuff, and CsoundQT-html still hangs on startup. On 18 November 2017 at 21:37, Steven Yi <stevenyi@gmail.com> wrote: Did you run -j2 (multicore) with any file? I suspect your build will |
Date | 2017-11-18 21:44 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
I just tried this and got the following error: C:\Program Files\Csound_x64\bin>csound ..\examples\xanadu.csd -odac -j2 0dBFS level = 32768.0 --Csound version 6.10 (double samples) Nov 18 2017 [commit: 6ea7e663e1f99819b8e661c0f7c58a0dfee9dff0] libsndfile-1.0.29pre1 UnifiedCSD: ..\examples\xanadu.csd STARTING FILE Creating options Creating orchestra closing tag Creating score rtaudio: PortAudio module enabled ... using callback interface Elapsed time at end of orchestra compile: real: 0.004s, CPU: 0.005s sorting score ... ... done Elapsed time at end of score sort: real: 0.006s, CPU: 0.006s csoundCreateBarrier() is not implemented on this platform. Failed to allocate barrier end of score. overall amps: 0.0 0.0 1 errors in performance Elapsed time at end of performance: real: 0.007s, CPU: 0.007s C:\Program Files\Csound_x64\bin> This happens with my local build as well. I believe it used to work, but I'm not sure. Best, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Nov 18, 2017 at 1:37 PM, Steven Yi |
Date | 2017-11-18 21:48 |
From | Rory Walsh |
Subject | Re: [Csnd] New Windows installer release candidate |
I just tried this too. Same issue. I'm on Win10. On 18 November 2017 at 21:44, Michael Gogins <michael.gogins@gmail.com> wrote: I just tried this and got the following error: |
Date | 2017-11-18 22:05 |
From | Steven Yi |
Subject | Re: [Csnd] New Windows installer release candidate |
Thanks, that confirms Nathan's problem and I believe my analysis. Could you respond to my last email then as to why you added the code to #ifdef in csoundCondWait and related functions? For me, I can run with -j2 and I'm using VS2017. I do not have VS2015 here to test anything (last I tried to get VS2015 sdk and/or VS installed here it messed up things so that I'm loathe to try installing either of those again). On Sat, Nov 18, 2017 at 4:44 PM, Michael Gogins |
Date | 2017-11-18 23:36 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
The issue arises from trying to build on my Windows 8 machine with Visual Studio 2015. Microsoft has unresolved problems with installing the appropriate Windows SDK for Visual Studio on Windows 8, which on my computer caused the installer for Visual Studio 2015 to install the correct Windows SDK only incompletely. The syncapi.h header is only available in a complete installation of the correct SDK. .Ultimately, I was able to work around this problem, and at some point, I will get an up to date Windows computer and the issue will be moot. I don't see why this should cause problems on AppVeyor, but if it does the #ifdef can simply be removed. Be aware that as far as I can see this will impose a requirement of using Visual Studio 2015 or later on Windows 8.1 or later for the MSVS build. The condition variable functions are not available on Windows 7. If that's OK, let me know and I will remove the #ifdefs. Best, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Nov 18, 2017 at 2:05 PM, Steven Yi |
Date | 2017-11-18 23:47 |
From | Steven Yi |
Subject | Re: [Csnd] New Windows installer release candidate |
Thanks for explaining that. I think for me, it's no problem as I'm already using VS2017 and am unaffected by this. However, the only way I see the AppVeyor build printing those messages is if it is affected by the #ifdef. Windows 8 gets end of life for mainstream support in a little less than two months (Jan 9, 2018): https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet I think we can't really proceed without fixing the issue. I suspect there might be a way to implement something similar to the SYNCHRONIZATION_BARRIER code on < win 8, but it may not be worth it, IMO. I'd suggest we get rid of the #ifdefs, move forward, and revisit if someone else raises an issue. On Sat, Nov 18, 2017 at 6:36 PM, Michael Gogins |
Date | 2017-11-18 23:59 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
I should add, I downloaded this just now and it comes with CsoundVST: https://ci.appveyor.com/api/buildjobs/kk8d47adayyya153/artifacts/msvc%2FSetup_Csound_x64_6.10.0rc-vst.exe After clearing and resetting the VST paths in Reaper, CsoundVST worked fine for me. Regards, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Nov 18, 2017 at 12:46 PM, Nathan Holmes |
Date | 2017-11-19 00:00 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
I will remove the #ifdefs. Best, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Nov 18, 2017 at 3:47 PM, Steven Yi |
Date | 2017-11-19 00:01 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
By the way, I would like to change the AppVeyor build to include debug information. In other words, to build both Csound and CsoundQt with both optimizations and debug information databases. This could enable us to get a fix on problems without having to rebuild everything. Is that OK with you? Best, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Nov 18, 2017 at 4:00 PM, Michael Gogins |
Date | 2017-11-19 00:05 |
From | Steven Yi |
Subject | Re: [Csnd] New Windows installer release candidate |
Do you mean RelWithDbgInfo? I thought we had originally used that but I don't remember. I think that'd be fine, but I don't know if there are any linking issues with that. I'd say if you can get it to work then sounds good to me. On Sat, Nov 18, 2017 at 7:01 PM, Michael Gogins |
Date | 2017-11-19 00:18 |
From | Michael Gogins |
Subject | Re: [Csnd] New Windows installer release candidate |
It works for me here. I will push it and we will see if it builds and runs from the installer. It's actually "RelWithDebInfo" for CMake and QMAKE_CXXFLAGS_RELEASE+=/Zi ^ QMAKE_CXXFLAGS_RELEASE+=/Od ^ QMAKE_LFLAGS_RELEASE+=/DEBUG ^ for qmake. Best, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Nov 18, 2017 at 4:05 PM, Steven Yi |
Date | 2017-11-20 16:38 |
From | Tarmo Johannes |
Subject | Re: [Csnd] New Windows installer release candidate |
Hi, Finally I was able to download and install the build on a Windows 10 machine and CsoundQt 0,9,5 works fine, also with multicore functions, I will try if can also build CsoundQt using these llibs (when I get to another machine) but I believe it should work, Great! Thanks, Steven and Michael! tarmo 2017-11-18 2:30 GMT+02:00 Steven Yi <stevenyi@gmail.com>: I put in a few hours of Windows debugging and I think I've fixed some |
Date | 2017-11-22 11:27 |
From | Anders Genell |
Subject | Re: [Csnd] New Windows installer release candidate |
Hi!
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
I don't know if this is the correct thread to reply in, but here goes: I just downloaded the latest appveyor build and tried to run trapped from the examples folder. It ran almost all the way through, but the CsuondQt crashed. There was an option to run a debug, which I started to do, though not really knowing wjhat I was doing :-) I got a lot of messages like "Exception thrown at 0x00007FFC0F6B5CA5 (vst4cs.dll) in CsoundQt-d-cs6.exe: 0xC0000005: Access violation reading location 0x0000000000000008." Also, there seem to be no manual folder included in the installer... Version info: Microsoft Windows [Version 10.0.15063] CsoounQt Version 0.9.5 Using Csound version:6100 Precision:double (64-bit) C:\WINDOWS\system32>csound -z 0dBFS level = 32768.0 --Csound version 6.10 (double samples) Nov 20 2017 [commit: d1687a962bb272df726115199ce1a8970b30c884] libsndfile-1.0.29pre1 2162 opcodes Regards, Anders On Mon, Nov 20, 2017 at 5:38 PM, Tarmo Johannes <trmjhnns@gmail.com> wrote:
|