hemmer / mlrvst Goto Github PK

I had 1 sample loaded using 2 different channels. Added the same sample to a third different channel and set the mode to play once and triggered the sample on the fifth slice. Then it locked cubase.

Occasionally the VST thinks buttons are held down and therefore calls the stop combo. I need to try and work out exactly what causes this, can't reproduce yet.

1. load sample
2. set sample to "loop" mode
3. change playback to "rev"
4. hold down button on row
5. playback proceeds only to that button, then restarts from the beginnig

contrast this with forward loop mode, where as long as the button is held down, playback of the sample proceeds past the held button, to the end, then restarts from the beginning.

i actually kinda like the ability to do inner loops like this, without needing a pattern recorder. it would be nice if i could do something like hold down one button in a row, then hold down another button on another spot in the same row, and mlrVST would just loop that section, with direction dependent on the playback setting for that row. just hit "latch" (or maybe registering two button presses simultaneously automatically engages "latch" mode), and it keeps playing that inner loop.

but even if this doesn't make it as a feature, "rev" and "forward" play behavior should still work the same way when "loop" mode is engaged. thanks!

Key input doesn't work when clicking on text fields / sliders etc on Windows (works fine on mac). There is a fix which requires editing JUCE core files (not part of the project here on github). The full details are listed in this post:

http://www.rawmaterialsoftware.com/viewtopic.php?p=17454#p17454

(hopefully this will be fixed in upcoming releases of JUCE)

problem: file drag and drop doesn't work on linux.
workaround: the file load button implemented on the left side, which functions as it should.

it seems that FileDragAndDropTarget may be deprecated:

http://www.rawmaterialsoftware.com/viewtopic.php?f=2&t=7204
http://juce.git.sourceforge.net/git/gitweb.cgi?p=juce/juce;a=commit;h=f4c4f310e1797886ae2f82a6f71b17d3f62d616a

i also found s'more stuff on how d&d is handled on linux:

juce/src/native/linux/juce_linux_Windowing.cpp

If I Ctrl-shift-drag on one of the sample strips, I can drag past the end of the sample which can lead to a crash.

Still trying to work out what's causing this one, sometimes pressing play / stop in Ableton causes the whole DAW to hang.

If you close the host without closing the GUI first, memory leaks are reported.
NOTE: if you close the GUI then the host there are no issues.

what about making mlrVST show up as a VST instrument, rather than a VST effect? right now, it only appears in the "Track DSPs" section of renoise, which means mlrVST is saying to the host that it's an effect, not an instrument in its own right. this makes routing complicated, since renoise and other hosts i've tried route audio and effects differently depending on whether you're trying to play a VST instrument, or run audio through a VST effect.

Self explanatory!

The new playspeed slider arrangement (which allows dragging to negative values) sometimes only plays a very buzzy sound, only a couple of samples long.

This is due to the thumbnails reopening / regenerating, ideally these should be stored in the PluginProcessor.

Potentially pretty serious bug where at the end of a sample, sometimes a very loud pop can be heard. This is potentially damaging to speakers.

It might be due to the linear interpolation between sample points going wrong (for play speeds != 1) and wildly miscalculating the final sample.

GUI (both host and plugin) can become sluggish when many channels are playing. This is probably due to the way that the code currently handles repainting during playback (i.e. repaints occur everytime the playback percentage is recalculated).

Self-explanatory, probably to do with sysex messages...