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.

Sign up for GitHub

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

Jump to bottom

OSC Output "base 10:" Error #953

Closed
Jorkim opened this issue May 10, 2024 · 3 comments · Fixed by #954
Closed

OSC Output "base 10:" Error #953

Jorkim opened this issue May 10, 2024 · 3 comments · Fixed by #954
Labels
improvement Improvement on existing feature

Comments

@Jorkim
Copy link

Jorkim commented May 10, 2024 •
edited
Loading

Hi,

first i have to say i really like ontime. Especially the new v.3 version.
But i have a problem since i have started using it (v.2)

When i use the OSC Output to trigger Ableton Live v.11 (via the plugin AbletonOSC) i get a base 10 error.

to trigger a cue in ableton i have to use the command: /live/clip/fire track_id clip_id

in the case of triggering the 1 column in the first 1 row i have to use: /live/clip/fire 0 0 but it looks like if ontime is converting these integers to a string because of the space inbetween.

When i just use /live/clip/fire 0 i am only getting an out of range error but it leaves the command as an integer.

This occours for all inputs with more than one variable.
This is the exact error message: /live/error,Error handling OSC message: invalid literal for int() with base 10: '0 0'

When i use the console from the AbletonOSC plugin to send an OSC message to Ableton averything works as it should with exactly the same command.

Thanks for your help.
@cpvalente
Copy link
Owner

cpvalente commented May 11, 2024 •
edited
Loading

Hi @Jorkim, thank you for this.

I had a quick test and found that you are correct.
the payload is treated as a string in that case.
Screenshot 2024-05-11 at 09 16 45

I also see several threads in different apps about similar issues, so I guess this may be a common implementation problem.

I done some quick changes on our side and we can get the expected payload
Screenshot 2024-05-11 at 09 27 48

However, I just need to ensure that this wont have unintended consequences.
We will have a fix for the upcoming release, thank you again

@cpvalente cpvalente mentioned this issue May 11, 2024
Merged
@cpvalente cpvalente added the improvement Improvement on existing feature label May 11, 2024
@cpvalente
Copy link
Owner

Hi @Jorkim , could you please test out the new beta and give us some feedback on the behaviour?
Betas need to be downloaded from the release page here
https://github.com/cpvalente/ontime/releases/tag/v3.1.0-beta.1

@Jorkim
Copy link
Author

Jorkim commented May 31, 2024

Hi,
it looks like everything is working so far. Ive not found any problems with it.
I will let you now if i encounter any problems.
Thanks for your help and work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement Improvement on existing feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

refactor: improve payload type cpvalente/ontime
2 participants
@cpvalente @Jorkim