Trancit@Zynewave wrote:
@Trancit wrote:
Had that already posted in the support forum, but deleted there, because here is a better place:
For me adjusting velocities is much easier by seeing the current value with numbers…
In the editor we have this nice numeric window for “mouse cursor”…would it be much work to implement a numeric value for note velocity????
I’m sorry, but the velocity value readouts didn’t make it into this round of piano roll updates. I’ll save it for a future update. There have been a lot of changes to the piano roll in this release, so I think it is a good idea to let users work with what we have now, and then provide feedback based on their experience with the new editor.
No problem…it´s not a big issue 8)
Trancit
TrancitBut I think you are not a happy bunny about my idea, aren´t you?? 8)
Trancit
TrancitYes of course, it would solve to be able to store a “combined” preset, but it wouldn´t be almost as flexible as an Kore2 alternative and as I wrote before, I would love to see a tagging system instead of browsing folders and subfolders and up and down and…you know, what I mean 🙂
As well as stepping through my presets with a single mouseclick is for me, by far more luxury…
Trancit
Trancit@LiquidProj3ct wrote:
Maybe you want to mean this:
http://www.zynewave.com/forum/viewtopic.php?t=2035
It’s planned for Podium 6.42 as you can read in the thread 😆
No, that I don´t like to see…than I could use energyXT…
For me very important is that preset organizing thingy…with modularity I meant to be able to combine more than one plugin in a preset, not especially such a virtual wirering system…
Trancit
TrancitOk, i must say, that I don´t understand a single word …:-)
But if you plan to revise it, it doesn´t matter…
Perhaps you could think about that:
I personally wonder a lot, why quite clever plugins like NI Kore don´t get any competition…I don´t care about the controller, but the idea of the plugin is quite needful for people like me…
The idea to have one single plugin to reach all presets of any plugins categorized by the tag system is imho the easiest way to deal fairly with the tons of presets, modern plugins offer these days as well as it´s advantages for sounddesign…
Steinberg tried something like this with their mediabay, but its only half done and only work for one single plugin at a time…as well as Wusik VM, which uses also folders and subfolders instead of tagging and remember the browser of Omnisphere…
Back to Podium:
You would like to revise the preset library system, Podium doesn´t support midi plugins at the moment, energyXT doesn´t offer any tagging or categorizing and Kore is quite heavy on Ram load and overbloated by its controller editing and automating system (not to mention, that it is quite expensive), Abletons Lives Rack system is internal as well as Reasons Combinator (the mother of that all, beside energyXT as a plugin)…
So why not taking the best of every world…instead of “only” changing the library preset thingy from track to plugin based, go one step ahead and built up a little lightweighted “mini subhost”, that offers preset tagging, combining midi plugins, instruments and effects (all vst based, no need for internal FX like Kore has) in one preset to be able to save stacked, arpeggiated or fx tweaked sounds in one single file and steppin through a user based preset library by a single mouseclick on a preset name, without any need of navigating up and down through zillions of folders and sub folders, which simulate a poor tagging system…
I don´t know how other people work, but for me, I often got lost in the preset jungle and wish a good and light solution to handle this disaster from a universal platform…
I think the idea of the Kore plugin (again, without the controller) is completely right…to think in terms of sounds you need and not in plugins…
Please think a little about this…it would solve some issues with Podium, would add a lot of comfort in preset browsing and sounddesign and would even add somewhat of modularity to podium…major selling points for energyXT and MuLab….
Trancit
Trancit@Zynewave wrote:
Do others think it is important that you have timing and velocity adjustments in a single dialog?
I would prefer it in a single dialog…
TrancitBecause you were working already to improve the Pianoroll editor:
What´s for me very long-winded to do is editing velocities…(again 🙂 )…
What about expanding the “Adjust timing” dialog with parameters for velocity, where you can change the velocities of the selection (or all) on a fixed value, random values, adding/substracting a certain amount or perhaps “compress/ expand” the velocity “dynamic”…
That would turn the existing “Adjust timing” dialog not only into a full featured “Humanizing” dialog, but would add on an easy way a very powerfull velocity tool rather than editing every velocity handle by mouse, especially because of the lack of a line tool to draw ….
What do you think of that??? I would find this quite handy…
Trancit
TrancitI think, it would be nice to be able to have something like a minimize view, with only the meter and the volume fader visible…
By working at larger projects it would give an better overview…
And of course, to be able to define a mixer profile as a multitrack mixer view…
Trancit
TrancitHad that already posted in the support forum, but deleted there, because here is a better place:
For me adjusting velocities is much easier by seeing the current value with numbers…
In the editor we have this nice numeric window for “mouse cursor”…would it be much work to implement a numeric value for note velocity????
This would be a big helper…
Trancit
TrancitOK, thx
TrancitThank you very much for implementing my FR so fast…and for me it´s working well.
If I name notes in the pianoroll, I would suggest, if I swith to the drum map, that this would reflect the name changes as well…I think those two should interact and it would be nice, if you could figure this out…
The Drum map isn´t named correctly in the View menu…it only shows two times “Timeline”
If I am too fast, please forgive me… 8)
Trancit
TrancitNo need for a seperate setting here…if you would change it to 100 8)
Trancit
Trancit@Zynewave wrote:
Another idea I’m considering:
The piano roll and drum map regions share a lot of functionality, so I’m considering removing the drum map region completely, and instead make the “piano roll” region into a “note” region, which will combine the two regions into one. Some of the latest updates to the piano roll have not made it into the drum map editor, and so combining them will ensure that the event editing is similar in both the piano roll and drum map mode.
So, instead of selecting between the “piano roll” and “drum map” editor profiles, there will be one profile, and you then have a “enable drum map” option in the menu button (as introduced in the new drum map region), which will toggle between the piano roll and drum map layout.
Good/bad idea?
For me, it´s of course a good idea…this would be the “Reaper” way 🙂
Trancit
Trancit@Zynewave wrote:
@Trancit wrote:
A very elegant way I think, is the integration in the piano roll editor and to be able to switch via the “View” menu between the classic piano roll and the drum editor…the best integration at the moment is in Reaper, imho.
Is there anything in Reapers drum map handling that you prefer over the changes I’m currently making? If you want Podium to improve, you’ll need to give me some more details.
The first parts, of what Reaper does quite well are already explained by the added pictures of my “helpers” :-)…
In the same editor you can choose between the shapes of the events and by the “view” menu, which editor you like to use, while “named notes” together with Diamonds shape the matching part to an conventionell drum editor is…for me it is easier, if I don´t have to define before, if this track is now a drum track or not
For me the most important thing is:
(you´ve already told, that you like this 🙂 )You can even in the normal piano roll just right doubleclicking a note on the onscreen keyboard and enter a name for it, like Kick, OHH or so on…and can build drummaps on the fly (all this works in the named notes view as well) and one of my highlights:
You can save these named notes as a simple textfile and re import any time later…
Next thing is the “Hide unused note rows” and “Hide unused and unnamed note rows”…both very usefull
One more: Velocity handles on the events
@LiquidProj3ct wrote:
About Reaper “drum roll”: I don’t like it. The different view settings you use are for each clip and that’s messy, not per track. Triangles and diamonds seems cheesy and antiquated, you cannot define note lenght and they’re difficult to click, and you couldn’t use the change of height that Podium do to different velocities. The velocity for each drum is a little uncomfortable when you want to tweak quicky timmings and velocities. I love Podium approach instead: You select notes and you can change its velocity (and only it’s velocity if you have “Edit only selected event” button on.
That you cannot change the note length is the trick, if working on drumnotes…mostly you don´t want to change them and with these different shapes you don´t have to care about this…
But I have to say, that different shape events are for me not important…
The three main features I like to work with:
1. To be able to work in one editor on different “types” drums and “normal ones” just by switching the view.
2. Naming notes directly in the editor
3. To be able to hide unwanted rows
Trancit
Trancit@Zynewave wrote:
Beta7:
Some UI adjustments and bug fixes.
The drum map enable/solo/mute is now added to the undo history.
The note audition will stop when the mouse is released.
I’ve given the drum kit preset feature some thought:
I developed the current drum kit preset feature many years ago, back when the focus was external MIDI modules and their proprietary ways of handling drums. Fortunately it has become much easier to work with drum plugins. I think it is time to retire the drum kit preset feature completely, and implement a simpler solution for reordering and renaming drum keys in the drum map editor.
Instead of having the drum maps in the project file, the drum maps could be stored in the global setup. One solution could be to include all drum maps in the Podium.ini file, but this means you would lose all the drum maps if you select the “restore default setup” command. A more advanced solution could be to have each drum map as a separate .ini file in a new “Drum Maps” folder, similar to how the color setup files are handled.
The drum map editor menu will then have a submenu for selecting between the drum map files found, along with commands such as “create new drum map” etc.
Comments?
A very elegant way I think, is the integration in the piano roll editor and to be able to switch via the “View” menu between the classic piano roll and the drum editor…the best integration at the moment is in Reaper, imho.
To be able to store the drum maps as seperate ini files is very wellcome here, too.
Trancit
Trancit