Just a thought: nbits should never have been an input argument of a
playback function, since the precision of the internal data is much
higher than even 24 bit, the higher bit resolution usually found in
audio playback systems (not to be confused with the internal
representation of many digit
hi all,
What can cause the following behaviour:
there are two "circuits", one is built entirely of the original xcos
components,
another one uses a mix of coselica and xcos.
The circuit with coselica reports "Algebraic loop", whereas the pure xcos
does not.
The two schemes are attached. The figur
Le 02/03/2020 à 16:45, Perrichon a écrit :
Ok but this is a strange way to handle backward compatibility
I agree. This is why i asked for confirmation to a second reviewer
before removing nbits,
when the first reviewer asked me to remove it.
nbits was never implemented (never actually used
Ok but this is a strange way to handle backward compatibility
De : users De la part de Samuel Gougeon
Envoyé : lundi 2 mars 2020 16:15
À : users@lists.scilab.org
Objet : Re: [Scilab-users] strange sounds repeated over and over in scilab
6.1.0
Le 02/03/2020 à 14:52, Perrichon a écrit :
Le 02/03/2020 à 14:52, Perrichon a écrit :
Hello
Few years ago, I got routines producing sounds in threads
With Scilab 5.5.2, sounds are produced once.
With Scilab 6.1.0, sounds are repeated endlessly.
No no, "only" 16 times :-)
You can stop it with playsnd([]) or CTRL+C.
I have proposed
Hello
Few years ago, I got routines producing sounds in threads
With Scilab 5.5.2, sounds are produced once.
With Scilab 6.1.0, sounds are repeated endlessly.
Best regards
W10 x64
function Sound1()
// by Gary Scavone, McGill University, 2004
// Bell-like sound
Hello,
Zoom and datatips no longer work in Xcos version 6.1.0 during runtime
It well run with Scilab 5.5.2
See also bugzilla #16353
Best regard
Pierre P.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.
Hello Pierre,
Thanks for the numbers, I will try to describe what can be down to work around
the time to results.
>From when you start the simulation to the first scope popup, the schema is
>converted to a list of functions to be called in a specific order and passed
>to a solver that will ite
Hello Clément,
Yes, I have some function blocks and expression blocks.
Must I understand that I have to write CBLOCK for scilab function or scilab
expression or both ?
Here are other results for a more complex project name PELT1
Time request : 100 s
Results :
Xcos Scilab 5.5.2 :
Hello Pierre, Samuel,
First, did you opened a bug on that issue?
Second, to me, the bug is located on the script2var() function which resolves
the context and output a struct of `variable=value` that are defined for the
diagram (and its parents). For example, when I explicitly define A=100 in t
10 matches
Mail list logo
