@lukesleepwalker said:I am a big fan of default options in settings. CUE option for Groups. CUE option for overdub and mute Loops.
Jack;353" said:I think I agree, an option in the settings would be less confusing as well. Something like 'CUE mute' and 'CUE overdub'. The question is now, would these new CUE functions follow the behaviour of the main CUE button in the transport view or be completely independent? Any ideas?
@ricksteruk said:Hmm tricky - it would be good to set CUE options for group playback, Mute and Overdub - but I wonder what the current CUE button would do? Would it then be redundant? Would it apply to all tracks or to just the selected loop or group? What would it affect? Only the Mute Cue, only Overdub Cue.. or both?How about this?If the existing CUE was replaced with two cue buttons: a "Play/Mute" cue button and a "Rec/Overdub" cue button. (with MIDI binding please ) These buttons would apply to the selected group (or loop) and would change to reflect the state of the current group/loop as you select different ones. The Settings menu would hold defaults for Group CUE, Loop Mute CUE and Loop Overdub CUE.
@lukesleepwalker said:It would be interesting to know how many users use that Cue button in the transport. I don't see the need for it with my use case and it's tough for me to imagine someone going back/forth regularly. (Would love to see someone using it to learn more.) To me, the Cue behavior is something expect to be global and sit in a settings panel.
Jack;397" said:Just wondering how you guys would expect overdub CUE to behave? Specifically i'd like to know if, after overdub has CUE'd in, should it stop recording automatically after one cycle of the loop or rather continue recording indefinitely?@dubbylabby, @lukesleepwalker, @nonchai, @ricksteruk any thoughts?
Jack;402" said:Thanks guys, it's invaluable beeing able to hear your opinions. All points made are valid but do conflict somewhat. Maybe there should be two options for overdub CUE then to suit all needs. One for overdub CUE in and another for CUE out.
@ricksteruk said:I agree simple is best!!!! Whatever options are added behind the scenes the default setting should probably be to just overdub one pass of the loop when CUE is on.Personally I like to overdub with no CUE at all and just use my MIDI foot switch to start and stop overdubbing manually. Just having the current CUE button assignable to MIDI would be great for me to enable this without touching the iPad. ***I think on the whole my CUE default preferences would be:GROUP SWAPPING CUE - ONLOOP RECORDING CUE - ON (unless I wanted to use first loop to set a tempo)LOOP MUTE/UNMUTE CUE - OFF (normally I'd want to stop/start loops immediately)OVERDUB CUE - OFF (manual)wonder what other people would do? I guess it might depend if you use a MIDI footswitch or touch iPad screen.*** I took part in / helped set up a Looping workshop with SK Shlomo yesterday ( I set up the house PA and brought my CCK and USB digital mixer so we could get a good quality connection from people's iPads into Shlomo's rig. ) ..... anyhow my point is that Shlomo said in his experience using touch screens live does not work for him, as you need to be looking at the audience not staring down at the gear all the time - and so he prefers physical buttons whereby you can feel the button with your fingers and know you'll actually hit it. I think GTL's CUE is a great feature as it helps eliminate this uncertainty (especially when running to a metronome or Ableton Link). I did mention GTL to Shlomo and all the people on the workshop
@lukesleepwalker said:Will you need beta testers soon, Jack?
ricksteruk;517" said:I've got a friend coming tomorrow and I'm going to show him GTL and iPad so he can see if he wants to replace his simple Boss pedal. He's a guitarist. One thing I know he does live currently is to create a loop during the middle of a piece... so he just manually starts and stops recording to create the loop/tempo (and hopefully gets it right or it really puts off the rest of the band )So, I've just been having a go with "no click recording" (no Cue) to see how this would work for him. The first loop works just as expected - it's entirely up to the accuracy of your stomps wether the loop sounds any good or not.Next... When I try adding the second loop I can press record at pretty much any time and GTL syncs it with the initial loop which is great However - I noticed it does make a difference when you press Rec again to stop recording. If you stop recording after the same length as the initial loop then no problem - they sync up neatly. But if you do a shorter or longer loop it seems that GTL is dividing initial loop into 3 and syncing with these thirds.I wonder if there is some preference setting that explains what GTL is doing?? @Jack Say for example you have recorded 4 bars as your first loop (probably quite a common occurrence I'd say) - then maybe you want to just add a 1 bar or a 2 bar phrase to it.So press record on Bar 1, then press again on Bar 2 and you'd get a 1 bar loop right?Nope.. you get a 1 1/3rd bar loop.If you press record on Bar 1 then stop on Bar 3 you get a 2 bar loop right?? Nope.. you get a 2 2/3rds bar loop I experimented turning on Cue and found that it also seemed to be relating to the 1/3rds of the initial loop.Oh any btw.. Cue was very useful for swapping between verse / chorus sections so it will be great to have that as an option for Group playback and not recording for these kind of "no click track" sessions.