Forum Replies Created
-
AuthorPosts
-
2019/05/19 at 1:00 am #83908
I have some of them saved, pm me your e-mail address and I can send you a copy of them. I don’t see them on the website either.
2019/05/19 at 12:46 am #83907You use the “archive show” button.
If you are not saving(overwriting) an existing show, it will be highlighted in the file name box, you will simply just have to replace the highlighted name with the new name for the show.2019/05/13 at 11:00 am #83808So Nicola, I’m guessing that setting the 96k card to 48k also then reduces the channel count back down to 64 in/out?
Considering the cost difference between the new 96k and the older 48k, what is the real advantage of the new card if the rest of the Dante system is still running at 48k.
Any idea how long the 48k will continue to be produced?Sorry to hi-jack the thread. Just some questions as we are preparing for a new dLive system in the near future.
Scott.
2019/05/12 at 7:05 pm #83793Correct me if I’m wrong, but I didn’t think that there was a 96k Dante card yet for the dLive system, only the current 48k card and mounting adapter.
I’m sure I have read that they(Audinate) is working on building a card for 96k, but it wasn’t ready yet.2019/04/11 at 10:20 pm #83316Like Ray says, but you have to be on the ‘outputs’ config page 1st.
Unless you are using Editor on-line, then you want so select the I/O config tab from the left edge options.2019/04/05 at 10:59 am #83187I’d be interested to see what someone says on this.
As you make the show edits, I presume you are saving them, yes?
When the system boots, is it booting and loading your changes?
I’m thinking that in order for the name of this show to show up under “last show” you have to use the recall/load function to load the show from the saved file at least once to populate the data register with information(boot up alone won’t do it). I would imagine that the scene info would be similar(you need to ‘recall’ one to populate the data register). System start up would load the scene that was last active(not necessary the last recalled) unless there is an option to select a specific scene on boot/load.I know that with the iLive, if I wanted a specific show file to be recalled on start up I had to be sure that the file was the last recalled/loaded show file just before the system was shut down. Otherwise, when it would boot, it would boot to the last state it was when it was shut down(including all changes since the listed show file was saved), not necessarily the show file(as saved/stored) listed on the status screen. I don’t know with the dLive if you can boot to a specific scene like the older one would allow you to do.
I would load our base show, make edits and save under a new name. Shut down system, on next boot it would load the status as shutdown, showing “base show” in the last show recalled info, yet the edits I made were loaded from the “shut down state” config that was stored on shutdown(hidden info).To help correct this confusion, I load the base show, store the show with the new name(I use dates), then recall that newly names show file. Now the ‘last show’ data is populated with my new show file info. I can then do my edits and modifications, save the edits before shutdown. On the next boot up, it will load all the edits and state of the system as it was when shut down.(provided no one else boots the system and makes changes, but that’s another issue… lol )
2019/03/26 at 10:47 am #82983Then I’d be getting an RMA and returning it. Nothing you can do with it.
2019/03/26 at 2:46 am #82975Have you tried a different usb drive… I’ve sometimes had to remove/insert my thumb drive 3-4 times before the ME recognized it. I have read of others also having usb drive issues.
I have not tried to install this recent update.2019/03/26 at 2:38 am #82973How old is the mixer, there seems to be a rash of them having this power up issue lately. I seem to recall the discussion focusing on an internal board issue/problem.
2019/03/23 at 6:52 pm #82927It’s all a matter of patching in the console software controller. You basically have to “tunnel” your signals to the slave rack thru the ACE line(64 channels available)
It can seem a bit unconventional, but once you understand how the data(audio) flows between the racks, it’s not that hard.
I complicated our system even more with a Dante card in our slave rack portB slot for multi-track recording and playback…. that can become a patching headache without a good set of notes, and a very good understanding of how the patching is done.I sent you a couple of screen shots to your e-mail. One is the patch setting for the master rack output on the ACE, the 2nd is the patching setup for the XLR jack of the slave rack.
This patching can be done either with the surface, or a pc running Editor software.
2019/03/23 at 5:31 pm #82924You are on the right track. Keep following the instructions I posted earlier, especially the mapping to the ACE line. That is the key. Master rack->out on ACE-> into Slave rack from ACE
I’m going to be out at our system in a hour or so(we have a service tonight).
I’ll take some screen shots and e-mail them to you.2019/03/23 at 2:43 pm #82922If the laptop is still available, you can also setup the outputs routing thru the I/O screen of iLive Editor, if that would be more comfortable at this point.
2019/03/22 at 10:07 pm #82908Barrett, I tried to attach a document that explains Dual Rack setup. It’s too large.
If you PM me an e-mail address I can send it to you.2019/03/22 at 9:57 pm #82907Have you read this document:
2019/03/22 at 9:51 pm #82906For a Dual Rack setup, you have to “patch” the in’s and out’s between mix-racks using the ACE patching.
From the slave rack to the master rack, 32 of the 64 ACE channels are user programable. (The 1st 32 ACE channels are reserved for the 32 inputs of the slave rack).
From the master rack to the slave rack, you have all 64 channels available to program, and you have to program these channels to get your audio from the master(and surface) to the slave.The patching is done from the ‘outputs’ button, located under the surface touch screen.
Located at the top of the outputs screen you have to select either the ‘master’ rack or the ‘slave rack’.
Start with the ‘master’ rack selection, then locate the tab labeled as ‘port B ACE’, select an ACE channel, then on the right side of the screen select the source signal to send out on this ACE channel(your “mains” source).
Next step, select the ‘slave’ rack at the top of the outputs page.
Select your physical output port of the slave rack, on the right side select the source for this port, in this case select “port B ACE” then the ACE channel that you assigned in the previous steps.When I expanded our system from a single rack to a dual rack, it took me a bit to grasp the “ACE” routing aspect as well.
-
AuthorPosts
