Page 2 of 2
Re: "Copy" Causes Crash
Posted: Fri Apr 19, 2013 9:23 am
by billv
Perfect Human Interface wrote:Yeah, syncs to FL's playback
Cool.
I'm wondering now if if Trog can make use of this in his VST PPQ set up, wich is spot on everywhere,
except FL, this could be a solution. I wonder weather a FS Standalone export
could somehow tell what host it was in

?????, providing a way for Trog to flick a switch, so to speak.
Re: "Copy" Causes Crash
Posted: Fri Apr 19, 2013 11:03 am
by Perfect Human Interface
Hmm, well, if not, there are other ways to flick that switch.
There's actually a primitive that makes a module only show up in FL FS (or only in non-FL FS). I assume it's for compatibility issues, but from the way it sounds I have doubt it would effect exported programs.
But then I wonder what would happen when you set something to only show in non-FL FS when you're using FL FS...
Re: "Copy" Causes Crash
Posted: Fri Apr 19, 2013 11:48 am
by billv
Perfect Human Interface wrote: I assume it's for compatibility issue
Was always a bit of a grey area for me. i thought it was a "safegaurd" to protect FLSM users
modules, inside thier OSM's getting poached by SM users.
Re: "Copy" Causes Crash
Posted: Fri Apr 19, 2013 8:19 pm
by Perfect Human Interface
I haven't tested it at all but I actually suspect it may just be for controlling whether it shows up in the toolbox and nothing more. The Flowstone developers likely use it just to control which components show up for which users rather than maintaining separate lists.
Re: "Copy" Causes Crash
Posted: Sat Apr 20, 2013 4:03 am
by Jay
just tried exporting the FL timing primitives and the FL clock into a schematic and loading them into FS but alas they get replaced with the non FL variants when loaded into FS! try it!
does not look like they are interchangeable between the two apps

Re: "Copy" Causes Crash
Posted: Sat Apr 20, 2013 6:24 am
by billv
Jay wrote: FL timing primitives and the FL clock into a schematic and loading them into FS but alas they get replaced
yeh , this behaviour has always been standard, since FLSM began , it's always done this.
Can I ask exactly "How" the FS clock is built, as im still on 10.09.
Is it still taking a green output from the PPQ??????
Re: "Copy" Causes Crash
Posted: Sun Apr 21, 2013 12:59 am
by billv
Jay wrote:just tried exporting the FL timing primitives and the FL clock into a schematic
You might find this new version of the the old FLSM Clock interesting
viewtopic.php?f=3&t=1255&start=40#p4961
Re: "Copy" Causes Crash
Posted: Sun Apr 21, 2013 1:27 am
by Perfect Human Interface
billv wrote:Can I ask exactly "How" the FS clock is built, as im still on 10.09.
Is it still taking a green output from the PPQ??????
Yeah, have a look.
http://i40.photobucket.com/albums/e241/ ... /clock.png
Re: "Copy" Causes Crash
Posted: Sun Apr 21, 2013 2:03 am
by billv
Click the link, several times, no access

Re: "Copy" Causes Crash
Posted: Sun Apr 21, 2013 9:54 am
by billv
Tried again, this time I saw it. And when I did, I
Bloody hell, thats the same clock we've always had.
And there calling this the FS CLock??
Where's ruby?....not required?......old FLSM method better?......
hhhmmmmmmmm........