hi,
quick update before moving to the new version: it seems related to the
switch between sessions. i mean, if i switch directly i got the issue,
whereas if i close the session and then i move to the new one, all the
connections are kept.

max


On Thu, Nov 28, 2013 at 11:45 PM, The name of my band is 1984 <
[email protected]> wrote:

> hi,
>  i'm not running the most updated version...i'll do it soon...i've
> refreshed patchage quite a lot, open/close everything...the only thing that
> seems to keep the connections is to stop/start jack before moving to the
> new session.
>
> btw, i will update to the latest version and i'll let you know
>
> cheers
> max
>
>
> On Thu, Nov 28, 2013 at 10:51 PM, J. Liles <[email protected]> wrote:
>
>> Oh, also, are you sure the connections are *really* not made? Patchage is
>> pretty bad at updating its state--so it often shows an incorrect view of
>> the JACK graph (one has to hit Ctrl+R to refresh it--or sometimes restart)
>>
>>
>> On Thu, Nov 28, 2013 at 2:39 PM, J. Liles <[email protected]> wrote:
>>
>>> Are you running the latest version of everything (from git)?
>>>
>>>
>>> On Thu, Nov 28, 2013 at 2:36 PM, The name of my band is 1984 <
>>> [email protected]> wrote:
>>>
>>>> hi there,
>>>> i'm experiencing some issues duplicating sessions. basically, i have 3
>>>> clients: jackpatch, non-timeline, non-mixer.
>>>>
>>>> non-timeline: 5 Audio tracks
>>>> non-mixer: 6 strips (1 for each track + 1 for master)
>>>>
>>>> capture goes IN to each Audio and into master (for  input level
>>>> monitoring)
>>>> each audio track goes IN 1 mixer strip, then all OUTs are routed to
>>>> Master strip. Master strip OUT is routed to playback.
>>>>
>>>> that's going to be my template for quick setup. every time i reload
>>>> this session is ok. Patchage is showing all the original connections.
>>>>
>>>> when i try to duplicate this sessions (e.g., song1) some connections
>>>> get lost...i mean it could be from capture to Track1 or to Mixer...
>>>>
>>>> am i missing anything?
>>>>
>>>> thanx
>>>> non-max
>>>>
>>>
>>>
>>
>

Reply via email to