Hello
I'm experiencing a bug with the audio unit version of TX16Wx. Zooming in and out in the wave editor is causing the plugin and daw to crash. I tested it in Logic, Renoise, and Reaper. Same problem in all of them. This does not happen with the VST version.
TX16Wx: Wave Editor Crashing DAW
-
- KVRer
- Topic Starter
- 14 posts since 14 Nov, 2015
-
- KVRAF
- 2400 posts since 27 May, 2005 from Stockholm
Can you provide some system details? OSX version, hardware etc?
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRer
- Topic Starter
- 14 posts since 14 Nov, 2015
Sure thing.
Late 2013 iMac
OS X El Capitan (10.11.5)
Processor: Intel Core i5 2.9 GHz
Memory: 8 GB 1600 MHz DDR3
Hard Drive: 1TB 5400 RPM
Graphics: NVIDIA GeForce GT 750M 1024 MB
Late 2013 iMac
OS X El Capitan (10.11.5)
Processor: Intel Core i5 2.9 GHz
Memory: 8 GB 1600 MHz DDR3
Hard Drive: 1TB 5400 RPM
Graphics: NVIDIA GeForce GT 750M 1024 MB
-
- KVRAF
- 2400 posts since 27 May, 2005 from Stockholm
So, not surprisingly, I cannot reproduce this at all. 
That it would happen only in AU is even more puzzling. Zooming the wave editor posts zero events to the host, and the UI code is virtually identical (including host binding).
Can you post the OSX crash report (if one was generated)? Does it happen with all material, or only certain files?
That it would happen only in AU is even more puzzling. Zooming the wave editor posts zero events to the host, and the UI code is virtually identical (including host binding).
Can you post the OSX crash report (if one was generated)? Does it happen with all material, or only certain files?
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRer
- 5 posts since 17 Aug, 2016
I have this same problem. Specifically, while scrolling with the mouse wheel aggressively over the wave editor, the plugin and DAW will hang (no crash report generated) every time. Even scrolling not so aggressively will also cause it to crash. This occurred using a USB mouse, as well as the built in track pad. Happens with all material.
For each system I tried it on, I tried Reaper32/64 bit, using VST and AU, with the original OS, and repeating on each system with Windows 10 VM (not running at the same time). Also, for each system, I tried putting the .wav file on the Desktop, and running off an OWC 2TB 7200 rpm drive.
I tried it on two different MBP systems, albeit they weren't too dissimilar:
Machine 1:
MacBook Pro (13-inch, Mid 2012)
OSX 10.10.5/Windows 10 VM
2.5 GHz Intel Core i5
8 GB 1600 MHz DDR3
Intel HD Graphics 4000 1024 MB
Machine 2:
MacBook Pro (13-inch, Mid 2012)
OSX 10.11.5/Windows 10 VM
2.5 GHz Intel Core i5
8 GB 1600 MHz DDR3
Intel HD Graphics 4000 1024 MB
I can try and post a video of it happening if that would help.
For each system I tried it on, I tried Reaper32/64 bit, using VST and AU, with the original OS, and repeating on each system with Windows 10 VM (not running at the same time). Also, for each system, I tried putting the .wav file on the Desktop, and running off an OWC 2TB 7200 rpm drive.
I tried it on two different MBP systems, albeit they weren't too dissimilar:
Machine 1:
MacBook Pro (13-inch, Mid 2012)
OSX 10.10.5/Windows 10 VM
2.5 GHz Intel Core i5
8 GB 1600 MHz DDR3
Intel HD Graphics 4000 1024 MB
Machine 2:
MacBook Pro (13-inch, Mid 2012)
OSX 10.11.5/Windows 10 VM
2.5 GHz Intel Core i5
8 GB 1600 MHz DDR3
Intel HD Graphics 4000 1024 MB
I can try and post a video of it happening if that would help.
-
- KVRAF
- 2400 posts since 27 May, 2005 from Stockholm
Again, I reproduce this at all. And now my mouse wheel is starting to smoke... 
(and my fingers hurt!)
Does this happen with all waves for you, or is there any wave in particular that causes the behaviour? If so, can you share it?
(and my fingers hurt!)Does this happen with all waves for you, or is there any wave in particular that causes the behaviour? If so, can you share it?
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRer
- 5 posts since 17 Aug, 2016
It happens with all waves, no particular one.
Here is a video of it happening: https://youtu.be/Lkt0FNzQh4k
In the video, once the waveform was in the editor, I started scrolling the mouse-wheel up and down, smoothly, and at a moderate speed. The little Mac "waiting rainbow" thing did not show up in the video (not sure why), but you'll notice that I could move the plugin, but couldn't interact with it, nor the DAW (I was clicking on plugin parameters and Reaper and nothing responded).
Here is a link to the audio file I tried in the video: https://drive.google.com/open?id=0B-WrZ ... VJnR3B1VXM
Let me know if there is anything else I can do to help. I do love this plugin!
Here is a video of it happening: https://youtu.be/Lkt0FNzQh4k
In the video, once the waveform was in the editor, I started scrolling the mouse-wheel up and down, smoothly, and at a moderate speed. The little Mac "waiting rainbow" thing did not show up in the video (not sure why), but you'll notice that I could move the plugin, but couldn't interact with it, nor the DAW (I was clicking on plugin parameters and Reaper and nothing responded).
Here is a link to the audio file I tried in the video: https://drive.google.com/open?id=0B-WrZ ... VJnR3B1VXM
Let me know if there is anything else I can do to help. I do love this plugin!
-
- KVRAF
- 2400 posts since 27 May, 2005 from Stockholm
Ok, now I could reproduce it.
Worth knowing:
1.) It is in fact not hung. It is just processing, and it takes a loong time.
2.) It is very much due to the material used. The wave you attached is 55MB large, and thus ~15M samples long. This means that in zoomed in mode, the scrollable size of the wave editor is huge. Of course, this is masked rendering, and the sample view only process what is visible, so one would think this should have no impact on rendering. One would be correct if it was not for one call (not actually related to the sample drawing) that relied on platform clipping instead, and thus infers to the system a canvas width of ~7M pixels or so. This, apparently, makes the underlying graphics go completely bananas, and suddenly we find ourselves having draw calls taking a minute or so.
I've changed the call in question to use manual clipping, and lo, suddenly the wave editor is as snappy as ever. I optimized the wave drawing ever so slightly also. I'll put up a patch release shortly.
Worth knowing:
1.) It is in fact not hung. It is just processing, and it takes a loong time.
2.) It is very much due to the material used. The wave you attached is 55MB large, and thus ~15M samples long. This means that in zoomed in mode, the scrollable size of the wave editor is huge. Of course, this is masked rendering, and the sample view only process what is visible, so one would think this should have no impact on rendering. One would be correct if it was not for one call (not actually related to the sample drawing) that relied on platform clipping instead, and thus infers to the system a canvas width of ~7M pixels or so. This, apparently, makes the underlying graphics go completely bananas, and suddenly we find ourselves having draw calls taking a minute or so.
I've changed the call in question to use manual clipping, and lo, suddenly the wave editor is as snappy as ever. I optimized the wave drawing ever so slightly also. I'll put up a patch release shortly.
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
Man, I love it when Calle explains the bug in detail even though majority of users might not know what he's talking about. I, for one, get the point. 
