Hi,
I am loving the idea of the Cubase TC insert as Protools, but I keep getting the wrong TC
so, I am inserting 01020304 i am getting 01:00:08:16 or any other TC
or 01050607 getting 1:00:12:22 could it be some code offset ?
its fine when I do it via set up timecode
Thanks
Frank
- In reply toFrank_Ilfman3⬆:Jesper Ankarfeldt @JesperA2021-04-14 11:51:20.661Z
Hi Frank.
Great. Well it's super powerful. I've used it for 4 years. So let's track down what could be the issue.
Just some quick ones:- where do you see the "wrong" timecode?
If it's on the video, then please check your the offset in the project setup.
.
- If it's on the transport bar please make sure your transpor panel is showing timecode and not seconds maybe.
Potentially make a screen capture or something so I can identify what might be wrong. I don't think there's other places where a offset can be applied.
- where do you see the "wrong" timecode?
- FIn reply toFrank_Ilfman3⬆:Frank Ilfman @Frank_Ilfman3
Hey Jesper,
All seem to be ok and works fine when i do it via the cubase set timecode, but not the command
Jesper Ankarfeldt @JesperA2021-04-23 12:36:32.606Z
Hi Frank. Sorry I didn't see your respond. I'll check up on this soon.
Jesper Ankarfeldt @JesperA2021-04-23 13:15:28.491Z
Hi Again.
So I realized what was the issue from your pictures. It's because I've always been working with subframes.
I've updated the whole packages so all commands should be able to work with and without subframes.
Let me know. Best
- FIn reply toFrank_Ilfman3⬆:Frank Ilfman @Frank_Ilfman3
Hey Jesper,
No worry, i have been away from the studio for a few days.
did the update im getting this erorr now"24.04.2021 15:55:35.07 [Backend]: !! Command Error: Set Timecode via popup (Pro Tools Style) [user:ckn8sq3l900048d10u1dunjrk:cjuvmfzbr000hwg102riaq59t]:
No text in clipboard after waiting 2000 ms (Set Timecode via popup (Pro Tools Style): Line 36)"Also my prefrences TC is diffrent, but i think it could be cubase vs Neuando
Jesper Ankarfeldt @JesperA2021-04-24 16:45:38.296Z
Yes your preference window looks a bit different, but that's indeed just Cubase vs Nuendo.
Can you try update again?
I think the issue was because your computer didn't manage to open the set timecode at cursor window (could be my computer is doing it faster so I don't experience the issue)
Now it should wait for the window to appear before continuing the script.Let me know.
- FIn reply toFrank_Ilfman3⬆:Frank Ilfman @Frank_Ilfman3
did the update and restarted sf but no luck
still the same :
24.04.2021 18:08:18.27 [Backend]: !! Command Error: Set Timecode via popup (Pro Tools Style) [user:ckn8sq3l900048d10u1dunjrk:cjuvmfzbr000hwg102riaq59t]:
No text in clipboard after waiting 2000 ms (Set Timecode via popup (Pro Tools Style): Line 38)i can see it opening the set Tc and then it just stay on screen with no numbers change
Jesper Ankarfeldt @JesperA2021-04-24 17:36:54.256Z
That's really odd. If only I had Cubase so I could check if that's were the difference lies.
Anyway, now I've replaced tab with a mouse click. Can you check if that works, if you update the app to 1.1.2 (Btw you shouldn't need to restart SF, but thanks for doing that just to remove that as an option of error).
- FIn reply toFrank_Ilfman3⬆:Frank Ilfman @Frank_Ilfman3
No go
"24.04.2021 18:53:27.74 [Backend]: Clicking with mouse here: 2951, 300
24.04.2021 18:53:30.21 [Backend]: Logging error in action (01) ClipboardWaitForTextAction: No text in clipboard after waiting 2000 ms
24.04.2021 18:53:30.21 [Backend]: !! Command Error: Set Timecode via popup (Pro Tools Style) [user:ckn8sq3l900048d10u1dunjrk:cjuvmfzbr000hwg102riaq59t]:
No text in clipboard after waiting 2000 ms (Set Timecode via popup (Pro Tools Style): Line 37)<< Command: Set Timecode via popup (Pro Tools Style) [user:ckn8sq3l900048d10u1dunjrk:cjuvmfzbr000hwg102riaq59t]
24.04.2021 18:53:46.68 [Backend]: [SF_FIREBASE_WS]: Sending keep-alive
"
you can download a full working demo of Cubase if thats helps ?
Jesper Ankarfeldt @JesperA2021-04-24 20:20:33.557Z
Very weird that it doesn't work.
Can you try a couple of things and screen record them.
You can do this with QuickTime Player.1
- open the Project -> Set Timecode at Cursor...
- press tab.
2
- open the Project -> Set Timecode at Cursor...
- click with your mouse where it says Start.
3
- Try to copy this in to an empty script:
var app = sf.ui.cubendo; app.getMenuItem('Project', 'Set Timecode at Cursor...').elementClick(); app.windows.whoseTitle.is("Set Timecode at Cursor").first.elementWaitFor(); app.windows.whoseTitle.is("Set Timecode at Cursor").first.mouseClickElement({ relativePosition: { x: 130, y: 50 } });
All of these should highlight the timecode field.
You could also run the command while recording the screen but that would only be for me to see "how" it's going wrong. But we should figure out if the things above doesn't work.I'm not gonna downloading a 10GB Cubase installer from Steinbergs slow servers, for it to stop working in a month, sorry :)
It would be different if we could just run Cubase from the Nuendo license, which would make a lot of sense as it contains all the same features.
- FIn reply toFrank_Ilfman3⬆:Frank Ilfman @Frank_Ilfman3
ok
Here are the link to the recorded files
1
https://www.dropbox.com/s/ht9c0cfdd01ewm7/WhatsApp Video 2021-04-26 at 18.40.39.mp4?dl=0
2
https://www.dropbox.com/s/i2nz9i249uls79i/WhatsApp Video 2021-04-26 at 18.40.54 (1).mp4?dl=0
3 (script)
https://www.dropbox.com/s/7tl37v37of6qubh/WhatsApp Video 2021-04-26 at 18.40.54.mp4?dl=0Jesper Ankarfeldt @JesperA2021-05-07 12:07:46.140Z
Sorry I've been traveling a bit.
Need to get to the bottom of this, cause I would like the feature to work for everyone :)
Still don't get why the tab works differently in Cubase. But I think I've found a method that should work.
I've implimented it in the package already. You can also try it standalone by copying this in to an empty script and tell me if it selects the full timecode:var app = sf.ui.cubendo; app.getMenuItem('Project', 'Set Timecode at Cursor...').elementClick(); app.windows.whoseTitle.is("Set Timecode at Cursor").first.elementWaitFor(); app.windows.whoseTitle.is("Set Timecode at Cursor").first.mouseClickElement({ relativePosition: { x: 130, y: 50 }, clickCount: 3 });
In case this doesn't work (either the full package or the small piece of script doesn't select the timecode field) then I would have you to play around by clicking on the "Set Timecode at Cursor" window and figure out what makes it select the current timecode.
The reason why this hasn't been tested was indeed because of the thing with subframes. If I had said it only works when you use Cubendo with subframes it wouldn't have been a problem, but I like both modes being supported.
Let me know your results
- FFrank Ilfman @Frank_Ilfman3
No worry,
Ok, so when i use the updated package it works, but getting this error:
07.05.2021 19:42:08.10 [Backend]: !! Command Error: Set Timecode via popup (Pro Tools Style) [user:ckn8sq3l900048d10u1dunjrk:cjuvmfzbr000hwg102riaq59t]:
No text in clipboard after waiting 2000 ms (Set Timecode via popup (Pro Tools Style): Line 37)<< Command: Set Timecode via popup (Pro Tools Style) [user:ckn8sq3l900048d10u1dunjrk:cjuvmfzbr000hwg102riaq59t]
When i use the script i only get whats in the pic, so i dont get the soundflow popup to enter the TC like when i use the package
"then I would have you to play around by clicking on the "Set Timecode at Cursor" window and figure out what makes it select the current timecode".
this works by mouse clicking or the -> arrow botton or as you put a number it jump to the next oneJesper Ankarfeldt @JesperA2021-05-11 15:28:22.429Z
What I ment was how to select the entire timecode, like this:
Clicks / Doubleclick and where you have to click in order to achieve it. I imagine a specific amount of tabs might also do it. I don't know. Maybe it's not possible all along, which have caused the problem. But it would be really weird if it wasn't.
- FFrank Ilfman @Frank_Ilfman3
Its a double click on the numbers to select all
Tab just jump to the second number and then OK or cancelJesper Ankarfeldt @JesperA2021-05-12 08:46:56.656Z
Alright. So I figured out another issue I hadn't paid attention to, which is the fact that the way timecode is represented changes depending on the fps. And you've probably been working in 24fps and I've been working in 25fps.
I've updated the package. I feel almost certain it will work now.Thanks
- FFrank Ilfman @Frank_Ilfman3
This seems to work now,
its a little comfusing at first as you dont see the Tc changeson the cubase set timecode but once you press play it updated and play from the right TCi notice its only for 24 and 25fps
Is it possible to add 23.98 and all of 29.97 and 30fps ?
Jesper Ankarfeldt @JesperA2021-05-13 12:12:32.161Z
Just to make sure, is it the function for "set timecode at cursor" where it doesn't change/update the timecode in Cubase?
or some of the other functions in the package where you jump to a new timecode position?I'll go through the different fps and make sure they will work.
- FFrank Ilfman @Frank_Ilfman3
Great.
Yes its the function for "set timecode at cursor" that doesn't change
Jesper Ankarfeldt @JesperA2021-05-14 09:16:56.194Z
Hmm. It works just fine here with all other fps. Maybe make a video of it to show me how it does it wrong.
About the timecode not updating. It's because you use the standalone "Time Display" that you can open and resize, right? Cause everything else does sync directly here. In case you want the Time Display to sync directly you could make a macro where you, after
calling the "set timecode via popup" adds two times clicking the "Transport -> Transport Commands -> Exchange Timeformat". This will up date it.(in terms of other fps, the only thing that "shouldn't" work is setting the frames part above 30 via the popup or functions, as that's so uncommon, so I'd rather want people to get an error message if they put in a timecode which have a higher frame position then 30, since this is most likely a wrong input rather then desired)
- FIn reply toFrank_Ilfman3⬆:Frank Ilfman @Frank_Ilfman3
My bad, the timecode dispaly dosnt change automaticlly when you change fps ( i have asked them to fix it as you need to do it manually everytime if using it, but no replay)
it seem to work now, thanks for all the help Jesper
Jesper Ankarfeldt @JesperA2021-05-14 15:44:19.871Z
Thanks for the feedback and patience.
Was a tuff one to get through :) But it will then work more solid for others moving forward.Yeah Steinberg isn't always the most responsive unfortunately.