1.4 beta and development thread

[ohm]

Can't reproduce this one. I tried loading EXT vst on a midi track in the sequencer, adding a liveslice there and everything works as expected - anyone else have this issue? How about the other controls (buttons etc.) are they disabled too?

If you are on the beta list please try again in a few days when the next beta is out - if not, please drop me an email.

[S.HUSH]

Yes, i am on the beta (i was former pharaoh). I did send you an email with me new email address. Do you want me to resend?

The other controls work fine.

[ohm]

Yes, i am on the beta (i was former pharaoh). I did send you an email with me new email address. Do you want me to resend?

The other controls work fine.

I have your email, I'll change address and all that before I send the next beta, in which I'll be addressing the issue in some way or other. And I will try, although it is tempting, not to refer to you as the artist formerly known as former pharaoh, because you probably heard that one a dozen times before

[S.HUSH]

And I will try, although it is tempting, not to refer to you as the artist formerly known as former pharaoh, because you probably heard that one a dozen times before

Actually, not as many times as i thought i would.
*thank god*

[R.A.W.]

What video drivers are you using?

latest catalyst

And what audio card?

ati radeon 9600

anyway, the latest beta i got from jacob almost fixed my issue, right now it seems that it's not a gfx issue as the drop-outs only occur when i interact with the gui using my mouse. when i use midi-notes or cc which change the grafics, everything is just fine.
p.s.: just in case it's important, i use a logitech mx 518 (yes, the gamer mouse ) with it's factory drivers and the setpoint application.

[kejkz]

I know it maybe sound silly, but I had some mouse problems with my previous computer. Whenever my mouse operated as USB device, just moving it cause cpu spikes and audio dropouts. Althrough I doubt that's your case R.A.W., maybe you can try to put it in ps/2 port just to be shure.

[R.A.W.]

my mouse is already used over ps/2 (i rather spend another interrupt than a usb port while wasting the ps/2 port ).
thanks for the hint anyway.

but i checked the logitech site yesterday and found new drivers for the mouse which i'll install today. we'll see if they make any difference in this regard.

[R.A.W.]

ok, updated drivers, no change.

still some (though with the beta fewer) drop-outs when i interact with the gui. i checked in eXT and phrazor for now, will check live 5 and 6 beta soon.

[ohm]

I'll send you another tester soon - you say it's not only the randomize function that causes the problems?

[R.A.W.]

you say it's not only the randomize function that causes the problems?

in the 1.43 final i had drop-outs also when i clicked a track to highlight it (using the fxb i posted). this seems to be gone with the tester you sent me, which only has a few drop-outs when i use the randomize (haven't checked the drag and drop of slices or other functions that change the view of the waves yet).
right now i'm thinking it could be my system because i used asio4all with the onboard chip for now (you know i changed my mainboard ).
i have a little more time tonite so i'll check it with my audiowerk8 card and the other hosts.

[R.A.W.]

ok, got the new tester and everything is fine now, no drop-outs anymore!

thanks, jacob!

[ohm]

glad it helped - the best part is that the speed improvement will benefit everybody - the gui is much more smooth now. I've been hunting for the cause of these gui slowdowns for a while - your report got me on track. Seemed the gui framework I'm using has problems making large bitmaps smaller, so I created a "mipmap" like they do in games, to speed up the display of waveforms.

[kejkz]

... I just received a new version and it works very well for now. There is only one little graphic glitch in current beta in new banks section: trigger indicator is only showing first 24 arrangements. When you switch to bank 2 or three it shows indicator from first one, but not their own...

I will continue testing...

[S.HUSH]

WIth LS setup within EXT VST (using XT stand alone as host), i cannot trigger arrangements with my LMB (meaning i cannot trigger the cells). It works fine if i just load LS onto the main window of EXT stand alone, but if i load it into a EXT VST within EXT stand alone, then the issue arises.

I have a better understanding of what is going on with this issue so let me explain a bit better.
The "Play" button in the arrangement is supposed to be global so once it is activated, ALL arrangement cells can be triggered independently/together (depending on one's settings) either using MIDI or the LMB.
The issue i am having is, LS is having me press the play button for EACH arrangement as opposed to working globally.
This happens within Ableton Live and within EXT.
With the latter host, the issue only arises when i use LS within EXT VST.
If i use LS in the main window of XT, i have no issue.

Both the instrument and FX version of LS do this using latest beta.




[second issue]
I notice after deleting a recorded loop in the Loops Menu (Cntrl/RMB), the arrangement track still shows small partial slices (pressing Lock to Loop on any arrangement track shows these slices).

[GilJ]

I have a better understanding of what is going on with this issue so let me explain a bit better.
The "Play" button in the arrangement is supposed to be global so once it is activated, ALL arrangement cells can be triggered independently/together (depending on one's settings) either using MIDI or the LMB.
The issue i am having is, LS is having me press the play button for EACH arrangement as opposed to working globally.
This happens within Ableton Live and within EXT.
With the latter host, the issue only arises when i use LS within EXT VST.
If i use LS in the main window of XT, i have no issue.

Both the instrument and FX version of LS do this using latest beta.

I think I noticed (and may be even reported here...) the same 'bug' some time ago, but with eXT Standalone ! (however I found a 'solution' to this issue )
1 - Start eXT Standalone (but don't hit play in eXT, the main sequencer should be stopped)
2 - Add LiveSlice
3 - Load 2 loops in LiveSlice
4 - Lock each one to a different Arrangement (I.E. C1 and D1)
5 - Select C1 Arrangement and hit Play in LiveSlice
6 - Select D1 Arrangement
The D1 Arrangement doesn't start to play. You must hit play again (meanwhile, C1 Arrangement continues playing instead of stopping itself)
I have come to the conclusion that all this problem is due to the fact that eXT sequencer has not been started ! If you hit on play in eXT (main sequencer), then changing Arrangements in LiveSlice will behave as it should (only one Arrangement playing at a time when the cells are triggered with LMB)
You can reproduce this 'bug' with many hosts, if you don't start the host's main sequencer...

S.HUSH, I think that the problem you are having is roughly the same one, I.E. the LiveSlice instance you loaded in the eXT VST isn't getting some kind of 'timing information' it should (as like loaded in eXT Standalone without hitting Play in eXT)

Hope I wasn't too confused with my explanations

Regards,
GilJ.