Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@Trancit wrote:
And one more:
Is there any option to set up, at which level the “Level Meter Overload” starts taking effect…
In my current settings, it starts at about -6db, but I would like to set it to about -1db or -0.5db…
I think -6db is definetely to soon to start turning the master level meter to deep red (yes I know I can change the color, but red is good for showing overloads, but overloads for me are more than 0db)Trancit
I assume you mean the default master output meters. If you click the meter in the mixer, you can toggle the RMS meter scale on/off. Alternatively you can configure the RMS scale in the arrangement properties dialog.
ZynewaveKeymaster@Trancit wrote:
How to bounce the individual outputs of an VSTi like in this tutorial:
http://www.zynewave.com/videos/Podianer/offlinebounce.html
There are no “group bounce tracks” anymore, aren´t they???
A lot of things have changed since that video was made. For a more recent video of how to work with multi-output bouncing, check this YouTube video:
ZynewaveKeymaster@LiquidProj3ct wrote:
Could you consider add it as an option in piano roll options window?
Perhaps in a future update. I think there are going to be plenty of changes in the 2.31 release, that I would like people to get used to before making further changes.
ZynewaveKeymaster@LiquidProj3ct wrote:
Not exactly, but I would use a lot that button turning it off when Podium is playing, saving time, so, please add it if you have a reason to preview notes while podium is playing.
I find the audition useful during playback, when trying to fit notes to the playing melody.
Siegfried pointed that preview of the note should start/restart when you create/move a new note, and it must last (sustain stage) until you release the mouse button (and sound would go to release stage). THis is very useful when you’re moving short (<1/32) and long (>1/1) notes looking for the best musical interval, but annoying if you don’t have it. Preview should work in the same way that piano roll’s keys. The time that preview note is sounding should depend only of mouse click, and it should be independent of event lenght.
Then when you move notes by dragging, the note would play continuously until you drop the note. I think that could be annoying to some.
The audition of the true note length can be useful, when you step through the notes in a sequence by using the arrow right key. The note length of especially short notes also can have a big impact on how the note will sound, so for short notes it is useful to have the true note length auditioned. For very long notes I agree that it can be annoying, but I think I will solve that for now by adding the audition on/off button to the editor.
ZynewaveKeymaster@LiquidProj3ct wrote:
Drumazon is a plugin that allow you use patterns OR simple drums. The different pitches (piano roll keys) acts as patterns OR simple drums.
You cannot change easily the drums names (you can use some black magic to do it, though) but it’s easy change the name of each pattern for each key (and move/copy them). I did this video for you. Notice if you have demo version you cannot use single drums, only patterns, but it will serve you.
http://www.youtube.com/watch?v=x-ws1mUj5lI
Very poor quality, I’m newbie doing videos 😳 If you need more clarifications feel free to ask
“hello frits”
Thanks. I’ll try the demo.
ZynewaveKeymasterBeta5 is up.
@LiquidProj3ct wrote:
– Is there any way to unmute and unsolo all keys? If there isn’t, please add one.
You can now do it by Shift+clicking the enable/solo/mute buttons, similar to how it’s done with the track solo/mute buttons.
@Zynewave wrote:
Can you confirm that, when used in other host software, the plugin will update the drum key names accordingly?
I can confirm you (with Drumazon/Nepheton) that FL Studio piano roll updates automatically each time you do a rename inside drumazon. Reaper piano roll updates when you re-open the piano roll, keeping the user names instead plugin keynames.
I had a quick look at Drumazon/Nepheton pdf manual, but could not see how you would change the note names. How do you do it?
Crash: Trying to open any Drum Roll made with previous Podium versions
Fixed. 😳
2. Ghost notes for drums are showed now in regular Piano Roll (and they shouldn’t)
Fixed.
ZynewaveKeymaster@thcilnnahoj wrote:
Addictive Drums also lets you re-map everything, and I assume it then passes the key names on to the host, if that’s what you mean by custom drum key names.
You mean you can reassign MIDI note numbers used for the individual drums in the plugin UI? Can you confirm that, when used in other host software, the plugin will update the drum key names accordingly?
Besides hiding unused keys, another feature dream would be being able to rearrange and rename the keys, and save them as a sort of drum map template.
You just described the drum kit preset feature :wink:. I’m going to revise this as well. I’m considering adding some commands to the new drum map editor menu button, for managing drum kit presets.
ZynewaveKeymaster@LiquidProj3ct wrote:
Thanks 🙂 I’d like to point that autocenter when opening an editor doesn’t work with Drum Roll
Are you sure? It works fine here.
If there are any selected events, they will be centered. If the selected events extend beyond the vertical space, then the topmost selected event is aligned to the top of the display. If there are no selected events, then all events within the displayed zoom range will be centered.
ZynewaveKeymasterBeta4:
• Added a “note enable mode” option button to the drum map editor. When the option is selected all drum keys show an enable/disable button. When the option is deselected, all disabled drum keys are hidden. This is useful for setting up a compact drum map with only the drum sounds you intend to use.
• Added a menu button to the drum map editor. The menu contains commands for enabling all GM drum keys or enabling only notes used on the track. There are also copy/paste commands for applying the enable/solo/mute states to other tracks.
• Added solo and mute buttons to each key in the drum map editor. The solo/mute state is applied to all sequences playing on the track.
Note that the new stuff is still not saved in the .pod file. The enable/solo/mute changes are also not added to the undo history yet. It’s a bit tricky, because the changes are applied to the tracks in the arrangement editor, but the edit action is done in the drum map editor. I think the undo should be done in the drum map editor, and not be listed in the arrangement editor undo history :-k.
I’m interested in your comments and suggestions.
ZynewaveKeymasterI can add a preview on/off button on the left side panel of the piano roll and drum map editors. Would that solve the problems?
ZynewaveKeymasterIn the piano roll editor:
Menu: View > Customize Region > Piano Roll
Disable the “audition selected and edited notes” option.
ZynewaveKeymasterBeta3 is up. Some bug fixes, and:
Added a vertical zoom slider to the drum map editor. This replaces the “line height” setting in the drum map region properties.
Tomorrow I’ll start experimenting with solo/mute.
May 27, 2010 at 21:49 in reply to: Why do electronic musicians keep using Logic and FL Studio? #18318ZynewaveKeymaster@tumult wrote:
http://www.propellerheads.se/reason5/index.cfm?fuseaction=get_article&article=blocks
Sound familiar?
Yes. It has already been discussed over in this topic:
http://www.zynewave.com/forum/viewtopic.php?t=2312&postdays=0&postorder=asc&start=15
ZynewaveKeymaster@thcilnnahoj wrote:
I must confess I’ve never used the drum editor before, so it’s entirely new to me.
Oh no!, I’m going to be flooded with bug reports the coming days! 😉
– Why are the “keys” arranged bottom to top compared to the piano roll?
You know, it made sense years ago when I implemented it :-k . I guess I was thinking that the most prominent drums (kick, snare, etc.) should be at the top when you first open the editor. If I implement a feature to hide unused drum lines, I think it’s ok to swap them around so low notes are at the bottom. If anyone objects to this, please post why.
– The grid/snap value seems to adjust all notes’ visual length – huh? A 1/16 note looks like a 1/4 note if you select that grid setting.
I don’t know how other sequencers’ drum maps work, but for me it’s important to be able to set note lenght (and see it). For example, Poise has a “note on” mode, in which a sample pad is triggered only as long as the note is held.All events are displayed with a minimum size of the grid value. There’s a historic reason for this: Years ago many MIDI drum files had very short note durations, because drum machines back then usually only needed a trigger note to play the entire drum sound. So if those ancient MIDI drum files should be displayed with true durations, you would only see very thin drum notes that would be difficult to click and edit.
Maybe this need to be updated as well. Instead of using the grid value as the minimum duration, it is perhaps better to have a minimum pixel width setting, and a way to display that the true length of the event is perhaps shorter than the clickable event. Suggestions are welcome.
ZynewaveKeymaster@Conquistador wrote:
@Zynewave wrote:
When I say they are properties of the track, then I mean they are just stored as hidden properties of the track object instead of the sequence object. They don’t interfere with normal track solo/mute. The difference is that when the drum map editor stores the note solo/mute states as track properties, then all sequences placed on that track will adopt the same solo/mute state. Like LiquidProj3ct, I prefer this behaviour.
That sounds like we are talking about the same thing…
“when the drum map editor stores the note solo/mute states as track properties, then all sequences placed on that track will adopt the same solo/mute state.”
I would definitely want a mute / solo command for a drum row to affect all MIDI sequences for that track but…if I then decide to Mute the Track (that holds the MIDI drum sequence/s ) that would override (so the drum lane would not interfere with the track mute) the drum row Mute track command, is that not what you are referring to here?
If not can you give me an example that explains / clarifies your suggestion?
A muted track will of course mute any soloed drum notes on that track.
In your original post you wrote:
@Conquistador wrote:
2. Using the Drum row Mute Solo buttons would solo or mute a single row within a drum MIDI event. So if I had snare and kick notes inside a MIDI event but then used the Kick row Mute button….
When you emphasized “within a drum MIDI event” I thought you suggested that the solo/mute should be local to only that clip, and other clips on the same track should not be affected. From your latest comments, I take it you didn’t mean that.