Home » The PARIS Forums » PARIS: Main » I think maybe this is why FXT isn't working-feedback please
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66409 is a reply to message #66397] |
Sun, 09 April 2006 18:03   |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
If FX teleport is accessing the partitions using Windows Networking, then
I can't see why the formats would make any difference.
But perhaps it doesn't.
To be honest, if I understand what it's doing properly, I can't see why it
actually needs to access the drives at all. I would have thought FX teleport
would simply talk directly from one machine to the other, from the teleport
app on one machine to teleport on the other, app to app, rather than accessing
the drive. Accessing the drive would simply slow the process down, as drives
are slow of course. I mean why does teleport need to access the drive? I
mean other than to read the plugins off the local machine, but as far as
transferring audio data between machines surely it doesn't have to read the
drive. The audio app would read the track off the drive and feed it to teleport,
which would feed it down the network cable to teleport at the other end,
apply the effect, and send it back to teleport, which would feed it back
to the app. Can't see why it needs to access the drive... other than to
access your plugins, but that would be on the local machine surely?
Cheers,
Kim.
"DJ" <animix_spam-this-ahole_@animas.net> wrote:
>My system drive (running Win XP) is formatted FAT 32 (I have my reasons
for
>this). FXT will not scan and recognize the plugins on the host machine and
>does not recognize my server machine either. The system drive on the server
>is formatted NTFS. All folders are being recognized through My Network
>Places and the files are accessable between both machines over the network,
>but for the life of me, I casn't get FXT to work ads advertized.
>
>I have tried everything. It just occurred to me that the drives on the host
>and server were formatted differently.
>
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66410 is a reply to message #66409] |
Sun, 09 April 2006 18:03 |
Don Nafe
Messages: 1206
Registered: July 2005
|
Senior Member |
|
|
I asked my better half and she seems to remember something about NTFS
recognising FAT 32 but not the otherway around.
My LAN guru is not around so I can't ask him where ther might be "issues"
but I will tomorrow AM
Don
"Kim" <hiddensounds@hotmail.com> wrote in message news:4439aed3$1@linux...
>
>
> If FX teleport is accessing the partitions using Windows Networking, then
> I can't see why the formats would make any difference.
>
> But perhaps it doesn't.
>
> To be honest, if I understand what it's doing properly, I can't see why it
> actually needs to access the drives at all. I would have thought FX
> teleport
> would simply talk directly from one machine to the other, from the
> teleport
> app on one machine to teleport on the other, app to app, rather than
> accessing
> the drive. Accessing the drive would simply slow the process down, as
> drives
> are slow of course. I mean why does teleport need to access the drive? I
> mean other than to read the plugins off the local machine, but as far as
> transferring audio data between machines surely it doesn't have to read
> the
> drive. The audio app would read the track off the drive and feed it to
> teleport,
> which would feed it down the network cable to teleport at the other end,
> apply the effect, and send it back to teleport, which would feed it back
> to the app. Can't see why it needs to access the drive... other than to
> access your plugins, but that would be on the local machine surely?
>
> Cheers,
> Kim.
>
> "DJ" <animix_spam-this-ahole_@animas.net> wrote:
>>My system drive (running Win XP) is formatted FAT 32 (I have my reasons
> for
>>this). FXT will not scan and recognize the plugins on the host machine and
>>does not recognize my server machine either. The system drive on the
>>server
>>is formatted NTFS. All folders are being recognized through My Network
>>Places and the files are accessable between both machines over the
>>network,
>>but for the life of me, I casn't get FXT to work ads advertized.
>>
>>I have tried everything. It just occurred to me that the drives on the
>>host
>>and server were formatted differently.
>>
>>
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66411 is a reply to message #66410] |
Sun, 09 April 2006 17:59 |
Deej [1]
Messages: 2149
Registered: January 2006
|
Senior Member |
|
|
My system drive on the Host machine is FAT 32. The system drive on the
server is NTFS. They are seeing/sharing data over the network just fine.
Perhaps there is some problem with this on the FT level, however, the
problem appears to be solely within FXT as it will not even find the drives
running on the host computer when run from the host computer.
"Don Nafe" <dnafe@magma.ca> wrote in message news:4439b0a0@linux...
> I asked my better half and she seems to remember something about NTFS
> recognising FAT 32 but not the otherway around.
>
> My LAN guru is not around so I can't ask him where ther might be "issues"
> but I will tomorrow AM
>
> Don
>
>
> "Kim" <hiddensounds@hotmail.com> wrote in message news:4439aed3$1@linux...
> >
> >
> > If FX teleport is accessing the partitions using Windows Networking,
then
> > I can't see why the formats would make any difference.
> >
> > But perhaps it doesn't.
> >
> > To be honest, if I understand what it's doing properly, I can't see why
it
> > actually needs to access the drives at all. I would have thought FX
> > teleport
> > would simply talk directly from one machine to the other, from the
> > teleport
> > app on one machine to teleport on the other, app to app, rather than
> > accessing
> > the drive. Accessing the drive would simply slow the process down, as
> > drives
> > are slow of course. I mean why does teleport need to access the drive? I
> > mean other than to read the plugins off the local machine, but as far as
> > transferring audio data between machines surely it doesn't have to read
> > the
> > drive. The audio app would read the track off the drive and feed it to
> > teleport,
> > which would feed it down the network cable to teleport at the other end,
> > apply the effect, and send it back to teleport, which would feed it back
> > to the app. Can't see why it needs to access the drive... other than
to
> > access your plugins, but that would be on the local machine surely?
> >
> > Cheers,
> > Kim.
> >
> > "DJ" <animix_spam-this-ahole_@animas.net> wrote:
> >>My system drive (running Win XP) is formatted FAT 32 (I have my reasons
> > for
> >>this). FXT will not scan and recognize the plugins on the host machine
and
> >>does not recognize my server machine either. The system drive on the
> >>server
> >>is formatted NTFS. All folders are being recognized through My Network
> >>Places and the files are accessable between both machines over the
> >>network,
> >>but for the life of me, I casn't get FXT to work ads advertized.
> >>
> >>I have tried everything. It just occurred to me that the drives on the
> >>host
> >>and server were formatted differently.
> >>
> >>
> >
>
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66412 is a reply to message #66411] |
Sun, 09 April 2006 18:21 |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
"DJ" <animix_spam-this-ahole_@animas.net> wrote:
>it will not even find the drives
>running on the host computer when run from the host computer.
This is on the FAT32 machine or the NTFS machine? You have RTFM'd for drive
formatting requirements I take it? When you say it wont find it, do you mean
it wont find the networked share, or it can't even read the drive, like locally?
Cheers,
Kim.
Cheers,
Kim.
>
>
>"Don Nafe" <dnafe@magma.ca> wrote in message news:4439b0a0@linux...
>> I asked my better half and she seems to remember something about NTFS
>> recognising FAT 32 but not the otherway around.
>>
>> My LAN guru is not around so I can't ask him where ther might be "issues"
>> but I will tomorrow AM
>>
>> Don
>>
>>
>> "Kim" <hiddensounds@hotmail.com> wrote in message news:4439aed3$1@linux...
>> >
>> >
>> > If FX teleport is accessing the partitions using Windows Networking,
>then
>> > I can't see why the formats would make any difference.
>> >
>> > But perhaps it doesn't.
>> >
>> > To be honest, if I understand what it's doing properly, I can't see
why
>it
>> > actually needs to access the drives at all. I would have thought FX
>> > teleport
>> > would simply talk directly from one machine to the other, from the
>> > teleport
>> > app on one machine to teleport on the other, app to app, rather than
>> > accessing
>> > the drive. Accessing the drive would simply slow the process down, as
>> > drives
>> > are slow of course. I mean why does teleport need to access the drive?
I
>> > mean other than to read the plugins off the local machine, but as far
as
>> > transferring audio data between machines surely it doesn't have to read
>> > the
>> > drive. The audio app would read the track off the drive and feed it
to
>> > teleport,
>> > which would feed it down the network cable to teleport at the other
end,
>> > apply the effect, and send it back to teleport, which would feed it
back
>> > to the app. Can't see why it needs to access the drive... other than
>to
>> > access your plugins, but that would be on the local machine surely?
>> >
>> > Cheers,
>> > Kim.
>> >
>> > "DJ" <animix_spam-this-ahole_@animas.net> wrote:
>> >>My system drive (running Win XP) is formatted FAT 32 (I have my reasons
>> > for
>> >>this). FXT will not scan and recognize the plugins on the host machine
>and
>> >>does not recognize my server machine either. The system drive on the
>> >>server
>> >>is formatted NTFS. All folders are being recognized through My Network
>> >>Places and the files are accessable between both machines over the
>> >>network,
>> >>but for the life of me, I casn't get FXT to work ads advertized.
>> >>
>> >>I have tried everything. It just occurred to me that the drives on the
>> >>host
>> >>and server were formatted differently.
>> >>
>> >>
>> >
>>
>>
>
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66414 is a reply to message #66412] |
Sun, 09 April 2006 18:13 |
Deej [1]
Messages: 2149
Registered: January 2006
|
Senior Member |
|
|
This is on the FAT 32 machine.
>do you mean it wont find the networked share, or it can't even read the
drive, like locally?<
It can't even read the drive, like locally.
;o)
"Kim" <hiddensounds@hotmail.com> wrote in message news:4439b30d$1@linux...
>
> "DJ" <animix_spam-this-ahole_@animas.net> wrote:
> >it will not even find the drives
> >running on the host computer when run from the host computer.
>
> This is on the FAT32 machine or the NTFS machine? You have RTFM'd for
drive
> formatting requirements I take it? When you say it wont find it, do you
mean
> it wont find the networked share, or it can't even read the drive, like
locally?
>
> Cheers,
> Kim.
>
> Cheers,
> Kim.
>
> >
> >
> >"Don Nafe" <dnafe@magma.ca> wrote in message news:4439b0a0@linux...
> >> I asked my better half and she seems to remember something about NTFS
> >> recognising FAT 32 but not the otherway around.
> >>
> >> My LAN guru is not around so I can't ask him where ther might be
"issues"
> >> but I will tomorrow AM
> >>
> >> Don
> >>
> >>
> >> "Kim" <hiddensounds@hotmail.com> wrote in message
news:4439aed3$1@linux...
> >> >
> >> >
> >> > If FX teleport is accessing the partitions using Windows Networking,
> >then
> >> > I can't see why the formats would make any difference.
> >> >
> >> > But perhaps it doesn't.
> >> >
> >> > To be honest, if I understand what it's doing properly, I can't see
> why
> >it
> >> > actually needs to access the drives at all. I would have thought FX
> >> > teleport
> >> > would simply talk directly from one machine to the other, from the
> >> > teleport
> >> > app on one machine to teleport on the other, app to app, rather than
> >> > accessing
> >> > the drive. Accessing the drive would simply slow the process down, as
> >> > drives
> >> > are slow of course. I mean why does teleport need to access the
drive?
> I
> >> > mean other than to read the plugins off the local machine, but as far
> as
> >> > transferring audio data between machines surely it doesn't have to
read
> >> > the
> >> > drive. The audio app would read the track off the drive and feed it
> to
> >> > teleport,
> >> > which would feed it down the network cable to teleport at the other
> end,
> >> > apply the effect, and send it back to teleport, which would feed it
> back
> >> > to the app. Can't see why it needs to access the drive... other
than
> >to
> >> > access your plugins, but that would be on the local machine surely?
> >> >
> >> > Cheers,
> >> > Kim.
> >> >
> >> > "DJ" <animix_spam-this-ahole_@animas.net> wrote:
> >> >>My system drive (running Win XP) is formatted FAT 32 (I have my
reasons
> >> > for
> >> >>this). FXT will not scan and recognize the plugins on the host
machine
> >and
> >> >>does not recognize my server machine either. The system drive on the
> >> >>server
> >> >>is formatted NTFS. All folders are being recognized through My
Network
> >> >>Places and the files are accessable between both machines over the
> >> >>network,
> >> >>but for the life of me, I casn't get FXT to work ads advertized.
> >> >>
> >> >>I have tried everything. It just occurred to me that the drives on
the
> >> >>host
> >> >>and server were formatted differently.
> >> >>
> >> >>
> >> >
> >>
> >>
> >
> >
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66415 is a reply to message #66409] |
Sun, 09 April 2006 18:28 |
Edna Sloan
Messages: 304
Registered: October 2005
|
Senior Member |
|
|
I think that is the way it works Kim, it has the plugins stored on the
server(also on the host, in case you dont want to process one on the server)
and applies them there and shoots it back to the host, as I understand it
anyway. This is why it unloads your host cpu workload. It only accesses the
drive for the plugins as you mentioned, and the fxt program itself . Also,
you can stream vistis from the server, but I havent tried this.
E
"Kim" <hiddensounds@hotmail.com> wrote in message news:4439aed3$1@linux...
>
>
> If FX teleport is accessing the partitions using Windows Networking, then
> I can't see why the formats would make any difference.
>
> But perhaps it doesn't.
>
> To be honest, if I understand what it's doing properly, I can't see why it
> actually needs to access the drives at all. I would have thought FX
teleport
> would simply talk directly from one machine to the other, from the
teleport
> app on one machine to teleport on the other, app to app, rather than
accessing
> the drive. Accessing the drive would simply slow the process down, as
drives
> are slow of course. I mean why does teleport need to access the drive? I
> mean other than to read the plugins off the local machine, but as far as
> transferring audio data between machines surely it doesn't have to read
the
> drive. The audio app would read the track off the drive and feed it to
teleport,
> which would feed it down the network cable to teleport at the other end,
> apply the effect, and send it back to teleport, which would feed it back
> to the app. Can't see why it needs to access the drive... other than to
> access your plugins, but that would be on the local machine surely?
>
> Cheers,
> Kim.
>
> "DJ" <animix_spam-this-ahole_@animas.net> wrote:
> >My system drive (running Win XP) is formatted FAT 32 (I have my reasons
> for
> >this). FXT will not scan and recognize the plugins on the host machine
and
> >does not recognize my server machine either. The system drive on the
server
> >is formatted NTFS. All folders are being recognized through My Network
> >Places and the files are accessable between both machines over the
network,
> >but for the life of me, I casn't get FXT to work ads advertized.
> >
> >I have tried everything. It just occurred to me that the drives on the
host
> >and server were formatted differently.
> >
> >
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66416 is a reply to message #66415] |
Sun, 09 April 2006 18:26 |
Deej [1]
Messages: 2149
Registered: January 2006
|
Senior Member |
|
|
I guess the last resort will be to reformat my server drive to FAT 32. I'm
not asbout to go the other way and reformat my system drive NTFS on my host
machine. Too much work to reinstall/reauthorize all my apps/plugins. If FXT
doesn't work with F 32, I'll just live without it.
I'm to the point of being totally disgusted with this app anyway. If it
can't locate the host plugins from the host drive, I'm really not too
impressed.
Deej
"Edna" <edna@texomaonline.com> wrote in message news:4439b67d@linux...
> I think that is the way it works Kim, it has the plugins stored on the
> server(also on the host, in case you dont want to process one on the
server)
> and applies them there and shoots it back to the host, as I understand it
> anyway. This is why it unloads your host cpu workload. It only accesses
the
> drive for the plugins as you mentioned, and the fxt program itself .
Also,
> you can stream vistis from the server, but I havent tried this.
> E
>
> "Kim" <hiddensounds@hotmail.com> wrote in message news:4439aed3$1@linux...
> >
> >
> > If FX teleport is accessing the partitions using Windows Networking,
then
> > I can't see why the formats would make any difference.
> >
> > But perhaps it doesn't.
> >
> > To be honest, if I understand what it's doing properly, I can't see why
it
> > actually needs to access the drives at all. I would have thought FX
> teleport
> > would simply talk directly from one machine to the other, from the
> teleport
> > app on one machine to teleport on the other, app to app, rather than
> accessing
> > the drive. Accessing the drive would simply slow the process down, as
> drives
> > are slow of course. I mean why does teleport need to access the drive? I
> > mean other than to read the plugins off the local machine, but as far as
> > transferring audio data between machines surely it doesn't have to read
> the
> > drive. The audio app would read the track off the drive and feed it to
> teleport,
> > which would feed it down the network cable to teleport at the other end,
> > apply the effect, and send it back to teleport, which would feed it back
> > to the app. Can't see why it needs to access the drive... other than
to
> > access your plugins, but that would be on the local machine surely?
> >
> > Cheers,
> > Kim.
> >
> > "DJ" <animix_spam-this-ahole_@animas.net> wrote:
> > >My system drive (running Win XP) is formatted FAT 32 (I have my reasons
> > for
> > >this). FXT will not scan and recognize the plugins on the host machine
> and
> > >does not recognize my server machine either. The system drive on the
> server
> > >is formatted NTFS. All folders are being recognized through My Network
> > >Places and the files are accessable between both machines over the
> network,
> > >but for the life of me, I casn't get FXT to work ads advertized.
> > >
> > >I have tried everything. It just occurred to me that the drives on the
> host
> > >and server were formatted differently.
> > >
> > >
> >
>
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66417 is a reply to message #66416] |
Sun, 09 April 2006 18:51 |
Edna Sloan
Messages: 304
Registered: October 2005
|
Senior Member |
|
|
Well hopefully it does work with fat32! You might check the reqs before you
go to all that trouble. One thing, if you have your plugs installed in
different folders on the host it may get confused? The only indication in
the applet that it found the plugs on the host is that the path is shown in
the lower window, and the dialog says it will use it to install the fx
subfolder. It wont attempt to locate the server plugs till the host
location is indicated. You could try switching the server/host fxt
installations to see what happens. If it then indicates the plugin path in
the "new" host, it may be a fat32 issue.
"DJ" <animix_spam-this-ahole_@animas.net> wrote in message
news:4439b814@linux...
> I guess the last resort will be to reformat my server drive to FAT 32. I'm
> not asbout to go the other way and reformat my system drive NTFS on my
host
> machine. Too much work to reinstall/reauthorize all my apps/plugins. If
FXT
> doesn't work with F 32, I'll just live without it.
>
> I'm to the point of being totally disgusted with this app anyway. If it
> can't locate the host plugins from the host drive, I'm really not too
> impressed.
>
> Deej
>
>
>
> "Edna" <edna@texomaonline.com> wrote in message news:4439b67d@linux...
> > I think that is the way it works Kim, it has the plugins stored on the
> > server(also on the host, in case you dont want to process one on the
> server)
> > and applies them there and shoots it back to the host, as I understand
it
> > anyway. This is why it unloads your host cpu workload. It only accesses
> the
> > drive for the plugins as you mentioned, and the fxt program itself .
> Also,
> > you can stream vistis from the server, but I havent tried this.
> > E
> >
> > "Kim" <hiddensounds@hotmail.com> wrote in message
news:4439aed3$1@linux...
> > >
> > >
> > > If FX teleport is accessing the partitions using Windows Networking,
> then
> > > I can't see why the formats would make any difference.
> > >
> > > But perhaps it doesn't.
> > >
> > > To be honest, if I understand what it's doing properly, I can't see
why
> it
> > > actually needs to access the drives at all. I would have thought FX
> > teleport
> > > would simply talk directly from one machine to the other, from the
> > teleport
> > > app on one machine to teleport on the other, app to app, rather than
> > accessing
> > > the drive. Accessing the drive would simply slow the process down, as
> > drives
> > > are slow of course. I mean why does teleport need to access the drive?
I
> > > mean other than to read the plugins off the local machine, but as far
as
> > > transferring audio data between machines surely it doesn't have to
read
> > the
> > > drive. The audio app would read the track off the drive and feed it to
> > teleport,
> > > which would feed it down the network cable to teleport at the other
end,
> > > apply the effect, and send it back to teleport, which would feed it
back
> > > to the app. Can't see why it needs to access the drive... other than
> to
> > > access your plugins, but that would be on the local machine surely?
> > >
> > > Cheers,
> > > Kim.
> > >
> > > "DJ" <animix_spam-this-ahole_@animas.net> wrote:
> > > >My system drive (running Win XP) is formatted FAT 32 (I have my
reasons
> > > for
> > > >this). FXT will not scan and recognize the plugins on the host
machine
> > and
> > > >does not recognize my server machine either. The system drive on the
> > server
> > > >is formatted NTFS. All folders are being recognized through My
Network
> > > >Places and the files are accessable between both machines over the
> > network,
> > > >but for the life of me, I casn't get FXT to work ads advertized.
> > > >
> > > >I have tried everything. It just occurred to me that the drives on
the
> > host
> > > >and server were formatted differently.
> > > >
> > > >
> > >
> >
> >
>
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66418 is a reply to message #66416] |
Sun, 09 April 2006 19:00 |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
In any case I'd suggest that the problem may well simply be that it doesn't
like FAT32 full stop, in which case that's what you'd have to do.
You would expect that it would be well documented if that was the case though.
Very odd.
Cheers,
Kim.
"DJ" <animix_spam-this-ahole_@animas.net> wrote:
>I guess the last resort will be to reformat my server drive to FAT 32. I'm
>not asbout to go the other way and reformat my system drive NTFS on my host
>machine. Too much work to reinstall/reauthorize all my apps/plugins. If
FXT
>doesn't work with F 32, I'll just live without it.
>
>I'm to the point of being totally disgusted with this app anyway. If it
>can't locate the host plugins from the host drive, I'm really not too
>impressed.
>
>Deej
>
>
>
>"Edna" <edna@texomaonline.com> wrote in message news:4439b67d@linux...
>> I think that is the way it works Kim, it has the plugins stored on the
>> server(also on the host, in case you dont want to process one on the
>server)
>> and applies them there and shoots it back to the host, as I understand
it
>> anyway. This is why it unloads your host cpu workload. It only accesses
>the
>> drive for the plugins as you mentioned, and the fxt program itself .
>Also,
>> you can stream vistis from the server, but I havent tried this.
>> E
>>
>> "Kim" <hiddensounds@hotmail.com> wrote in message news:4439aed3$1@linux...
>> >
>> >
>> > If FX teleport is accessing the partitions using Windows Networking,
>then
>> > I can't see why the formats would make any difference.
>> >
>> > But perhaps it doesn't.
>> >
>> > To be honest, if I understand what it's doing properly, I can't see
why
>it
>> > actually needs to access the drives at all. I would have thought FX
>> teleport
>> > would simply talk directly from one machine to the other, from the
>> teleport
>> > app on one machine to teleport on the other, app to app, rather than
>> accessing
>> > the drive. Accessing the drive would simply slow the process down, as
>> drives
>> > are slow of course. I mean why does teleport need to access the drive?
I
>> > mean other than to read the plugins off the local machine, but as far
as
>> > transferring audio data between machines surely it doesn't have to read
>> the
>> > drive. The audio app would read the track off the drive and feed it
to
>> teleport,
>> > which would feed it down the network cable to teleport at the other
end,
>> > apply the effect, and send it back to teleport, which would feed it
back
>> > to the app. Can't see why it needs to access the drive... other than
>to
>> > access your plugins, but that would be on the local machine surely?
>> >
>> > Cheers,
>> > Kim.
>> >
>> > "DJ" <animix_spam-this-ahole_@animas.net> wrote:
>> > >My system drive (running Win XP) is formatted FAT 32 (I have my reasons
>> > for
>> > >this). FXT will not scan and recognize the plugins on the host machine
>> and
>> > >does not recognize my server machine either. The system drive on the
>> server
>> > >is formatted NTFS. All folders are being recognized through My Network
>> > >Places and the files are accessable between both machines over the
>> network,
>> > >but for the life of me, I casn't get FXT to work ads advertized.
>> > >
>> > >I have tried everything. It just occurred to me that the drives on
the
>> host
>> > >and server were formatted differently.
>> > >
>> > >
>> >
>>
>>
>
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66427 is a reply to message #66418] |
Sun, 09 April 2006 22:24 |
Deej [1]
Messages: 2149
Registered: January 2006
|
Senior Member |
|
|
FXT is supposed to work with Win 98 and ME. those won't run with NTFS so I'm
sure FAT 32 is supported. Now if there is some issue with the FAT 32 (host)
app not being able to access the NTFS (server) app due to different drive
formats, this could explain it, but WTF can I share files between these two
drives with no problems over the network, just not using FX Teleport? My FAT
32 system drive on my Cubase machine can access files on my NTFS (server)
machine with no problem at all and my Paris machine (which is on the same
network) running FAT 32 can also access the NTFS formatted system drive of
the server machine and vice versa.
Very strange. I may just ditch these RME cards in favor of Lynx cards. I've
read too much that leads me to believe that the crackling I'm getting is an
RME driver issue. I thought the crackling had to do with overloading the PCI
bus with too many UAD cards, but now I'm not so sure. I'm not at all crazy
about other things RME either. The Totalmix software is undoubtedly the
crappiest software interface I've ever used.
Guess I'm just burned out on this and getting grouchy.
G'nite guys.............and thanks for all your help and suggestions
Deej
"Kim" <hiddensounds@hotmail.com> wrote in message news:4439bc2f$1@linux...
>
>
> In any case I'd suggest that the problem may well simply be that it
doesn't
> like FAT32 full stop, in which case that's what you'd have to do.
>
> You would expect that it would be well documented if that was the case
though.
> Very odd.
>
> Cheers,
> Kim.
>
> "DJ" <animix_spam-this-ahole_@animas.net> wrote:
> >I guess the last resort will be to reformat my server drive to FAT 32.
I'm
> >not asbout to go the other way and reformat my system drive NTFS on my
host
> >machine. Too much work to reinstall/reauthorize all my apps/plugins. If
> FXT
> >doesn't work with F 32, I'll just live without it.
> >
> >I'm to the point of being totally disgusted with this app anyway. If it
> >can't locate the host plugins from the host drive, I'm really not too
> >impressed.
> >
> >Deej
> >
> >
> >
> >"Edna" <edna@texomaonline.com> wrote in message news:4439b67d@linux...
> >> I think that is the way it works Kim, it has the plugins stored on the
> >> server(also on the host, in case you dont want to process one on the
> >server)
> >> and applies them there and shoots it back to the host, as I understand
> it
> >> anyway. This is why it unloads your host cpu workload. It only
accesses
> >the
> >> drive for the plugins as you mentioned, and the fxt program itself .
> >Also,
> >> you can stream vistis from the server, but I havent tried this.
> >> E
> >>
> >> "Kim" <hiddensounds@hotmail.com> wrote in message
news:4439aed3$1@linux...
> >> >
> >> >
> >> > If FX teleport is accessing the partitions using Windows Networking,
> >then
> >> > I can't see why the formats would make any difference.
> >> >
> >> > But perhaps it doesn't.
> >> >
> >> > To be honest, if I understand what it's doing properly, I can't see
> why
> >it
> >> > actually needs to access the drives at all. I would have thought FX
> >> teleport
> >> > would simply talk directly from one machine to the other, from the
> >> teleport
> >> > app on one machine to teleport on the other, app to app, rather than
> >> accessing
> >> > the drive. Accessing the drive would simply slow the process down, as
> >> drives
> >> > are slow of course. I mean why does teleport need to access the
drive?
> I
> >> > mean other than to read the plugins off the local machine, but as far
> as
> >> > transferring audio data between machines surely it doesn't have to
read
> >> the
> >> > drive. The audio app would read the track off the drive and feed it
> to
> >> teleport,
> >> > which would feed it down the network cable to teleport at the other
> end,
> >> > apply the effect, and send it back to teleport, which would feed it
> back
> >> > to the app. Can't see why it needs to access the drive... other
than
> >to
> >> > access your plugins, but that would be on the local machine surely?
> >> >
> >> > Cheers,
> >> > Kim.
> >> >
> >> > "DJ" <animix_spam-this-ahole_@animas.net> wrote:
> >> > >My system drive (running Win XP) is formatted FAT 32 (I have my
reasons
> >> > for
> >> > >this). FXT will not scan and recognize the plugins on the host
machine
> >> and
> >> > >does not recognize my server machine either. The system drive on the
> >> server
> >> > >is formatted NTFS. All folders are being recognized through My
Network
> >> > >Places and the files are accessable between both machines over the
> >> network,
> >> > >but for the life of me, I casn't get FXT to work ads advertized.
> >> > >
> >> > >I have tried everything. It just occurred to me that the drives on
> the
> >> host
> >> > >and server were formatted differently.
> >> > >
> >> > >
> >> >
> >>
> >>
> >
> >
>
|
|
|
|
| Re: I think maybe this is why FXT isn't working-feedback please [message #66447 is a reply to message #66427] |
Mon, 10 April 2006 07:37 |
Dedric Terry
Messages: 788
Registered: June 2007
|
Senior Member |
|
|
FWIW - the RME issue may be SX/Nuendo related, not necessarily just RME (may
not alter the idea of going to Lynx, but fwiw). I've been checking into why
RME cards aren't working well at low latency with Nuendo (since 3.0 this has
been the case), and found that they work amazingly well with Samplitude at
low latency, soooo....that leads me to believe it isn't simply a driver
issue. I don't have Lynx cards to confirm if they work even better with
Samplitude though. Nothing wrong with going to Lynx though - great cards,
and they do seem to perform well with Nuendo, at the moment. Just something
to look into before changing out your system.
Sorry you are having problems with FXT. I does work perfectly with multiple
NTFS systems under Nuendo, so at least there is hope, unless it's a Paris
issue.
FXT may be handling file sharing differently than Windows - it really isn't
just file sharing, it's running a dll in a local shell with a tunnel to the
host. You could get really anal about this, put a Sniffer on your LAN (rent
one from a Network systems developer) and see if FXT is sending and
receiving anything when instantiated. That would help trace down whether
it's a LAN communication issue, or FXT just isn't loading completely on one
end.
Regards,
Dedric
On 4/9/06 11:24 PM, in article 4439effd$1@linux, "DJ"
<animix_spam-this-ahole_@animas.net> wrote:
> FXT is supposed to work with Win 98 and ME. those won't run with NTFS so I'm
> sure FAT 32 is supported. Now if there is some issue with the FAT 32 (host)
> app not being able to access the NTFS (server) app due to different drive
> formats, this could explain it, but WTF can I share files between these two
> drives with no problems over the network, just not using FX Teleport? My FAT
> 32 system drive on my Cubase machine can access files on my NTFS (server)
> machine with no problem at all and my Paris machine (which is on the same
> network) running FAT 32 can also access the NTFS formatted system drive of
> the server machine and vice versa.
>
> Very strange. I may just ditch these RME cards in favor of Lynx cards. I've
> read too much that leads me to believe that the crackling I'm getting is an
> RME driver issue. I thought the crackling had to do with overloading the PCI
> bus with too many UAD cards, but now I'm not so sure. I'm not at all crazy
> about other things RME either. The Totalmix software is undoubtedly the
> crappiest software interface I've ever used.
>
> Guess I'm just burned out on this and getting grouchy.
>
> G'nite guys.............and thanks for all your help and suggestions
>
> Deej
>
>
> "Kim" <hiddensounds@hotmail.com> wrote in message news:4439bc2f$1@linux...
>>
>>
>> In any case I'd suggest that the problem may well simply be that it
> doesn't
>> like FAT32 full stop, in which case that's what you'd have to do.
>>
>> You would expect that it would be well documented if that was the case
> though.
>> Very odd.
>>
>> Cheers,
>> Kim.
>>
>> "DJ" <animix_spam-this-ahole_@animas.net> wrote:
>>> I guess the last resort will be to reformat my server drive to FAT 32.
> I'm
>>> not asbout to go the other way and reformat my system drive NTFS on my
> host
>>> machine. Too much work to reinstall/reauthorize all my apps/plugins. If
>> FXT
>>> doesn't work with F 32, I'll just live without it.
>>>
>>> I'm to the point of being totally disgusted with this app anyway. If it
>>> can't locate the host plugins from the host drive, I'm really not too
>>> impressed.
>>>
>>> Deej
>>>
>>>
>>>
>>> "Edna" <edna@texomaonline.com> wrote in message news:4439b67d@linux...
>>>> I think that is the way it works Kim, it has the plugins stored on the
>>>> server(also on the host, in case you dont want to process one on the
>>> server)
>>>> and applies them there and shoots it back to the host, as I understand
>> it
>>>> anyway. This is why it unloads your host cpu workload. It only
> accesses
>>> the
>>>> drive for the plugins as you mentioned, and the fxt program itself .
>>> Also,
>>>> you can stream vistis from the server, but I havent tried this.
>>>> E
>>>>
>>>> "Kim" <hiddensounds@hotmail.com> wrote in message
> news:4439aed3$1@linux...
>>>>>
>>>>>
>>>>> If FX teleport is accessing the partitions using Windows Networking,
>>> then
>>>>> I can't see why the formats would make any difference.
>>>>>
>>>>> But perhaps it doesn't.
>>>>>
>>>>> To be honest, if I understand what it's doing properly, I can't see
>> why
>>> it
>>>>> actually needs to access the drives at all. I would have thought FX
>>>> teleport
>>>>> would simply talk directly from one machine to the other, from the
>>>> teleport
>>>>> app on one machine to teleport on the other, app to app, rather than
>>>> accessing
>>>>> the drive. Accessing the drive would simply slow the process down, as
>>>> drives
>>>>> are slow of course. I mean why does teleport need to access the
> drive?
>> I
>>>>> mean other than to read the plugins off the local machine, but as far
>> as
>>>>> transferring audio data between machines surely it doesn't have to
> read
>>>> the
>>>>> drive. The audio app would read the track off the drive and feed it
>> to
>>>> teleport,
>>>>> which would feed it down the network cable to teleport at the other
>> end,
>>>>> apply the effect, and send it back to teleport, which would feed it
>> back
>>>>> to the app. Can't see why it needs to access the drive... other
> than
>>> to
>>>>> access your plugins, but that would be on the local machine surely?
>>>>>
>>>>> Cheers,
>>>>> Kim.
>>>>>
>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote:
>>>>>> My system drive (running Win XP) is formatted FAT 32 (I have my
> reasons
>>>>> for
>>>>>> this). FXT will not scan and recognize the plugins on the host
> machine
>>>> and
>>>>>> does not recognize my server machine either. The system drive on the
>>>> server
>>>>>> is formatted NTFS. All folders are being recognized through My
> Network
>>>>>> Places and the files are accessable between both machines over the
>>>> network,
>>>>>> but for the life of me, I casn't get FXT to work ads advertized.
>>>>>>
>>>>>> I have tried everything. It just occurred to me that the drives on
>> the
>>>> host
>>>>>> and server were formatted differently.
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
|
|
|
|
Goto Forum:
Current Time: Sat Nov 30 11:12:32 PST 2024
Total time taken to generate the page: 0.01692 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
