LiveSlice 1.47 beta thread

[audio_dude]

I use LiveSlice 1.47b3 in "instrument version" (tested in FL7 and FL8-RC2).


Please, see the pic below for more infos (it seems that the bug comes from "LiveSlice.dll").

Moreover (considering 1) the configuration described in the picture below, and 2) the pattern is actually playing) :
- the bug doesn't appear if there's no loaded sample in LiveSlice
- but the bug always appears when I load slices in arranger's very 1st track, and if I switch between all the open windows in FL and then going back to LiveSlice's GUI.

Hope this helps.



http://img249.imageshack.us/my.php?imag ... icera2.jpg

[Trip-]

Folks,
I'm sorry if these questions were answered before:

- How can I help beta testing this program (I'm using Logic Audio 5.5.1) ?

- I want to report a few 'bugs' or strange stuff with ver 1.46:
- What reffers to as C3 in the program, is actually C1 in Logic.
- The initial setting of pitch set option in the settings tab causes the
pitch to be lowered to minimum in the arrange when I press Play/Stop on
the transport in Logic. solution: removing that pitch set option
controller.

- A suggestion for a next version would be having the events replace their
corresponding event that you move it onto. Kind of like never having an
empty space when moving/mangling the events from one place to another.

I would like to say that this prog is amazing!
Simply awesome! Huge thanks goes to ohm for this... Not anything like it anywhere!

Philip

PS: If you need OSX beta testing on Logic 8, count me in

[audio_dude]

How can I help beta testing this program (I'm using Logic Audio 5.5.1) ?

Easy ! If you want to join the beta-list, just send a mail to ohm

I would like to say that this prog is amazing!
Simply awesome! Huge thanks goes to ohm for this... Not anything like it anywhere!

So true !

[Architeuthis]

Easily reproduceable crash in LiveSlice.

Using LiveSlice Effect:

Rec Start/Stop button will crash Reaper if clicked one too many times.

My computer:
Reaper 1.104
Core 2 Duo
4GB RAM
Windows XP

[ohm]

http://img249.imageshack.us/my.php?imag ... icera2.jpg

please try deleting the controller configuration in "other midi controller config" and see if that solves the problem. I fixed a bug related to the global parameter "set active loop" that could be responsible for the bug you describe.

It that doesn't solve the problem, please email me a fruity loops project that produces the crash, then maybe I can load it in the demo (or request a test version from image line)

thanks again.

[ohm]

Easily reproduceable crash in LiveSlice.

Using LiveSlice Effect:

Rec Start/Stop button will crash Reaper if clicked one too many times.

My computer:
Reaper 1.104
Core 2 Duo
4GB RAM
Windows XP

thanks,

not reproducable here unfortunately

I did notice however, that the LiveSliceEffect.dll I sent out was in fact beta 2, so the bug might be fixed in the actual beta 3 (I'll send it out right away, so please check again).

If it doesn't solve the problem, please send me a reaper project file, because I suspect some other liveslice settings to be responsible.

A screenshot of the settings page or your liveslice.ini file could also help.

[Architeuthis]

I got the e-mail. Also, did anyone yet report the bug where your channel settings in preferences aren't saved? They switch to default after you leave the setting page.

[Architeuthis]

Here's the crash video: http://shup.com/Shup/25170/ReaperCrashOnRecord.gif

Seems that when I try to play the project at 50bpm, LiveSlice stops working.

[ohm]

I got the e-mail. Also, did anyone yet report the bug where your channel settings in preferences aren't saved? They switch to default after you leave the setting page.

I fixed that long ago. Are you 100% you are using the latest beta? I just tried to verify but channel settings are just fine here, both on the gui, and the actual received channels.

[audio_dude]

please try deleting the controller configuration in "other midi controller config" and see if that solves the problem. I fixed a bug related to the global parameter "set active loop" that could be responsible for the bug you describe.

Nice ! You found the bug, and 1.47b4 runs fine ! Congratulations, ohm !


Anyway, maybe it's my fault, but I don't succeed in making the host trigger the slices (quite weird since I fully succeed in triggering arrangements using the host).

Please, could some users try this thing, because I don't know if there's a bug or if I miss something.

More infos :
- I tried and verified few MIDI channels, the port, the first and last used notes, and the selection is set to "sel.loop"
- "Trigger with host" is the only selected option


Thank you for your help because, actually, my host doesn't trigger the slices.


Again, congrats, ohm, for your very good work !

[ohm]

- I tried and verified few MIDI channels, the port, the first and last used notes, and the selection is set to "sel.loop"
- "Trigger with host" is the only selected option


Thank you for your help because, actually, my host doesn't trigger the slices.


Again, congrats, ohm, for your very good work !

"Trigger with host" should not be selected. It actually means: trigger with host transport - and what it does is: start playback of the selected arrangement when you click play in the host. (yes the labeling could improve a bit, I know).

On the screenshot you were not using the piano roll in FL, so you only sent out one midi note - you can check what note that is, by going to the liveslice settings screen, add a controller and click "midi learn" - that will show you what event liveslice is receiving.

It's probably just out of range of the selected notes in liveslice.

hope this helps

[Architeuthis]

I got the e-mail. Also, did anyone yet report the bug where your channel settings in preferences aren't saved? They switch to default after you leave the setting page.

I fixed that long ago. Are you 100% you are using the latest beta? I just tried to verify but channel settings are just fine here, both on the gui, and the actual received channels.

Alright, it seems the problem is fixed like you said. However, that crash was made with the newest version that you sent. So please look into that.

[ohm]

Alright, it seems the problem is fixed like you said. However, that crash was made with the newest version that you sent. So please look into that.

but the one I sent was beta 2 wasn't it? please try again, as I could not reproduce it

[audio_dude]

"Trigger with host" should not be selected. It actually means: trigger with host transport - and what it does is: start playback of the selected arrangement when you click play in the host. (yes the labeling could improve a bit, I know).

Ok, thank you, ohm, it makes perfect sense (because I was also wondering why I could listen to the arrangement instead of the slices )



By the way, I think there's another bug :

using a correct MIDI config, and the Piano Roll, I actually succeeded in triggering my slices from the host , but as soon as I went back to the LiveSlice GUI, my current selected loop (the loop in the list which contains the used loops, the list in the upper-left corner of the GUI) was immediately replaced by the very last entry of this list (and it was actually an empty entry !).
The result was there were no more sound coming from LiveSlice since the "sel. loop" was the option I chose in the "settings" tab, and the selected loop was now an empty entry.


Hope this helps.


Thanks again, ohm



PS : by the way, what is the difference between loading "LS instrument" and "LS FX" ?

[Architeuthis]

Alright, it seems the problem is fixed like you said. However, that crash was made with the newest version that you sent. So please look into that.

but the one I sent was beta 2 wasn't it? please try again, as I could not reproduce it

You sent 1.47 beta 4. Did you make sure you were trying to reproduce the crash with the host set at 50bpm? I dunno if you got my crash video or not, but there's the link again: http://shup.com/Shup/25170/ReaperCrashOnRecord.gif