Trancit.
chaseHi –
Just a quick note here – I donloaded your Zynwave free to try it out
– nice app and seems to be coming up strong since v2.2
anyhow – wanted to let you know – when closing it with some more advanced vst – you have to close it twice to get it to close.
TrancitThis is an issue we already have sorted out:
It happens, if you use any plugin from FXpansion like Synth Squad, Geist…
Happens in other hosts as well (not in all of course).
Trancit
chasethanx for the reply and glad to hear you have it sorted out.
I’m using plugins from FL Studio: Direct wave – Toxic – Harmless
– two maybe three instances of some at times.
Any projection as to a fix now that you know what the issue is?
btw,
I was impressed with some of the features Zynwave has
Like the look and feel of it for sure – I miss some features of my other apps but you all are in your infancy still from what i understand.
definitly like alot you guys have though
TrancitHave tried here with a few instances of DirectWave and Harmless, but no problems on closing…
Trancit
chaseHmmm – perhaps its the combo i had going – don’t know –
I’ll re-opend the project tonight and see exactly what i have in it
Edit:
Okay I opened up the project last night and this morning to try some things.
Got it to crash twice – though i think i know what the issue is – a vst was loading and i tried to delete the track.
Toxic in a second monitor window working fine now.
I have about 15 to 20 vsts in this project – none FXpansion so it could be any combo there of causing the issue i posted about.
I did notice one thing – i tried a new project with DrumAxx from Imageline.
used Drum in the editor and the Keys do not match with Drumaxx at all.
Drumaxx’s D5 is (gosh i hope i remeber correctly) G3 maybe?
Drumaxx’s C5 is Podiums C3
At any rate they do not jive at all.
I did download a demo from FXpansion as I’m familiar with there BFD2 and tried it in Podium – sure enough it didn’t close properly and as you mentioned you are already aware of this.
So what ever is causing the issue it’s probably the same thing as with FXpansions vst.
It doing the exact same thing with one of the plugins I’m using obviously.
So i take it when the fix comes for FXpansion vst’s so will it for which ever is also cusing it in my project.
Did you have a time frame of a fix or is this on FXpansion to fix it?
( which would mean it is on which ever plug-in I’m using that is causing the same issue for them to fix it as well is why I’m askling.)
Have another inquiry but will post another thread
end of edit
Trancit@chase wrote:
Drumaxx’s C5 is Podiums C3
That´s the way how IL and some other handle Midi. There are different midi standards. The logical way is to have the middle C (note number 60) on C5. But the most known standard is with middle C as C3, which means having to handle with minus values for the 2 lowest octaves.
But I didn´t noticed other problems with midi keys, but will check again
The problem with other VST´s seem to be the quite unclear SDK…Developers can handle things in different ways, which sometimes break the rules of the normal VST standard and lead in many cases to incompatibilities, which the DAW developers have to solve by changing the way of handeling plugins…
I think, this is a never ending story and one the biggest pro reasons of closed systems like Propellerheads Reason/Record.
Trancit
TrancitI´ve just checked Drumaxx here and apart from the different midi standards, which are used, it works completely normal…just 2 octaves lower: Podium C1 is drumaxx C3, D1 is D3 and so on…
Trancit
TrancitJust checked out with Toxic as well…whole combi: Sytrus, Drumaxx, Harmless, Direct Wave and Toxic…
No problems on exit…but working with single monitor here, so perhaps it´s the problem with Toxic on the second screen…
Trancit