bugs n' fixes

[fabi]

Thanks for the info everyone, all reported bugs have been fixed now. There'll be an update very soon, I just need to polish the new zoom and pan functionality of the slicer. If you have experienced crashes you can get a beta preview of the new liveslice 1.1 demo by emailing me on jacob at livelab dot dk - I'm working hard to make this next update 100% stable on all PC's.

- Jacob

i am so looking forward to purchasing this. i think in four days i should have the money to do so.

i had been 'in the market' for a beatslicer for ages, but nothing really impressed me. here, the GUI is incredibly usable and development/support pace seems about perfect.

thanks in advance for giving my money a new home.

[GilJ]

Ohm,
I sent you a mail... just wanted to post here in case it went directly to your spam folder
Gil.

[headcase59]

i played with v1.04 in SX3 for about an hour - no crashes. i've now made my purchase and i love the tech support!

[ohm]

headcase59: GilJ didn't imply that I delete his mails on purpose, I just happen to have a spamfilter on my email server that eats his emails (it ate the last one too)
but I'm glad you like the tech support and it's great to have all those positive comments in a thread with such a horrible title

[R.A.W.]

and it's great to have all those positive comments in a thread with such a horrible title

well, as the crashes are fixed now, you could just change the title to something like "Official BR consolidation thread"

[headcase59]

headcase59: GilJ didn't imply that I delete his mails on purpose, I just happen to have a spamfilter on my email server that eats his emails (it ate the last one too)
but I'm glad you like the tech support and it's great to have all those positive comments in a thread with such a horrible title

dun worry - i know you weren't trashing his mail
*changing post topic*
how's that? it did seem a bit harsh

[ohm]

I feel much better now

[GilJ]

I have a question about the state of the 'Lock to loop' button. Actually I would like to know how it works
When you first lock a loop, the button is in the 'enabled' (=blue) state, if you move the events and want to lock the loop again, you must click 2 times on it (I.E. one time to disable it -as it was still enabled from the previous time- and one more time to lock again )
Shouldn't the lock button be used only 'once' (like the Clear or quantize button) each time?
Maybe I've been missing something here

Thanks guys,
Gil.

[R.A.W.]

no, you are right, it only works like you expect it in combination with the "dice" or "clear", as soon as you click them, "lock to loop" is disabled.

everything else leaves the lock-button enabled so you have to click it twice to get the original again.
it's a minor issue and i'm sure that jacob can change that so that "lock to loop" gets disabled (=white) as soon as the shift ([<] or [>]) and quantize buttons are pressed.
in addition it would be good to disable it as well as soon as events are moved or inserted/removed/deleted.

until then just click twice.

[edit]
i just had another idea..

how about if the button would work like the clear-button?
clicked once it just blinks short, the loop gets reset to the original and right after that the button is disabled again and ready to lock the loop at the next use?
[/edit]

[ohm]

yep, that's an easy fix. It's supposed to be cleared whenever you change the track (except the parameters). The idea behind it is to let you hear your slices while you slice.
The fix can just make it to the next update.