[pete.jParticipant]

+1

[pete.jParticipant]

do you have IP6 activated and set to auto configure? As far as I remember even SoundGrid sends data on layer 2 it uses IP6 to configure itself.

Also, is the Waves card set to SoE Master. Don’t mess ClockMaster with SoundGrid Networkmaster. Therefore the dLive is you WordClock Master, but the WavesCard it self is the SoE Master for the SoundGrid side …

[pete.jParticipant]

Hi Steps,

as I said – Driver isn’t the same as network!

How many connection did you make in the Multirack Connections TAB (opens when you hit F3). This is the only number of interest if it comes to Network-Buffer, because there you set network traffic, regardless if how many channels you record and/or use for inserting PlugIns, thats just a matter of processing buffer (in MR) und Driver Buffer (in DAW).

My setup is.

dLive DM64 with Waves V3 card, Waves Server One, i7 19″ PC (for MR and TracksLive) with internal RealTech GB Ethernet.
Server and MR PC are connected directly to the Waves V3 card, 3rd port is linked to the dLive network port (100MBit Ethernet-Tunnel) for MIDI-over-TCP for scene recall in MultiRack via dLive Scenes.
I have 64 channels configured for MultiRack SG and 64 for TracksLive, all running at 96kHz.

I found a “bug” in Windows: when I start TracksLive (MR needs to be started first, as it does all connection for the SG Driver), Network-Traffic exceeds 100% in peaks. I then raise the network buffer in Inventory tab (F2) and lower it again, then the traffic falls down to about 55% avg and 75% peak.
I don’t have this behavior under MacOS X with my MacBook Pro and MacMini.

But after this little workaround even under Win 10 it works fine with 0.8ms network buffer and 512 samples driver buffer for TracksLive.

Even it doesn’t change anything for the network itself, I have like 32-36 inserts running and record 48 channels, complete show with 2h runtime.

So I cannot say, the Waves V3 doesn’t work. Also with my MGB (which works also with SoundGrid net) I had similar configurations with pure MADI-Console, as it has 2x 64 channels, but then normally with 48kHz.

There are few thing you have to be totally piggy with:

– firmware of Waves card and MR SG version should match. You see it in the overview, when the fw button isn’t grayed out, at least you’re Waves V3 has an older one (the other way round is hard to see, so always keep up to date with waves).
– firmware of your SG Server should match (same as above)
– only use certified switches (normally all AVB certified switches also work with SG, but no guarantee!).
– only use CAT5e or CAT6 cables, al lot had problems with CAT7 cables (also with AES50, DANTE, etc.).
– check firewall on MR remote computer – normally it should not matter, as firewalls on OS are configured mostly on Layer 3, SG is Layer 2, but you never know.
– ask Waves support – in my experience most of the time they are good, they also do remote sessions to find specific problems.

cheers Peter

[pete.jParticipant]

Hi Steph,

you have to know the concept of network based audio. So 128 I/O @96kHz means network traffic is 256 Channels @96kHz !!!
Therefore only you have to be shure, that you’re Ethernet-Interface can handle that.
Also, the Driver-Buffer isn’t the same as the network buffer! If you raise driver-buffer, network buffer still stays on 0.8ms, which with that channel count can be problematic.
Therefore in inventory tab of MultiRack SG theres also network buffer. Try to raise it!

I got the same running and absolute no problems recording 2h show with MultiRack and TracksLive on the same machine. So I doubt it’s a general problem, because my system works fine!

cheers peter

[pete.jParticipant]

Hi 8days,

1.52 fixed the problem with Waves Card. And with 1.5x you can use the new DAW Control Driver in “Thru” mode to send MIDI via TCP/IP to MultiRack for Snapshot-Control from dLives Snapshots.

Only you have to bridge the dLive Network-Port with one Port of the Waves-Card, to send MIDI from dLive to MR over the SoundGrid connection.

Cheers

[pete.jParticipant]

…just if someone is/was Loopings for As I did:

With 1.5 (and later) it’s NOW possible under Windows to do Midi PGM (f.e. To use with MultiRack).
With the Windoes DAW Controller Driver there’s a “Thru” mode in Windows (like HUI, Mackie Control). With this, MIDI is passed thru (there PGM Change is sent with Scene Recall).

It’s not easy to find, so I thought I’d share as it took me quite a bit to find it!

Cheers Peter

[pete.jParticipant]

… I think I’m little to late, but anyways:

– yes you can use MGB as a “format converter” as it is noting als – MADI-to-SoundGrid the other way round. You just need to to a Device-to-Device-Patch (MGB-to-Waves V3 and back) under SoundGrid Studio software
– you don’t need a Switch, as the Waves V2 and V3 have a built in 3 Port switch for exactly this. On port for MGB, one for your computer and (if you use) one für a SoundGrid Server.

Cheers Peter

[pete.jParticipant]

Hi Jon,

I didn’t check this feature in particular, but as far as my understanding:

It doesn’t matter where you connect the IP6/IP8 physically, but logically. If you have under “Mixrack”, than it behaves slightly different, as if you manage it under “Surface” menu. There it should behave like a surface extension, therefore follow the PAFL (also the selected busses if you have more PAFL configured as I do).

So, is you IP8 connected in dLive>Surface>IP Controller>Devices or did you just connect the cable to the surface?

Regards Peter

[pete.jParticipant]

I’d do it like this:

Drums to Subgroup, band to second Subgroup, both to Main L/R do your mastering there.

Lavs to third subgroup, Main + Lavs-Group go into Matrix.

Fourths Subgroup for rest, goes also to Matrix.

If you don’t like extra D/A-A/D but want subgroups use AES/EBU (as there are two on Surface).

Cheers

[pete.jParticipant]

@gustavh: a quick read on the internet tells you, that USB-Chipset doesn’t support AVB at all. So ANY Ethernet connection that’s on the USB-side (as most USB-C devices are at the moment) won’t work as the QoS for clocking won’t work with AVB, DANTE, SoundGrid, AES67 and so on.

Cheers Peter

[pete.jParticipant]

@8days:

send me a pm and we can phone. I know your company well and touring with a dLive System with a almost identical setup.

All channels (lets say 1-64) you setup for virtual soundcheck a blocked exclusively at the moment when you activate Record or Virtual Soundcheck mode, so the patch has a higher priority.

Also you have to think of the SoundGrid network as network. Means a channel “subscribed” for MultiRack is used. So the trick is to use f.e. channels 1-64 for Multirack and Channels 65-128 for recording.
In MultiRack connections you have to “patch” than dLive 1-64 to MR 1-64 (and back) and dLive 65-128 to SoudGrid ASIO (which is the virtual Soundcard for TracksLive then) and back (if you want to do virtual soundcheck).
It has nothing to do with the firmware as it was the same on 1.4x.

But: I didn’t upgrade to 1.5 because there’s a bug. If you have set a scene-recall filter, as soon as you recall this scene, there will be no audio anymore on SoundGrid. As I’m on tour right now and don’t want to upgrade a running system I didn’t check 1.51 if it still has this bug. But Johannes didn’t say anything that they already fixed it, so I assume it’s not fixed yet.

cheers Peter

[pete.jParticipant]

@Art: Waves doesn’t “advice” to run it on different machines.

In the setup they connect the MR Computer by using the 100MBit-Tunnel from the iLive/dLive in they ACE/GigaACE connection. Therefore it is way too slow to have the recording channels going thru that connections, but it would safe you from an extra CAT5e/CAT6 cable from stage to FOH.

I have a setup running a Waves V3 card in the dLive Stagebox and setup 64 Channels MR and 64 recording (for virtual soundcheck) using TracksLive and have it all on one machine and it runs stable. All on 96kHz btw.!

If you look at the other setups (Yamaha, etc.) you see that they “recommend” MR and DAW on the same computer. It’s just irrelevant if:

– the machine is fast enough
– the connection is fully GBE

cheers Peter

[pete.jParticipant]

…. just do it, no problem. The only thing is you can’t import a show stored with 1.5. But go up and down as you like, it’s done easily in several minutes and works fine.

Cheers Peter

[pete.jParticipant]

Hi Adam,

which LAN-Card do you use? There’ve been reports that new USB-C/LAN-Adapter have trouble (also with DANTE etc.). What#s confirmed to work is:

MacBook Pro -> USB-C-Thunderbolt-Adapter -> Thunderbolt-Gigabit-Adapter

Sounds odd to use 2 adapters in a row, but not all USB-C adapters are Thunderbolt but USB. And USB-Ethernetapdaters are mostly not AVB-Compatible, therefore also don’t work with DATNE oder Waves SoundGrid.

@nicola: as he “change to a new MacBook Pro” for me it sound’s like he had everything working on his old one, therefor I assume in general he knows how to setup sync etc. But yes, better to look twice at it.

Cheers Peter

[pete.jParticipant]

Yes, but it’s not a special dLive issue in my understanding.

At least under OSX they use rtp MIDI. And with every Start of OSX you have to ope the networkconection, regardless if you’re connections several Macs or a dLive and a Mac.

One “Master” has to open the session, and than all other can participate. That’s beyond dLive functionality, so I really doubt that it can be done so easy, as it’s not foreseen in OSX (and I guess also in Windows).

If the Mac doen’t alow “Auto reconnect” how should the dLive handle this?

I maybe wrong, but I did a lot Midi-remote control over LAN on tours (no dLive involved) and even I would love to see the Macs connect automatically there is no such feature so far.

Cheers

[Author]

Posts