That’s an interesting feedback.
It seems something seriously wrong. I spent some time to read though all of the logs.
The problem there’s no strait indication what is going on with the drive.
This can be happens because of the “sleep mode”, you can see right after starting the recording there’s a problem
(14:08:57) -> Started pre-recording
(14:21:36) -> Start Recording
(14:21:36) -> Renaming Directory from /MultiTrack/_TempTake0007 to /MultiTrack/Take0007
(14:21:37) -> Entered Recording State
(14:21:47) -> Error: No streaming message received for last 10 seconds!!!
(14:21:53) -> Button Stop pressed from uRemote: Stopping recording Now
(14:21:54) -> Exiting Recording State
But this one is really strange. Here you can see in the first chuck has no problem at all then everything messed up.
(16:14:18) -> Started pre-recording
(16:45:38) -> Start Recording
(16:45:38) -> Renaming Directory from /MultiTrack/_TempTake0005 to /MultiTrack/Take0005
(16:45:40) -> Entered Recording State
(16:45:45) -> Next Gapless recording file created : MultiTrack/Take0005/Take0005(0002).wav
(16:53:28) -> Next Gapless recording file created : MultiTrack/Take0005/Take0005(0003).wav
(16:55:16) -> Error: Dropout @:564 seconds
(16:55:22) -> Error: Dropout @:569 seconds
(16:55:22) -> Error: No streaming message received for last 10 seconds!!!
(16:55:27) -> Error: Dropout @:574 seconds
(17:13:39) -> Next Gapless recording file created : MultiTrack/Take0005/Take0005(0004).wav
(17:13:44) -> File Enocder Error: File WriteError
Some of your logs has this line: Error: No streaming message received for last 10 seconds!!!
This means something is really wrong and the data trasfer stops more than 10 seconds, and after that the “File Enocder Error: File WriteError” really indicate serious problem.
Do you ever experienced issue where you try to record from analog inputs using the console internal clock?
Which device is the master in your setup where you are using digital communication?
About the uTool, in Target editor mode it just reads the first chunk of the recording, which is around 8 minutes, that’s why you cannot play back the entry song. I don’t think we will provide a solution for this request in the coming weeks (sorry)
I agree it worth to try with SSD (MUST BE FORMATTED WITH THE CARD).
It would be nice to try with one another HDD as well.
Somehow the uTrack-X32 cannot access to the drive cannot finish the write process.
When the first band start I start the record after while of a time I notice that Cymatic record time freeze and runs not synchro white the normal time. The seconds make some jumps or lost.[/i]
This can happens if you have a lot’s of dropouts in the recording or when not possible to write on the drive.