Could please somebody clarify what should go where? Talking about the SD and USB.
Ive tried all combinations and possibilities and still I am stuck on 4 white LEDS and frozen normal mode.
After powering the module it works normally for 10-15 seconds after that its a White led dimming into a circle, as it would be searching something. after another 10 seconds it loads back into the normal mode but completely frozen and its the searching again.
For clarification I would need a explanation what file should be going where.
-Technobears new software doesn’t work. (either flashed into the USB via Etcher or just dragged it there)
-The PI3 image qubit provided on their webpage doesn’t work (either onto SD or USB/ Flashed via Etcher or not flashed)
tried two different SD cards formatted into the pi3 image via etcher.
-USB stick was formatted into FAT32
-After removing everything from the overlay folder inside the SD card, the searching is not triggered it just stays white all the time, so I figured it is for sure with the SD card.
Could anybody provide me the correct files that should be going into SD card and USB ?
Thank you
Hi, it sounds obvious, but also try emailing their support. They are really helpful.
For the SD card, the image provided on QUBit’s site should stay as it is. No need for putting files on there. Just reimage with the correct RPi version 3 or 4. I have no experience with technobears version.
When inserting a USB, sound files are copied to the SD card, but this should al be managed by the Nebs OS. Don’t fiddle around with the SD after imaging.
Just to be sure, it will not load more than 75MB of files. If the one file (or first file) is already more than 75MB, it cloud get ‘stuck’ after loading. I’m not sure.
This is all logical what you just wrote, but I don’t own the original usb which came with the module.
I have a normal USB in which case I have had to put something into.
So I would need a file into my usb, but which one?
Also its not the fist time I see somebody mention the 75MB load issue.
So. where I should be looking for the sounds? on the Sd card, there is a folder called Overlay, which looks the closest to audio material, besides that its just Logs.
And as I mentioned on the usb is nothing, so where does the sounds come from?
Ah ok. You just put samples, wav of flac, on the USB drive in the root of the USB disk. That’s all. Folders are ignored. The Nebulae will load the sound files from the USB.
There are some examples files on the original USB and a folder with the manual I think, but it can be completely empty but just the sound files.
It should also write a logfile on the USB disk after turning on the Nebulae.
So, a freshly imaged SD (which would done only once, never to be touched again) and then put wav of flac files on the USB. Try a single wav of a few MBs first.
Put the USB in the Neb and power it on.
It should start with the Granular Instrument, if it doesn’t, long press ‘Speed’ until LEDs are green. Rotate Speed until all four LEDs are green (not three). Short press the the first button (record) and press Speed again. This should load the Granular Instrument.
Ok, if you mean that even the USB is empty, but you still hear sounds, that’s because the sounds are copied to the SD from the USB. If the USB is empty it will still play the ‘cached’ files from SD.
I don’t exactly know where they are on the SD, but I think you need to look in an ‘audio’ folder. Maybe because it’s an RPi, there is a second partition the SD card which you need to mount on Linux. I don’t know exactly.
All my Nebulae programming I do on an emulator, I barely touch the SD card itself (only once because of a tuning issue).
On another note, if the new samples are not showing up in the SD card, I recommend trying to load them by placing the USB Drive directly into the RPi on the back of Nebulae.
Occasionally the PCB chit and ribbon cable that connects the front panel USB port and the Pi can cause intermittent issues.
Still waiting for the official response from qubit but I’ve picked up a brand new USB and micro SD
I might need a factory reset or something at this point. There are no problems with the sounds, in that 10 second interval Im pretty much capable of manipulating the audio, even pressing 'file’allows me to search thru some.
My problem is that it freezes completely as it’s loading into a booting mode. 4 whites.
I need files. For rebooting the pi image.
Mem: 973Mi 45Mi 862Mi 0.0Ki 66Mi 913Mi
Swap: 0B 0B 0B
Number of files in [/home/alarm/mandatory_files.txt] found = [10]
Number of files in [/home/alarm/mandatory_files.txt] NOT found = [0]
No Missing Files.
Checking For Reversion Request
Unable to find Factory Firmware Reversion Request
No request to revert to firmware.
Number of files in [/home/alarm/mandatory_files.txt] found = [10]
Number of files in [/home/alarm/mandatory_files.txt] NOT found = [0]
No Missing Files.
Checking For Reversion Request
Unable to find Factory Firmware Reversion Request
No request to revert to firmware.
Number of files in [/home/alarm/mandatory_files.txt] found = [10]
Number of files in [/home/alarm/mandatory_files.txt] NOT found = [0]
No Missing Files.
Checking For Reversion Request
Unable to find Factory Firmware Reversion Request
No request to revert to firmware.
Number of files in [/home/alarm/mandatory_files.txt] found = [10]
Number of files in [/home/alarm/mandatory_files.txt] NOT found = [0]
No Missing Files.
Checking For Reversion Request
Unable to find Factory Firmware Reversion Request
No request to revert to firmware.
Number of files in [/home/alarm/mandatory_files.txt] found = [10]
Number of files in [/home/alarm/mandatory_files.txt] NOT found = [0]
No Missing Files.
Checking For Reversion Request
Unable to find Factory Firmware Reversion Request
No request to revert to firmware.
The information you’ve pasted from the neb_log.txt file is missing the firmware version check that normally accompanies this text. It would normally look like this:
Fri, 13 Apr 2018 02: 27:36 +0000 --- VERSION, v2_1_2
Fri, 13 Apr 2018 02: 27:36 +0000 --- VERSION_DATE, 4/24/2019
CPU temp=61.7'C
GPU temp=61.2'C
total used free shared buff/cache available
Mem: 973Mi 44Mi 861Mi 0.0Ki 67Mi 913Mi
Swap: 0B 0B 0B
Number of files in [/home/alarm/mandatory_files.txt] found = [10]
Number of files in [/home/alarm/mandatory_files.txt] NOT found = [0]
No Missing Files.
Checking For Reversion Request
Unable to find Factory Firmware Reversion Request
No request to revert to firmware.
It seems like the top portion of your text file might of been cut out of your paste, but I want to make sure you are seeing the Nebulae version lines in your text file. Otherwise, your text file is not indicating that there is an issue in particular.
That being said, we will want to confirm that the Disk Image was properly reformatted. You will want to take this .zip file for your Pi3 Nebulae, and place it directly into Etcher. Do not unzip it.
You will want to confirm which Raspberry Pi is on the back of your Nebulae, which you can decifer using this page on our site.
Select the Nebulae SD card as the Target, and flash. It should take upwards of 15 minutes to flash.
When you reboot your Nebulae, I recommend placing the default factory samples on the USB Drive. This helps rule out the possibility of audio files causing any issues.
Let me know if the issue is still happening after this!
I was able to figure out something very important with this information you just provided.
My module can’t load a firmware seems like. Because, yes, Ive already tried exactly what you just wrote just about 9-13 times. On different USB’s and SD cards.
Good to know. At this point, it might be best for us to check out your Nebulae here in the shop, as there may be an issue with the Pi itself. I’ve DM’d you instructions on how to get in touch with our tech support team. They will be able to help you from there!