From: Tim E. R. <ter...@ro...> - 2012-03-30 19:56:12
|
During recording I got "route already exists" message followed by "circular route found" messages. I'm pretty sure it's only when I use the 'Duplicate Selected Tracks' feature on wave tracks. (Yep, this feature sure is proving handy. So many re-takes! ) Possibly because the wave tracks are already routed to output by default. Possibly when switching the tracks from stereo to mono, then duplicating. Not sure. Need to test more. So far, it can be worked around by saving then restarting. My department. Likely some loose ends I need to tie up there. I'll try to fix by Sunday if y'all can wait. Thanks. Tim. |
From: Robert J. <spa...@gm...> - 2012-03-31 07:55:54
|
Hi Tim, Den 30 mars 2012 21:55 skrev Tim E. Real <ter...@ro...>: > During recording I got "route already exists" message > followed by "circular route found" messages. > > I'm pretty sure it's only when I use the > 'Duplicate Selected Tracks' feature on wave tracks. > (Yep, this feature sure is proving handy. So many re-takes! ) > > Possibly because the wave tracks are already routed to output by default. > Possibly when switching the tracks from stereo to mono, then duplicating. > Not sure. Need to test more. > > So far, it can be worked around by saving then restarting. > > My department. Likely some loose ends I need to tie up there. > > I'll try to fix by Sunday if y'all can wait. Sure, I'm away until sunday in any case... Apart from that are there any other bugs of priority? I'm sure there were some but maybe we can reprioritise if they have workarounds (or non serious) and don't break compatibility. Regards, Robert > Thanks. > Tim. > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Tim E. R. <ter...@ro...> - 2012-04-19 02:39:06
|
On March 30, 2012 3:55:56 PM Tim E. Real wrote: > During recording I got "route already exists" message > followed by "circular route found" messages. > > I'm pretty sure it's only when I use the > 'Duplicate Selected Tracks' feature on wave tracks. > (Yep, this feature sure is proving handy. So many re-takes! ) > > Possibly because the wave tracks are already routed to output by default. > Possibly when switching the tracks from stereo to mono, then duplicating. > Not sure. Need to test more. > > So far, it can be worked around by saving then restarting. > > My department. Likely some loose ends I need to tie up there. > > I'll try to fix by Sunday if y'all can wait. > > Thanks. > Tim. > Was having trouble figuring conditions for this. Then I found my note in audiotrack.cpp at line 210, in AudioTrack::internal_assign() which is part of the track copying feature I added: // FIXME: May get "addRoute: src track route already exists" when say, // an audio output and wave track are selected just because // of the redundancy (wave track wants to connect to output by default). Will try to concentrate on this. It's an important bug in a useful function. Causing me trouble in my project. Possible quick solution: Would anyone mind if we DON'T automatically connect wave tracks to the first available output track? I did remove it from a few of the other track types like groups because it got to be very annoying with large projects. And it will become annoying with wave tracks if I start routing them to groups in my projects again. I know, auto connect is useful especially for newbies... I'll try to preserve it, but shouldn't we be consistent? (I'm speaking of track-to-track routes. Keep Output Track Jack connections.) The user sees no track-to-track auto connect on other track types and then suddenly sees it only on wave-to-output tracks... Or maybe I should try to reinstate all the former auto connects, like from Groups to Outputs, for newbies, but this time only for the first instance, like we do with Outputs and Jack ports. More work... Tim. |
From: Robert J. <spa...@gm...> - 2012-04-19 07:49:04
|
Hi Tim, Den 19 april 2012 04:37 skrev Tim E. Real <ter...@ro...>: > On March 30, 2012 3:55:56 PM Tim E. Real wrote: >> During recording I got "route already exists" message >> followed by "circular route found" messages. >> >> I'm pretty sure it's only when I use the >> 'Duplicate Selected Tracks' feature on wave tracks. >> (Yep, this feature sure is proving handy. So many re-takes! ) >> >> Possibly because the wave tracks are already routed to output by default. >> Possibly when switching the tracks from stereo to mono, then duplicating. >> Not sure. Need to test more. >> >> So far, it can be worked around by saving then restarting. >> >> My department. Likely some loose ends I need to tie up there. >> >> I'll try to fix by Sunday if y'all can wait. >> >> Thanks. >> Tim. >> > > Was having trouble figuring conditions for this. > Then I found my note in audiotrack.cpp at line 210, > in AudioTrack::internal_assign() which is part of the track copying > feature I added: > > // FIXME: May get "addRoute: src track route already exists" when say, > // an audio output and wave track are selected just because > // of the redundancy (wave track wants to connect to output by > default). > > Will try to concentrate on this. It's an important bug in a useful function. > Causing me trouble in my project. > > Possible quick solution: Would anyone mind if we DON'T automatically > connect wave tracks to the first available output track? I do mind actually, but I can give it up if it reduces complexity (and hence maintainability) of the code. > I did remove it from a few of the other track types like groups because > it got to be very annoying with large projects. > And it will become annoying with wave tracks if I start routing them > to groups in my projects again. > I know, auto connect is useful especially for newbies... > I'll try to preserve it, but shouldn't we be consistent? This is ofcourse true, we should be as consistent as possible, but auto-connects are very good for smaller projects. Best would be if both was possible, holding shift while adding would add without an auto connection, for instance. This made me think that we should change the iR and oR buttons so they signal when there are no connections, change color to darker gray seems a good idea for inputs and red for outputs (there should always be an output connected) > (I'm speaking of track-to-track routes. Keep Output Track Jack connections.) > The user sees no track-to-track auto connect on other track types > and then suddenly sees it only on wave-to-output tracks... > > Or maybe I should try to reinstate all the former auto connects, like > from Groups to Outputs, for newbies, but this time only for the first > instance, like we do with Outputs and Jack ports. More work... For now, leave it at the solution that is less work. This shouldn't affect compatibility so we can always revisit it. Regards, Robert > > Tim. > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Tim E. R. <ter...@ro...> - 2012-04-22 06:38:13
|
On April 19, 2012 9:48:53 AM Robert Jonsson wrote: > Hi Tim, > > Den 19 april 2012 04:37 skrev Tim E. Real <ter...@ro...>: > > On March 30, 2012 3:55:56 PM Tim E. Real wrote: > >> During recording I got "route already exists" message > >> followed by "circular route found" messages. > >> > >> I'm pretty sure it's only when I use the > >> 'Duplicate Selected Tracks' feature on wave tracks. > >> (Yep, this feature sure is proving handy. So many re-takes! ) > >> > >> Possibly because the wave tracks are already routed to output by > >> default. Possibly when switching the tracks from stereo to mono, then > >> duplicating. Not sure. Need to test more. > >> > >> So far, it can be worked around by saving then restarting. > >> > >> My department. Likely some loose ends I need to tie up there. > >> > >> I'll try to fix by Sunday if y'all can wait. > >> > >> Thanks. > >> Tim. > > D'oh! Stupid error I knew my code looked slimy when I wrote it but it slipped through. - Duplicate Tracks: Fixed routing bug. In tracks' ::internal_assign(), don't call msgAddRoute, simply push_back the route node, because caller later calls msgAddTrack which 'mirrors' that single routing node. Exception: Audio Input and Output still need to call msgAddRoute which connects to Jack. May still cause audio processing problems ? Tested as thoroughly as I could, loading and saving. I do hope them "circular route found" jobbies are gone too ! --- Note: It turns out the Duplicate Tracks feature may have to become much more intelligent *if* two or more tracks are selected and they route to each other. Currently it just blindly duplicates as if you had duplicated *each* track separately. This is kinda dumb if for example a wave track and an output are selected, and the wave track routes to the output, because one would probably expect that the new wave track would exclusively route to the new output. But this does not happen. So really Duplicate Tracks is currently mostly useful for selecting some wave or midi tracks and duplicating them, not along with groups, inputs, outputs etc. > Best would be if both was possible, holding shift while adding would > add without an auto connection, for instance. > This made me think that we should change the iR and oR buttons so they > signal when there are no connections, change color to darker gray > seems a good idea for inputs and red for outputs (there should always > be an output connected) Hm similar but not exactly, to the midi controller graphs showing when there are events with the green dot. Nice touch, whoever added that. Also, I'd really like to add the track type icons to the routing popups ! It's hard to judge just by the text what track is what, so many tracks... Cheers. Tim. |