Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in the seek and play behaviour + Various improvements #18

Open
saefr opened this issue Aug 4, 2024 · 3 comments
Open

Bug in the seek and play behaviour + Various improvements #18

saefr opened this issue Aug 4, 2024 · 3 comments

Comments

@saefr
Copy link

saefr commented Aug 4, 2024

Hi nikarh, i hope you are fine since the last time ? :) I worked with your project smoothly for the last months, also used for live and it was a really powerful tool ! The edit playlist "as-you-go" is wonderful by the way.

I just wanted to point some improvements or bugs i have seen during the time working with your interface.

It seems the regions are not properly seeked after a song is ended. If i use the < Previous or > Next button on the interface, everything is okay. But automatically when the song come to the end, it doesnt goes to the next one and the marker stays where it is. I dont know if its wanted or not as a behaviour,

I also wanted to use a Midi pad to have physical buttons for stop/play/previous song/next song. Is there a way to access your functions (like action) since it's directly in the web interface and not in the Reaper ?

And finally, is it possible to have the control buttons always fixed on the top of the page ? If you have enough songs, you cant access the buttons if you scroll enough. Also, if its possible to scroll automatically on the song with the actual focus, it will be great.

image

Thanks for your time as always, and have a great week.

Saefr

@nikarh
Copy link
Owner

nikarh commented Aug 5, 2024

Hey!

It seems the regions are not properly seeked after a song is ended. If i use the < Previous or > Next button on the interface, everything is okay. But automatically when the song come to the end, it doesnt goes to the next one and the marker stays where it is. I dont know if its wanted or not as a behaviour,

It is expected behaviour, but this is something that can be changed.

I also wanted to use a Midi pad to have physical buttons for stop/play/previous song/next song. Is there a way to access your functions (like action) since it's directly in the web interface and not in the Reaper ?

This is a nice idea. I suppose you have a midi controller with daw control buttons? Or do you want to be able to map physical buttons to actions in the UI?

And finally, is it possible to have the control buttons always fixed on the top of the page ? If you have enough songs, you cant access the buttons if you scroll enough. Also, if its possible to scroll automatically on the song with the actual focus, it will be great.

Both make sense, will try to find time for that on the weekend

@saefr
Copy link
Author

saefr commented Aug 6, 2024

It is expected behaviour, but this is something that can be changed.

Okay, good to know ! On others playlists/region plugins, you can choose how the playlist works : with a stop/without a stop after playing the previous song, or automatically goes to the other song/or not automatically goes to the other song . Maybe if we have the possibility to choose how it behave, with an option somewhere ?

This is a nice idea. I suppose you have a midi controller with daw control buttons? Or do you want to be able to map physical buttons to actions in the UI?

I have one yes. For the play/stop the actions exists already in Reaper, so its not a problem. For the next song/previous song, its a specific action on your ui since it use its own logic to choose the playlist, so the daw control buttons will not work. I have also the option to use midi pads instead of daw controls buttons.

I dont know which one is the best : create actions in Reaper to mimic your buttons, mapping a shortcut or a midi action to the web interface? With how i see your project, the easiest and more valuable way is adding the actions in the interface itself. If it works for this, it can also be used to add shortcut or midi mapping for other buttons : each song in the playlist can have is own shortcut, or the loop button, etc ...

Both make sense, will try to find time for that on the weekend

Great, thanks !

@saefr
Copy link
Author

saefr commented Nov 12, 2024

Hi, hope you are doing well. Do you think you're gonna be able to work on this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants