pdc again, just to know..

[jens]

I don't care the least for such a delay and I think it'd o.t. - maybe you should start a new FR request for it. moonlite?

b.t.w. - please let me give you a small production-tip:

if you sometimes feel that one sound or the other (be it drums, a pad or whatever) is coming to late or to early you should look at the single part, not the track - putting a delay on the track would imo be a bad habit - look at a certain moment and fix what you think is wrong at this moment in the part - if it is an audio-track well then open the editor and cut the sample into smaller chunks and start moving them around until you think the problem is fixed - and with midi look at the single notes.

But in any case this has got NOTHING to do with pdc and thus it imo doesn't belong into this thread!

[jorgen]

PDC will not work ubnless I delay tracks internally in the sequencer, so the track delay must be coded anyway.

cheers
jorgen

[moonlite]

I don't care the least for such a delay and I think it'd o.t. - maybe you should start a new FR request for it. moonlite? ;-) :-)

b.t.w. - please let me give you a small production-tip:

if you sometimes feel that one sound or the other (be it drums, a pad or whatever) is coming to late or to early you should look at the single part, not the track - putting a delay on the track would imo be a bad habit - look at a certain moment and fix what you think is wrong at this moment in the part - if it is an audio-track well then open the editor and cut the sample into smaller chunks and start moving them around until you think the problem is fixed - and with midi look at the single notes.

But in any case this has got NOTHING to do with pdc and thus it imo doesn't belong into this thread! ;-)

yeah, it could be a separate fr, too, but it's kinda related, so what's the harm in requesting this simultaneously? =)

and for the tip .. well, yeah, that's one approach to that prob, but since i usually only have one "sound" per track, it's much more easy and intuitive to adjust the whole track ..

let's say a bd that i've made in some synth, that's just perfect othervice, but sounds a little better when dealyed f ex (+ or -) 5 ms from the rest of the song. (this is more than often the case, or something similar). now wouldn't it just be silly to 1. adjust the env of the bd so that the /sound/ gets worse, or 2. sample the sound. by sampling it you'd loose the tweakability ..

it's pretty stupid to cut off a samples attack (f ex a db or hihat or snare etc) just to get the timing right. sometimes it even destroys the sound itself. much better to adjust the timing of the track =)

i always have everything quantized .. actually step-recorded or drawn with a mouse, so it's not about single notes not being on time or other things that are caused by poor timing while recording etc ...

hmm, not quite off-topic imho, just giving arguments to why track delay can't (in practice) be substituted by other means. to avoid misunderstandings.

[moonlite]

an other example would be to have a pad sound that have such a slow attack that it must be started, say, 500ms beforehands to make it "sound right".

much easyer to give the track 500ms of negative delay, at least when working with step recording ..

and i'd imagine, that it would in /any/ case be a MUCH easier way to adjust the (negative) delay than adjusting the single notes one at a time.

say, for example, if you've already mostly finished the song, but decide that the attack of the pad should be even longer than before. which do you find easyer: open every pattern and adjust every note, of just tweak one slider?

i myself find the slider much better.

coud be that you record everything live, so this doesn't affect you that much, but if you ever feel that after quantizing some instrument plays a bit too late or in front, this would work for you too. without having to open plugins or patterns or anything unintuitive and unnecessarily timeconsuming.

[druid]

Just to add my two cents, I've been looking at purchasing EnergyXT, to use it by itself to produce music. PDC is one feature that's held me back. While it is not the most important reason for me, I am still afraid of not realising a plugin has a substantial delay and therefore screwing something up.

Of course, 32-bit automation of plugin parameters was another high on my list feature .. but I have this feeling I read that was implemented .. possibly a while ago.

Really, I find it very difficult to find out exactly what it does support and what it does not without reading 30 threads with 100 posts each and multiple trillions of websites ('slight' exaggeration may have been used :)).

[jens]

let's say a bd that i've made in some synth, that's just perfect othervice, but sounds a little better when dealyed f ex (+ or -) 5 ms from the rest of the song. (this is more than often the case, or something similar). now wouldn't it just be silly to 1. adjust the env of the bd so that the /sound/ gets worse, or 2. sample the sound. by sampling it you'd loose the tweakability ..

it's pretty stupid to cut off a samples attack (f ex a db or hihat or snare etc) just to get the timing right. sometimes it even destroys the sound itself. much better to adjust the timing of the track =)

an other example would be to have a pad sound that have such a slow attack that it must be started, say, 500ms beforehands to make it "sound right".

of course I get your point if you usually have just one part per track... but anyway - here's how I do it:

- make the part a bit longer (let's say a quarter of a bar) by dragging its start to the left in case you want something to start a bit earlier

- select the part and press shift+return (to play the selected part in a loop)

- for the BD open the midi-editor and press 'x' to disable quantize, zoom in and the move the bd just a tiny bit until it sounds good for you

- for the pad set quantize to 1/16, deselect all notes and then click on the left move button in the left upper corner of the editor-window, listen and maybe click the move-button again until it sounds right (it depends on the tempo but usually 1/8 is about right)

- now if you copy the part it will overlap but that's no problem

[jens]

Really, I find it very difficult to find out exactly what it does support and what it does not without reading 30 threads with 100 posts each and multiple trillions of websites ('slight' exaggeration may have been used ).

just start a thread and ask!

[moonlite]

jens, ah, yeah .. that might work too, but it sounds unnecessarily elaborate to be used in any and all phases of the creation process. compared to a single little slider that does it in a jiff and is visible all the time for quick adjustment =)

well, have i managed to talk you over yet? ;)) (well, i guess you don't have to do this as much as me ...)

anyway,
cheers =)

[jens]

well, have I managed to talk you over yet?

Nope!

[DarkStar]

hvaring, you're wrong

Yeah well it happens. I was wrong back in '63 too, I believe, if memory serves.

I think you'll find it was '62

[moonlite]

PDC will not work ubnless I delay tracks internally in the sequencer, so the track delay must be coded anyway.

cheers
jorgen

so, now, where's the controls? ;)



THANKS for pdc btw!

[DarkStar]

in the Sequencer, F9
in the Main window, right-click >> Options >> Project

[djsubject]

in the Sequencer, F9
in the Main window, right-click >> Options >> Project

thanx dark star,

i didint know it was there

Subz

[moonlite]

KEWL! didn't know about that :o

[moonlite]

hm, that info could fit even on those channel thingies that have the mute&solo buttons aswell ..