KVR Audio

Mighty_Hero · Post by **Mighty_Hero** » Tue Oct 12, 2004 7:26 am

Hey gang. I have had RMIV problems here recently (when the upgrade came out, I obviously bought it).

Stubar in another thread [ http://www.kvr-vst.com/forum/viewtopic.php?t=57150 ] posted a problem with his stylus. I misread his post as it's been happening the whole time (as in other previous versions) which is impossible.

I am working on a track right now in (well was) 4.5, and when I bounced the track down, sure enough the audio stuttered on stylus parts only.

Now I know for a fact stylus works fine in 4.12 (been doing audio demos a long time in 4.12 and using stylus), so I never thought anything more about it, when I read his post.

I thought I was doing new projects in 4.12 (I like to let the new versions sit a while before going full on testing), but I had the new 4.5 icon on my desktop. I was working away in 4.5 never 'knowing' it, bounced it down, and boom....stuttering.

Keep in mind, NO changes what so ever were made to my DAW, no new installs etc etc. When you bounce down something in 4.12 it works flawlessly. (I must tell you, I left orion because of similiar stuttering problems and Rich said it 'must' be stylus, so when I bought fl studio WAYYY back and it worked fine, I knew it wasn't stylus, and never checked on this again since I was now using fl studio)

So I uninstalled fl studio 4.12 all together thinking the two versions installed back to back, might be causing a problem somewhere. Good thing I keep .execs and backups. The moment I bounced down my track in 4.5 (AFTER running reg clean, checking for dup dll's, registry additions, etc etc) I still got the stuttering.

I re-installed fl studio 4.12, and sure it couldn't find flangus (since I used it on the flp project from 4.5), but once I bounced it down in 4.12, stylus (the whole track whatever you want to call it), played fine. I am now BACK on 4.12 and will stay here until we get this resolved. I am more than willing to check anything you want, but I am certain there is something wrong. I am a computer technician by day (just don't know programming AT all

), and the only thing I have changed at all, is loading new wav samples.

From another thread, I also am having RMIV troubles, and I have asked if the newest wrapper might fix these problems. As computer guys yourself, you can understand why I am not so willing to try the new wrapper (and add stuff to my registry, h.d. etc etc) when the newest version (5 or whatever) is shortly coming out. [ http://www.kvr-vst.com/forum/viewtopic.php?t=57153 ]

Please help us find the problem, so we can enjoy fl studio the way it was meant to be used. I am a DIE hard fl studio user, and would really like to resolve these little problems.

I also know I posted either here or on looptalk about the drivers showing up twice for 2496 cards. If we could get this resolved, I think all the bugs will be worked out. I updated these just normal, and also because I thought maybe it would help the original problem I was having in 4.1.1 of RMIV. You can see the post dates....

Thanks again gentlemen!
Brice

Stubar and whoever else might not have noticed any of this, Gol and gang will fix the problems, they rock

Mighty_Hero · Post by **Mighty_Hero** » Tue Oct 12, 2004 6:01 pm

I know you guys are busy getting the newest version out in 'time' (just saw the ad post, looks great!)
Can you guys please see what changed in I guess the wrapper from 4.12 to 4.5.2? Only stylus and RMIV are having issues that I have found.
For now I am composing again in 4.12 and all is well. I am patient, just really want this looked at. I would also like to be part of the next beta testing after 5 is released.
Thanks.

reflex · Post by **reflex** » Wed Oct 13, 2004 6:58 am

I have tested the Stylus problem in FL 4.1.2 and it happens there too (realtime that is), so the actual problem was always there and appears to be a UVI engine problem. I have contacted both Spectrasonics (repeatedly) and the PlugSound people, so I hope they'll be able to look into it, but so far I haven't heard back from either.

The problem happens both realtime and when rendering, except that you need to have a relatively big buffer size (say 100ms) to notice it. It could be that the buffer size for rendering has changed between 4.1.2 and 4.5, I'm not sure anymore.

Mighty_Hero · Post by **Mighty_Hero** » Wed Oct 13, 2004 3:54 pm

Ok so maybe the rendering buffer changed?
This makes sense to me, since I haven't changed my buffer settings as far as the audio card.
Ok well for now since it works in 4.12 fine, I am composing in 4.12.

Hopefully someone will find the problem and the 5 coming out soon will work fine too.
So what is spectrasonics saying on this subject when you contact them?

Jaeson Merrill · Post by **Jaeson Merrill** » Thu Oct 14, 2004 1:31 am

apparently nothing.... they havent gotten a response, afaik..

this is an issue that definetly NEEDS attention.

Mighty_Hero · Post by **Mighty_Hero** » Thu Oct 14, 2004 3:19 am

Yeah no joke!
I don't want to have to stay stuck in 4.12 because of little bugs.....I want to use the new features I have seen coming out

Mighty_Hero · Post by **Mighty_Hero** » Fri Oct 15, 2004 4:10 am

Anyone had time to check into this perhaps?

kode_poet · Post by **kode_poet** » Fri Oct 15, 2004 3:35 pm

I've always had the bug with FL and a few VSTis that use samples. Some of them are

1. Groove agent, which doesnt recognize on/off MIDI notes apparently.

2. USB Plugsound modules - Apparently some latency problems as the buffers increase. Not only when played but also when rendered.

3. Stylus. - The loops start getting out of sync as the song progresses. One quick fix I've had for this one is to chop the MIDI notes in the piano roll every bar, depending on the loop length.

I dunno if this has anything to do with the VSTis or with Fruity Wrapper. In the USB Plugsound manuals, it is mentioned that they had 'improved' compatibility with FL and sync problems, so I'm guessing its more with them than with Image Line. About the other ones I dont know, but I hope this gets resolved in the new version.

PS. AND WHERE THE HELL IS MY SUSTAIN PEDAL SUPPORT!!!

j/k

Jaeson Merrill · Post by **Jaeson Merrill** » Fri Oct 15, 2004 4:08 pm

also, drum brains that send a midi on note, and then another midi on note at 0 velocity to imitate a midi off note will not work in FL....

i love FL, and i hope this doesnt get me flamed, but most of these problems dont exist in other hosts.

ouroboros · Post by **ouroboros** » Fri Oct 15, 2004 5:02 pm

My impression of this thread is that it is filled by sincerely happy users of FL studio so to be clear, this post isn't a knock on the problems you are all having: sounds like you want to use FL to the fullest!

But for whatever reason, for the first time, it occurs to me what a ridiculous task de-bugging is. I have run into some problems installing some new software and after a lot of time realized it was a hardware/driver issue afterall. Anyways, it's Friday and I'm musing about how difficult it must be to respond and address all the problems reported about a given software in differnt countries on different machines with different OS config's. Blecccch. thank God I'm not a programmer. (Of course the repeatability of the problems makes it easier to pin down I imagine.)

The SE preset bug in FL has annoyed me for a while, but that is SE's issue.

Anyways, carry on.

Mighty_Hero · Post by **Mighty_Hero** » Fri Oct 15, 2004 5:28 pm

I think anyone who spends time here, know how I feel about studio.

I just want to get these things resolved, so I can install the soon to be out, new version, and the vsts I use work right. Besides I now have atmosphere problems as well (after running the updater), so here's another thing for me to get upset about

It sucks when something is wrong, when you just want to jam, but these things happen.

ouroboros · Post by **ouroboros** » Fri Oct 15, 2004 6:08 pm

Agreed

Sounds hair-pullingly frustrating, and I wish you the best!

topaz · Post by **topaz** » Fri Oct 15, 2004 6:08 pm

try making videos with sound, mp3's of the problem, take the IL team for a great meal, let them use your family holiday home, etc.

you (may) get a fix

stubar · Post by **stubar** » Sun Oct 24, 2004 8:12 am

hey man...

im kinda glad that someone else has a problem with this!! Cos i did feel all alone and I gave up hope in sorting the stylus - FL Studio thing out until RMX or v5 of FL was released!! which is a shame as I do like the sounds that come outta stylus. (was even considering changing vst host!!)

Mightyhero - am I right to think that using 4.12 makes everything okay for stylus?!

just to reitterate my problems - on playback in real time in FL, stylus does stutter a little, but it I can bear it.... I have to click to a part of the tune that Stylus "likes" and then click to the beginning and it seems to work ok.

When rendering the "sync/stutter" is completely noticeable - sounds like a deaf DJ mixing in a new tune!!

Im with you on this one dude.. I like using FL Studio, I would be happy to (as a temporary workaround) make a tune in 4.5 then load it into 4.1 to render to wav, if this works, but I feel quite resigned at the minute to leave Stylus on the shelf until RMX is released then reapproach the problem.

Especially seeing as one of the spectrasonics dudes on here has said that RMX DEFINATELY does not have this problem when working in FL Studio....... I am not so confident...... but then again I hope I am wrong and it works fine!!

Im not gonna go on too much, just wanted to stick together on this one man... If I find a solution I will let you know for sure...

play · Post by **play** » Sun Oct 24, 2004 8:42 am

Here's a snippet from a recent exchange with the Exciton developer regarding the midi-processing in FL-Studio. It might shed some light on the issue at hand, but I doubt that it's something Gol isn't aware of. So it's either deliberately that way or not considered a real host problem.

At any rate it seems that the plugin developer can successfully adjust to this "feature"! So it might be a good idea to pester them a bit.

Problem
-------
MIDI messages are dropped with playing on FL sequence.
Drop-out patterns depend on the playback modes.
(sequencer, live play, mix down, etc)

Cause
-----
According to the VST interface specification, each MIDI message packet must be sent to a plugin just after the prevoius packet is completely processed. But FL sometimes sends a packet even if some of previous messages are left unprocessed. (In plain words, it sometimes sends MIDI events to plugins too first.)

Solution
--------
We have improved the MIDI message processing for FL users.
As we checked, the problem has been resolved.
We need beta testers. If you have some time to help us...

Gol, JMC, etc. Fl Studio problems big time.