Thread: [Bluemusic-users] Status
Brought to you by:
kunstmusik
|
From: Steven Y. <ste...@gm...> - 2008-09-08 19:37:54
|
Hi All, Just a quick note that I'm still working on completing the new release. It took a while to build out using the API when auditioning soundObjects, and I have to add support for API in freezing and in the soundfont viewer. Otherwise, want to take a look at blueX7 UI for envelope editing. So looking more like middle of this week for release. Thanks! steven |
|
From: Steven Yi <ste...@gm...> - 2009-09-11 02:30:20
|
Hi All, Just wanted to mention that I'm finally done with many things that have taken up a lot of my time and I'm back on blue work. Right now blue2 is coming along and I have a list of things that still need to be implemented. I'm taking care of them a little each day and progress is good. I am hoping to get some sort of beta out in two weeks. At that point I'll be looking forward to hearing everyone's thoughts on blue2. =) The first release of blue2 will be pretty much just have the same features as 0.125.0 but with the new window system and reorganized code. blue2 will also have some issues I'm sure and I've had to defer some of the more rarely used features until I can work out how to implement them. After the first release of 2.0, I'll also continue to work on internal restructuring and reimplementing of code. It'll take some time to be completely in-line with Netbeans RCP framework but it's something that will be ongoing work. I'm also starting to brainstorm to try to work out a plan for things to work on. Working out MIDI input is high on my list (as is all the things that go with that including instrument meta data for notes), as is working on the issues in the issue tracker. I did have the thought today that blueLive needs to be completely reworked. I am thinking of changing a number of things around with it, and perhaps making it have an interface like BlueSynthBuilder with the widgets being able to be used in global context. Another thought was to have score objects be boxes and be somewhat PD-like, with triggers and timers, etc. I'm thinking going down either of these routes can potentially be a lot of work, so it's still a brainstorming exercise. Another thing on my mind is samples in all of their usages: samplers, loops, waves, etc. The idea in my mind is adding features to make solved-problems solved, in other words making tools in blue that will solve a usage scenario so that we won't have multiple ways to do it or require heavy Csound knowledge if we can just solve the problem once and have it pre-built and ready. I'm also thinking of extending blueShare to be more of a community site. I'm not sure what will happen yet, but finding ways to make this a bigger community is of interest. Anyways, looking forward to getting this all going and of course will be excited to see what everyone does with blue! Thanks, steven |
|
From: Steven Yi <ste...@gm...> - 2009-09-28 16:35:12
|
Hi All, Just a status update, this weekend was a long one for blue but I was finally able to get the python interpreter working! It took a while as I was both trying to get the python library folder copying in the build system as well as upgrading to Jython 2.5.1 which required updating how Jython was called. Just a moment ago I was finally able to get it all working! The rest of my list of todo's has mostly minor features left, then a number of cosmetic issues (need to implement a few classes for Netbeans RCP). I'm hoping this week to get through the big issues to get to a point where I can work on the small issues while testing begins (hopefully can start this next week!!!) Thanks! steven |
|
From: Dave S. <da...@su...> - 2009-09-28 22:01:38
|
Exciting, looking forward to trying it out when you are ready! - Dave Steven Yi wrote: > Hi All, > > Just a status update, this weekend was a long one for blue but I was > finally able to get the python interpreter working! It took a while > as I was both trying to get the python library folder copying in the > build system as well as upgrading to Jython 2.5.1 which required > updating how Jython was called. Just a moment ago I was finally able > to get it all working! > > The rest of my list of todo's has mostly minor features left, then a > number of cosmetic issues (need to implement a few classes for > Netbeans RCP). I'm hoping this week to get through the big issues to > get to a point where I can work on the small issues while testing > begins (hopefully can start this next week!!!) > > Thanks! > steven |
|
From: Steven Yi <ste...@gm...> - 2009-12-09 03:17:27
|
Hi All! Just wanted to give you all a status note, blue's been on hold the past couple of weeks due to some out of town trips but Jim Hearon and I are finishing up work on the next issue of the Csound Journal. We're finishing up soon and I'll be back to finishing blue2 after that. Thanks for your patience! steven |
|
From: Steven Yi <ste...@gm...> - 2010-04-05 01:11:59
|
Hi All, Just wanted to give a heads up on status here. I'm happy to say that MIDI input has hit it's first milestone, getting MIDI input to generate Csound SCO notes to turn on/off instruments! I still have to work out some of the mappings for key and amplitude (i.e. using scala scales), but it's getting there. I have not yet figured out how I'm going to work out recording of notes into SoundObjects, but I am taking one step at a time. A note about the design: currently, I am going with forcing this format for note on: i<instrId>.<midiNoteNum> 0 -1 <pitch> <vel> where pitch and velocity go through mapping functions, and this format for note offs: i-<instrId>.<midiNoteNum> 0 0 >From my early test this works well, and if there are hung MIDI notes, the all notes off button works fine. I had originally spent a lot of time considering a generic format for notes, but I think really that it would be better to force a 5 pfield format as that is what matches MIDI's note-on convention. One can make instruments work for both MIDI-initiated notes from blue and with your own custom format by looking at pcount equal to 5 and doing realtime related code there, and then doing whatever else you might like otherwise. I'll have examples of this when 2.1 goes out the door. Otherwise, I am finding that the "r" opcodes that add a release time to be great and will probably migrate to using that for all ADSR-style envelopes in all of my work, as it makes sense whether working from MIDI or SCO I believe. One thing to note, I did see immediately that BSBDropdown is somewhat lacking in that it is not automatable considering it replaces content via string value. I think now what I will do is add an automatable flag that if used, will ignore the value part of the key/value and just use the index. This will help make things work for backwards compatibility and not require a new object (and should help get code migrated to make automatable easier). So, for example, if you have these key values set for BSBDropdown: sine/0 triangle/1 square/2 pulse/4 saw/8 if you set it automatable, instead of using the values on the right, the values would be one of [0,1,2,3,4] depending on what is selected. Does this sound like a good way to go? The reason for using index like this is that for it to be a k-rate signal, it has to be a number, which can't be guaranteed if using key/value. Also to note, for 2.1, I am targeting only working with MIDI note on/note offs. I will probably look at the audio track work for 2.2, and return to MIDI in 2.3 to consider MIDI controllers. This will give more time to consider the design for controllers and mapping. Thanks! steven |
|
From: Steven Yi <ste...@gm...> - 2012-02-05 17:13:42
|
Hi All, Just FYI, I'm wrapping up here in the States and am heading back to Ireland today. I'll be arriving Monday morning and am planning to hit the ground running on blue development. I've been busy with redoing the theme to make blue look more polished; this will take hopefully another week, maybe two, and I will cut a release after that. I'll be balancing my time with updating the documentation on the Wiki as well (many thanks to Wolf Peuker for his assistance with the Wiki!). I should have more time for blue development this semester, so am expecting to get through some bigger architecture changes I've been planning. Thanks! steven |
|
From: Steven Yi <ste...@gm...> - 2012-11-21 13:22:20
|
Hi all, Just wanted to let everyone knew I am working on replacing the text editor in blue with something more featureful. On thing I am planning on is a new autocompletion that will show the csound documentation for an opcode in a popup window.I have a prototype going for auto completion already,and hope to make some headway on the syntax coloring (requires writing some parsers). Other than that I found a bug we here automations were not correctly generating for time when the API is on and rendering from a time other than zero. I hope to have these things completed by early next week as I have workshop to give next Friday. Thanks! Steven |
|
From: Steven Yi <ste...@gm...> - 2013-01-29 11:10:28
|
Hi All, Just wanted to update you all on my latest. I've gotten to a good point with the Clojure SoundObject, creating a couple examples, and had to fix up some unexpected issues as well. The only thing left is to create a Clojure Console to hold a REPL, but I may delay that until the next release. My plans at the moment are to do some documentation for the ClojureObject, then try to knock out bugs from the bug tracker for the next few days. I'm looking at Friday for the next release. Thanks! steven |
|
From: Steven Yi <ste...@gm...> - 2013-07-15 16:01:52
|
Hi All, I've been a bit absent from blue development work for a while due to working on Csound6. We're doing a number of bug fixes from the 6.0 release but that's starting to slow down. I'm starting to work again on Blue now. My current plan is to do the next release to support Csound 6. I'm also rewriting the render services as part of this, and I hope to fix the Audition bug during this time. After that, I did some graphics test code and I am planning on rewriting the score timeline to use floating point rendering. This should make for a faster and nicer timeline, as well as better zooming. The floating point timeline changes will be done in parallel to the audio layers work. For those who've been waiting on new blue changes and bug fixes, apologies! I hope to get back on track very shortly. All best! steven |