PlanetZ forums - scopeusers.com

I just tried something today.. i made a copy of my xtcproject.pro and renamed it to xtcproject.dev
And then i imported into sfp..
It told me about asio modules etc that were allready used, but i actually got a small box/device called xtcproject on my sfp desktop!
nothing happened when i doubleclicked it..
but this makes me think! is it possible for someone with SDK to somehow open up the xtc project.. and make ins/outs..
that way, i could open the sfp routing window in xtc mode!
and we would have a mixed SFP/xtc mode! the best of both worlds.

is this somehow possible??

My hopes for Scope 5.0 or, at least, Scope 6.0...
Anyway is a matter for Sconic|core development team!

it wont be in scope 5.0
i already asked ralf
but in 2000 years when they will release scope 6.0, maybe it will!

sigh!

the19thbear wrote:I just tried something today.. i made a copy of my xtcproject.pro and renamed it to xtcproject.dev
And then i imported into sfp..
It told me about asio modules etc that were allready used, but i actually got a small box/device called xtcproject on my sfp desktop!
nothing happened when i doubleclicked it..
but this makes me think! is it possible for someone with SDK to somehow open up the xtc project.. and make ins/outs..
that way, i could open the sfp routing window in xtc mode!
and we would have a mixed SFP/xtc mode! the best of both worlds.

is this somehow possible??

Interesting observation.

I think I will try check this out in SDK.

The ASIO errors are likely because your active project has ASIO modules loaded and this will conflict with the ones in XTCproject.dev.
In any case, I think XTCproject.pro needs the application interface (ASIO), but you could try inserting an empty project as a device. This would probably defeat the original purpose though. Try both!

Also try renaming this device to .mdl extention.

i'm sorry but i dont really understand.. could you explain again?? thanks!

anayone out there with the sdk and time?