headers
Lieven Moors | 2 Feb 23:00
Picon

Re: input monitoring



On Tue, Jan 10, 2012 at 5:20 AM, David Adler <david.jo.adler <at> gmail.com> wrote:

Downsides:
* when recording one synth to a track, I must
 first un-enable the record buttons of all
 others.


I vaguely remember that enabling or disabling "tape machine mode"
under the monitoring options changes this behaviour.
Also, I found this document which describes how the different
monitoring modes react.

http://www.google.be/url?sa=t&rct=j&q=ardour%20tape%20machine%20monitoring&source=web&cd=6&sqi=2&ved=0CGAQFjAF&url=http%3A%2F%2Fwww.harrisonconsoles.com%2Fmixbus%2FArdour_Mixbus_Monitoring_Modes.pdf&ei=kAUrT4iLD86o8AOqrtCPDw&usg=AFQjCNG8-gn4lZesAQ_im0BCdzE66oKRPQ&cad=rja

This might not be of any help, but it might be worth a try.
_______________________________________________
Ardour-Users mailing list
ardour-users <at> lists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
Permalink | Reply | 1 comment |
headers
David Adler | 3 Feb 00:57
Picon

Re: input monitoring

On Thu, Feb 2, 2012 at 11:00 PM, Lieven Moors wrote:
>
> On Tue, Jan 10, 2012 at 5:20 AM, David Adler <david.jo.adler <at> gmail.com>
> wrote:
>>
>> Downsides:
>> * when recording one synth to a track, I must
>>  first un-enable the record buttons of all
>>  others.
>>
>
> I vaguely remember that enabling or disabling "tape machine mode"
> under the monitoring options changes this behaviour.
> Also, I found this document which describes how the different
> monitoring modes react.
>
> http://www.google.be/url?sa=t&rct=j&q=ardour%20tape%20machine%20monitoring&source=web&cd=6&sqi=2&ved=0CGAQFjAF&url=http%3A%2F%2Fwww.harrisonconsoles.com%2Fmixbus%2FArdour_Mixbus_Monitoring_Modes.pdf&ei=kAUrT4iLD86o8AOqrtCPDw&usg=AFQjCNG8-gn4lZesAQ_im0BCdzE66oKRPQ&cad=rja
>
> This might not be of any help, but it might be worth a try.

Thanks Lieven, a very helpful table.
It confirms that the behaviour I wanted to achieve isn't possible
with using just tracks.

To render it in form of a table, I was looking for settings that give
me is this:
http://paste.pocoo.org/raw/544905/
and by now I start to see why implementing that sort of behaviour
for a track would not be a good idea.

Solution:
Using tracks (for recording) and buses (for mixing and effects).
Now I have the input routed into one track and one bus, and the
track's output routed into the bus.
Setting "Mode" to "Normal" and "Auto Input" to "Off", the track
never outputs its input, so the bus doesn't receive two signals
when nothing is recorded on the track.
As soon as I have recorded a track, it is then my own
responsibility to silence/disconnect the source.

That sort of routing is now implemented in my sessions (i.e. in
the default preset found on http://chino.tuxfamily.org), and I'm
happily starting to actually use it. Thanks for all the answers.

best,
david
_______________________________________________
Ardour-Users mailing list
ardour-users <at> lists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
Permalink | Reply | 0 comments |
headers
Kromatic Photography | 4 Feb 23:38
Picon

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
Permalink | Reply | 1 comment |
headers
Kromatic Photography | 4 Feb 23:40
Picon

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
Permalink | Reply | 1 comment |
headers
Paul Davis | 5 Feb 02:05

Re: Armed Recording Track Records ALL Tracks Playing?

you're using the builtin audio "soundcard" on your computer. its
hardware mixer is set to capture the output that is being sent to the
speakers.

neither JACK nor Ardour touch the hardware mixer of your audio
interface. this is a task for a specialized application (in some
cases, an application written solely for your specific type of audio
interface).

start with something like qamix (GUI) or alsamixer (terminal). it can
be complicated.

On 2/4/12, Kromatic Photography <kromaticphoto <at> gmail.com> wrote:
>     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
>
Permalink | Reply | 0 comments |
headers
superplant | 5 Feb 21:20
Picon
Picon

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
Permalink | Reply | 1 comment |
headers
Paul Davis | 5 Feb 22:04

Re: LV2-Plugins

On Sun, Feb 5, 2012 at 3:20 PM,  <superplant <at> gmx.de> wrote:
> 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

"state support" is a new thing, based on stuff in drobilla's latest
LV2 support libs. it is *not* necessary in order to actually use LV2
plugins.

> variable. Have I missed something like Ardour 3 has currently a disabled LV2-
> support? Google hadn't much to say about it.

this has not happened. i am building without drobilla's latest, and
LV2 plugins work fine for me with the proviso that i have to set LV2
path because on my fedora x86_64 system, they get installed into
/usr/lib64 and the default search path in drobilla's lv2 support code
does not include this.

--p
Permalink | Reply | 0 comments |
headers
Brett Clark | 6 Feb 14:08
Favicon

Re: Armed Track Records ALL Other Tracks Playing?


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

This statement seems to imply that there were previous statements.  Unfortunately i didnt see any previous so im missing information such as the version of Ardour, platform, audio interface, and usual other info.

If you verified that your armed track is only pulling from the line/mic in source, then id be curious which audio interface you're using.  My first thought, although odd, would be that your hardware could be mixing the outputs back into the input.  Another more probable thought could be that you're routing everything through a mixer board and its pushing the outputs back into the input.

Could you please provide additional details on your setup, including external routings?

Thanks
--Brett




On Sat, Feb 4, 2012 at 4:40 PM, Kromatic Photography <kromaticphoto <at> gmail.com> wrote:
    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


_______________________________________________
Ardour-Users mailing list
ardour-users <at> lists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
Permalink | Reply | 0 comments |
headers
superplant | 7 Feb 22:15
Picon
Picon

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'])
Permalink | Reply | 4 comments |
headers
Paul Davis | 7 Feb 22:37

Re: MIDI-Note under the playhead

On Tue, Feb 7, 2012 at 4:15 PM,  <superplant <at> gmx.de> wrote:
> 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'])

this has been long fixed.

if you're testing ardour3, its wise and useful to stay current with at
least the latest beta release, if not current svn.
Permalink | Reply | 3 comments |

Gmane