Topic: Preview 2.10: Scales and stuff

This topic has 25 replies, 10 voices, and was last updated 15 years, 2 months ago by LiquidProj3ct.

Viewing 11 posts - 16 through 26 (of 26 total)

← 1 2

February 26, 2009 at 09:35 #14612

Zynewave
Keymaster

@Pigini wrote:

@Zynewave wrote:

@adlaius wrote:

I have two requests that are almost certainly too far afield, but hey, why not? First, Hermode Tuning would be awesome. Some (few) instruments have it already, but Logic is the only sequencer (thus far) to offer it. Huge, fantastic feature, and offering it in a DAW vs. a VSTi gives added advantages (offline processing for bouncing to perfect harmonic tuning).

Also, what about native microtonal support a la Scala? A good number of popular synths (Albino, Alpha, Cameleon5000, Dimension Pro, z3ta+, and others) can load Scala tuning files; having host support would be really great.

Hermode tuning and microtonality need to be supported by the instrument plugin. MIDI notes sent from the host are integer numbers representing keys, so the host cannot adjust these for different tunings. I don’t know how Logic implements this. Perhaps it just works with their own instruments, or maybe there is something in the OSX AudioUnit plugin protocol that supports tuning setup from the host.

The universal way of using nonstandard tunings works with pitchbend events, if I remember correctly.

Pitchbend messages apply to all notes/chords playing on a MIDI channel, so it won’t work for adjusting the tuning of individual notes.

February 26, 2009 at 09:41 #14613

Zynewave
Keymaster

@Pigini wrote:

@Zynewave wrote:

Any other uses for scales?

Yes, lots. What level of depth are you planning on?
A programmable variations generator, a master editor?

Thanks for the suggestions, but I’m afraid that is going to take a huge amount of time to implement. For this release I’ll settle with using scales as a visual guide in the piano roll.

February 26, 2009 at 10:47 #14614

Pigini
Participant

@Zynewave wrote:

@Pigini wrote:

The universal way of using nonstandard tunings works with pitchbend events, if I remember correctly.

Pitchbend messages apply to all notes/chords playing on a MIDI channel, so it won’t work for adjusting the tuning of individual notes.

Yes, it has its limitations. Maybe they could be overcome by having kind of a mapped virtual midi driver system working internally. Anything that would allow to get pitch tuned polyphony up.

from http://xenia.media.mit.edu/~bdenckla/thesis/texts/htthe/node55.html:
“In order to use the pitch bend tuning technique, simultaneous notes that require distinct pitch bends must be played on different channels. This limits the polyphony to 16 notes in the worst case. Larger polyphony can be accommodated if some of the simultaneously sounding notes are separated by a doubling since these notes can be played on the same channel.”

But maybe the compexity of the subject calls for more specialized software, like thatone:
http://www.justonic.com/
(btw, makes an interesting read about the whole tuning stuff)

February 26, 2009 at 15:59 #14615

thcilnnahoj
Participant

It’s all great so far… the only exception being scale highlighting. It gets awfully cluttered when used together with black key highlighting.
Unfortunately, I have no suggestions for improvement to offer right now, other than just don’t use both options at once. 😕

February 26, 2009 at 22:46 #14619

H-man
Participant

@thcilnnahoj wrote:

It’s all great so far… the only exception being scale highlighting. It gets awfully cluttered when used together with black key highlighting.
Unfortunately, I have no suggestions for improvement to offer right now, other than just don’t use both options at once. 😕

What about being able to choose a colour for the scale?

March 2, 2009 at 21:00 #14629

xis23
Participant

Yeaaah good idea Fritz….. I used to just make a midi track with the relevant notes on and repetitively paste it on a track so the notes would appear grey in the background. This feature will help a lot so I don’t have to do that anymore!

March 3, 2009 at 00:37 #14632

Zynewave
Keymaster

Beta3 is up.

I’ve added a “scale name” text field to the tempo event properties dialog. This enables you to e.g. shorten the default “A Minor” to “Am”, or to select custom scale and set up an exotic scale with the proper name (for example “C Mela Dhirasankarabharana” 😮 ).

March 4, 2009 at 03:39 #14638

Zynewave
Keymaster

@LiquidProj3ct wrote:

A small bug. When editor snap mode is set to “start of grid unit under cursor”, if you drag a note foward it works nice, but if you drag a note backward it’s weird, the note goes backward before you reach the gridline with mouse cursor.

This picture was taken when I had the mouse where I point with a red dot:

Thanks. This is now fixed in beta4.

Also in beta4, when using the “start of grid unit under cursor” option, dragging the end of sequence or note events will snap upwards to the next gridline instead of downwards. This makes it behave more as a pasting action.

March 4, 2009 at 06:48 #14639

LiquidProj3ct
Participant

@Zynewave wrote:

Also in beta4, when using the “start of grid unit under cursor” option, dragging the end of sequence or note events will snap upwards to the next gridline instead of downwards. This makes it behave more as a pasting action.

Yes that’s a good idea too!! thanks!

edit: A small improvement. When reproducing Podium shouldn’t preview the notes (add,move) in piano roll, only when it’s stopped. It’s confussing when you’re writting/modifing a melody in play mode.

March 4, 2009 at 10:47 #14643

Conquistador
Participant

@Zynewave wrote:

Beta1 changelog:

Context help for the UI control under the mouse cursor can now be shown in a docked help panel below the inspector panel or the list panel. The help panel can be toggled with the “Docked help” option in the help menu.

Looks very slick. Thanks.

Added “editor mouse snap mode” setting to the Preferences dialog. Options are “grid line closest to cursor” and “start of grid unit under cursor”.

Nice response to recent feedback.

Creating a new plugin parameter track from the inspector parameter panel or the track context menu, will also create a curve sequence on the track. The current plugin parameter value is set as the starting point in the curve sequence.

That should make things even easier.

Added “drum map region properties” shortcut to the drum map right-click menu.

Much needed IMO thanks. Drum map usage can still be simplified. It’s quite a sparse aspect of Podium compared to others IMO. It really does need some further refinement badly.

Added “bypass processing when detecting CPU overload” option to preferences. Disabling this option can result in smoother playback, but with a more sluggish UI when CPU overload occurs

IMO one of *the* biggest single additions to Podium ever. Thankfully it will be off (to take advantage of it) by default.

March 4, 2009 at 11:40 #14645

LiquidProj3ct
Participant

@Conquistador wrote:

Much needed IMO thanks. Drum map usage can still be simplified. It’s quite a sparse aspect of Podium compared to others IMO. It really does need some further refinement badly.

I cannot stress it enought: Drum maps in Podium is a pain compared with our outstanding piano roll. It needs a serious revision.

Viewing 11 posts - 16 through 26 (of 26 total)

← 1 2

You must be logged in to reply to this topic.