[announce] VeeSeeVST Rack VST2 plugin

Modular Synth design and releases (Reaktor, SynthEdit, Tassman, etc.)
Post Reply New Topic
RELATED
PRODUCTS
VCV Rack

Post

bsp804 wrote: Sun Mar 10, 2019 9:09 pm It's a known issue that's happening with certain DAWs.

As a workaround, close the plugin window after you've changed the resolution (click the window close button, "X").
When you reopen the window, the graphics should be good again.
Thanks! I tried closing and reopening the GUI, but the issue still persists.

I noticed though, that the margin of error in the mouse detection seems to be exactly the height of the top bar of Reaper's plugin window, which houses the preset dropdown box, bypass checkbox etc. It's probably also what's skewing the vertical resolution.

Post

Eleventh wrote: Mon Mar 11, 2019 3:27 pm Thanks! I tried closing and reopening the GUI, but the issue still persists.

I noticed though, that the margin of error in the mouse detection seems to be exactly the height of the top bar of Reaper's plugin window, which houses the preset dropdown box, bypass checkbox etc. It's probably also what's skewing the vertical resolution.
Have you tried updating your graphics driver ?

I just tested this in Reaper 5.95 and it worked w/o any graphics glitches or mouse offset issues.

other DAWs:
  • in Studio One 4.1 I had to close and reopen the plugin window after the resolution change to get rid of same empty areas.
  • same thing in Reason 10.1
  • in FL Studio 20, the outer window was too small after changing the resolution but reopening the plugin window fixed this.
    (note by: patch file drag'n'drop does not work in FLS but it works in all other DAWs so it's probably an FLS issue)
  • same thing in vsthostx64 (except that drag'n'drop works there)
  • in Acoustica 7.1 the resolution change works w/o any issues.
There were no mouse-offset issues in any of the DAWs I tested.

That's not to say that the resize code is perfect but since this is particulary annoying to debug, and apparently seems to be GL driver specific, I won't investigate this any further.
Last but not least, setting the resolution is something you usually only do once. If everything else fails, just edit the settings.json file manually.

Post

Thank you for the help. With all the different implementations, plugin support sounds like a hassle :)

Post

Here in 32 bit version, the GUI is black and the modules too.
FL Studio 12, Windows 7 Professional, 3.00 GB RAM, AMD Athlon(tm) II X3 440 Processor 3.00Ghz.
Can you fix it please?
You do not have the required permissions to view the files attached to this post.

Post

espejoooo221v wrote: Wed Mar 13, 2019 2:10 pm Here in 32 bit version, the GUI is black and the modules too.
FL Studio 12, Windows 7 Professional, 3.00 GB RAM, AMD Athlon(tm) II X3 440 Processor 3.00Ghz.
Can you fix it please?
Like I said on one of the previous pages: the 32bit build is completely unsupported.

It does work in general (just tested it in vsthostx86, see screenshot) but in your case my guess is that either your graphics drivers are outdated (try updating them), or your graphics card is simply too old.
You do not have the required permissions to view the files attached to this post.

Post

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
Quick question: are the modules quoted below in the new release (March 2019)? I can't seem to find them. Would really love the Neil (Parable) and Smoke (Southpole) versions for the alternative Parasites firmware of Clouds :)

Will these be featured in a future release? Really hope so :)

Thanks and keep up the good work!

bionrg wrote: Fri Mar 08, 2019 12:19 am
bsp804 wrote: Thu Mar 07, 2019 9:24 pm @bionrg / melodyz: I'm on it (~70% done).

Are there any other (open source) modules you want to see in the "final" ?
(please point me to the sources!)
SouthPole & (Parasites)
https://github.com/gbrandt1/southpole-vcvrack/ (https://github.com/gbrandt1/southpole-vcvrack/)

Parable:
https://github.com/adbrant/ArableInstruments/ (https://github.com/adbrant/ArableInstruments/)

Arable
https://github.com/adbrant/ArableInstruments (https://github.com/adbrant/ArableInstruments)


any of these if you can will be appreciated.
Thanks a lot!!

Post

Okay, going to do that, but I don't think it's a graphic issue because i run programs with more GUI resources.
Although I don't know what are the specs of the official VCV Rack Standalone.

Post

Downloading now, thanks for the update!

Post

johnstigter wrote: Thu Mar 14, 2019 4:07 pm Quick question: are the modules quoted below in the new release (March 2019)? I can't seem to find them. Would really love the Neil (Parable) and Smoke (Southpole) versions for the alternative Parasites firmware of Clouds :)
Then I suggest you haven't looked close enough... Smoke has been there since I first used VeeSee last March.

Post

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
True! But I'm guessing it doesn't have the alternative Parasites mode?

https://github.com/gbrandt1/southpole-vcvrack (https://github.com/gbrandt1/southpole-vcvrack)
Extra "Southpole Parasites" for parasites firmware based modules are on a separate branch

toonertik wrote: Fri Mar 15, 2019 10:40 am
johnstigter wrote: Thu Mar 14, 2019 4:07 pm Quick question: are the modules quoted below in the new release (March 2019)? I can't seem to find them. Would really love the Neil (Parable) and Smoke (Southpole) versions for the alternative Parasites firmware of Clouds :)
Then I suggest you haven't looked close enough... Smoke has been there since I first used VeeSee last March.

Post

johnstigter wrote: Fri Mar 15, 2019 2:12 pm True! But I'm guessing it doesn't have the alternative Parasites mode?

https://github.com/gbrandt1/southpole-vcvrack
Extra "Southpole Parasites" for parasites firmware based modules are on a separate branch

toonertik wrote: Fri Mar 15, 2019 10:40 am

Then I suggest you haven't looked close enough... Smoke has been there since I first used VeeSee last March. EDIT >> July.. March was official VCV :dog:
Correct .. Lets hope they get added... but it could be they are not available, other wise I am sure Bsp would have already added them :shrug:

Post

@johnstigter: "Smoke" is there. The ArableInstruments modules didn't work (crashed) so I removed them. Some of the Southpole modules didn't work, either (can't remember which ones). Regarding the firmware: I may take another look at this but no promises (porting the Mutable instruments stuff to Windows/VisualC++ was a lot of work and to be honest I'm not so keen on doing it all over again)

@espejoooo221v: from the looks of it, I suspect that render-to-texture / GL framebuffer objects don't work correctly on your system (maybe your driver only supports power of two texture sizes). Not much I can do about this. Let me know if the driver update fixed it !






Here's a One Synth Challenge type demo track I made with VeeSeeVSTRack:
https://youtu.be/XTpLfcz-6Vo
  • 23 instances
  • 465 modules, 90% CPU load :-)
  • no other effects, samples or instruments were used
  • Made with 100% free open source and / or selfmade software (except for the OS+drivers)

And another update since I found an issue with the "MIDI Note On" idle detection mode (playing a note shortly before it turned idle didn't reset the idle timeout):

Code: Select all

** March 15th, 2019
- fix "MIDI Note On" idle detection mode
- add configurable threshold settings for MIDI idle detection (short, default, long)
- add new demo video: https://youtu.be/XTpLfcz-6Vo
veeseevstrack_0_6_1_win64_bin-15Mar2019.7z (win64)
veeseevstrack_0_6_1_win32_bin-15Mar2019.7z (win32, unsupported)

Post

And the updated Linux build can be found at veeseevstrack_0_6_1_lin64_bin-15Mar2019.tar.gz.

@bsp804 - Thanks again ! :)

Best regards,

Dave Phillips

Post

re: graphics issues - As bsp804 has pointed out, you may need to update your video device and/or driver. VCV Rack does require support for OpenGL 2.0 with the GL_EXT_framebuffer_object extension. On Linux you can check for that by running the following command:

Code: Select all

$ glxinfo64 | grep GL_EXT_framebuffer_object
On my system that results in this report:

Code: Select all

$ glxinfo64 | grep GL_EXT_framebuffer_object
    GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, 
    GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, 
I don't know how to do the same on another platform, but checking for that support will tell you instantly whether your OpenGL is up to the requirements for VCV Rack.

HTH,

dp

Post

Sorry for late reply.

@bsp804 . Updating the driver for my graphic card doesn't fix this. sad. What is that extension render-to-texture?, sorry for my ignorance in graphics. Also I agree that all my system is old, but is fine with me.


@studiodave . Thanks for the detailed explanation, I downloaded a program called "OpenGl Extension Viewer". And looks like I have the extension, so it must be another reason.
You do not have the required permissions to view the files attached to this post.

Post Reply

Return to “Modular Synthesis”