v4: Midi

[caseyjames]

gulp...

[schwa]

There is at least one major MIDI feature in the works for v4.

[zappadave]

Groove Quantize?
Score Editor?
Both?

[Eyes]

Is there any way to have the piano roll view automatically show other midi events in the same piano roll (as in other tracks midi in the same editor, similar to Pro Tools and Sonar)?

I can't see any notes of changes to this sort of behavior so just wondering if anything has been changed or is planned? Thanks.

[Jae.Thomas]

Originally Posted by zappadave

Groove Quantize?=

would be nice (I started the FR about it, a long time ago) however, I am not sure I would call this a major feature. It's MAJORLY wanted, but from a non-coders perspective, it's not something that seems like will change the face of things too much.

Originally Posted by zappadave

Score Editor?

now although this is in less demand, would be a MAJOR feature simply due to the undertaking in development that would be required - imo - and also the support of such a feature.

[pbognar]

Originally Posted by Jason Brian Merrill

would be nice (I started the FR about it, a long time ago) however, I am not sure I would call this a major feature. It's MAJORLY wanted, but from a non-coders perspective, it's not something that seems like will change the face of things too much.


now although this is in less demand, would be a MAJOR feature simply due to the undertaking in development that would be required - imo - and also the support of such a feature.

<broken record mode = "ON">

Whenever the "N" word is used, REAPER users (those who don't need or want it) jump to the conclusion that what some of us would like is a full blown engraving quality program built into REAPER.

Not even close.

I just want to be able to enter or edit MIDI note data on a staff view please. If I want to print, I'll gladly send the MIDI data over to a dedicated notation program.

As for exporting to another program just to edit the MIDI note data - what a major workflow buzz kill. Not only that, you'd be messing with the data in a vacuum - it would be nice to see the notes in the context of the track view and the audio tracks.

<broken record mode = "OFF">

[LFO]

Ok, so at the risk of sounding disappointed...

I've played with v4 MIDI and I am underwhelmed. Perhaps I was living in fantasy land based on all the FRs that I've been supporting. I really thought we would see some major changes and improvements to the MIDI editor. Maybe Cockos just hasn't implemented it yet in the alpha code, I've no clue. I sure do hope so.

MIDI tabs or just being able to select multiple MIDI tracks (ala DP) would have been a very welcome addition. Smoother CC data editing (ala FL) would have been terrific. The list goes on and on.

I guess the audio side has to be the priority, but dang it us MIDI folks need love too! Lol!

Don't get me wrong, MIDI is perfectly functional for me currently. I can get done what I need to do. It just isn't as convenient or fast as with competing products.

What do you guys think? Am I whining? I hope not! Just want to voice that the lack of a significant MIDI editor is missed by at least one MIDI head.

-Kevin

[jens]

Originally Posted by pbognar

As for exporting to another program just to edit the MIDI note data - what a major workflow buzz kill.

as I already mentioned you can open the MIDI-items via secondary-editor (by action) - so there's not need to export them at all... just saying.

[pbognar]

Originally Posted by schwa

There is at least one major MIDI feature in the works for v4.

<holding on to shorts>

[dub3000]

my gut feeling is it's NOT going to be notation, but it is very likely something to do with OSC.

[pbognar]

Originally Posted by dub3000

my gut feeling is it's NOT going to be notation, but it is very likely something to do with OSC.

Still holding out hope for basic staff editor (no printing)...

What is OSC?

[dub3000]

Originally Posted by pbognar

Still holding out hope for basic staff editor (no printing)...

What is OSC?

i reaaally think notation just isn't going to show up. there are ways around this with third-party tools though, apparently.

OSC is open sound control - like a next-generation MIDI and control standard, can operate over network/wifi. think: iPad control of reaper, crazy sound controllers. devs have gone on record as saying it'll show up in v4 somewhere and that a lot of the midi improvements will depend on how they implement OSC.

[mabian]

My bet is for some kind of logical editor... and possibly for in project ghosts (which wouldn't be huge in itself but pretty major for my workflow).

- Mario

[EvilDragon]

In-project ghosts! All items in the same take line considered as one überitem, visible at once in MIDI editor (think Sonar)! No more blocky CC editing! Proper drum maps! Logical editor! Better and smoother mouse behavior (see FL)! etc. etc. etc.

[hopi]

Originally Posted by schwa

There is at least one major MIDI feature in the works for v4.

OK great... any more hints?

[Amazed]

Is the Pitch Lane in Midi Editor Redundant?

[Amazed]

The names for Lanes in the Midi Editor appear to be hard coded? Shouldn't they come from the current note names file?

[gofer]

Originally Posted by Amazed

Is the Pitch Lane in Midi Editor Redundant?

No, it lets you edit MIDI pitch bend events. That's the same message which is sent by a pitch bend wheel.

Originally Posted by Amazed

The names for Lanes in the Midi Editor appear to be hard coded? Shouldn't they come from the current note names file?

Absolutely. There is a FR ticket for friendly MIDI CC names in the tracker which is asking for exactly this. I hope this will be implemented at some point. Would help heaps with many instruments which don't follow the GM specifications.

[pc999]

1+ to ghost notes/items

+++ Also one thing I would like is that when I am working in a "midi track" in a specific item around , lets say, C5 and proceed to a new item it would open in the same notes, ie around C5 and not C2, and when you go back to the previous item to make some improvements it would open again around C5.


+++++++ And what I would really like is that one didn't need to keep opening new midi editor windows, it would just go forth or back
________
HEADSHOPS

[pbognar]

Originally Posted by hopi

OK great... any more hints?

Now what fun would that be? You've got to believe that they would want a stable foundation upon which to hang that MAJOR MIDI FUNCTIONALITY.

[MatticusFinch]

Originally Posted by pbognar

Now what fun would that be? You've got to believe that they would want a stable foundation upon which to hang that MAJOR MIDI FUNCTIONALITY.

fair enough but i dont want to see any more complaining about people saying "im dissapointed not to see X feature in v4." "Its just an Alpha, more features will show up so STFU" is not really valid when some features are announced and others are deliberately not.

[hopi]

chiming in... but the big question remains: ARE those really the notes you intended to paint?

Personally that is why I can't use paint in any real manner...

[lowellben]

Originally Posted by schwa

There is at least one major MIDI feature in the works for v4.

I can't wait to hear what it is

[Subz]

Originally Posted by lowellben

I can't wait to hear what it is

+1 & Some

[Juca]

I wish the standard MIDI time be implemented in REAPER Event List.
Now, we have the two digit representation of notes position/duration. So, we put a note at 3.2.34, being the last two digits the tempo subdivision representation.
However, the MIDI standard representation should be 3.2.345 by exemple, with a 3 digits number. As REAPER can work with a resolution of 960 ticks per quarter note selectable at REAPER Preferences/Media/MIDI (a 3 digits number), would be possible put a note in that position or make it sound for 345 ticks.
By other side, all the other DAW programs use the standard 3 digits representation, so this is also a standard in the market.
I don't know how REAPER internally treat this and how this can affect the timming perfection in a project, because when we inform to the program that the note is at 3.2.34 this could be anything between 3.2.340 to 3.2.349, with 10 levels of losted information at each digit change (from 340 to 341, in this example).
I prefer the standard 3 digits system.
Greetings.

[gofer]

@Juca:
That has been implemented in one of the later 3.x versions. In MIDI editor's Options menu you find "Time format for ruler/transport/event properties" Pick "Measures.Beats.MIDI_ticks".
Funny enough, I was one of those who advertised for ticks, but now use 100ths, because I find it way easier to deal with. Of course I'm glad it's there anyway.

[captain caveman]

Originally Posted by schwa

There is at least one major MIDI feature in the works for v4.

*cough*

[lowellben]

Originally Posted by schwa

There is at least one major MIDI feature in the works for v4.

Any word as to what the "major" MIDI update/feature is?
Perhaps several features?

I can't wait!

[bennisixx]

Originally Posted by lowellben

Any word as to what the "major" MIDI update/feature is?
Perhaps several features?

I can't wait!

last alpha on the 26th, must be big(or a beta), its probably on the next alpha




of course I am full of hot air

[mirceablue]

Let's try to do some aggressive lobby for this future.It should be implemented before final V4 is out.

[hopi]

please vote for this midi action if yer heart says it right!

http://forum.cockos.com/project.php?issueid=3209

If you have not followed the thread for Arpeggios, etc. take a look, the link in in the voting thread.

if you don't understand why... do ask...

[typewriter]

I don't think this is possible yet:

It would be nice to be able to set the colours of the Keyboard in the midi Editor (and on the virtual keyboard).

By that be could mark the keyswitches of sample instruments or mark the playing range of a sample instrument.

This would be very useful for any kind of orchestral work.

[Mike Stop Continues]

Originally Posted by typewriter

I don't think this is possible yet:

It would be nice to be able to set the colours of the Keyboard in the midi Editor (and on the virtual keyboard).

By that be could mark the keyswitches of sample instruments or mark the playing range of a sample instrument.

This would be very useful for any kind of orchestral work.

yes, theme colors for that would be amazing.

And snap-to-scale stuff too (but that's outside the realm of walter...)

[gofer]

Piano Key colors would be nice, but I think that wouldn't be a Walter job either. They should be loaded together with note name files. Maybe simply a number 1,2 or 3 possible in each line in the note name file which would call the approriate color tint from the theme color list in the preferences could do the job.

For plugins which report note names themselves it must be possible to load a list of customized key colors without destroying the existing names, of course.

At the moment I make the playable range obvious by giving those keys their pitch names, keyswitch keys get friendly names and all unused keys get no name. As this actually works pretty good I'd find friendly CC names and friendly channel names more urgent (should also best be integrated with note name files, if possible)

EDIT: Just now I thought of another nice use for key colors: It would surely help me to color code drum kit pieces, eg kick keys a color, hihat keys another, similar but yet different colors for the different cymbales... that'd be helful, as my eyes sure don't get better

Maybe we should move this discussion branch into the MIDI thread? - Yep, done that. Ladies and gentle people, may I introduce: Post #379, #385 and #386 which are all immigrants from the Walter thread.

[Eyes]

Originally Posted by gofer

Piano Key colors would be nice, but I think that wouldn't be a Walter job either. They should be loaded together with note name files. Maybe simply a number 1,2 or 3 possible in each line in the note name file which would call the approriate color tint from the theme color list in the preferences could do the job.

+1 this is a brilliant idea.

It could just be a text file that specifies note name and colour. If it had the option for specifying other metadata that could be useful, like if its a note or keyswitch and Reaper can display differently depending.

-----------------------------------------------------

::Midi Keymap::
::Plugin: Battery 3
::Creator: Native Instruments::
:
:
Define Keyswitch; Bold;
:
:
C0; Keyswitch; Flam; 141312
:
C1; Note; Kick; 12a714;
C2; Note; Clap; 12a316;

-------------------------------------------------------

And so forth. All it would need to do is recognize a text file and react based on that. It would be like super drum maps.

[gofer]

Just in case you're not aware, we already have note name textfile support. It's just that they are only defining a name per pitch as of now.

Your example with full color code numbers would of course be most versatile, but a bit tedious to set up. I was thinking simpler:
Have say 8 Piano Key Color tint selectors plus a fill mode selection thingie (like those for marquee and time selection) in Preference -> Theme Editor color list. Then in the Note name file it would look something like

36	C1 Kick         1
37	C# Sidestick    2
38	D Snare Right   2
39	D# Snare Left   2
40	E RimShot       2
41	F Low Tom       3
42	F# HH Closed    4
43	G Low Tom       3
44	G# HH Pedal     4
45	A Mid Tom       3
46	A# HH Open      4
47	B Mid Tom       3
48	C4 Hi Tom       3
49	C# CrashA       5

where the last number calls the associated color from the theme editor list.

That way all note name files could have common coloring and are influenced by the theme. If you don't fancy the blue, go to the theme editor and change it for all note name files instead of dealing with the color number code in multiple files.

EDIT: These numbers could also be used for a "reorder pitches by Key Color" option, which would automagically bring all your kicks/toms/hihats/snares/etc to adjacent rows, that'd be an evergreen request fulfilled /edit

I love your the idea to have variables and influence on the font style. Left that out in my example, but would sure be cool.

Lots of stuff could be packed into a consolidated MIDI definition file, like CC friendly names, Channel friendly names (which implies one big consolidated list for up to 16 channels, or do we have that already?), pitch mapping (to reorder pitches, mostly to remap drum keys), Bank/Patch lists...