I started with standard Ubuntu, but then switched to Xubuntu pretty quickly -- din't really like the Unity desktop, and xfce is just fine with me. Finally bit the bullet with Jack last night (ditched pulseeaudio), and as of a little while ago, even got it going in realtime mode. So I'm pretty happy with the environment at this point. It helps that I started playing with Red Hat in 2000, used Fedora and CentOS full-time at my last job, and continue to deploy to CentOS in my current job, so I didn't have to go cold-turkey in a completely unfamiliar OS.

I hadn't considered using a PythonProcessor with PianoRoll; in fact I've never used PythonProcessor. I guess I don't tend to use note processors very much. I've found that I tend to forget about them after they're set because there's no visual indication of their presence except in the SoundObject Properties dialog, which I don't usually have visible. So yeah, I like to idea of pulling the NoteProcessors up into a less hidden part of the UI. I don't have any specific ideas on how that might work, but if I come up with some I'll certainly share them.

Anyway, using a PythonProcessor makes perfect sense in with a PianoRoll, it just had never occurred to me. Thanks for the info and the sample code! I still like the idea of being able to access the pfields as named tokens as in BSB code (e.g.: <p1>), but it's probably not worth the development effort since PythonProcessor should work really well. Can I assume the the code in the processors will execute in the same instance/namespace as PythonObjects on the timeline? I rely on this when I define constants and functions on one PythonObject which I then reference in other PythonObjects.

Thanks for the tip on switching between projects as a workaround instead on closing/reopening the project. I'll see if that helps the next time I experience the issue (assuming it isn't magically fixed in 2.3.2). And I will write up a bug for it. It's not just the buttons (mute, solo, ...) -- when the project gets into this state, it blocks other functionality in the label/control areas of the layers. For example, right-click menu is gone, and so is the ability to double-click to name the layer.

- Dave 


On Sun, Dec 16, 2012 at 12:23 PM, Steven Yi <stevenyi@gmail.com> wrote:
Hi Dave!

Glad you like the new editor, and glad you're enjoying Ubuntu as well!
 I've been meaning to make my Macbook dualboot to Xubuntu some time
but haven't gotten around to setting that up. I'm using Xubuntu now in
a VM for testing.

For the mute/solo problems, I have had this happen in 2.3.0 but I
thought I had fixed it in 2.3.1 with offloading onLoad of python
scripts to a separate thread.  It looks like this wasn't the root
cause of the problem.  My trouble with this is that the bug has been
intermittent and very difficult to consistently reproduce.  I've found
that I didn't have to close the project, but could just switch to
another one and come back for it to sort itself out.  I'll see if I
can do some more bug hunting on this one; if you would file a bug
though, that would help me out very much.

For the PianoRoll, have you considered using a Python NoteProcessor?
You should be able to use that to transform the generated notes from
the PianoRoll and essentially use it just as input data to your
functions.  (I've attached an example that uses the PianoRoll as a
source of pitch data and then generates random notes.)

Using the Python NoteProcessor code editor can be a bit of a pain to
keep going into the editor and back out to test.  I had been meaning
to modify NoteProcessors for some time to no longer use the property
editor but instead have their own user interfaces and make a rack-like
interface for them.  Perhaps this would be something worth planning
out for a new release. Even then, I'm not sure what the code editor
part should look like.  Would love to hear ideas at this point. :)
(Also, I had planned to make NoteProcessors have something like
BlueSynthBuilder, but where users can design their own processors,
does this sound of interest to anyone?)

Let me know what you think, and thanks as always for your music!

steven

p.s. - I hope you don't mind, I modified Palimpsest to fix a code
issue with newer Csounds and the # not being allowed for comments (it
was in the global score with the tempo statement).


On Sat, Dec 15, 2012 at 9:18 PM, Dave Seidel <dave.seidel@gmail.com> wrote:
> Hi Steven,
>
> I've been using blue on Ubuntu for a couple of months now (Windows laptop
> died, a good excuse to switch). I'm using Quantal Quetzal (12.10).
>
> It's generally working really well. I *really* like the new editor! It's a
> great improvement.
>
> An issue: I've had a number of times when I change the settings of solo/mute
> buttons in the timeline layers and they won't "take": i.e., no change to the
> CSD output generated either to screen or disk. When that happens, I have to
> close and reopen the project, then it's fine for a while. I don't have a
> particular set of actions that provokes it. It's happened in more than one
> project.
>
> And a feature request: I would love to be have a version of the PianoRoll
> that generates a line of Python code instead of a line of orchestra code
> (using the same templating you already have). The Python code would then be
> rendered just like a PythonObject. My process these days almost invariably
> involves writing a series of Python functions in one PythonObject that are
> called by other PythonObjects to generate orchestra code. It would be
> fantastic to be able to call those functions from with a PianoRoll.
>
> As always, thanks for all of your work and dedication.
>
> - Dave
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Bluemusic-users mailing list
> Bluemusic-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Bluemusic-users mailing list
Bluemusic-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluemusic-users