Closed philipphnz closed 7 months ago
Hi @philipphnz can you please post an excerpt of the module logs with debug level turned on while this is occurring.
Thats the Log. Thanks for the fast response!
I can see the problem. Can you try the version in this fork and let me know how it goes (I dont have access to a unit): https://github.com/phillipivan/companion-module-tascam-cd/tree/master
If you dont know how to build that let me know and I can email a build to you.
Thanks for the fast response! I would be very grateful if you could explain to me, how i build it!
There are instructions here but it can take a while to get the environment setup and going the first time. Happy to email a build to you if you message me your address.
companion-module-tascam-cd.zip
Put this in a sub-folder inside a companion-modules-dev folder and point companion at it. If companion reports a version of 2.0.3 for the module then its running this version. Let me know how you go.
Thanks the module 2.0.3 is running, now i must go to the company where we installed the player and have to test it. I will keep contact to you if the bug is fixed!
When you test it can you please also check the Track Time variable, especially as you change modes with the Current Track Time Sense.
companion-module-tascam-cd.zip Actually try this. It should also do the follow: End of Media feedback. Timer mode (set with Current Track Time Sense) is saved in the device config, and the time polling should pick up this value.
Now I had the time to check the patch! It works great, thank you very much for your fast response and great work! The track id and the current timecode is working great. Do you need any evidence?
Nope. Thank you.
The updated module is in recent Betas, and will be in the next companion release.
Hello, we connected a tascam ss-crd250n with companion (3.2.0) and want to display the current track-ID. When no media is loaded (no SD/USB/CD) there is a "0" as variable. When we put a USB Stick/SD/CD in the tascam, the number is flickering between a number (100/200/400) and very short time the track number. Here is a photo that shows the glitch as good as i could capture it: Do you know that problem? Did we configered something wrong?