finally found the problem, theres a note level editing button!
Now i have found a problem, if i have a midi note thats right at the start of the region bang on the beat, and the region starts bang on the beat, those notes disapear and also disapear in all regions that i have copied, only by having the first not just infront of the beat will the notes stay in place.
I think this may be a bug but i will have to create a new track to confirm.
oh dear
next problem.
If you copy a region and paste it, anything you do to any of those copied regions effect the original region that it was copied from, thats great, im copying a 2 bar drum pattern and putting a fill in but now its put the fill in the original and theres not enough undo levels to fix it.
@veda_sticks At the very least you should be bringing this up in IRC, it probably would help you find the tools that exist in Ardour much faster. And you should be reporting bugs on Mantis, as they will get lost here. I am not up to date on MIDI editing, but IIRC there are two different ways to copy the region, and I suspect what you are looking for, again IIRC, is called FORK, which will create a new region that is not ‘linked’ to the original.
Also make sure you are actually reading the manual sometime, for instance the information on copying MIDI regions may come in very useful for you as it likely answers some of your last post…
http://manual.ardour.org/editing-and-arranging/edit-midi/copy-midi-region/
SeabladeDisappearing notes on the start of a region is actually a bug that I often encountered. But it doesn’t happen always… Just move the note I small amount to the right to work around this.
To make a copy of a region not refer to the same MIDI-data like the original, just invoke “Unlink from other copies” in the MIDI-menu of the copy.
thanks for the link to a more usefull manual.
Ardour links to here http://en.flossmanuals.net/Ardour/Introduction/ within there program.
So theres 2 different manuals.
I dont have time to go registering yet another place or to go finding people on irc, having already spent 2 hours because there was a button that should be pressed.
Theres a region bar under the midi track, so instead of having to press note edit to edit the notes, and click again to go out of edit to be able to modify the region, why not simply be able to move resize by draging the bar under the drag, no more need for that note edit button, because you can do both at the same time… Clicking the bar will select the hole region, thers no need for as far as i can see. its just an extra step to trip you up if you forget what mode your in
Ok reading the proper manual i can see how region links can be usefull, this should be disabled by default.
This is the manual that shoulld be loaded from within ardour instead of the manual its currently linking to.
That manual you linked to is for Ardour2 actually, and yes it could likely at this point be considered a bug that it links there if that is the default in A3 and no option exists for the one I linked to above. So again I point you to Mantis(Well LeatusPenguin beat you to it;) However the one I linked to above is linked to in the support section of this website, the first link in fact, and the second link is the one to the tutorial with a section describing it’s history as well:)
Seabladeive submitted a bug report, yet another account accumulated.
Not sure if its ardours fault or a library somewhere or the plugin im using, but ardour just quits without warning and 9 times out of 10 no data since the last save gets recovered.
ive probably lost a few hours of painful penciling in notes and adjusting velocitys due to ardour just disapearing and leaving me on my desktop.
ardour-3.3: …/libs/evoral/src/Sequence.cpp:1216: typename Evoral::Sequence:
:const_iterator Evoral::Sequence::note_lower_bound(Time) const [with Time = double]: Assertion `i == _notes.end() || (*i)->time() >= t’ failed.
Aborted
Bazsound@bazsoundstudio:/media/Storage$
This we would need more info on to figure out what exactly the problem is.
http://ardour.org/debugging_ardour.html
Make certain this information goes into Mantis as well.
SeabladeI think this is related more to ardour 3.3, i managed to get 1 particular note edit to consistantly crash ardour and it was when i was moving a midi note to the beginning of a region and moved it back a little to far which would have been before the region. it would only do this consistantly in 1 part of the file however it would sometimes do it in other regions but more randomly.
i went back to ardour 3.0 that came with av linux and didnt have any more problems.
im having a look at the debugging page aswell and will see what i can do to provide more details.
thankfully ive managed to get my project to some form of demoable version.
Until these bugs are worked out id suggest sticking with earlier versions if your wanting to get stuff done. Ive finatlly got my head round how ardour works with editing midi and can build up songs. And with the quality of some sound fonts availible for free you can get some nice results.
https://soundcloud.com/bazsound/composition1-demo-v2
heres what i have so far.
The only live instrument is 2 acoustic guitar trakcs, the rest is midi using calf fluidsynth using a nice dry drumkit sound font and a really good bass guitar sound font. The bass guitar sound font has really really long decay which posed a bit of a problem since the if there are any gaps between notes it stops abruptly and i dont think you can set any decay settings in fluid synth. As long as you have no gaps between notes you get a really nice thick bass sound with a bit of low end boost and lowmid cut to get an even thicker sound.
Bug report has been updated with debugging information which can be found
http://tracker.ardour.org/view.php?id=5656
If anyone else has issues with crashes during moving notes beyond regions or notes disapearing when resizing regions to the start or end of notes please report add information to this bug report
here we go again with un explained behavoiur.
this time in ardour 3.0
for some odd reason i can no longer copy and paste regions of midi, like to copy a drum part to repeat it.
Also i can no longer move regions, and now exporting problems and then ive had 2 midi regions shifted themself a bar ehead and wont move back without getting messed up if i move them.
ok never mind, splice mode.
I’m trying to figure out how to bring up the velocity track so I can contour dynamics into my passages. Is there such a thing in Ardour, or a way to do it?
That - manually adding humanlike expression and eventual mastering - is the man reason I use a DAW after composing a score in MuseScore.
There is no velocity track in ardour. You can edit the velocity values by moving the cursor over the notes and move the mouse wheel or by hitting ‘v’ and enter the values numerically.
or by clicking on the “a” (automation) button in the track header, and making the Volume controller track visible. Then graphically edit or record CC #7 data. This will control volume BUT not velocity, which is not quite the same thing (the difference depends on the target instrument).
@Paul I’m glad you recognize they are not the same thing. A delicate cadenza passage played on a concert Steinway D, for example, demands control over each note. Unfortunately for Ardour, that’s the type of music I compose.
It sounds like we need an additional automation lane called “velocity scaling” or “velocity offset” which allows you to adjust playing dynamics across a range, without having to edit individual notes.
I think Paul’s point is that some smart plugin manufacturers use the “Volume CC” for this purpose, since the track usually has an audio fader that provides “real” volume control.
-Ben
I see that Ardour also allows you select a group of notes (either by shift-click or by drawing a box around them) and then raising or lowering the velocity of all notes relative to the starting position of each. (I see one cannot select notes by both methods at the same time which could be useful - i.e. select multiple regions by shift-boxing). Ardour3 does give you control over each note, at least the velocity which I think is the main way to control volume. Seems like altering the volume with Volume CC is defeating the point of velocity-based samples, ie. the fact that instruments like the piano have different timbre’s at different volumes. I also recording piano pieces from live play and edit the midi with Ardour. Note level editing is intrinsically tedious though I’m finding the latest Ardour3 works fairly well for this kind of editing. I do not do a lot of edits, but remove the odd wrong note or adjust a velocity. As is normal with recording, a good take is far superior to trying to fix a sub-par performance with editing.
yes. we do need the extra automation lane.