@amk9809

Basically, I am new to react-native and javascript, but I am trying to learn both while making this app.
The plan for the app is to have a calendar and I have spent 8 out of these 10 hours on trying to implement libraries with installed calendars like react-native-calendars, react-native-big-calendar, etc. And after none of them working and me trying to fix their libraries, dependencies and what not, I have decided that it will be a lot easier and better for me If I just build myself a calendar using javascript (I’ll even learn more by doing that). So the last hour and a half I have been building the base of it, trying out the .map so I can load every day as a TouchableOpacity. Every day will have a little line underneath it so you can see how many of the five spots are filled fot that day. The calendar is still in progress but I think It won’t take as long as me trying to fix someone else’s libraries.
Under the calendar I am planning like an Agenda for that day, like which dogs are there and if they are leaving that day and stuff like that….

I’m finally done with the idea of this synthesizer. From the last update I have tried to implement a different approach to the pitch change. I have tried, instead of the librosa pitch_shift, to use the sound made using a FFT. That ended up not sounding better, even though I though it would.
I basically just turned my audio info into a complex array using a FFT, where I mover the frequency bins higher or lower depending on if the sound should be lower or higher. There I also calculate how much the sound should be moved based on how many semitones you want.
In the end, the full project consists of a notebook (where you can see the FFT) where there are some tests with the audio. There are also the input audio: C_Major_Piano and the output audio(Only used in testing): Output_Note. Other than that, there are two GUIs, where on one you play with the C Major note and change it’s pitch and on the other you just play the frequency of the wanted note.

I have mostly finished the week organizer in c++, but I am not as happy with it as I thought I’d be. There are some small problems that could be solved manually each time, but that’s not how I want it to work. I want it fully automated. From the last update I have only added a few things to make it run smoother and fix some small mistakes like, like adding a memory for each day, so one person doesn’t show up two times in a day.
I think I should rework this design a bit and I want to use a matrix instead of a string, which I don’t know why I didn’t use from the beginning, like it’s so much better for this.
I’ll keep on working on this and improving it and I’ll post soon… :>

After working around eight and a half hours on the c++ script for this sorter, how I call it, I’ve finally made the platform from which I’ll build everything else.
How it works? Well, basically, you input the path to your .txt file containing all the info you want to input, the info being in the form of a lot of users, each user having his for lines, first: being the name, second: time of day, third: type of training and fourth: some exceptions that may exist for the said user.
Next, the script reads the file and creates a list with all the users and their info. After that it creates a long string that contains all the users, sorted into days of the week and times of days. It calculates it so it uses the least hours of day per week, and so that everyone has the same amount of appointments as it says in the file.
For good measure, I have a function to count how many times each user appears in the string, so I know if there is an error.
That’s all for now (the segmentation errors took a lot of time…), and I’ll keep working and posting about this project! :D

From the last devlog, I have been working on the GUI of the synthesizer. For now it looks pretty promising and I lile how it is going. I have made the synthesizer work and now you click on the notes and the sound lasts two seconds.
The high pitched sounds don’t sound like the piano though…but I’m not sure how to work that out yet.
What was the hard part from the last update wasd making the buttons change colour once clicked. Since they are not part of any class or struct, I have to draw them again in different colour once they are clicked and again in the original colour two seconds later. For that I use a matrix which serves as a memory, which works fine for now, which holds the time when the button was clicked and its position so it can be drawn again.

Currently I have imported the .mp3 file of the C major note onto python and have read it’s contents. And here is the plot of the sound itself.
One part of the code currently reads from your terminal which note you want to play, for example “A4”, and it scales the C major note to that pitch and plays it. After that there is a low-pass filter to clear the frequencies over 4500Hz, mainly to make the notes of higher octaves sound cleaner and like piano notes and not banjo.
I have started to copy the final products from a jupyter notebook to a python file because I want to create a GUI so the user can actually click the note to play, like a little piano.