Facebook-f Instagram Youtube

uTrack-X32 recording suddenly stops!

Home Page › Forums › Cymatic Audio Forum › uTrack-X32 › uTrack-X32 recording suddenly stops!

Viewing 24 posts - 1 through 24 (of 24 total)
  • Author
    Posts
  • 13th November 2017 at 22:08 #29106
    Francesco Lanza
    Participant

    Hi, I assembled a rack for live recording consisting in two X32 Core units, both loaded with a uTrack-32. I also bought two identical HDDs for this specific use (Toshiba HDTB310EK3AA, 1TB, 2.5″, USB 3.0).
    After getting everything set up, firmwares updated (both X32 Cores and uTrack cards), HDD formatted via uTrack (all as recommended), I start recording and after some random time (5-40 mins) one of the units suddenly stops! It happens indipendently if recording is started by card button or by uRemote app.
    Up to the point when recording stopped, files are well preserved. I tried changing each single variable, stress testing che system: I swapped the HDDs, still it happened on the same uTrack unit. I swapped the two uTrack cards between the X32 Cores, still the same uTrack card stopped.
    So it must be a problem in that specific uTrack x32 expansion card…
    Have you ever experienced anything like this during testing? It happens both if sound is flowing through the channels o if everything is silent and there are literally no vibrations (which I know could make the HDDs writing fail).
    If that uTrack is connected to a PC and a DAW, via USB driver, it records flawlessly (at least it seems so after a 2-hours test).
    Any suggestion on how to fix this?
    I bought these cards on Thomann some months ago, so they’re still under warranty. Should I ask for a “repair under warranty” service?
    Thank you very much for the assistance.

    14th November 2017 at 10:46 #29107
    Laszlo
    Keymaster

    Hi,

    Please send me the recording log from the last song folder on your HDD.
    Does your X32’s connected to the same network?
    Could you please try to do a test recording independently (internal clock) on both two device?
    The recording fails on the master or on the slave device?
    What is your clock source in your recording setup?

    14th November 2017 at 15:57 #29114
    Francesco Lanza
    Participant

    Hi, thank you for you response.
    Here’s the log of a recording which stopped in the described way:

    (02:43:11) -> Fw:3865 HwVs:2
    (02:43:11) -> Device type:Hard Drive, Vendor:TOSHIBA, ProductId:External USB 3.0, Rev:5438
    (02:43:11) -> Start prepare pre-recording
    (02:43:11) -> StreamingChannelMode set to Recording… Executing!
    (02:43:12) -> Date 14-11-17
    (02:43:12) -> Created Folder : /MultiTrack/_TempTake0005
    (02:43:12) -> SR:48000 depth:24: ActiveTracks:32
    (02:43:12) -> Renaming Directory from /MultiTrack/_TempTake0005 to /MultiTrack/Take0005
    (02:43:12) -> Entered Recording State
    (02:43:12) -> Next Gapless recording file created : MultiTrack/Take0005/Take0005(0002).wav
    (02:50:59) -> Next Gapless recording file created : MultiTrack/Take0005/Take0005(0003).wav
    (02:58:44) -> Next Gapless recording file created : MultiTrack/Take0005/Take0005(0004).wav
    (03:06:30) -> Next Gapless recording file created : MultiTrack/Take0005/Take0005(0005).wav
    (03:14:15) -> Next Gapless recording file created : MultiTrack/Take0005/Take0005(0006).wav

    both X32 and uTrack units are connected to the same 4 ports WiFi Router. The recording fails indipendently on master and/or slave device. During last night’s tests It happened a couple of times on the other card too, without an apparent systematic cause. I also tried to shut down the slave unit and use only the master one, which is also Master Clock, but same result.
    I tried a differend HDD, a Seagate 250GB, same result.

    Could it be a problem with USB powered HDDs, failing at receiving enough power at some point? I’ll try to run a test on a 3.5″ HDD with external power source as soon as I can…

    14th November 2017 at 18:09 #29117
    Laszlo
    Keymaster

    I don’t think is that HDD power issue. We had test the uTrack-X32 with the same Toshiba Canvio drives we were able to make more than 48hours recording with no problem.
    From your description I still thinking about the following causes:
    -Loose connection or cable, but as you said you tried with different drives I don’t think all of your cables are broken, please try to use the shortest as possible cables.
    -Clocking issue –> please do a test recording on a stand alone device where no router, no noting connected only the X32 card then start the recording.
    -To make sure that HDD powering issue, it would be nice to try with an SSD drive.

    At least we can step one step further is that networking , clocking or power/drive related issue.

    14th November 2017 at 23:23 #29122
    Francesco Lanza
    Participant

    Just came back home after leaving uTracks recording… both are still running after more than 6 hours!
    Only different thing now: Before starting this session I unplugged the LAN cables from uTrack cards, leaving only X32 cores connected to the router.
    Could that be the solution? Using different routers or not using remote control for the uTrack? I’ll stress them a little bit again to see if I can replicate this result.

    I tried before with an SSD flashdrive (not sure is the same as a SSD 2.5″ drive), same issue.
    USB cables to HDD are not longer than 30cm (1 foot), and i also tried swapping them, same problem.
    I did a test with only one X32 core powered on, but was still connected to the router just as the uTrack card, and had same problem.

    For now everthing leads to a LAN connection issue on the uTrack card. I’ll keep you posted after running further tests.

    Thank you!

    16th November 2017 at 18:34 #29127
    Francesco Lanza
    Participant

    Ok, after some more testing it’s definitely a network related problem. While uTrack is connected to the router (even if it’s the only device connected) the problem is present; if uTrack has no LAN cable connected, it records flawlessly (at least for 12hrs, as far as i tested).
    Now I’m trying using another router, and it’s been recording fine for almost 2hrs, let’s see how far it goes…

    The main router i’m using (which causes interruption) is a TP-Link TL-WR841N, the one I’m testing now is a TP-Link TL-WR802N.

    16th November 2017 at 18:41 #29128
    Laszlo
    Keymaster

    Thank you for your feedback.
    Does this place are crowded wifi environment? Do you need to connect the uRemote to have that problem or it is enough to connect to the router?
    Have you tried to connect only uTrack-X32 to the router (no other wired or wireless devices connected)

    17th November 2017 at 19:32 #29142
    Francesco Lanza
    Participant

    I’m in my flat, so there are some wi-fi routers nearby, but that’s definitely not crowded as in a public wi-fi place…
    It’s enough to connect to the router to get the problem, without using uRemote. Yes I tried connecting only the uTrack to the router and still same problem.

    20th November 2017 at 16:54 #29150
    Laszlo
    Keymaster

    That’s very weird.
    We did a test with different routers like Linksys, Netgear, D-Link with factory and open source firmware’s on the router but we never seen that problem.
    Are you saying you had that issue with both two router is that correct?
    Could you please try to use different cable, or to connect directly to any computer does the problem is present in this case as well?

    Sorry to ask that much question but you are the first user who has this issue and I’m not really sure what can cause any similar issue.

    21st November 2017 at 15:26 #29152
    Francesco Lanza
    Participant

    I only had problems with the TP-Link TL-WR841N, while the second router I tested (TP-Link TL-WR802N) ran smoothly without problems. I tried different cables but it doesn’t depend on that. I’ll try soon connecting to a computer or to different routers to see if it happens again.
    Thank you for the assistance, let’s hope to figure it out together 🙂

    21st November 2017 at 16:06 #29153
    Laszlo
    Keymaster

    Wow that’s an interesting feedback.
    I think we should get one of this TP-Link TL-WR841N for testing.

    Thank you for your feedback.

    27th November 2017 at 12:53 #29165
    Laszlo
    Keymaster

    Hi,

    We have bought a TP-Link TL-WR841N for testing purpose, but unfortunately we cannot reproduce the issue I have started the recording Friday morning and the device still in recording state today.
    Could you please tell me the firmware version on your TP-Link TL-WR841N router?

    11th December 2017 at 07:24 #29205
    Francesco Lanza
    Participant

    Hi, sorry for answering with delay, but I could put hands on the router only today:
    The Firmware version is “3.16.9 Build 150616 Rel. 52099n”
    Hardware version: WR841N v11 00000000

    12th December 2017 at 13:45 #29207
    Laszlo
    Keymaster

    Hi,

    Thank you for your feedback.
    It is really interesting our router has a same firmware. I’ve made 2x3days recording with no issues.

    I know you already spent way too much time on this issue, but if you still have a possibility to test something that would be helpful for us at least to know where to search the issue. Could you please try is that issue present as well when the wifi disabled on the router? There’s a switch on the back, need to push and hold down for 5 seconds for disable the wifi.
    Or update the router to the current firmware release: https://www.tp-link.com/us/download/TL-WR841N_V11.html#Firmware

    Attachments:
    12th December 2017 at 18:20 #29209
    Francesco Lanza
    Participant

    Sure thing, I’ll do some tests like the ones you suggested in the next few days and I’ll let you know.
    Thank you for your support.

    15th January 2018 at 12:04 #29340
    Petri
    Participant

    Don’t know if this is right topic, but I had same kind of issue yesterday. External USB3 hard drive was connected straight to u-track. Formatted it with u-track and started to record rehersals strait from card’s rec-button. It has stopped recording around 55 min from start without any reason. X32-rack runs on latest firmware and this was the first recording with that firmware. U-track is connected to ethernet switch, but no software were used during the session.

    15th January 2018 at 12:34 #29342
    Laszlo
    Keymaster

    Hi,

    Do you have a recording.log file in the recording folder?
    If yes please send me that file.
    Is the uRemote was connected during the recording? Does it display any error message on the screen?

    15th January 2018 at 13:21 #29343
    Petri
    Participant

    (19:16:58) -> Fw:3865 HwVs:2
    (19:16:58) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (19:16:58) -> Start prepare pre-recording
    (19:17:00) -> Date 14-01-18
    (19:17:00) -> Created Folder : /MultiTrack/_TempTake0001
    (19:17:00) -> SR:48000 depth:24: ActiveTracks:32
    (19:17:00) -> StreamingChannelMode set to Recording… NoChange!
    (19:17:00) -> Started pre-recording
    (19:17:47) -> Start Recording
    (19:17:48) -> Renaming Directory from /MultiTrack/_TempTake0001 to /MultiTrack/Take0001
    (19:17:49) -> Entered Recording State
    (19:17:53) -> Next Gapless recording file created : MultiTrack/Take0001/Take0001(0002).wav
    (19:18:01) -> Button REC Long pressed: Stopping recording Now
    (19:18:01) -> Exiting Recording State

    (19:18:02) -> Fw:3865 HwVs:2
    (19:18:02) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (19:18:02) -> Start prepare pre-recording
    (19:18:03) -> Date 14-01-18
    (19:18:03) -> Created Folder : /MultiTrack/_TempTake0002
    (19:18:03) -> SR:48000 depth:24: ActiveTracks:32
    (19:18:03) -> StreamingChannelMode set to Recording… NoChange!
    (19:18:03) -> Renaming Directory from /MultiTrack/_TempTake0002 to /MultiTrack/Take0002
    (19:18:03) -> Entered Recording State
    (19:18:03) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0002).wav
    (19:25:49) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0003).wav
    (19:33:35) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0004).wav
    (19:41:21) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0005).wav
    (19:49:06) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0006).wav
    (19:56:52) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0007).wav
    (20:04:38) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0008).wav
    (20:12:24) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0009).wav

    (20:13:30) -> Fw:3865 HwVs:2
    (20:13:30) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (20:13:30) -> Start prepare pre-recording
    (20:13:30) -> StreamingChannelMode set to Recording… Executing!
    (20:13:33) -> Date 14-01-18
    (20:13:33) -> Created Folder : /MultiTrack/_TempTake0003
    (20:13:33) -> SR:48000 depth:24: ActiveTracks:32
    (20:13:33) -> Started pre-recording
    (20:40:58) -> Start Recording
    (20:40:58) -> Renaming Directory from /MultiTrack/_TempTake0003 to /MultiTrack/Take0003
    (20:40:58) -> Entered Recording State
    (20:41:00) -> Button REC Long pressed: Stopping recording Now
    (20:41:03) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0002).wav
    (20:41:03) -> Exiting Recording State

    Take 002 was suddenly stopped. No software were connected during the record.

    16th January 2018 at 16:54 #29347
    Laszlo
    Keymaster

    Well somehow the recording log does not contains any useful information…
    Could you please try to leave your device in recording state for over a night? I would like to see how does it work in long recordings.

    16th January 2018 at 23:47 #29348
    Petri
    Participant

    So, here’s the setup and test resault:

    Hard disk Toshiba SSD 1Tb USB 3
    Formatted directtly from card
    X32 with 32/32 card setup
    x32 firmware 3.08
    Card, X32-rack and Airport Express connected to ethernet switch
    no software used or opened during the test

    Take 001 just to see that recording starts
    Take 002 was the long test. Started 16:43 and that has stopped by itself at 20:13
    Take 003 was only to test that it would start to record again after hitting the rec-button

    (16:43:01) -> Fw:3865 HwVs:2
    (16:43:01) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (16:43:01) -> Start prepare pre-recording
    (16:43:03) -> Date 16-01-18
    (16:43:03) -> Created Folder : /MultiTrack/_TempTake0001
    (16:43:03) -> SR:48000 depth:24: ActiveTracks:32
    (16:43:03) -> StreamingChannelMode set to Recording… NoChange!
    (16:43:03) -> Started pre-recording
    (16:43:03) -> Start Recording
    (16:43:03) -> Renaming Directory from /MultiTrack/_TempTake0001 to /MultiTrack/Take0001
    (16:43:03) -> Entered Recording State
    (16:43:03) -> Next Gapless recording file created : MultiTrack/Take0001/Take0001(0002).wav
    (16:43:32) -> Button REC Long pressed: Stopping recording Now
    (16:43:32) -> Exiting Recording State

    (16:43:35) -> Fw:3865 HwVs:2
    (16:43:35) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (16:43:35) -> Start prepare pre-recording
    (16:43:35) -> Date 16-01-18
    (16:43:35) -> Created Folder : /MultiTrack/_TempTake0002
    (16:43:35) -> SR:48000 depth:24: ActiveTracks:32
    (16:43:35) -> StreamingChannelMode set to Recording… NoChange!
    (16:43:35) -> Renaming Directory from /MultiTrack/_TempTake0002 to /MultiTrack/Take0002
    (16:43:35) -> Entered Recording State
    (16:43:35) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0002).wav
    (16:51:22) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0003).wav
    (16:59:07) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0004).wav
    (17:06:53) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0005).wav
    (17:14:38) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0006).wav
    (17:22:25) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0007).wav
    (17:30:10) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0008).wav
    (17:37:55) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0009).wav
    (17:45:42) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0010).wav
    (17:53:27) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0011).wav
    (18:01:13) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0012).wav
    (18:08:58) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0013).wav
    (18:16:44) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0014).wav
    (18:24:30) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0015).wav
    (18:32:15) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0016).wav
    (18:40:01) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0017).wav
    (18:47:46) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0018).wav
    (18:55:32) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0019).wav
    (19:03:18) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0020).wav
    (19:11:03) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0021).wav
    (19:18:49) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0022).wav
    (19:26:34) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0023).wav
    (19:34:20) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0024).wav
    (19:42:06) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0025).wav
    (19:49:51) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0026).wav
    (19:57:37) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0027).wav
    (20:05:22) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0028).wav
    (20:13:08) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0029).wav

    (20:19:58) -> Fw:3865 HwVs:2
    (20:19:58) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (20:19:58) -> Start prepare pre-recording
    (20:19:58) -> StreamingChannelMode set to Recording… Executing!
    (20:20:01) -> Date 16-01-18
    (20:20:01) -> Created Folder : /MultiTrack/_TempTake0003
    (20:20:01) -> SR:48000 depth:24: ActiveTracks:32
    (20:20:01) -> Started pre-recording
    (22:23:42) -> Start Recording
    (22:23:45) -> Renaming Directory from /MultiTrack/_TempTake0003 to /MultiTrack/Take0003
    (22:23:46) -> Entered Recording State
    (22:23:51) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0002).wav
    (22:24:00) -> Button REC Long pressed: Stopping recording Now
    (22:24:01) -> Exiting Recording State

    17th January 2018 at 11:53 #29350
    Petri
    Participant

    New test. Same config.
    take 001 and 002 just checking
    take 003 has been stopped by itself
    Before take 004 I unplugged ethernet cable from the card. Over 8 hours later it was still recording until I stopped it.
    Is network somehow causing this issue?

    (00:09:43) -> Fw:3865 HwVs:2
    (00:09:43) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (00:09:43) -> Start prepare pre-recording
    (00:09:43) -> StreamingChannelMode set to Recording… Executing!
    (00:09:45) -> Date 17-01-18
    (00:09:45) -> Created Folder : /MultiTrack/_TempTake0001
    (00:09:45) -> SR:48000 depth:24: ActiveTracks:32
    (00:09:45) -> Started pre-recording
    (00:13:37) -> Start Recording
    (00:13:40) -> Renaming Directory from /MultiTrack/_TempTake0001 to /MultiTrack/Take0001
    (00:13:42) -> Entered Recording State
    (00:13:42) -> Button REC Long pressed: Stopping recording Now
    (00:13:44) -> Exiting Recording State

    (00:13:46) -> Fw:3865 HwVs:2
    (00:13:46) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (00:13:46) -> Start prepare pre-recording
    (00:13:47) -> Date 17-01-18
    (00:13:47) -> Created Folder : /MultiTrack/_TempTake0002
    (00:13:47) -> SR:48000 depth:24: ActiveTracks:32
    (00:13:47) -> StreamingChannelMode set to Recording… NoChange!
    (00:13:47) -> Renaming Directory from /MultiTrack/_TempTake0002 to /MultiTrack/Take0002
    (00:13:47) -> Entered Recording State
    (00:13:47) -> Next Gapless recording file created : MultiTrack/Take0002/Take0002(0002).wav
    (00:13:51) -> Button REC Long pressed: Stopping recording Now
    (00:13:51) -> Exiting Recording State

    (00:13:54) -> Fw:3865 HwVs:2
    (00:13:54) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (00:13:54) -> Start prepare pre-recording
    (00:13:54) -> Date 17-01-18
    (00:13:54) -> Created Folder : /MultiTrack/_TempTake0003
    (00:13:54) -> SR:48000 depth:24: ActiveTracks:32
    (00:13:54) -> StreamingChannelMode set to Recording… NoChange!
    (00:13:54) -> Renaming Directory from /MultiTrack/_TempTake0003 to /MultiTrack/Take0003
    (00:13:54) -> Entered Recording State
    (00:13:54) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0002).wav
    (00:21:40) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0003).wav
    (00:29:26) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0004).wav
    (00:37:12) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0005).wav
    (00:44:57) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0006).wav
    (00:52:44) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0007).wav
    (01:00:29) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0008).wav
    (01:08:15) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0009).wav
    (01:16:00) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0010).wav
    (01:23:46) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0011).wav
    (01:31:32) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0012).wav
    (01:39:17) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0013).wav
    (01:47:03) -> Next Gapless recording file created : MultiTrack/Take0003/Take0003(0014).wav

    (01:53:49) -> Fw:3865 HwVs:2
    (01:53:49) -> Device type:Hard Drive, Vendor:TOSHIBA , ProductId:External USB 3.0, Rev:0
    (01:53:49) -> Start prepare pre-recording
    (01:53:50) -> StreamingChannelMode set to Recording… Executing!
    (01:53:52) -> Date 17-01-18
    (01:53:52) -> Created Folder : /MultiTrack/_TempTake0004
    (01:53:52) -> SR:48000 depth:24: ActiveTracks:32
    (01:53:52) -> Started pre-recording
    (02:04:07) -> Start Recording
    (02:04:07) -> Renaming Directory from /MultiTrack/_TempTake0004 to /MultiTrack/Take0004
    (02:04:09) -> Entered Recording State
    (02:04:14) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0002).wav
    (02:11:51) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0003).wav
    (02:19:37) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0004).wav
    (02:27:23) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0005).wav
    (02:35:08) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0006).wav
    (02:42:54) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0007).wav
    (02:50:40) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0008).wav
    (02:58:26) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0009).wav
    (03:06:11) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0010).wav
    (03:13:57) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0011).wav
    (03:21:42) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0012).wav
    (03:29:28) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0013).wav
    (03:37:14) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0014).wav
    (03:44:59) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0015).wav
    (03:52:45) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0016).wav
    (04:00:30) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0017).wav
    (04:08:16) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0018).wav
    (04:16:02) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0019).wav
    (04:23:47) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0020).wav
    (04:31:33) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0021).wav
    (04:39:18) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0022).wav
    (04:47:04) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0023).wav
    (04:54:50) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0024).wav
    (05:02:35) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0025).wav
    (05:10:21) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0026).wav
    (05:18:06) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0027).wav
    (05:25:52) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0028).wav
    (05:33:38) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0029).wav
    (05:41:23) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0030).wav
    (05:49:09) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0031).wav
    (05:56:54) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0032).wav
    (06:04:40) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0033).wav
    (06:12:26) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0034).wav
    (06:20:11) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0035).wav
    (06:27:57) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0036).wav
    (06:35:42) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0037).wav
    (06:43:28) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0038).wav
    (06:51:14) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0039).wav
    (06:58:59) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0040).wav
    (07:06:45) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0041).wav
    (07:14:30) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0042).wav
    (07:22:17) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0043).wav
    (07:30:02) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0044).wav
    (07:37:47) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0045).wav
    (07:45:33) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0046).wav
    (07:53:18) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0047).wav
    (08:01:04) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0048).wav
    (08:08:51) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0049).wav
    (08:16:35) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0050).wav
    (08:24:21) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0051).wav
    (08:32:06) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0052).wav
    (08:39:52) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0053).wav
    (08:47:38) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0054).wav
    (08:55:23) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0055).wav
    (09:03:09) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0056).wav
    (09:10:54) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0057).wav
    (09:18:40) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0058).wav
    (09:26:26) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0059).wav
    (09:34:11) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0060).wav
    (09:41:57) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0061).wav
    (09:49:44) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0062).wav
    (09:57:28) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0063).wav
    (10:05:14) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0064).wav
    (10:12:59) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0065).wav
    (10:20:45) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0066).wav
    (10:28:30) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0067).wav
    (10:36:16) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0068).wav
    (10:44:02) -> Next Gapless recording file created : MultiTrack/Take0004/Take0004(0069).wav
    (10:45:29) -> Button REC Long pressed: Stopping recording Now
    (10:45:30) -> Exiting Recording State

    17th January 2018 at 23:17 #29355
    Petri
    Participant

    One final test behind. I bought cat6 ftp cables and now over 7 hour recording without issue.

    Strange that this kind of behaviour haven’t been earlier. I have been using this setup over a year or so.

    18th January 2018 at 13:09 #29361
    Laszlo
    Keymaster

    But how is that CAT6 FTP cable related to the problem?
    You said you had problems even when no uRemote was connected.
    [quote=”Drumfreak74″ post=3632]
    Take 002 was suddenly stopped. No software were connected during the record.[/quote]
    Is that means the card was connected to the network but no uRemote was on the network?
    If yes please tell me some details about your network setup and devices.

    18th January 2018 at 13:41 #29362
    Petri
    Participant

    As I have mentioned in my earlier posts. Card was indeed connected to network, but uRemote wasn’t in use. Only physical connection caused the issue.

    Setup
    X32-rack with U-track X32 card. Both connected to the ethernet switch. To the ethernet switch has also been connected Apple Airport Express to greate wireless network. Thru that wireless network iPad, iMac etc. can connect to X32 and u-track.

  • Author
    Posts
Viewing 24 posts - 1 through 24 (of 24 total)
  • You must be logged in to reply to this topic.
Copyright © 2022 Cymatic Audio part of