I finally took the time to take a look at v0.2.9
Sadly, the GUI recall still doesn't work. In fact, the GUI starts completely blank and I have to load the default preset to get the grid on the FFT.
There is also still no screen size setting (numeric), it's still drag and drop, until you're at about the size you want.
Another thing I realized, the default setting uses AAx16 still. I'm now on a NVidia 760 with OpenGL4.x, so 60fps for me no matter which resolution (at least until 720p), but this might not be the best experience for users with weaker cards
Then I found a possible bug. And to me, that's a bit severe.
I can't use Signalizer in Wavelab 9 if I load a mono WAV file. Either there is no readout on the meter (no matter which channel I select on the GUI), or it simply crashes Wavelab. Not cool, but kind of expected. It's still in beta state.
I was also surprised that you currently only have an X/Y Oscilloscope and Spectrogram view. But I take it, we'll see a major update coming soon. Definitely looking forward to the sandbox feature, would love to see meter bargraphs, a 1/3rd octave view, etc. In the future, maybe even a "multi instance" version where several channels overlay to see what multiple channels do and how they affect each other. A Waveform view synced to the host bpm, and of course the announced "measurement suite functionality" (interaction with test signals).
So yeah... I'll still keep my eyes on your project. Great tool so far. Hopefully it will be something more from this road on out.
Signalizer: Sidechaining update! Open-source & free audio visualization plugin (v. 0.4.3)
-
- KVRAF
- 14668 posts since 19 Oct, 2003 from Berlin, Germany
-
- KVRian
- 753 posts since 2 Aug, 2013
Woaw how did I only come across this now? I actually just started learning how to program and DSP development a bit ago because I wanted to development some personal tools that also included a visualization plugin too. This looks really impressive, I look forward to testing it.
Edit: Where can I check out the source code?-
Edit: nvm, I'm dumb.
Edit: Where can I check out the source code?-
Edit: nvm, I'm dumb.
Last edited by SeeingInMidi on Tue Sep 20, 2016 1:43 pm, edited 1 time in total.
-
- KVRian
- Topic Starter
- 576 posts since 1 Jan, 2013 from Denmark
Hi Compy
The source code is right here: https://bitbucket.org/Mayae/signalizer/src
I know it's a lot to ask, but can you make a video of your problem? I looked through the code and analyzed your patches and nothing seems to be able to create your problems - also heard of noone else struggling with this, so I don't really know where to start. If you have the time, please let me know (you can also contact me over mail if thats preferable).Compyfox wrote:Sadly, the GUI recall still doesn't work. In fact, the GUI starts completely blank and I have to load the default preset to get the grid on the FFT.
Right, I'll add that in.There is also still no screen size setting (numeric), it's still drag and drop, until you're at about the size you want.
I haven't really spend time on the presets, but I actually forgot to lower that setting. As others have reported, flood-filling drawings can make artifacts (especially on mobile NVidia cards) that are resolved on lower AA, so I'll do that on next release.Another thing I realized, the default setting uses AAx16 still. I'm now on a NVidia 760 with OpenGL4.x, so 60fps for me no matter which resolution (at least until 720p), but this might not be the best experience for users with weaker cards
I recently did some patches to fix mono behaviour, but yes you're right, this is serious. This is on Windows, right? I assume you're using the spectrum (the vectorscope wouldn't make much sense in a mono setting). Additionally, are there any crash logs (a file called signalizer exceptions.log in the plugin folder)? Any other info, like what Windows/OS X is telling you when the program crashes is appreciated.Then I found a possible bug. And to me, that's a bit severe.
I can't use Signalizer in Wavelab 9 if I load a mono WAV file. Either there is no readout on the meter (no matter which channel I select on the GUI), or it simply crashes Wavelab. Not cool, but kind of expected. It's still in beta state.
Yes, well inbetween full-time studies, part-time job & working on multiple albums there's not much time left for programming open source in the evenings (currently). While the latest patch might not look like much, it was a lot work behind the scenes. Things will get done when they're ready.I was also surprised that you currently only have an X/Y Oscilloscope and Spectrogram view. But I take it, we'll see a major update coming soon.
Me too, but one thing at a timeDefinitely looking forward to the sandbox feature, would love to see meter bargraphs, a 1/3rd octave view, etc. In the future, maybe even a "multi instance" version where several channels overlay to see what multiple channels do and how they affect each other. A Waveform view synced to the host bpm, and of course the announced "measurement suite functionality" (interaction with test signals).
Well it's not advertised in any way, so probably thats whySeeingInMidi wrote:Woaw how did I only come across this now? I actually just started learning how to program and DSP development a bit ago because I wanted to development some personal tools that also included a visualization plugin too. This looks really impressive, I look forward to testing it.
Edit: Where can I check out the source code?
The source code is right here: https://bitbucket.org/Mayae/signalizer/src
-
- KVRian
- 753 posts since 2 Aug, 2013
Very impressive! This puts a lot of paid plugins to shame even in its alpha state.
+1 for minimal GUI. Very ergonomic, no fancy icons in the way. I don't know why developers always feel the need to waste precious space and add a 20 pixel thick bezel to their analyzers.
+1 for minimal GUI. Very ergonomic, no fancy icons in the way. I don't know why developers always feel the need to waste precious space and add a 20 pixel thick bezel to their analyzers.
-
- KVRian
- Topic Starter
- 576 posts since 1 Jan, 2013 from Denmark
Thanks man, happy you like it
I agree, bezels do no good for this application. You can enable the "auto-hide" in the global options (cogwheels to the left) to completely remove all UI.
I agree, bezels do no good for this application. You can enable the "auto-hide" in the global options (cogwheels to the left) to completely remove all UI.
-
- KVRian
- 753 posts since 2 Aug, 2013
Signalizer has been my go to spectrum analyzer and I have some suggestions/requests. Sorry if any of these have been mentioned before or has already been implemented.
- An option to keep the vectorscope squared. So even if Signalizer's window's height and width aren't equal, they vectorscope will stay squared.
- To be able to set the spectrum's min freq and max freq like in Voxengo Span. So if the user really wants to, the can set the min freq to 0 HZ.
- It seems like the grid is layered on top of the line graph in the spectrum analyzer. I think the line graph should be layered on top of the grid and allow the user to change the opacity of the graph to reveal the grid behind it.
- An option to allow custom vertical gradient colors for the background in the spectrum analyzer.
- An option to enable vertical and horizontal scroll bars. This will let the user maneuver and pan through the vectorscope and spectrum analyzer when zoomed in easier. The scroll bars should only appear when zooming in. Let the user choose if they want the scroll bar to be always present or only appear when their mouse is hovering over the bars positions.
- Separate settings for the the line graph and spectrogram. At the moment, they both share some settings like "Upper limit", "Lower limit", ect. It becomes annoying when switching between the line graph and spectrogram.
- Have the option the let the spectrogram scroll left to right instead of right to left. Also have the option the option to have the spectrogram scroll from top to bottom like a waterfall.
- If the waterfall is implemented, allow the background of the the line graph to be the water falling spectrogram. I think one of the Blue Cat Audio's spectrum analyzers or EQs do this. It's pretty neat.
- 3D Spectrogram.
- An option to increase the spectrogram's precision. The most precise spectrogram I have come across with is Image Lines Edison with 64 bands precision.
- Allow the oscilloscope, spectrum analyzer, spectrogram, vectorscope to be viewed all at the same time like Flux's Pure Analyzer.
These are just my thoughts, some of it could be handy hah.
- An option to keep the vectorscope squared. So even if Signalizer's window's height and width aren't equal, they vectorscope will stay squared.
- To be able to set the spectrum's min freq and max freq like in Voxengo Span. So if the user really wants to, the can set the min freq to 0 HZ.
- It seems like the grid is layered on top of the line graph in the spectrum analyzer. I think the line graph should be layered on top of the grid and allow the user to change the opacity of the graph to reveal the grid behind it.
- An option to allow custom vertical gradient colors for the background in the spectrum analyzer.
- An option to enable vertical and horizontal scroll bars. This will let the user maneuver and pan through the vectorscope and spectrum analyzer when zoomed in easier. The scroll bars should only appear when zooming in. Let the user choose if they want the scroll bar to be always present or only appear when their mouse is hovering over the bars positions.
- Separate settings for the the line graph and spectrogram. At the moment, they both share some settings like "Upper limit", "Lower limit", ect. It becomes annoying when switching between the line graph and spectrogram.
- Have the option the let the spectrogram scroll left to right instead of right to left. Also have the option the option to have the spectrogram scroll from top to bottom like a waterfall.
- If the waterfall is implemented, allow the background of the the line graph to be the water falling spectrogram. I think one of the Blue Cat Audio's spectrum analyzers or EQs do this. It's pretty neat.
- 3D Spectrogram.
- An option to increase the spectrogram's precision. The most precise spectrogram I have come across with is Image Lines Edison with 64 bands precision.
- Allow the oscilloscope, spectrum analyzer, spectrogram, vectorscope to be viewed all at the same time like Flux's Pure Analyzer.
These are just my thoughts, some of it could be handy hah.
Last edited by SeeingInMidi on Thu Sep 22, 2016 3:24 am, edited 2 times in total.
-
- KVRAF
- 14668 posts since 19 Oct, 2003 from Berlin, Germany
@Mayae:
I'm currently a bit busy myself, but I try to get back to you around the end of the week with a short video showing what's going on.
Yes I am on Windows 7 x64 SP1, I'm using Wavelab 9 x64. Stereo is fine, mono is not. Even if a Goniometer won't make much sense in mono, I'd still love to use it. Also... I'm still hoping for more "view types".
Yes, there is a crashlog in the root of your plugin folder. Here is the code:
Since Wavelab is not a realtime engine like Cubase/Nuendo, it mostly crashes on playback, or on initialization of a freshly loaded mono WAV file. Didn't try it in Cubase to be honest.
Looking forward to a screen size setting (with numeric values) and a default preset with AAx2 (which should be enough for most people, including weak cards like I originally used). Maybe a frame cap implementation would also be great (60-80frames max)
Also, didn't you want to reintroduce new toggle buttons?
I'm currently a bit busy myself, but I try to get back to you around the end of the week with a short video showing what's going on.
Yes I am on Windows 7 x64 SP1, I'm using Wavelab 9 x64. Stereo is fine, mono is not. Even if a Goniometer won't make much sense in mono, I'd still love to use it. Also... I'm still hoping for more "view types".
Yes, there is a crashlog in the root of your plugin folder. Here is the code:
Code: Select all
----------------20/9/2016, 18:0:27----------------
- Exception in "Signalizer" v."0.2.9"
Handler: JUCE Message window procedure
- SEH exception description:
Non-software exception at 0x00000000772E3290 (at image base 0x000007FEEFF10000 - 0x000007FE78C2CD70)
Exception code: c0000005, actual code: 0, extra info: 0
Formatted message: Access violation reading address 000005E3517BAD28.
- Stack backtrace:
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 - 0x000007FE78C2CE40 + 0xd0 | RtlFreeHeap
0x000007FEEFF10000 - 0x000007FE78D7D000 + 0xa | HeapFree
0x000007FEEFF10000 + 0x0000000000338150 + 0x4fae4 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000058F3D
0x000007FEEFF10000 + 0x000000000004D721
0x000007FEEFF10000 + 0x000000000004D7C6
0x000007FEEFF10000 + 0x0000000000006761
0x000007FEEFF10000 + 0x00000000000074D4
0x000007FEEFF10000 + 0x0000000000338150 + 0x8a1b5 | VSTPluginMain
0x000007FEEFF10000 + 0x0000000000338150 + 0x2c404 | VSTPluginMain
0x000007FEEFF10000 - 0x000007FE78C56380 + 0xad | RtlDecodePointer
0x000007FEEFF10000 - 0x000007FE78C679F0 + 0xbbf | RtlUnwindEx
0x000007FEEFF10000 - 0x000007FE78C2EDE6 + 0x2e | KiUserExceptionDispatcher
0x000007FEEFF10000 + 0x0000000000027251
0x000007FEEFF10000 + 0x0000000000027272
0x000007FEEFF10000 + 0x0000000000027272
0x000007FEEFF10000 + 0x000000000002717B
0x000007FEEFF10000 + 0x0000000000022D65
0x000007FEEFF10000 + 0x000000000004A892
0x000007FEEFF10000 + 0x0000000000049C7E
0x000007FEEFF10000 + 0x0000000000026CA5
0x000007FEEFF10000 + 0x0000000000027239
0x000007FEEFF10000 + 0x0000000000027272
0x000007FEEFF10000 + 0x000000000002717B
0x000007FEEFF10000 + 0x000000000005002A
0x000007FEEFF10000 + 0x00000000000EBBF5
0x000007FEEFF10000 + 0x00000000001F8150
0x000007FEEFF10000 + 0x00000000001F75AA
0x000007FEEFF10000 + 0x00000000001F75D3
0x000007FEEFF10000 + 0x00000000001F7289
0x000007FEEFF10000 - 0x000007FE78E866D0 + 0x2a1 | TranslateMessageEx
0x000007FEEFF10000 - 0x000007FE78E86910 + 0x1ea | TranslateMessage
0x000007FEEFF10000 - 0x000007FE7C0AE160 + 0x546 | QEventDispatcherWin32::processEvents
0x000007FEEFF10000 + 0x00000000041B5950 + 0x2479 | qt_plugin_query_metadata
0x000007FEEFF10000 - 0x000007FE7C0F9120 + 0x1b3 | QEventLoop::exec
0x000007FEEFF10000 - 0x000007FE7C0F6A50 + 0x147 | QCoreApplication::exec
0x000007FEEFF10000 - 0x000007FDAFBB9D15
0x000007FEEFF10000 - 0x000007FDAF6DDB0B
0x000007FEEFF10000 - 0x000007FDAF6F63BA
0x000007FEEFF10000 - 0x000007FE78D89AE0 + 0xd | BaseThreadInitThunk
0x000007FEEFF10000 - 0x000007FE78C53AE0 + 0x21 | RtlUserThreadStartLooking forward to a screen size setting (with numeric values) and a default preset with AAx2 (which should be enough for most people, including weak cards like I originally used). Maybe a frame cap implementation would also be great (60-80frames max)
Also, didn't you want to reintroduce new toggle buttons?
-
- KVRian
- Topic Starter
- 576 posts since 1 Jan, 2013 from Denmark
Hi SeeingInMidi, thanks and I really appreciate your suggestions!
As an example, tampering with some settings the spectrogram can easily generate these pixel-perfect visuals:
Note that the global anti-aliasing also affects the spectrogram, so if you want pixels you should disable it.
And yes, I'll get to the buttons soon
This is not a bad idea, and I wanted to do something similar - at least for the text that is otherwised squashed.SeeingInMidi wrote:- An option to keep the vectorscope squared. So even if Signalizer's window's height and width aren't equal, they vectorscope will stay squared.
If you're in linear mode, the min freq is already 0 Hz. If you're in logarithmic modes, it doesn't make mathemathical sense to start at 0 - it has to be a positive value above zero. So it can be 100, 10, 1, 0.1 etc. I considered adding this, and perhaps I'll do it..- To be able to set the spectrum's min freq and max freq like in Voxengo Span. So if the user really wants to, the can set the min freq to 0 HZ.
This has to do with how Signalizer composites layers. Normally, everything is done in a saturating mode, but OpenGL doesn't support this for transparent layers (like the grid). It's on my to-do list to rewrite the compositing to support both plain transparancy modes and saturated composition, so for now you'll have to accept the less-than-ideal rendering of layers- It seems like the grid is layered on top of the line graph in the spectrum analyzer. I think the line graph should be layered on top of the grid and allow the user to change the opacity of the graph to reveal the grid behind it.
I'm not entirely sure what you mean by this.- An option to allow custom vertical gradient colors for the background in the spectrum analyzer.
Not a bad idea, I'll try it out.- An option to enable vertical and horizontal scroll bars. This will let the user maneuver and pan through the vectorscope and spectrum analyzer when zoomed in easier. The scroll bars should only appear when zooming in. Let the user choose if they want the scroll bar to be always present or only appear when their mouse is hovering over the bars positions.
I understand your frustration. Currently, they are merged together because they share 99% of the same codebase and memory/storage, but ideally it really should be separated in to two separate views... The amount of controls for the spectrum is already too high.- Separate settings for the the line graph and spectrogram. At the moment, they both share some settings like "Upper limit", "Lower limit", ect. It becomes annoying when switching between the line graph and spectrogram.
When the specturm and spectrogram is split up, the spectrogram will be a true 3D image that can be transformed like the vectorscope so this will be natively supported.- Have the option the let the spectrogram scroll left to right instead of right to left. Also have the option the option to have the spectrogram scroll from top to bottom like a waterfall.
So the spectrum is layered on top of the spectrogram?- If the waterfall is implemented, allow the background of the the line graph to be the water falling spectrogram. I think one of the Blue Cat Audio's spectrum analyzers or EQs do this. It's pretty neat.
The spectrogram is already optimally precise and pixel perfect, and with the unbound Q setting the precision exceeds any other spectrogram at the cost of exceeding the visual resolution bandwith (normally, the spectrogram is tuned such that you cannot have scalloping losses exceed -3dB).- An option to increase the spectrogram's precision. The most precise spectrogram I have come across with is Image Lines Edison with 64 bands precision.
As an example, tampering with some settings the spectrogram can easily generate these pixel-perfect visuals:
Note that the global anti-aliasing also affects the spectrogram, so if you want pixels you should disable it.
Thanks for the report, I'll investigate it. The frame cap is implemented through vertical sync, where you can specify integer fractions of your framerate as a cap (see the swap interval).Compyfox wrote:Maybe a frame cap implementation would also be great (60-80frames max)
Also, didn't you want to reintroduce new toggle buttons?
And yes, I'll get to the buttons soon
-
- KVRian
- 753 posts since 2 Aug, 2013
Thanks for the reply Mayae!
If I have any more ideas/suggestions in the future, I'll keep you posted.
Oops, you are correct. But yeah, to be able to see all the way down to 0.1 would be a nice addition.If you're in linear mode, the min freq is already 0 Hz. If you're in logarithmic modes, it doesn't make mathemathical sense to start at 0 - it has to be a positive value above zero. So it can be 100, 10, 1, 0.1 etc. I considered adding this, and perhaps I'll do it..To be able to set the spectrum's min freq and max freq like in Voxengo Span. So if the user really wants to, the can set the min freq to 0 HZ.
It's not really important, but it adds cosmetic depth and flair to the background. DMG's Equilibrium has the option to enable/disable "Fade" which makes the background fade white to black from top to bottom.I'm not entirely sure what you mean by this.- An option to allow custom vertical gradient colors for the background in the spectrum analyzer.
Exactly, the spectrogram would act like a histogram. An option like this would be great in the future. Its seems more ergonomic to me, no need to switch between the two or no need to have them both displayed in different windows.So the spectrum is layered on top of the spectrogram?- If the waterfall is implemented, allow the background of the the line graph to be the water falling spectrogram. I think one of the Blue Cat Audio's spectrum analyzers or EQs do this. It's pretty neat.
Ah, didn't know about this. Sorry!The spectrogram is already optimally precise and pixel perfect, and with the unbound Q setting the precision exceeds any other spectrogram at the cost of exceeding the visual resolution bandwith (normally, the spectrogram is tuned such that you cannot have scalloping losses exceed -3dB).- An option to increase the spectrogram's precision. The most precise spectrogram I have come across with is Image Lines Edison with 64 bands precision.
As an example, tampering with some settings the spectrogram can easily generate these pixel-perfect visuals:
Note that the global anti-aliasing also affects the spectrogram, so if you want pixels you should disable it.
If I have any more ideas/suggestions in the future, I'll keep you posted.
-
- KVRist
- 223 posts since 15 Jun, 2013
I thank you MayaeMayae wrote:Hi again,True, this is changed in the next version.marioisaac wrote:-I would suggest changing the grid div space scaling. The finest resolution of the scale goes from 3db per line, then it jumps to 5dB. Given that dB values doubles and halves each 6db, it makes more sense to have them scale to multiples of 6.
The meters would originally be included in the stats page, that's yet to come. Perhaps it would be nice, although compositing of views is deferred to when I make a "sandbox" mode, where you can put multiple views together.-Also implementing an option to add a Peak/RMS global meter to the right would be a nice addition. The Peak/RMS could be a sections on it's own in the same way as the (vectorscope, oscilloscope, and spectrum views).
It can be confusing, yes. I'll see if I can figure out a nice solution.-When selecting the global settings the tab does not give a user a hint on whether he is changing the parameters for the vectorscope, spectrum, or general settings. Now I understand the plugin, but at first sight this was confusing, and I guess for others users will be as well. eg. If I am on the Spectrum settings tab, and I click the Vectorscope tab, the Spectrum header tab turns into black and the Vectorscope header tab turns into the colour of the settings tab, but if I click on the global settings icon, there is no visual feedback (colour change) to indicate I am in a different settings section.
Thanks for the feedback, and I'm happy to hear that (most) of your problems are resolved.
-
- KVRian
- 753 posts since 2 Aug, 2013
Hey Mayae, any progress on Signalizer? 
-
- KVRian
- Topic Starter
- 576 posts since 1 Jan, 2013 from Denmark
Hi, been swamped with work & studies sorry. I've started on the oscilloscope, and hope to have more time in a month or so.SeeingInMidi wrote:Hey Mayae, any progress on Signalizer?
-
- KVRian
- 967 posts since 26 Sep, 2013 from Arizona, USA
Looking forward to more updates! Hope your studies are going well!! 
I noticed a problem when using Signalizer with the FL Studio Mac alpha as well as Renoise 3: Any ideas?
I noticed a problem when using Signalizer with the FL Studio Mac alpha as well as Renoise 3: Any ideas?
You do not have the required permissions to view the files attached to this post.
-
- KVRian
- Topic Starter
- 576 posts since 1 Jan, 2013 from Denmark
Well, forwards at least.Naenyn wrote:Looking forward to more updates! Hope your studies are going well!!
I noticed a problem when using Signalizer with the FL Studio Mac alpha as well as Renoise 3: Any ideas?
Haven't seen that error before in the wild, but I'm glad it's caught at least. Hard to tell what's wrong without some more info, so if you're game:
I'm assuming you haven't changed the file in question (that would include changing/update the default preset of signalizer)? Do you have any hosts not exhibiting this behaviour?
If you could provide the file to me somehow, I could check whether it actually has been corrupted, although I doubt it. If you create a copy of the file, and then try to save a preset as the default the global settings, do you still experience this behaviour? What about loading any other preset, project recall etc.?
-
- KVRian
- 967 posts since 26 Sep, 2013 from Arizona, USA
I've not changed any of the presets. Logic and Hosting AU both work fine. Maybe it's a VST vs AU problem?
Here is a link to the preset. I actually get that same error with any of the presets... and otherwise, get a blank plugin window. I can see the controls.. and some text if I toggle on Diagnostics.. but otherwise, nothing in the window.
Happy to continue helping troubleshoot. I could make videos if that'd help.
Here is a link to the preset. I actually get that same error with any of the presets... and otherwise, get a blank plugin window. I can see the controls.. and some text if I toggle on Diagnostics.. but otherwise, nothing in the window.
Happy to continue helping troubleshoot. I could make videos if that'd help.
