DTS IN ASO

my dimension are like this
measures
model
part
supplier
time (dts as Y-T-D)
apptime
scenario
I want to apply dts as ytd on time dimension how to apply dts please guid us

Try :- http://garycris.blogspot.com/2008/07/time-functionality.html
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

  • Using PeriodToDate MDX function in an ASO cube (Dynamic Time Series)

    Hyperion Essbase 7.1.2
    Since ASO doesn't support Dynamic Time Series (DTS), I am trying to use the "PeriodToDate" MDX function to get MTD and YTD totals. Below is my Time dimension:
    Time (Time - Stored)
    ...I---> 2007
    ......l---> Q1-2007
    .........l---> Jan-2007
    ............l---> 2007-01-01
    ............l---> 2007-01-02
    ............l---> 2007-01-03
    .........l---> Feb-2007
    .........l---> Mar-2007
    ......l---> Q2-2007
    ......l---> Q3-2007
    ......l---> Q4-2007
    Syntax:
    PeriodsToDate ( [layer [, member ]] )
    I tried many different ways to get the right syntax but it didn't work when I set the formula on member "2007" for YTD totals or on months to get MTD. Any help would be appreciated.
    Message was edited by:
    user597443

    ASO does not have Dynamic Time Series at all (unless something just recently changed)
    Period to date functionality has to be managed via MDX formulas and/or alternate roll ups in your time dimension.
    Time Balancing does have to be a stored hierarchy, which is what you generally want anyway. The issue you have with Time balancing is that some times if you have an alternate roll up in your time dimension, it can cause problems with Time balancing.
    If you want to use Time balancing, I would sugest a single stored time heriarchy and use an anakytic view dimension for the period to date functionality.
    You can see a post I have on my blog that talks about this: garycris.blogspot.com
    One other thing to mention. If you wan to use built in time balance functionality, you must tag a dimension as Account Type and it will have to be a dynamic dimension.

  • ASO Cube with BSO Partition as a Target

    Hi,
    Can someone please explain me the following because after reading different blogs as well as some other Essbase documents I am not able to understand,
    What is the actual use of having a BSO Transparent partition (target) of an ASO cube (source)?
    How exactly does the Write-Back functionality works if I have a BSO Transparent partition (target) of an ASO cube (source)?
    And lastly, in what business scenario one would implement a BSO Transparent partition (target) of an ASO cube (source)?
    Your help is much appreciated.
    thanks,
    fikes

    I have a situation where I have a BSO (target) on top of an ASO (source).  This was to try and resolve the dynamic time series (where time and periods are in different dimensions).  The DTS works almost great in the BSO partition.
    The other problem (or why we wanted to go to ASO) was that BSO cubes do not handle attributes across partitions (we have quarterly data in transparent partitions) to the target cube. -- but we do have dynamic time series.
    What I'm facing now it that the attributes work in the BSO (target) except when using a dynamic time series.
    The attributes are defined in both the BSO and ASO cubes.
    Any suggestions on how to handle attributes AND dynamic time series ?

  • Can we upload data in ASO Cube version 11.1.2

    Hi,
    I have a requirement where in ASO cube users need the ability to enter their plan data into the ASO application. Do we need to create Transparent Partition for that. I have an ASO and Hyperion Planning cube and in my Planning cube I have more number of dimensions as compare to ASO.
    Please advise
    Thanks in advance.

    If you are using the Excel add-in you do NOT do a lock, just a send. The lock is a BSO concept to put a hold on blocks. ASO has no blocks to lock. From smartview you do a submit and it handles it all for you. The beauty of using ASO is exactly what you mention, results are immediate without a calc.

  • Can we load data for all levels in ASO?

    Hi All,
    Im creating cube in ASO
    can i load data for all levels in ASO
    we can load data for all Levels In BSO but in ASO i need confirmation????
    and one more
    wat is the consider all levels option in ASO is used for ? wat is the purpose?
    Can any one help ,it would be appriciate.
    Thanks

    In an ASO cube you can only load to level zero
    The consider all levels if used for aggregation hints. It allows you to tell the aggregation optimizer to look at all levels when deciding if aggregation needs to be done on the dimension

  • Can we load data for all levels in ASO cube

    Hi All,
    Can we load data for all levels of members in ASO cube in 9.3.1.
    Regards

    Yes you can load data for all levels in an ASO cube in any version HOWEVER, none of the upper level data in any cube will be there when you look for it. You will get a warning message in the load because ASO cubes don't store data at upper levels. It is the same as loading data into dynamic calc members in BSO cube. It will do the load without compalints, but there will be no data there (At least you get the warning in ASO)

  • Need to convert DTS packages to SQL Server 2012 environment.

    Hi Friends,
    As Part of the Project Requirement,we need to convert DTS packages to SQL Server 2012 environment.
    Please sugest me best approach.
    Thanks

    Best approach is to re-design the packages in SSIS 2012 directy if it is feasible. Because most of the DTS feaures are discontinued and also you will have to clean up all errors that you are going to get after migration.
    Discontinued Integration Services Functionality in SQL Server 2012
    Otherwise you need to migrate it first to 2008R2 and then 2012 version.
    Below ones would be helpful for you:
    Migrate DTS packages to SSIS (SSIS2008R2)
    Support of DTS packages in 2008 R2
    Known DTS Package Migration Issues
    Cheers,
    Vaibhav Chaudhari

  • [SOLVED] unable to play mp3 or flac files in mpd, .dts files play fine

    I had a perfect running mpd setup before I tried to fiddle around with some dependancies to get xbmc-svn to compile without errors. I installed some AUR packages (ffmpeg-svn, x264-git, libva-sds, libvpx, libid3tag).
    After that I started to experience trouble with mpd, it start fine and says it plays audio files just fine but whenever i play a mp3 or flac file the progress bar just looks like it's playing the file but I hear no sound. Whenever I play a .dts file i hear the sound correct.
    I'm very curious to why this happends.
    I rolled back the packages mentioned above but the issue remains unsolved.
    My setup: pc is connected to receiver by hdmi cable using the latest alsa version with digital passthrough over hdmi, currently using mpd-git from AUR
    mpd -v --no-daemon shows the following:
    # mpd -v --no-daemon /etc/mpd.conf
    config: loading file /etc/mpd.conf
    listen: binding to address for 192.168.1.3
    listen: binding to socket address 192.168.1.3:6600
    path: path_set_fs_charset: fs charset is: UTF-8
    database: reading DB
    disabling the last.fm playlist plugin because account is not configured
    daemon: opening pid file
    daemon: writing pid file
    snippet from mpd.log:
    Jun 28 00:54 : client: [0] process command "playlistfind filename "Lossy - Tagged and Sorted/Wild Oats/WO-0001 - Kyle Hall - Worx Of Art EP 1 - 2008/Kyle Hall - 01 - Fuse N Me .mp3""
    Jun 28 00:54 : client: [0] command returned 0
    Jun 28 00:54 : client: [0] process command "addid "Lossy - Tagged and Sorted/Wild Oats/WO-0001 - Kyle Hall - Worx Of Art EP 1 - 2008/Kyle Hall - 01 - Fuse N Me .mp3""
    Jun 28 00:54 : add to playlist: Lossy - Tagged and Sorted/Wild Oats/WO-0001 - Kyle Hall - Worx Of Art EP 1 - 2008/Kyle Hall - 01 - Fuse N Me .mp3
    Jun 28 00:54 : database: get song: Lossy - Tagged and Sorted/Wild Oats/WO-0001 - Kyle Hall - Worx Of Art EP 1 - 2008/Kyle Hall - 01 - Fuse N Me .mp3
    Jun 28 00:54 : client: [0] command returned 0
    Jun 28 00:54 : client: [0] process command "playid "7""
    Jun 28 00:54 : playlist: play 7:"Lossy - Tagged and Sorted/Wild Oats/WO-0001 - Kyle Hall - Worx Of Art EP 1 - 2008/Kyle Hall - 01 - Fuse N Me .mp3"
    Jun 28 00:54 : decoder_thread: clearing mixramp tags
    Jun 28 00:54 : decoder_control: mixramp_start = NULL
    Jun 28 00:54 : decoder_control: mixramp_prev_end = NULL
    Jun 28 00:54 : client: [0] command returned 0
    Jun 28 00:54 : client: [0] process command "status"
    Jun 28 00:54 : client: [0] command returned 0
    Jun 28 00:54 : client: [0] process command "idle"
    Jun 28 00:54 : client: [0] command returned 1
    Jun 28 00:54 : client: [0] process command "playlistid "7""
    Jun 28 00:54 : client: [0] command returned 0
    Jun 28 00:54 : mad: detected LAME version 3.97 ("LAME3.97 ")
    Jun 28 00:54 : mad: LAME peak found: 0.000000
    Jun 28 00:54 : mad: LAME track gain found: -5.000000
    Jun 28 00:54 : mad: encoder delay is 576, encoder padding is 1818
    Jun 28 00:54 : decoder: audio_format=44100:24:2, seekable=true
    Jun 28 00:54 : alsa: default period_time = buffer_time/4 = 185759/4 = 46439
    Jun 28 00:54 : client: [0] process command "plchangesposid "2""
    Jun 28 00:54 : client: [0] command returned 0
    Jun 28 00:54 : alsa: buffer_size=8192 period_size=2048
    Jun 28 00:54 : output: opened plugin=alsa name="My ALSA Device" audio_format=44100:32:2
    Jun 28 00:54 : output: converting from 44100:24:2
    Jun 28 00:54 : Failed to open mixer for 'My ALSA Device': no such mixer control: PCM
    mpd.conf:
    # An example configuration file for MPD
    # See the mpd.conf man page for a more detailed description of each parameter.
    # Files and directories #######################################################
    # This setting controls the top directory which MPD will search to discover the
    # available audio files and add them to the daemon's online database. This
    # setting defaults to the XDG directory, otherwise the music directory will be
    # be disabled and audio files will only be accepted over ipc socket (using
    # file:// protocol) or streaming files over an accepted protocol.
    music_directory "/media/media9/Muziek/"
    # This setting sets the MPD internal playlist directory. The purpose of this
    # directory is storage for playlists created by MPD. The server will use
    # playlist files not created by the server but only if they are in the MPD
    # format. This setting defaults to playlist saving being disabled.
    playlist_directory "/var/lib/mpd/playlists"
    # This setting sets the location of the MPD database. This file is used to
    # load the database at server start up and store the database while the
    # server is not up. This setting defaults to disabled which will allow
    # MPD to accept files over ipc socket (using file:// protocol) or streaming
    # files over an accepted protocol.
    db_file "/var/lib/mpd/mpd.db"
    # These settings are the locations for the daemon log files for the daemon.
    # These logs are great for troubleshooting, depending on your log_level
    # settings.
    # The special value "syslog" makes MPD use the local syslog daemon. This
    # setting defaults to logging to syslog, otherwise logging is disabled.
    log_file "/var/log/mpd/mpd.log"
    # This setting sets the location of the file which stores the process ID
    # for use of mpd --kill and some init scripts. This setting is disabled by
    # default and the pid file will not be stored.
    pid_file "/var/run/mpd/mpd.pid"
    # This setting sets the location of the file which contains information about
    # most variables to get MPD back into the same general shape it was in before
    # it was brought down. This setting is disabled by default and the server
    # state will be reset on server start up.
    state_file "/var/lib/mpd/mpdstate"
    # The location of the sticker database. This is a database which
    # manages dynamic information attached to songs.
    #sticker_file "~/.mpd/sticker.sql"
    # General music daemon options ################################################
    # This setting specifies the user that MPD will run as. MPD should never run as
    # root and you may use this setting to make MPD change its user ID after
    # initialization. This setting is disabled by default and MPD is run as the
    # current user.
    user "mpd"
    # This setting specifies the group that MPD will run as. If not specified
    # primary group of user specified with "user" setting will be used (if set).
    # This is useful if MPD needs to be a member of group such as "audio" to
    # have permission to use sound card.
    #group "nogroup"
    # This setting sets the address for the daemon to listen on. Careful attention
    # should be paid if this is assigned to anything other then the default, any.
    # This setting can deny access to control of the daemon.
    # For network
    bind_to_address "192.168.1.3"
    # And for Unix Socket
    #bind_to_address "~/.mpd/socket"
    # This setting is the TCP port that is desired for the daemon to get assigned
    # to.
    port "6600"
    # This setting controls the type of information which is logged. Available
    # setting arguments are "default", "secure" or "verbose". The "verbose" setting
    # argument is recommended for troubleshooting, though can quickly stretch
    # available resources on limited hardware storage.
    log_level "verbose"
    # If you have a problem with your MP3s ending abruptly it is recommended that
    # you set this argument to "no" to attempt to fix the problem. If this solves
    # the problem, it is highly recommended to fix the MP3 files with vbrfix
    # (available from <http://www.willwap.co.uk/Programs/vbrfix.php>), at which
    # point gapless MP3 playback can be enabled.
    #gapless_mp3_playback "yes"
    # This setting enables MPD to create playlists in a format usable by other
    # music players.
    #save_absolute_paths_in_playlists "no"
    # This setting defines a list of tag types that will be extracted during the
    # audio file discovery process. Optionally, 'comment' can be added to this
    # list.
    #metadata_to_use "artist,album,title,track,name,genre,date,composer,performer,disc"
    # This setting enables automatic update of MPD's database when files in
    # #music_directory "path_to_your_music_collection"
    auto_update "yes"
    # Limit the depth of the directories being watched, 0 means only watch
    # the music directory itself. There is no limit by default.
    #auto_update_depth "3"
    # Symbolic link behavior ######################################################
    # If this setting is set to "yes", MPD will discover audio files by following
    # symbolic links outside of the configured #music_directory "path_to_your_music_collection"
    #follow_outside_symlinks "yes"
    # If this setting is set to "yes", MPD will discover audio files by following
    # symbolic links inside of the configured #music_directory "path_to_your_music_collection"
    #follow_inside_symlinks "yes"
    # Zeroconf / Avahi Service Discovery ##########################################
    # If this setting is set to "yes", service information will be published with
    # Zeroconf / Avahi.
    #zeroconf_enabled "yes"
    # The argument to this setting will be the Zeroconf / Avahi unique name for
    # this MPD server on the network.
    #zeroconf_name "Music Player"
    # Permissions #################################################################
    # If this setting is set, MPD will require password authorization. The password
    # can setting can be specified multiple times for different password profiles.
    #password "password@read,add,control,admin"
    # This setting specifies the permissions a user has who has not yet logged in.
    #default_permissions "read,add,control,admin"
    # Input #######################################################################
    input {
    plugin "curl"
    # proxy "proxy.isp.com:8080"
    # proxy_user "user"
    # proxy_password "password"
    # Audio Output ################################################################
    # MPD supports various audio output types, as well as playing through multiple
    # audio outputs at the same time, through multiple audio_output settings
    # blocks. Setting this block is optional, though the server will only attempt
    # autodetection for one sound card.
    # See <http://mpd.wikia.com/wiki/Configuration#Audio_Outputs> for examples of
    # other audio outputs.
    # An example of an ALSA output:
    audio_output {
    type "alsa"
    name "My ALSA Device"
    device "hw:0,3" # optional
    ## format "44100:16:2" # optional
    ## mixer_type "hardware" # optional
    ## mixer_device "default" # optional
    ## mixer_control "Master" # optional
    ## mixer_index "0" # optional
    # An example of an OSS output:
    #audio_output {
    # type "oss"
    # name "My OSS Device"
    ## device "/dev/dsp" # optional
    ## format "44100:16:2" # optional
    ## mixer_type "hardware" # optional
    ## mixer_device "/dev/mixer" # optional
    ## mixer_control "PCM" # optional
    # An example of a shout output (for streaming to Icecast):
    #audio_output {
    # type "shout"
    # encoding "ogg" # optional
    # name "My Shout Stream"
    # host "localhost"
    # port "8000"
    # mount "/mpd.ogg"
    # password "hackme"
    # quality "5.0"
    # bitrate "128"
    # format "44100:16:1"
    ## protocol "icecast2" # optional
    ## user "source" # optional
    ## description "My Stream Description" # optional
    ## genre "jazz" # optional
    ## public "no" # optional
    ## timeout "2" # optional
    ## mixer_type "software" # optional
    # An example of a recorder output:
    #audio_output {
    # type "recorder"
    # name "My recorder"
    # encoder "vorbis" # optional, vorbis or lame
    # path "/var/lib/mpd/recorder/mpd.ogg"
    ## quality "5.0" # do not define if bitrate is defined
    # bitrate "128" # do not define if quality is defined
    # format "44100:16:1"
    # An example of a httpd output (built-in HTTP streaming server):
    #audio_output {
    # type "httpd"
    # name "My HTTP Stream"
    # encoder "vorbis" # optional, vorbis or lame
    # port "8000"
    ## quality "5.0" # do not define if bitrate is defined
    # bitrate "128" # do not define if quality is defined
    # format "44100:16:1"
    # max_clients "0" # optional 0=no limit
    # An example of a pulseaudio output (streaming to a remote pulseaudio server)
    #audio_output {
    # type "pulse"
    # name "My Pulse Output"
    ## server "remote_server" # optional
    ## sink "remote_server_sink" # optional
    ## Example "pipe" output:
    #audio_output {
    # type "pipe"
    # name "my pipe"
    # command "aplay -f cd 2>/dev/null"
    ## Or if you're want to use AudioCompress
    # command "AudioCompress -m | aplay -f cd 2>/dev/null"
    ## Or to send raw PCM stream through PCM:
    # command "nc example.org 8765"
    # format "44100:16:2"
    ## An example of a null output (for no audio output):
    #audio_output {
    # type "null"
    # name "My Null Output"
    # mixer_type "none" # optional
    # This setting will change all decoded audio to be converted to the specified
    # format before being passed to the audio outputs. By default, this setting is
    # disabled.
    #audio_output_format "44100:16:2"
    # If MPD has been compiled with libsamplerate support, this setting specifies
    # the sample rate converter to use. Possible values can be found in the
    # mpd.conf man page or the libsamplerate documentation. By default, this is
    # setting is disabled.
    #samplerate_converter "Fastest Sinc Interpolator"
    # Normalization automatic volume adjustments ##################################
    # This setting specifies the type of ReplayGain to use. This setting can have
    # the argument "off", "album" or "track". See <http://www.replaygain.org>
    # for more details. This setting is off by default.
    #replaygain "album"
    # This setting sets the pre-amp used for files that have ReplayGain tags. By
    # default this setting is disabled.
    #replaygain_preamp "0"
    # This setting enables on-the-fly normalization volume adjustment. This will
    # result in the volume of all playing audio to be adjusted so the output has
    # equal "loudness". This setting is disabled by default.
    #volume_normalization "no"
    # MPD Internal Buffering ######################################################
    # This setting adjusts the size of internal decoded audio buffering. Changing
    # this may have undesired effects. Don't change this if you don't know what you
    # are doing.
    #audio_buffer_size "2048"
    # This setting controls the percentage of the buffer which is filled before
    # beginning to play. Increasing this reduces the chance of audio file skipping,
    # at the cost of increased time prior to audio playback.
    #buffer_before_play "10%"
    # Resource Limitations ########################################################
    # These settings are various limitations to prevent MPD from using too many
    # resources. Generally, these settings should be minimized to prevent security
    # risks, depending on the operating resources.
    #connection_timeout "60"
    #max_connections "10"
    #max_playlist_length "16384"
    #max_command_list_size "2048"
    #max_output_buffer_size "8192"
    # Character Encoding ##########################################################
    # If file or directory names do not display correctly for your locale then you
    # may need to modify this setting.
    #filesystem_charset "UTF-8"
    # This setting controls the encoding that ID3v1 tags should be converted from.
    #id3v1_encoding "ISO-8859-1"
    # SIDPlay decoder #############################################################
    # songlength_database:
    # Location of your songlengths file, as distributed with the HVSC.
    # The sidplay plugin checks this for matching MD5 fingerprints.
    # See http://www.c64.org/HVSC/DOCUMENTS/Songlengths.faq
    # default_songlength:
    # This is the default playing time in seconds for songs not in the
    # songlength database, or in case you're not using a database.
    # A value of 0 means play indefinitely.
    # filter:
    # Turns the SID filter emulation on or off.
    #decoder {
    # plugin "sidplay"
    # songlength_database "/media/C64Music/DOCUMENTS/Songlengths.txt"
    # default_songlength "120"
    # filter "true"
    Whenever I run xbmc using the hdmi digital output it just plays mp3 and flac files without problems.
    Anyone any clues on how to solve this issue?
    TIA, dafart
    Since
    Last edited by dafart (2010-07-01 00:38:09)

    aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    Which correspondents fine with the
    device "hw:0,3"
    in my mpd.conf alsa section.
    Also sound worked fine withh this config before I started installing ffmpeg-svn and alikes
    hokasch:
    I tried changing the mixer to "Master" but that did not change much.

  • How to add a new dimension in ASO cube without losing all data

    Hi,
    I have an ASO cube with 18 dimensions and I want to add a new one (regular). When I add this new dimension it asked me that the all data has to cleared before the restructure can take place. If I click yes then I would lose all data regardless of the fact if I have a level0 export or not. Because when I tried to reload the export back into the cube it gave me an error cause all the dimensions were not present in the export. Does anyone know how would I be able to accomplish this task?
    Thanks
    fikes

    You can try this work around solution.
    1) Export Lev0 data
    2) Clear the cube
    3) Add new dimension Regular.
    4) Add a default member Reg00 in the new dimension and save.
    5) Open the Lev0 data in a text editor, Insert "Reg00" in the begining of the file and Enter.
    6) Lev0 file will have first record "Reg00" and the remaining export file will be from the second record.
    7) Load the modified file with out rule file.
    You can verify that all your history data will be loaded w.r.to the Reg00 of the New dimension Regular.

  • Issue with write Security filter in ASO 9.3.1

    Hello All -
    I'm having a strange security filter issue in system 9.3.1 ASO cube. We've the native users for the ASO cube and created several write security filters based on cost centers in that cube.
    For example, the below security filter sometime works, and sometime not:
    Write "Adjustments", @RELATIVE ("S532179", 0), @RELATIVE ("S587724", 0), @RELATIVE ("S525701", 0)
    There are total 8 standard dimensions in the cube. I tried all possible combinations to make it work constantly, but it doesn't. Even modified the filter like below so that it has all dimensions (using LEVMBBRS, IDESCENDANTS, RELATIVE) , still users can't load data at level 0 members.
    Write @LEVMBRS ("Chart of Accounts",0),@LEVMBRS ("Full Year",0),@LEVMBRS ("Business Unit",0),@LEVMBRS ("Fixed/Variable",0),@LEVMBRS ("Source",0),@LEVMBRS ("Products",0),@LEVMBRS ("Scenario",0),@LEVMBRS ("Cost Center",0)
    It looks like the user and filter association is not working. If I give the user direct write access to the cube (bypassing filter totally), the users can write fine. Please help!

    I didn't know that the logs didn't work; I tested it and they are not generated for ASO updates in 9.3.1. I didn't see any other setting that would cause them to be created; my guess is that the logs are created based on block manipulations that Essbase does internally using BSO. As there are no blocks in ASO then the same algorithm doesn't apply.
    We log Essbase changes in our Dodeca product but we use a different algorithm. We evaluate the update in our server before committing the changes and generate a relational log that has the datapoint information plus the old value, new value and standard 'who' information for the person making the update.
    Tim Tow
    Applied OLAP, Inc

  • I have some dts cd's that I want to import into itunes on a windows pc and then play back on my apple tv 3 (i think its 3, about 9 months old) to listen to through my onkyo amp via hdmi as dts, when I play back I just get white noise.

    I have some dts cd's that I want to import into itunes on a windows pc and then play back on my apple tv 3 (i think its 3, about 9 months old) to listen to through my onkyo amp via hdmi as dts, when I play back I just get white noise. I have seen lots of old posts which go on about converting files but am wondering wherher at the current time with the latest versions of itunes and apple tv whether this should by now be a virtual play out of the box solution.
    I have tried connecting my atv to the amp by optical cable but that didnt produce anything better and am assuming that a hdmi cable should be able to reproduce everything an optical cable does.
    Is this something I should be able to achieve without having to recode the files?
    Tracks are imported to itunes as apple lossless, have tried setting the atv audio settings to auto and 16 bit, neither works yet I was told some time ago by an apple rep that the atv shoud be able to handle any type of audio as it just passes it to the amp to decode. I am not stupid but not that technical when it comes to audio and bitrates etc so any explaination would be appreciated.
    Thanks in advance for any help

    Willy, the procdedure you describe works perfectly for AppleTV G1. In fact, I frequently play DTS music discs ripped to my iTunes library as Apple Lossless (ALAC) and synched to the ATV. What happens is that, as far as iTunes and the ATV are concerned, a conventional stereo 16/44 audio file is being played; however my reciever detects the DTS data stream, and instead of outputting static, it decodes the 5.1 channels correctly. This process parallels the way DTS discs were designed to be played back: a conventional CD player is connceted, via digital out, to a DTS-aware reciever/pre-amp and the two channels of static are recognized as 6 channels of DTS-encoded audio.
    However this process will only work if the player (CD, ATV, PC, etc.) sends a "bit-perfect" 16 bit/44.1 khz data stream to the decoding device. In the case of ATV G2 and G3, as has been discussed elsewhere, the unit resmaples all audio - including 16/44 PCM (Redbook CD)  - to 16/48. While this is not a big deal for conventional audio CDs, MP3s, and AAC files, it mangles the fragile DTS datastream and renders it undecodable. The resulting static that you hear is just like the static you would hear if you played a DTS CD on a non-DTS capable system.
    Sadly, I'm not aware of any easy way around this. You could use a program like Foobar (and the DTS plugin) to convert your DTS CDs to 6-ch .wav or .flac file. From there you could transcode the file to AC-3 and then mux it into a video container that ATV supports. You may need add a dummy video track, for iTunes/AppleTV to be ok with the file, though I'm not sure. This may be a lot of work.
    Sorry for the bad news. I wish that the iTunes/ATV ecosystem had better multi-channel audio support.
    Steven

  • BSO to ASO Formula Conversion - Help Needed

    ASO is not my forte...I am trying to get a simple formula to work in ASO cube as part of BSO-&gt;ASO conversion.
    If it is level 0 entity, the formula is (Last Shipped (PU) * Part Volume)...works fine.
    If its upper level, it should just sum the values of its children. The BSO equivalent that we typically use is @SUM(@CHILDREN(@CURRMBR("Entity"))).
    I attempted the same in the ASO MDX script as shown below, it is not yielding me the correct result....any thoughts why this is not working?
    Thanks in advance.
    Nima
    Member Formula*
    CASE WHEN ISLEVEL(Entity.CurrentMember, 0) THEN+
    Last Shipped (PU) x Part Volume+
    ELSE+
    SUM(Children(Entity.CurrentMember))+
    END+
    Edited by: Nima.V on Nov 12, 2008 7:12 PM

    Have you tried specifying which measure you want it to sum?
    e.g.
    CASE WHEN ISLEVEL(Entity.CurrentMember, 0) THEN
    Last Shipped (PU) x Part Volume
    ELSE
    SUM(Children(Entity.CurrentMember), [Measure].[Part Volume])
    END
    also I'm not sure whether the SUM is correct. This might work as it definately specifies the tuples:
    SUM({Products.CurrentMember.children},[Measures].[Part Volume])
    hope it helps,
    Gee

  • Data Write to ASO cube

    Hi,
    Please help.
    Case like that;
    Base member of Period in Planning is Month as calendar, but Base member of Period in ASO cube is Week, like that:
    Jan
        JanWeek1
        JanWeek2
        JanWeek3
        JanWeek4
        JanWeek5
    now, need to load planning data to ASO cube as reporting.
    but seems cannot directly load data from Jan in Planning to Jan in ASO cube, since Jan in ASO cube is a parent member. am i correct? what i tested in smartview is as that.
    so is there any better way to do that?
    Thank you.

    You can go ahead with the approach of what VBajaj has said.
    We have a similar process where our Plan data is 1 level higher than ASO (i., level1 of ASO is level0 of plan for most of the dimensions). So, we have created the level1 as level0 in ASO ending with _Plan and then loaded the data for those members.
    From a data loading standpoint, you can just put suffix in the rule file itself.
    Regards
    Amarnath
    ORACLE | Essbase

  • SQL Server to Oracle migration with SQL Server DTS

    I migrate database from SQL Server to Oracle with SQL Server DTS. the process is success. I can select table_name from user_tables or user_objects. I also can see the table from DBA Studio. But When I use desc to list the structure of table in SQLPLUS. it tell me object don't exist.
    What is wrong?
    Thanks

    use sp_help <tablename>

  • Report script taking very long time to export in ASO

    Hi All,
    My report script is taking very long time to execute and finally a message appears as timed out.
    I'm working on ASO Cubes and there are 14 dimensions for which i need to export all data for all the dimensions for only one version.
    The data is very huge and the member count in each dimension is also huge, so which is making me difficult to export the data.
    Any suggestions??
    Thanks

    Here is a link that addresses several ways to optimize your report script. I utilize report scripts for Level 0 exports in an ASO environment as well, however the majority of our dimemsions are attribute dimensions.
    These are the most effective solutions we have implemented to improve our exports via report scripts:
    1. Make sure your report script is written in the order of how the Report Extractor retrieves data.
    2. Supressing Zero and Missing Data
    3. We use the LINK command within reports for some dimensions that are really big and pull at Level 0
    4. Using Symmetric reports.
    5. Breakout the exports in multiple reports.
    However, you may also consider some additional solutions outlined in this link:
    1. The MDX optimizing commands
    2. Back end system settings
    http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/drpoptim.htm
    I hope this helps. Maybe posting your report script would also help users to provide feedback.
    Thanks
    Edited by: ronnie on Jul 14, 2011 9:25 AM
    Edited by: ronnie on Jul 14, 2011 9:53 AM

Maybe you are looking for