Loop Recorder BIG issue
Loop Recorder BIG issue Posted on: 16.07.2012 by Kecia Wnukowski I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere.I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% | |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Kecia Wnukowski 16.07.2012 | I know that actually few people use the loop recorder but I'm amazed nobody saw that/ or I'm missing a piece of info I didn't see elsewhere. I use an s4, and never had this issue before so it seems/sounds like a bug/change in 2.5 (and I just cant' find an explanation about that). My settings have always been and stayed for the loop recorder as 0% decay and 0% latency whatever the version, using cue(s) as source. Quantize is on. (quantize is off on the remix deck but I don't see that as very relevant as it shouldn't be affecting the loop recorder anyway). I tend to grab a loop inside the loop recorder, play it, stop it, replay it on time, never had an issue (before the recorded loop started from its starting point again, in sync, in time, no worries like it's supposed to behave). Now if someone could try this: take track, grab a loop from it, it plays (of course you should have a phase sound now but that's unimportant). Stop loop recorder play (stop) while the track is still running. Now press play again. The loop recorder is unsynced with the track. Stop the loop recorder. Press play again, it's still unsynced. Why the F% |
| Charline Dye 18.07.2012 | Thanks for the update!! When and if I update to 2.5.x I'll just use dry/wet to turn loop recorder on an off untill that is fixed. |
| Kecia Wnukowski 18.07.2012 | this is indeed a bug: TP-5560 stopping the loop recorder and then starting it again causes sync loss in 2.5 As soon as we have a solution we will release this as an update or we will contact you directly via email. |
| Kecia Wnukowski 18.07.2012 | I've sent a ticket to NI, I'll update the answer here eventually. |
<< Back to NI - Native Instruments S4/S2 Controller talkReply