Can this be put on a raspberry pi 4?

[audovoice]

The Sc1000 is amazing in its simplicity, affordability, and performance.
But I am confused about how it works.
The firmware code seems to just be about configuring and reading the magnetic rotary sensor and crossfader. Is that right?

Then I came across http://xwax.org/ and was looking at that code before I even realized that was what was in the OS folder this project.

What if any modification did were made to xwax to make it work with the sc1000 device?
There is a project that puts xwax on a pi 3 but it still uses digital vinyl.
https://pideck.com/

It seems like one need only jump into the code for xwax after the point it has turned the input stream of audio from jack into a timecode. possibly in timecoder.c or player.c

Or does the sc1000 just make a digital vinyl input stream for xwax? If so is that efficient?

Anyway I am looking into all this because I'd like to try adding features. I'd like to mix in live loop recording. Recording a loop and then getting that into the sc1000 to scratch it. I saw someone make a simple but effective looper with a pi 4.
https://www.youtube.com/watch?v=S_rkdmCzIO0&t
But with a separate device they would need a shared memory.

I see that xwax does have rudimentary live loop recording functionality by loading a file with .live as the file type.

Ultimately I am asking how hard would it be to do something like this project with a crossfader and magnetic rotary sensor, but on a raspberry pi 4.

[DubbyLabby]

“Edited for further clearification”
sc1000 is based on special xwax modified version so the audio mangling comes from it.
Firmware for the pic18f has control over xfader and some buttons, magnetic encoder is directly attached to olimex board which in essence is cheap rpi alternative. It could be possible add extra features but it will require coding as you imagine.

I will suggest you to get djplayer pro on ol iPhone if you aren’t prone to code by yourself.
Money wise isn’t so expensive in comparision (rpi, screen, audio injector…) and you will have support for everything (dvs, rotary encoders, loops… ) and send recorded audio from true live looping apps is just “two clicks” (with AudioShare in between if the source app can send directly to djplayer). Also it’s possible to read pendrives so you can even use sample from other source or export from the iDevice into other gear which reads pendrives, so even looping on iDevices, sample to pendrive and scratch it on sc1000 (and avoid djplayer) could be another workaround.

Said that, I will love to see what you describe happening but after long time expecting someone makes it happen and studying alternatives that will be my suggestion.

[audovoice]

The reality is that in DIY or Buy, the honest answer is almost never DIY. Economy of scale is so crushingly powerful. I think sc1000 manages to be a worthwhile DIY option. Mostly because highly portable doesn't seem to be common design choice. Also music gear in general gets less benefit from scale because it is more of a niche market.

That said, computers are handy for music, tablets are handy too, and used gear is out there and still works.

Good price of a raspberry pi 4 b 2gb is $35 if you can find it in stock. All other things being the same it does not change the price much. Adding a screen for ~$50 bucks minimum, and OR getting the 8gb pi for $75 moves the price of the whole thing much further into not worth it. I think fitting the screen into the lid of a hinge open wooden jewellery box off aliexpress is a good option for form factor. That or plastic, or aluminum junction boxes.

I am basically new to working with hardware. I am an OK programmer. Mostly I do just modify other peoples projects as a starting point to build off of. I am not that familiar with C.

I'd still like to try making the modification. I am guessing most of the code is intact and it would not be a monumental effort to make a sd card image for the pi 3 and pi 4. pideck as it is on github only works on pi 3 but can apparently be copied over to a pi 4 image. But I don't even own a pi 4 and their is a shortage of them.

I think this could possibly revitalize interest in developing pideck, and any feature developed over there has a good opportunity to be ported back to sc1000.

If you have the source code somewhere I would love to see it. If you don't have it handy or want to release it, some info on how you did it I am sure would go a long way. Like what class you modified. Where was sensor data being read. Like was it added to an existing thread or did it have its own.

[DubbyLabby]

The reality is that in DIY or Buy, the honest answer is almost never DIY. Economy of scale is so crushingly powerful. I think sc1000 manages to be a worthwhile DIY option. Mostly because highly portable doesn't seem to be common design choice. Also music gear in general gets less benefit from scale because it is more of a niche market.

That said, computers are handy for music, tablets are handy too, and used gear is out there and still works.

Good price of a raspberry pi 4 b 2gb is $35 if you can find it in stock. All other things being the same it does not change the price much. Adding a screen for ~$50 bucks minimum, and OR getting the 8gb pi for $75 moves the price of the whole thing much further into not worth it. I think fitting the screen into the lid of a hinge open wooden jewellery box off aliexpress is a good option for form factor. That or plastic, or aluminum junction boxes.

That’s what I said “old iPhone” (SE 1st gen are under 100€ second hand and older even cheaper). Also because software is done (and maintained by other).

I am basically new to working with hardware. I am an OK programmer. Mostly I do just modify other peoples projects as a starting point to build off of. I am not that familiar with C.

I’m similar approach with hardware trying to avoid coding the most I can.

I'd still like to try making the modification. I am guessing most of the code is intact and it would not be a monumental effort to make a sd card image for the pi 3 and pi 4. pideck as it is on github only works on pi 3 but can apparently be copied over to a pi 4 image. But I don't even own a pi 4 and their is a shortage of them.

I’m agree and if you are prone to code I encourage you to try it.

I think this could possibly revitalize interest in developing pideck, and any feature developed over there has a good opportunity to be ported back to sc1000.

I thought the same when I proposed some improvements at their github but they aren’t interested in controllers, just timecode.

If you have the source code somewhere I would love to see it. If you don't have it handy or want to release it, some info on how you did it I am sure would go a long way. Like what class you modified. Where was sensor data being read. Like was it added to an existing thread or did it have its own.

Rasteri’s code I’m pointing is all in this github we are talking at the moment. Did you check the folders? I have not extra code by myself but it seems you maybe get confused because I reply more than Rasteri. He has less time than me (stated by himself) and I’m fan of his work from old days of “scratch box controller” which was the sc1000 granpa.
Since I studied the project (alongside others) for my own projects (mostly unfinished or directly interest-lost) I try to help other users in its own journey (and wait Rasteri’s answers on its own too), that’s why I pointed to djplayer since there’s few people in dj field prone to code and/or share their code. Most djs are just users.

[audovoice]

Its funny I just didn't see that software folder. pideck/xwax.c and SC1000/xwax.c are very different. I suspect they do largely the same things but there is so much more error checking that needs to be done on a PiDeck.
Its to the point where I wonder if it would be easier to change pideck to accept rotatory sensor input or change SC1000 so it has a gui again.
I am tempted to go with changing SC1000 as I think it would be easier and cleaner. But I'd like it to be able to record a loop off of a line in or internally and that means using Jack, which is already a part of how pideck works. It might be cleaner and easier to just write something new for recording a loop, using jack.
Anyway I will continue to look into this a bit more.

[DubbyLabby]

AFAIK midi encoder was implemented for song browsing in piDeck but everytime someone ask for digital platter implementation they reject and point into mixxx direction. I also approached them for similar and other request but they have their own issues/roadmap so take some “patience pills”. It’s also a huge development project… maybe xwax will be better option for small improvements and it’s touch-friendly GUI…

pideck/pideck#21

pideck/pideck#42