Topic: Preview 2.27: Adjust timing

Viewing 15 posts - 16 through 30 (of 75 total)
1 2 3 4 5
  • March 2, 2010 at 18:22 #17606
    LiquidProj3ct
    Participant

    No man 🙂

    I don’t know what is “Quantize within range”, it seems a sensivity, and it seems that 100 is maximum sensivity. I understand the randomize start, and Swing, and preview.

    Now is where I’m confused. Quantize duration and set duration, what is the difference? They seems to work in the same way.

    The notes, when I quantize start, always move to the left, when the right grid line is closer even, same with end and duration. I’m used to FL Studio quantizer which quantize to the nearest quantize point (left or right).

    Anyway when I change the comboboxes it seems that the quantizer doesn’t work anymore (bug?) that was the reason because I was really confused.

    Best regards

    March 2, 2010 at 18:51 #17607
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    I don’t know what is “Quantize within range”, it seems a sensivity, and it seems that 100 is maximum sensivity.

    Yes, it is a sensitivity. Maybe a name change can improve this. What about “Sensitivity min/max” or “Magnetic range min/max”?

    Now is where I’m confused. Quantize duration and set duration, what is the difference? They seems to work in the same way.

    Quantize duration adjusts towards the nearest quantized duration. Set duration adjusts towards a duration of the grid note value. If the duration of all your events are within one grid unit, then you won’t see a difference between the two. Anyone has a better naming for the “Set duration” option?

    The notes, when I quantize start, always move to the left, when the right grid line is closer even, same with end and duration. I’m used to FL Studio quantizer which quantize to the nearest quantize point (left or right).

    It does quantize towards the nearest grid line. There may be a problem if your sequence doesn’t start on a bar, because I haven’t yet made it sensitive to bar positions.

    Anyway when I change the comboboxes it seems that the quantizer doesn’t work anymore (bug?) that was the reason because I was really confused.

    Works fine here. What are you changing?

    March 2, 2010 at 19:23 #17608
    LiquidProj3ct
    Participant

    @Zynewave wrote:

    Yes, it is a sensitivity. Maybe a name change can improve this. What about “Sensitivity min/max” or “Magnetic range min/max”?

    Much better, until read that I was thinking that the knobs were Sensitivity for start time” and “Sensitivity for end time”. But if their values are inverted (as example min:100 and max:0) I get the same results.

    Quantize duration adjusts towards the nearest quantized duration. Set duration adjusts towards a duration of the grid note value. If the duration of all your events are within one grid unit, then you won’t see a difference between the two. Anyone has a better naming for the “Set duration” option?

    Thanks, I understand now 🙂

    It does quantize towards the nearest grid line. There may be a problem if your sequence doesn’t start on a bar, because I haven’t yet made it sensitive to bar positions.

    I tried in these events and they are displaced to the left (the first note!) and the snap is 1/16. I’ll wait to next betas

    Anyway when I change the comboboxes it seems that the quantizer doesn’t work anymore (bug?) that was the reason because I was really confused.

    Works fine here. What are you changing?[/quote][/quote]

    Uhm… I don’t know how replicate now, probabily the problem was the confusion with sensitivities, if I find something weird I’ll tell you

    Best regards

    March 2, 2010 at 21:04 #17610
    thcilnnahoj
    Participant

    @Zynewave wrote:

    @michi_mak wrote:

    this window looks very promising – maybe it lacks an entry for adjusting velocities?

    I considered a single big dialog with controls for adjusting all note event properties, like velocity and transpostion. There would then be similar dialogs for sound events and automation point events, with controls for adjusting fade curve etc. I felt the dialogs became too big, so I decided to split out all timing related adjustments into this dialog. In a later release I’ll add the adjust dialogs for the other event properties, including velocity.

    Have you considered still putting all (future) event properties in one dialog, but one using tabs?
    It might just be a little quicker and more comfortable if you want to adjust note quantize values, velocities, and maybe other things in one go, compared to closing and opening multiple dialogs.

    March 3, 2010 at 03:02 #17613
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    @Zynewave wrote:

    @michi_mak wrote:

    this window looks very promising – maybe it lacks an entry for adjusting velocities?

    I considered a single big dialog with controls for adjusting all note event properties, like velocity and transpostion. There would then be similar dialogs for sound events and automation point events, with controls for adjusting fade curve etc. I felt the dialogs became too big, so I decided to split out all timing related adjustments into this dialog. In a later release I’ll add the adjust dialogs for the other event properties, including velocity.

    Have you considered still putting all (future) event properties in one dialog, but one using tabs?
    It might just be a little quicker and more comfortable if you want to adjust note quantize values, velocities, and maybe other things in one go, compared to closing and opening multiple dialogs.

    Yes, that may be a solution. But it’s a bit into the future. After this adjust timing dialog, I’ll return to my previous development schedule.

    March 3, 2010 at 03:04 #17614
    Zynewave
    Keymaster

    Beta2 is up. There are some refinements to the dialog, and bar positions are now quantized correctly.

    March 3, 2010 at 07:14 #17616
    LiquidProj3ct
    Participant

    Frits I’ve emailed you a project with a swing bug

    March 3, 2010 at 16:53 #17619
    Merkury
    Participant

    << I had a look at the documentation for some of the other major hosts, and they all seem to support an "undo quantize" type of command. That means that all events are stored with both the original recorded time, and the last quantized time. That feature will make this release take a bit longer than I anticipated when I started, but I can see the benefit of always having the option to go back to the recorded timing, if you later on regret changes you've made with the adjust timing dialog. Anyone have an opinion on this?>>

    Ok i ‘ve just tried the beta,works great by now. I’ve tried on a beat and it does EXACTLY what expected ! And seems capable of doing even more,which is great.
    And i love the fact that the quantization options are really advanced,some other DAWS seems to be afraid of givin’the user too many options .[/quote]

    March 4, 2010 at 02:18 #17620
    Lion
    Participant

    Have you considered doing this non-destructively?

    I have not tried the beta yet, but this is a feature I really love about Reason. It’s not a definite ‘Must-Have’ feature, but it IS a desirable one.

    March 5, 2010 at 19:46 #17623
    Zynewave
    Keymaster

    @Lion wrote:

    Have you considered doing this non-destructively?

    I have not tried the beta yet, but this is a feature I really love about Reason. It’s not a definite ‘Must-Have’ feature, but it IS a desirable one.

    The final 2.27 release will save any timing adjustments made to each event in the project, so that you at any time can revert back to the original timing. That’s sort of semi-destructive I guess. If you mean a way to set up quantization or swing to be applied only during playback, then that is not something I have planned.

    March 5, 2010 at 20:05 #17624
    Lion
    Participant

    @Zynewave wrote:

    If you mean a way to set up quantization or swing to be applied only during playback, then that is not something I have planned.

    Thats exactly what I mean. The ReGroove Mixer in Reason4 does this. Where as, it applies the groove (basically midi, in a proprietary extension) to the track without actually altering the midi notes. (while the destructive option is still available)

    March 5, 2010 at 21:37 #17626
    kyran
    Participant

    @Lion wrote:

    @Zynewave wrote:

    If you mean a way to set up quantization or swing to be applied only during playback, then that is not something I have planned.

    Thats exactly what I mean. The ReGroove Mixer in Reason4 does this. Where as, it applies the groove (basically midi, in a proprietary extension) to the track without actually altering the midi notes. (while the destructive option is still available)

    While I have no idea how reason tackles this, but I think that only applying during playback is quite limiting, because you can only delay notes and not shift them forward.

    March 6, 2010 at 19:39 #17628
    Lion
    Participant

    @kyran wrote:

    While I have no idea how reason tackles this, but I think that only applying during playback is quite limiting, because you can only delay notes and not shift them forward.

    I’m not sure how they do it either. But its not true that you can only delay them. It has positive & negative ticks, so it shifts left and right. The regroove is acts exactly the same as quantization, but without actually altering the notes timing in the sequencer. Only during playback.

    But like I said, it not something thats a MUST HAVE. It would just be nice to have it, especially when Podium feels a bit like Reason to me. Its the only software that I know does this tho.

    March 8, 2010 at 21:08 #17645
    Zynewave
    Keymaster

    Beta3 is up.

    Unless bugs are reported, this is the last beta before I release 2.27 in a day or two. I need to write the help page for the adjust timing dialog, while I still remember what all the settings do 😉

    The changelog so far reads:

    • Added “Adjust Timing…” command to the edit menu. This opens a dialog with advanced quantization options. There are controls for setting grid, quantize mode, strength of start/length quantization, min/max sensitivity, randomization and swing.

    • Timing adjustments on each event are now saved in the project. This allows you to at any time undo adjustments or redo timing adjustments based on the original recorded timing with the “calculate adjustments from original timing” option in the adjust timing dialog.

    • When events have been modified with the “quantize” or “adjust timing” commands, the edit menu shows two additional commands: “undo timing adjustments” and “commit timing adjustments”. The commit command allows you to do iterative timing adjustments.

    • Fix: Adding child tracks to a group track that had a plugin instrument assigned would wrongly create the child track as an audio track.

    The extract groove feature I mentioned earlier in this topic will come at a later time.

    Note that the .pod file format is not yet updated to save the undoable timing adjustments, but with this beta you can at least try out the commands and see if they work as you expect.

    March 9, 2010 at 05:31 #17649
    Lion
    Participant

    @Zynewave wrote:

    • Fix: Adding child tracks to a group track that had a plugin instrument assigned would wrongly create the child track as an audio track.

    Does that mean comping works for MIDI as well? Cause if so I LOVE you. 😆

Viewing 15 posts - 16 through 30 (of 75 total)
1 2 3 4 5
  • You must be logged in to reply to this topic.
© 2021 Zynewave