Thread: [Bluemusic-users] [announce] - blue 0.110.0
Brought to you by:
kunstmusik
From: Steven Y. <ste...@gm...> - 2006-12-25 08:01:46
|
Hi All, I'd like to announce the latest version of blue is now available at: http://www.csounds.com/stevenyi/blue The big change for this release is the new Parameter Automation system allowing users to draw control signals on the main timeline to automate knobs, sliders, and xy controllers for BSB Instruments and Mixer Volumes and Effects. A picture is available here: http://www.kunstmusik.com/automation.png and some basic documentation here: http://www.csounds.com/stevenyi/blue/usermanual/html/parameterAutomation.html There a number of other changes listed in the ChangeLog below. Since there was a lot of internal reworking done and since there was a lot of code done and redone to support Parameter Automation, it is highly recommended to make backups of any existing projects before working with the new version. I'd like to especially thank Will Light for helping to test out the beta releases. The feedback greatly helped to find bugs and improve the overall release. Also, thanks to Michael Bechard and everyone else who reported bugs and requests! Otherwise, best wishes, happy holidays, and enjoy! steven [CHANGE LOG] >Notes for 0.110.0< [released 2006.12.25] Steven Yi----------------------------------------------------------------------- blue [new] - Parameter Automation - Editable automation of parameters (knobs, sliders, xy-controller from BSB and Effects, mixer volume) on timeline (see documentation for more information, also examples/features/automation1.blue for an example) [new] - BSB/ObjectBuilder - PresetManager now able to cut/copy/paste items in PresetsManager Dialog, as well as able to add groups in dialog and import/export item or folder to file - reworked to require all object names to have unique names for their replacement values and don't clash with any other object within that BSB or ObjectBuilder [new/updated] - Piano Roll - added labels for all notes in MIDI mode (Request 1604019 by Paolo) - added new green hilighter in row header for selected notes, follows selected notes when moved up and down to easier show what note is currently being edited [new/updated] - Redid blueLive interface, started work on MIDI SCO Pad to record MIDI data as SCO using note templates (not yet finished) [updated] - Redid SoundLayer User Interface; no longer uses JTable, instead using custom panels [updated] - Changed number of different height sizes for layers from 5 to 9 [updated] - When setting min and max values for lines and BSB Objects that have these values, better checking is done and user is alerted if new boundary value crosses the other boundary, and option is shown to user to either rescale the values to the new min and max, or to keep values and truncate any that are outside of the boundaries to the boundary value [updated] - Render to Disk dialog stays open after finishing [updated] - Changed drawing strategy for TimeBar in main timeline and PianoRoll editor for speedup [fix] - When using "Render to Disk" or "Render to Disk and Play", now puts quotes around output file name [fix] - ProgramOptions Setting Dialog was setting values for RealTimeRender and DiskRender settings on global ProgramOptions even when window was closed or cancelled; now only saves values when OK button is selected [fix] - ProgramOptions Setting Dialog was not using saved window size correctly as it was incorrectly being reinstantiated every time it was opened [fix] - When editing line points using table from popup, setting y value was not respecting min and max values [fix] - BSB/ObjectBuilder - CheckBox item was not loading correctly from presets [fix] - Made parsing of nchnls more robust by trimming spaces before parsing [fix] - nchnls from realtime settings were always being used when rendering mixer code even when doing disk renders internal [updated] - Reworked Note parsing and toString() methods; speed increase by about 3x (the Note class is a fundamental class and this speedup should improve CSD generation time) [updated] - Libraries and starter scripts updated -commons-lang library to 2.2 -swing-layout to 1.0.1 [updated] - LinePoint's y-values converted to be absolute instead of 0-1.0 relative [updated] - BSBWidget values converted to be absolute isntead of 0-1.0 relative |
From: Brent B. <bb...@ex...> - 2007-01-05 06:45:34
|
Great tool! I've just begun using blue again. First time I've really tried it out since version 0.8x although I've downloaded every release. I love the way blue is evolving. In running through the manual/tutorial I've had some issues with the PianoRoll object. Most likely user error, but when sending notes to BlueX7 I've had a hard time getting predictable pitches from the PianoRoll. BlueX7 is expecting pch format I think. blue PCH option must be just different enough to cause problems. I end up just editing the note template for each note which for a few notes is no big deal but for several it could get old. I love the PatternObject. I was messing with the example file and changing Pattern C. The thing I haven't discovered is how you edit an instance as Pattern A and Pattern B are. I open the Sound Object Library and there they are, but no way to edit. What did I miss? Something I would like to add to your request list is some kind of MIDI object to load in MIDI files. More specifically, something to make it easier to go from MIDI to .sco to blue. I like to use lilypond (and lilypondtool) for notation and composing. It spits out a MIDI file to play back. Is there a way to incorporate into blue a tool like MIDI to Csound on the Mac and then import the sco into blue? (I'm not using a Mac so have not tried the MIDI to Csound tool). Anyway, once again, great work on blue. I'll never go back to plain text files again. Brent -- View this message in context: http://www.nabble.com/-announce----blue-0.110.0-tf2878819.html#a8173703 Sent from the Csound - Blue - User mailing list archive at Nabble.com. |
From: Steven Y. <ste...@gm...> - 2007-01-06 15:13:07
|
Hi Brent, (Just a note, I had to approve your original email for the list as the mailing list software said you were not subscribed. For future emails, if you could subscribe to the list, even if you set it not to send you emails, it'll let you send emails without me having to manually approve them. I've set the list to subscribers only to prevent spam.) Really glad you like what you're seeing! I'll reply to your email inline below: > In running through the manual/tutorial I've had some issues with the > PianoRoll object. Most likely user error, but when sending notes to BlueX7 > I've had a hard time getting predictable pitches from the PianoRoll. BlueX7 > is expecting pch format I think. blue PCH option must be just different > enough to cause problems. I end up just editing the note template for each > note which for a few notes is no big deal but for several it could get old. blue PCH is different than normal PCH in that what comes after the . is the exact scale degree, so "8.1" in pch is equal to "8.10" while in bluePCH it's really octave 8 and scale degree 1. One should only use blue PCH if one is using the Tuning noteProcessor or other noteProcessors which accept blue PCH (never got around to some of those...). Otherwise, I'd recommend setting the frequency generation option on the pianoRoll to frequency when used with blueX7. > I love the PatternObject. I was messing with the example file and changing > Pattern C. The thing I haven't discovered is how you edit an instance as > Pattern A and Pattern B are. I open the Sound Object Library and there they > are, but no way to edit. What did I miss? For editing objects in the SoundObject library, double click it and the area in the main timeline where editing of soundObjects happens will be populated with the library copy. You can tell you're editing a library object as the soundObject's editor will have a green border around it. > Something I would like to add to your request list is some kind of MIDI > object to load in MIDI files. More specifically, something to make it easier > to go from MIDI to .sco to blue. I like to use lilypond (and lilypondtool) > for notation and composing. It spits out a MIDI file to play back. Is there > a way to incorporate into blue a tool like MIDI to Csound on the Mac and > then import the sco into blue? (I'm not using a Mac so have not tried the > MIDI to Csound tool). I could do this but I need more information as to what exactly should happen. Say a user wants to import MIDI file, I could set it up to be either from drag and drop or right-click on the timeline and select "Import MIDI file". From there, some kind of options would be necessary on how to handle the different number of tracks (show a template string for each to convert?), if there should be options to split different channels into different soundObjects, etc. It's simple to do a fixed MIDI2SCO translation, but it gets to be a lot more work when you start giving options on how to import that data, which to me seems where it gets interesting. If you and others here can explain in very detailed terms how you would like the user experience to go when you import a file, I'll be happy to implement it. Thanks and glad you're enjoying blue! steven |
From: Brent B. <bb...@ex...> - 2007-01-11 17:48:56
|
I am on the list now so viewing and posting comments should not be a problem. What I imagine happening is this: Lilypond puts out a separate MIDI channel for each instrument in your score. I believe it is saved as a type 1 MIDI file. Similar to how Midi2Sco converts each MIDI channel to send data to a unique instrument, and how blue imports .sco files to separate SoundObjects on the score timeline, I would like to see blue take my MIDI file, convert or process it however needed, and create a SoundObject for each channel in the MIDI file, possibly each channel on its own layer. It seems to me it could be a fairly straitforward process, but not being a programmer (yet) and unfamiliar with how Midi2Sco accomplishes what it does I thought I would present the idea to you and see what comes of it. Brent -- View this message in context: http://www.nabble.com/-announce----blue-0.110.0-tf2878819.html#a8278102 Sent from the Csound - Blue - User mailing list archive at Nabble.com. |
From: Steven Y. <ste...@gm...> - 2007-01-11 18:13:19
|
Hi Brent, I had to approve this message as well and the mailing list does not have you listed as a member. Could you try resubscribing? As for importing, it seems that what you're looking for was actually much simpler than what I had imagined. If the MIDI conversion is done like the import from CSD, then it doesn't give you an option to take a MIDI file and drop it at a specified point in time in an existing blue project. If all that is wanted is to take a MIDI file and import it to start a project, then that shouldn't be too big a deal. Could someone point me to where MIDI2SCO is, and if source is available? I'll probably just write it from scratch (well, Java comes with some MIDI reading functions already so it's not too bad I think), but having something as a reference would be nice. steven On 1/11/07, Brent Boylan <bb...@ex...> wrote: > > I am on the list now so viewing and posting comments should not be a problem. > > What I imagine happening is this: Lilypond puts out a separate MIDI channel > for each instrument in your score. I believe it is saved as a type 1 MIDI > file. Similar to how Midi2Sco converts each MIDI channel to send data to a > unique instrument, and how blue imports .sco files to separate SoundObjects > on the score timeline, I would like to see blue take my MIDI file, convert > or process it however needed, and create a SoundObject for each channel in > the MIDI file, possibly each channel on its own layer. It seems to me it > could be a fairly straitforward process, but not being a programmer (yet) > and unfamiliar with how Midi2Sco accomplishes what it does I thought I would > present the idea to you and see what comes of it. > > Brent > -- > View this message in context: http://www.nabble.com/-announce----blue-0.110.0-tf2878819.html#a8278102 > Sent from the Csound - Blue - User mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |
From: Brent B. <bb...@ex...> - 2007-01-12 05:53:05
|
Actually, I guess it's called Midi2Csound and the cSounds.com site points to some files at http://www.cs.bath.ac.uk/pub/dream/utilities/mac/midi2cs/ This version was made for Mac OS9. I thought I had seen a recent post somewhere for a newer OSX version. That's what got me thinking about it. I'll do some more searching. -- View this message in context: http://www.nabble.com/-announce----blue-0.110.0-tf2878819.html#a8292745 Sent from the Csound - Blue - User mailing list archive at Nabble.com. |
From: Brent B. <bb...@ex...> - 2007-01-13 02:32:31
|
Found this also: http://www.csounds.com/istvan/html/scoreproc.html -- View this message in context: http://www.nabble.com/-announce----blue-0.110.0-tf2878819.html#a8310474 Sent from the Csound - Blue - User mailing list archive at Nabble.com. |
From: Steven Y. <ste...@gm...> - 2007-01-13 10:06:38
|
Hi Brent, Thanks, I also came across this yesterday. I downloaded a midi file from Mutopia and will probably get a couple more for tests. In the end, I think I'll just do it from scratch as the code I'm seeing around is a bit much compared to just using the java library available. I think today I'll start working on the conversion part of the program, then after that will see how long it takes to implement the GUI part (I'll want to make it flexible, basically allowing different template notes for each channel so that one can assign whatever channel as well as how they want to do the pfields, with sensible defaults of course). Not sure how long it will take, but would guess within a few days. I've got a number of fixes I put in yesterday while working with blue as well as a new feature for setting a default layer height and setting all layer heights, so when the MIDI importing is done I'll probably push a new release. Thanks! steven On 1/13/07, Brent Boylan <bb...@ex...> wrote: > > Found this also: > > http://www.csounds.com/istvan/html/scoreproc.html > > -- > View this message in context: http://www.nabble.com/-announce----blue-0.110.0-tf2878819.html#a8310474 > Sent from the Csound - Blue - User mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |
From: Steven Y. <ste...@gm...> - 2007-01-13 15:38:23
|
Hi Brent and all, I've just completed an initial version of the MIDI import and placed a beta here: http://www.kunstmusik.com/blue_0.111.0_beta_installer.jar Right now there are no options, it just does a straight import and splitting between layers, one soundObject per layer, and one layer per track that has note data. I have it mostly set up to take in note templates in the same way that blueLive now takes them, where you're template is going to look like: i<INSTR_ID> <START> <DUR> <KEY> <VELOCITY> and the following keys allowed (you can see them from the code): note = TextUtilities.replaceAll(note, "<INSTR_ID>", instrId); note = TextUtilities.replaceAll(note, "<START>", Float.toString(start)); note = TextUtilities .replaceAll(note, "<DUR>", Float.toString(duration)); note = TextUtilities.replaceAll(note, "<KEY>", midiKey); note = TextUtilities.replaceAll(note, "<KEY_PCH>", midiPch); note = TextUtilities.replaceAll(note, "<KEY_OCT>", midiOct); note = TextUtilities.replaceAll(note, "<KEY_CPS>", midiCps); note = TextUtilities.replaceAll(note, "<VELOCITY>", midiVel); note = TextUtilities.replaceAll(note, "<VELOCITY_AMP>", midiVelAmp); So, my plan now is to add a step after parsing the MIDI that shows a table with each row representing a track, and in it the ability to edit the options for how to import that track, i.e. note template, truncating of soundObject and translation of note times within (trimming), and whatever other options users would want. If you're interested in MIDI import, please give this a try and voice your opinions on what you would like to see. Also, MIDI files can have time given in various ways. I have only test with time set as PPQ, and not any of the SMPTE times as I do not have any MIDI files with SMPTE time. Since I'm not necessarily that interested in this feature for myself, if you'd like support for this please send me a MIDI file with SMPTE and I'll program the support for it, otherwise it'll just stay the way it is. Now, I'm not sure about what controller values I can import, though I may be able to support reading of tempo (will have to see how that works) to generate a t-statement. (Please let me know if you'd like this). Also, with the current implementation, it expects noteOn's to be followed by noteOn's with vel 0 or noteOff's. If there's overlapping notes, there is no support at the moment. I can show a dialg for options on what strategy to use for this case and I think the possibilities are: -Truncate - if a new Note On appears that overlaps a note, the old note is turned off -NoteOff or Vel 0 turns off last note on, so notes may overlap -Join - after first note on, any new note on's will be ignored and the note will be closed off after the first note off All of the above is possible but a little complicated. Any ideas for what to do, what options to give (if any), and what names to give the options appreciated. Thanks! steven On 1/13/07, Steven Yi <ste...@gm...> wrote: > Hi Brent, > > Thanks, I also came across this yesterday. I downloaded a midi file > from Mutopia and will probably get a couple more for tests. In the > end, I think I'll just do it from scratch as the code I'm seeing > around is a bit much compared to just using the java library > available. I think today I'll start working on the conversion part of > the program, then after that will see how long it takes to implement > the GUI part (I'll want to make it flexible, basically allowing > different template notes for each channel so that one can assign > whatever channel as well as how they want to do the pfields, with > sensible defaults of course). Not sure how long it will take, but > would guess within a few days. > > I've got a number of fixes I put in yesterday while working with blue > as well as a new feature for setting a default layer height and > setting all layer heights, so when the MIDI importing is done I'll > probably push a new release. > > Thanks! > steven > > On 1/13/07, Brent Boylan <bb...@ex...> wrote: > > > > Found this also: > > > > http://www.csounds.com/istvan/html/scoreproc.html > > > > -- > > View this message in context: http://www.nabble.com/-announce----blue-0.110.0-tf2878819.html#a8310474 > > Sent from the Csound - Blue - User mailing list archive at Nabble.com. > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > opinions on IT & business topics through brief surveys - and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Bluemusic-users mailing list > > Blu...@li... > > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > > > |