1.4 beta and development thread
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
BR 1 and 2 have been fixed, BR 3 and 4 still unreproducable here, but I'll look further into it for the next update - more details would be helpful.
http://www.livelab.dk - slice up your life
-
- KVRist
- 282 posts since 16 Mar, 2005
Thanksohm wrote: BR 1 and 2 have been fixed,
For BR3, here are some more details, hope you'll be able te reproduce it:ohm wrote: BR 3 and 4 still unreproducable here, but I'll look further into it for the next update - more details would be helpful.
1 - Load 2 instances of LiveSlice in eXT (We'll call them LsPlayer & LsRecorder)
2 - Connect LsPlayer audio output to LsRecorder audio input
3 - Enable Trigger with host option for LsPlayer and LsRecorder
4 - Load a loop (4 beats) in LsPlayer (+ Lock to loop)
5 - Click play in eXT
6 - Click on rec in LsRecorder (in order to record the loop playing from LsPlayer)
7 - Enable sync (+ mon) in LsRecorder
8 - Click on start in LsRecorder
You can now hear the original loop from LsPlayer still playing, and the recorded loop in LsRecorder playing together; however, the 2 loops are not playing perfectly in sync
In order to confirm that, just record the loop again in LsRecorder by hitting the start button.
You'll notice that each time you record a loop, it is not recorded exactly 'in the same place' even if sync is enabled.
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
thanks GilJ - It'll have to wait for the next update though - 1.41 is already done and delivered.
http://www.livelab.dk - slice up your life
-
- KVRist
- 282 posts since 16 Mar, 2005
Thanks Ohm
Here's a small one for the latest release (1.41)
GUI not updated correctly when deleting a slice
1 - Load a loop
2 - MMB a slice in the slicer in order to delete it
The slice doesn't get deleted; however if the GUI is updated, the slice doesn't appear anymore (only a GUI refreshing issue)
Here's a small one for the latest release (1.41)
GUI not updated correctly when deleting a slice
1 - Load a loop
2 - MMB a slice in the slicer in order to delete it
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
yeah - I noticed that one - stupid mistake. The slicer is not updated when inserting, deleting and changing outputsGilJ wrote:Thanks Ohm![]()
Here's a small one for the latest release (1.41)![]()
GUI not updated correctly when deleting a slice
1 - Load a loop
2 - MMB a slice in the slicer in order to delete it
The slice doesn't get deleted; however if the GUI is updated, the slice doesn't appear anymore (only a GUI refreshing issue)
http://www.livelab.dk - slice up your life
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
[LiveSlice 1.4.1]
Just a quick look at this release
- Can confirm the above: and:
BR014 - Ctrl+v is not pasting the selected Event. Rather it looks like the "N'th slice" from the first loop (try a paste, select another loop into the first loop slot and you will see the pasted events change).
BR015 - sometimes (not sure when), the word "empty" was not displayed in the Loops pane.
FR016 - when an Arrangement is padlocked, can the Mute and Solo and Audition (RMB) functions still work?
Just a quick look at this release
- Can confirm the above: and:
BR014 - Ctrl+v is not pasting the selected Event. Rather it looks like the "N'th slice" from the first loop (try a paste, select another loop into the first loop slot and you will see the pasted events change).
BR015 - sometimes (not sure when), the word "empty" was not displayed in the Loops pane.
FR016 - when an Arrangement is padlocked, can the Mute and Solo and Audition (RMB) functions still work?
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
thanks, fixed the bugs and sending out an update today. Didn't come across the "empty not displayed bug" though, that'll have to wait.DarkStar wrote:[LiveSlice 1.4.1]
Just a quick look at this release
- Can confirm the above: and:
BR014 - Ctrl+v is not pasting the selected Event. Rather it looks like the "N'th slice" from the first loop (try a paste, select another loop into the first loop slot and you will see the pasted events change).
BR015 - sometimes (not sure when), the word "empty" was not displayed in the Loops pane.
FR016 - when an Arrangement is padlocked, can the Mute and Solo and Audition (RMB) functions still work?
As for your FR, I agree that there's no reason to lock the mute and solo buttons. I'll put it on the list.
http://www.livelab.dk - slice up your life
-
- KVRist
- 282 posts since 16 Mar, 2005
Thanks Ohm this quick 1.42 update 
I just have a question about the Play function in LiveSlice (since v1.4x):
In older versions, you could only Play one arrangement at a time when the Play button was pressed. Clicking on another arrangement would just stop the previous one and start playing the new one.
Currently, this behaviour is quite strange:
1 - Create 2 arrangements
2 - Select the first one
3 - Click on Play
4 - Select the second arrangement
The second arrangement doesn't start to play; I have to click on Play in order to disable it, then Play again (moreover, the first arrangement continues playing
)
I just have a question about the Play function in LiveSlice (since v1.4x):
In older versions, you could only Play one arrangement at a time when the Play button was pressed. Clicking on another arrangement would just stop the previous one and start playing the new one.
Currently, this behaviour is quite strange:
1 - Create 2 arrangements
2 - Select the first one
3 - Click on Play
4 - Select the second arrangement
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
[LiveSlice v1.42]
"The slicer is not updated when inserting, deleting and changing outputs" - fixed.
BR014 - fixed
BR015 - not reproducible, so far
"The slicer is not updated when inserting, deleting and changing outputs" - fixed.
BR014 - fixed
BR015 - not reproducible, so far
-
- KVRian
- 783 posts since 6 Jan, 2006 from Premià
Verified (in 1.4x on energyXT and Tracktion2).GilJ wrote:Thanks Ohm this quick 1.42 update
I just have a question about the Play function in LiveSlice (since v1.4x):
In older versions, you could only Play one arrangement at a time when the Play button was pressed. Clicking on another arrangement would just stop the previous one and start playing the new one.
Currently, this behaviour is quite strange:
1 - Create 2 arrangements
2 - Select the first one
3 - Click on Play
4 - Select the second arrangement
The second arrangement doesn't start to play; I have to click on Play in order to disable it, then Play again (moreover, the first arrangement continues playing
)
Plus a weird one (verified also in 1.4x on energyXT and Tracktion2):
1 - Load liveslice (note that there's 2 visible tracks)
2 - Try to load "liveslice demobank.fxb"
3 - Click Cancel on the search window
Cheers.
The mind boggles.
-
- KVRian
- 1263 posts since 15 Jun, 2004 from hamburg
it's not as weird as you think - confirmed btw.Juanjo wrote:Plus a weird one (verified also in 1.4x on energyXT and Tracktion2):
1 - Load liveslice (note that there's 2 visible tracks)
2 - Try to load "liveslice demobank.fxb"
Liveslice doesn't find "demo loop.wav" and displays a search window
3 - Click Cancel on the search window
Now the number of visible tracks is 1 (!)
Cheers.
here's the explanation: the demobank uses the demoloop which is hardcoded into the demoversion .dll of LS, while the full version doesn't come with that loop.
the fxb itself doesn't include the wav as well, so that's why you now get the filesearch dialog when loading it to the full version. and you get the 1 track coz that's the setting in the demobank (settings are saved with fxbs along).
-
- KVRian
- 783 posts since 6 Jan, 2006 from Premià
Indeed, thanks R.A.W. I'm used to the 1.3x demo and I just got my license with 1.40... moving from old demo version to new full version has proved to be a bit too much for my single neuron
The mind boggles.
-
- KVRist
- 30 posts since 13 Feb, 2006
Hey just wanted to report an issue I was having with the copy and paste function of v1.42. It works fine most times for single events in an arrangement (holding the left click on the area, then ctrl+v) but when I try to copy events from one arrangement to another my host, Live 5.2, shuts down. I'm unable to detail exactly what happens to create the error but it has happened to me twice today and both times while using the copy and paste function between arrangements. I'll try to narrow down what steps I took to create the error but for now here is exactly what I did before I encountered the crash.
-imported three short drum sounds
-create three separate tracks in the arrangment
-played the arrangement back
-selected events in one track and hit cntr+c (while still playing back)
-click on an empty arrangment, click on an empty track.
-hit cntrl+v
I should note that I tried these steps again later and was able to perform the function sucessfully. Btw, is LS capable of copying full tracks from one arrangement to another or even a full arrangement? It might be easier to do that than selecting multiple events to copy.
1-0ne
-imported three short drum sounds
-create three separate tracks in the arrangment
-played the arrangement back
-selected events in one track and hit cntr+c (while still playing back)
-click on an empty arrangment, click on an empty track.
-hit cntrl+v
I should note that I tried these steps again later and was able to perform the function sucessfully. Btw, is LS capable of copying full tracks from one arrangement to another or even a full arrangement? It might be easier to do that than selecting multiple events to copy.
1-0ne
-
- KVRist
- 282 posts since 16 Mar, 2005
I have had some weird behaviour with LiveSlice v1.42
I have tested it on 2 computers, on the first one I have some GUI problem (on renaming a recorded file, or changing the number of tracks), but on the second computer, it just works fine
I have been able to reproduce a bug difficultly (don't know if it has something to do with the other ones?) in eXT 1.3.6:
1 - Load LiveSlice
2 - Click on settings
3 - RMB Number of visible tracks
4 - Click on settings
5 - Repeat steps 2 & 3 & 4 (10 times
)
Exception EAccessViolation in module LiveSlice.dll at 000540A2.
Access violation at address 0205400A2 in module 'LiveSlice.dll'. Read of address 00000044.
I have tested it on 2 computers, on the first one I have some GUI problem (on renaming a recorded file, or changing the number of tracks), but on the second computer, it just works fine
I have been able to reproduce a bug difficultly (don't know if it has something to do with the other ones?) in eXT 1.3.6:
1 - Load LiveSlice
2 - Click on settings
3 - RMB Number of visible tracks
4 - Click on settings
5 - Repeat steps 2 & 3 & 4 (10 times
Access violation at address 0205400A2 in module 'LiveSlice.dll'. Read of address 00000044.
-
- KVRist
- 282 posts since 16 Mar, 2005
2 (more
) questions about the latest releases of LiveSlice:
1/ In the latest versions of LiveSlice (v1.41,v1.42), when you right click a slice it doesn't select it anymore.
Therefore if you want to put it in a track, you need to right-click (to listen to it), left click to select it, then left click again in the track to paste it.
In the previous versions of LiveSlice, we right-clicked a slice to listen to it, if we liked it, we just had to left click in a track to paste it there.
Has this behavior been modified intentionally?
2/ In the manual, in the Arranger section, it is written that:
Holding down CTRL when inserting the event will force the new event to be created exactly where the cursor is, ignoring existing events and snap settings.
However, when I hold down CTRL, it doesn't force the new event to be created exactly where the cursor is? Can anyone please confirm this? Thanks.
1/ In the latest versions of LiveSlice (v1.41,v1.42), when you right click a slice it doesn't select it anymore.
Therefore if you want to put it in a track, you need to right-click (to listen to it), left click to select it, then left click again in the track to paste it.
In the previous versions of LiveSlice, we right-clicked a slice to listen to it, if we liked it, we just had to left click in a track to paste it there.
Has this behavior been modified intentionally?
2/ In the manual, in the Arranger section, it is written that:
Holding down CTRL when inserting the event will force the new event to be created exactly where the cursor is, ignoring existing events and snap settings.
However, when I hold down CTRL, it doesn't force the new event to be created exactly where the cursor is? Can anyone please confirm this? Thanks.
