liveslice 1.45 beta thread
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRian
- 508 posts since 8 Dec, 2004 from Belgrade
Bug1: Liveslice responds to midi channel 1, altrough channel 2 is selected in liveslice settings.
bug2: selecting cc as control source in settings doesent lead to showing cc numbers, it still shows notes. In second try, it shows numbers, but it always resets to all...
How to make midi controls work? It still doesen't act as expected...
bug2: selecting cc as control source in settings doesent lead to showing cc numbers, it still shows notes. In second try, it shows numbers, but it always resets to all...
How to make midi controls work? It still doesen't act as expected...
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
You can repitch and stretch alright, but the algorithm only sound good on percussive material. I'm using the most common algorithm in slicers that leave the beginning of each slice intact and only stretches the last part of each slice, by simply ping pong looping the last 40 ms. You completely avoid stretchihng artifacts, and can still fill out those annoying gaps between slices.ttoz wrote:hi, just to check, does this allow pitch shifting without altering time? Also, what algo does this use?ohm wrote:here's the list of new features:
- time stretching
The reason I'm not using one of the common generic time stretching algorithm is that they just sound bad on drums.
I'm aware that a lot of users actually use liveslice for much more than drums, but for now I'm focusing on slicer features.
Later on I'm probably gonna play around with some of the available stretching libraries and try applying them only to the tail of the slice to see how that works. This could be customized to stretch the whole sample if you are playing back pads / bass in liveslice, and liveslice would be much closer to an ableton live clone.
Personally I'm using energy xt 2 when I need to stretch non percussive material though, so I don't have a personal need to add this functionality to LiveSlice.
http://www.livelab.dk - slice up your life
-
- KVRer
- 6 posts since 22 Feb, 2007
Fair play ohm, i utilise several programs for stretching/re-pitching of material, and feel that liveslice is the best for anything percusssive. I always feel that a program that is focused on doing one aspect of its functionality really well (in this case liveslice and messing with drumloops and breaks) i get a much more stable and usable operation out of it. Thats only my opinion tho, and i can still understand other peoples desires to be able to apply liveslices said awesome functionality to other material.
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
Why do you need mono outputs? To speed up processing? Doesn't all hosts automatically convert to mono if you use for instance a mono insert?english wrote:FR - Mono outputs for 1.45 final pleaaasseee ohmy!
eng
If there's really a popular demand I'll add it - just need to know why, to decide how the best implementation will be. Would you need mono and stereo simultatniously (manually configure mono/stereo for the 8 outputs?) I'm thinking that a switch that forces the last four outputs to mono is the simplest for all, if it suffices.
http://www.livelab.dk - slice up your life
-
- KVRist
- 131 posts since 2 Apr, 2006
I'd like mono outputs ohm. Why use a plugin to do that? When it uses more CPU if it can be done in LS. Surely it keeps the work-flow more focused making mono outputs an option. Also when will we have the outputs in the arranger window as promised some time ago.
Parris........
Parris........
-
- KVRist
- 282 posts since 16 Mar, 2005
Sorry to screw up the atmosphere a bit 
, but it seems more logical to me that the current priority is to correct all the bugs reported by beta testers (special cheers to DarkStar 
) in order for LiveSlice to rock solid?
Don't get me wrong, I have also posted a list of FRs and am waiting for them impatiently, but if the current version isn't 100% 'reliable', it's not very wise to continue adding new features, don't you think so?
GilJ.
, but it seems more logical to me that the current priority is to correct all the bugs reported by beta testers (special cheers to DarkStar ) in order for LiveSlice to rock solid?Don't get me wrong, I have also posted a list of FRs and am waiting for them impatiently, but if the current version isn't 100% 'reliable', it's not very wise to continue adding new features, don't you think so?
GilJ.
-
- KVRian
- 508 posts since 8 Dec, 2004 from Belgrade
Fully agreeing with GilJ, there are too many issues and questions in current version, we have to concentrate on them... personaly, I don't see a point in adding mono outputs... maybe I'm missing something.
Sorry if this sounded harsh, it wasn't my attention
Sorry if this sounded harsh, it wasn't my attention
-
- KVRist
- 178 posts since 15 Mar, 2003 from Windsor, England
Ya ok, np 
Maybe for a later revision.
On a side note, anyone got LS working with Reaper ok yet? It seems to have slight audio glitches when playing back the actual slices, but playing the full loop from LS loop browser it sounds perfect. Anyone else tried it yet?
eng.
Maybe for a later revision.On a side note, anyone got LS working with Reaper ok yet? It seems to have slight audio glitches when playing back the actual slices, but playing the full loop from LS loop browser it sounds perfect. Anyone else tried it yet?
eng.