1.25 Beta Thread

[R.A.W.]

Host sync within Live 5.2 works fine

confirmed.
i ran a loop for about 20minutes, played and changed several arrangements meanwhile, changed manual sync on and off and had no drop-outs, double-triggers or whatever. works like a charm!

-------

i noticed one minor issue while playing back loops though:
lock to loop is activated all the time and i switch the number of beats in the arranger with RMB. when i reach 32 beats, the next RMB, which sets the arranger back to 8, causes a very short audio-dropout. lowering beats manually with dragging in the box doesn't do this.

[Maniah]

i noticed one minor issue while playing back loops though:
lock to loop is activated all the time and i switch the number of beats in the arranger with RMB. when i reach 32 beats, the next RMB, which sets the arranger back to 8, causes a very short audio-dropout. lowering beats manually with dragging in the box doesn't do this.

I couldn't reproduce this. By the way, after 32 beats, does the arranger go to 4 or 8? It should go to to 4 then 8.

[R.A.W.]

it goes to 4, i just messed with the numbers.

i can definately reproduce it, just switch while a bassdrum or snare is played.. i also could reproduce this in eXT, though it doesn't dropout everytime (and much less than in live).

[edit]removed mp3 example[/edit]

[ohm]

Quote:
i noticed one minor issue while playing back loops though:
lock to loop is activated all the time and i switch the number of beats in the arranger with RMB. when i reach 32 beats, the next RMB, which sets the arranger back to 8, causes a very short audio-dropout. lowering beats manually with dragging in the box doesn't do this.


I couldn't reproduce this. By the way, after 32 beats, does the arranger go to 4 or 8? It should go to to 4 then 8.

First of all: it does go back to 4, not 8.

And yes: there is a dropout if you go from 32 to 4 beats, and the playback position is beyond 4 beats - no way to work around this, because the event being played is deleted when you get rid of the 28 beats. The only workaround I can think of is to delay the request for lowering the arrangement duration until the next event is done playing but what if that event is 10 seconds long? I'm sorry this is just too complicated to fiddle with just to get rid of a short dropout - it you really need to change the duration of the arrangement while it's playing, simply do it while the first slices are playing.

[R.A.W.]

And yes: there is a dropout if you go from 32 to 4 beats, and the playback position is beyond 4 beats - no way to work around this...

yep, i already thought so.. and that's why i wasn't refering to it as a bug but a "minor issue".
it's no problem, leave it like it's now, i made moves you'd normally don't when playing live - i just wanted to let you know, but as it would be too much coding for such a little thing, it's absolutely ok with me!

[GilJ]

I just found 2 little bugs in Liveslice (seems to work with all the versions of Liveslice)

BR1:
1- Lock a loop in an arrangement
2- RMB on pitch button (set range to 48 for example)
3- Pitch up all the events in the arranger to the max
4- Reset the range parameter (= 0)
The Events' graphics are not correctly updated
-----------------------------------------------------

BR2:
1- Create this structure of folders: C:\sfx\125bpm
2- In Liveslice, browse to the 125bpm folder
The path is not correctly displayed in the File browser
-----------------------------------------------------

Can anyone reproduce these bugs here?
Otherwise, just wanted to say that Liveslice v1.25 rocks

Thanks,
GilJ.

[R.A.W.]

BR1:
The Events' graphics are not correctly updated

i can't reproduce it here.. works like a charm in eXT beta v1.4 26-nov-2005.

BR2:
The path is not correctly displayed in the File browser

confirmed.
that's an odd issue.. it seems to be related to the 'length < 4 chars' of the folder name, e.g. i tested this one D:\ts\125bpm and it's the same.