There's a few on the Italian second-hand music site at the moment (where I got my Scope cards):
http://www.mercatinomusicale.com/ann/se ... ightbridge
Audio Over Ethernet
Re: Audio Over Ethernet
Not because it is easy, but because it is hard...
Re: Audio Over Ethernet
I am thinking of another way of solving this: What if I buy an used Pulsar II, already with the 5.1 (I found one, for less than the M-Audio Profire Lightbridge 
) and install it in the pc of the room?
This way I would add 16 channels I/O for ADAT, and still have all the good things Sonic:Core gives us.
) and install it in the pc of the room? This way I would add 16 channels I/O for ADAT, and still have all the good things Sonic:Core gives us.
Re: Audio Over Ethernet
That'd work! 
Do report back to indicate success or otherwise...
Does your motherboard in the attic support WOL (Wake On Lan)? Not sure if scope will like that way of restarting...
Do report back to indicate success or otherwise...
Does your motherboard in the attic support WOL (Wake On Lan)? Not sure if scope will like that way of restarting...
Not because it is easy, but because it is hard...
Re: Audio Over Ethernet
Yes, it does.Eanna wrote:That'd work!
Do report back to indicate success or otherwise...
Does your motherboard in the attic support WOL (Wake On Lan)? Not sure if scope will like that way of restarting...
I'm considering to pull the energy wire from the room downstairs. That way I solve the on/off issue and isolate the energy circuit for the pc/rack synths from the one in the atic.
Re: Audio Over Ethernet
Not totally sure I understand what you mean, but you should try to share a common Ground, otherwise your unbalanced connections run the risk of ground loops without an isolating transformer... Not sure if CAT5 for your Midi transport is isolated? But optical cables are not conductors... so, not sure what you're gaining? Maybe I'm misunderstanding your intentions with power there...
Not because it is easy, but because it is hard...
Re: Audio Over Ethernet
Summing up: The ALL(Room+Atic) Sound+Synths+Keyboards+PCs will use the very same energy wire circuit. That is, the mains outlet for the synth+PC in the atic will be coming from the room, which is the very same that is feeding them now.Eanna wrote:Not totally sure I understand what you mean, but you should try to share a common Ground, otherwise your unbalanced connections run the risk of ground loops without an isolating transformer... Not sure if CAT5 for your Midi transport is isolated? But optical cables are not conductors... so, not sure what you're gaining? Maybe I'm misunderstanding your intentions with power there...
The other things in the atic (Freezer, threadmill, lamp, Soldering Iron) will NOT "know" that the music stuff is there, because it isn't connected to the same energy circuit.
I think I explained it correctely.
Re: Audio Over Ethernet
I have it all working like a charm.
I made a Y in the Windows XP's Scope Computer's power switch's cable. That is, that computer (the one in the atic) still has it's original power switch, but also has another one that goes to the room downstairs.
I can now turn on the pc from the studio. (The Off part is done through Remote Desktop)
I just have to enter the XP PC through remote desktop from the windows 8 PC in the studio.
Midi and Sound are working perfectly.
Life is cool!
I made a Y in the Windows XP's Scope Computer's power switch's cable. That is, that computer (the one in the atic) still has it's original power switch, but also has another one that goes to the room downstairs.
I can now turn on the pc from the studio. (The Off part is done through Remote Desktop)
I just have to enter the XP PC through remote desktop from the windows 8 PC in the studio.
Midi and Sound are working perfectly.
Life is cool!
Re: Audio Over Ethernet
Good stuff!
What wire transport are you using for Midi? And for Audio?
What wire transport are you using for Midi? And for Audio?
Not because it is easy, but because it is hard...
Re: Audio Over Ethernet
Eanna wrote:Good stuff!
What wire transport are you using for Midi? And for Audio?
Midi = Copperlan (As such: Ethernet)
Audio = Optical Cable
Re: Audio Over Ethernet
I forgot to mention something that I think deserves to be remarked:
I was having a problem with the copperlan configurations and the Alyseum AL88. It simply was vanishing from the Copperlan Manager and didn't let me configure it in full. Sometimes it let me work a little longer but some of the connections kept unrecognized.
After some days trying to fix it I talked to Copperlan through their forum and at the same time sent an email to Alyseum.
They both answered with some ideas to try to find the problem. Alyseum sent me a new AL88, free of charge (even the freight costs) before I sent them the faulty one, on their expense too.
It turned out to be a problem with the firmware and also (yes, two problems) I wasn't giving the proper attention to the channels part in the manager. That last one was making the AL88 go mad, because there were a nice 900+ connections for it to manage and the memory was blowing, lol.
They found out this last one as I told them what I was doing in detail (I was going to go there later, but didn't gave a damn to it at that phase) and immediately solved it.
This is only to emphasize the great interest Alyseum and Copperlan give to their costumers' claims and that these guys do really deserve to see their work having more visibility than it is having for now.
Copperlan is a fantastic idea becoming true. For me, it was a blessing. Without Copperlan I couldn't have made this project... at least with this budget and 3 wires.
Thank You Copperlan and Alyseum.
I was having a problem with the copperlan configurations and the Alyseum AL88. It simply was vanishing from the Copperlan Manager and didn't let me configure it in full. Sometimes it let me work a little longer but some of the connections kept unrecognized.
After some days trying to fix it I talked to Copperlan through their forum and at the same time sent an email to Alyseum.
They both answered with some ideas to try to find the problem. Alyseum sent me a new AL88, free of charge (even the freight costs) before I sent them the faulty one, on their expense too.
It turned out to be a problem with the firmware and also (yes, two problems) I wasn't giving the proper attention to the channels part in the manager. That last one was making the AL88 go mad, because there were a nice 900+ connections for it to manage and the memory was blowing, lol.
They found out this last one as I told them what I was doing in detail (I was going to go there later, but didn't gave a damn to it at that phase) and immediately solved it.
This is only to emphasize the great interest Alyseum and Copperlan give to their costumers' claims and that these guys do really deserve to see their work having more visibility than it is having for now.
Copperlan is a fantastic idea becoming true. For me, it was a blessing. Without Copperlan I couldn't have made this project... at least with this budget and 3 wires.
Thank You Copperlan and Alyseum.
Re: Audio Over Ethernet
Hey Ripper any chance some pics of your setup ? This sound like a great article for ScopeRise.
Re: Audio Over Ethernet
Hi Dante.dante wrote:Hey Ripper any chance some pics of your setup ? This sound like a great article for ScopeRise.
Meanwhile I just found a "small" bug in Copperlan, and they will fix it till the middle of this month.
It is enumerating 3 devices as being the same, which makes them not usable till a reconfiguration, but is ok after that reconfiguration. The problem appears when you re-open Copperlan. As I said, not a big deal at this moment because I am currently using only one midi channel per device and only one device each time, the configuration is simple to be done, just annoying to have to reconfigure the stuff. This only occurs in physical ports, not VMidi ports.
I can make come pics without any problem. When I have a bit I will do some and send them to you.
Re: Audio Over Ethernet
Excellant thanks Ripper. This would be a welcome addition to ScopeRise November.
Re: Audio Over Ethernet
I think I am running into this bug.
I am using Copperlan to run a vMidi from my main XITE-1 based 64bit machine to a 32Bit machine, so I can use STS on a Luna card.
I am using one (or two) vMidi links (out of a sequencer to Luna - not XITE Scope Midi outs).
The issue is when I open Cubase or Samplitude on the main machine, EXITE Scope midi is no longer available (or at least not initially - sometimes I can recover, but not sure on the best workaround at this stage). I get Scope communication error messages and often Scope wants to shut down.
I am not connecting the Scope Midi instances to anything in Copperlan.
I also note that Scope Midi instances are usually switched 'off' in Copperlan.
Anyone have these issues?
Have you found any workarounds?
I like Copperlan and want to keep using it.
Regards
Maus
I am using Copperlan to run a vMidi from my main XITE-1 based 64bit machine to a 32Bit machine, so I can use STS on a Luna card.
I am using one (or two) vMidi links (out of a sequencer to Luna - not XITE Scope Midi outs).
The issue is when I open Cubase or Samplitude on the main machine, EXITE Scope midi is no longer available (or at least not initially - sometimes I can recover, but not sure on the best workaround at this stage). I get Scope communication error messages and often Scope wants to shut down.
I am not connecting the Scope Midi instances to anything in Copperlan.
I also note that Scope Midi instances are usually switched 'off' in Copperlan.
Anyone have these issues?
Have you found any workarounds?
I like Copperlan and want to keep using it.
Regards
Maus
Re: Audio Over Ethernet
I do not have these problems. When you have activated a scope midi source in the edit panel of the copperlan interface then copperlan keeps that connection open. The copperlan program doesn't have to be running. To make available the midi sources to other programs you have to deactivate them through the edit menu in the copperlan program.
I have encountered the situation that reaper didn't see my scope sequencer midi sources but when i deactivated these in the copperlan everything was ok. They are not multiclient...
I use it with a virtualbox midi sequencer and everything works ok. (3 vm's to 3 scope midi sequencer outputs)
I have encountered the situation that reaper didn't see my scope sequencer midi sources but when i deactivated these in the copperlan everything was ok. They are not multiclient...
I use it with a virtualbox midi sequencer and everything works ok. (3 vm's to 3 scope midi sequencer outputs)
Re: Audio Over Ethernet
Yeah,
Things have got even more F**ked up, so I have uninstalled Copperlan and there is still communication issues with my XITE when I import a Sequencer Midi Dest module and open a sequencer or Midi-Ox and try to connect that Dest Module.
I think it is likely two devices are trying to connect to the scope midi outs and causing the problem.
Not sure at this stage.
I am going to go back to a very simple setup, get that working and expand from there
Things have got even more F**ked up, so I have uninstalled Copperlan and there is still communication issues with my XITE when I import a Sequencer Midi Dest module and open a sequencer or Midi-Ox and try to connect that Dest Module.
I think it is likely two devices are trying to connect to the scope midi outs and causing the problem.
Not sure at this stage.
I am going to go back to a very simple setup, get that working and expand from there
Re: Audio Over Ethernet
when copperlan is set to auto startup, then it starts before scope, so it doesn't find the scope midi ports and you have to reload the virtual routing configuration each time.
A solution is to disable cpvnm from windows services, and run it after scope has been started.
It can be started also from its location such as "C:\Program Files\CopperLan\CPVNM\CPVNM.exe" or by entering command line and typing "net start cpvnm" .
A solution is to disable cpvnm from windows services, and run it after scope has been started.
It can be started also from its location such as "C:\Program Files\CopperLan\CPVNM\CPVNM.exe" or by entering command line and typing "net start cpvnm" .
Re: Audio Over Ethernet
Exactly what I do.djmicron wrote:when copperlan is set to auto startup, then it starts before scope, so it doesn't find the scope midi ports and you have to reload the virtual routing configuration each time.
A solution is to disable cpvnm from windows services, and run it after scope has been started.
It can be started also from its location such as "C:\Program Files\CopperLan\CPVNM\CPVNM.exe" or by entering command line and typing "net start cpvnm" .
Re: Audio Over Ethernet
It's always a good thing to share information for the community, this is why i wrote it down, not for you, but for the others.Ripper wrote:Exactly what I do.djmicron wrote:when copperlan is set to auto startup, then it starts before scope, so it doesn't find the scope midi ports and you have to reload the virtual routing configuration each time.
A solution is to disable cpvnm from windows services, and run it after scope has been started.
It can be started also from its location such as "C:\Program Files\CopperLan\CPVNM\CPVNM.exe" or by entering command line and typing "net start cpvnm" .