kmatheussen / radium

A graphical music editor. A next generation tracker.
http://users.notam02.no/~kjetism/radium/
GNU General Public License v2.0
842 stars 36 forks source link

No way to make a continuous glissando #16

Closed StudioDotfiles closed 10 years ago

StudioDotfiles commented 11 years ago

Currently the glissando command inserts chromatic notes between two other notes, thus creating what Wikipedia calls a discrete glissando.

One of my favorite features of old school trackers was the ability to glide from note to note.

kmatheussen commented 11 years ago

Sounds like a good feature. But I don't see immediately how the interface should be...

On Tue, Sep 10, 2013 at 11:32 AM, StudioDotfiles notifications@github.comwrote:

Currently the glissando command inserts chromatic notes between two other notes, thus creating what Wikipedia calls a discrete glissando.

One of my favorite features of old school trackers was the ability to glide from note to note.

— Reply to this email directly or view it on GitHubhttps://github.com/kmatheussen/radium/issues/16 .

kmatheussen commented 11 years ago

Let me clarify. Everything is possible, but how should you a glissando between two notes look in the editor?

On Tue, Sep 10, 2013 at 11:42 AM, Kjetil Matheussen < k.s.matheussen@gmail.com> wrote:

Sounds like a good feature. But I don't see immediately how the interface should be...

On Tue, Sep 10, 2013 at 11:32 AM, StudioDotfiles <notifications@github.com

wrote:

Currently the glissando command inserts chromatic notes between two other notes, thus creating what Wikipedia calls a discrete glissando.

One of my favorite features of old school trackers was the ability to glide from note to note.

— Reply to this email directly or view it on GitHubhttps://github.com/kmatheussen/radium/issues/16 .

StudioDotfiles commented 11 years ago

I see a couple of possible ways of visualizing this, but not I'm not sure which is the best.

The common thread is very clear though: You should be able to define where the glide starts, which could be at the note start or after it, and define where it ends, but by default it should end at the start of the next note. Those should be the only settings.

That was the main thing that made the old school tracker way of doing glissandos so easy. In most music software you have to either: -Make a pitch bend, which is hard to end at the exact note you want, and has limited range. -Set your instrument's portamento time. That is only possible if the instrument supports it, and it's not easy reach the next note be at the exact time you want to.

As for the question how to visualize it, I see a couple of options: -You could use the FX automation UI. -You could make a separate lane for it, where one enters additional 'note articulation commands', as with other trackers. See http://www.milkytracker.org/docs/MilkyTracker.html#fxE3x -Maybe something else entirely, but keeping the same common thread: define the start and end, nothing else.

kmatheussen commented 11 years ago

Yes, this definitely sounds like something a normal tracker handles better. Perhaps a new separate lane should be introduced (which can easily be shown/hidden).

On Tue, Sep 10, 2013 at 12:54 PM, StudioDotfiles notifications@github.comwrote:

I see a couple of possible ways of visualizing this, but not I'm not sure which is the best.

The common thread is very clear though: You should be able to define where the glide starts, which could be at the note start or after it, and define where it ends, but by default it should end at the start of the next note. Those should be the only settings.

That was the main thing that made the old school tracker way of doing glissandos so easy. In most music software you have to either: -Make a pitch bend, which is hard to end at the exact note you want, and has limited range. -Set your instrument's portamento time. That is only possible if the instrument supports it, and it's not easy reach the next note be at the exact time you want to.

As for the question how to visualize it, I see a couple of options: -You could use the FX automation UI. -You could make a separate lane for it, where one enters additional 'note articulation commands', as with other trackers. See http://www.milkytracker.org/docs/MilkyTracker.html#fxE3x -Maybe something else entirely, but keeping the same common thread: define the start and end, nothing else.

— Reply to this email directly or view it on GitHubhttps://github.com/kmatheussen/radium/issues/16#issuecomment-24151216 .

kmatheussen commented 11 years ago

Well, there's room in the Fx area too. Think this should be quite simple.

On Tue, Sep 10, 2013 at 1:20 PM, Kjetil Matheussen <k.s.matheussen@gmail.com

wrote:

Yes, this definitely sounds like something a normal tracker handles better. Perhaps a new separate lane should be introduced (which can easily be shown/hidden).

On Tue, Sep 10, 2013 at 12:54 PM, StudioDotfiles <notifications@github.com

wrote:

I see a couple of possible ways of visualizing this, but not I'm not sure which is the best.

The common thread is very clear though: You should be able to define where the glide starts, which could be at the note start or after it, and define where it ends, but by default it should end at the start of the next note. Those should be the only settings.

That was the main thing that made the old school tracker way of doing glissandos so easy. In most music software you have to either: -Make a pitch bend, which is hard to end at the exact note you want, and has limited range. -Set your instrument's portamento time. That is only possible if the instrument supports it, and it's not easy reach the next note be at the exact time you want to.

As for the question how to visualize it, I see a couple of options: -You could use the FX automation UI. -You could make a separate lane for it, where one enters additional 'note articulation commands', as with other trackers. See http://www.milkytracker.org/docs/MilkyTracker.html#fxE3x -Maybe something else entirely, but keeping the same common thread: define the start and end, nothing else.

— Reply to this email directly or view it on GitHubhttps://github.com/kmatheussen/radium/issues/16#issuecomment-24151216 .

StudioDotfiles commented 11 years ago

This is actually the thing I miss most in radium. I hope you'll be able to add this!

I'm also really curious how the physical modeling instruments react to bends; should be possible to get some interesting sounds that way!

kmatheussen commented 10 years ago

Radium has pretty extensive possibilities to change the pitch of notes now. Press return to add pitch, or edit with the mouse. pitchchange