transcoder won't record

[zehn.lotus]

Operating System:
Linux CentOS
Server Location:
Hosted

I cannot get the transcoder to record the DJ's sets when connecting via the dsp plugin to the transcoder, even though the config file specifies the location (which does exist), the DJs are set up in the config file and the calendar.xml, and in the calendar.xml archive="1"

the DJs can connect without issue and the log files don't throw up any relevant errors to the issue even with djdebug enabled.

am I missing something?

[jaromanda]

check the permissions of folder you're trying to write to ... perhaps make it "world" writeable

chmod -R 0777 /path/to/destination/folder

[zehn.lotus]

I made it world writable using that command and it didn't help. thank you for your quick reply though!

[jaromanda]

are you using relative or absolute paths in the config?

[fc*uk]

two things.

1. jaromanda beat me to it.

2. Users have complained from time to time that things that should work don't work for them. The instances I am referencing, we can't figure out why certain features do not work. The only thing we do know is in nearly all of these cases the user is using CentOS. We have concluded that there is just something strange with that OS. Any possibility of using a different *nix OS?

[zehn.lotus]

/plurfm/recorded/

that'd be absolute, right?

[jaromanda]

Originally Posted by zehn.lotus

/plurfm/recorded/

that'd be absolute, right?

yes

what are the following config items set to

djbroadcasts
djcapture
djfilepattern

[zehn.lotus]

djbroadcasts=/plurfm/recorded/
djcapture=1

djfilepattern isn't specified, so it should be default, right?

[DrO]

i've got this on my todo list to see if i can figure out the exact cause (and as current builds of sc_trans are built on CentOS it should be simpler to work out the cause i hope).

-daz

[DrO]

just as a follow-up on this, the recording of dj connections only works when using the legacy protocol to connect to sc_trans.

when using the DSP or another sc_trans in v2 mode (e.g. outprotocol=3 for sc_trans).

am seeing if this can be easily hooked up to work though i currently don't know why it was left incomplete.

[edit]
ok that was simpler to get fixed so will be in the next release of sc_trans though due to some protocol changes about to be started on i cannot provide any eta on when that will be made available.

-daz