From: Mark K. <mar...@at...> - 2002-12-16 02:11:04
|
Hi, I did a couple of hours work today porting over a session I started in Pro Tools but never finished. Mostly things went pretty well, but there were some interface issues I ran into. If there is some agreement that these make sense, or that I haven't missed how to do some of these, then I'll enter feature requests. On the very positive side, I didn't have a single real technical problem running RG and Ardour together on the same machine at least for live audio. I did not record any audio, so I still have that threshold to cross, but I'm not worried. IMPORTANT 1) No solo functions. As I was setting up MIDI tracks and listening to things it suddenly dawned on me that while there is a mute button for each track, there is no solo function. We need one. 2) One fixed size for tracks in the main track window. Often you want to see a bit more info. I have previews turned on, but I can't see enough to make it worthwhile, other than seeing at a very high level whether a track should be playing or not. It would be useful to have a choice of sizes for each track. (Pro Tools has 7. I think that's too many, but 3 or 4 would be used.) The one size available in RG is about the same as the smallest in Pro Tools, which I never use for other than showing the track. MODERATE 3) In the Edit as Matrix window, I tended to work with the zoom quite far out. In this case the moving play line leaves behind a lot of artifacts as it scrolls across the screen. Zooming i and out again gets rid of them, but you get new ones of course as it goes playing along. 4) I had fewer problems now than before with selecting lots of MIDI notes and hearing lots of noise, but it does still happen. Interestingly, if I do a select all from the menu RG plays no notes, which I think is the right thing to do. 5) I personally don't like the way the transport is mapped to keyboard hits, most specifically that most apps (that I use...) use the space bar to start and stop, but RG is arming for record. I'd very much like to have a way to configure this for my preferences. 6) I had to do some complete transposes of tracks today. This mostly worked well, but I had one problem that was sort of catastrophic, at least if it really happened. I had a complete bass track selected, and transposed it down believe 3 octaves. Apparently I had gone too low, and needed to transpose it back up. When I did the track was oddly out of tune. It turned out that some notes, the lowest ones, were no longer the right notes. I am guessing that I hit the lower limit on MIDI notes or something, and that some notes could not be transposed as far as the y needed to be, so RG probably made them note 0, but the distance between notes changed. It was a bit of a mess. My input would be that RG should inform me when it cannot carry this operation out and tell me without making the change. I am not 100% sure this happened this way, but something happened... 7) After the recent changes about MIDI interfaces and how it recognizes multiple ports on a single card I responded that the two ports were showing up identically when you chose a MIDI channel. This was a problem today. I'd like to see RG be much more clear about which interface and which port I am choosing. In general, while it may look like a lot, I'm really pretty impressed with how well RG, Ardour and jack all worked together. This is going pretty well. An upcoming email will once again prod us toward making transports between these apps talk, but I know the solution for that is probably quite a long ways away. Thanks much guys. It's really quite a good app. Cheers, Mark |
From: Richard B. <bo...@bo...> - 2002-12-16 07:54:20
|
On Monday 16 December 2002 02:12, Mark Knecht wrote: > 1) No solo functions. As I was setting up MIDI tracks and listening > to things it suddenly dawned on me that while there is a mute button > for each track, there is no solo function. We need one. No you're wrong - try the big "S" on the transport (under the flap). > 2) One fixed size for tracks in the main track window. Often you want > to see a bit more info. I thought there was already a feature request for vertical zooming - it's certainly something we plan at some point. > 3) In the Edit as Matrix window, I tended to work with the zoom quite > far out. In this case the moving play line leaves behind a lot of > artifacts as it scrolls across the screen. Zooming i and out again > gets rid of them, but you get new ones of course as it goes playing > along. > 5) I personally don't like the way the transport is mapped to > keyboard hits Feature request. > 6) I had to do some complete transposes of tracks today. Bug report. > 7) After the recent changes about MIDI interfaces and how it > recognizes multiple ports on a single card I responded that the two > ports were showing up identically when you chose a MIDI channel. This > was a problem today. I'd like to see RG be much more clear about > which interface and which port I am choosing. Make a comment on that cascading menu BR you submitted. B |
From: Romain d'A. <r.a...@fr...> - 2002-12-16 10:15:24
|
Richard Bown wrote: > On Monday 16 December 2002 02:12, Mark Knecht wrote: > > > >1) No solo functions. As I was setting up MIDI tracks and listening > >to things it suddenly dawned on me that while there is a mute button > >for each track, there is no solo function. We need one. > > No you're wrong - try the big "S" on the transport (under the flap). I guess what Mark is talking about is an "obvious" per-track solo button along with each track; it's a UI layout matter, not functionnality. Mute and solo are respective functions to each other (soloing a track means muting all others; you can too solo several tracks - it's easier to solo 3 tracks than mute 8 others to hear only the 3 desired). The transport Solo button is not explicit about which track is being soloed, but the one being "selected". Just my opinion, anyway. :) romain. |
From: Mark K. <mar...@at...> - 2002-12-16 12:23:02
|
On Sun, 2002-12-15 at 23:46, Richard Bown wrote: > On Monday 16 December 2002 02:12, Mark Knecht wrote: > > > 1) No solo functions. As I was setting up MIDI tracks and listening > > to things it suddenly dawned on me that while there is a mute button > > for each track, there is no solo function. We need one. > > No you're wrong - try the big "S" on the transport (under the flap). OK, so I missed that, but... How do I use it when I need to solo two or three tracks? I do understand that muting 12 out of 15 tracks gets me down to three, but most programs have solo as a function of a tarck, not of the transport. |
From: Chris C. <ca...@al...> - 2002-12-16 10:29:57
|
Mark Knecht wrote: > 6) I had to do some complete transposes of tracks today. [...] > It turned out that some notes, the lowest ones, were no longer > the right notes. I am guessing that I hit the lower limit on MIDI notes > or something That sounds very probable. We do cut off pitch at the MIDI boundaries, so your really low notes will have been sharpened when you transposed them up again. As you say, this is bad form -- we should probably just store negative pitch and cut it off when playing instead, or at the least warn about it. I'll look into this -- preventing it from cutting off the pitch is trivial but I want to make sure we don't allow the negative pitches through to the sequencer side of things. Chris |
From: Mark K. <mar...@at...> - 2002-12-16 12:04:45
|
Thanks! On Mon, 2002-12-16 at 02:28, Chris Cannam wrote: > Mark Knecht wrote: > > 6) I had to do some complete transposes of tracks today. [...] > > It turned out that some notes, the lowest ones, were no longer > > the right notes. I am guessing that I hit the lower limit on MIDI notes > > or something > > That sounds very probable. We do cut off pitch at the MIDI boundaries, > so your really low notes will have been sharpened when you transposed > them up again. As you say, this is bad form -- we should probably just > store negative pitch and cut it off when playing instead, or at the > least warn about it. I'll look into this -- preventing it from cutting > off the pitch is trivial but I want to make sure we don't allow the > negative pitches through to the sequencer side of things. > > > Chris > |
From: Silvan <dmm...@us...> - 2002-12-17 08:25:47
|
On Sunday 15 December 2002 09:12 pm, Mark Knecht wrote: > IMPORTANT > > 1) No solo functions. As I was setting up MIDI tracks and listening to > things it suddenly dawned on me that while there is a mute button for > each track, there is no solo function. We need one. There is a Solo button. It's the [S] on the free-standing Transport wind= ow,=20 between the Metronome and the Record button. I'd like to see one of these on every transport toolbar as well... Havin= g to=20 go out to the main window to use the main transport for this is cumbersom= e. --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |