I am indeed using 32-bit. I only have this problem with Zebra2 and Zebralette, but I've only tested it recently enough with EZDrummer, M1 LE, Synth1, BR808, Zebra2, Zebralette and Oatmeal. I'll try it with some of my other VSTi's and post if I find another one with this issue.

I switched to default theme and tried making those changes to the source, but now the window is blank grey/blue, AND it spawns as a desktop environment window rather than inside of LMMS. If this is only happening to me, it could be a fluke in my Linux installation or Zebra2 copy, right? Maybe I'll try installing LMMS on windows, or setting up another partition with Linux to test in, just to get the maximum amount of data.


On Tue, Jan 29, 2013 at 3:47 AM, Mike Choi <rdavidian71@gmail.com> wrote:
BTW, I see from your screens you have there cutom theme, could you also try with default theme or style.css?

-Mike


On Tue, Jan 29, 2013 at 10:29 AM, Mike Choi <rdavidian71@gmail.com> wrote:
Hi,

And rre you on 32bit Linux? As Zebra2 is loaded as VSTi and not an effect, I think that should not be affected by later GUI patch for VST effect windows.
Have you noticed such problems with any other VSTi? 

I now tried that on VirtualBox 3.5.0-17-generic, wine Qt 4.8.5, GCC 4.7.6 2012208 (prerelase), wine 1.4.1, 32bit and this seems to load Zebra2 GUI ok.

I dont have access into current lmms git from my test computer now, but maybe could you try following change in lmms/plugins/vst_base/VstPlugin.cpp?

And In this function: void VstPlugin::showEditor( QWidget * _parent, bool isEffect )
Make this code block
else
{
sw->setWindowFlags( Qt::WindowCloseButtonHint );
sw->setWidget( m_pluginWidget );

QX11EmbedContainer * xe = new QX11EmbedContainer( sw );
xe->embedClient( m_pluginWindowID );
xe->setFixedSize( m_pluginGeometry );
xe->move( 4, 24 );
xe->show();
}
Look like:
else
{
QX11EmbedContainer * xe = new QX11EmbedContainer( m_pluginWidget );
xe->embedClient( m_pluginWindowID );
xe->setFixedSize( m_pluginGeometry );
xe->show();
}

Well if that wount help you, try instead remove all lines from this file, containing "setAttribute( Qt::WA_TranslucentBackground )" text or "setWindowFlags".

Thanks, Best regards
- Mike C.

On Tue, Jan 29, 2013 at 1:15 AM, John Serafino <lzrblade@gmail.com> wrote:
Removing them both fixes it. Adding back 1c9c76f breaks it again, and I cannot have 32e9ddc without 1c9c76f.


On Mon, Jan 28, 2013 at 4:56 PM, Mike Choi <rdavidian71@gmail.com> wrote:
Hi, 
I am currently using wine 1.3.28, qt 4.7.4, gcc 4.6.1, 32bit with some integrated graphic card and this seems to work. 
I will try with a newer version.

To identificate concrete patch, you can try to de-select (to remove) that patches:
pick 1c9c76f VST GUI fixes, improvements
pick 32e9ddc VST effect control window re-design

via this git command
git rebase 071358bd98f7b039044d6f80c403fe4c66d0124b --interactive

Best regards
MIke C.


On Mon, Jan 28, 2013 at 7:09 PM, John Serafino <lzrblade@gmail.com> wrote:
I still have the problem with the new patch, sync enabled or not. My current wine version is 1.4.1, my current qt version is 4.8.3, and gcc is 4.7.2.


On Mon, Jan 28, 2013 at 2:31 AM, Mike Choi <rdavidian71@gmail.com> wrote:
BTW, I couldn't reproduce missing GUI problem, but because of sound issues I guess that could be too connected with the wrong sample rate settings of shared memory patch. So otherwise if that will not help you, let me know   also please what Qt, Wine and Gc versions you are using.

Thanks,
-Mike C.


On Mon, Jan 28, 2013 at 9:21 AM, Mike Choi <rdavidian71@gmail.com> wrote:
Hi,

Can you try again with latest patch I uploaded now?

Well it seems as I moved samplerate initialization into shared memory (this should be optional with "Sync VST plugins to host playback" option from general settings, see screenshot) it really did affected Zebra2, Zebralette, etc because those plugins seems to require samplerate to be set during init part, not as before. So I moved this samplerate initialization into plugins init part. And Zebra2 sound output seems to work now. So could you try this last patch also and if no change with Global Settings option turned on / off? (see screenshot).

BTW it also seems as I moved samplerate settings into init part, almost all VST crashes from Master channel are gone now with this sync/ shared memory patch, no matter actual playback.

-----

As for sound cracking issue with dBlue Glitch with VST sync option on, it seems those sound artifacts are there even with the highest precision of Sync I got from sync timers, or even samplerate current position on plugin side (if syncing to host is done quite often, like every 1, 4ms..), but if sync to host is not so frequent , like every 10ms or so, and rest recounted on plugin side, It seems there is much less sound crackling, so I guess those artifacts come from rounding errors or so on lmms host sync part if that sync is done too often. I will try to dig it more.

Best regards
Mike C. 

On Sun, Jan 27, 2013 at 10:42 PM, John Serafino <lzrblade@gmail.com> wrote:
Okay, confirmed with latest GIT version. It happens regardless of whether or not the VST sync patch is applied, ruling it out IMO. Just to present as much data as possible, here is a screenshot while the VST is loading, with the GUI visible: https://lh3.googleusercontent.com/-SVIaKC_Qe1w/UQWepIpEmxI/AAAAAAAABEA/tcRmmp0pxSE/s1600/Screenshot+from+2013-01-27+15%3A16%3A38.png And this is what happens when the VST finishes loading: https://lh4.googleusercontent.com/-vTMye10Df5A/UQWepC8OAjI/AAAAAAAABD8/yABTyzbq_jU/s1108/Screenshot+from+2013-01-27+15%3A18%3A06.png


On Sun, Jan 27, 2013 at 12:14 PM, Mike Choi <rdavidian71@gmail.com> wrote:
Hi,

Thanks John, I will check this tonight.

BTW I just released a patch update which adds global option to turn VST sync on / off. (no localisations yet)
You can get it from this link:

I was also trying to investigate this sound crackling issue that Chrissy mentioned, but my test computer keeps crackling all time now, I will check it better from home, but if this will be an issue, I think it would be better to leave that VST Sync patch for some later release, as it will be fixed overall, but I will look on this tonight.

Best regards
Mike C.

On Sun, Jan 27, 2013 at 3:59 PM, John Serafino <lzrblade@gmail.com> wrote:

Using Linux with 8 gb of DDR 3 ram and a dual core 3 ghz CPU. I'm not sure if I have the latest patch or not, so I'll check on that when I get home today. I usually scale my work space across two 1600x900 monitors, but I've never had any problems as a result.

I can check on my onboard sound card when I get home too, if you need thus data.

On Jan 27, 2013 1:58 AM, "Mike Choi" <rdavidian71@gmail.com> wrote:
Hi,

I will look on this John, also are you using Linux or Windows and latest patch? What are your computer spec?
As per GUI problems I am aware now just that if you re-size lmms workspace to something small, than if you load new plugin it will affect resulting window size, but will look on this too.

As per VST sync. patch, (please assure at first you have latest patch from link below)  I personally dont have problems with it on winXp and two Linux machines. Chrissy do you have any problems with latest patch?

Also as per potential VST effects, I think this sync patch should not do any wrong coz it is targeted on VSTs which do sync to host normally, so without it  they don't work either as supposed to be. But I may add this Sync functionality like on/off feature into global settings today.

Best regards
- Mike C.

On Sat, Jan 26, 2013 at 11:18 PM, John Serafino <lzrblade@gmail.com> wrote:
Something borked Zebra2 compatibility around the time this was introduced. Not sure if the two are connected though. Zebra2 still works, but the GUI disappears to grey as soon as it finishes loading. I'm guessing it's actually related to the GUI patches, but I posted it here cause... well cause. ;)


On Sat, Jan 26, 2013 at 4:01 PM, Tobias Doerffel <tobias.doerffel@gmail.com> wrote:
Hi,

2013/1/24 Mike Choi <rdavidian71@gmail.com>:
> I uploaded new version of the patch and cleaned the code. Should be faster,
> more accurate sync.

Is there any potential impact on existing code/functionality? I'm
asking because I'm not sure whether to include it for the 0.4.14
release. How do you estimate the stability of current VST
implementation?

Best regards

Tobias

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel



--
Johnny

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel






--
Johnny





--
Johnny



------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel




--
Johnny





--
Johnny