Code Monkey home page Code Monkey logo

blue's People

Contributors

ainola avatar kunstmusik avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

blue's Issues

mixer improvement [sf#16]

When using mixer, you can't overlap two or more notes
of a single instrument, because the automatic
generated code for blueMixerOut is something like:
ga_bluemix_0_1 = aout
and not
ga_bluemix_0_1 = ga_bluemix_0_1 + aout
(and if you try putting manually that code into the
instrument code, you get out-of-range samples,
because in the mixer instrument, there's no zeroing
of those variables after outc).

Thank you,
Remigio

[email protected]

GUI flag: (don't) use persistent temp files [sf#47]

Sometimes blue leaves behind alot of tempCsd****.csd in the project directory, probably when exiting in an unclean way. It would be nice with a flag that told blue not to keep them around but to deleate them after every run.

Line Object [sf#5]

Hi Steven,
I'm writing to propose the creation of a "Line Object"
type.
What I mean is an object that can be placed on a track
on the score, which contains a graph that can be
edited, and which produces output to a "Line
instrument" which in turn produces output to a global
k-rate variable (or maybe even a zak variable).
The behaviour of the graph could be very similar to the
envelopes in the DX7 instrument, with maybe the
addition of maximum and minimum values. It would be
nice if while dragging, the value of the point, plus
the time (within the object, and also in the global
score) could be shown.

What do you think?

Cheers,
Andres

An error message for not having assigned a widget – value [sf#27]

An error message for not having assigned a widget – value. This is just helpful for new users. I really spent some time to evoke a list of my assigned widget- names with "ctrl+shift and space", until I found out that configuring it in BSB had not worked for me. But I would like to request is only if it is easy and quick to do.

clearing File Selector [sf#45]

It would be nice with some way to clear a File Selector widget, so that the user who downloads an instrument via Blue Share doesn't get it filled out with the last file the developer had in the widget.

Grid for Line-Objects [sf#26]

A user defined horizontal grid for Line-Objects would be nice. The user could choose how many grid- lines are wanted (1,3,9,) and if the scale should be logarithmic or normal. ...just an idea :-)

copy button [sf#50]

- a copy button to copy the path of a SoundFont (SF2) in the SoundFont Viewer

clickable levels in mixer

It would be nice it it was possible to (double-)click on the "0.0 db" text on each mixer strip and enter a numeric volume (like -2.4) in a small popup box or in a way simmilar to when editing values in fx's gui.

Assigning expression to controls [sf#31]

In an instrument made with BlueSynthBuilder, allowing a value of a control to be replaced with an expression like p5 or gavalue instead of its numerical value (so every <name> in the instrument code is replaced literally by that expression), would make the use of these instruments much more flexible.

Present BlueSynthBuilder instruments have the advantage of making it easy to choose values, but the disadvantage that you cannot let the parameters vary wildly in the score, because you would have to make a new instrument for every combination of parameters. Ramping, using previous and next values (np5, pp4), and random distribution are not at all possible now. It would be if the value of controls could be expressions.

The expression could be any text, e.g. p5 for one control and p5*1.5 for another.

static lineObject [sf#9]

Hi Steve,

I was thinking about a different version of the line
object that would just create tables using Gen7,
without the instruments as the other linObject does.
These tables would always be rendered, regardless of
where this new line Object is in the score timeline.
Essential a graphical means to create tables, using the
code that's already there for line/zakObject. The name
of the line would be the f-table number.

-Bill B
[email protected]

Preset comments [sf#49]

I was thinking it would be nice to have a preset comments BSB widget that would allow one to enter notes specific to the preset. This would be useful for such information as suggested range of frequency or duration, and any other comments.

bw

scaling lines [sf#28]

would it be possible when scaling a Generic Object that is in use with the BlueSynthBuilder, that the lines would be scaled also?

feeze counting [sf#42]

when freezing SoundObjects it overwrites a previous frozen sound.
It is true that i froze a sound, then un-froze it and then freeze another sound. It then overwrites the saved sample of the un-frozen sound which i like to have it around as a sample for later use.
Of course i could rename the frozen sample but when i'm in the creative process i tend to forget such administrative side-effects.
Is it possible to continue the numbering of freezes even if they are unfrozen at some point?

Pasting with middle button on linux [sf#18]

Hi Steven,
I am missing the ability to paste using the middle
button on linux, this used to work but after a move to
a different system it stopped. If it's not difficult,
I'd really appreciate this, if not don't bother.

Thanks as usual,
Andrés

new instrument i# behavior [sf#1]

i wouldn't mind a change in the behavior of new
instruments. rather than pick the first available
number, i propose it picks the next available number
starting from the instrument you have selected.

here's my reasoning for why:

i like to group my instruments in two or three main
categories, the main two being instruments and global
dsp effects. a lot of times in more developed work
i'll also have a controller category for fine tuning
performances.

i seperate these categories by hundreds in the
instrument number, so regular instruments would use
1-99, dsp would use 100-199, etc.

this would allow me to select a dsp instrument, and if
i were to add a new, or duplicate an old instrument, it
would be in the same &quot;range&quot; of numbers.

audio loop [sf#3]

the ability to loop audio files.
this might include: time stretch, transposing.

Piano Roll improvements [sf#22]

I use midi note in the piano roll object.
Often i lose myself between the rows, because on the left
there is only marked the first C note of each octave. I would like to see marked every rows of the "keyboard", just like in the "blue PCH" mode. Thanks.
Paolo.

add a split tool in the score timeline [sf#17]

This tool would be like the scissors in most DAW
software. It would allow the user to divide one object
into two or more pieces. For example, one 10 second
GenericScore object could be cut into two objects, one
3 seconds and one 7 seconds. The 7 second block could
also be cut into three segments, perhaps 2 seconds, 2
seconds, and 3 seconds.

Repeat Time Behavior change [sf#7]

The current "Repeat" option for a soundObject's Time
Behavior (as accessed from the soundObject's Properties
dialog box) seems to have a staticly-defined loop point.
That is, it will only repeat the soundObject once the
previous soundObject instance's notes have all died.

I suggest that there be a user-defined loop point within
the soundObject, indicating when the next loop will
begin, relative to the other i-statements in the
soundObject. For instance, with a genericScore object
containing the following notes:

i1 0.0 2 8.00 15000
i1 0.5 2 8.02 15000
i1 1.0 2 8.04 15000
i1 1.5 2 8.07 15000

...one could be able to, having specified a repeat
behavior in the properties box, define the loop point to
be at beat 2.0; otherwise, the next loop would begin at
3.5, after the last i-statement finishes playing.

BSB waveform rendering object for assigned audio-files [sf#32]

A BSB object that shows waveform of an assigned (through a file selection object?) audio-file would be very useful. Particularly if it supported a highlighting feature to set the beginning and end of samples in seconds for looping (so to be used with loscil or lposcil opcodes for instance).

Thanks

loop and speed [sf#19]

two small and simple functions that would blue and my
life easier:

- checking/unchecking the loopfunction by Control + l

  • adding a little box for entering the speed (t in csound)

Randomize instrument [sf#30]

I would like it if an instrument made with BlueSynthBuilder could be randomized. Letting Blue choose random values for the parameters of an instrument may make it easier to find unexpected interesting sounds. Or if the user likes a preset but is not entirely satisfied, he/she might find better settings by allowing small random variations.

I think it would be best done with a third mode besides edit mode and non-edit mode, called randomize mode or something. It would add extra stuff on

  • knobs
  • sliders
  • XY controllers
  • line objects
    and maybe also on
  • dropdown lists
  • checkboxes
  • text fields
    that allow the user to specify a minimum and maximum for the random values (by default the whole range of the control). Forbidding randomization of a control could be done by making the maximum and the minimum equal.

The user could check the new random values by simply playing a small score that contains the instrument.

Integration with documentation [sf#4]

Hi Steven,
Something I find very useful, especially when I was new
to csound was the option in WinXoundPro to display the
appropriate help page when pressing F1. What happened
was that the word you were standing on would determine
the help page that was opened. If the opcode did not
exist, the index would be shown. Maybe it's prudent to
wait a while while the final format of documentation is
determined...
An alternative to this would be to display the
appropriate syntax for the opcode you are standing on
(which might be easier since this is already there for
the syntax highlighting)

Thanks as always,
Andres

tracker object [sf#29]

I would love if in the track object pressing insert would shift all the notes below the cursor (including the one the cursor is on) down by one position. Similary pressing delete would push everything up. It's the way all trackers work. Also how come there isn't a standart csound pitch class option in Piano Roll pitch generation options? This way i have to design instruments for use especially with piano roll which is whack. Thank you:)

my e-mail is [email protected]

midi-out support [sf#11]

a module for sending out mididata to external synthsizers.
a module like the PianoRoll for sending mididata (With
the opcode 'noteondur')to external synthesizers. Maybe
an extension of this module could be the sending of
controller data -for controlling brightness for
example, or panning- by drawing lines?
With the present PianoRoll i can't get the right
resolution in octaves, this module would make it much
simpler.

Bars below piano roll notes for graphical P field editing [sf#10]

It would be great to have vertical bars below piano
roll notes for graphical P field editing, with the
ability to switch between which P field was being
displayed - similar to velocity and controller editing
in MIDI sequencers. This would be a great help when
working with complex instruments.

split for samples [sf#20]

a scissors tool for splitting samples - sounds that
once were Objects but now frozen, or imported sounds.
Maybe a start to make Blue even more suitable as a
compositional environment for Musique Conctrete.
And dubbelclicking on a frozen Object or imported sound
and go to Audacity, make modifications and
automatically re-imported back in Blue.

Add and multiply note processor that deals with random vals. [sf#6]

Have an add and multiply note processor that act like
the existing ones, except instead of using a constant
value to add or multiply by, use a random number falling
within a user-defined range (floating-point). The
random number applied should be different for each note
(i-statement) in the object.

Denorm Checkbox in mixer [sf#48]

A unified way of handling denorms in blue would be great.

Adding a denorm checkbox to the mixer seem handy to handle all the cases with the mixer and that might generally be enough.

Frequency slider [sf#23]

Currently, when creating BlueSynthBuilder instruments, in order to create an input for the full range of frequencies, I have to use two sliders to achieve the best accuracy; one (0-1000 increment 1) plus the other (1000-16000 increment 1000) equals the desired frequency. This is kind of a pain.

If there was a slider that graduated its values so that most of the slider's positions represented the most used/desired frequencies, that would be handy. For instance, the low third of the slider would cover 0-200, middle third 201-3000, top third 3001-16000. There is precedence; Sound Forge uses this kind of widget for purposes of setting the CO of one of its filters, I think.

markers [sf#12]

dropping markers as you play your composition.
now that the cursor is working, it might be nice to
drop markers when listening to the composition you're
making. The use is to say:'here i want something to
happen'or 'this Object has to move a little ahead'.
(In SoundForge this is done when pressing the M.)

line numbers for Generate CSD To Screen [sf#44]

- the Csound Output Dialog tells me when there is an error and in what line in the CSD.
It would be handy to give the "Generate CSD To Screen" option linenumbers (don't know if it is possible). It will make the error searching a lot easier.

zooming [sf#24]

zooming in the Score Timeline with keys Alt + - and Alt + + on the numeric field.
if problems with Mac (i don't know) the Shift insteas of Alt

edit values of points [sf#15]

in the LineObject i'd like to be able to edit the x and
y values of a chosen point. In case of making a line
with points for the pitchgeneration it would be great
to give precise values for this pith so it can easily
harmonise with other sounds.
of course within the bounderies i put in as min and max
values.

automation point list [sf#43]

- being able to make a selection of several or all points in a edit list or in the Score Tab and make some copying and calculations possible to these numbers.
A scaling possibility - i requested this before - could be roughly like this:
Control+a point on the automation line = begin of selection
Control+rightclick on a point = end of selection
Then for scaling:
Control+Shift+leftclick on point = moving the selection
Control+Shift+rightclick on point = all selected point can be scaled like at the moment a SoundObject can be scaled

Visual indication for content in tabs [sf#38]

It would be nice to have some visual indication whether there is content in the global tabs for instruments. Sometimes you miss some obvious error, because the problem is in the global orc or global sco tabs of the instrument.
I'm not sure exactly what to suggest, maybe a lighter color if they're empty, or something like bold title if there is content.

Thanks!
Andrés

Playback AudioFile/FrozenObject from mid-point [sf#33]

It would be nice to be able to playback an AudioFile or FrozenObject mid-point and have the audio play at that point in the audio, especially for long compositions/objects. Right now if you do this, the object doesn't get included in the rendered score at all.

Allow to change the type of a widget [sf#40]

When a user removes a widget and adds a widget of a different type, giving it the same name as the widget that was removed, the value of the widget in the presets is usually incorrect. Moreover it can't be safe because the values of different types of widgets are not always compatible.

Therefore it would be better if the user interface allowed to change the type of a widget (to those types it is compatible with of course, e.g. change knob into slider). Particularly interesting is changing a checkbox into a dropdown list or slider, to allow more choices where before two were sufficient.

zooming sliders [sf#8]

- sliders for the zooming function (like Sympheo,
another Java application) in the Scoretab

utilities [sf#13]

an intergration of the utilities like hetro, lpanal,
pvanal and cvanal into Blue

ideas for development [sf#2]

- counter or cursor so one can see where one is
on the timeline. Also being able to put markers so when
listening making intuitivly points so that one can drag
his sounds to these markers.

  • saving the width of the window of the timeline
  • draw your own linseg for your envelopes---
    this envelope can also be used for score-events-
    generation, (maybe combined with a Pythonpreset?)
    and can be scaled on the timeline.
  • make a link for a soundfile to be processed by
    Cecilia. Maybe more connection with Cecilia where one
    can use it hetro, pvoc and other csoundutilities.

restyle of mixer [sf#37]

- the mixer as it is now takes a lot of space on my screen. i think it can be twice (or more) as small and not lose its functionallity.
This will also improve the general view of the faders.

split for samples [sf#20]

a scissors tool for splitting samples - sounds that
once were Objects but now frozen, or imported sounds.
Maybe a start to make Blue even more suitable as a
compositional environment for Musique Conctrete.
And dubbelclicking on a frozen Object or imported sound
and go to Audacity, make modifications and
automatically re-imported back in Blue.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.