Re: [Bluemusic-users] problem with very first steps

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hi All,

I'm now having a very difficult time reproducing this problem.  Since
things seem to be working here at least, I'll wait to hear back from
Stefan, otherwise I will move on to other tasks for the time being. If
anyone comes across this, please take note of what steps you were
doing when it happened.

Thanks!
steven

On Wed, Oct 5, 2011 at 3:24 PM, Steven Yi <ste...@gm...> wrote:
> Hi All,
>
> Just an update on status, regarding allowing i() to allow i-rate
> variables, I have added that to Csound and that will be in the next
> release. If you compile csound from git, you can take advantage of
> that change now.
>
> Regarding the test project, strangely enough it worked for me right
> after loading it.  I did some analysis and it looks like the direct
> value is used (instead of creating a k-rate var) when parameter
> automation is not enabled for a widget.  That is correct as it
> preserved backwards compatibility from when before parameters were
> able to be used in realtime with the API, and from before automation.
>
> However, there seems to be a bug when creating instances of an
> instrument or effect when somehow an instrument or effect might think
> it is not set to allow automation when it really is.  I get the
> impression from what I'm seeing so far that it's a case when first
> instantiating it from the library into a project, but that if you save
> the project and reload it it will be good again.  I'm looking into
> what triggers this scenario now; hopefully should figure it out soon.
>
> Stefan: is the problem still there for you if you re-open the project?
>
> Thanks!
> steven
>
>
> On Wed, Oct 5, 2011 at 6:30 AM, Stefan Thomas
> <kon...@go...> wrote:
>> Dear Steven,
>> I'm sending You my project.
>> Thanks very much for Your help!!
>>
>>
>>> Hi Stefan,
>>>
>>> The problem is one that can come up with blueSynthBuilder instruments
>>> and how they're designed.  I end up running into the same issue myself
>>> at times, and it happens when you run blue without the API enabled.
>>> There are some solutions to this:
>>>
>>> 1. Change csound's i() function to allow i values (will be looking into
>>> this)
>>> 2. change blue's output to always generate k-values
>>> 3. modify the original instrument
>>>
>>> If you would, could you send me a copy of your .blue project to my
>>> email and I'll use it to see if I can find an easier solution that
>>> would require no changes to blue projects. (I'll look into this
>>> tonight)
>>>
>>> Thanks!
>>> steven
>>>
>>>
>>> On Mon, Oct 3, 2011 at 9:45 PM, Stefan Thomas
>>> <kon...@go...> wrote:
>>> > Dear community,
>>> > as You suggested me, I took a look at the output menu, of my file. I
>>> > also
>>> > generated a csd file which I could run without problems, but without
>>> > sound
>>> > also.
>>> > Here is the text of the error message:
>>> >
>>> >> virtual_keyboard real time MIDI plugin for Csound
>>> >> PortAudio real-time audio module for Csound
>>> >> PortMIDI real time MIDI plugin for Csound
>>> >> 0dBFS level = 32768.0
>>> >> Csound version 5.13 (double samples) Mar? 8 2011
>>> >> libsndfile-1.0.23
>>> >> UnifiedCSD:
>>> >> /home/stefan/computermusik/
>>> blue_examples/tempCsd488722403502125920.csd
>>> >> STARTING FILE
>>> >> Herstellen des Orchesters
>>> >> Creating score
>>> >> orchname:? /tmp/csound-XFa9P2.orc
>>> >> scorename: /tmp/csound-z8G9aJ.sco
>>> >> RAWWAVE_PATH: /usr/share/stk/rawwaves/
>>> >> rtaudio: PortAudio module enabled ... using blocking interface
>>> >> rtmidi: ALSA module enabled
>>> >> orch compiler:
>>> >> ??? opcode??? panner??? kk??? k
>>> >> ??? opcode??? mvpPluck??? a??? ikiiii
>>> >> ??? instr??? 1
>>> >> St?rung:? illegal opcod from expr anal, line 54:
>>> >> asig mvpPluck iamp, ifreq, 1, i(0.1047733), i(0.09501993),
>>> >> ifreq/(i(1.3687252))
>>> >> St?rung:? input arg '#i5' used before defined, line 54:
>>> >> asig mvpPluck iamp, ifreq, 1, i(0.1047733), i(0.09501993),
>>> >> ifreq/(i(1.3687252))
>>> >> St?rung:? illegal opcod from expr anal, line 54:
>>> >> asig mvpPluck iamp, ifreq, 1, i(0.1047733), i(0.09501993),
>>> >> ifreq/(i(1.3687252))
>>> >> St?rung:? illegal opcod from expr anal, line 54:
>>> >> asig mvpPluck iamp, ifreq, 1, i(0.1047733), i(0.09501993),
>>> >> ifreq/(i(1.3687252))
>>> >> St?rung:? input arg 'i(0.09501993)' used before defined, line 54:
>>> >> asig mvpPluck iamp, ifreq, 1, i(0.1047733), i(0.09501993),
>>> >> ifreq/(i(1.3687252))
>>> >> St?rung:? input arg 'i(0.1047733)' used before defined, line 54:
>>> >> asig mvpPluck iamp, ifreq, 1, i(0.1047733), i(0.09501993),
>>> >> ifreq/(i(1.3687252))
>>> >> St?rung:? illegal opcod from expr anal, line 59:
>>> >> ??? isilence_length = i(0.04797499)
>>> >> St?rung:? input arg 'i(0.04797499)' used before defined, line 59:
>>> >> ??? isilence_length = i(0.04797499)
>>> >> St?rung:? illegal opcod from expr anal, line 60:
>>> >> ??? istart = isilence_length + i(0.15186237)
>>> >> St?rung:? input arg '#i10' used before defined, line 60:
>>> >> ??? istart = isilence_length + i(0.15186237)
>>> >> St?rung:? illegal opcod from expr anal, line 61:
>>> >> ??? kenv linseg 0, isilence_length, 0, i(0.15186237), 1,
>>> >> p3-istart-0.12290563, 1, 0.12290563, 0
>>> >> St?rung:? input arg 'i(0.15186237)' used before defined, line 61:
>>> >> ??? kenv linseg 0, isilence_length, 0, i(0.15186237), 1,
>>> >> p3-istart-0.12290563, 1, 0.12290563, 0
>>> >> ??? instr??? blueAllNotesOff
>>> >> instr blueAllNotesOff uses instrument number 2
>>> >> 12 syntax errors in orchestra.? compilation invalid
>>> >
>>> >
>>> >
>>> >> Csound Output Dialog is located under the Window Menu (it is called
>>> >> Output).
>>> >>
>>> >> There is another interseting Output Dialog (which could have been
>>> >> called
>>> >> blue Output Dialog) located under the View Menu and it's called blue
>>> >> Application Log.
>>> >>
>>> >> The manual is outdated but some elements (like these ones) are still
>>> >> relevant in it.
>>> >
>>> >
>>> > ------------------------------------------------------------------------------
>>> > All the data continuously generated in your IT infrastructure contains a
>>> > definitive record of customers, application performance, security
>>> > threats, fraudulent activity and more. Splunk takes this data and makes
>>> > sense of it. Business sense. IT sense. Common sense.
>>> > http://p.sf.net/sfu/splunk-d2dcopy1
>>> > _______________________________________________
>>> > Bluemusic-users mailing list
>>> > Blu...@li...
>>> > https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>>> >
>>> >
>>
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy1
>> _______________________________________________
>> Bluemusic-users mailing list
>> Blu...@li...
>> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>>
>>
>