Announcement

Collapse
No announcement yet.

ERROR 157k ?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • pro424
    commented on 's reply
    Thank you Aaron! I will try reformatting the card but I'm not sure when I will have time to do more testing. I assume the problem is not something you recognize? If it is of any help I could send you the entire project if you wanna try it on your end. If so, please send my a message so I can prepare a download link. Do you know anything about the corrupted files not being able to open in Ableton and looking like they are hours long on the Bluebox while in reality they are only a few minutes?

  • Aaron
    commented on 's reply
    Sorry to hear this. By "open tracks" I mean track is the project set to active (EDIT then A). Clearly that is not the problem here. Please let us know if reformatting the card does not do the trick.

  • pro424
    replied
    So I continued working on the project yesterday and today. In hope of getting rid of errors I used it standalone and just plugged in instruments but I still gor a lot of errors and had to redo most takes. The final nail in the coffin was when I had finally goten all tracks down and was about to record the master but it wouldn’t go through the 7 minutes the whole track was so I transferred everything to Ableton Live. I made sure I only had the relevant tracks active under edit. I noticed however that tracks recorded when getting an error usually looks like they are several hours long in the edit view. Ableton was also unable to open them. VLC on the other hand ould open them and convert them to the same file format after which Ableton didn’t complain about corrupted files anyomre. Will reformat the card but tbh I’ll most lilely just record straight to Ableton next time I’m multitracking.

    Leave a comment:


  • 0101-Usr
    commented on 's reply
    pro424: I have to check it, but I think it's not about midi messages, but just because of play/stop/play, whatever it's via midi or not. I just play/stop often in my midi controller, so that's why I filter it. But good question, I'll try to check it.

  • pro424
    commented on 's reply
    I'm not sure what "tracks open" mean in this case. How many tracks I have recorded on in this particular project? This started happening for me after having recorded single track in a new project.

  • Aaron
    replied
    Here is an update: We reviewed recording and discovered that you can run out of buffers fairly quickly if you have lots of tracks open. For example, if you press EDIT then B, if there are more than about 30 active tracks you might start to see this problem. Please check it out on your end and let us know.

    Thank you.

    Leave a comment:


  • pro424
    commented on 's reply
    And even with those filters you still get the error? I could easily setup my system so that only clock and no start/stop is sent to the Bluebox if it would help.

  • 0101-Usr
    commented on 's reply
    pro424: I don't have solution for BlueBox, I hope firmware will fix this issue. I only set midi filter on midi router to send clock to BB (sync for echo) but no start/stop messages.

  • pro424
    commented on 's reply
    Interesting! This was the first time I tried to do overdubs and multitracking in several sessions. Before I’ve only done multitrack plus master in one session without any problems as well so it may be similar to your issue. Do you have solution for it? Is a reboot of the machine enough or is the error reoccurring in projects where there’s already recordings?

  • nanostepper
    replied
    Thanks for all the responses, everyone. After I got the error, I rebooted and haven't had a recurrence yet. To be continued...

    Leave a comment:


  • Aaron
    replied
    Thanks for letting us know. We will investigate.

    Leave a comment:


  • rev-eng
    replied
    I've had this happen once too, using the supplied SD card and power supply. Can't remember the number associated with the error 254ish I think

    Leave a comment:


  • 0101-Usr
    replied
    As mentioned before, I had this error too. But it happen only when start recording, stop and start again. It's second time when i filter stop/start messages and allow to record without any breaks all jam (about 3,5 hours), all channels + main. And it works. But when I stop and record again, then it show errors. In that case I think it's not about card, but something else.

    Leave a comment:


  • pro424
    replied
    Had something similar happening repeatedly today for the first time. Recording a first track around seven minutes went well but when recording on a second track I got an error after a few minutes which just kept counting up quite rapidly. This happened several times and I had to reboot the bluebox each time it happened. In a few seconds it reached several thousand and it never stopped counting really. I have my Bluebox synced to an Elektron Analog Four through a Blokas MIDIhub. Could there be some kind of sync issue or is it rather related to the card (Kingston Canvas Select Plus 64gb with around 50gb free)?

    Leave a comment:


  • Aaron
    replied
    There is only one error message on bluebox: It means it could not record a piece of audio for some reason. The 157K refers to how many times it happened--which is a lot in this case.

    As far as how to address this error, the first place to look is the micro SD card. We supply cards that are good but not great. We have found the SanDisk cards with an A2 rating to be the most reliable. You may also want to try freeing up space or reformatting your existing card to streamline recording.

    Let us know if this does not help.

    Leave a comment:

Working...
X