superplant | 7 Feb 22:15
Picon
Picon
Gravatar

MIDI-Note under the playhead

When programming a MIDI-Loop the note at the very beginning of the loop, i.e. 
where the playhead is located when the loop starts (with gridsnapping), won't 
get sent correctly and so won't get sounded. The terminal shows me:

"drop flushed event on the floor, time 0 < 3"

The next loop cycle then is processed correctly.

I'm using Ardour 3.0beta1a (built from revision ['11069'])
superplant | 5 Feb 21:20
Picon
Picon
Gravatar

LV2-Plugins

Hello.

sadly I can't get LV2-plugins to work with a freshly cloned svn-repo build of 
Ardour 3. "waf configure" tells me:

 * LV2 UI embedding                                  : True 
 * LV2 support                                           : True 
 * LV2 state support                                 : False

But after starting up, the Plugin-Manager shows only the LADSPA-plugins.
I'm running it on Debian Sid and Ardour 2 works fine with LV2-plugins on the 
very same machine. I tried every possible combination of the LV2_PATH env-
variable. Have I missed something like Ardour 3 has currently a disabled LV2-
support? Google hadn't much to say about it.

Alex
Picon
Gravatar

Armed Track Records ALL Other Tracks Playing?

    As I say, the track armed to record picks up ALL the tracks open in the session. 

    Obviously, I need to be able to record JUST the line/mic in audio.   I need to HEAR all the other tracks, but NOT record them.  I tried messing around with input options on the armed record track, but I seem to record all the current tracks + input or nothing at all.

    Any suggestions?  Thanks for taking the time to help!  The program looks great... if I can just figure this out.




- K
_______________________________________________
Ardour-Users mailing list
ardour-users <at> lists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
Picon
Gravatar

Armed Recording Track Records ALL Tracks Playing?

    As I say, the track armed to record picks up ALL the tracks open in the session. 

    Obviously, I need to be able to record JUST the line/mic in audio.   I need to HEAR all the other tracks, but NOT record them.  I tried messing around with input options on the armed record track, but I seem to record all the current tracks + input or nothing at all.

    Any suggestions?  Thanks for taking the time to help!  The program looks great... if I can just figure this out.


- K

_______________________________________________
Ardour-Users mailing list
ardour-users <at> lists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
Paul Coccoli | 17 Jan 03:03
Picon

Beta2 crash on startup - should I report it?

Beta 2 is now crashing for me with a trivial session (six short MIDI
regions).  It looks the same as mantis ID 0004638, so I wasn't sure it
was worth reporting.  I could include easily attach the entire session
dir along with a proper backtrace, if anyone thinks it will would be
helpful.
Edward Diehl | 15 Jan 23:18
Picon
Favicon

Bouncing midi tracks


I recently recorded a piano piece on Ardour3B2 with midi + Pianoteq plugin.
  I did some editing on the midi file, only at the region level, deleting
one section and splicing 2 regions together.   Now I'd like to save the
edited midi file.  There are no "export" options for midi that I can see. 
I was able to make a "bounced" version by recording the edited midi track
to a new midi track (which makes a file in 
interchange/<session name>/midifiles/), but I wondered if there was any
other way to save the edited midi file. 

Thanks
David Adler | 13 Jan 17:29
Picon

input monitoring

Hi Fred!

On Tue, Jan 10, 2012 at 7:54 PM, fred wrote:
>
> Hi, why not another approach :
>
>> At first, during "composition", Ardour would
>> just be used as an eight channel mixer, with
>> some effect sends per channel
>>
>
> *create 8 MIDI tracks in A3, feeded with your MIDI-HW-keyboard
> *OUTS of these tracks goes to synths & samplers
> *OUTS of synths... to 8 (or more) audio tracks
> *auto input is ON
> *the audio tracks goes to busses
> *SENDS in audio tracks goes pre or post fader to "FX BUSSES"
> *"FX BUSSES" OUTS goes to the busses where plugins are living
> (there you can name the busses, tracks, like :
> -guitar
> -GUIT-TO-REV
> -REV-GUIT... like to change the case for BUS, it's more visual,
> and you can this way have 2  with the same name))
> *and of course all busses - but not FX ONES- goes to the master bus

I've now installed and had a look at ardour3, in order
to try the suggested setup. I must admit though that
I'd have to learn quite a bit more to familiarise with it.
Nice to have it though, for sure I'll migrate to v3 one
day.

I quite like the effect routing you described, i.e. feeding
the sends to per-channel-FX BUSSES before they go
to the bus where the effects/plugins live. Though this
adds another eight buses to the session (and probably
latency(?)), it is an improvement in usability towards
having a separate window for each send.
Not too important for me though, 'cause I use a hardware
Midi controller for accessing the sends' faders.

>> Whenever DSP load approaches the limit due
>> to the number of softsynths/samplers, I'd like
>> to record some of them to tracks in Ardour.
>> Thus finally, when composition is done, I'd have
>> eight recorded tracks that I can mix down to
>> stereo.
>>
>
> with the way describe up there, you will have acces to FX and
> audio tracks fader automation to mix in a better mood,
> and you can record the output of synths at any moment !
>

This is also the case with the setup suggested by Giso.
As I am postponing migration to a3, I'll stick with that
one for a while.

>> * when recording this way, all other synth
>>   tracks are silent (which is tolerable when
>>   recording a synth driven by a sequencer,
>>   but this makes it impossible to play-through
>>   and record an analogue instrument along with
>>   the synths.
>>
>
> Strange, are you sure you can't deal with that ???
> *some auto input stuff ?
>

I can't, that was the whole point of posting my question
in the first place.

To have tracks output the sound arriving at their input
while transport is rolling, I need to set 'Options' ->
'Monitoring' to 'Ardour does monitoring', disable
'Auto Input' and arm all tracks for recording.

Thus, in order to record only *one* track, all others
can not be record-enabled, of course, and are silent
consequently, so I can't record audio while listening
to synths playing through tracks.

However, this is solved by using the track&bus
combination Giso suggested.

>> (2)
>> * create eight buses and eight tracks in Ardour
>> * connect each synth to a bus and to a track
>>
>
> Remark the busses comes at last in "my" connects plan
>>
>> Downsides:
>> * complicated
>>
>
> Well, if you use always that set, you can easily create a template in
> Ardour,
> so you have to do it only one time in a life :)

...maybe more often, each time new versions of ardour arrive. :)
But yes, using templates is a wise thing to do.

>> * more CPU-usage, due to the extra routing
>>
>
> not so much...

Agreed.

>
>> * fader settings of the corresponding
>>   buses' and tracks' effect sends must always
>>   be the same.
>>
>
> That can't happend if you use a FX bus feeded only 1 time

Yes, as written in my previous mail, this is a none-issue,
easily solved by proper routing. My mistake.

>>
>>
>> Anyone a better idea?
>
> Not sure it's said better, different yep ! Hope That Helped, sorry for the
> book !!

No problen, sorry for the delayed answer.
(I had to read a book first :), and compile&try a3)

best,
david
_______________________________________________
Ardour-Users mailing list
ardour-users <at> lists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
Paul Davis | 10 Jan 15:54

Ardour 3 beta 2 released

Another month, another Ardour3 beta! More than 130 fixes and
changes since beta1, all documented below. Download at:

 Linux x86 (32 bit) binary package:
   http://ardour.org/files/Ardour_32bit-3.0beta2_11213-dbg.tar

 Linux x86_64 (64 bit) binary package:
   http://ardour.org/files/Ardour_64bit-3.0beta2_11213-dbg.tar

 OS X Intel binary package:
   http://ardour.org/files/Ardour-3.0-11213.dmg

IMPORTANT NOTES FOR ANY OS X BETA TESTERS
----------------------------------------------------------------------

* You **must** be using JackOSX 0.89 (the
  latest release). Earlier versions of JackOSX will cause
  strange behaviour and/or crashes. Upgrading from existing
  JackOSX versions is recommended anyway, even if you are
  using it with Ardour2 or other software.

* If you want access to any hardware MIDI ports and/or
  other MIDI software on your OS X system, you need to start
  JACK with JackPilot and ensure that the CoreMIDI bridge is
  enabled in its preferences settings.

* As with beta1 and the zero-cost prebuilt versions of
  Ardour, plugin preset saving is disabled.

My hope is that there will be two more betas before Ardour
3.0. Beta 3 will concentrate on remaining matters of
functionality that must work, and Beta 4 will focus mostly
on polish and the first time user experience. I doubt that
these boundaries will be strictly adhered to, tough.

NEW/SUBSTANTIVE CHANGES
-----------------------------------------

* Completely new implementation of the audio clocks used throughout Ardour (for
    docs on using them, please see: http://ardour.org/a3_features_clocks)
* Lots of work on Ardour's handling of tempo and meter.
    *  tempo and only tempo affects the computation of frames_per_beat()
    *  allow tempo changes on any beat of a bar
    * fix lots of bugs associated with dragging and place new tempo or
meter markers
    *  provide config parameter to allow non-quarter note pulses; off
by default; no GUI to reset it at this point
* Save templates as directories with plugin state. Unfortunately breaks
    existing Ardour3 session templates. They can be fixed by
    moving the .template file into a new directory with the
    name of the template (minus the .template)
* Re-work layering in possibly debatable ways. Preliminary documation
at doc/layering.
* Add option to glue new regions to bars and beats
* On OS X, Ardour3 now uses ~/Library/Preferences/Ardour3 as its "user config
folder", rather than ~/.config/ardour3.

GUI TWEAKS AND FIXES
--------------------

* Label solo iso / solo lock buttons even on narrow strips
* Make activate/deactivate all only operate on visible processors (and
also exclude the fader from its effect)
* add a signal so that if the Big Clock is closed, the edit window can
grab focus back
* Remove solo buttons from the master route in the route list
* Remove panner altogether, if necessary, when configuring the UI panning
* Tooltips for mixer strip width and hide button
* Remove ghost notes when actual notes are deleted
* Reset a mixer strip's peak display when its route is changed (notably affects
  the editor mixer strip)
* Change label of audition button in region editor to "Audition" to
indicate *how* it will be heard (via the audition bus, not in-place)
* Fix use of GTK Dialog windows, by (a) adding buttons to all actual
Dialogs (b) using Windows for all non-dialog windows. Fixes
     problems for users of GNOME 3 where Dialogs do not have the usual
window manager decoration, and so could not be closed.
* Fix mute display on session load
* Fix for AFL/PFL button misbehaviour
* Start autoscroll in from the right-hand edge of the screen if the
editor list is not in view, so that autoscroll kind-of works in this
situation
* Display underscores in plugin names correctly
* Fix autoscroll fudge calculations
* Remove code to zoom on up/down mouse movement when dragging the playhead
* Save location UI clock mode in Session instant.xml
* Make fader belts wider to take up maximum space and line up with things nicely
* Shift-ctrl-click on a mixer width button toggles width of all strips
* Fix partial visibility of piano roll when changing MIDI track height
in various way
* Set up piano roll and scroomer objects before the MidiTimeAxisView
height gets set up, so that their visibility can be initialised
correctly
* New zoom button icons
* Set ellipsizing behaviour for mixer strip name button
* Add full name tooltip to name button
* Fix a number of fundamental issues with Gtkmm2ext::Prompter, mostly
centered on bad behaviour when Enter/Return is pressed
* Allow Cancel button on route rename dialog to actually cancel
* Rename new send options to be more clear on the difference;
* Relabel "sends" button to say "Aux Sends" to be clearer on what it does
* Restore the functionality of the join-play-range button,
* Desensitize make-mono-regions as appropriate
* Add tooltips to editor region list column headers
* Add tooltips to the editor track/bus list column headers
* Add tooltips to the editor route group list column headers
* Fix column expansion behaviour of editor region list
* New configuration variable to control display of periodic MIDI
messages (MIDI Clock, MTC)
* Gradient-ized waveforms
* Fix somewhat unlikely crash on doing add note; start drag to resize
note; undo; finish drag to resize note.
* Do not show panner GUI in external send UI, to avoid confusion
* Consistent colors for selected treeview rows
* Fix scroll wheel handling on both gain faders and parameter controls
in automation track headers
* Add monitoring column to route group list;
* Make click in blank area of route list and route group list cancel
selection and/or name editing
* Add color editor button to editor route groups list
* Add "enabled" column to editor route groups list
* Clarify meaning of route group tab context menu items
* Remove visible "sound notes" button,add Config parameter to control this
* Fix setup of gain envelope visible menu item.
* Use same modifiers with the mouse wheel in the summary as in the editor
* Fix scroll-wheel direction in summary
* Fix, or at least improve, management of the editor toolbar when
maximising editing space
* Fix reversed scroll in timeline rulers wrt editor pane
* Add middle-clock-on-range/marker-clock to locate there
* Tweak constants that affect whether/where trimming cursors are shown
for MIDI notes, to avoid making it so hard to drag relatively small
notes
* Make a few region/track context menu actions able to use the mouse
location where the context click occured
   (insert-patch-change, paste )
* Fix comparison of beats to frames when deciding whether to show a patch change
* Improve layout and display of CD range info in location display
* Make the export ranges view expand with the export dialogue.
* Show generic plugin UI toolbar (for presets etc.) on LV2 UIs (except
external).
* Show panner drag information tool-tip style, and also show it when
the button is pressed to start a drag
* Make the MidiRegionSelection notice when its MidiRegionViews go
away; fixes one source of memory corruption during MIDI edits
* Add select all / deselect all to timespan section of export dialogue
* Tweak up size+spacing of main menu bar info box
* Make sure that create drags make notes with a minimum length of 1 tick
* Use a Drag class for midi note selection, so that it gets autoscroll
* Remove OS X specific code for key editor binding displays
* Use the correct display for key accelerators (key "label" not key "name")
* Show pulse note type in tempo markers (optionally)

PLUGIN STUFF
---------------------

* Make Carbon GUI support for AU's optional at compile time
* Fixes for Windows VST support build
* Share code between native linux VST and windows/x86 VST support,
where possible
* Implement the LV2 urid extension and remove implementation of
(experimental) LV2 uri-unmap extension
* Support new URIs for LV2 presets (Old stuff continues to work for
Calf, but it'd sure be nice if it would be updated)
* Implement latest LV2 state extension (0.4)
   (Corresponding patch to LinuxSampler available here:
http://drobilla.net/files/linuxsampler_lv2_state_0_4.diff)
* Save references to external files in LV2 state as symbolic links

      With this commit it is possible to archive sessions that contain
plugins with
      complex file-containing state (e.g. Linuxsampler with a sample
bank loaded)
      with any archive tool, e.g.:

        tar -hjcf session.tar.bz2 session

      Which will give you a fully self-contained archive of everything
used in the
      session, so you can e.g. send it to a collaborator who may not
have the same
      sample banks in the same place as you and it will work.

CODE CHANGES/BUG FIXES
----------------------------------------

* Slightly unpleasant fix for creation of tracks from templates
* Fix erroneous setup of order keys when tracks have children: order
keys relate to the actual tracks only, and ignore child automation
views
* Fill extra channels if monitor sends have more outputs than inputs
* Re-add code to support do-not-record-plugins
* Add track-solo-toggle / track-mute-toggle to make them bindable to keys
* Sort session routes before trying to do the group tabs collection
* Provide and use mechanisms for resolving translation ambiguity
* Fix mis-ordering of MIDI events when merging MidiBuffers in-place
* Patch from colinf to fix build on gtkmm versions prior to 2.28
* Don't load program 0 on initialising a VST
* Fix crash on save caused by never having shown the locations editor
* Fix confusion with midi note selection and channel selection
* Use compiler-generated _LP64 macro to detect x86_64 rather than USE_X86_64_ASM
* Made region export default to use region gain and fades
* Fix failure to find export formats in packages
* Be consistent in the way we merge environment-set search paths and
pre-defined ones
* Make Freesound support default to true
* Provide sensible default step and page sizes for
AutomationControllers based on parameter max and min values
* Fix incorrect position of a copied region
* Fix up some logic so that we don't replicate the session dir path
twice in the search path(s)
* Check that adding a port to an IO is ok with the processors in its
route, and raise an error if not
* Centralize legal-session-name-checkng and include : and ; in
characters that we disallow, because they conflict with search path
conventions on *nix and windows
* Use session_name_is_legal for snapshots too
* Remove unnecessary silencing of unused plugin inputs; unnecessary as
(LADSPA/LV2 at least) connect_and_run routines pass in silent buffers
for inputs that are not in the ChanMapping.  The explicit silencing
also failed if the plugin had more inputs than any processor on the
route
* Compute delta time correctly when appending events to an SMF object;
the converter must be used to convert a source time, not a delta time,
otherwise tempo / meter changes are not correctly accounted for
* Fix for most (all? we can dream ...) issues involved in #4399
(editing multiply-applies operations to playlists used more than
once), and as a side-issue, fix playlist selection which broke when we
hid Diskstreams inside Tracks by using orig_track_id() rather than
orig_diskstream_id()
* Move note creation code into a Drag; fix snapping of note starts
when drag-created
* Keep track of MIDI region's start positions in beats, to match the
source, so that starts are not corrupted when tempos change
* Fix lack of marker/range display in marker/range list at startup,
and tweak location display quite a bit to improve things
* Clarify stop-at-session-end behaviour
* Patch from roy vegard to stop feedback from causing jumps when a
MIDI controller and ardour are out of sync
* Send sustain=off and all-notes-off when a MIDI track is muted
* Tidy up monitoring slightly so that it gets closer to matching chris
goddard's truth table for the various different states.
* Grab bag of changes correcting and improving the way MIDI note
on/off tracking is done. may/should fix a number of problem with
spurious note-offs under a variety of circumstances
* Do not write sequential same-value automation data into a
ControlList (bug fix)
* Thin AutomationList data when reloading from disk (similar code as
Ben's from Ardour 2.X & Mixbus, but without user-adjustable thinning
density at present).
* Move patch changes when inserting silence at the start of a model.
* Add configure option to raise a FP exception when a denormal is
detected (--denormal-exception)
* Create Freesound working directory a little more lazily so that a
Freesound directory doesn't appear in the user's home directory
without ever using Freesound.
* Don't round control list events when x-scaling them; prevents large
loss of accuracy with xfades when they are scaled to be small and then
expanded again
* Use the correct flag for DAZ and default to using FTZ and DAZ
denormal protection.
* Fix issues with export caused by exporting and disk butler threads
working in parallel
* Miscellaneous other crash fixes.

TRANSLATION UPDATES

* .de Richard Oax
* .en_GB Colin Fletcher ("Transport roll" => "Tally ho!")
* .cz Pavel Frich

CONTRIBUTORS

Carl Hetherington, David Robillard, Andre Colomb, Roy
Vegard, Robin Gareus, Mike Start, Colin Fletcher, Paul
Davis
David Adler | 10 Jan 05:20
Picon

input monitoring

I'd like to use Ardour in the following way:

A sequencer is driving some (let's say eight)
softsynths/samplers.

At first, during "composition", Ardour would
just be used as an eight channel mixer, with
some effect sends per channel.

Whenever DSP load approaches the limit due
to the number of softsynths/samplers, I'd like
to record some of them to tracks in Ardour.
Thus finally, when composition is done, I'd have
eight recorded tracks that I can mix down to
stereo.

I've found two ways of doing this:

(1)
* create eight tracks in Ardour
* connect the synths to their inputs
Then, to make the tracks play through when
transport is rolling:
* set Options -> Monitoring -> Ardour does monitoring
* turn 'Auto Input' off (not green)
* record-enable all tracks

Downsides:
* when recording one synth to a track, I must
  first un-enable the record buttons of all
  others.
* when recording this way, all other synth
  tracks are silent (which is tolerable when
  recording a synth driven by a sequencer,
  but this makes it impossible to play-through
  and record an analogue instrument along with
  the synths.

(2)
* create eight buses and eight tracks in Ardour
* connect each synth to a bus and to a track

Downsides:
* complicated
* more CPU-usage, due to the extra routing
* fader settings of the corresponding
  buses' and tracks' effect sends must always
  be the same.

Anyone a better idea? Preferably without any of
the downsides. Best would be (1) without the need
to rec-enable all tracks.

The question isn't exactly new [1][2][3], but none of
those answers really helped me.
This somewhat lengthly mail is just my attempt to
provide some workflow context rather than repeating
the same question.

[1] http://linuxaudio.org/mailarchive/lau/2011/1/29/178208
[2] http://comments.gmane.org/gmane.comp.audio.ardour.user/10389
[3] http://permalink.gmane.org/gmane.comp.audio.jackit/25095

best,
david
Bruno Ruviaro | 6 Jan 00:43
Picon
Favicon

LAC Deadline Extension - now January 22, 2012

Dear Ardourers,

The Linux Audio Conference submissions deadline has been extended! It is 
now January 22nd, 2012.

So, if you were considering submitting a paper but couldn't make up your 
mind yet, here is your chance to become active! Never forget that this 
conference lives through the people participating in it.

January 22nd is the new deadline for all submissions: papers, music, 
installations, workshop proposals.

Notifications of acceptance will still be sent out on February 6th, 2012.

Check out the link below more info:

http://lac.linuxaudio.org/2012/participation

Please spread this information to anyone who might be interested.

Questions? Drop us a line at lac <at> linuxaudio.org

We are looking forward to seeing you at Stanford in April!

Thanks,

The LAC 2012 organization team
Q | 1 Jan 21:05

Re: Denormals

On 01/01/12 19:33, Ross Hamblin wrote:
> Did you try the pre-built binary of ardour 2.8.12 as a test? I had the
> problem
> with disabled denormals functions in several versions previous to 2.8.12
> (both distro packaged and self compiled), scons threw a warning about
> CPU unknown IIRC, but with the release of binary 2.8.12 I am able to use
> those functions again. The binary Ardour 3 also works fine here. I have
> an AMD Phenom CPU.
>
> Hope this helps,
> Ross.
>

Hi Ross

I hope you don't mind me CC'ing this to the list.

Many thanks for the suggestion, I hadn't thought of that. When I 
originally downloaded 2.8.12 I was only able to get the source code. But 
being the first of the month, I've just been able to download the binary 
version (it was the binary of A3 that I downloaded and installed earlier 
today).

The binary version is allowing me to select processor-handling of 
denormals.

I've re-activated the three instances of Invada Delay which seemed 
earlier to be pushing the DSP load up. The session's load was around 25% 
at idle, rising to around 35% whilst playing.

I gave it some abuse, starting and stopping a lot and jumping around 
from one marker to another whilst playing. The load eventually shot up 
to 60% but not much more and stayed there for the time it's taken to 
write this until just a moment ago (and it's shot back up again [and a 
few minutes later still dropped back to 32%. And is back up again! {And 
down again. And up again, I'm getting seasick!}]).

So it seems that the processor denormal handling is helping a great 
deal, but isn't completely resolving the issue.

In future, if building from source I'll have to pay closer attention to 
the messages from scons, or just wait until I can download the binary 
(or pay for it).

Once again, many many thanks for this specific tip -- I cc'd this to the 
list to share this nugget of information for the benefit of everyone. 
And thanks to everyone else who has responded and chipped in, as I say, 
it seems better but not cured so if anyone else has any other ideas, 
fire away...

Q

Gmane