Hey guys!
I am sure I am not the only who notices that CALF Vintage Delay does not
clean its buffer when you stop playing the tune in a sequencer. But just to
be sure,
here is a description of what happens.
1. You are in a sequencer (I personally worked in my first Linux days in
LMMS, today work mostly in Qtractor).
2. You use CALF Vintage Delay.
3. You stop the track in the middle.
4. When you put the playhead to the beginning of the tune and start to
play, CALF Vintage Delay will output leftovers from the previous position.
This is not only annoying, most of the time it is confusing and even
interferes with rendering a song.
I don't know if I am correctly calling it a "buffer", but obviously CALF
Vintage Delay does not clean up its memory after being stopped.
Can anyone look into this, please?
--
Louigi Verona
http://www.louigiverona.ru/
On , Louigi Verona <louigi.verona(a)gmail.com> wrote:
> Seems obvious, but wanted to make sure that Luppp has sync of different
> loops?
> If not in stretching, than at least in being able to trigger loops
> together?
Hi Louigi,
Currently luppp's sync is like this:
-resampling to achieve loop lenghts that correspond with "bars" in music
terms.
-BPM is currently set to a value, but dynamically modifyable trough MIDI (&
GUI soon)
-Resampling means that the pitch of loops will go up / down depending on
playback speed
I've fixed the pitch issue using the SoundTouch library, however it
glitched & popped quite
a bit too much. Either a better implementation using SoundTouch, or else
I'm going to use
libRubberBand, which seems to be the more widely used timestretch library.
Due to the resample to "bars" code, if you record some material, but not to
precise bars lengths
it will be resampled (just a little bit) but will sound aweful in the
harmonic sense :(
See the following issue: https://github.com/harryhaaren/Luppp/issues/2
Cheers, -Harry
Hi all Linux Audio Developers!
With recent changes in the world of live looping software I've decided to
open my private repo of Luppp.
Lots of information & sources available here:
http://harryhaaren.blogspot.com/2012/01/luppp-source-opened-but-still-pre-a…
Thanks to the entire LAD community for supporting me while I have been
working on this project!
Cheers, -Harry
On 17/01/12 18:15, Tvrtko Ursulin wrote:
> On 17/01/12 17:57, Niels Mayer wrote:
>> Re http://code.google.com/p/mudita24/issues/detail?id=6
>>
>> In http://code.google.com/p/mudita24/issues/detail?id=6#c5
>> tvrtko at ursulin wrote:
>>> I had a small peak in your code and it looks you reference this
>>> control by name, not numid, so the bug is probably somewhere else.
>>> I'll grab the current version and give it a spin...
>>> [...]
>>> Right, have 1.1.0 14 runnig now. A more detailed description of the
>>> bug is that meters seem to be sampled once on startup but then they
>>> are otherwise stuck/static. Pressing "Reset Peaks" clears them and
>>> puts in to "(Off)" state.
>>
>> .............
>>
>> Hunch: if the meters work once, the meters work, IMHO. This is a
>> clocking issue. Also, if talking of the level of the "Digital Mixer"
>> meter to the left, you have to make sure that the inputs to the
>> digital mixer are "live." However the mention of "stuck state" means
>> the ICE1712 metering registers are putting out DC at the digital level
>> that they were at when they lost clock.
>>
>> The issue is probably somewhere else. I've seen this sort of thing
>> happen before with the ICE1712 chips when they're "locked up" waiting
>> for clocking, perhaps because the external spdif input in "Hardware
>> Settings"->"Master Clock"->"S/PDIF In" is selected. Even more likely,
>> there's a lockup, because "Multi Track Rate Locking" or "Multi Track
>> Rate Reset" are selected in "Hardware Settings". Deselect, kill any
>> processes using the devices, and start over again.
>>
>> For details, see
>> http://alsa.cybermirror.org/manuals/icensemble/envy24.pdf :-)
>>
>> The lockup will "stick" if the audio device is in use, for example if
>> pulseaudio has grabbed it, or if it's still lingering around in some
>> spinning or zombie jackd. So changing the settings in the ICE1712
>> control panel may not actually take effect until the device is
>> relinquished and can be overridden out of it's locked state via the
>> control panel.
>>
>> Note that this is all said as a hunch. I am not even running an OS
>> that supports the latest GTK changes and I am a Fedora user so there's
>> little chance I'll switch to Ubuntu without getting paid for it. So I
>> guess I'll find out if it's related to later versions of ALSA, GTK, or
>> Linux next time I setup a new machine.... and then I'll stick the
>> Terratec and it's lovely enclosed Yamaha DB50XG clone (NEC XR385) into
>> the new machine, pull down the latest mudita24 from SVN and give it a
>> try again.
>
> I appreciate it was a hunch but I wouldn't have reported that meters are
> not working if I couldn't hear any audio - which would be the case with
> a clocking problem. :)
>
> So no, it is not that and envy24control works fine for example.
>
> Unfortunately I am not a GUI programmer so I wouldn't know how to
> approach any possible GTK issues myself. It was just an observation I
> made in an unrelated thread on LAU which got turned into a bug report.
> It is not terribly important to me I just like the real scale in
> mudita24 as opposed to useless numbers in envy24control.
Here is a fix:
--- envy24control.c (revision 14)
+++ envy24control.c (working copy)
@@ -2404,7 +2404,7 @@
/* NPM for efficiency&power-savings, replaced multiple 40ms&100ms timeouts
for each of the callbacks contained here, with a single 100ms one which
calls gtk_timeout_add(100, (GtkFunction)envy24control_poll, ...) */
-void envy24control_poll() {
+gboolean envy24control_poll() {
level_meters_timeout_callback(NULL);
master_clock_status_timeout_callback(NULL);
internal_clock_status_timeout_callback(NULL);
@@ -2412,6 +2412,8 @@
rate_reset_status_timeout_callback(NULL);
if (card_has_delta_iec958_input_status)
iec958_input_status_timeout_callback(NULL); /* NPM */
+
+ return TRUE;
}
QasTools version 0.17.0 is available.
QasTools is a collection of dektop applications for ALSA.
Changes:
* all: setting names for state save/restore changed/regrouped
* all: smart main window sizeHint() to get a useable window
size after leaving fullscreen
* all: new common info dialog - uses QListView page
selection intead of tabs
* shared: device selection style tweaks: selected item
now emphasized by a thin frame
* shared: device selection style tweaks: Rounded selection area
* shared: use QSplitter instead of QDockwidget for device selection
view. It couldn't be detached anyway and size restoring
works more reliable.
* qasconfig: settings directory changed to shared ~/.config/qastools/
(was ~/.config/qasconfig/)
* qasconfig: new basic command line options (--version, --help, etc.)
* qashctl: new basic command line options (--version, --help, etc.)
* qasmixer: new application icon
Homepage with more information
http://xwmw.org/qastools
Project page
http://sourceforge.net/projects/qastools/
Happy volume changing!
-- Sebastian Holtermann
Hey All,
I've just set up the GitHub repo I'm using to host Luppp with an Issue
tracker:
Please redirect all bugs you encounter there. Also please check that its
not filed already, I've already put some bugs in there :)
Excuse the new topic for this announcment,
Cheers, -Harry
Hi all,
The libsndfile source repository has been moved to Github:
https://github.com/erikd/libsndfile
My hope is that this will make will make it easier for others to
contribute and I also gained an issue tracker and a patch queue.
Cheers,
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/