[Csnd] OSX 10.9
Date | 2013-11-08 12:12 |
From | flaviosp |
Subject | [Csnd] OSX 10.9 |
I'm with Mac OSX 10.9. And I have some problems. I get this message: WARNING: could not open library '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libfaustcsound.dylib' (-1) WARNING: could not open library '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libjacko.dylib' (-1) WARNING: could not open library '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libjackTransport.dylib' (-1) WARNING: could not open library '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/librtjack.dylib' (-1) What it means? How can I correct it? Csound is crashing after run! -- View this message in context: http://csound.1045644.n5.nabble.com/OSX-10-9-tp5729327.html Sent from the Csound - General mailing list archive at Nabble.com. |
Date | 2013-11-08 12:19 |
From | flaviosp |
Subject | [Csnd] Re: OSX 10.9 |
I have 'csound6.01.0-OSX10.8-x86_64'. I got also the message 'Buffer overrun in real-time audio input' -- View this message in context: http://csound.1045644.n5.nabble.com/OSX-10-9-tp5729327p5729331.html Sent from the Csound - General mailing list archive at Nabble.com. |
Date | 2013-11-08 12:20 |
From | Victor Lazzarini |
Subject | Re: [Csnd] OSX 10.9 |
it's not crashing because of these warnings. They are just opcodes that did not load. The crash is probably to do with something else. CsoundQT had a bug where it would hang at the end of the performance, so it's probably what is happening. Try 'Run in Term' (if you don't have any widgets). That will be fine. Victor On 8 Nov 2013, at 12:12, flaviosp |
Date | 2013-11-08 12:24 |
From | Victor Lazzarini |
Subject | Re: [Csnd] OSX 10.9 |
You can also try the new CsoundQT http://sourceforge.net/projects/qutecsound/files/CsoundQt/nightly-osx/CsoundQt-nightly-2013-11-07.tar.gz/download On 8 Nov 2013, at 12:20, Victor Lazzarini |
Date | 2013-11-08 12:26 |
From | Victor Lazzarini |
Subject | Re: [Csnd] OSX 10.9 |
That should not be a problem, unless you are hearing breakdown in audio. On 8 Nov 2013, at 12:19, flaviosp |
Date | 2013-11-08 15:49 |
From | Steven Yi |
Subject | Re: [Csnd] OSX 10.9 |
It's a bit odd that the faust opcode was not loading. I have it compiled with all of the dependencies compiled in as static libs, so: Steven-Yis-MacBook-Pro:embind stevenyi$ otool -L ~/Library/Frameworks/CsoundLib64.framework/Resources/Opcodes64/libfaustcsound.dylib /Users/stevenyi/Library/Frameworks/CsoundLib64.framework/Resources/Opcodes64/libfaustcsound.dylib: libfaustcsound.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) Not sure what's going on there. On Fri, Nov 8, 2013 at 7:26 AM, Victor Lazzarini |
Date | 2013-11-08 18:43 |
From | flaviosp |
Subject | [Csnd] Re: OSX 10.9 |
Thanks for your reply. I tried with 'Run in Term'. It was fine. No problem. I will install the new CsoundQT. About the 'Buffer overrun', it isn't a problem. The audio is perfect. I thought that could be part of the 'crashing' problem. -- View this message in context: http://csound.1045644.n5.nabble.com/OSX-10-9-tp5729327p5729356.html Sent from the Csound - General mailing list archive at Nabble.com. |
Date | 2013-11-08 19:21 |
From | flaviosp |
Subject | [Csnd] Re: OSX 10.9 |
I installed the new CsoundQT. Now I have the message: WARNING: could not open library '/Applications/CsoundQt-d-cs6.app/Contents/MacOS/../Frameworks/CsoundLib64.framework/Resources/Opcodes64/libjacko.dylib' (-1) WARNING: could not open library '/Applications/CsoundQt-d-cs6.app/Contents/MacOS/../Frameworks/CsoundLib64.framework/Resources/Opcodes64/libjackTransport.dylib' (-1) WARNING: could not open library '/Applications/CsoundQt-d-cs6.app/Contents/MacOS/../Frameworks/CsoundLib64.framework/Resources/Opcodes64/librtjack.dylib' (-1) Everything looks normal. No more 'crashing'. Thanks! -- View this message in context: http://csound.1045644.n5.nabble.com/OSX-10-9-tp5729327p5729358.html Sent from the Csound - General mailing list archive at Nabble.com. |
Date | 2013-11-08 22:34 |
From | Jacques Leplat |
Subject | Re: [Csnd] Re: OSX 10.9 |
Can you use core audio instead of jack? it's just that I am using osx 10.9, qt and the latest csound for ios. I vaguely remember getting jack audio errors, and switched to tell qt to use core audio instead. since then no problems to report. Jacques Leplat > On 8 Nov 2013, at 19:21, flaviosp |
Date | 2013-11-09 10:31 |
From | flaviosp |
Subject | [Csnd] Re: OSX 10.9 |
Thanks for the advice. I will try also with 'core audio'. -- View this message in context: http://csound.1045644.n5.nabble.com/OSX-10-9-tp5729327p5729365.html Sent from the Csound - General mailing list archive at Nabble.com. |
Date | 2013-11-09 14:07 |
From | flaviosp |
Subject | [Csnd] Re: OSX 10.9 |
Now, with the new CsoundQT, when I 'Run Term' I got the message: WARNING: could not open library '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libfaustcsound.dylib' (-1) WARNING: could not open library '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libjacko.dylib' (-1) WARNING: could not open library '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libjackTransport.dylib' (-1) WARNING: could not open library '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/librtjack.dylib' (-1) There is '1 errors in performance' -- View this message in context: http://csound.1045644.n5.nabble.com/OSX-10-9-tp5729327p5729369.html Sent from the Csound - General mailing list archive at Nabble.com. |
Date | 2013-11-09 15:14 |
From | Victor Lazzarini |
Subject | Re: [Csnd] OSX 10.9 |
These are warnings, not errors. Your error in performance is due to something else. On 9 Nov 2013, at 14:07, flaviosp |
Date | 2013-11-09 15:17 |
From | joachim heintz |
Subject | Re: [Csnd] Re: OSX 10.9 |
i had an error as well yesterday in using the Run in Term command in csoundqt. the reason seems to be related to the changes andrés did with the midi. the error message is for me: error: -+rtmidi='hostbased': unknown module is this your error message, too? j Am 09.11.2013 15:07, schrieb flaviosp: > Now, with the new CsoundQT, when I 'Run Term' I got the message: > > WARNING: could not open library > '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libfaustcsound.dylib' > (-1) > WARNING: could not open library > '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libjacko.dylib' > (-1) > WARNING: could not open library > '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/libjackTransport.dylib' > (-1) > WARNING: could not open library > '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64/librtjack.dylib' > (-1) > > There is '1 errors in performance' > > > > > > -- > View this message in context: http://csound.1045644.n5.nabble.com/OSX-10-9-tp5729327p5729369.html > Sent from the Csound - General mailing list archive at Nabble.com. > > > 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" > > > |
Date | 2013-11-09 16:33 |
From | Andres Cabrera |
Subject | Re: [Csnd] Re: OSX 10.9 |
Yes, this is my fault ( problem is in csoundqt only), will fix soon . A On Nov 9, 2013 7:18 AM, "joachim heintz" <jh@joachimheintz.de> wrote:
i had an error as well yesterday in using the Run in Term command in csoundqt. the reason seems to be related to the changes andrés did with the midi. the error message is for me: |
Date | 2013-11-13 09:52 |
From | Luis Antunes Pena |
Subject | Re: [Csnd] Re: OSX 10.9 |
I can't get CsoundQT to output any
sound after the latest installation
(CsoundQt-nightly-2013-11-07.tar.gz). Is it the same problem. or
am I missing something?
Thanks, Luis Am 09.11.13 17:33, schrieb Andres Cabrera:
|
Date | 2013-11-14 00:12 |
From | Andres Cabrera |
Subject | Re: [Csnd] Re: OSX 10.9 |
This is strange as CsoundQt doesn't output any sound, but uses csound's audio output modules. Can you double check your configuration, hardware and report any error messages? Cheers, Andrés On Wed, Nov 13, 2013 at 1:52 AM, Luis Antunes Pena <k_o_m_p@yahoo.de> wrote:
|
Date | 2013-11-14 07:16 |
From | Luis Antunes Pena |
Subject | Re: [Csnd] Re: OSX 10.9 |
Attachments | Bildschirmfoto 2013-11-14 um 08.13.16.png |
Well I haven't changed the options of
CsoundQt so it should work as it was doing before.
I have notice now that CsoundQt is using this csound version: Csound version 6.00.1 (double samples) Aug 11 2013
SECTION 1: Score finished in csoundPerformKsmps(). inactive allocs returned to freespace end of score. overall amps: 0,00000 overall samples out of range: 0 0 errors in performance closing device 216 1024 sample blks of 64-bit floats written to dac
Thanks for
your help. Luis Am 14.11.13 01:12, schrieb Andres Cabrera:
--
Severinswall 54 D-50678 Köln http://luisantunespena.eu +49 (0)221 29020757 +49 (0)176 968 09 867 (mobile) |
Date | 2013-11-14 17:56 |
From | Andres Cabrera |
Subject | Re: [Csnd] Re: OSX 10.9 |
Hi, I can see what you describe in my mac system. I'm not sure why, but you actually need to specify sr and ksmps for audio to work now. I'm not sure what has changed in Csound or CsoundQt to cause this, but the fix is to specify something like:sr=44100 It is normal for CsoundQt nightly builds to have a different version because they bundle Csound inside them, and we haven't updated the version of Csound in the nightly build server. Andrés On Wed, Nov 13, 2013 at 11:16 PM, Luis Antunes Pena <k_o_m_p@yahoo.de> wrote:
|
Date | 2013-11-15 09:44 |
From | Luis Antunes Pena |
Subject | Re: [Csnd] Re: OSX 10.9 |
Thanks Andres. I'll try it.
Luis Am 14.11.13 18:56, schrieb Andres Cabrera:
--
Severinswall 54 D-50678 Köln http://luisantunespena.eu +49 (0)221 29020757 +49 (0)176 968 09 867 (mobile) |