List of things that simply don't work.
-
- KVRer
- Topic Starter
- 17 posts since 9 Aug, 2015
1. Collective randomly stops playing sound.
I have two tracks with Collective and both are having this problem. You can see the keys pressed inside the plugin but there is no sound. Restarting project sometimes help, but not often. Restarting Waveform does the job.
It can bork itself in the middle of MIDI clip. Just because...
Also it seems to be Collective problem because putting different instrument on the track doesn't have that problem.
2. Moving playback line/cursor is REALLY choppy whenever I put MidiEditor in separate window.
It just doesn't update when mouse is moving. Inside the Editor window it's smooth. On the main screen it looks as if I was using potat PC.
3. Looping MIDI clip makes the first note not working.
Again it's something that likes to break after some time. Put a note at the very beggining of a clip and the only thing that comes out is click. After delaying that note ~20ms it works as intended.
4. In MIDI editor - selecting notes with right mouse button is a recipe for a quick crash.
Also the selection box stay visible after mouse release.
5. vstInstruments can break into not having sustain, just single pluck.
It happens with Collective and few other instruments. Sound is stopping after the first sample(???)/frame.
6. Velocity number indicator in MIDI editor is not updating while changing it with SHIFT + Mouse.
Only after selecting the note once again i returns current value.
7. Sometimes putting vst on master bus will simply not work.
In that case the whole project is borked because there is no way in million years master bus will take a vst.
With all these shenanigans using Waveform is simply not an option
Some of these were a problem in T6. Waveform just added new ones
Please, crush these bugs
Cheers
I have two tracks with Collective and both are having this problem. You can see the keys pressed inside the plugin but there is no sound. Restarting project sometimes help, but not often. Restarting Waveform does the job.
It can bork itself in the middle of MIDI clip. Just because...
Also it seems to be Collective problem because putting different instrument on the track doesn't have that problem.
2. Moving playback line/cursor is REALLY choppy whenever I put MidiEditor in separate window.
It just doesn't update when mouse is moving. Inside the Editor window it's smooth. On the main screen it looks as if I was using potat PC.
3. Looping MIDI clip makes the first note not working.
Again it's something that likes to break after some time. Put a note at the very beggining of a clip and the only thing that comes out is click. After delaying that note ~20ms it works as intended.
4. In MIDI editor - selecting notes with right mouse button is a recipe for a quick crash.
Also the selection box stay visible after mouse release.
5. vstInstruments can break into not having sustain, just single pluck.
It happens with Collective and few other instruments. Sound is stopping after the first sample(???)/frame.
6. Velocity number indicator in MIDI editor is not updating while changing it with SHIFT + Mouse.
Only after selecting the note once again i returns current value.
7. Sometimes putting vst on master bus will simply not work.
In that case the whole project is borked because there is no way in million years master bus will take a vst.
With all these shenanigans using Waveform is simply not an option
Some of these were a problem in T6. Waveform just added new ones
Please, crush these bugs
Cheers
- Beware the Quoth
- 33177 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
version? platform?
my other modular synth is a bugbrand
-
- KVRer
- 14 posts since 2 Dec, 2015
I can confirm that I have seen issue #1 with collective firsthand.
Waveform: 8.0.27
Collective: 1.0.3
Windows 10 64-bit
In particular I noticed it with the drum kits. After some period of time certain drum sounds stop playing, then everything out of collective stops playing. The solution for me is to delete and re-add the plugin, but obviously this isn't ideal, so I don't use collective much.
Waveform: 8.0.27
Collective: 1.0.3
Windows 10 64-bit
In particular I noticed it with the drum kits. After some period of time certain drum sounds stop playing, then everything out of collective stops playing. The solution for me is to delete and re-add the plugin, but obviously this isn't ideal, so I don't use collective much.
-
- KVRAF
- 1777 posts since 30 Dec, 2012
Thanks, we are aware of this and are looking in to a fix but it's been difficult to replicate. It doesn't seem to happen on every machine.pacmanpl wrote:1. Collective randomly stops playing sound.
I have two tracks with Collective and both are having this problem. You can see the keys pressed inside the plugin but there is no sound. Restarting project sometimes help, but not often. Restarting Waveform does the job.
It can bork itself in the middle of MIDI clip. Just because...
Also it seems to be Collective problem because putting different instrument on the track doesn't have that problem.
I've not seen this, is the CPU usage particularly high? Is it always choppy or do you need to have a complex Edit for it to start getting choppy?2. Moving playback line/cursor is REALLY choppy whenever I put MidiEditor in separate window.
It just doesn't update when mouse is moving. Inside the Editor window it's smooth. On the main screen it looks as if I was using potat PC.
Thanks, I'm not sure exactly what the cause of this is but we are planning to improve the MIDI note handling later on in the year.3. Looping MIDI clip makes the first note not working.
Again it's something that likes to break after some time. Put a note at the very beggining of a clip and the only thing that comes out is click. After delaying that note ~20ms it works as intended.
Thanks, this has been fixed and should be sorted in the next release, 8.1.2.4. In MIDI editor - selecting notes with right mouse button is a recipe for a quick crash.
Also the selection box stay visible after mouse release.
Can you provide a bit more detail about the circumstances in which this happens?5. vstInstruments can break into not having sustain, just single pluck.
It happens with Collective and few other instruments. Sound is stopping after the first sample(???)/frame.
I can't seem to replicate this either. If a shift drag a note, the velocity is immediately updated in the properties panel.6. Velocity number indicator in MIDI editor is not updating while changing it with SHIFT + Mouse.
Only after selecting the note once again i returns current value.
What VST are you using? Are you sure that your tracks are outputting to the "Default audio output"? These are the only tracks that go through the master bus.7. Sometimes putting vst on master bus will simply not work.
In that case the whole project is borked because there is no way in million years master bus will take a vst.
If we can get to the bottom of the issues, we'll fix themWith all these shenanigans using Waveform is simply not an option
Some of these were a problem in T6. Waveform just added new ones
Please, crush these bugs
Cheers
-
- KVRer
- Topic Starter
- 17 posts since 9 Aug, 2015
It's not an issue anymore in 8.1.2.2. Moving playback line/cursor is REALLY choppy whenever I put MidiEditor in separate window.
Smooth as butter <3
https://youtu.be/kXqMuc9dIOY3. Looping MIDI clip makes the first note not working.
This is very random and doesn't happen often... After some mad clicking around it can "fix itself".5. vstInstruments can break into not having sustain, just single pluck.
Gonna keep my guard when messing with MIDI keyboard.
I mean this one:6. Velocity number indicator in MIDI editor is not updating while changing it with SHIFT + Mouse.
When you collapse bottom toolbar you can't see the big velocity bar.
You can only add up to four master plugins7. Sometimes putting vst on master bus will simply not work.
Welp, now I know!
-
vitocorleone123 vitocorleone123 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=333504
- KVRAF
- 1895 posts since 30 Jun, 2014 from Pacific NW
If you're not using submixes and/or need to put lots of plugins on the Master there's a simple, albeit not necessarily obvious, answer: use a Rack (it'll allow you to put whatever plugins you want/need/your computer can run on the Master). It may not be as convenient because you have to click into it before you can edit things, but it does work.
-
- KVRAF
- 3735 posts since 17 Sep, 2016
Yup, I was thinking exactly the same thing!vitocorleone123 wrote:If you're not using submixes and/or need to put lots of plugins on the Master there's a simple, albeit not necessarily obvious, answer: use a Rack (it'll allow you to put whatever plugins you want/need/your computer can run on the Master). It may not be as convenient because you have to click into it before you can edit things, but it does work.
Windows 10 and too many plugins
- KVRist
- 121 posts since 31 Aug, 2015
Step Clips -
1. I'd like to be able to drop a step clip in and use a preset I made.
2. Then if I make a copy of that clip and I decide to fill it will another preset I made - it fills visually - but still plays the 1st Step Clip preset.
It's almost as if I have to drop a whole new step clip just to fill with a new preset. I mean is that due to loss of memory in the program?
1. I'd like to be able to drop a step clip in and use a preset I made.
2. Then if I make a copy of that clip and I decide to fill it will another preset I made - it fills visually - but still plays the 1st Step Clip preset.
It's almost as if I have to drop a whole new step clip just to fill with a new preset. I mean is that due to loss of memory in the program?
-
- KVRAF
- 1777 posts since 30 Dec, 2012
I'm not able to replicate this say I do the following:geqfreq wrote:Step Clips -
1. I'd like to be able to drop a step clip in and use a preset I made.
2. Then if I make a copy of that clip and I decide to fill it will another preset I made - it fills visually - but still plays the 1st Step Clip preset.
It's almost as if I have to drop a whole new step clip just to fill with a new preset. I mean is that due to loss of memory in the program?
1. Drag "Step Clip: Blues 1" from the search panel on to a track and set it playing
2. Copy that clip to a new clip and position it afterwards
3. Select the newly copied clip and press the "Load Preset" button
4. Select a new preset e.g. "Step Clip: Funk"
5. The step clip interface changes and the played pattern also updates
If when you change the preset and then press the panic button in the transport area, does the audio update to reflect the UI then?
- KVRist
- 121 posts since 31 Aug, 2015
yes - thank you it does work after hitting the panic button the new clip plays - it would be nice if the buffer allowed it to play when the clip is loaded.If when you change the preset and then press the panic button in the transport area, does the audio update to reflect the UI then?
- KVRAF
- 2356 posts since 3 Mar, 2010
I am seeing this, as well, with one plugin in particular - Virsyn Tera 3. I am using Waveform 8.1.2 on Windows 10, 32 bit version. When pressing a note, whether on the Waveform virtual keyboard, the on-screen keyboard within Tera 3 or my external midi keyboard, the note does not sustain and stops playing as soon as I press the key - sounds like a pluck, no matter which preset I use. This same plugin works correctly in Tracktion 7, as well as other DAWs on this machine (e.g., FL Studio). Please help!!pacmanpl wrote:5. vstInstruments can break into not having sustain, just single pluck.
It happens with Collective and few other instruments. Sound is stopping after the first sample(???)/frame.
-
- KVRian
- 1116 posts since 3 May, 2005 from Victoria, BC
A fix for this will be in the next release.bharris22 wrote:I am seeing this, as well, with one plugin in particular - Virsyn Tera 3.pacmanpl wrote:5. vstInstruments can break into not having sustain, just single pluck.
It happens with Collective and few other instruments. Sound is stopping after the first sample(???)/frame.