Reaper issue is "Project Load Warning"?
Can you try this?
Option > Preferences > VST > clear cache/re-scan
Then re-open the project.
Tadashi
Tried it, does not work. It does not use the 1.0.7x to replace the previous 1.0.0hyakken wrote: ↑Mon Jul 13, 2020 9:31 pm I might have used incorrect version number format.
version 1.0.0 was two points format and previous one (1.072) was single point.
This may make some hosts confused.
So I just made v1.0.73 with two points format.
If someone try it, please let me know the result.
https://hy-plugins.com/product/hy-poly/
Tadashi
Thank you for those information.] Peter:H [ wrote: ↑Tue Jul 14, 2020 3:37 pmTried it, does not work. It does not use the 1.0.7x to replace the previous 1.0.0hyakken wrote: ↑Mon Jul 13, 2020 9:31 pm I might have used incorrect version number format.
version 1.0.0 was two points format and previous one (1.072) was single point.
This may make some hosts confused.
So I just made v1.0.73 with two points format.
If someone try it, please let me know the result.
https://hy-plugins.com/product/hy-poly/
Tadashi
I have loaded both into VSTHost and opend the info page. It shows different unique IDs. That's probably the reason.
Left is the latest version, to the right is the 1.0.0 Version. Two interesting observations
- both report Version 1000 which probably stands for 1.0.0.0.
- Your latest Version 1.0.73 replaces the version before that without any problem, because the have the same unique ID depicted on the left.
So I have now 3 versions in my VSTHost window, two share the same uniqueID (> 1.0.0) but differ from the uniqueID of version 1.0.0.
Seems like you have to dive into the build process and figure out how to reliably set the uniqueID of the plugin.
I think I should open a software faith healer business with remote diagnosis and voodoo debugging
The next tipp will cost you a drink
Tadashi, here's btw two tracks I did with Hy-Poly (free) accompanied by various DAW and free FX, but no other synth.
Code: Select all
35 juce::threadEntryProc(void*) (in HY-POLY free) + 527 [0x1084c509f]
34 juce::TimeSliceThread::run() (in HY-POLY free) + 98 [0x1084b5ef2]
28 juce::TimeSliceThread::run() (in HY-POLY free) + 0 [0x1084b5e90]
Code: Select all
275 juce::threadEntryProc(void*) (in HY-POLY free) + 527 [0x1084c509f]
274 juce::TimeSliceThread::run() (in HY-POLY free) + 98 [0x1084b5ef2]
Thank you for your tracks.] Peter:H [ wrote: ↑Mon Jul 20, 2020 6:27 pmTadashi, here's btw two tracks I did with Hy-Poly (free) accompanied by various DAW and free FX, but no other synth.
https://soundcloud.com/p-e-t-e-r-h/hy-a-gressive
https://soundcloud.com/p-e-t-e-r-h/osc1 ... nd-concret
hope you like them
] Peter:H [
Thanks for the quick turnaround! This is definitely somewhat better -- probably good enough I can try to finish a track for the OSC now - but it still hasn't entirely solved the issue. The existing project I have went from: 580 of these threads to:
Code: Select all
114 juce::threadEntryProc(void*) (in HY-POLY free) + 527 [0x10de5220f]
113 juce::TimeSliceThread::run() (in HY-POLY free) + 98 [0x10de43062]
81 juce::TimeSliceThread::run() (in HY-POLY free) + 0 [0x10de43000]
73 __gettimeofday (in libsystem_kernel.dylib) + 0 [0x7fff73b3fe01]
Code: Select all
19 juce::WaitableEvent::wait(int) const (in HY-POLY free) + 133 [0x10de43475]
18 juce::threadEntryProc(void*) (in HY-POLY free) + 527 [0x10de5220f]
17 juce::TimeSliceThread::run() (in HY-POLY free) + 98 [0x10de43062]
Thank you for your testing.z.prime wrote: ↑Sun Jul 26, 2020 2:17 pmThanks for the quick turnaround! This is definitely somewhat better -- probably good enough I can try to finish a track for the OSC now - but it still hasn't entirely solved the issue. The existing project I have went from: 580 of these threads to:However, to make sure I wasn't using the oscilloscope, I manually opened and closed each instance and usage dropped to:Code: Select all
114 juce::threadEntryProc(void*) (in HY-POLY free) + 527 [0x10de5220f] 113 juce::TimeSliceThread::run() (in HY-POLY free) + 98 [0x10de43062] 81 juce::TimeSliceThread::run() (in HY-POLY free) + 0 [0x10de43000] 73 __gettimeofday (in libsystem_kernel.dylib) + 0 [0x7fff73b3fe01]
But reloading the project (with no open GUIs, no oscilloscope added) goes back to the 113/114 above. I'll reiterate: this does not seem to happen in REAPER with the same plugin count, so I assume it's something about the order and/or specific calls to the plugin from Bitwig (and presumably Live, too).Code: Select all
19 juce::WaitableEvent::wait(int) const (in HY-POLY free) + 133 [0x10de43475] 18 juce::threadEntryProc(void*) (in HY-POLY free) + 527 [0x10de5220f] 17 juce::TimeSliceThread::run() (in HY-POLY free) + 98 [0x10de43062]
Another issue: for some reason, I have to delete the VST/VST3 plugins manually before running the installer, or it doesn't seem to replace them (this has been a problem with all the installers, for me).
Thanks again for the quick look at this issue!
Please try this one.z.prime wrote: ↑Sun Jul 26, 2020 2:17 pmThanks for the quick turnaround! This is definitely somewhat better -- probably good enough I can try to finish a track for the OSC now - but it still hasn't entirely solved the issue. The existing project I have went from: 580 of these threads to:However, to make sure I wasn't using the oscilloscope, I manually opened and closed each instance and usage dropped to:Code: Select all
114 juce::threadEntryProc(void*) (in HY-POLY free) + 527 [0x10de5220f] 113 juce::TimeSliceThread::run() (in HY-POLY free) + 98 [0x10de43062] 81 juce::TimeSliceThread::run() (in HY-POLY free) + 0 [0x10de43000] 73 __gettimeofday (in libsystem_kernel.dylib) + 0 [0x7fff73b3fe01]
But reloading the project (with no open GUIs, no oscilloscope added) goes back to the 113/114 above. I'll reiterate: this does not seem to happen in REAPER with the same plugin count, so I assume it's something about the order and/or specific calls to the plugin from Bitwig (and presumably Live, too).Code: Select all
19 juce::WaitableEvent::wait(int) const (in HY-POLY free) + 133 [0x10de43475] 18 juce::threadEntryProc(void*) (in HY-POLY free) + 527 [0x10de5220f] 17 juce::TimeSliceThread::run() (in HY-POLY free) + 98 [0x10de43062]
Another issue: for some reason, I have to delete the VST/VST3 plugins manually before running the installer, or it doesn't seem to replace them (this has been a problem with all the installers, for me).
Thanks again for the quick look at this issue!
This is GREAT! Looks like it's solved the issue - I'm only seeing things related to audio processing in the thread list now and CPU usage is way down! Thank you so much for the quick turnaround on this, Tadashi! I'll try to make you proud before end of the month
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement